Yes, and there are programs that can capture part of a stream to a file
to examine. So you don't need access to the stream to see where the
broadcasters are failing to follow the FCC set standards. I think
Dvbsnoop is one and I have compiled, though I only used it once or twice
several years ago.
I think the plugin dev once said it is likely that the reason I don't
get data sometimes is because there is some flag to set that there is
data and they don't set it. The converter boxes and TV's ignore the flag
and go look for the data.
On 8/28/2012 9:53 AM, VDR User wrote:
On Tue, Aug 28, 2012 at 8:05 AM, Dominic Evans <oldmanuk@xxxxxxxxx> wrote:
On 25 August 2012 20:54, Timothy D. Lenz <tlenz@xxxxxxxxxx> wrote:
The problem here in the US is, DVB is not a standard for anything.
I'm guessing Klaus' problem here is that he doesn't live in the US so
can't access ATSC broadcasts for testing, so it doesn't really make
sense for him to attempt to maintain it in VDR core :)
Where is the current home for the ATSC plugin and who is/was the
original maintainer? Ideally it needs a US-based maintainer, but
(failing that) it should at least be migrated to somewhere more public
(e.g., github or vdr-developers) so that bugs/issues can be tracked.
It would be nice if it were moved to vdr-developers. I don't think the
author would even have a problem with that. The real drawback for NA
is that while there are plenty of users, there's practically no coders
here. The ones I know have either left VDR, or dvb altogether.
Thankfully there has been some EU coders willing to throw us a bone
and help out occasionally. With their help, and Klaus, NA VDR is far
less painful today that in the past. :)
_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
