discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Re: ATSC decoding - Zero Output Problem - Update


From: Tom Rondeau
Subject: Re: [Discuss-gnuradio] Re: ATSC decoding - Zero Output Problem - Update
Date: Fri, 22 Oct 2010 18:00:09 -0400

On Fri, Oct 22, 2010 at 11:33 AM, Bryce Kahle <address@hidden> wrote:
> Has anyone been able to get the ATSC receiver working end-to-end since it
> was ported from 0.9? I'm able to get field sync aways into a small capture
> file, but the resulting transport stream file is not playable in Totem (with
> Xine backend). Does anyone have suggestions for where to look? I'm new to
> Gnuradio, so I'm still getting a feel for the codebase. Also, is there a
> better media player I should be using for the TS files?
> Thanks,
> Bryce Kahle


I've recently gotten about as far as you in working with it. I get the
field syncs fine, but the following decoding hasn't worked for me for
a long time. I have an interest in getting it back up and running
again, so please pass on anything more you can find out about it.

Tom



> On Sun, Oct 17, 2010 at 6:01 PM, Bryce Kahle <address@hidden> wrote:
>>
>> I'm new to GNURadio and trying to get ATSC receiving going again. This
>> message is in response to the message
>> at: http://lists.gnu.org/archive/html/discuss-gnuradio/2010-07/msg00285.html
>> I believe the reason your 0.9 output is working beyond the bit timing loop
>> is because of a sampling rate difference between 0.9 and 3.X. 0.9 samples at
>> either 20MS/s or 21.52MS/s, while 3.X uses 19.2MS/s. The test files located
>> at http://comsec.com/data/README are sampled at 20MS/s. The reason it works
>> beyond the bit timing loop, with the output from 0.9, is because only
>> the interpolator, fpll, and bit timing loop (at least those are the ones
>> that I found an explicit reference to a sampling rate) care about the
>> sampling rate.
>> Thus you have proven that the field_sync_demux and beyond are working, but
>> anything before that is potentially at fault. I'm trying to narrow down the
>> issue, but haven't found anything yet.
>> Bryce Kahle
>
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]