SP-DIF source

PC Configurations, motherboards, etc, etc

Moderators: valis, garyb

Post Reply
Dekkie
Posts: 13
Joined: Mon Mar 27, 2006 4:00 pm
Location: Holland

Post by Dekkie »

Dear (more expierienced) friends,

I would like to set up the following:
On my first PC, I would like to play back music, using the sp-dif output of my Audigy, then via the sp-dif input of my Scope Home on my second PC, record it in Cubase.
Please, how do I go about setting this up?
I cannot even get Cubase to 'see' a different input than analog...

Thanks!

Dekkie
arela
Posts: 858
Joined: Tue Aug 27, 2002 4:00 pm
Location: Norway

Post by arela »

Hi
On the "Scope Livebar" >Set >Samplerate settings. A red dot will appear when s/pdif is connected.
And when recording, i think you need to set Scope as slave.
On "Routing Window" >Hardware IOs > sp-dif source.

Why not play and record the files in the same pc?

Cubase should just see your Scope ASIO drivers whatever you use s/pdif, adat or analog.
User avatar
astroman
Posts: 8455
Joined: Fri Feb 08, 2002 4:00 pm
Location: Germany

Post by astroman »

Cubase cannot 'see' it directly.
In your project you have to connect s/pdif source to an asio destination channel, then it will show up in the sequencer at the respective position.

You may have to set the master (digital clock) sync source in Scope's sample rate dialog to s/pdif, effectively slaving Scope to the Audigy's clock - at least that's the way s/pdif works according to specs (example to connect an external cd player via s/pdif)

in your current setup it's most likely set to 'internal'.
It may work to keep Scope as the clock master if you have connected the s/pdif destination as well and set the Audigy to accept it as it's master clock.

That's the 'modern extension' of the classic mode and supposed to work with several external FX units - it definetely does NOT work on the Pulsar One, but everything from the Luna upwards supports it.
But afaik it's non-standard - some devices work, some not.

Sounds complicated ?
well, it is (kind of), but it's crucial for (the quality of) any digital connection, so worth spending some extra time understanding it.

The problem is that ALL digital connections (must) have an error correction which some times works so well that it may even fool you about your setup.
I.e. it makes wrong connections work, at least to a degree and without close listening one may overlook it and eventually end with total crap on the tracks.

From the software view your problem is solved by adding the s/pdif modules to the project and connect them to an asio source/destination pair - then they appear in the sequencer.
On the hardware side it's the proper setting of digital sync AND the use of the proper cables (!).
Use a 75 Ohm coax as used for video in multimedia applications - the one with the yellow connector. For a short distance this should be ok, but a quality cable (speced for digital audio) is a good investment.
A 'regular' audio cable will NOT work - try it out, you will hear a faint brizzling noise or a (very slightly) distorted or blurred sound.

So to say - digital is not digital :wink:
it's NOT like a sector from a hard disk that always retrieves the same bits and bytes.

The quality depends on the cable, the clock stability and the error correction of the receiving device.
It is not uncommon that the analog ports produce a better (or at least identical) sound quality - as mentioned it depends on several influences and only careful listening can tell.

Added noise is of only few concern for current converters (imho) - so you may use the analog ports as well and spare the config.
I don't have an Audigy myself, but I wouldn't want to slave my Pulsars to it's clock - there must be a reason why people spend > 1k Euro for a dedicated high quality clock source... :wink:

cheers, Tom
Post Reply