They aren't completely the same, although currently the same demuxer demuxes
both. This might change at some point, though. The file formats aren't exactly
the same.

I think we did this for the RB guys, so they can separate between 'plain'
Quicktime and MPEG-4.

should it be noted to gstreamer/docs/random/mimetypes.txt then closed ?

What's the difference?

Can i close this? 

The reason for this bug being open is this: GStreamer should not have mimetypes
or caps that discribe the same format in two different ways. So it is important
that every file can be identified as _either_ quicktime _or_ m4a.
This is to avoid issues people get when they write plugins for the quicktime
mimetype and then wondering why m4a files are not processed with this or vice
versa. I did quite some work to ensure this doesn't happen in the
video/x-raw-rgb mimetype.

So I'll rephrase the question: Are we sure we want to differentiate between
these two formats and are we sure we can differentiate between these two formats?

If so, close the bug.
If not, keep it open until one of these is gone.

(Inventing a mimetype just to make work for the RB guys easier doesn't sound
like a good idea to me after all ;)

can we have sample files / pipelines that use those mimetypes ? I'd be for
having one single mimetype in 0.9.

I think we should keep these separated. Formats like MP4, M4A, quicktime and 3GP are all quite similar (somehow related to "Iso base media file format") but they have certain differences (profiles etc.) that make them incompatible. I just reported a bug 331526 since in my current project it is essential to distinguish the difference between quicktime and 3GP formats.

do you need to autoplug another demuxer/decoder based on the result of the typefind function?

This is essentially the same as bug #340375. Marking it a dup of the other since the other one already has 0.11 API keywords etc.


*** This bug has been marked as a duplicate of 340375 ***

@Wim: yes, we do.