On Sat, Jan 3, 2015 at 8:39 PM, Luis Colunga <[email protected]> wrote:
> Hi Dan, > > Thanks for the response, but it seems like burst tagger would not work > in this case because I am working with audio. What I want is when > power squelch is triggered demod a NFM signal and then save it to a > wav file with the time power squelch was triggered. > You can try keeping power squelch's gate to false (so that you will get zero samples) and then use it as a trigger for "burst_tagger" after doing some math manipulations. This along with a "tagged_file_sink" should work. Please look into "gnuradio/examples/tags" for examples. Sreeraj > > Thanks > > 2015-01-02 16:12 GMT-07:00 Dan CaJacob <[email protected]>: > > Hi Luis, > > > > I am pretty certain there is a block in mainline GR to do this with > tagging. > > Burst tagger maybe? The tags define the burst boundaries and a > timestamp is > > recorded as well. > > > > On Jan 2, 2015 5:46 PM, "Luis Colunga" <[email protected]> wrote: > >> > >> Hello, > >> > >> I have a Python handcoded block in which I want every time that power > >> squelch is triggered, grab the actual time and then use that filename > >> to write a wav file with a decoded stream. > >> > >> What would be a good approach? I tried using variables but I see they > >> don't update at runtime and I am not sure if you are able to change > >> the wav sink name on runtime and just expect it to work or if it > >> neccesary to do something else there. > >> > >> Thanks. > >> > >> _______________________________________________ > >> Discuss-gnuradio mailing list > >> [email protected] > >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > _______________________________________________ > Discuss-gnuradio mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > -- Regards Sreeraj Rajendran http://radioninja.in/
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
