Extremely slow seek in videos. Takes +3 minutes

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start a video
2. Press triangle
3. Choose Go To or Scene
4. Pick any time

What is the expected output? What do you see instead?
Just a black screen for a long time (about 3 minutes for a simple xvid-file).

What version of the product are you using? On what operating system?
1.03 Ubuntu Linux x64

If you are transcoding a media file, which engine are you using (mencoder,
avisynth/mencoder, tsmuxer?)
mencoder

Original issue reported on code.google.com by patrik.d...@gmail.com on 19 Jan 2009 at 8:50

[GoogleCodeExporter]

what's your mencoder build number/version ?
debug.log could help also

Original comment by ps3mediaserver@gmail.com on 19 Jan 2009 at 10:22

[GoogleCodeExporter]

same here, version 1.03 on Windows 7 / XP (32-bit), using Core2Duo w/ 2GB RAM.

seeking takes A LONG time (if not freezing completely) on 720p movies at least. 

MenCoder:
MEncoder Sherpya-SVN-r28126-4.2.5 (C) 2000-2008 MPlayer Team
CPU: Intel(R) Core(TM)2 CPU          6700  @ 2.66GHz (Family: 6, Model: 15, 
Stepping: 6)
CPUflags: Type: 6 MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.

Original comment by hyperspa...@gmail.com on 20 Jan 2009 at 10:14

[GoogleCodeExporter]

does it happens with every movie ?

Original comment by ps3mediaserver@gmail.com on 21 Jan 2009 at 6:06

[GoogleCodeExporter]

At least with 720p movies, yes, and only when using the search function (square 
button).
When stopping an 720p movie while playing and then pressing play again, it 
resumes 
from the point that it was stopped just fine.

Original comment by hyperspa...@gmail.com on 21 Jan 2009 at 7:06

[GoogleCodeExporter]

Maybe you should explain in the FAQ how transcoding in PMS works and explain why
people will experience problems with "fast forward", "jumping" and "search". 
People
seems to think that you easily can transcode X different parts of a movie at 
the time.

I have always assumed that transcoding with mencoder is something that always 
starts
at the beginning of the film and is then done sequential to the end of the 
film. So
if you want to jump to 5:00 in a movie PMS still have to transcode 0:00 - 4:59 
first.
I could be wrong but I would like to know how you do it either way.

Original comment by topg...@gmail.com on 22 Jan 2009 at 12:49

[GoogleCodeExporter]

no, pms seeks as well in the movie and send a new mpeg stream with fake 
timestamps... 
fast fwd/rwd/seek_in_time is working fine here (not as fast as a streamed file 
though)

but AGAIN !, no debug.log = no solution (I'm no magician)

Original comment by ps3mediaserver@gmail.com on 22 Jan 2009 at 1:29

[GoogleCodeExporter]

OK, I am attaching the debug.log file in compressed rar format.

Here's my test methodology:
1. Played an mkv video
2. Press square to search, selected a minute e.g. 25th minute.
3. A network error appeared, but the video did jump to the location specified 
almost 
instantly
4. Pressed square again, selected different minute
4. Network error again, this time video took 1-2 minutes to jump.

Original comment by hyperspa...@gmail.com on 22 Jan 2009 at 4:06

Attachments:

• debug.rar

[GoogleCodeExporter]

Here's another debug file. I think I have located the source of the problem.
This time I used 2 fixed time frames to perform the search test, not random. 
Specifically I used the 27th and the 31th minute on the SAME video file.

EVERY time, jumping to the 31th minute was OK. In a couple of seconds I had 
correct 
video.
EVERY time, jumping to the 27th minute the video took 2~3 minutes to load.

Something happens when you feed that specific frame (on 27th minute) to 
mencoder. 
The safest bet would be do a forward search and jump to the next available I 
frame 
(keyframe), otherwise (B or P frames) it will require previous data frames.

IN ALL CASES, after selecting a minute to jump to, a "Network Error" message 
was 
displayed.

Original comment by hyperspa...@gmail.com on 22 Jan 2009 at 4:25

Attachments:

• debug.rar

[GoogleCodeExporter]

correction: 2~3 minutes is an understatement: most of the times it plays the 
file 
back from the beginning!

Original comment by hyperspa...@gmail.com on 22 Jan 2009 at 4:32

[GoogleCodeExporter]

Issue 210 has been merged into this issue.

Original comment by ps3mediaserver@gmail.com on 23 Jan 2009 at 11:52

[GoogleCodeExporter]

have you enabled the "A/V sync alternative method" ?

Original comment by ps3mediaserver@gmail.com on 23 Jan 2009 at 11:54

[GoogleCodeExporter]

this option is enabled by default. Yes. it's enabled on all my tests.

Original comment by hyperspa...@gmail.com on 23 Jan 2009 at 4:43

[GoogleCodeExporter]

Sorry for delaying with more information. I haven't had time to reproduce the 
problem
or add additional info. Here's the MEncoder build version:

MEncoder 2:1.0~rc2-0ubuntu17 (C) 2000-2007 MPlayer Team
CPU: Intel(R) Core(TM)2 Duo CPU     T8300  @ 2.40GHz (Family: 6, Model: 23, 
Stepping: 6)
CPUflags: Type: 6 MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.

Your question about A/V sync alternative method: I have disabled this because in
every movie I have tried the audio is out of sync about half a second when 15 
minutes
in the movie. I try to keep the encoder options as simple as possible. It does
however not make any difference if enabled or disabled.

If I try to play the same videos from a ReadyNAS dedicated DLNA server, jump 
works
every time. MEncoder works perfectly in MPlayer.

I'll try to post a debug file when I have made some more tests. Probably this 
weekend.

Original comment by patrik.d...@gmail.com on 2 Feb 2009 at 7:34

[GoogleCodeExporter]

No Solution?

Original comment by jennifer...@gmail.com on 24 Apr 2011 at 3:44

[GoogleCodeExporter]

Also experience this problem running Windows XP. PMS 1.50 b2

Original comment by m...@codycook.us on 14 Nov 2011 at 5:40

[GoogleCodeExporter]

Has this issue been solved?

Original comment by lenni...@googlemail.com on 14 Oct 2012 at 1:32