|
Post by John Tennison on Sept 27, 2017 14:47:10 GMT
Thanks, Nic. I'll give it a try.
|
|
|
Post by John Tennison on Sept 27, 2017 15:45:22 GMT
It works great. Thanks. (There were a couple of typos for controller 120 and 123, (FF had to be changed to 7F), but I had known what you meant.)
With great admiration for your genius, John "Nonjohn" Tennison
|
|
|
Post by John Tennison on Sept 27, 2017 20:07:24 GMT
I keep on thinking of ways that would make my setup more useful.
If I wanted to maintain the same functionality as before in terms of the the various CC values being sent out on 16 channels upon receiving a note-on, would there be a way to do that in Stream Byter and only block note-on/note-off events. That is, I occasionally need the same source to send program change commands or other one-time CC commands that I would not want re-channelized, but would want sent through unaltered.
Thanks.
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Sept 27, 2017 20:17:35 GMT
Sure. Change the blocking rule:
XX = XX +B
to
NX = XX +B
Regards, Nic.
|
|
|
Post by John Tennison on Sept 28, 2017 2:02:44 GMT
Thanks.
|
|
|
Post by carnbot on Jan 27, 2018 17:52:16 GMT
I hope the midi note remapper comes soon. In the meantime I guess the only way to make CCs trigger notes is with StreamByter too?
many thanks!
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jan 27, 2018 20:37:56 GMT
Hi carnbot , Yes, Stream Byter only for now but hope to push out a release with some MidiBridge modules ported to MidiFire very soon. If you let me know how exactly you want CCs mapped to notes I will give you a set of rules. Regards, Nic.
|
|
|
Post by carnbot on Jan 28, 2018 13:00:51 GMT
Hi carnbot , Yes, Stream Byter only for now but hope to push out a release with some MidiBridge modules ported to MidiFire very soon. If you let me know how exactly you want CCs mapped to notes I will give you a set of rules. Regards, Nic. Hi Nic, Many thanks. Well specifically I'm trying to remap CC's coming from led faders on a livid controller into notes so I can use them as a Step sequencer. Actually just remapping CCs would be useful first, which is probably easier, so I can use the controller with an app called Quantum a step sequencer with mid learnable controls. The Livid base can only send out 8 different CC's for the faders. But it has 7 states of presets which can remember different positions of the faders and sends out on different midi channels. So I'm thinking to use midifire to use the different midi channel presets to change and remap these CC's to different ones so I can midi learn a lot more steps of the sequencer than just the 8 cc's currently, so the remapped cc's would send and receive on the different channels. So I guess I would need different stream byter instances for different midi channels 2-7 remapping 8 CC's to different CC's giving me 56 CCs to use (including the original 8). The first midi channel 1 can remain unchanged. I've not used the Stream byter yet so I'm still a bit green with it
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jan 29, 2018 9:51:26 GMT
Hi carnbot , OK, I'm trying to wrap my head around what happens when a state preset is recalled. Maybe you can explain this for me? I looked at the livid documentation but it wasn't at all clear. Maybe you could hook up an event monitor in MidiFire and observe: - the CC messages on the faders *before* preset is recalled - any messages when the preset is recalled (we might need to watch for these to change internal state in the Stream Byter) - the CC messages on the faders *after* the preset is loaded That would really help me understand how this device works (I don't have one myself) and we'll be able to set something up so you can drive Quantum and also your ultimate goal of converting the CCs to notes. Regards, Nic.
|
|
|
Post by carnbot on Jan 29, 2018 12:56:18 GMT
Hi carnbot , OK, I'm trying to wrap my head around what happens when a state preset is recalled. Maybe you can explain this for me? I looked at the livid documentation but it wasn't at all clear. Maybe you could hook up an event monitor in MidiFire and observe: - the CC messages on the faders *before* preset is recalled - any messages when the preset is recalled (we might need to watch for these to change internal state in the Stream Byter) - the CC messages on the faders *after* the preset is loaded That would really help me understand how this device works (I don't have one myself) and we'll be able to set something up so you can drive Quantum and also your ultimate goal of converting the CCs to notes. Regards, Nic. Thanks Nic! Here's what's happening in the event monitor for the Base:
if you open the image in a new tab to view it larger. I can see that it sends a sysex message when changing presets of the positions of all 8 faders since this number is only different if the faders are in a different position. maybe that's important. I didn't think it would be more complex than having it listen to ccs on different channels and change them respectively but do you think I would need to manipulate the sysex too? many thanks
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jan 29, 2018 18:41:57 GMT
Hi carnbot , That's great stuff, thanks. The pieces are falling into place but a couple of things I still need to understand if I may. The fader CC changed from controller 1 to 2 after recalling and reverting the preset. This seems very strange. Are you sure you moved the same fader? Could you please try: - move fader 1 and then fader 8 - recall preset 2 - mover fader 1 and 8 again - recall preset used in first step - move faders 1 and 8 again We now can know whenever we switch to one of the presets via that sysex, which I think we are going to need. I just need to figure out whether those faders' CC numbers actually change before/after preset (I suspect they don't and we'll use the sysex to maintain which preset is currently active). You don't need to copy the UI graphics if you don't want to. All I need to know is the channel and number of the faders in each phase of the above experiments. Regards, Nic.
|
|
|
Post by carnbot on Jan 31, 2018 1:27:45 GMT
Hi carnbot , That's great stuff, thanks. The pieces are falling into place but a couple of things I still need to understand if I may. The fader CC changed from controller 1 to 2 after recalling and reverting the preset. This seems very strange. Are you sure you moved the same fader? Could you please try: - move fader 1 and then fader 8 - recall preset 2 - mover fader 1 and 8 again - recall preset used in first step - move faders 1 and 8 again We now can know whenever we switch to one of the presets via that sysex, which I think we are going to need. I just need to figure out whether those faders' CC numbers actually change before/after preset (I suspect they don't and we'll use the sysex to maintain which preset is currently active). You don't need to copy the UI graphics if you don't want to. All I need to know is the channel and number of the faders in each phase of the above experiments. Regards, Nic. Thanks for the assistance! Here are the steps in order numbered 1-5 . I did it as a screengrab so I didn't make any mistakes. I did move a different fader I think in the first example I sent yes
1. move fader 1 and then fader 8 2. recall preset 2 3. mover fader 1 and 8 again 4. recall preset used in first step 5. move faders 1 and 8 again
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jan 31, 2018 8:45:11 GMT
Hi carnbot , Parfait! I now understand how this works. OK, so when you change to preset 1 then the channel of the CC changes too (to channel 2) so you already can use MIDI Learn with Quantum and have it respond differently based on which preset is active (as the CC channel is different). We don't even need to worry about monitoring those sysex messages to know which preset is active. Therefore, I don't think you need to do anything to make this work how you want (7 presets x 8 faders) for Quantum - or have I missed something? Do you want them all mapped to unique CCs on one channel? We can easily remap those to notes too in whichever way you want. For example we could map each of the 56 CCs to 56 different notes or something different. We might need to send an extra note off as we go too, but that is easy. If you could let me know how you might want notes generated from the faders and presets I can advise further. Regards, Nic.
|
|
|
Post by carnbot on Jan 31, 2018 17:05:38 GMT
Hi carnbot , Parfait! I now understand how this works. OK, so when you change to preset 1 then the channel of the CC changes too (to channel 2) so you already can use MIDI Learn with Quantum and have it respond differently based on which preset is active (as the CC channel is different). We don't even need to worry about monitoring those sysex messages to know which preset is active. Therefore, I don't think you need to do anything to make this work how you want (7 presets x 8 faders) for Quantum - or have I missed something? Do you want them all mapped to unique CCs on one channel? We can easily remap those to notes too in whichever way you want. For example we could map each of the 56 CCs to 56 different notes or something different. We might need to send an extra note off as we go too, but that is easy. If you could let me know how you might want notes generated from the faders and presets I can advise further. Regards, Nic. Hi Nic, Yes, I can use Quantum with midi learn fine for the first 8 steps. But Quantum has up to 64 steps and multiple tracks. so I want to control more steps with the different banks of faders. And yes The Base outputs each preset on different midi channels which is useful. So for this I just need to remap CCs 1-8 to different sets of 8 different CCs on midi channels 1-7 (the max number of base presets available) Quantum can only receive on one channel for a track so I want to be able to route it all to one channel in the output to Quantum. Quantum currently can't midi learn on multiple channels for example. This will be useful for controlling lots of things not just Quantum as it's annoying that Livid didn't allow different CCs on the Base presets by default. So I'll use the CC remapping to create extra banks of faders than the default 8 CCs I think it's pretty straightforward and will be even more so with a remapper module, just I'm not sure of the Stream Byter yet Although I do plan do do some more elaborate presets with midifire and the Livid base with the rest of the controls at some point. The interesting thing about the Base is you can control the LED lights and colors from an external source so that's something I want to do at a later time, eg highlight keyboard scales etc. Animate timelines etc
|
|
|
Post by carnbot on Jan 31, 2018 17:09:32 GMT
Do you want them all mapped to unique CCs on one channel? So yes exactly, this would be great
|
|