Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Timeline]

Thanks Bob,

"I think you are hitting a few nails on the head here. Internal headroom in converters is often not well taken care of. That's why I recommended -3 dBFS peak maximum when converting, unless you have a well-designed converter."

Do you mean -3 on my IO's peak meter?

"If all you are doing is mixing, it's not possible to create INTERSAMPLE peaks (additional peaks between the samples, or "higher bandwidth"). The material was prefiltered to the Nyquist rate when it was recorded, and you'll create nothing new there. "

So your saying even if you record at 96K or above nyquist filter would strip harmonics and no interaction above 20K even though the audio bandwidth is higher could exist?  That doesnt make sense if you have audio there. It can't be all noise.

Lavry said  96K SR was well beyond the filter points and 60K SR was clear.

I don't get it.  

[bobkatz]

Timeline wrote on Sun, 26 December 2004 20:41

Thanks Bob, "I think you are hitting a few nails on the head here. Internal headroom in converters is often not well taken care of. That's why I recommended -3 dBFS peak maximum when converting, unless you have a well-designed converter." Do you mean -3 on my IO's peak meter?

Yes, of course that's extremely conservative. If you have a sharp eye, -1 dBFS peak will also do. But you have tons of "footroom" at 24 bit, why not just be safe and be done with it.

Quote:

BK said: If all you are doing is mixing, it's not possible to create INTERSAMPLE peaks (additional peaks between the samples, or "higher bandwidth"). The material was prefiltered to the Nyquist rate when it was recorded, and you'll create nothing new there. and you replied: So your saying even if you record at 96K or above nyquist filter would strip harmonics and no interaction above 20K even though the audio bandwidth is higher could exist?  That doesnt make sense if you have audio there. It can't be all noise.

No, that's not what I said. I said that digital mixing would not create any additional bandwidth above Nyquist. Since the 96K sample rate can conceivably contain harmonics of the music up to its Nyquist frequency of 48 kHz, then if they are there in the recording, the digital mixing will preserve them, not adding or taking away from them.

You should see what kinds of non-musical garbage above 20 kHz my Cedar Retouch color graph display shows in a number of "96 kHz" recordings. Remember, all the buzz and harmonics of tics and pops and electrical noises end up there along with whatever harmonics of the music might be up there. Oh well, it's inaudible, anyway?  Who cares about a few burnt out tweeters?  (My tweeters have never burned out so it's an academic question anyway).

BK

[Timeline]

OK Bob,

Thanks very much for your fine advise on IO peaks and I will do exactly that on my next sessions.

After reading Dans threads and your comments, I thought it would be a good idea to freshen my memories of this test I did once on a ProTools rig.

So, I just now finished convertomg a tune of 54 tracks of 96k audio to 48K that I had been working on today. it was mostly live instruments. Rock stuff.  

The G5 2.5ghz computer headroom was fine at 96k and I thought it would be a good one tune to use because of the many vocal tracks and rock percussive rhythms.

I used the internal clock of one of my MOTU HD192's as sync master per reading here that this would likely be best for the conversion.  I used the DAW's best algorithm available as well which doubled the conversion time.

When it finished,  about an hour later, I A/B'd the sound of the tracks mixed with identical eq's and plugs in exactly the same mannor I had been listening all day.

My setup was that I fed multitrack analog from the DA's IO's through the same API mixer at calibrated levels to an L2 and then to monitor.  I listened on headphones, MA1 Dynaudio monitors and M-audio BX8 for a lo-fi comparison.

What I heard was: less top on the rhythm & acoustic guitars.  Silkiness between symbols snare and hard transient percussion like tamb and shakers lost snap as well as most of the other instruments. Vocals became a bit more grainy.
Overall just less hi-fi on the top end and the mix sounded clean but with less separation in the mids. Similar to taking 15k and rolling off 2 db shelf.

Also the low end didn't seem quite as nice although I don't understand why.

Here's the thing.  At all times the entire all day session and this 96K to 48K comparison was done monitoring THROUGH an L2 set to 44.1  16bit.

Since Nyquist rolls everything off in the L2 from either playbacks above 20khz,  why did it still sound cleaner with 96K on the original audio tracks out analog?

Consider also that I did this same test at O'Henry Studios Burbank about 2 years ago on a ProTools HD system and it rendered the same results to my ear and the tech in the room.

Would you agree for now that with todays commonly used collection of digital audio gear it might be safer to continue 96K recordings to preserve our projects for future remixes for a time when better gear might be available considering we don't really know 'what's inside the box' and why these sound changes appear in the most popular equipment used in todays studios?   This is still gray area to my ear.

Thanks

Gary Brandt

[Albert]

Gary, my response is based on personal experience, not scientific knowledge:

In my opinion, if you had recorded the original tracks at 48k it would sound better than recording at 96k and then SRC'ing down to 48k. Likewise, if you had played the mix back at 96k, gone analog through good converters and re-recorded it through good converters on another machine running at 48k it would sound better than using SRC to reduce the sample rate. Also, I think to be entirely objective, your test would require that the audio be played back directly to analog from 96k and then directly to analog at 48k. Putting the L2 at 44/16 in there would seem to me to skew the listening test because you are adding the variable of how it handles the calculations to 16/44 from two different sample rates.

Most likely, I have not had access to the very finest in SRC software/gear, but I've never been entirely happy with PT, DP, Peak, BarbaBatch, or even my hardware L2, although that has been pretty good.

But SRC is probably a subject for a whole 'nother thread.

Getting back to mixing in the box, I'd like to revisit the comment about summing being just math, and then Bob O's reply. If indeed summing is simple addition, then why would this be implemented differently in different DAW's? Addition is addition.

And I do hear differences between DAW's. Often very very subtle, but there nevertheless. Even playing back two track stereo mixes between different software can produce slightly differnet tone or levels.

[Bob Olhsson]

While addition IS addition, there are limits to how much you can add before running out of headroom. It's a SYSTEM. This must ALWAYS be borne in mind!

How the application systematically handles the level changes required can be all over the map in terms of the number and accuracy of calculations and how the level changes are dithered back to something that can be written to a file or sent to an output.

[bobkatz]

Timeline wrote on Tue, 28 December 2004 01:28

OK Bob, Thanks very much for your fine advise on IO peaks and I will do exactly that on my next sessions.

Maaaa Pleazur

Quote:

So, I just now finished convertomg a tune of 54 tracks of 96k audio to 48K that I had been working on today. it was mostly live instruments. Rock stuff.   SNIP I used the internal clock of one of my MOTU HD192's as sync master per reading here that this would likely be best for the conversion.

Well, if you are doing a digital sample rate conversion from file to new file, the MOTU operates without any clock or real time audio at all. You can do this without a clock. Unless Motu complains because its audio system wants a clock, which is just a subsystem, not relevant to the other subsystem doing the SRC that doesn't even need an audio interface.

Quote:

I used the DAW's best algorithm available as well which doubled the conversion time.

Were you able to produce 32 bit float output files?  If not, did you tell it to dither down from 32 to 24 after doing the conversion from 96 khz to 48 kHz?

Quote:

What I heard was: less top on the rhythm & acoustic guitars.  Silkiness between symbols snare and hard transient percussion like tamb and shakers lost snap as well as most of the other instruments. Vocals became a bit more grainy. Overall just less hi-fi on the top end and the mix sounded clean but with less separation in the mids. Similar to taking 15k and rolling off 2 db shelf.

There is always some loss. But it's not due to the sample rate. It's due to several variables:

1) Consider whether your D/A converter's upsampling ratios and internal filtering are giving your less than optimum picture or presentation at the two different sample rates

2) Consider whether MOTU's algorithm was as well implemented as it could be (see dither notes above) and/or is as good as a $4000 Weiss or DCS or Lavry or other sample rate converter

3) And even with all the above considered, since every DSP in line is cumulative, it is possible, that even with the VERY best of the above, that that single generation of additional filtering to reduce the rate, on top of the original recording, was enough to take it down hill. However, this has not been my experience to my ears in straight SRCs done with extremely high quality algorithms and then reproduced by a D/A converter whose upsampling path at 48 khz is as good-sounding as at 96K.

And a question: Is there a technical reason why you reduced the rate to 48K now rather than mix at 96K, and retain that resolution until the last minute when and ONLY in the mastering it gets reduced to 44? That reduces one more huge filtering and calculatoin step.

Quote:

Here's the thing.  At all times the entire all day session and this 96K to 48K comparison was done monitoring THROUGH an L2 set to 44.1  16bit.

I might be a little obtuse, but I don't understand the block diagram. How did you feed the L2 a 96K or 48K source and get it to say "4416" at all? You were using the D/A converter in the L2?

Quote:

Since Nyquist rolls everything off in the L2 from either playbacks above 20khz,  why did it still sound cleaner with 96K on the original audio tracks out analog?

Can we leave that question open until we sort out the other data?  For many years I heard a BIG difference between 96 and 48 (especially 44) until I updated to converters whose philosophy is to more properly upsample the lower rates. Also, for many years I heard a BIG difference between 96 sources and downsampled results until I got the Weiss SRC. One pass through the Weiss, monitored through a good DAC, is the least degraded SRC I've heard so far. I'm sure the DCS and a few others pass that test as well.

However, two passes through the Weiss and you start to hear it. It's important to separate the issues, though. Take a 96 down to 44 and then back up to 96 and it sounds very very close to the original. This helps to eliminate the variables of whether the sample rate itself is poorly reproduced on a DAC. Calculations in the digital world have gotten better than I think MOTU at least can handle. Have you tried Barbabatch? You might be in for a surprise. NO, I have not personally done a shootout yet between Barbabatch and MOTU, but I have a lot of confidence in BB's file integrity. BB also allows you to either make 32 bit float files (which unfortunately MOTU cannot handle to my knowledge) or dither down to 24 within the SRC algorithm.

Quote:

Consider also that I did this same test at O'Henry Studios Burbank about 2 years ago on a ProTools HD system and it rendered the same results to my ear and the tech in the room.

Not surprised. One of the reasons we are arguing for the 96 K sample rate it is a lot easier (less costly, less lossy) to deal with in the face of the mediocre DSP that we encounter. That's why I suggested you mix and stay at 96K for as long as possible and then let the mastering engineer do the one and only conversion to 44 and to 16 at the very very end of the game. You will get better results, I doubt anyone would argue with you.

It is a separate issue from whether 96 is "better" than 48. In a perfectly designed world, they should be virtually indistinguishable. But perfect DACs and perfect filters hardly exist.

Quote:

Would you agree for now that with todays commonly used collection of digital audio gear it might be safer to continue 96K recordings to preserve our projects for future remixes for a time when better gear might be available considering we don't really know 'what's inside the box' and why these sound changes appear in the most popular equipment used in todays studios?   This is still gray area to my ear.

I'm 100% in favor of it for that reason and also because of the reasons of cumulative degradation. It just takes longer to reach the bottom of the hill if you start higher on the hill  

After a few mixes and compressors, and equalizers and filters are thrown in, the inevitable degradation begins.

Hope this helps, too,



Bob

[bobkatz]

Albert wrote on Tue, 28 December 2004 12:18

Gary, my response is based on personal experience, not scientific knowledge: In my opinion, if you had recorded the original tracks at 48k it would sound better than recording at 96k and then SRC'ing down to 48k.

If your goal is to mix at 48K, I would tend to agree, the losses of the SRC conversion completely cancel out any advantages of an original recording at 96K. However, why not mix at 96K in the first place?

Quote:

Likewise, if you had played the mix back at 96k, gone analog through good converters and re-recorded it through good converters on another machine running at 48k it would sound better than using SRC to reduce the sample rate.

Now I think this is the reaction of someone who has not experienced the most transparent of SRC conversions. It's been a good 5-10 years since D/A/D conversion sounds better, transparent, more open, and purer than a given SRC. Ask 10 mastering engineers. Ask Bob Ludwig.... Unless you like the additional analog "flavor" of the D/A/D conversion.

Quote:

Getting back to mixing in the box, I'd like to revisit the comment about summing being just math, and then Bob O's reply. If indeed summing is simple addition, then why would this be implemented differently in different DAW's? Addition is addition.

Addition is addition, but it is usually accompanied by multiplication, unless all the DAW's faders are held at exactly 0 dB and pans are full left and right (unless you're Yamaha, but that's another topic). In other words, you'll find that most DAWs manage the addition pretty well, if you run, for example, a 4 into 2 folddown through a DAW with all faders at 0 and if the signal doesn't overload, you'll get a completely transparent summing. You won't even have to add dither!

So, back to multiplication, that does separate the men from the boys, though most would argue that equalization and compression further separates them. The multiplcation should be done at high precision, the coefficients for the fader values well chosen, etc. I'm sure that's done very well within Pro Tools TDM or HD, by the way.

Quote:

And I do hear differences between DAW's. Often very very subtle, but there nevertheless. Even playing back two track stereo mixes between different software can produce slightly differnet tone or levels.

Yes, often subtly different. Makes you bang your head against the wall, as it is DIGITAL. Separating the variables and finding out WHY they sound different is a much more difficult investigation.

Even the L2 Native sounds subtly different from the Hardware or TDM  versions. Different calculations, naturally, so I'm slowly dissolving into obscurity......  

BK

[Albert]

Bob said:

"Now I think this is the reaction of someone who has not experienced the most transparent of SRC conversions. It's been a good 5-10 years since D/A/D conversion sounds better, transparent, more open, and purer than a given SRC. Ask 10 mastering engineers. Ask Bob Ludwig.... Unless you like the additional analog "flavor" of the D/A/D conversion."

Well, then it is obvious I haven't experienced good SRC conversions. Most of what I've heard sounds absolutely terrible. That's using standard settings in DP, Peak, PT, that kind of software. In all fairness, it has been a long time since I've heard BarbaBatch, so it's quite likely more recent versions are better. Perhaps I should try it again.

[jfrigo]

Albert wrote on Tue, 28 December 2004 15:17

Bob said: "Now I think this is the reaction of someone who has not experienced the most transparent of SRC conversions. It's been a good 5-10 years since D/A/D conversion sounds better, transparent, more open, and purer than a given SRC. Ask 10 mastering engineers. Ask Bob Ludwig.... Unless you like the additional analog "flavor" of the D/A/D conversion." Well, then it is obvious I haven't experienced good SRC conversions. Most of what I've heard sounds absolutely terrible. That's using standard settings in DP, Peak, PT, that kind of software. In all fairness, it has been a long time since I've heard BarbaBatch, so it's quite likely more recent versions are better. Perhaps I should try it again.

I must concur with Bob. SRC is no longer a dreaded problem. Sonic HD in the software world, or Lavry, Weiss, and some others in the hardware world, and the current  t.i. 4192 chip (and 4193) being used in some new more affordable designs are all very capable SRC options and are more transparent than a trip through D/A/D. The software you mention is not state of the art for SRC.

OK, only 8 more mastering engineers to ask...

[Ralf Kleemann]

Quote:

You should see what kinds of non-musical garbage above 20 kHz my Cedar Retouch color graph display shows in a number of "96 kHz" recordings. Remember, all the buzz and harmonics of tics and pops and electrical noises end up there along with whatever harmonics of the music might be up there. (...) BK

I'm going back a few postings here, but I just wanted to add that there are enough bad things happening in the audible band - I've heard more than one recording with incredible peaks in the 15-16 kHz region that told me a lot about the listening capabilities of the people involved "Afro Celt Sound System 2: Release" is a good example - possibly an exciter turned up to "11" on the title track, and no one noticed it.

I'm aware that this does not touch the original topic, it's just meant to be a footnote...

Ralf

[danlavry]

jfrigo wrote on Wed, 29 December 2004 07:07

Albert wrote on Tue, 28 December 2004 15:17 Bob said: "Now I think this is the reaction of someone who has not experienced the most transparent of SRC conversions. It's been a good 5-10 years since D/A/D conversion sounds better, transparent, more open, and purer than a given SRC. Ask 10 mastering engineers. Ask Bob Ludwig.... Unless you like the additional analog "flavor" of the D/A/D conversion." Well, then it is obvious I haven't experienced good SRC conversions. Most of what I've heard sounds absolutely terrible. That's using standard settings in DP, Peak, PT, that kind of software. In all fairness, it has been a long time since I've heard BarbaBatch, so it's quite likely more recent versions are better. Perhaps I should try it again. I must concur with Bob. SRC is no longer a dreaded problem. Sonic HD in the software world, or Lavry, Weiss, and some others in the hardware world, and the current  t.i. 4192 chip (and 4193) being used in some new more affordable designs are all very capable SRC options and are more transparent than a trip through D/A/D. The software you mention is not state of the art for SRC. OK, only 8 more mastering engineers to ask...

One needs to “slow down” here. Yes, SRC’s have come a long way. The older AD1890 yielded 106dB THD+N at 1KHz (full scale) and 100dB at 10KHz. The AD1895 specs are much better, THD of 115dB and DR of 125dB. The AD1896 yields 117dB THD and 132dB dynamic range worst case!.  

Crystal (Ciruss) and TI have some great specs as well. Clearly the initial inclination is to go for the better numbers. But what do the numbers mean? The very old AD1890 already had respectable numbers when compared to most IC AD’s (even by today’s standards).
Should there be any difference between say an AD1895 and AD1896?. The story regarding the differences (AD1896 is better) is not so much because of better THD and dynamic range specs.

Say you have a great AD, with a great un weighted dynamic range of 125dB. Say you pass the data through a SRC. What is the combined outcome?
125dB AD with 130B SRC yield 123.8dB dynamics
125dB AD with 135B SRC yield 124.6dB dynamics
125dB AD with 140B SRC yield 123.86dB dynamics
125dB AD with 144B SRC yield 123.946dB dynamics

In other words, there is hardly a difference or improvement.

Let’s repeat it with say 100dB dynamic range digital audio signal (closer to real world 16 bit release)
100dB signal with 130B SRC yield 99.996dB dynamics
100dB signal with 135B SRC yield 99.999dB dynamics
100dB signal with 140B SRC yield 100dB dynamics
100dB signal with 144B SRC yield 100dB dynamics

I could repeat the above exercise for THD+N (total harmonic distortions and noise). With similar OUTCOME NUMBERS for THD+N, one may wonder if and why the better SRC NUMBERS tell the story. I’ll say that much: they don’t tell the whole story.

One has to understand the mechanism of what takes place with the SRC and the clocks. Also one has to understand the measurement itself (what does it measure, and what does it not measure).

But even before we get deep into it, the first question is: How much jitter was there during the measurement? If you wish to use an SRC to help solve jitter, what is the use in specifying it while it is operating with almost no jitter? What will happen when you introduce some jitter?

In my view it is very shallow to see the SRC as a jitter removing magic block. Yes, the devices are getting better, and some are good. But to assume that their operation will not degrade when the input and/or output (sampling ratio) is jittery or varying with time is sloppy at best. Sample rate conversion does alter the data. With more jitter, SRC alters it differently, and some of the tools used to measure do not show the differences well.
 
Regards
Dan Lavry
http://www.lavryengineering.com

“In a time of deceit, telling the truth is a revolutionary act.”

[Timeline]

Curious,

What meathod would one use to 'introduce' controlled jitter for a measurment?
What might the jitter source be?

What might the source be which cause jitter in actual use?

[bobkatz]

Timeline wrote on Sat, 08 January 2005 23:34

Curious, What meathod would one use to 'introduce' controlled jitter for a measurment? What might the jitter source be? What might the source be which cause jitter in actual use?

You use a "jitter generator". I have one of those, actually. But I haven't used it in a long time. In the old days I was trying to get the cleanest signal into a DAC's receiver chip. But that was in the days of the Crystal 8412 receivers and so on. Things have come a long way, dual PLLs implemented well have been done by a select few manufacturers. I no longer bother to measure the interface jitter on the digital side, I just measure the effects on the analog side.

Jitter generators are probably at this point only important to OEMs and chip manufacturers. To test jitter attenuation.

BK

[danlavry]

bobkatz wrote on Sun, 20 February 2005 21:45

Timeline wrote on Sat, 08 January 2005 23:34 Curious, What meathod would one use to 'introduce' controlled jitter for a measurment? What might the jitter source be? What might the source be which cause jitter in actual use? ....I just measure the effects on the analog side. BK

I heard about such practices, the "poor man" way to measure jitter by looking at an FFT. It never made sense to me, and still does not. That 1KHz sideband measurement around 10KHz tone does not reveal much of the jitter picture. Generating those 1KHz sideband requires a well calibrated 1KHz modulated jitter source, and the FFT test is only about the rejection of 1KHz energy. It does not show all the random causes of jitter, such as an oscillator with a lot of random jitter energy (say below 1KHz), or other jitter sources (such as power line coupling or coupling of the MSB from the data to the clock, which can induce a lot of jitter below 1KHz.

So far, that FFT 1KHz sideband test seems to me to have been invented by some one's marketing department, but I am certainly open and ready to be corrected.

It is not only the concept that I question. The measurement itself may yield some approximate results while inducing high level of jitter, but as you approach tiny jitter, the measurement loses accuracy. One can not assume that injecting say 1nsec 1kHZ modulation will yield information about what will happen when you inject say 50psec jitter. The random jitter and the 1KHz "forced" jitter do not add linearly. Not to mention that the test does not answer the jitter rejection at across the audio band and way beyond (jitter at any frequency is bad news).

I do not view the job of inserting say a 50psec 1KHz jitter, with say 10psec random component, a poor man tool. I can design and build such a source, and verifying (measuring) it will take some real jitter meaqsuring equipment - we are talking upwards of $50000 at those low levels.

If one wishes to learn about the PLL filter characteristics, I would sugest that there are simpler and very solid methods available, and they yield a plot across a wide frequency band, not just 1KHz. Of measuring the filter does not tell the whole story either.

The costs of state of the art jitter measurement equipment are very high, but I do not view it as a justification for cutting corners...

I hope I am wrong. I also want to find a cheaper way to measure jitter.

Regards
Dan Lavry
www.lavryenineering.com

     

[bobkatz]

danlavry wrote on Tue, 22 February 2005 11:29

bobkatz wrote on Sun, 20 February 2005 21:45 Timeline wrote on Sat, 08 January 2005 23:34 Curious, What meathod would one use to 'introduce' controlled jitter for a measurment? What might the jitter source be? What might the source be which cause jitter in actual use? ....I just measure the effects on the analog side. BK I heard about such practices, the "poor man" way to measure jitter by looking at an FFT. It never made sense to me, and still does not.

Well, ultimately it is the effect on the analog signal that counts. Jitter in the interface is a bit like the "if a tree falls in the forest does anyone hear it" argument, because until it goes through the PLL and is attenuated, and then is reclocked, drives the converter section and then the "modulated" affect can be seen or heard... what's the point?

The late Julian Dunn invented the J-Test signal which has been very successful. And a simple 1/4 sample rate sine wave test signal does reveal differences between various converters quite well. In addition, TC Electronic has written an excellent white paper on a simple 12 kHz sine wave test:

Please see:

http://www.tcelectronic.com/default.asp?id=1573  and click on "Clock and Synchronization inthe System 6000"

Quote:

It is not only the concept that I question. The measurement itself may yield some approximate results while inducing high level of jitter, but as you approach tiny jitter, the measurement loses accuracy.

I agree, when you're interested in looking at the clock directly. But accuracy compared to what? Isn't it ultimately the effect on the analog stage that you are looking for? Yes, designers like you absolutely need to be able to measure the clock jitter directly and the attenuation of the PLL.  If they have the money to purchase a clock jitter analyser, as you say, not a poor man's tool) but ultimately it is the effect on the analog signal that counts. And the job of the testing engineer to see the effect on the analog signal. How little jitter do you want to have in a clock signal? The answer: As little jitter as is necessary so that it has no audible (or measurable) affect on the analog signal.