3 Dec
2008
3 Dec
'08
8:03 a.m.
On Sun, 30 Nov 2008 08:13:38 +0100
torbenh(a)gmx.de wrote:
On Wed, Nov 26, 2008 at 10:29:15AM +0100, Mysth-R
wrote:
But is the lossy codec (celt) a good idea for a LAN?
Hi,
Yesterday I tried with a friend of mine to synchronize our
computers with a simple midi cable.
We just want to make music together, and synchronize, the transport
AND the tempo with a Master and a Slave.
After hours and hours of tests, we just made the transport sync
works. But we couldn't sync the tempo.
Someone told me on the #LAD IRC, about netjack, but it seems to be
to "loud" for what we want to do.
can you explain loud ?
In fact, most of the softs can sync themself each other with JACK
transport, but can't send Midi Time Code to the midi out.
so why not use netjack ?
grab current jack release and go.
it now works over wireless. use celt codec to
reduce bitrate. should give you 4channels in both directions easiely.
and i guess you only want 8 channels in one direction.
And when we even they can send Midi Time Code, it
can't be sync
with jack transport on the other computer.
The top would be to find a soft which can act as a bridge between
Midi Time Code and Jack Transport. like for exemple :
First Computer : Seq24 -> Midi Time Code send to Midi out of the
Sound card. Second computer : -> Midi Time Code received in the
Midi In -> bridge on JackTransport -> and then each softs could be
sync.
The other solution :
First Computer : Seq24 -> JACK Transport -> BRIDGEto Midi Time Code
send to Midi out of the Sound card.
Second computer : -> Midi Time Code received in the Midi In ->
BRIDGE to JACKTransport -> and then each softs could be sync.
Is someone knows a simple solution ?
I am a bit disapointed
netjack.
its even sample accurate.