I have the following problem that I would like your opinion on how to solve
elegantly:
I have a block A (say a standard sync block with some memory--eg an fir
filter) which
has input x(t) and output y(t) and is pretty computationally intensive.
I would like to add the following functionality to i
PM
To: Discuss-gnuradio@gnu.org
Subject: [Discuss-gnuradio] Activating/Deactivating Blocks in real time
I have the following problem that I would like your opinion on how to solve
elegantly:
I have a block A (say a standard sync block with some memory--eg an fir filter)
which
has input x(t) and
nuradio@gnu.org
> *Subject:* [Discuss-gnuradio] Activating/Deactivating Blocks in real time*
> ***
>
> ** **
>
> I have the following problem that I would like your opinion on how to
> solve elegantly:
>
> I have a block A (say a standard sync block with some memory-
discuss-gnuradio-bounces+tmonahan=qti.qualcomm@gnu.org] *On Behalf
>> Of *Achilleas Anastasopoulos
>> *Sent:* Wednesday, October 02, 2013 3:48 PM
>> *To:* Discuss-gnuradio@gnu.org
>> *Subject:* [Discuss-gnuradio] Activating/Deactivating Blocks in real time
>>
>
ell, Tim <
>> tmona...@qti.qualcomm.com> wrote:
>>
>>> Can you do this with a 2:1 mux block? Input 2 = constant 0, control
>>> input is s(t)?
>>>
>>> ** **
>>>
>>> *From:* discuss-gnuradio-bounces+tmonahan=qti.qualcomm
<
>> tmona...@qti.qualcomm.com> wrote:
>>
>>> Can you do this with a 2:1 mux block? Input 2 = constant 0, control
>>> input is s(t)?
>>>
>>> ** **
>>>
>>> *From:* discuss-gnuradio-bounces+tmonahan=qti.qualcomm@gnu.or
) to make
>> it dynamic and allow multiple streams coming in to be synchronized and let
>> any input stream control output of all streams. It also still uses 3.6 API
>> (I know, the shame!)
>>
>> -Nathan
>>
>>>
>>>
>>> On Wed, Oct 2, 2013
