Handbrake: VOB to MKV - Framerate cut in half

[Track]

Okay, so I'm trying to convert a VOB file to an MKV using Handbrake.

There are two big problems:

1.) The output file has a ridiculous amount of interlacing which the source did not - I've managed to fix this by deinterlacing, but I'm not sure what caused it in the first place.

2.) The framerate is always 25fps, even though I choose "same as source", and even when I choose 50, it still feels like 25fps.

Appreciate the help,

Chris

[poisondeathray]

When you say "feels like 25fps" => that implies the motion is choppy. This suggests the original was interlaced

Is the VOB maybe encrypted ? did you decrypt it ?

Are you sure it's not interlaced? Maybe posting a sample will help . You can cut a representative segment with motion with dgindex or mpg2cut2

You need the nightly builds of handbrake to "bob" deinterlace, unless something has changed recently . Bob deinterlacing preserves both fields, preserving the motion (a 50i file would become 50p, each frame representing a moment in time). Single rate deinterlacing throws away 1/2 the fields (a 50i file would become 25p; and selecting 50p will only duplicate the frames - effectively motion will be choppy and really still 25p because frames are repeated)

[Baldrick]

1. Software players deinterlaces interlaced dvds/vobs.
2. 25fps is normal for dvds....they are not in 50fps.

[mail2tom]

If all that's desired is to go from VOB to MKV why not just take the VOB and add it to MKVMerge and output a Matroska file?

[johns0]

Most people using handbrake to convert dvd to mkv do it to reduce file size with minimal loss in quality,adding a vob to mkvmerge defeats that purpose.

[Track]

1. Software players deinterlaces interlaced dvds/vobs.

I'm using Media Player Classic and it's definitely utilizing my GTX 660, so I don't know if you could call it a software player.



So, you guys are saying that the VOB is 50fps but, in fact, interlaced so it's actually 50i which is the same as 25p?

But then how come it seems to run as smoothly as a 50p video?

I basically want to convert it to an MKV with the same resolution and framerate.

You need the nightly builds of handbrake to "bob" deinterlace, unless something has changed recently . Bob deinterlacing preserves both fields, preserving the motion (a 50i file would become 50p, each frame representing a moment in time). Single rate deinterlacing throws away 1/2 the fields (a 50i file would become 25p; and selecting 50p will only duplicate the frames - effectively motion will be choppy and really still 25p because frames are repeated)

Yes, that's exactly what is happening.

Why is Bob only on the nightly builds? Alright, I'll try it.

I won't have access to the files until tomorrow but I'll upload a sample if I have further trouble.

[johns0]

The file is 25i,not 50i,there are 25 frames with each one having 2 fields.Read more about dvd interlacing and frame rates.

[poisondeathray]

50i and 25i are actually the same thing , just different naming conventions .

They both mean 50 fields per second. Fields are like half-frames. With true interlaced content, each field represents a different moment in time. When a bob deinterlace is applied, it becomes 50p, each frame representing a different moment in time

[johns0]

What i meant was 25fps interlaced for 25i,his dvd isn't 50fps which the op was getting confused about.

[Track]

Read more about dvd interlacing and frame rates.

I didn't come on this forum to read.




I don't understand. The file is clearly running at a rate of 50fps - the smoothness is undeniable. So, I figured 50i = 25p.

Now you're telling me that 25i = 50i? But 25p and 50p are a world's apart and the difference in viewing between 25i and 50i and 25p and 50p is identical - the latter always seems way way more smooth.

[poisondeathray]

I don't understand. The file is clearly running at a rate of 50fps - the smoothness is undeniable. So, I figured 50i = 25p.

Now you're telling me that 25i = 50i? But 25p and 50p are a world's apart and the difference in viewing between 25i and 50i and 25p and 50p is identical - the latter always seems way way more smooth.

25i and 50i are the same thing, different naming conventions as explained above

25p and 50p are different, as the name indicates 25 progressive frames/sec , and 50 progressive frames/s

When you watch an interlaced DVD in a DVD player or DVD playing software , it gets bob deinterlaced to 50p, that's why it looks so "smooth". Essentially, each field becomes a frame . With handbrake, it's getting single rate deinterlaced to 25p. Even if you select 50p, it will just double the 25p frames (50p with duplicates) . The only way in handbrake to bob deinterlace (at least in the past) was to use the nightly builds. Or you can use other GUI's like megui, ripbot, xvid4psp - they all offer different deinterlacing options

50p is incompatible with DVD-Video (only blu-ray at 720p50) , so interlaced PAL DVD only comes as 50i (or 25i, same thing)

[poisondeathray]

It looks like they added it to the main branch in handbrake

from the changelog HandBrake 0.9.9:

Double framerate ("bob") mode for the deinterlace and decomb filters

[manono]

I didn't come on this forum to read.

Maybe you should read a little bit so you don't look so foolish. Where's the sample that was requested? 10 seconds with steady movement will be plenty. Until we see that we can only guess at what you have since, apparently, you don't have a clue.

[Track]

25i and 50i are the same thing, different naming conventions as explained above

Everything you said was very enlightening, but it occurs to me.. why should 25i and 50i be the same thing?

It would make more sense for 50i = 25p and 25i = 12.5p or 12.5fps.

I didn't come on this forum to read.

Maybe you should read a little bit so you don't look so foolish.

Looks aren't everything.

Where's the sample that was requested?

I already explained that.

Until we see that we can only guess at what you have since, apparently, you don't have a clue.

Now just imagine a doctor saying that to a patient. If you laugh as hard as I did, I'll respect you more.

[poisondeathray]

Everything you said was very enlightening, but it occurs to me.. why should 25i and 50i be the same thing?

It would make more sense for 50i = 25p and 25i = 12.5p or 12.5fps.

It used to be called 25i exclusively . I think some marketing guy woke up one day and thought of how to sell more conusmer camcorders. 50i sounds like a bigger number than 25i. Both naming conventions are now commonly used in literature, software . I would say "50i" (60i in NTSC regions) is the more common naming format now

[Track]

Everything you said was very enlightening, but it occurs to me.. why should 25i and 50i be the same thing?

It would make more sense for 50i = 25p and 25i = 12.5p or 12.5fps.

It used to be called 25i exclusively . I think some marketing guy woke up one day and thought of how to sell more conusmer camcorders. 50i sounds like a bigger number than 25i. Both naming conventions are now commonly used in literature, software . I would say "50i" (60i in NTSC regions) is the more common naming format now

But then why isn't there an actual 50i - as in, a framerate double that of 25i?

[poisondeathray]

It used to be called 25i exclusively . I think some marketing guy woke up one day and thought of how to sell more conusmer camcorders. 50i sounds like a bigger number than 25i. Both naming conventions are now commonly used in literature, software . I would say "50i" (60i in NTSC regions) is the more common naming format now

But then why isn't there an actual 50i - as in, a framerate double that of 25i?

Because a 50i frame rate (using frame rate now, not field rate naming convention) would mean a field rate of 100. That' s not common because "PAL" areas are 50Hz , "NTSC" areas are 60Hz . Those are common broadcast setups . It would take a lot of $$ and revamping infrastructure to make 100 fields per second the standard (or 120 fields per second in NTSC land)

Interlaced formats are going to be gone in the (far) future anyway . Direct interlaced encoding is not even included in HEVC for example . More and more content use web delivery (progressive only)

[manono]

I didn't come on this forum to read.

Maybe you should read a little bit so you don't look so foolish.

Looks aren't everything.

Everything you said was very enlightening, but it occurs to me.. why should 25i and 50i be the same thing?
It would make more sense for 50i = 25p and 25i = 12.5p or 12.5fps.

I rest my case.

[Track]

Because a 50i frame rate (using frame rate now, not field rate naming convention) would mean a field rate of 100.
Interlaced formats are going to be gone in the (far) future anyway . Direct interlaced encoding is not even included in HEVC for example . More and more content use web delivery (progressive only)

Yes, of course. Interlaced is linked directly to analog technology, so it will eventually die out.

So, basically, there is no such thing as 50i and the simple answer is that it's been a marketing lie for decades?

But if it's really running at 25fps, why does it feel as smooth as 50fps? MPC can't make a video twice as smooth just during playback..

I rest my case.

You've already rested your case that I look foolish, Manono.

And I ruled in favor of myself because I don't mind looking foolish.

[Track]

I tried using the Bob deinterlacing option, but the resulting file is still 25p, not 50p.

[hello_hello]

You might need to specify 50fps (or same as source) along with bob de-interlacing to output 50p (I'm not a handbrake user so I'm not sure).

But if it's really running at 25fps, why does it feel as smooth as 50fps? MPC can't make a video twice as smooth just during playback

If the video is being de-interlaced to 50p on playback, then it'll look pretty smooth. A lot smoother than if it's being de-interlaced to 25p.