I have an h.264 file created with the TI DM365 chip. When I play it in VLC, it seeks to the end of the file very quickly. However, when I package it into an mp4, even without audio, the seek to the end of a 40 minute file takes around 4 minutes. I tried using the :forcesync option, but I suspect that was intended for other cases.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a small (approx 1.3MB sample) I can email you. My email is wlmyers at aol.com. I'll send the h264 in reply. Or I can post somewhere else for your convenience. Thanks.
Bill
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We've received the files and understood the problem. We'll let you know when we patch it. Please note you will need the latest VLC (2.0.2) to read it correctly once fixed.
Just for our information, is this a h264 raw from a camera? Did you encode it using a tool?
Romain
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Romain,
This seems like a definite improvement, but the seek still seems to take about 1.25 minutes to seek toward the end of our 40 minute file (it used to take almost 4 minutes). Here's some more information: I can generate an mp4 with ffmpeg that seeks very quickly, but takes 10 minutes to create. Is there some option that I need to set with mp4box to make the seek faster? What settings did you use on the h264 file that I posted?
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have an h.264 file created with the TI DM365 chip. When I play it in VLC, it seeks to the end of the file very quickly. However, when I package it into an mp4, even without audio, the seek to the end of a 40 minute file takes around 4 minutes. I tried using the :forcesync option, but I suspect that was intended for other cases.
Hi,
I have the feeling your h264 is encoded with open GOPs, am I right? Could you try to use the ":forcesync" flag and tell if it's better?
Romain
@rbouqueau - Yes, I tried using :forcesync, but didn't see a difference in the seek time. Here's my command line:
c:\development\idvrconvert\idvrconvert\bin\Release>mp4box.exe -import "C:\development\vnl01122012-155043.h264":forcesync "C:\development\vnl01122012-155043.mp4"
Is there a possibility for you to share a sample? (Send a PM if you can't share it publicly).
Romain
I have a small (approx 1.3MB sample) I can email you. My email is wlmyers at aol.com. I'll send the h264 in reply. Or I can post somewhere else for your convenience. Thanks.
Bill
Hi Bill,
We've received the files and understood the problem. We'll let you know when we patch it. Please note you will need the latest VLC (2.0.2) to read it correctly once fixed.
Just for our information, is this a h264 raw from a camera? Did you encode it using a tool?
Romain
Now fixed on SVN, thanks for the sample
That's awesome. When will there be a windows build with this patch included?
http://gpac.wp.mines-telecom.fr/downloads/gpac-nightly-builds/#Windows 32 bits
starting at rev 4095
Romain
Romain,
This seems like a definite improvement, but the seek still seems to take about 1.25 minutes to seek toward the end of our 40 minute file (it used to take almost 4 minutes). Here's some more information: I can generate an mp4 with ffmpeg that seeks very quickly, but takes 10 minutes to create. Is there some option that I need to set with mp4box to make the seek faster? What settings did you use on the h264 file that I posted?
Thanks.
Bill,
Which player do you use? The GPAC player (osmo4) and VLC 2.0.2 both seek instantaneously.
My CL: mp4box -add vnl01122012-155043.h264:forcesync -new tmp.mp4
Romain
Got it. Forgot the :forcesync. Works beautifully. Thanks, guys!