Dr Bob
06-18-2008, 04:33 AM
Hi, a message to those who have programmed a csurf ...
Okay, I am an OK programmer ... what are the best tools, compiler-wise to use please?
What I would like to do is write a "virtual" control surface. The idea is that two computers can be linked back to back with this to enable collaboration. Basically one is the master with all the audio tracks, the other(s) will be streamed the tracks, and the linked "csurfs" allow mixing.
In the first instance I would simply transmit and receive transport controls and basic track manipulation ... ie MUTE, SOLO, FADER, PAN.
It would be nice to also send the time position, so the remote could start the master at any timecode.
My initial experiments with existing csurfs show this will work OK. However, SOLO is a wee problem, as to make it work and stream the midi between systems, a pair of tracks are set up to send and receive. SOLO an audio track will kill this! So, somehow, these "control info" tracks need to be immune in some way to the normal SOLO/MUTE actions ... or better still, a new way to send/receive the csurf midi stream to a remote system.
Hopefully someone (Justin???), can say that it would be possible for this csurf .dll to tap directly into the streaming code, and in it's setup then all you do is give the network address of the systems which are "interacting".
Any bright ideas people???
Cheers,
db
Okay, I am an OK programmer ... what are the best tools, compiler-wise to use please?
What I would like to do is write a "virtual" control surface. The idea is that two computers can be linked back to back with this to enable collaboration. Basically one is the master with all the audio tracks, the other(s) will be streamed the tracks, and the linked "csurfs" allow mixing.
In the first instance I would simply transmit and receive transport controls and basic track manipulation ... ie MUTE, SOLO, FADER, PAN.
It would be nice to also send the time position, so the remote could start the master at any timecode.
My initial experiments with existing csurfs show this will work OK. However, SOLO is a wee problem, as to make it work and stream the midi between systems, a pair of tracks are set up to send and receive. SOLO an audio track will kill this! So, somehow, these "control info" tracks need to be immune in some way to the normal SOLO/MUTE actions ... or better still, a new way to send/receive the csurf midi stream to a remote system.
Hopefully someone (Justin???), can say that it would be possible for this csurf .dll to tap directly into the streaming code, and in it's setup then all you do is give the network address of the systems which are "interacting".
Any bright ideas people???
Cheers,
db