After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 173102 - seeking in large files doesn't work
seeking in large files doesn't work
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.8.9
Other Linux
: Normal major
: 0.8.11
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-04-08 18:41 UTC by Simon Morgan
Modified: 2005-10-03 11:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Simon Morgan 2005-04-08 18:41:05 UTC
Version details: 0.8.4-0ubuntu1
Distribution/Version: Ubuntu 5.04

Trying to seek in any file larger than a few minutes doesn't seem to work. I've
tried both AVI and Matroska files encoded using various versions of various
codecs and the long ones (e.g. films) are the ones that refuse to seek.
Comment 1 Ronald Bultje 2005-04-08 18:56:21 UTC
0.8.4 is not recent enough, please retry with latest releases. Seeking works
fine on small and large files here.q
Comment 2 Simon Morgan 2005-04-08 19:14:19 UTC
Sorry, my mistake. I started off filing it as a bug against gstreamer-ffmpeg.
The version i'm using (gstreamer core) is actually 0.8.9.
Comment 3 Ronald Bultje 2005-04-08 20:02:18 UTC
So is this the case for any large file? Any AVI file? Can you provide me with a
sample?
Comment 4 Simon Morgan 2005-04-08 20:19:40 UTC
Simply any large file. Not a single film that I have will seek. If you still
think it's worth downloading one (seeing as none of them work i'm assuming it's
a bug that only I can reproduce) and it doesn't break any rules then i'd be
happy to put one up for download for you.
Comment 5 Ronald Bultje 2005-04-08 20:43:05 UTC
I have large files of 1-and-a-half hour or 700 MB (AVI), and they work fine.
Please put one online, yes.
Comment 6 Ronald Bultje 2005-04-09 07:45:22 UTC
I downloaded the file, and seeking works fine for me. Are the files on a
particular partition? What's the output of "gst-launch file:///dev/null !
fakesink --gst-debug=*:5 --gst-debug-no-color 2>&1 | grep
gst_element_make_from_uri"?

Sebastian, do you have similar problems?
Comment 7 Sebastien Bacher 2005-04-09 10:34:03 UTC
That's works fine with the differents file I've on my disk here.
Comment 8 Simon Morgan 2005-04-09 11:48:52 UTC
simon@bainbridge:~$ gst-launch-0.8 file:///dev/null ! fakesink --gst-debug=*:5
--gst-debug-no-color 2>&1 | grep gst_element_make_from_uri
LOG   (0x50ac30 - 309179:47:59.992416000)         GST_URI( 7295)
gsturi.c(495):gst_element_make_from_uri:<gnomevfssrc0> created source for URL
'file:///dev/null'
Comment 9 Simon Morgan 2005-04-09 11:52:36 UTC
Files on 2 large ReiserFS partitions, 1 ext3 partition and 1 NTFS partition all
exhibit the same problem.
Comment 10 Simon Morgan 2005-04-09 15:18:32 UTC
Just tried with an OGM file and had the same problem. I think it's safe to say
it's not a problem with a specific container format.
Comment 11 Ronald Bultje 2005-04-09 15:55:18 UTC
I'm confused, I don't have a clue what may cause this... Can you set GST_DEBUG
to "*:5" as environment variable and run totem &> /tmp/logfile, try to seek once
in a file and attach the logfile here?
Comment 12 Simon Morgan 2005-04-09 16:07:26 UTC
Sorry I couldn't attach it but it exceeds the maximum file size for attachments.

http://bollo.mine.nu/~simon/totem_gst_debug.log.bz2
Comment 13 Simon Morgan 2005-04-10 20:39:33 UTC
I think i've pinpointed the cause of the bug. With the debug level set to 2 I
noticed that right after I attempted to seek in a file i'd get the following
debug output:

WARN  (0x540100 - 309212:33:15.496833000)            alsa( 2071)
pcm_hw.c(476):snd_pcm_hw_delay: alsalib error: SNDRV_PCM_IOCTL_DELAY failed:
File descriptor in bad state
WARN  (0x540100 - 309212:33:15.589411000)            alsa( 2071)
gstalsa.c(1701):gst_alsa_probe_hw_params:<alsasink0>
"snd_pcm_hw_params_set_period_size_near (this->handle, hw_params, &period_size,
0)": Invalid argument
WARN  (0x540100 - 309212:33:15.659245000)            alsa( 2071)
gstalsa.c(1701):gst_alsa_probe_hw_params:<alsasink0>
"snd_pcm_hw_params_set_period_size_near (this->handle, hw_params, &period_size,
0)": Invalid argument
WARN  (0x540100 - 309212:33:15.729647000)            alsa( 2071)
gstalsa.c(1701):gst_alsa_probe_hw_params:<alsasink0>
"snd_pcm_hw_params_set_period_size_near (this->handle, hw_params, &period_size,
0)": Invalid argument
WARN  (0x540100 - 309212:33:15.799451000)            alsa( 2071)
gstalsa.c(1701):gst_alsa_probe_hw_params:<alsasink0>
"snd_pcm_hw_params_set_period_size_near (this->handle, hw_params, &period_size,
0)": Invalid argument

Changing the default sink to OSS fixes the problem of seeking, but the sound
itself is quite badly out of sync. Anybody got any ideas?
Comment 14 Ronald Bultje 2005-04-11 05:34:44 UTC
I'll have a look at alsasink. It shouldn't do anything with a seek...
Comment 15 Ronald Bultje 2005-04-12 11:37:26 UTC
The above are messages after a state change. I don't think they matter w.r.t.
the actual seeking. I don't know the real cause yet.
Comment 16 Simon Morgan 2005-04-12 12:10:10 UTC
Then how come I can seek using the OSS sink but not the ALSA one?
Comment 17 Ronald Bultje 2005-07-02 10:39:52 UTC
I've done some updates lately to the ALSA plugins w.r.t. the above warnings that
you seem to be suffering from. Again, I don't know if they are related at all (I
doubt it), but since you say OSS works fine, they may be. Can you retry
gst-plugins 0.8.10 and see if it works any better now? Thanks.
Comment 18 Simon Morgan 2005-07-02 11:48:10 UTC
I've since switched back to Ubuntu Hoary but fortunately I've just noticed that
a new Breezy live CD image has been released so I'll download that and do some
testing.
Comment 19 Simon Morgan 2005-07-02 13:35:04 UTC
Unfortunately the kernel modules on the livecd are pretty broken so I'll have to
wait until the next one to test this.
Comment 20 Luca Ognibene 2005-10-02 14:35:44 UTC
Any news on this? Can you replicate ?
Comment 21 Simon Morgan 2005-10-02 15:45:59 UTC
I'm not longer experiencing this problem with 0.8.11.