Dither
-
- Posts: 1743
- Joined: Wed May 15, 2002 4:00 pm
- Contact:
-
- Posts: 307
- Joined: Thu Nov 13, 2003 4:00 pm
- Location: Oregon
- Contact:
I'm curious about that as well.
The thread about VDAT has been good for explaining that SFP is 32-bit INT internal.
So the obvious questions are if you -> 24-bit
or if you -> 16-bit, what is actually happening there.
So for example, if I play from Scope into ASIO in Samplitude at 24-bit/44.1, whom is doing what do get that to there...????
The thread about VDAT has been good for explaining that SFP is 32-bit INT internal.
So the obvious questions are if you -> 24-bit
or if you -> 16-bit, what is actually happening there.
So for example, if I play from Scope into ASIO in Samplitude at 24-bit/44.1, whom is doing what do get that to there...????
-
- Posts: 777
- Joined: Sat May 25, 2002 4:00 pm
- Location: The Great White North
- Contact:
- BingoTheClowno
- Posts: 1722
- Joined: Wed Nov 12, 2003 4:00 pm
- Location: Chicago
- Contact:
-
- Posts: 777
- Joined: Sat May 25, 2002 4:00 pm
- Location: The Great White North
- Contact:
-
- Posts: 307
- Joined: Thu Nov 13, 2003 4:00 pm
- Location: Oregon
- Contact:
unless you have a high quality - highly dynamic signal (say solo violin in a classical orchestra recording) I bet you don't hear any (quality) difference at all, even from truncation.
You possibly may notice a slight difference due to the converter's playback (a 24 bit converter fed with a 16 bit signal), but not at 'regular' mixing levels.
We're not talking SACD mastering, do we ?
cheers, Tom
You possibly may notice a slight difference due to the converter's playback (a 24 bit converter fed with a 16 bit signal), but not at 'regular' mixing levels.
We're not talking SACD mastering, do we ?
cheers, Tom
-
- Posts: 777
- Joined: Sat May 25, 2002 4:00 pm
- Location: The Great White North
- Contact:
SCOPE uses 32 bit floating point internally, NOT 32 bit integer.
Regardless of the results of this interesting investigation, I have no desire to "avoid" the SCOPE dithering algos. They sound good to me. I don't really care whether or not they're sub-optimal. If the dithering turns out to be some kind of shortcut, who's going to go throw their SCOPE cards away? Not me.
Regardless of the results of this interesting investigation, I have no desire to "avoid" the SCOPE dithering algos. They sound good to me. I don't really care whether or not they're sub-optimal. If the dithering turns out to be some kind of shortcut, who's going to go throw their SCOPE cards away? Not me.
-
- Posts: 777
- Joined: Sat May 25, 2002 4:00 pm
- Location: The Great White North
- Contact:
Hmmm, maybe you're right. (Maybe we're both right...?!?)
SHARC ADSP-21065L
Sorry for spreading mis-information, I was sure that the SHARCs were floating point only...
SFP could be done entirely using 32 bit ints after all. I'd like to see the reference, but regardless you all have my apologies!
Johann
SHARC ADSP-21065L
Sorry for spreading mis-information, I was sure that the SHARCs were floating point only...

SFP could be done entirely using 32 bit ints after all. I'd like to see the reference, but regardless you all have my apologies!
Johann
Things are a bit confusing.
I've always thought that SFP was 32 integer, and what I know for sure is that VDAT records in that format.
Confusion is brought from what is written on two different pages of CWA site.
I quote what's said in the Introduction page for Scope platform:
"The employed SHARC DSP was specifically designed to perform high-resolution audio processing. It always processes the audio with a 32-bit resolution, and algorithms and parameters are computed with a floating-point resolution of even 40 bits. "
This seems a confirmation of the 32 integer resolution...
But in the Scope Project page (the link 3 places lower after Introduction), in the Highlights paragraph, processing is reported to happen at 32bits floating point.
This creates some confusion....
I've always thought that SFP was 32 integer, and what I know for sure is that VDAT records in that format.
Confusion is brought from what is written on two different pages of CWA site.
I quote what's said in the Introduction page for Scope platform:
"The employed SHARC DSP was specifically designed to perform high-resolution audio processing. It always processes the audio with a 32-bit resolution, and algorithms and parameters are computed with a floating-point resolution of even 40 bits. "
This seems a confirmation of the 32 integer resolution...
But in the Scope Project page (the link 3 places lower after Introduction), in the Highlights paragraph, processing is reported to happen at 32bits floating point.
This creates some confusion....
-
- Posts: 777
- Joined: Sat May 25, 2002 4:00 pm
- Location: The Great White North
- Contact:
It probably is both then.
The older SHARC can handle 32 bit int and 32 bit float.
The newer SHARCs also support 40 bit float, so maybe the old ones do too... Dunno.
Anyway it makes sense that the data flies around as integers and the math processing is at least sometimes done as floating point. There are many algorithms that nobody in their right mind would optimize for integer...
<font size=-1>[ This Message was edited by: blazesboylan on 2004-08-19 18:51 ]</font>
The older SHARC can handle 32 bit int and 32 bit float.
The newer SHARCs also support 40 bit float, so maybe the old ones do too... Dunno.
Anyway it makes sense that the data flies around as integers and the math processing is at least sometimes done as floating point. There are many algorithms that nobody in their right mind would optimize for integer...
<font size=-1>[ This Message was edited by: blazesboylan on 2004-08-19 18:51 ]</font>
whether certain calculations are done with floats is impossible to tell but the sync and async signals are all done with 32 bit integer.
if you want to find out how the signals are being transfered between your recording software and the scope card record a signal into a 2track editor and look at it. also try attenuating the signal on one side of the exchange and boosting it on the other.
what would your audio sound like it was dithered over and over as you build your mix or do multiple passes for processing.
j9k
if you want to find out how the signals are being transfered between your recording software and the scope card record a signal into a 2track editor and look at it. also try attenuating the signal on one side of the exchange and boosting it on the other.
what would your audio sound like it was dithered over and over as you build your mix or do multiple passes for processing.
j9k
-
- Posts: 307
- Joined: Thu Nov 13, 2003 4:00 pm
- Location: Oregon
- Contact:
Yeah, I understand what Blaze is saying about not really worrying to much about this... but since there are a lot of audio geeks here...

I was thinking on the way home today that truncation in PCM could blast you in both FREQ and in AMPLITUDE. So a simple test might be to generate a 440Hz signal, and then push it to a near-peak level. Then check out the values of the samples in 32-bit INT. Then the fun part, take that, and just blast it to 24-bit INT, and see what you end up with. If it's truncating, you could end up with next-to-nothing on output.
Someone correct me if this I'm wrong. I'm just thinking about amplitude for this experiment...

I was thinking on the way home today that truncation in PCM could blast you in both FREQ and in AMPLITUDE. So a simple test might be to generate a 440Hz signal, and then push it to a near-peak level. Then check out the values of the samples in 32-bit INT. Then the fun part, take that, and just blast it to 24-bit INT, and see what you end up with. If it's truncating, you could end up with next-to-nothing on output.
Someone correct me if this I'm wrong. I'm just thinking about amplitude for this experiment...