nic
Soapbox Supremo  
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jan 15, 2019 10:48:34 GMT
Hi janosax , I have made an attempt at your random panner - I think it does most of what you are looking for but might need some refinement. I have created a new thread for this rather than bury it in this seemingly unrelated thread. Regards, Nic.
|
|
|
Post by danklim on Mar 7, 2019 19:53:22 GMT
Hi nic , is there any way to use this 'blue velvet' functionality for a KMI Soft Step? I want to use the same kind of controls (shown here www.youtube.com/watch?v=KD2kTBqm5ag ) to control the Ableton looper device and other things, but I have a softstep, not a blueboard. I'm new to Midifire and have never used steambyter, I see i can download the Blue Velvet scene from the scene's club in midifire but it looks like it relies on specific blueboard software. I don't know if it would work with the Softstep, but midi is midi so it should be possible, right? If so, how? Thanks, Dan
|
|
nic
Soapbox Supremo  
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Mar 7, 2019 20:40:22 GMT
Hi danklim, Actually Blue Velvet will work with anything that sends a note on with a down-press and a note off with a release (on channel 1) 'out of the box'. I think a softstep is highly configurable, so if you were to set it up to operate as above, then you could pipe it straight into the Blue Velvet module. Based on whether you do single, hold, double tap etc will change the MIDI channel of the note event so you can distinguish between the types of actions. Regards, Nic.
|
|
|
Post by danklim on Mar 14, 2019 3:06:13 GMT
Thanks Nic. That is awesome and it works great with the soft step!
Now, I’m trying to set up the blue velvet scene to trigger Ableton clip looping functions on the Mac and have some questions about the routing and other capabilities of the blue velvet script, can you please help answer?
For the routing- I have an iPad connected to Mac via a iConnectivity 4+ interface. I am able to get the Blue Velvet to work correctly on the iPad and route midi from my foot pedal (which is connected directly to the Mac) thru Ableton and into Midi fire, through the Blue Velvet module, and back into Ableton.
It works perfectly fine when I set output the midi from the iPad to the Mac via wifi midi network, but it seems to cause a feedback loop when routed back through the iConnectivity or bluetooth. I want to route it back through the iConnectivity because that is simplest, fastest, and most reliable, but whenever I hit the pedal once both of the input source and output destination keep flashing yellow until I delete the output. The same thing happens when i set the output destination in midifire to the mac via bluetooth, but does not happen when i set the output destination in midifire to the mac via network session. How can I make it so that it sends it back via the Connectivity 4+ without repeating itself in an infinite feedback loop?
Also, would it be much easier to do this if I used the midi fire Mac app instead of the iPad midi fire app? If so, how?
And now here are two other questions about other capabilities of the blue velvet script:
1. Is there any way to easily change the midi channel or midi notes sent out by the blue velvet script? If so, how? I looked into the settings cog for it and don’t see any simple variables to change.
2. Would it be possible to use the blue velvet script for timing critical/sensitive functions, like starting/stopping an unquantized loop in ableton? I would like to use the blue velvet functionality to expand on the power of the multi-function button of the Ableton Looper Device (or re-create a multi-function button that has more functionalities), but I’m not sure if the blue velvet script would introduce too much latency, and (because its not quantized) timing is essential for this purpose. Would there be any latency introduced from either:
a) the time spent for the midi signals to route through midi fire?
b) the delay that i understand is built into the blue velvet script (to allow it to distinguish a single tap from a double tap, and etc)?
If so, how much latency would there be?
|
|
nic
Soapbox Supremo  
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Mar 14, 2019 8:59:24 GMT
Hi danklim , > How can I make it so that it sends it back via the Connectivity 4+ without repeating itself in an infinite feedback loop?Something on the mac is reflecting the events back. Given that this doesn't happen with wifi, I'd make a guess that it is Ableton. Maybe it has some sort of 'thru mode' for the track that you need to switch off. An alternative would be to place a Stream Byter on the canvas after the iConnect input blocking all notes on channels > 1 to throw away the Blue Velvet generated events. The rule for this would be: N1-F = XX +B> would it be much easier to do this if I used the midi fire Mac app instead of the iPad midi fire app?Yes, you could run the mac version only and not have to route events through the iPad. I would say this will be easier. The routing in MidiFire mac would be something like: KMI -> Blue Velvet -> MidiFire and you would configure Ableton to use the 'MidiFire' port. There would be no infinite loop issue in that case. > 1. Is there any way to easily change the midi channel or midi notes sent out by the blue velvet script? If so, how? I looked into the settings cog for it and don’t see any simple variables to change.My advice is to treat Blue Velvet as a black box, and although it would be possible to modify it, it is better to remap the Blue Velvet events to something else using a Stream Byter on its output to change the channel or notes. > 2. Would it be possible to use the blue velvet script for timing critical/sensitive functions, > a) the time spent for the midi signals to route through midi fire? Routing events through MidiFire is lightning fast. Latency is going to be bottlenecked by the signal path to/from iPad. If you switch to the mac version, then the latency will be reduced to virtually undetectable as virtual CoreMIDI routing is done internally. > b) the delay that i understand is built into the blue velvet script (to allow it to distinguish a single tap from a double tap, and etc)?Yes, you cannot escape this - You *can* change the delays in the Blue Velvet script (so much for black box). The two delays are near the top and marked in the code. Regards, Nic.
|
|
|
Post by novelty on Mar 15, 2023 8:37:40 GMT
Is it possible to get a version of the BlueBoard code that works in StreamByter, instead of MidiFire?
|
|
|
Post by novelty on Mar 15, 2023 8:39:24 GMT
Is it possible to get a copy of this BlueBoard code that works in StreamByter instead of MidiFire?
|
|
|
Post by redheronmusic on Mar 17, 2023 12:33:52 GMT
Is it possible to get a copy of this BlueBoard code that works in StreamByter instead of MidiFire? AFAIK, MIDI Fire has the same StreamByter code as the stand alone version, so if it works in one, it should work in the other.
|
|