Getting teletext right from VANC/VBI data is tricky, because the teletext clock
is not synced to the video clock. Therefore we have to first measure the
frequency of the teletext clock in the reconstructed signal, and then resample
the original data appropriately.
What I do is that I measure the d
Why not use libzvbi's slicer? It should be pretty robust with
less-than-ideal signal.
Regarding your code - is there a need to calculate a frequency? I did
something similar a while back with VBI from TV signal and in my experience:
a) this kind of frequency/phase estimation doesn't work that wel
On Wed, 13 Jan 2016 at 02:16 Andrey Turkin wrote:
> Why not use libzvbi's slicer? It should be pretty robust with
> less-than-ideal signal.
>
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Wed, 13 Jan 2016 at 02:16 Andrey Turkin wrote:
> Why not use libzvbi's slicer? It should be pretty robust with
> less-than-ideal signal.
>
(now with a proper response).
IMO FFmpeg shouldn't be doing analogue signal processing. This should be
left to libzvbi.
Kieran
__
On Wed, Jan 13, 2016 at 05:01:01AM +0300, Andrey Turkin wrote:
> Why not use libzvbi's slicer? It should be pretty robust with
> less-than-ideal signal.
>
> Regarding your code - is there a need to calculate a frequency? I did
> something similar a while back with VBI from TV signal and in my expe
Andrey Turkin gmail.com> writes:
> Why not use libzvbi's slicer? It should be pretty
> robust with less-than-ideal signal.
It is not entirely available under LGPL afaict.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg
2016-01-13 22:32 GMT+03:00 Michael Niedermayer :
> to calculate the phase
>
> the area that has alternating 0/1 values can be correlated with a
> sin() and a cos(), if you consider the 2 resulting values as x and y
> coordinates the angle they form from the origin is the phase.
> (this can be word
Slicer is a part of the library and as such is under LGPL; in fact FFmpeg
already uses the library to decode DVB teletext.
2016-01-14 1:27 GMT+03:00 Carl Eugen Hoyos :
> Andrey Turkin gmail.com> writes:
>
> > Why not use libzvbi's slicer? It should be pretty
> > robust with less-than-ideal sig
On Thu, Jan 14, 2016 at 01:41:51AM +0300, Andrey Turkin wrote:
> 2016-01-13 22:32 GMT+03:00 Michael Niedermayer :
>
> > to calculate the phase
> >
> > the area that has alternating 0/1 values can be correlated with a
> > sin() and a cos(), if you consider the 2 resulting values as x and y
> > coor
Andrey Turkin gmail.com> writes:
> Slicer is a part of the library and as such is under
> LGPL; in fact FFmpeg already uses the library to
> decode DVB teletext.
But FFmpeg's configure claims libzvbi is GPL,
an LGPL replacement for at least some functionality
is certainly welcome!
Carl Euge
On Wed, 13 Jan 2016, Michael Niedermayer wrote:
On Wed, Jan 13, 2016 at 05:01:01AM +0300, Andrey Turkin wrote:
Why not use libzvbi's slicer? It should be pretty robust with
less-than-ideal signal.
Regarding your code - is there a need to calculate a frequency? I did
something similar a while
11 matches
Mail list logo
