out of my custom block. I did not find any demux-block -- and then investigated
how the muxer works to understand why there's no demuxer. In this case the only
way a demuxer could work is to have the muxer scheme constant and share it to
m
Hi all,
I stumbled across the stream_mux tag propagation. In my understanding, tags are
associated with one item and should be associated with the same item after
processing, if possible. The stream_mux block however does not propagate tags
like that:
Say we mux two tagged streams A and B, whi
tted a pull request, so if anyone is interested, see
https://github.com/gnuradio/gnuradio/pull/792
--Merlin Chlosta
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
e gr-qtgui code, see below. Any comments on this? I'm
pretty sure it's not done right.
What do you think of this feature? Does this already exist and I did not find
it?
--Merlin Chlosta
---
commit 5df55a2ec563002161d43cca53aad119a32a38f2
Author: Merlin Chlosta
Date: Tue Apr 12
On 04.11.2014 09:43, Felix W. wrote:
> Hi list,
>
> I have a strange problem with one of my custom blocks. It's a char stream
> sink with a message output. It basically takes the input stream, selects a
> few samples, packs them into blobs, makes a pmt::cons out of it and
> publishes the message.
