[Bug 693175] Endianness inconsistency in ffmpegcolorspace caps

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Tue Feb 5 05:53:42 PST 2013


https://bugzilla.gnome.org/show_bug.cgi?id=693175
  GStreamer | gst-plugins-base | 0.10.36

Wim Taymans <wim.taymans> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wim.taymans at gmail.com

--- Comment #2 from Wim Taymans <wim.taymans at gmail.com> 2013-02-05 13:53:38 UTC ---
(In reply to comment #0)
> Is it normal that bpp=24 and bpp=32 have endianness=4321 but bpp=16 has
> endianness=1234?

24 and 32 bits are always big endian, we use the masks to say where the R,G,B
is.

For 16 bits it depends on how the bytes are in memory. You need to look at how
16 bits are placed inside the memory by the driver and then put this in the
endianness property.

ffmpegcolorspace can only handle the native endianness for 16 bits so it only
exposes BYTE_ORDER.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list