- Joined
- Aug 29, 2018
- Messages
- 13
- Karma
- 0
- Gear owned
- mx2424 analog, adat, aes
There are other ways to do this if you're on a windows computer or a mac pro w/ PCIE cards. But if you're on a laptop or some other Mac that only has thunderbolt and USB and just want the simplicity of not transferring files at all, this is one way. It's pretty much this vs. an adat interface for us folks.
I cannot personally verify that this works, though you could verify w/ the manufacturer (Lynx)... It may not be cost effective depending on how many channels you need, where you live, etc.
1) Have an AES card in the Mx2424, of course.
2) Get a PCIE -> thunderbolt chassis. (sonnet or OWC .. make sure you get one with enough slots for the # of channels you need and make sure it fits the correct sized card(s)).
3) Get a Lynx AES16e (or two... or a similar card if someone else does these)
4) install whatever drivers from Lynx (or similar) . Make sure the company who makes the AES card supports using it over thunderbolt.
https://www.lynxstudio.com/downloads/aes16e
NOTE - the lynx may require using their specific 25 -> 26 pin cables, but you'll also have to either buy an adapter from Redco (to get between the yamaha/tascam pinout) or re-solder the head, or order a custom cable to start with from redco or pro audio LA.
WHY would anyone want to do this instead of using toslink/adat? Perhaps you prefer AES over toslink. I'll be soon testing these two against each other (subjectively and with some null test type stuff), by sending the AES to a Lynx Aurora (borrowed). Might be subjective/superstition about the jitters, might not. Perhaps the wordclock cable keeps it clean.
That has not been my experience so far when trying to send spdif over toslink to my DA at least. It's smeared and narrow compared to sending it from an AES jack. And every cable has sounded different. But, different application sort of so who knows.
As I said, it's subjective but perhaps this is a useful idea to someone. If I'm missing some crucial point, let me know. If that silly MOTU 2408 used actual firewire instead of their proprietary cable, that would be an option too, but I get why since Firewire often isn't the most stable connection (disturbed by bus priority on the computer etc).
I cannot personally verify that this works, though you could verify w/ the manufacturer (Lynx)... It may not be cost effective depending on how many channels you need, where you live, etc.
1) Have an AES card in the Mx2424, of course.
2) Get a PCIE -> thunderbolt chassis. (sonnet or OWC .. make sure you get one with enough slots for the # of channels you need and make sure it fits the correct sized card(s)).
3) Get a Lynx AES16e (or two... or a similar card if someone else does these)
4) install whatever drivers from Lynx (or similar) . Make sure the company who makes the AES card supports using it over thunderbolt.
https://www.lynxstudio.com/downloads/aes16e
NOTE - the lynx may require using their specific 25 -> 26 pin cables, but you'll also have to either buy an adapter from Redco (to get between the yamaha/tascam pinout) or re-solder the head, or order a custom cable to start with from redco or pro audio LA.
WHY would anyone want to do this instead of using toslink/adat? Perhaps you prefer AES over toslink. I'll be soon testing these two against each other (subjectively and with some null test type stuff), by sending the AES to a Lynx Aurora (borrowed). Might be subjective/superstition about the jitters, might not. Perhaps the wordclock cable keeps it clean.
That has not been my experience so far when trying to send spdif over toslink to my DA at least. It's smeared and narrow compared to sending it from an AES jack. And every cable has sounded different. But, different application sort of so who knows.
As I said, it's subjective but perhaps this is a useful idea to someone. If I'm missing some crucial point, let me know. If that silly MOTU 2408 used actual firewire instead of their proprietary cable, that would be an option too, but I get why since Firewire often isn't the most stable connection (disturbed by bus priority on the computer etc).