Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vobsubs don't display correctly when using Libav #12

Closed
kax4 opened this issue Jan 7, 2013 · 8 comments
Closed

Vobsubs don't display correctly when using Libav #12

kax4 opened this issue Jan 7, 2013 · 8 comments

Comments

@kax4
Copy link
Contributor

kax4 commented Jan 7, 2013

mpv not show bluray sub:
mplayer2: http://www.mediafire.com/view/?wcj66id7vj0pmp6
mpv: http://www.mediafire.com/view/?drhvu9saiw2iuzw
Ugly dvd sub:
mplayer2: http://www.mediafire.com/view/?01agh3vwuor43co
mpv: http://www.mediafire.com/view/?du1vkgbbd64zkbi

@ghost
Copy link

ghost commented Jan 7, 2013

None of these mediafire links work. I think they're specific to your mediafire login and won't work for anyone else.

@ghost
Copy link

ghost commented Jan 7, 2013

Vobsubs in mkv work for me. What ffmpeg/Libav versions are you using? (This matters a lot, because mpv uses ffmpeg's vobsub decoder, while mplayer2 does not.)

@ghost
Copy link

ghost commented Jan 7, 2013

I actually tried with Libav: yep, it's broken there.

Please use ffmpeg instead. ffmpeg contains tons of bug fixes and especially subtitle related feature additions.

Will keep this open until Libav fix their vobsub decoder.

@kax4
Copy link
Contributor Author

kax4 commented Jan 7, 2013

Im using Libav 9, test with ffmpeg 1.1 seem fine.

@ghost
Copy link

ghost commented Jan 7, 2013

@ghost
Copy link

ghost commented Jan 17, 2013

Libav finally merged the relevant 2 ffmpeg commits to support vobsubs correctly. I haven't tested whether it works correctly, though.

I'll close this as soon as there's a Libav release which contains these commits.

@ghost
Copy link

ghost commented Jan 19, 2013

Correction: Libav pushed one of the required commits to fix this just now (3 days later).

@ghost
Copy link

ghost commented Jan 24, 2013

I hoped Libav would fix this quickly, but I think they'll take a while to make a new minor release etc.

Fixed this with a crappy hack 64b0395 by falling back to the old internal decoder if Libav is detected.

@ghost ghost closed this as completed Jan 24, 2013
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant