In HDTV streams, there is a large quantity of data that is always there. Each block, therefore, always has data to send to the next block, and the scheduler happily keeps iterating over the flowgraph. In a data network, we have bursty traffic. Are there any complications because of this? I'm thinking of buffering along the Tx path, specifically. Will data that is buffered in the host stay there until the next time the sink block is run, or does everything written to the USRP Tx eventually make it to the Tx d'card, even if the Tx sink block is never run again? I'm seeing behaviour that could either be that not all data is transmitted, or maybe my synchronization sequence isn't long enough. Either way, it seems that there needs to be a "critical mass" of data being transmitted continuously before recovery works (based on the fsk_rx/tx example: it doesn't work sending a file in non-looping mode, at least for me)
Thanks, -Rahul -- Rahul Dhar [EMAIL PROTECTED] Actually, my goal is to have a sandwich named after me.
pgpjOLD4tXL5G.pgp
Description: PGP signature
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
