New to using the 301 and have some questions about devices

That’s what I’ve used with it so far, for a “traditional” wave folder type of thing. But again, Brian is very clever in designing these units, and wave folding is perhaps just one application for it. So I wouldn’t conclusively say yes, single cycle is best. Very possible other applications for this unit have yet to reveal themselves to us. Here’s a thread on the sample scanner.

(Edit: I need to review this thread - some good stuff posted here, including making a wavetable oscillator!)

Have a look here for a better and more concise description than I could come up with.

http://wiki.orthogonaldevices.com/index.php/ER-301/Variable_Speed_Player#Address_Mode

1 Like

I have an question regarding i/o routing for this chain

If I’m understanding your question correctly there are a couple of possible solutions in the current firmware.

The first (possibly easiest to grok the first time) is to build part of your chain as a global chain. In your case I think this would be the grain stretch, sample scanner, and limiter units. A global chain (accessed by flipping the first/left rocker switch to admin mode) is not tied to a physical output. But it can be referenced anywhere you can select a physical input (or output) by toggling the selection to “globals”. Therefore you could use the global chain’s output as both the main signal source on channel 1, and also as the input to your envelope follower inside the subchain of the LPF.

The second would be to build this entire thing as a custom unit. Perhaps try the global chain approach first, as the concepts are really similar, and the custom unit approach will make more sense after you’ve done that.

Check out @NeilParfitt’s video on global chains. I think it will help you get the idea.

http://wiki.orthogonaldevices.com/index.php/ER-301/Neil's_Getting_Started_Videos#What_is_a_Global_Chain.3F

2 Likes

Perfect! The global chain was the solution to my issue. I will investigate custom chains as well!

Thanks again for the prompt response

2 Likes

Glad to be of help, and welcome to the rabbit hole. :slight_smile:

What was your sample in that video? I liked the sound you were getting.

1 Like

Lol happy to be here, The song is an unfinished track that i’ve been working on, just through the entire thing in there and granulated it with some random on the slicer. The white noise that was threw a sample and hold was triggered via gate coming from my daw to sync it with the drum loop I had. I’ve uploaded the track here so you can play with it if you like :smiley: its the least I can do for your time spent helping this newbie

1 Like

Weird i thought I attached the file to this message and it showed it was uploaded. Does this site not support file uploads larger than a certain file size?

I think it is 3Mb limit.

ahh, well in that case here is a google drive link for you

https://drive.google.com/file/d/12fawteRQ0fRa51fFQ-FmuRMfLs18HTdz/view?usp=sharing

I’ll probably take the link down in a few days, but let me know if it doesn’t work for any reason

1 Like

Got it! Thanks for sharing. Doesn’t sound terribly unfinished to me. Lots of sound variety in there. I like it even before the “remix.” :slight_smile:

Thanks I appreciate that

Having a lot of fun today, been playing with this all day and my little brother has been getting a kick out of what this thing can do. I have another question regarding zooming in on waveforms as shown in this video I took.

To my knowledge there is currently no adjustment of the waveforms that appear in the lower display. There is also no adjustment of the waveform displays in the upper screen that are “live” type waveform displays. There is however, vertical and horizontal zoom control over the waveform display in the sample slice/edit views. Those are accessed by holding the fine/coarse button down and turning the encoder. Pressing the fine/coarse button toggles whether you are zooming vertically or horizontally.

Also, I’m going to tag your topic with ER-301 just to give it a little more visibility. Some ER-301 users may only monitor that category.

1 Like

Good to know thanks. What is the purpose of the focus buttons next to each of the displays?

In some cases, pressing an M button will execute an action, such as inserting the unit that is above that button on the insert menu. In other cases it focuses a control so that it can be adjusted with the encoder.

I’m not sure why it has a box around it as though it requires the shift key to do the focus function. It doesn’t. Perhaps something that will be unveiled in a later firmware?

1 Like

I played around with these a bit in the scale quantizer. As far as I can tell they are just offsets that affect the voltage before and after the quantization. If you had some incoming CV signal you were quantizing into a melody, you could use the post control for transposition (e.g. C major to D major). You could use the pre control to adjust which register it’s quantizing in (e.g. think of a piano keyboard or guitar fretboard, playing the exact same notes up higher without transposing the key.)

To adjust the actual range of notes (e.g. cover more octaves of the scale) you’d probably want a VCA before the quantizer. You could do the same things the pre and post do by basically just putting an offset unit before and after, but these are handy since they’re built in, and also have a scale of V/Oct rather than a linear scale like the offset unit does.

1 Like

Multiple mapped to one knob

Ideas anyone?

Mapping the 3 custom controls so that they are all controlled by a single (additional) custom control should be pretty straightforward. You could just create the new custom control (let’s call it “master” for sake of discussion). Then go into the subchain for each of the existing controls, and set their modulation source to be the local control “master”. You could assign a gain amount (pos or negative), and also a +/- bias amount so that they could even move by different amounts and in different directions when “master” changes. Alternatively, you could use an external offset coming in through one of the ABCDx ports to simultaneously control all 3.

It sounds like what you actually want to do is to have something more like preset values. I.e. if “master” is at 1.0, then control 1 should “jump” to a specific value, control 2 should “jump” to a different specific value. If master is at 2.0 then they “jump” to arbitrary (but preset) new values.

I think that the latter is possible strictly using the ER-301. You would have to use recorded samples to store values for the destination controls for each preset stop, and slice the sample so that the “master” control could play the correct slice of the sample corresponding to the preset.

I will offer up this tutorial video I made a while back. It is not quite exactly what you’re trying to do, but it leverages the sample player as a means to store and recall CV values. It is probably enough for you to make the connection.

http://wiki.orthogonaldevices.com/index.php/ER-301/Joe's_Tutorials_and_Patches#Quantize_to_Any_Scale_with_Probability

Of final note, the monome teletype, using the i2c connection to the ER-301 would make something like this pretty trivial. So might mutable instruments frames.

The other thing you might want to have a look at is the somewhat tentative roadmap for the 301. (Also read the caveats that the list is not a guarantee).

http://wiki.orthogonaldevices.com/index.php/ER-301/Tracker

But some things that are pretty involved workarounds today may be trivially easy in tomorrow’s firmware. In your particular question I am looking at some of the plans in the “Unit Parameters” section.

One more edit: something like this might already be pretty easy if you were to build it in the middle layer (LUA code). There I think you might be able to define specific values that each control is allowed to stop at. I’m not 100% sure as I’m still learning the middle layer myself. And as you just got your 301 it might not be something you even want to think about yet, but thought I’d include it. :slight_smile:

2 Likes

Great solutions! Thanks again!