Hi AbsentFriend,AbsentFriend wrote: ↑31 Oct 2022Hi @Brian – great device!
A (hopefully small) request: When selecting a scene, would it be possible to send the switch-scene-CV even if the scene is already chosen in LaunchEon? Example scenario: I create a scene 1 where all players are off. Scenes 2 onward are playing any combination of patterns. I leave LaunchEon at scene 1 while editing a pattern in a connected player. If I then hit Run the player will play the currently selected pattern, even if I click Scene 1 in LaunchOn again. If I create a second "all-off" scene and alter between them, LaunchEon does not seem to send the CV anyway, unless it registers an actual pattern change, is that correct? And if so – is it by design?
Thanks again for a very useful RE.
Cheers.
Thanks for your kind words, it's always nice to hear that people are enjoying my stuff!
Wow, a great question for first thing in the morning too.
TL;DR - This is how plugins work, regardless of type, be it RE, VST, AU, AAX etc
.........................
So, first part of the problem is that CV is always on, and always has a value, which is unlike audio that can be nulled off as "empty buffer" when there is no "noise", or MIDI notes which become 0 velocity events when off; in other words CV always has an "on-state" even when it is off.
If we say that the output state of port 1 is 0, then a change internally in LaunchEon from one "memory store" of 0 to another memory store of 0 (i.e. switching scene), then the output will go from 0 to 0 - for context, the device which is outputting CV probably will rewrite the 0 as it makes less sense to check it first before rewriting as it just adds more work.
The second part of the problem is that, for performance reasons, this property change won't be passed between the device because the property hasn't changed, the DAW will filter it out. This is the case for both REs and VSTs, so the assumption would be the same for all plugin formats, as they all do more or less the same thing.
The third part of the problem is that the receiving CV device will filter out anything that doesn't change the input port value, again for performance reasons.
So ultimately it doesn't much matter what LaunchEon does here as sender, as there are two levels of filtering going on in the host and the receiver.
..................
All the above said... I think I might be able to trick my way around this, although it's difficult to know if it would work well on every receiving device. Let me experiment a little - certainly, I can get the signal past the host, then after that it's probably the case that some devices would be compatible and others wouldn't.
As a short term workaound you could click the pattern device on to any pattern that is empty before you hit Run?
Cheers,
Brian