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 <[email protected]> wrote: > On Mon, Jan 5, 2015 at 10:44 AM, Sylvain Munaut <[email protected]> wrote: > >> Hi, >> >> > 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 >> fd. >> >> >> Cheers, >> >> Sylvain >> > > This sounds like a good idea. > > Tom > >
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
