By now, I feel fairly confident in saying that a 2 deck system going to front of house is the most basic form of live performance one can achieve. Whether this is handled well by FOH staff is another question entirely, but it got me thinking how to truly perform live...not across one machine, but across multiple machines, MAYBE even multiple machines running different DAWs. This would harness the computational power of more than one device, and enable you to play out entire project files live without too many problems (theoretically).
In the past, musicians had to rely on more primitive technology, and I remember an early FutureMusic mau5 interview in which sample accuracy and minimal latency were clearly a problem. (
https://www.youtube.com/watch?feature=player_detailpage&v=GTCqeWu094I&t=728)
"
There is too much jitter, MidiTimeCode seems to be stable somehow. Except, Live cannot send MTC (but receive), so you have to run a program or an external device, that provides MTC. Only, but minor, problem is, MTC doesn't not include tempo information, so you have to setup the tempo on the different machines and then start. That is also possible in between, e.g. you change the tempo in the course of a song, we tested it and happened to be successful."
To have the data be super tight and sample accurate across multiple devices would require a hardware solution, which got me curious as to how to solve this problem in my own DAW without going and purchasing an AVID Sync I/O (or similar) that would be reliant on SMPTE streams.
Being an Ableton user, this got me thinking that there's a M4L device that seriously needs to be made. Simply put, a plug-in that converts SMPTE to MTC (which is more sample accurate) out in Live. Live only takes MTC in, and if you want to send MTC out, you need to Rewire and slave with another DAW. I think it would be something cool, and something super useful for people so they don't have to a) rely on midi clock and b) worry that their devices arent SMPTE compatible.
That being said, in a hardware solution, SMPTE gets converted into MTC when it goes down a MIDI cable. The aforementiond M4L device would keep everything in house and reduce costs for everyone wanting to communicate with another DAW, external device, etc. (via Ethernet or otherwise).
Upon further consideration, to do it as software would require a plug to read and write the actual linear time code from a hardware emulation, so unless your coding is pristine you will have latency issues. At this point, I was lost, so I consulted Steve Duda for answers. Here is what he had to say:
http://imgur.com/a/LvNuCLong story short - we knew SMPTE wasn't sample accurate (still, MTC > SMPTE) , and without resorting to an ITB solution, you can branch out either to external hardware solutions, or use ReWire (or a similar API).
Any additional thoughts are much appreciated!
Show Posts
