Hello,
Q1: If I use a file_sink to record data, and my app never reports "Ou"
on the console, have all the bits been written to disk?
Q2: Does anyone have a suggestion about how I can avoid Ou messages when
using file_sink?
Q1 commentary: Sometimes the data I get from file_sink looks funky. It
could be a problem with my implementation of my application, but I
suspect the data is corrupted and I suspect it contains gaps eventhough
no "Ou" was reported.
Q2 commentary: Ramdisk doesn't work because I'm writing gigabytes of
data. I am thinking maybe I could write a multithreaded file_sink that
operates more cleverly than the currently implementation. I am sampling
4e6 complex short samples per second. I have also tried sending the
data over TCPIP using file_descriptor_sink attached to a python socket
with setblocking(0). Even when the receiving server is just throwing
away the data (i.e. no disk access or processing) data is sometimes lost.
Thanks for your help and suggestions,
Chris
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
