[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] Locking TopBlock stops WavFile-Sink
From: |
Sylvain Munaut |
Subject: |
Re: [Discuss-gnuradio] Locking TopBlock stops WavFile-Sink |
Date: |
Mon, 5 Jan 2015 13:34:00 +0100 |
Hi,
When there is a lock()/unlock() cycle, the ->stop() will end up being
called on all the flowgraph() blocks.
The wavsink block does implement stop() and that's where it closes the
file and updates the wavheader.
But there is no implementation for start(), it actually opens the file
in the constructor, so it can't resume.
Cheers,
Sylvain
- [Discuss-gnuradio] Locking TopBlock stops WavFile-Sink, Luke Berndt, 2015/01/05
- Re: [Discuss-gnuradio] Locking TopBlock stops WavFile-Sink,
Sylvain Munaut <=
- Re: [Discuss-gnuradio] Locking TopBlock stops WavFile-Sink, Luke Berndt, 2015/01/05
- Re: [Discuss-gnuradio] Locking TopBlock stops WavFile-Sink, Tom Rondeau, 2015/01/05
- Re: [Discuss-gnuradio] Locking TopBlock stops WavFile-Sink, Sylvain Munaut, 2015/01/05
- Re: [Discuss-gnuradio] Locking TopBlock stops WavFile-Sink, Tom Rondeau, 2015/01/05
- Re: [Discuss-gnuradio] Locking TopBlock stops WavFile-Sink, Luke Berndt, 2015/01/05
- Re: [Discuss-gnuradio] Locking TopBlock stops WavFile-Sink, Johnathan Corgan, 2015/01/05
- Re: [Discuss-gnuradio] Locking TopBlock stops WavFile-Sink, Luke Berndt, 2015/01/07