Save all scene assignable parameter changes, which have occurred since the part was last saved, to a scene. Starting with a just saved part; I often find myself tweaking away, and then wishing I could create a scene with the tweaks. Button combo, something like, [Scene A] + [trig 1] + [Part], would save all the changes to parameters that are scene assignable to scene 1.
Offer several static LFO waveforms. Deigning one with the designer costs time and a slot that would be better used for something a bit more interesting. There are many places when using the OT where a constant high-state or a constant low-state LFO waveform is required. Iād like to see 3 different high-state and 3 different low-state LFOs offered as standard waveforms. A high and low at 100%, 10 or 20 percent, and one notch above/below zero for fine-tuning of parameters.
Lot of folks would like to see midi scenes come to life. I have thought of two workarounds that might make it feasible.
a. This first idea is more convoluted to the user, but itās implementation should be easier to program. Offer midi LFO depth as a destination from the audio track LFO. It would work like this: on audio track 1, one of the LFO destination choices would be midi track 1, LFO 1 depth (midi track 1, LFO 2 and 3 depth could be offered as destinations as well). With the use of static LFOs, normal scene behavior could be assigned to 3 midi parameters per track. This limitation, with the addition to sacrificing a midi LFO, should keep the midi stream to an acceptable level.
b. Offer midi track LFO depth as a scene assignable parameter. Similar to above, but one step easier to the user. Probably, more laborious to program.
A little sidenote to thatā¦ on my still_to_try listā¦
to my knowledge the crossfader sends out CC# 78.
Always wondered what would happen if i map the joystick control of the monomachine to the ot_fader_cc ā¦ might not work
might sound horribleā¦ orā¦
never tried it thoughā¦ so many things on my to try listā¦
and on topicā¦
yeahā¦ be fun if i could use the fader for the midi-stuff.
I understand their worriesā¦ butā¦ in this case i would say
i dont care it still a nice feature if they can add it.
A little sidenote to thatā¦ on my still_to_try listā¦
to my knowledge the crossfader sends out CC# 78.
Always wondered what would happen if i map the joystick control of the monomachine to the ot_fader_cc ā¦ might not work
might sound horribleā¦ orā¦
never tried it thoughā¦ so many things on my to try listā¦
and on topicā¦
yeahā¦ be fun if i could use the fader for the midi-stuff.
I understand their worriesā¦ butā¦ in this case i would say
i dont care it still a nice feature if they can add it.[/quote]
Wouldnāt you need another device to convert the CC#s? I thought about this as well but I donāt want to add one more device.
Iād like to see this, even if just so you could mute MIDI channels in a scene! This would make a huge difference, and if the OT was also handling the audio from the synths, thereās a lot you can do with scenes to mangle the audio. You could still achieve big mix changes between the scenes.
I am almost certain that this will be implemented in time. It would be magical and Elektron make magical musical devices. That is unless the next black box would be undermined by such a great moveā¦
Itās quite possible that doing morphs will cause midi congestion.
Fot example, if you have 8 midi tracks and lock all the 10 ccās you have 80 ccās simultaneously generated per ā tickā the crossfader moves.
Iām assuming the crossfader has a resolution of 127 steps here. so if you flick the crossfader from left to right in a quarter of a second you will generate
this will be 40640 messages per second.
Add up youāre sending note data as well for 8 tracks.
I think youāll experience timing problems and other strange behaviour on the machines that are sequenced by the octa.
So, what would you do? Implement it with a warning not to use it too extensive, causing a lot of discussion what should and shouldnt be possible.
Iād love to see this but I think it will cause a mess midi-wise.
Itās quite possible that doing morphs will cause midi congestion.
Fot example, if you have 8 midi tracks and lock all the 10 ccās you have 80 ccās simultaneously generated per ā tickā the crossfader moves.
Iām assuming the crossfader has a resolution of 127 steps here. so if you flick the crossfader from left to right in a quarter of a second you will generate
this will be 40640 messages per second.
Add up youāre sending note data as well for 8 tracks.
I think youāll experience timing problems and other strange behaviour on the machines that are sequenced by the octa.
So, what would you do? Implement it with a warning not to use it too extensive, causing a lot of discussion what should and shouldnt be possible.
Iād love to see this but I think it will cause a mess midi-wise.
.R
[/quote]
implement it without the fader morphā¦yeah, limited if you compared with the audio scenes but having static midi scenes would be great anyway
it still a nice feature if they can add it.