Forum Replies Created
-
Posts
-
Nice graphics!
But what if you have more than one cluster in a bank? How would holding the selector button show them, and more inportantly, differentiate? The individual cluster steps could be mixed (interleaved). The graphic doesn’t cover that, or does it?
I’ll very much need it when the next OS update will hit me. If it doesn’t support data downward compatibility I’ll probably be stuck to v1.42 for a long time.
But I know that this is very high on Gabriel’s list, so I’m not worried about it. He’s fully aware of the situation.
My live set will be the Octo, MPC4k and G2x, where the Octo will drive parts from both the G2x (obviously) and the MPC. Imagine the fun of a sequencer based patch on the G2x, driven by Octo…
For the studio both the Octo and MPC will have access to the rest of the gear, squeezed into 32 midi channels. I’m working on that right now.
Uhm, delicate question, but now that the bug videos did their job, maybe it’s a good idea to remove them from YouTube again?
I’m not trying to cover up, I just think that these videos may cause more damage in the end than the bug being discussed, which will no doubt be fixed (in my personal opinion).
Random ARP?
What if I make a track of 1 step long, set that step to a polyphony of 1, and start it. Next, you realtime-record chords into this step. My guess is that this is your random ARP.
gseher wrote:
Quote:Thanks once more for the input Robert.
Have some good news in that the monophonic switch is removed, the octave display is as we’ve had it, and the functionality seems to be all there. It’s all about the polyphony selectors. Will make a beta update shortly.DARN! I need that machine! Pronto!
My Octo will be delivered coming tuesday, so there’s your time frame, lol.Very excited over the fact that the polyphonic version of the random-pick is being implemented. It’s definitely some work.
As an addition, we could show the all of the notes pitch values in the pitch circle when one of the 7 note buttons is held down. In that case the circle shows green for ocatave 1, orange for octave 2, red for octave 3. Release that button and we get the note/rest/off info again.
Okay!
Here’s one more idea to possibly cleanup the interface around chord pool and the random pick from pool concept.
What if we do not color code the note’s octave (1, 2 or 3) in the note LED, but instead show that information elsewhere (e.g. where BPM is shown) with the note button held down?
That would result in a 3-step note sequence:
1. On (LED green or orange for base note)
2. Rest (LED blinking green).
3. Off (LED off).With the note button grabbed, use the main encoder to set the octave value to 1, 2 or 3.
Using your new chord-size approach, set the chord’s polyphony from 1-7, which adds rests when chord-size gets larger than note/rest-count (and these added rests show up in the circle).
The single monophonic switch you recently introduced is removed.
Yes, the price is that you no longer see the octave of the notes in the pitch circle. But it also leads to a cleaner interface, imo.
Without Octo it’s a bit hard to imagine how the note assignment within that grid would work. But if I get this right, you are free to assign whatever note to whatever page or track, right? That is, muscially related page/track trigger notes can be placed right next to each other on the keyboard, right? If that’s the case, this sure sounds like fun!
Regarding track trigger style, there’s lots of options:
1. A track always loops when triggered, until it gets triggered again with a velocity of zero. So several triggers with non-zero velo stutters the track. A note with zero velocity stops the track.
2. We could use several ‘hot’ velocity values: 0 for stop. 1 for one-shot, 2-9 for the corresponding amounts of loops, anything higher than 9 for permanent loops.
3. We could use even more hot velocity values to encode track playback speed. Certain ranges for slomo factors, other ranges for hi-speed factors. The default velo value (64?) must be placed in the range for normal playback speed.
Erm, I was still going for the 5-step on1, on2, on3, rest, off note selection approach, only with another color/blink scheme for the added rest state. In that case the new chord-size UI approach is free for polyphony, including a polyphony of 1.
When you said that the used orange color for the base not was not an issue, I assumed that another color would be available. But I guess I misinterpreted that one?
We have the following LED colors:
– off
– green-solid
– green-blink
– red-solid
– red-blink
– orange-solid
– orange-blinkWith the orange-solid scheme reserved for the base note, we still have 6 colors left for a 5-step button. Wouldn’t this work? I guess some other colors are used already?
