On 5/12/2017 5:51 PM, Michael Niedermayer wrote:
On Fri, May 12, 2017 at 01:19:43PM -0700, Aaron Levinson wrote:
On 5/9/2017 11:56 AM, Michael Niedermayer wrote:
On Thu, May 04, 2017 at 11:46:30PM -0700, Aaron Levinson wrote:
I've provided a new version of the patch. When I created the
On Fri, May 12, 2017 at 01:19:43PM -0700, Aaron Levinson wrote:
> On 5/9/2017 11:56 AM, Michael Niedermayer wrote:
> >On Thu, May 04, 2017 at 11:46:30PM -0700, Aaron Levinson wrote:
> >>
> >>I've provided a new version of the patch. When I created the first version
> >>of the patch on March
On 5/9/2017 11:56 AM, Michael Niedermayer wrote:
On Thu, May 04, 2017 at 11:46:30PM -0700, Aaron Levinson wrote:
I've provided a new version of the patch. When I created the first version of the patch on March
26th, this was the first patch that I submitted to ffmpeg, and some aspects were
On Thu, May 04, 2017 at 11:46:30PM -0700, Aaron Levinson wrote:
> On 4/12/2017 6:08 PM, Aaron Levinson wrote:
> > On 3/26/2017 10:34 AM, Aaron Levinson wrote:
> >> On 3/26/2017 4:41 AM, Matthias Hunstock wrote:
> >>> Am 26.03.2017 um 11:50 schrieb Aaron Levinson:
> When using the following
On 5/5/2017 2:26 AM, wm4 wrote:
On Fri, 5 May 2017 01:11:17 -0700
Aaron Levinson wrote:
As I said on IRC, I'm skeptic against this, but I'm also not sure
whether I understand the situation.
First, your change seems a bit fragile, and almost relies on
coincidences. This
On Fri, 5 May 2017 01:11:17 -0700
Aaron Levinson wrote:
> > As I said on IRC, I'm skeptic against this, but I'm also not sure
> > whether I understand the situation.
> >
> > First, your change seems a bit fragile, and almost relies on
> > coincidences. This could easily
On 5/5/2017 12:55 AM, wm4 wrote:
On Thu, 4 May 2017 23:46:30 -0700
Aaron Levinson wrote:
On 4/12/2017 6:08 PM, Aaron Levinson wrote:
On 3/26/2017 10:34 AM, Aaron Levinson wrote:
On 3/26/2017 4:41 AM, Matthias Hunstock wrote:
Am 26.03.2017 um 11:50 schrieb Aaron
On Thu, 4 May 2017 23:46:30 -0700
Aaron Levinson wrote:
> On 4/12/2017 6:08 PM, Aaron Levinson wrote:
> > On 3/26/2017 10:34 AM, Aaron Levinson wrote:
> >> On 3/26/2017 4:41 AM, Matthias Hunstock wrote:
> >>> Am 26.03.2017 um 11:50 schrieb Aaron Levinson:
> When
On 4/12/2017 6:08 PM, Aaron Levinson wrote:
> On 3/26/2017 10:34 AM, Aaron Levinson wrote:
>> On 3/26/2017 4:41 AM, Matthias Hunstock wrote:
>>> Am 26.03.2017 um 11:50 schrieb Aaron Levinson:
When using the following command to play back either file:
ffmpeg -i -f decklink -pix_fmt
On 3/26/2017 10:34 AM, Aaron Levinson wrote:
> On 3/26/2017 4:41 AM, Matthias Hunstock wrote:
>> Am 26.03.2017 um 11:50 schrieb Aaron Levinson:
>>> When using the following command to play back either file:
>>> ffmpeg -i -f decklink -pix_fmt uyvy422 "DeckLink SDI
>>> 4K", I noticed that with
On 3/26/2017 4:41 AM, Matthias Hunstock wrote:
Am 26.03.2017 um 11:50 schrieb Aaron Levinson:
When using the following command to play back either file:
ffmpeg -i -f decklink -pix_fmt uyvy422 "DeckLink SDI
4K", I noticed that with the mpegts file with the AAC audio stream,
it would
Am 26.03.2017 um 11:50 schrieb Aaron Levinson:
> When using the following command to play back either file:
> ffmpeg -i -f decklink -pix_fmt uyvy422 "DeckLink SDI
> 4K", I noticed that with the mpegts file with the AAC audio stream,
> it would correctly select an interlaced video mode for the
Hopefully I went through the patch process correctly, as this is the first time
that I've done this. I didn't submit a ticket regarding this issue, but a
detailed description of the problem can be found below. It is possible that
there is an already existing ticket that corresponds to this
13 matches
Mail list logo