[Top][All Lists]

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

Re: [Discuss-gnuradio] ATSC decoding

From: Klaus Hueske
Subject: Re: [Discuss-gnuradio] ATSC decoding
Date: Thu, 24 Jun 2010 09:51:31 +0200

Hi Stephen,
Did you make progress with this zero byte output problem? Anyway, I'm
wondering if the ATSC receiver implementation will work at all with the
current version of Gnuradio. It looks like parts of the original ATSC
implementation that was working with Gnuradio 0.9 have been adapted to be
used in Gnuradio 2.0, but now we have 3.2.2. Anyone here who can verify that
the provided code can decode ATSC signals?

On Mon, Apr 19, 2010 at 8:12 PM, Stephen Branch <address@hidden> wrote:
>Hello everyone,
>I am part of Auburn University's Software Defined Radio Senior Design team,
>Software being used:
>Ubuntu v.9.10 on xfs partition
>GNURadio v.3.3 (git)
>Available hardware: USRP1, USRP2, WBX daughterboard, TVRX daughterboard
>We followed the instructions in ./gnuradio/gr-atsc/src/python/README to no 
>Using the FFT we found 507.25M to have a strong signal.
>According to 
> this is channel 20.
>And according to 
> this is WCOV from Montgomery, Alabama.
>So we do have the correct video carrier frequency, which I assume is the 
>frequency we want to record and decode into a video.
>Question #1) Is the video carrier the one that carriers the video, or would
>be the ATSC carrier?
>We then used:
>./usrp_rx_cfile.py -s -d 10 -g 20 -f 507.25e6 atsc_data_6-4m_complex
>./interp_short.py atsc_data_6-4m_complex
>./viterbi-out.py test.mpeg
>/tmp/atsc_pipe_5 never fills with data.
>The output file, 'test.mpeg' is empty.
>Question #2) What do we need to fix to get /tmp/atsc_pipe_5 to fill.
>Question #3) What do we need to fix to get temp.mpeg to fill.
>Thank you,
>Bobby Black & Stephen Branch
>address@hidden (please do not blank out this email)
>black85 @ auburn . edu
>Bobby Black
>Auburn University
>(334) 804-4826 

reply via email to

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