Topic: OctaMic II > Lynx AES16 > SONAR...hook-up/signal problem
hello...
I'm attempting to record 8 digital channels into my PC's DAW (SONAR) using my RME OctaMic II...& my Lynx Aurora 8 / AES 16...
[The Aurora 8 is connected to Port A of the AES 16...handling 8 analog inputs (from various preamps) & the analog outs, for monitoring]...& the OctaMic II is connected to Port B of the AES 16...digitally (AES)...for my 8 digital recording channels. Since the RME sports a TASCAM PinOut...& the AES 16 supports a Yamaha PinOut...on the back of the RME (at the 25 D-Sub) I've connected 25-Pin AVLA TASCAM to Yamaha adapter.
What I have in SONAR is an errant stereo signal (where I don't want it...only getting stereo input activity on 7 & 8...for some odd reason)...& no mono signal where I do want it...(Track 1 = Lynx ASIO Left 5, Track 2 = Lynx ASIO Right 5, etc., etc.)
Lynx thinks it's a cabling problem...as do I...& AVLA mfg.'s two different adapters in this case...an FCTY-AES & an FCYT-AES. [I have the former...perhaps I need the later...???]
So...Questions:
1) anybody familiar w/ a hook-up similar to this...(& able to offer advice or solution)...???
2) using the OctaMic's AES output...(whereby I'm utilizing the converters in the unit & outputting digital to an AES type PCI Interface...the AES 16)...where should my Mode Pins be set (for the 6 positions)...???
3) Do I need Word Clock...???
thanks,
MoonMix
ADK Pro Audio Core 2 | Intel DP35DP MoBo/Chipset | Intel Q6600 Quad Core CPU | 4 GB SuperTalent DDR2-800 CL5 RAM | Seagate 160 GB SATA II Primary HD | Western Digital 320 GB SATA II Audio HD | Lynx Aurora8 ~ AES16 | RME OctaMic II | Universal Audio UAD-1 | SONAR PE 7.0.2 | Cubase LE | WaveLab 5.0.1b | NI Komplete5
UPDATE:
not-so-good news on the adapter front:
on the the FCTY-AES...the adapter I'm using...the TY stands for TASCAM > Yamaha...whereby the TASCAM side is Male & the Yamaha side is Female.
this means that I'm using the correct adapter (TASCAM being on the RME side & Yamaha being on the Lynx side).
this also means the problem's origins lie somewhere else...somewhere in my RME's output settings.
man o man, oy vey,
MM