smallbutfine
Well-known member
Hi guys,
finally some more interest in the interface discussion, nice!
For all people interested into adat, as said before there already is a solution available with Mikkels board.
So there is no obstacle for you if you want to keep your system like it is and add the hardware.
Up to 48khz. Awsome enough one could immediately start building without any fear there would be no interface available ;-) .
Next, AES definitely has it's advantage of the low jitter level that can be achieved.
Obviously preferable for tracking or mastering (low channel count, high quality). Seems no way around dedicated hardware computer interface (e.g. lynx) and, well, much cabeling.
IEEE1394 aka firewire is a nice thing IF it works (e.g. using a lightbridge is really cool once all is up and running and unbeatable in price/value).
Took me quite some time on some machines. Worked right o-o-b with others...issues with pc latform due to ms can be resolved (RME had some very useful instructions on their site. Complicated for developers really, limited cable length etc are drawbacks really.
If you already have a cool running high channel count system, well, a new interfacing method might not be for you. Nevertheless, the option to try an ethernet based one (computer interface cost = 0, hehe, liked that one) really cannot be wrong....
Short status report
from my work on this (WDM PC ethernet audio driver)...
Made a concept paper/todo list for myself to not loose the focus in all those sdk's, DDK's, WDK's...
During research and programming, I read on the dev forums 'bout a guy who already did it to stream audio from win to linux (closed source/commercial), similar model used by motorola to stream to BT headsets, etc, so I guess I am on the right trail now.
I found all the bits and pieces that are needed, but things have to be knitted together now.
Yes, driver development is absolutely no piece of cake, in no way.
I don't know much about the mac and vhdl hardware side of things but i assume things are worse in win driver world.
(learning curve is very steep. highly proprietary and abstract stuff even for people who do or did programming for a living)
Porting to mac might not be much easier than driving mac stuff from scratch.
ASIO: From experience I know asio4all is quite mature in the meantime, I used it once to integrate/'merge' 2 different cards (wdm drivers) and was able to use both at the same time under ONE asio driver. Cool stuff. Very usable under Win....
don't know about asio driver stuff on mac platform...
Unfortunately mac and vhdl hardware developers, excuse me if it sounds odd, may be a bit more on the commercially oriented side of things...(i.e. they know the cost of a man-hour.)
Raphael is right about the hardware side of things, i see no commitments so far reg. fpga development....definitely a show stopper.
Kind regards,
Martin
finally some more interest in the interface discussion, nice!
For all people interested into adat, as said before there already is a solution available with Mikkels board.
So there is no obstacle for you if you want to keep your system like it is and add the hardware.
Up to 48khz. Awsome enough one could immediately start building without any fear there would be no interface available ;-) .
Next, AES definitely has it's advantage of the low jitter level that can be achieved.
Obviously preferable for tracking or mastering (low channel count, high quality). Seems no way around dedicated hardware computer interface (e.g. lynx) and, well, much cabeling.
IEEE1394 aka firewire is a nice thing IF it works (e.g. using a lightbridge is really cool once all is up and running and unbeatable in price/value).
Took me quite some time on some machines. Worked right o-o-b with others...issues with pc latform due to ms can be resolved (RME had some very useful instructions on their site. Complicated for developers really, limited cable length etc are drawbacks really.
If you already have a cool running high channel count system, well, a new interfacing method might not be for you. Nevertheless, the option to try an ethernet based one (computer interface cost = 0, hehe, liked that one) really cannot be wrong....
Short status report
from my work on this (WDM PC ethernet audio driver)...
Made a concept paper/todo list for myself to not loose the focus in all those sdk's, DDK's, WDK's...
During research and programming, I read on the dev forums 'bout a guy who already did it to stream audio from win to linux (closed source/commercial), similar model used by motorola to stream to BT headsets, etc, so I guess I am on the right trail now.
I found all the bits and pieces that are needed, but things have to be knitted together now.
Yes, driver development is absolutely no piece of cake, in no way.
I don't know much about the mac and vhdl hardware side of things but i assume things are worse in win driver world.
(learning curve is very steep. highly proprietary and abstract stuff even for people who do or did programming for a living)
Porting to mac might not be much easier than driving mac stuff from scratch.
ASIO: From experience I know asio4all is quite mature in the meantime, I used it once to integrate/'merge' 2 different cards (wdm drivers) and was able to use both at the same time under ONE asio driver. Cool stuff. Very usable under Win....
don't know about asio driver stuff on mac platform...
Unfortunately mac and vhdl hardware developers, excuse me if it sounds odd, may be a bit more on the commercially oriented side of things...(i.e. they know the cost of a man-hour.)
Raphael is right about the hardware side of things, i see no commitments so far reg. fpga development....definitely a show stopper.
Kind regards,
Martin