Chadwick
03-28-2002, 04:09 AM
Hey guys,
I just found a post at the Yahoo Giga forum which pointed out a new product from a Russian company which has been doing midi plugins for Sonar and Cubase. They\'re called MusicLab and they\'re home page is here:
http://www.musiclab.com/ (\"http://www.musiclab.com/\")
They have a programme called the MIDI Replicator Driver.
Sounds like they started out designing it to get around the Windows \'Sorry that midi device is in use\' problem by applying a multiclient approach to windows midi devices, but then they expanded it to include sending midi over TCP/IP networks.
The programme appears to allow up to 8 midi ports to operate over your network simultaneously.
Thats 8x16 = 128 midi channels
I know there have been a few \'midi over net\' type programmes, but they\'ve been limited in features.
I\'m also wondering what the jitter would be on a network based midi transmission setup. Would it be worse than sending things across two good hardware midi interfaces, like my Unitor IIs?
Is there a problem with time stamping midi packets over a network??
Any chance of Tascam R&D taking a look at how effective this programme is compared to using a couple of good quality hardware midi interfaces? There\'s no point in using it if it makes latency sloppy.
If it works well, it could be an inexpensive solution.
I\'ve seen a lot of people complain about the cost of adding GSIF audio cards and Multiport hardware midi interfaces in order to run Giga on a separate PC.
Maybe this could solve one of those quibbles.
I just found a post at the Yahoo Giga forum which pointed out a new product from a Russian company which has been doing midi plugins for Sonar and Cubase. They\'re called MusicLab and they\'re home page is here:
http://www.musiclab.com/ (\"http://www.musiclab.com/\")
They have a programme called the MIDI Replicator Driver.
Sounds like they started out designing it to get around the Windows \'Sorry that midi device is in use\' problem by applying a multiclient approach to windows midi devices, but then they expanded it to include sending midi over TCP/IP networks.
The programme appears to allow up to 8 midi ports to operate over your network simultaneously.
Thats 8x16 = 128 midi channels
I know there have been a few \'midi over net\' type programmes, but they\'ve been limited in features.
I\'m also wondering what the jitter would be on a network based midi transmission setup. Would it be worse than sending things across two good hardware midi interfaces, like my Unitor IIs?
Is there a problem with time stamping midi packets over a network??
Any chance of Tascam R&D taking a look at how effective this programme is compared to using a couple of good quality hardware midi interfaces? There\'s no point in using it if it makes latency sloppy.
If it works well, it could be an inexpensive solution.
I\'ve seen a lot of people complain about the cost of adding GSIF audio cards and Multiport hardware midi interfaces in order to run Giga on a separate PC.
Maybe this could solve one of those quibbles.