Topic: setup problem with AES-32 interfacing to ADI-8-QS & ADI-192-DD

I have a problem with an AES-32 interfacing to an ADI-8-QS & ADI-192-DD:

want to setup all single wire @ 192 KHz:
RME AES-32 TDIF#1 (AES 1-4) (8out+8in channels @ 192 KHz single wire) to ADI-8-QS using a DB25/TDIF cable
RME AES-32 TDIF#2 (AES 5-8) (8out+8in channels @ 192 KHz single wire) to ADI-192-DD using a DB25/TDIF cable

sync is as follows (see pictures labeled 0):
Apogee Big Ben as master clock @ 192 KHz
RME ADI-8-QS (75-ohm TERM is ON) as slave synched to BB#1 output
RME ADI-192-DD (75-ohm TERM is ON) as slave synched to BB#2 output
RME AES-32 (no TERM switch ?) as slave synched to BB#3 output

questions:

1) Why the AES-32 has no sync TERM switch like the ADI-8-QS and the ADI-192-DD ? (you can see the Big Ben # 3 OUT shows no term at all -unlit LED) (see pictures labeled 1)

2) After booting the PC and powering all units I see the ADI-8-QS showing QS state ON, the AES-32 driver showing IO 1~4 and Word synched to 192 KHz as expected ... but the System Clock Freq shows 48 KHz (?) and MIDIremote shows 44.1 KHz & QS for the ADI-8-QS (?) Why is this so ? Musn't FREQ being showing 192 KHz for single-wire also ? Musn't MIDIremote being showing 192 KHz also ? In MIDIremote; what is the follow clock switch for ? It has no counterpart in the actual unit, does it ? (see pictures labeled 1)

3) Attempting to play some 2-channel file results in ADI-8-QS showing weird metering in all 8 channels (it should be displaying 2 only) (see pictures labeled 2)

4) When playback stops all ADI-8-QS meters freeze ... until something is played back again (see pictures labeled 3)

What am I doing wrong ?

ADI-8-QS worked perfectly when feeding it with a custom DB25/TDIF-to-single-SPDIF cable (tested it with a CD player while waiting for the AES-32 arrival)

lastest driver (3.0.5.8) and firmware (2.33) installed and DDS off



http://img444.imageshack.us/img444/7025/0setupid2.jpg

http://img182.imageshack.us/img182/6049/1statusafterbootek8.jpg

http://img183.imageshack.us/img183/7127/1statusafterbootas9.png

http://img138.imageshack.us/img138/6412/2startingplaybackgh2.jpg

http://img132.imageshack.us/img132/8997/2startingplaybackdh9.png

http://img91.imageshack.us/img91/5467/3stoppingplaylq9.jpg

2

Re: setup problem with AES-32 interfacing to ADI-8-QS & ADI-192-DD

Hello,

first of all please make sure that you are talking about Tascam digital cables, not TDIF. With TDIF cables your whole setup would not work.

Second you have to understand that you need to do a recording or playback at 192 kHz for everything to work correctly. So far you set up the hardware right, but used the computer only with 48 kHz.

Third the AES-32 has a 75 Ohm switch for the WC input. See manual. The Apogee measurement does not show TERM for most or our devices, don't worry.

Finally, follow clock is explained in the QS manual. It is also found on the unit itself within the menu.

Regards
Matthias Carstens
RME

Re: setup problem with AES-32 interfacing to ADI-8-QS & ADI-192-DD

Thanks for the reply !

? first of all please make sure that you are talking about Tascam digital cables, not TDIF. With TDIF cables your whole setup would not work.

yes, both digital cables are Zaolla ZAES-306T AES/EBU clearly labeled "wired for use with Tascam and compatible devices"
http://www.zaolla.com/zaolla_product_zaes_snakes.html

? Second you have to understand that you need to do a recording or playback at 192 kHz for everything to work correctly. So far you set up the hardware right, but used the computer only with 48 kHz.

huh ... of course, this is what happens when you're trying to fix something late at night, I apologize for attempting to play this file fryingpan I got it wrong while taking the snapshots, sure throwing some 44.1 KHz file in GraphEdit won't make it upsampled to 192 KHz as is the case on QuickTime. In QT you set the max allowed by your card and everything you throw at is upsampled if neccessary.

? Third the AES-32 has a 75 Ohm switch for the WC input. See manual. The Apogee measurement does not show TERM for most or our devices, don't worry.

I see, it's a blue jumper on the board ... done, solid green on BB now, all working right now, it seems this was the key to the kingdom

? Finally, follow clock is explained in the QS manual. It is also found on the unit itself within the menu

missed this one on the manual -you're right ... I have it enabled anyway.

question: after powering ADI-8-QS on with no card activity (ie nothing playing back) it shows AES1-4 clock state as solid green (ie: synched to BB @ 192 KHz) ... so why is MIDIremote showing mode = 44.1 KHz ? Ain't gotta showing 192 KHz ?

question: after playing back something from QuickTime (which is set at 24/192/7.1 -same surround layout as in Windows audio properties) I got sound as expected; for example, playing a stereo signal channels 1/2 are OK with said signal, 3/4 & 5/6 are solid green with no metering (OK) but 7/8 remains unsynched showing random metering, when playing a 5.1 sorround track 1/2 & 3/4 & 5/6 are solid green with metering and signal OK but 7/8 remains unsynched showing random metering, if I stop and close QT all AES1-4 come back to solid green ... I got a feeling this has nothing to do with the hardware setup but something related to QT for an 8-channel layout am I right ?

by the way (#1), annoying behaviour: when I switch of the ADI-8-QS a huge brief spike is heard on the monitors ... ain't the 8-QS be shutting off the outputs from the DA section before going off ? this is standard behaviour for most of high-end gear to avoid damage to whatever is connected to the analog outputs ... just wondering

by the way (#2), the 8-QS + MSP7 combo sound ... terrific :-) !

I'm still impressed ...

4

Re: setup problem with AES-32 interfacing to ADI-8-QS & ADI-192-DD

Spectrvm wrote:

question: after powering ADI-8-QS on with no card activity (ie nothing playing back) it shows AES1-4 clock state as solid green (ie: synched to BB @ 192 KHz) ... so why is MIDIremote showing mode = 44.1 KHz ? Ain't gotta showing 192 KHz ?

It does not measure and indicate incoming frequencies. If you look closer you will see that the sample rate field is dimmed as soon as Master is deselected.

Spectrvm wrote:

but 7/8 remains unsynched showing random metering, when playing a 5.1 sorround track 1/2 & 3/4 & 5/6 are solid green with metering and signal OK but 7/8 remains unsynched showing random metering, if I stop and close QT all AES1-4 come back to solid green ...

Sync problems with audio signal (modulated) only indicate a connection problem. I would first change the used AES cable. Is this really certified to work at 192 kHz? Many cables I know do not. Second step would be to change the clock source from WC to AES. See what happens.

Spectrvm wrote:

when I switch of the ADI-8-QS a huge brief spike is heard on the monitors ... ain't the 8-QS be shutting off the outputs from the DA section before going off ?

Yes, they are dimmed, but not totally muted (that requires relays, which is both clumsy and expensive).

Spectrvm wrote:

this is standard behaviour for most of high-end gear

...with hi-end prices...

Seriously I think that you have a big mismatch between the analog output levels of the QS and the sensitivity of the connected monitors. I am pretty sure you can easily overload them and have to reduce the volume at the QS for normal operation a lot. Then you get loud pops during power on/off. Reduce the sensitivity of the speakers and let the QS spit out more steam, then not only SNR is improved, but the noise is no longer disturbing too.

Regards
Matthias Carstens
RME

Re: setup problem with AES-32 interfacing to ADI-8-QS & ADI-192-DD

Hi Matthias ! Thanks for your replies !

This setup is getting problematic so I decided to step back from my initial surround setup to a 2-channel one until things get sorted out a bit. Divide et impera so they say ...

First, as you indicated previously I thoroughly checked both AES snakes and are OK -no problems with cabling so far. My ADI-8-QS works as expected as DA when feeding it with (and slaving it to) a CD player in any of it's AES/EBU inputs for example. This is valid for any of it's eight channels driving MSP7 speakers. I checked this using the same above-mentioned 8-channel AES snake using a BOB-32 and using every XLR input to connect the CD player successfully. On each channel-pair I got sound as expected.

But I'm still encountering erratic behaviour with the AES-32 feeding the ADI-8-QS with all the gear synched to Big Ben. What it works as a stand-alone setup it seems doesn't work as expected from the computer due to sync loss somewhere in the line.

I can't manage to get proper sound from the AES-32 with any major Windows app. To start with, running a sound test in dxdiag.exe shows everything OK but sound gets rendered to the right channel only even when TotalMix is clearly showing dxdiag reproducing a stereo signal. All apps, Audition configured with ASIO, MPC, etc, render sound to the right channel only, while again TotalMix shows a proper stereo signal being reproduced.

Before AND after upgrading the AES-32 driver from 3.0.5.8 to 3.0.5.9 (stating a fixed external sync issue) the ADI-8-QS AES digital input LEDs flash oftenly showing sync loss, even when the AES-32 driver property page shows all 8 channels firmly synched to the external Big Ben, to which the ADI-8-QS is obviously synched too -Big Ben shows all devices firmly synched at 192 KHz. This sync loss (whether real or not) is not noticeable while playing back (from QuickTime for example) with a stereo setup and the AES-32 interleaved option OFF, but, IS EXASPERATINGLY real and noticeable (cracks pops etc) with a stereo and/or surround setup and the interleaved option ON (which by the way is neccessary in a sourround setup). I don't know what QuickTime is using to send sound to the card but is obviously something different than anything all the major Windows apps do, because all in all is the only app which is sending audio to all channels in all configurations without any problems -even automatically upsampling to 24/192 when neccessary.

So, rounding things up:

1) synching: do you think the synching problem is in the ADI-8-QS trying to catch up or in the AES-32 outputs (which I'm more inclined to think they are) ? Does an AES-32 externally synched to Big Ben guarantee that all it's outputs will stay put at the rate Big Ben is dictating no matter what the computer apps are attempting to do ?

2) sound: what in the hell can be wrong in the setup/config (and it's obviously system-wide) to be getting sound in the right channel only ?  ... this issue annoys me the most. It's obviously something related to Windows/DirectShow/ASIO since QuickTime manages to get sound right.

The computer I'm using is the same I used for the last three years, it's super-stable, meticously cared for, minimal apps, no crap of any kind, dual Xeon workstation with plenty of resources. Before entering RME worked like a charm with a crappy AudioPhile for almost three years never having an issue with DirectShow and/or nothing else. It's tested to the bone.

And the worst part is that I started to get blue screens whenever TotalMix is open, but NEVER when I never opened it even once, and this is valid up to two weeks using QuickTime daily so I'm now almost sure is TotalMix the offending app ... system halt, hardware malfunction, happens sometime after opening TotalMix.

non-relevant issues:

Seriously I think that you have a big mismatch between the analog output levels of the QS and the sensitivity of the connected monitors. I am pretty sure you can easily overload them and have to reduce the volume at the QS for normal operation a lot. Then you get loud pops during power on/off. Reduce the sensitivity of the speakers and let the QS spit out more steam, then not only SNR is improved, but the noise is no longer disturbing too.

The ADI-8-QS is set at +4.2 dBu on all its outputs and my MSP7 speakers are all set to this same +4.2 dBu setting (they have switches on the back), so they are perfectly matched. This is what I first checked so I can reach 0 dBfs without risk.

6

Re: setup problem with AES-32 interfacing to ADI-8-QS & ADI-192-DD

According to your screenshot you forgot to set 'Professional' as output status. That would explain the sync problems at 192 kHz, as without Professional the output voltage is dropped to SPDIF standard.

If Quicktime plays back stereo, then all other applications do too. If not then you are not using 192 kHz with those (for example ASIO) and have to reconfigure your whole system to Single Speed operation.

Regarding your speakers: 'perfectly mateched' will most probably mean in this case to set the speakers to +19 dBu or whatever lower (!) sensitivity they offer. Try it.

Regards
Matthias Carstens
RME

Re: setup problem with AES-32 interfacing to ADI-8-QS & ADI-192-DD

first thing in the morning:

According to your screenshot you forgot to set 'Professional' as output status. That would explain the sync problems at 192 kHz, as without Professional the output voltage is dropped to SPDIF standard.

in driver property page: PROFESSIONAL ON ... done

If Quicktime plays back stereo, then all other applications do too. If not then you are not using 192 kHz with those (for example ASIO) and have to reconfigure your whole system to Single Speed operation.

in driver property page: WCK OUT SINGLE SPEED ON ... done

rebooting ... opened the driver property page and opened audition:

http://img72.imageshack.us/img72/6369/desktopse8.th.png

I did what you told me to do so why is the driver system clock set to 96 KHz (Audition is also showing the driver set at 96 KHz) when I clearly set all for 192 KHz as shown in Input status / pref sync ref ?

8

Re: setup problem with AES-32 interfacing to ADI-8-QS & ADI-192-DD

You did not set Audition to use 192 kHz. That simple. In general the application sets the sample rate, not the driver.

For all the rest (like WC Out) please study the manual.

Regards
Matthias Carstens
RME