23.976 in, 23.976 out

[csundbom]

For NTSC Film DVDs, I want to preserve the framerate of 23.976 and avoid audio resampling. A dropped audio frame now and again over SPDIF doesn't bother me. My output frame rate is 23.976 and works perfectly with my external scaler.

With 23.976 source rate, ReClock insists of using "Cinema Adapation" and changing the source framerate to 24.000, which is not what I want. Forcing frame rate to 23.976 in the dropdown effectively invalidates ReClock, and no syncing between input and output clocks takes place.

How can I configure ReClock to do what I want?

[Jong]

Maybe James can finally confirm this once and for all, but the common understanding is that Reclock already does what you want it to do and the messages displayed are wrong/confusing. If you refresh rate is set to 23.976 or a multiple and you playback 23.976 media there will be no adaptation.

[James]

Maybe James can finally confirm this once and for all, but the common understanding is that Reclock already does what you want it to do and the messages displayed are wrong/confusing. If you refresh rate is set to 23.976 or a multiple and you playback 23.976 media there will be no adaptation.
Correct. Confirmed.

[James]

With 23.976 source rate, ReClock insists of using "Cinema Adapation" and changing the source framerate to 24.000, which is not what I want.
Look closer. It does not change the source framerate.

[ashlar]

Look closer. It does not change the source framerate.Well, then change the message. :)

But, for instance, Zoom Player reports (pressing I on the keyboard):

Listed FPS: 23.976

Actual FPS: 24.000

Where does the difference between listed and actual come, if not from the change that Reclock is declaring to be applying?

Furthermore... I am on 48.008Hz, does this qualify for no adaptation? All things summed up, I think some clarifications in the documentation would be really useful. Reclock is full of "little mysteries".

[csundbom]

Look closer. It does not change the source framerate.

ReClock reports "Cinema Adapation: media speed changed to 24.000 fps. Audio resampled to 48048 Hz". 48040 happens to be "24.000/23.976 * 48000". If input and output framerates are both 23.976 and "Cinema Adapation" indeed does nothing to the frame rate, audio should stay untouched, no? Or is this just a message problem?

[James]

Well, then change the message. :)

But, for instance, Zoom Player reports (pressing I on the keyboard):

Listed FPS: 23.976

Actual FPS: 24.000

Where does the difference between listed and actual come, if not from the change that Reclock is declaring to be applying?

Ask Blight. Certainly not from ReClock.


Furthermore... I am on 48.008Hz, does this qualify for no adaptation?

Sure.

[James]

ReClock reports "Cinema Adapation: media speed changed to 24.000 fps. Audio resampled to 48048 Hz". 48040 happens to be "24.000/23.976 * 48000". If input and output framerates are both 23.976 and "Cinema Adapation" indeed does nothing to the frame rate, audio should stay untouched, no?
It is. The message means that the speed of source (media) and destination (refresh rate) are aligned to a speed "around" 24fps.
The real audio clock rate is visible ... at "audio clock".

[csundbom]

It is. The message means that the speed of source (media) and destination (refresh rate) are aligned to a speed "around" 24fps.
The real audio clock rate is visible ... at "audio clock".

Ok, thanks for the confirmation. You should change the message though, very confusing.

[ashlar]

Ask Blight. Certainly not from ReClock.Hmmm... I'll double check tonight, but I'm pretty sure that if I use the standard audio renderer the fps do not change between listed and actual. I might be wrong.

[ashlar]

Hmmm... I'll double check tonight, but I'm pretty sure that if I use the standard audio renderer the fps do not change between listed and actual. I might be wrong.Exactly, ZP6 reports actual fps at 23.970 when Reclock is not in use. Something bust be going on, because if I use Reclock the actual fps always goes to 24.000

[Mark_A_W]

The whole Cinema = 24fps, Audio Resampled at 48048hz has always driven me nuts!!

I asked Blight about it and never got a decent answer.


I would have thought that it should stay at Source = 23.976fps, Audio Resampled at 48000hz for 23.976fps material, as lets face it, the materials is 23.976fps now.


So does it really matter if I run a 95.904hz or 96.000hz refresh rate?

Which should I aim for?

It certainly seems smooth with 95.904hz (if I use VRM9 Windowless instead of Haali Renderer on XP).

Mark

[James]

The whole Cinema = 24fps, Audio Resampled at 48048hz has always driven me nuts!!

I asked Blight about it and never got a decent answer.


I would have thought that it should stay at Source = 23.976fps, Audio Resampled at 48000hz for 23.976fps material, as lets face it, the materials is 23.976fps now.


So does it really matter if I run a 95.904hz or 96.000hz refresh rate?

Which should I aim for?

It certainly seems smooth with 95.904hz (if I use VRM9 Windowless instead of Haali Renderer on XP).

Mark
It doesn't matter, ReClock takes care of it. (Unless you feed SPDIF into ReClock, that is).

[Mark_A_W]

James, to my way of thinking, we should aim for Reclock to do as little resampling as possible.

Does aiming for either 96.000 or 95.904hz help this?

Or once it's in the "good enough" range, it's resampling anyway and it doesn't matter?

[Mark_A_W]

Ahh, answered my own question.

The Audio Clock reading is 48003 or 47997 most of the time, despite the text saying "Audio Resampled at 48048hz".

It's just text.


Edit: Well, almost just text. The Audio Correction readout says -50 or so hz. So it is calculating based on 48048, at least in some way.

[Momber]

very confusing.
I find this very confusing as well. Always have - even before Slysoft took over ReClock ;)

[Jong]

The reason I believe is this.

Reclock was original written before the widespread use of TVs as PC monitors. It was written with PC monitors in mind and these usually use "whole number" refresh rates.

So, in Reclock's mind it is adapting 23.976fps to 24fps for display on a 48Hz (or 72Hz) monitor. However, because it is also capable of adapting to any deviance from the desired target rate, when the actual rate is 47.952Hz it alters everything back - video goes to 47.952fps, audio to 48Khz.

It kinda makes sense, historically. But I agree when the product is otherwise finished it would be good to rewrite this text to bring it up to date. I also hope there is no degradation caused by all this (rounding errors etc.). I have not noticed any, but it would be nice to be reassured!

[James]

It kinda makes sense, historically. But I agree when the product is otherwise finished it would be good to rewrite this text to bring it up to date. I also hope there is no degradation caused by all this (rounding errors etc.). I have not noticed any, but it would be nice to be reassured!

Of course not.

[Jong]

Well that is sure good to hear, and what I thought, although not being in your privileged position I would not say it was that unquestionably obvious.

[ashlar]

Of course not.Would you agree that there is a need for clearer explanations of all these aspects in the documentation?
Reclock is an application that tends to do things "by magic" looking at it from the "outside".