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 679146 - avidemux can't decode avi file
avidemux can't decode avi file
Status: RESOLVED INVALID
Product: GStreamer
Classification: Platform
Component: dont know
0.10.x
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-06-29 15:14 UTC by cornel panceac
Modified: 2012-10-08 10:46 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
the error output from script (1.72 KB, text/plain)
2012-06-29 15:14 UTC, cornel panceac 		Details

Description cornel panceac 2012-06-29 15:14:53 UTC 
Created attachment 217634 [details]
the error output from script

muxer=avimux
gst-launch-0.10 filesrc location=\"$IN\"  ! taginject tags=\"$TAGS\" ! $muxer ! filesink location=$OUT

input file is:

$ file "samples/VIDEO_ONLY/3. VIDEO_AVi/8. MPEG 4 - Part 2 - Xvid _ 3ive_Nero Digital/XVid/meta_meta_meta_mpeg4xvid.avi"
samples/VIDEO_ONLY/3. VIDEO_AVi/8. MPEG 4 - Part 2 - Xvid _ 3ive_Nero Digital/XVid/meta_meta_meta_mpeg4xvid.avi: RIFF (little-endian) data, AVI, 1024 x 1024, 25.00 fps, video: XviD

output error is:

ERROR: from element /GstPipeline:pipeline0/GstAviMux:avimux0: Internal GStreamer error: negotiation problem.  Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.

additional info in the attached file.

please help :)
Comment 1 Tim-Philipp Müller 2012-06-29 15:49:00 UTC 
This has nothing to do with avi *demux*. The error message says the error comes from the *muxer*. Your pipeline has no demuxer in it, only a muxer. You get that error because you are feeding data without caps to the muxer, which is not going to work. This whole pipeline is not going to work, retagging is much more complicated than that I'm afraid. In any case, I'm going to close this because it's not actually a bug, despite the error message.