I have enabled "Log Timestamps" in the settings menu, but no timestamp file is produced when saving the project. Indexing, demuxing and Info Log work though, but no *.timestamps.txt is produced. Am I missing something? My source is an .mp4 with VFR. Thanks. Edit: Same problem with .mkv. Timestamps c...

Source is AVC video with AC3 audio muxed in .m2ts container. DGindexNV shows the tracks in its Demux menu, but whichever track(s) I select there, the audio gets ALWAYS demuxed but the video gets NEVER demuxed. I think this is a bug, or do I miss something? Edit: Uuupps! Sorry. Your slipstream update...

It would actually be demuxing and possibly involve decoding i.e. outputting the left and right eye streams. Or perhaps just the independent AVC stream of the stereoscopic mkv. Now I can't load such a mkv file in DGIndexNV e.g. for quick analysis or inspection. I can't however tell whether this would...

admin wrote: ↑

Fri Mar 09, 2018 6:32 am

It shouldn't matter for the results but it can be faster to crop before as there is less video to deal with.

Aren't there some restrictions due to chroma for YV12 (4:2:0), like cropping or picture resolution should be mod2 or mod4?

Great work!
Any plans to include the demuxing of stereoscopic .mkv files?

A cosmetic issue with DGDenoise:

When I set strength=0.0 I am getting an almost black picture for chroma=false, and a green picture for chroma=true.
Well, one should not set strength to zero, right?

Just a huge THANK YOU Donald for your ongoing development of DGDecNV and for keeping the forum alive!

Greetings
Sharc

Eventually coming back to the original question, it seems that the usual method for 25p -> 29.97i conversion (hard-telecining) is simply

Hi Donald
Congratulations for the finalization and acceptance of your paper!

Any plans already about resuming your video/CUDA activities?

No. It is NOT a spec. As the title says, it is just a White Paper (a tutorial if you like). That makes a huge difference.
I don't have access to the Blu-Ray spec. but I think to remember that it is a document of more than 1000 pages.

Finally (!) I found the document which made me believe that not all Blu-Ray players support 25 fps ("PAL"), and converting 25 to 29.97 ("NTSC") might still be advisable to be on the safe side, even in the global Blu-Ray age. Search for example for "50Hz" in the document here (e.g. Para. 3.3.1, 3.3.2...

Doing some more research, I am not really convinced that 25/50fps support for Blu-ray is "mandatory in PAL regions only". It seems to be a quote from the "Blu-ray Demystified" book only, which is NOT a standard. But nevertheless, I would also recommended to avoid 'NTSC editions' of converted 25 fps ...

Unless you have to target DVD-Video as your output format, I don't think there's any reason to do any of this anymore. HDTVs support all framerates regardless of region, so if you have a Blu-ray player, you can just leave the video as 25 fps and burn it to a DVD-R in a MP4 or MKV container and play...

Hard-telecine 6/5 was exactly my concern. I'll run an encode and report back how it behaves .... Edit: Here some results: PC: The 12/10 telecined stream can be perfectly IVTCed with script+PC, as expected. Audio adjustment is minimum 24.75/25=0.99 (1% slowdown only, same as mentioned by Aleron Ives ...

Shouldn't this be Video = SelectEvery (Video, 8, 0,1, 2,3,2, 5,4 , 7,6,7) in order not to break the Top-Bottom sequence? Seems you are correct. Well spotted! This is giving a ratio of 10 output fields per 8 input fields. That converts 25 to 31.25. Why wouldn't they use a correct ratio such as 12 pe...

Yes, I am familiar with the usual film-to-PAL (24 => 25) DVD speedup and pitch shift issues. (The speedup can be a godsend for certain movies, when it's a relief to finish watching a couple of minutes earlier...... ;) ) . Pitch shift can be an annoyance though with concert DVDs, especially for the f...

I tried the frame repeats option as well to minimize audio pitch shift. Although the judder is less for 6/5 (24.975=>29.97) than it would be for 5/4 (23.976=>29.97) it's still noticable for "PAL spoiled viewers" when playing it at 29.97. Possibly some smart HW players/TVs can restore the progressive...

I will take the slowdown route, no problem. Good to know that there is no simpler or better way of doing it.
And it would definitely not make much sense to put efforts in a new tool which hardly anyone would use.

Converting 24 (23.976)fps film to 30 (29.97)fps NTSC is normally done with soft or hard-telecining 3:2 pulldown. Is there a similar (standardized) conversion process (pulldown pattern) for 25 => 29.97fps? Or would one normally slowdown the 25p to 24p and apply standard 3:2 telecine (+stretch the aud...

Ah I see, very clear. We can't take the total frame number out of the equation. Thank you.

Thanks! I came to the exactly same conclusion with my experiments, but I thought I might have missed something. So there is no "direct route" for IVTCing this by field matching plus m by n decimation to hit the 25.00fps Actually, it is not a real problem. I just bumped across it when I converted a 2...

Here is a sample (sorry for the confusion, I meant a 25 => 29.97 telecined source, not 59.94)
http://www.mediafire.com/file/by4ykayn2dmotwx/ma_30i.ts

Seems like I have a blackout, but how can I IVTC a 59.94 telecined 25fps source using DGTelecide() and DGDecimate() such as to get the 25.00 fps progressive source back?
(I think the 59.94 telecined material is 3:2:3:2:2 telecined)

Yep, I confirm it's fixed.
(DGIndexNV I mean, I don't know about your window ......)

Ah, that's interesting. I am on 32 bit version! Thanks for your testing.

@Donald
No rush with fixing. Just finalize your paper first!