wifi midisync w. Macs Audio Midi Setup

Originally posted by : liquidbass

In the Mac-Utilities there's a tool called "Audio Midi Setup" with a network function that allows you to send midi signal through a classical Ethernet- oder a Wifi-Network. I tried this to synchronize the midiclock of Reason 4 running on two Macs The network connection appears in the Reason preferences as midi input... but theres no control at all. Anyone an idea about what I am doing wrong? Anyone a suggestion about how to make this work?

i can be wrong, but i think i heard that the lan-sync is only supported in logic..

I got my macbook only few days ago... so I am still a lil bit helpless...

would be sad

is reason configured correctly to 1) send out midi sync 2) receive midi sync? 

http://www.studiotoolz.net/wii-loop-machine

yep

MIDI via LAN an Scene syncing Another great feature that came with OS 10.4 (le Tigre) was the possibility of transmitting MIDI signals via LAN. Yes, that includes via wireless also.I was able successfully to actually MIDI-jam (with two machines using my G4 Powerbook and another MacBook Pro), with syncing Ableton Live sequencer existent on both machines. And no “strings” attached! latency was minimal so the two machines tapped happily on the same tempo…This all was done via my friend’s wireless network. Insane, huh? This is how you do it: The Core MIDI (only in Tiger) has a Network connection (found in the Audio MIDI Setup settings). With this cool new added feature you can actually sync two (or more!)sequencers on different machines or even use software instruments that are sitting on remote machines, easing the strain on your main machines that’s already bogged down with enough proccessing to do with your host sequencer. Setting up the MIDI network Session: Bring up the Audio MIDI Setting screen (from your Utilities folder), and you will ?nd the cool new feature called “Network” from where you will now set up a MIDI via LAN connection session. MIDI Network’sfunctionalityuses theconcept of having a session(s), where other machines (connected to the same LAN network) can take part in a certain session to send and receive MIDI data. You can actually create multiple sessionsand theneach of them willfeature a single pair of MIDI input and output ports on your system. Create A Session:

1. Add a new session with the”+” button in the My Sessionssection. There are certain settings you can con?gure for this newly created session such as re-naming your current session name on the Local name ?eld. Also this name willshow up in your Ableton Live’s MIDI/Sync Preferences ports list.The Bonjour name for the currentsession, defaultly your machine’s name, is used to broadcastthe current session’spresence on the network. The Directory shows all available sessions on the network by their Bonjour names as well. Does this look like a network game setting yet?
2. Considering that another machine has already set up a network session, and it shows up in the Directory list, you will now be able to see that remote machine’s name listed in the Participants list.
3. Bingo! You have a happy working MIDI via LAN connection (be that wireless or not). MIDI In/MIDI Out: Now, it is time to set your Ableton Live to transmit (MIDI send/receive) on thisMIDI session you’ve just created.Practically in our two-Macs session, we had a Master and a Slave machine. The Master was used to sort of “direct” the fun (sending clock, tempo changes, scene changes, etc.) and the Slave did all sorts of cool on-the-?y looping. From Ableton’s Prefs (Apple+,), choose MIDI/Sync pane and there you will ?nd your current MIDI Network session you just set up in the MIDI Port List. From there is simple. On the Master machine Output Network MIDI session’s port turn the Track/Sync/Remote on: And on the Slave machine turn the Input Network MIDI session’s port turn the Track/Sync/Remote on: The theory here is that the Master sends and the Slave(s) receive. Now, go tell Ableton Live that will be your slave, to “align” or listen to the external clock coming from the Master machine. See that “EXT” button in Live next to the Metronome? That’s the External Sync Switch. Click it! Bingo! Now your Slave Live will wait patiently for the Master’s signal to start the fun! The Joy of Latency: The MIDI Network Setup screen has a nifty little Latency display showing the amount of latency in little red strikes. The way we checked for latency was “by ear”, turning both Ableton’s metronome on and playing with the Latency adj. (by double clicking the value in the Participants list) miliseconds offset until both clicks were synced. ForwardingScene Changesto SlaveLive: There was however a hurtle I had to overcome and that was the fact that Live didn’t pass along mapped MIDI notes I have mapped from my MIDI pedal to trigger scene changes. After a couple email changes with the kind folks at Ableton, one guy there gave me a very practical way of solving this and I am going to quote him (Daniel): “Your Master Mac is receiving notes from your MIDI controller to trigger speci?c scenes. On your Master computer, you create one extra MIDI track where you have a MIDI clip in each scene. Those MIDI clips contain exactly the same note you are using to trigger the scene on the Master computer. This MIDI track sends MIDI to a virtual MIDI network port that you need to create in the OS X Audio MIDI Setup (you could use the same MIDI port that you use for sending the MIDI clock). The Slave computer will receive the note from the virtual MIDI port. In the Live Preferences on the Slave machine, you need to enable “Remote” on this virtual MIDI port. Then you still have to MIDI Map the scenes on the slave machine to get triggered from the MIDI note that is being sent from the “dummy” MIDI track on the Master computer. Each time you trigger a scene on the Master computer, it should immediately trigger the MIDI clip in that scene sending a trigger to the slave computer triggering the scene there.” As an addition, I also disabled the “Loop” button on the Trigger MIDI track clips on the Master machine. I assumed the trigger note was needed only once to trigger the scene on the Slave machine. Small Trouble: For some mysterious reason, the clips on the scenes on the Slave machine started playing always one measure later. When I trigger the scenes on the Master machine, you can see the clip on the Slave with its light ?ashing and then starts playing but only at the next measure, instead of immediately. Small Fix: You will have to turn the global Quantization on the Slave machine off. We need no quantisation here since we have it set on the Master machine already. Also, depending on the MIDI delay between both machines, it might also help to set a negative track delay on the MIDI track sending the trigger note (on the Master machine). Of course all the above is possible to be set with rudimentary MIDI cable setup, which makes more sense if you are a travelling musician and there is no wireless network to rely on at your concert venue. Ant to be honest, why would one rely on somebody else’s wireless network when going to a concert?

Originally posted by : liquidbass

Small Trouble: For some mysterious reason, the clips on the scenes on the Slave machine started playing always one measure later. When I trigger the scenes on the Master machine, you can see the clip on the Slave with its light ?ashing and then starts playing but only at the next measure, instead of immediately. Small Fix: You will have to turn the global Quantization on the Slave machine off. We need no quantisation here since we have it set on the Master machine already. Also, depending on the MIDI delay between both machines, it might also help to set a negative track delay on the MIDI track sending the trigger note (on the Master machine). Of course all the above is possible to be set with rudimentary MIDI cable setup, which makes more sense if you are a travelling musician and there is no wireless network to rely on at your concert venue. Ant to be honest, why would one rely on somebody else’s wireless network when going to a concert? 

thanks for the info!! it's very normal that the slave is always 1 measure behind: it recieves the scene-launch-command just milliseconds after the clock-pulse ; it is indeed solved by putting a negative delay on the dummy-track in the master. about the wireless network: you don't need otherones wireless network, just make it yourself: click on the wireless lan-logo, and click "create wireless network" on one of the 2 machines. then the other laptop will see that wireless-network, and be able to share data, like midi-signals. bare in mind that you plug in the power adaptor, because yer battery will die quickly ;)