|
Title: 44.1 and 48 clocks Post by: manisandher on April 26, 2016, 10:04:05 am Hey Peter, a quick question...
If I've been listening to a 44.1 based file for hours and then switch to a 48 based file, will the 48kHz clock need to be given any time to warm up? Or is it 'on' all the time? Mani. Title: Re: 44.1 and 48 clocks Post by: PeterSt on April 26, 2016, 10:10:28 am Mani,
Phew, good question, as I never really thought about that. Maybe they even require burn in ? Point is, I hardly ever play 48 based material, and if I do it is coincidence. So my own 48 based clock should be pretty cold ... I suppose that is the downside of switching off the other oscillator so it won't influence tyhe "playing one". Regards, Peter PS: Quote Point is, I hardly ever play 48 based material Ok, not true because I watch at least one movie per week (and they always use 48KHz sound).Title: Re: 44.1 and 48 clocks Post by: manisandher on April 26, 2016, 10:19:03 am It seems that the NOS1a switches back to the 44.1 oscillator by default. What I mean here is that if I play a 48 track, and then stop, and then start another 48 track, there is always that small tick before it plays. So the NOS1a has defaulted back to 44.1. So I can't simply play one 48 track and assume the 48 oscillator is still engaged and 'warming up', or 'burning in'.
I wonder if a 'cold' 48 oscillator would give the sound a bit of an edge compared to a 'warm' 44.1 oscillator. Is there even a case for deriving everything from a single 'super' oscillator that remains primed and ready to go all the time? I strongly suspect not, as all high-end gear has 2 oscillators... but I just wondered... Mani. Title: Re: 44.1 and 48 clocks Post by: PeterSt on April 26, 2016, 10:54:48 am Indeed that tick is always there, but strangely enough I only noticed myself last week (I don't even remember what I was doing, but it was quite annoying because I was testing something (?) which required start of playback each 5 seconds or so).
I don't think that tick belongs and I really wonder what it is. Should be something like me myself not detecting the current state and explicitly re-engage the 48 clock while it is already running. Or it is something with Windows 10 ? Point is : this wasn't so (I think). Peter Title: Re: 44.1 and 48 clocks Post by: PeterSt on April 26, 2016, 05:32:09 pm Quote (I don't even remember what I was doing, but it was quite annoying because I was testing something (?) which required start of playback each 5 seconds or so). LOL, I was comparing YOUR recordings ... Peter Title: Re: 44.1 and 48 clocks Post by: manisandher on April 26, 2016, 08:05:59 pm Haha... I knew there was a reason why I chose 24/48 for those!
Mani. |