On 31-08-2019 08:11 PM, Marton Balint wrote:
On Sat, 31 Aug 2019, Gyan wrote:
On 31-08-2019 04:14 AM, Marton Balint wrote:
On Fri, 30 Aug 2019, Gyan wrote:
On 22-08-2019 01:10 AM, Marton Balint wrote:
On Tue, 20 Aug 2019, Devin Heitmueller wrote:
A couple of follow-up Qs:
Is
On Sat, 31 Aug 2019, Gyan wrote:
On 31-08-2019 04:14 AM, Marton Balint wrote:
On Fri, 30 Aug 2019, Gyan wrote:
On 22-08-2019 01:10 AM, Marton Balint wrote:
On Tue, 20 Aug 2019, Devin Heitmueller wrote:
A couple of follow-up Qs:
Is auto-detection available for all Decklink
On 31-08-2019 04:14 AM, Marton Balint wrote:
On Fri, 30 Aug 2019, Gyan wrote:
On 22-08-2019 01:10 AM, Marton Balint wrote:
On Tue, 20 Aug 2019, Devin Heitmueller wrote:
A couple of follow-up Qs:
Is auto-detection available for all Decklink devices?
No, but AFAIK it is for all
On Fri, 30 Aug 2019, Gyan wrote:
On 22-08-2019 01:10 AM, Marton Balint wrote:
On Tue, 20 Aug 2019, Devin Heitmueller wrote:
A couple of follow-up Qs:
Is auto-detection available for all Decklink devices?
No, but AFAIK it is for all devices which support SDI. Generally it's
the older
On 22-08-2019 01:10 AM, Marton Balint wrote:
On Tue, 20 Aug 2019, Devin Heitmueller wrote:
A couple of follow-up Qs:
Is auto-detection available for all Decklink devices?
No, but AFAIK it is for all devices which support SDI. Generally it's
the older analog capture devices which don't
On Tue, 20 Aug 2019, Devin Heitmueller wrote:
A couple of follow-up Qs:
Is auto-detection available for all Decklink devices?
No, but AFAIK it is for all devices which support SDI. Generally it's
the older analog capture devices which don't support it.
For those for which it is
> A couple of follow-up Qs:
>
> Is auto-detection available for all Decklink devices?
No, but AFAIK it is for all devices which support SDI. Generally it's
the older analog capture devices which don't support it.
> For those for which it is available, are there any edge cases in which
> it sets
On 19-08-2019 07:15 PM, Ilinca Tudose wrote:
Hi Marton,
I want to confirm that we get correctly synced TCs when leaving out the
format_code parameter and using an ffmpeg build from head (not with Gyan's
patch). However, I was under the impression that we need the format_code so
that we can
Hi Marton,
I want to confirm that we get correctly synced TCs when leaving out the
format_code parameter and using an ffmpeg build from head (not with Gyan's
patch). However, I was under the impression that we need the format_code so
that we can capture different content types, in the original
On 17-08-2019 09:21 PM, Marton Balint wrote:
On Sat, 17 Aug 2019, Gyan wrote:
On 17-08-2019 08:42 PM, Marton Balint wrote:
On Wed, 14 Aug 2019, Marton Balint wrote:
On Wed, 14 Aug 2019, Gyan wrote:
On 09-08-2019 04:59 PM, Ilinca Tudose wrote:
Hi Marton,
The issue with the
On Sat, 17 Aug 2019, Gyan wrote:
On 17-08-2019 08:42 PM, Marton Balint wrote:
On Wed, 14 Aug 2019, Marton Balint wrote:
On Wed, 14 Aug 2019, Gyan wrote:
On 09-08-2019 04:59 PM, Ilinca Tudose wrote:
Hi Marton,
The issue with the out of sync TC was reproducible on all tapes and
On 17-08-2019 08:42 PM, Marton Balint wrote:
On Wed, 14 Aug 2019, Marton Balint wrote:
On Wed, 14 Aug 2019, Gyan wrote:
On 09-08-2019 04:59 PM, Ilinca Tudose wrote:
Hi Marton,
The issue with the out of sync TC was reproducible on all tapes and
decks
that we tested. I don't have
On Wed, 14 Aug 2019, Marton Balint wrote:
On Wed, 14 Aug 2019, Gyan wrote:
On 09-08-2019 04:59 PM, Ilinca Tudose wrote:
Hi Marton,
The issue with the out of sync TC was reproducible on all tapes and decks
that we tested. I don't have the exact number now, but a few dozens, less
than
On Wed, 14 Aug 2019, Gyan wrote:
On 09-08-2019 04:59 PM, Ilinca Tudose wrote:
Hi Marton,
The issue with the out of sync TC was reproducible on all tapes and decks
that we tested. I don't have the exact number now, but a few dozens, less
than 100. They all had between 7 and 17 frames out
On 09-08-2019 04:59 PM, Ilinca Tudose wrote:
Hi Marton,
The issue with the out of sync TC was reproducible on all tapes and decks
that we tested. I don't have the exact number now, but a few dozens, less
than 100. They all had between 7 and 17 frames out of sync. We were not
able to obtain
Hi Marton,
The issue with the out of sync TC was reproducible on all tapes and decks
that we tested. I don't have the exact number now, but a few dozens, less
than 100. They all had between 7 and 17 frames out of sync. We were not
able to obtain anything more in sync than 7 frames.
The TC sync
On 28-07-2019 01:37 AM, Marton Balint wrote:
On Fri, 26 Jul 2019, Gyan wrote:
Patch supported by and tested at Google.
Seems like a huge hack for a decklink issue... ;)
I wonder if there are better approaches to work around this. Like
dropping all frames until we have a valid signal.
On 28-07-2019 01:37 AM, Marton Balint wrote:
On Fri, 26 Jul 2019, Gyan wrote:
Patch supported by and tested at Google.
Seems like a huge hack for a decklink issue... ;)
I wonder if there are better approaches to work around this. Like
dropping all frames until we have a valid signal.
On Fri, 26 Jul 2019, Gyan wrote:
Patch supported by and tested at Google.
Seems like a huge hack for a decklink issue... ;)
I wonder if there are better approaches to work around this. Like dropping
all frames until we have a valid signal.
How is this repoducible? do you have an exact
Patch supported by and tested at Google.
Gyan
From e51bd8201ddf618dce33ada70a9bc6ce2f33b07b Mon Sep 17 00:00:00 2001
From: Gyan Doshi
Date: Mon, 1 Jul 2019 23:43:44 +0530
Subject: [PATCH] avdevice/decklink: adjust for timecode lag
The decklink demuxer may not start receiving timecode with
the
20 matches
Mail list logo
