From: Derek Lesho <dlesho@codeweavers.com>
Subject: Re: [PATCH] winegstreamer: Fixup raw audio caps to be compatible with IMFMediaType.
Message-Id: <ed56d6dd-c8c8-2e95-84bc-0dfcbb08db76@codeweavers.com>
Date: Fri, 6 Nov 2020 14:20:21 -0600
In-Reply-To: <b7696131-bb34-782c-76ae-05d7b9f198ba@gmail.com>
References: <20201106181252.254864-1-dlesho@codeweavers.com> <b7696131-bb34-782c-76ae-05d7b9f198ba@gmail.com>

On 11/6/20 2:13 PM, Zebediah Figura wrote:

> This is done in a rather inconsistent way relative to how video streams
> are handled.
Yes, because the goals are different for each of the paths.  The video 
path is just an enhancement to report video formats in a defined order 
as if they were coming from a decoder, since right now we're skipping 
the decoder MFT step.  The step for fixing up the audio caps is meant to 
be a generic solution for any caps which are un-representable as a 
IMFMediaType object.  This same path is used for compressed h.264 video 
on my local branch for example.