Vienna Symphonic Library Forum
Forum Statistics

201,375 users have contributed to 43,245 threads and 259,258 posts.

In the past 24 hours, we have 6 new thread(s), 17 new post(s) and 57 new user(s).

  • Sorry, my first message was meant as a joke - I certainly didn't try to sound snotty.

    Regarding your question: No, we won't use a "classical" audio-connection between MIR-host and VI-slaves, although it is clear that you will need audio-outputs on the MIR in almost all imaginable setups. The system we have now is a proprietary driver-stucture for FireWire-connections, theoretically enabling us to bring in up to 64 stereo-channels into the MIR-machine from up to 64 slave-machines. - But for some guys within the VSL this is not enough, so maybe we will see yet another solution for the final product.

    I hope this is cleartext ;-) ... thanks for your interest, Fritz.

    /Dietz - Vienna Symphonic Library
  • Ok! Thats great to know. Thanks for the information Dietz. PC only would mean, that also the VI slave can be PC only in order to work with mir? in other words: will you be able to connect a mac with these firewire connections to a PC running mir? - Thanks!

  • last edited
    last edited

    @Another User said:

    [...] will you be able to connect a mac with these firewire connections to a PC running mir?
    This is how it's meant to work - as long as our developers can keep up with the unexpected changes in Apples's OS-X.

    /Dietz - Vienna Symphonic Library
  • ... though currently it seems the firewire chip manufacturers are troubling us more than any OS issue does ....

    too bad such a great protocol (responsibly developed by apple btw and invented for streaming) gets screwed up by a handful profiteers ...

    christian


    and remember: only a CRAY can run an endless loop in just three seconds.
  • I'm curious, why not use an Ethernet protocol instead? FW busses in most computers are already pre-ocupied with other tasks, and I wonder how stable such an solution would really be? 


  • some things to consider:

    ethernet has been invented for reliably receiving data, firewire for realtime streaming, ethernet needs configured identity of hosts (IPs), firewire is autoconfiguring (deviceIDs), ethernet puts a tic more load on the processor than firewire, ethernet packages can collide (get dropped and resent), firewire works basically *timesliced*

    128 tracks 44.1/24 need 16 MB/s which is below the limit of both connection types and it depends on the circumstances beyond which load dropouts will occure.

    last but not least: ethernet support or resolving connection problems can be tricky, firewire works or not.

     

    on the other hand: if the issues with firewire continue as they came up lately maybe we should drop it ....

    christian


    and remember: only a CRAY can run an endless loop in just three seconds.