Log in

View Full Version : Can't fast-forward (no timeline) after remuxing mkv to m2ts


olikl
30th June 2008, 15:23
Hi,
I have some .mkv files that I muxed from .h264 and .ac3 streams. They are all 1920x1080p, 25fps.
I can play all of them on the PC without having any problems. After using M2ts merge to remux the .mkv to .m2ts for PS3 playback, I can't fast-forward SOME of them. All files are from the same source (Sky HD) and I do not understand why I can just fast-forward a few of them. Muxing directly to .m2ts does not solve this either.
Neither my PC nor my PS3 can fast-forward them, they do not even show a timeline at the bottom.
What can I do to make this work? My guess is that I have modify the .h264 in some way. But how?

Thanks!
Oliver

Atak_Snajpera
30th June 2008, 17:51
Try again but uncheck Continually insert SPS/PPS in TsMuxer

olikl
30th June 2008, 21:51
Try again but uncheck Continually insert SPS/PPS in TsMuxer

Hi,
thanks for your help, but this did not work for me. Any other suggestions?

Thanks!

survivant001
2nd July 2008, 13:05
I have a similar problem with the PS3.. I have to wait 30-120 sec before the ff and rw start. It's only doing that with m2ts

Staz
8th August 2008, 05:31
Did anyone find a solution to this problem? Waiting over one minute before ff starts is very annoying.
I use tsmuxer with the following settings:

MUXOPT --no-pcr-on-video-pid --new-audio-pes --vbr --vbv-len=500
V_MPEG4/ISO/AVC, "video.h264", insertSEI
A_AC3, "audio.ac3"

Cheers

survivant001
8th August 2008, 12:49
YEp.. take your output from tsmuxer (000001.m2ts) and mux it again in tsmuxer. it fixed my problem.. I know.. there a bug somewhere.. but that,s a good workaround for me.

Staz
8th August 2008, 12:52
Interesting fix :)

Which settings did you use in tsmuxer? ('add picture timing info' and 'continually insert SPS/PPS')

survivant001
8th August 2008, 15:30
all the settings are the default (all ON)

G_M_C
8th August 2008, 15:45
all the settings are the default (all ON)

I've tried ticking ON "change framerate", without actually changing it (forcing tsMuxeR to write the correct framerate). My versions all fforward/reverse now. Also make shure your original clip is indeed fully compliant with level 4.1 AVC.

survivant001
8th August 2008, 17:33
I'm talking about real 4.1 AVC.. no info264 hack.. I don't care about others settings.. a full 4.1 compliant.

ChuckleWorthy
8th August 2008, 18:19
YEp.. take your output from tsmuxer (000001.m2ts) and mux it again in tsmuxer. it fixed my problem.. I know.. there a bug somewhere.. but that,s a good workaround for me.
Interesting fix. Would you mind posting your tsMuxer 'meta' options for these two steps please?

Staz
9th August 2008, 01:26
I've tried ticking ON "change framerate", without actually changing it (forcing tsMuxeR to write the correct framerate). My versions all fforward/reverse now. Also make shure your original clip is indeed fully compliant with level 4.1 AVC.

G_M_C, you are a legend!

I can now fast forward / rewind at speeds x1.5, x10, x30 and x120 with no problems at all! Seeking forwards and backwards also works brilliantly.

Another thing I should mention: Since I got the latest firmware (2.42) I have never had to change the AVC profile. Can you guys try skipping this step and let me know your results?

Cheers

G_M_C
9th August 2008, 09:06
G_M_C, you are a legend!

I can now fast forward / rewind at speeds x1.5, x10, x30 and x120 with no problems at all! Seeking forwards and backwards also works brilliantly.

Another thing I should mention: Since I got the latest firmware (2.42) I have never had to change the AVC profile. Can you guys try skipping this step and let me know your results?

Cheers

Thought so, i didn't set the framerate-switch at first too. tsMuxeR then takes the fps from the stream. That should work fine, but i also noticed that i couldn't fforward/reverse too. I also noted the the video didnt seem to play fluently sometimes.

All was well when i simply forced the correct framerate with he "Change fps" -switch (without actually changing the setting, cause tsMuxeR DOES know the correct framerate). Might be a bug there, but i think tsMuxeR isn't maintained anymore :(

But it is a muxer-problem and not really mpeg4-AVC related. Maybe a mod can move this thread to the correct part of the forum ?