HD Omni and ADAT Lightpipe

[jeremyseanbell]

I just tried using a lightpipe to connect a Focusrite Octopre to an HD Omni, but for some reason only two extra inputs showed up. What gives? Does the lightpipe really only add another two inputs or was I doing something wrong? I was running at 48kHz.

[Darryl Ramm]

Originally Posted by jeremyseanbell

I just tried using a lightpipe to connect a Focusrite Octopre to an HD Omni, but for some reason only two extra inputs showed up. What gives? Does the lightpipe really only add another two inputs or was I doing something wrong? I was running at 48kHz.

The Omni does a *total* of 8 inputs. Widely discussed on DUC in the past and explained in the user guide.

[Matt Hepworth]

Sounds like you have optical set to S/PDIF instead of ADAT.

True about 8 combined inputs, though.

[jeremyseanbell]

Yes, I understand it does a total of 8. I'm saying the ADAT lightpipe only added two inputs, so there was a total of 6.

[nst7]

As mentioned, it sounds like it's set to Spidf, rather than Adat.

[YYR123]

You should be able to set that up in the

Hardware Setup section in Pro Tools.

Just surf thru those tabs and you should find what you need to change the inputs to Adat optical

[djjazzy41]

Not trying to hijack the thread here, but I have a relevant issue with my Omni. I record all my sessions at 88.2, hence the need for both ADAT inputs on the back of my Omni and the SMUX protocol. Currently I am running out of an Audient ASP880 via two ADAT cables so that all 8 channels can be transmitted at the 88.2 sample rate. Both the Audient and the Omni say they can do this by using both outputs on the ASP880 and both ADAT inputs on the Omni. Clock is locked, I/O in ProTools is set up so that all 8 inputs on the Omni are ADAT, but I can only get the first 4 to receive signal through the Omni. For some reason, when I try to use the last 4 channels from the ASP880, there is no sound or signal present in ProTools. The I/O is set up correctly in PT in both setup and on the PT mixer, but no sound is passing through. I have signal in the last 4 channels of the ASP880, and signal out of the ASP880 (light pipe is red and kicking), but it is not getting in the second ADAT input of my Omni. What am I missing? It has to be something easy I am missing. Any help in identifying my mistake would be greatly appreciated!

[Darryl Ramm]

Originally Posted by nst7

As mentioned, it sounds like it's set to Spidf, rather than Adat.

Exactly.

[YYR123]

Originally Posted by djjazzy41

Not trying to hijack the thread here, but....

...but you did

Originally Posted by djjazzy41

For some reason, when I try to use the last 4 channels from the ASP880, there is no sound or signal present in ProTools.

First I would, swap the Adat into the Omni. Not out of the 880 but only the connections at the back of the Omni.

This will point to which system has the issue. If it's the Omni you should see the inputs 4-8 (880) making movements on the meters in the session (still showing inputs 1-4 in the session and on the Omni)

[djjazzy41]

Originally Posted by YYR123

...but you did




First I would, swap the Adat into the Omni. Not out of the 880 but only the connections at the back of the Omni.

This will point to which system has the issue. If it's the Omni you should see the inputs 4-8 (880) making movements on the meters in the session (still showing inputs 1-4 in the session and on the Omni)

Swapped the cables on the back of the Omni as you suggested, and I still have signal into the first 4 inputs of the Omni, although they are now coming from output 7-8 of the ASP880 as should be the case. No issue with the 880 or cables. Regarding the Setting of ADAT vs. SPDIF, in my Hardware setup menu, there is no way to select either of them on the Main tab Input section of the Omni Hardware Setup page. I only have that option on the output section, and it is set to ADAT/SMUX. On the input side, I can only select Digital 1-2 Format, and my only options are AES/EBU, S/PDIF, or Optical (S/PDIF). Since I am not having a problem with input 1-2, I didn't think this could be part of the issue.