--pulldown and --qpfile with X264

[jdobbs]

I'm doing some encoding that converts 720x480@29.97fps to 1280x720p (for output to Blu-ray). Since the BD standard doesn't allow 720p at 29.97 it has to be converted to 59.94fps.

In the past I've doubled the frames using AVISYNTH. But recently decided it would be better to simply set "--pulldown double" instead. So here's my question: Since I'm using pulldown to double the framecount -- what frame values should I use in the file I am using with "--qpfile" for chapter points? Do I use the frame number of the input (at 29.97fps) or the output (doubled via pulldown to 59.94fps)?

Any help would be appreciated.

[nixo]

Can't answer your question, I'm afraid, but just thought I would mention that TSMuxer supposedly doesn't like any of the pulldown options:
http://www.x264bluray.com/issues-with-certain-players

--
Nikolaj

[jdobbs]

Can't answer your question, I'm afraid, but just thought I would mention that TSmuxer supposedly doesn't like any of the pulldown options:
http://www.x264bluray.com/issues-with-certain-players

--
NikolajInteresting... I've done several of these using "--pulldown double" to get to 59.94fps and and then muxed them with TSMuxer. They play fine in PowerDVD 11 and also on my standalone.

I have had trouble in the past trying to use "--pulldown 32" with TSMuxer to get from 23.976fps to 29.97fps. It didn't play back well.

[Guest]

Can't you answer the question with a simple test?

[jdobbs]

Hmmm... now that you mention it, I guess I could scan with DGIndexNV and check the DGI file to see where the I frames are inserted.

[jdobbs]

Ok. Having tested it with DGIndexNV now -- the answer is: As you would logically think, the qpfile references the input frame number...

[Edit] And in case anyone is interested, if you use the "--seek" parameter in your X264 command line the --qpfile specified frame number also remains consistent with the input frame number, not the output.

[MasterNobody]

jdobbs
Note: x264's "--pulldown double" option doesn't really change output number, it only signals "frame doubling" pic_struct in picture timing SEIs and thus increase frame display duration. So there is no difference between input and output frame numbers in this case. And yes, in most (all?) cases in options user specify only input frames numbers.

[jdobbs]

jdobbs
Note: x264's "--pulldown double" option doesn't really change output number, it only signals "frame doubling" pic_struct in picture timing SEIs and thus increase frame display duration. So there is no difference between input and output frame numbers in this case. And yes, in most (all?) cases in options user specify only input frames numbers. Yeah, I knew it wouldn't change the actual frame count, only flags... but wasn't sure about how it was calculated. I just wanted to make sure the files I'm creating for chapters are correct when I assert frame-doubling.

Thanks.

[Sharc]

Interesting... I've done several of these using "--pulldown double" to get to 59.94fps and and then muxed them with TSMuxer. They play fine in PowerDVD 11 and also on my standalone.

Hmm... no luck here with --pulldown double for 25 to 50fps conversion and muxing with tsMuxer. It only works for --bframes 0. Jerky playback otherwise on standalone and SW player.

[jdobbs]

Hmm... no luck here with --pulldown double for 25 to 50fps conversion and muxing with tsMuxer. It only works for --bframes 0. Jerky playback otherwise on standalone and SW player.Really... maybe I should rethink adding it as an option to BD-RB.

[jpsdr]

For encoding with x264, chapters are from source file. Any idea how it would be for setting chapters in authoring SW like Scenarist ?