It is a similar concept to the video from 2013 I posted above, but it is easier in 2016 because there appear to be prebuilt Reaktir objects that simplify the process. This will enable me to route around the Ableton limitation, giving me two independent sources of midi (both ultimately sourced from the same Blocs ensemble) for sending o my external synths. It will involve sending data from one instance of Reaktor to another instance of Reaktor (the second instance on a different Ableton channel) and sending midi from that second instance to my external device. Means I can't have my beautiful all in one Blocks ensemble doing the work.Īny other thoughts, especially on a M4L fix for this, are very welcome!įor now I am working on a solution using OSC (open sound control). ![]() Run multiple Reaktor ensembles inside Ableton. Use CV data instead of midi, which means buying a DC coupled audio interface, a good solution, but expensive.ħ. ![]() Wait for Ableton to fix this (not likely - it has been a recognised issue for many years).Ħ. Move to a different DAW (not a good option because I have a Push 2 and like Ableton).ĥ. ![]() Finding a M4L device that addresses this issue ( obviously this is the best option, but I haven't found anything yet).Ĥ. The workaround in the youtube video above using OSC in Reaktor and porting, external to Ableton, inside the Mac.ģ. Running Reaktor standalone, and feed the audio into Ableton (not sue if this is possible, and may have midi synch issues with Albleton when running other devices inside Ableton).Ģ. This is unfortunate because my dream of building beautiful single-ensemble generative midi sequencers with Reaktor Blocks for my external gear won't come true.ġ. the inability to separately route midi channel data from a VST into multiple Ableton midi tracks, for sending to different external devices or soft synths). I have done further research on this, and found out that this is a well recognised missing feature in Ableton (i.e. one synth per Reaktor midi block, but I can't for the life of me figure it out. There must be a way to achieve what I want to do - i.e. bypassing ABleton, but still running Reaktor as a VST), but can't find a way to do this, I think Ableton takes over the midi side of the Focusrtie. I tried triggering the synths directly from reaktor (i.e. This means I can't have each of my synths triggered by a different Reaktor midi block. REaktor instrument properties "connect" panel is set to External = "All," midi channel = 1 and 2 (respectively for each midi out block) channel 1 and 2), what feeds through to Ableton is one single stream of midi. This means, despite the midi blocks inside reaktor being set to the correct midi channels (i.e. I only seem to be able to select Reaktor as a whole, not midi channels within Reaktor. The problem is, I can't seem to configure Ableton so that each ableton midi channel recieved the midi from A DIFFERENT REAKTOR BLOCK. I am routing the midi from reaktor through Ableton by sselecting midi from: reaktor/reaktor on the Ableton midi tracks. The other only recieved on midi channel 2. ![]() One synth receives only on midi channel 1. I am using midi USB for one synth, and a midi cable for the other. The midi chain is Reaktor 6 (as VST) -> two midi tracks in Live 9.6 -> Forcusrite scarlett 6i6 -> synths. I want to trigger two external synths, via two separate midi out blocks,within the same ensemble. I am wondering if anyone can help with an issue I am having. I bought Reaktor 6 two nights ago and am LOVING it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |