[Top][All Lists]

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

Re: [Discuss-gnuradio] Locking TopBlock stops WavFile-Sink

From: Luke Berndt
Subject: Re: [Discuss-gnuradio] Locking TopBlock stops WavFile-Sink
Date: Mon, 5 Jan 2015 11:08:13 -0500

I will give it a try and see if I can make a start() that does this.

One last question - does calling lock() in a HeirBlock2 just lock and call stop() on the internal blocks of the HeirBlock2 graph? or does it bubble up all the way to the TopBlock and cause a lock there?

I am trying to figure out why calling lock() on one instance of a HeirBlock cause all the other instances to lock().

On Mon, Jan 5, 2015 at 10:58 AM, Tom Rondeau <address@hidden> wrote:
On Mon, Jan 5, 2015 at 10:44 AM, Sylvain Munaut <address@hidden> wrote:

> You could try and modify the code to overload the start() function to
> open/reopen the file again (can't say for sure this will be safe with a wav
> file, though). Though probably easiest to create your own block as part of
> any oot module you've built for your projects.

I'd tend to say that the included block should support that. Since
apparently multiple start()/stop() calls by the scheduler is something
blocks should handle gracefully.

I'd assume stop() was made to close the file to ensure the header is
properly written.
But it could just update the header and seek back to the end without
actually closing the file and let the destructor do the close on the



This sounds like a good idea.


reply via email to

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