![]() Most DAWS have settings like "Monitor Midi on Rec-armed channel" Sounds like you've found an incompatibility here. Plogue Bidule - I have used Plogues stuff, and they work as advertised. There is one thing to consider in such a setup: Make sure you don't create a MIDI "Feedback Loop" which happens if both Reason and Logic mirror MIDI input to MIDI output. So the only reason it is not possible is because Avid doesnt want you to do it. Make sure the Logic Track sends its Midi data to IAC, exactly like you said, and Reason has its MIDI input set to IAC. You can use the IAC driver to route MIDI from Logic to Reason too. My problem was that the rewire wasn't working so the Bidule Rewire module wasn't there to choose. Create your VI instance, connect the midi and the audio in Bidule and you should be good to go. If all is good, it could be some level control in Logic, or different audio formats being converted without level scaling maybe? Under Midi Devices, grab Bidule 1 and drag this to the screen. I would run any wave editor and record some audio from Jack, just to make sure the level is not modified by Jack itself. bidule does not show up when I choose inputs for an audio track. The master fader in Reason controls the audio level into Jack, then Jack itself might do something, and in Logic Pro X you have again multiple points of gain control. Remember that in your setup, you have many points of level control. Thanks for your feedback, I'm happy I could help you! I use a similar setup (Live and Reason) with the Reason Demo for the time being, until I have decided to shell out the $400 for Reason 8 which is still far too much compared with Ableton Live or even Logic Pro X.Īs "thor" is still my main reason for Reason, I can always use my iPad+thor integrated in Live for a much more acceptable price This virtual IAC Midi Interface will be visible in both Logic and Reason, so choose it as Midi Sync output in Logic and as Midi Sync input in Reason. Then select Window -> Show Midi Window and doubleclick on IAC Driver. MacOSX Applications -> Utilities -> Audio Midi Setup, If you're fine with Logic and Reason playing simultaneously, you can skip it and create a virtual MIDI port using Note that you need JackOSX only to record Reason's output in Logic. Reason -> Preferences -> Sync -> Input and > Midi Clock -> Allow to send Song Position Pointer while playingĪre you sure Reason is set to slave-sync to Midi Clock? You only need Midi Clock and Midi Status messages like Start, Stop and Continue, and ideally MIDI Song Position Pointer, so the arranger locator will move to the same position as in Logic.Įnable sending of SPP messages in the page too: You don't need to enable MTC neither MMC btw. You can load up a looped click track (or enable the metronomes) in both Logic and Reason and move the slider until both play in perfect sync. The "Delay Transmission" slider allows for fine-tuning the sync between Logic and Reason. Here, change the check mark to active and in the drop-down box below, select JackOSX (or whatever MIDI router you use) as MIDI destination. Originally appearing in the ReBirth software synthesizer in 1998, the protocol has since evolved into an industry standard. Logic Pro X -> Preferences -> Midi -> -> -> Transmit Midi Clock Apparently they are assigned in the order they are added and I'm unaware of a way to manually choose what device goes on what ReWire bus.Of course you have to enable Midi Sync in Logic: It's a bit of an issue because it looks like I can only get 2 ReWire busses which each provide access to 16 Reason devices. Reason doesn't seem to respect the settings I provide in Plogue and always launches with 2 MIDI inputs and 64 audio outputs + main mix L/R. I'm trying to increase the number of MIDI inputs available when using Reason as a ReWire slave inside of Bidule (Plogue).
0 Comments
Leave a Reply. |