x265 Conversion with RipBot?

[tommy2010]

Hi Everyone,

I'm having an issue with HEVC encodes with RipBot and stuck on finding a solution. For starters I get an error by choosing a tuning method but eventually found a thread saying that tuning is not supported with x265. However, my main problem is with the frame rate. Whenever I do a x265 encode the resulting video always shows "no frame rate found" in TsMuxer. Consequently, if I mux a blu-ray structure with audio the resulting video output pauses for a split second every few seconds and the audio is greatly out of sync.

I had an issue like this before with a source but when I forced fps by telling RipBot "Assume --> 23.976" under the change speed setting the resulting encode showed that it has a 23.976 fps in TsMuxer and consequently the playback was fixed after muxing but in that case the file was encoded with x264 and not x265.

I'm confident that this lack of the fps flag is the source of the problem but I'm not knowledgeable enough to put it back in. Is this even possible or it's a possible bug that needs to be addressed withing Ripbot? Again, I never had an issue with the fps when encoding x264 with Ripbot only now when attempting to do x265 encodes.

Would appreciate some help in this matter.

Thank you.

EDIT: In RipBot's Avisynth edit window I tried including ChangeFPS(23.976) but unfortunately TsMuxer still tells me "frame rate not found". On another thread that I read it suggested that fps header information might be getting lost before the encoded video stream is put into a container by RipBot.

[LigH.de]

A raw HEVC video stream outside any container possibly has no header field storing the frame rate (I am not sure under which circumstances, but there are some which have none). If it also contains no SEI data with the encoder parameters (--no-info), there is hardly any way to guess it.

A converter producing an intermediate raw HEVC video would have to remember the frame rate to explicitly tell it to the multiplexer to have it stored in the container's header.

The author of RipBot264, Atak_Snajpera, can be found in the doom9 forum; I will tell about this question there..


BTW: Don't confuse "AssumeFPS" with "ChangeFPS"; the first only sets an attribute, the other changes the video content by e.g. dropping or duplicating frames, or blending them. You may not want the latter.


P.S.: Using x265 v2.9+1 without RipBot264, just directly in a batch, MediaInfo can detect a frame rate even when I use the option "--no-info". So it may have other reasons that your results lack it...

[tommy2010]

LigH.de,

Thank you for re posting my question in the doom9 forum so the author of RipBot could see.

A converter producing an intermediate raw HEVC video would have to remember the frame rate to explicitly tell it to the multiplexer to have it stored in the container's header.

Yes that makes sense but then something happens after the video stream has been put inside the container. I just don't understand why TsMuxer doesn't take the FPS info from the HEVC stream when MediaInfo sees this info no problem. Also, from what I can tell MeGUI gives a choice of Raw HEVC output which could be a solution but I still would rather use RipBot because of its Distributed Encoding feature.

BTW: Don't confuse "AssumeFPS" with "ChangeFPS"; the first only sets an attribute, the other changes the video content by e.g. dropping or duplicating frames, or blending them. You may not want the latter.

I tried "AssumeFPS" first which is directly accessible through RioBot GUI but when that didn't work "ChangeFPS" made sense to include in the AviSynth edit window based on doc which said "When you want to change FPS but don't want frame blending". Thought that maybe it would force FPS info if kept the same as source FPS but no such luck. Anyways, thanks for clarifying.

Thanks again and for your response.