MEncoder unsyncs MKV

For help and support with Universal Media Server
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Post Reply
Larkas
Posts: 3
Joined: Sun Apr 20, 2014 7:17 am

MEncoder unsyncs MKV

Post by Larkas »

Hello there, guys. I'm a little frustrated that I can't get MEncoder to sync audio and video properly (and, to a lesser degree, that I can't get VLC to properly render styled subtitles). I've attached the debug file below.

Thing is, every time I try to play this file with the MEncoder, the video speeds up, and by 2:00 the audio is already some 5~10 seconds late. When I use VLC as the encoder, however, audio and video are perfectly in sync, but I can't get the SSA subtitle to display the proper fonts.

So,

1) Is there any way to get MEncoder to sync properly?

2) Failing that, is there any way to get VLC to properly display styled subtitles?
Attachments
ums_dbg.zip
(43.53 KiB) Downloaded 508 times
User avatar
DeFlanko
Posts: 724
Joined: Thu Jun 21, 2012 3:43 am
Location: San Pedro, CA
Contact:

Re: MEncoder unsyncs MKV

Post by DeFlanko »

what does switch your default engine to FFMpeg do?
Larkas
Posts: 3
Joined: Sun Apr 20, 2014 7:17 am

Re: MEncoder unsyncs MKV

Post by Larkas »

DeFlanko wrote:what does switch your default engine to FFMpeg do?
It doesn't work. The PS3 returns the following:

"This content cannot be played.
(800288E1)"
Larkas
Posts: 3
Joined: Sun Apr 20, 2014 7:17 am

Re: MEncoder unsyncs MKV

Post by Larkas »

So, any ideas?
johngcp
Posts: 15
Joined: Mon Sep 22, 2014 9:04 pm

Re: MEncoder unsyncs MKV

Post by johngcp »

You can completely avoid MEncoder by default by also unticking "remux videos with tsmuxer" in the FFmpeg settings. It will mean that all videos will be transcoded though instead of remuxed but it shouldn't be a problem on a fast network.

"This content cannot be played.
(800288E1)"
That's a bug at the moment and unfortunately didn't get it fixed in time for 4.1.2, but hopefully it will be fixed in the release after that.
In the meantime you might want to roll back to 4.0.1 since that didn't have that bug :)

Those are answers I got that might apply to what you're dealing with as well.
Post Reply