gets applied to both ins and outs.
Eventually you can find this in the docs and examples, but even then it is not
obvious.
From: Gavin Jacobs
Sent: September 21, 2016 10:07 AM
To: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Module development and de
Sorry, that last email was empty for some reason. Not sure if I can
remember all the things... let me try:
On 09/21/2016 09:07 AM, Gavin Jacobs wrote:
>>You trigger, or simply stop the output (middle click). There's probably
>>a way to overlay signals with different rates, but I can't think of one
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Martin,
Thanks for those tips. A few follow-up points below.
Are you saying that on the same file, it gives non-deterministic
results? If so, that might be a bug in the file, but could also be in
GNU Radio. There are rumours that there's a randomness bug in the
scheduler, but it's hard to reprod
Gavin,
wow, looks like you went through a lot of learning! Maybe I can give you
some pointers:
On 09/19/2016 04:03 PM, Gavin Jacobs wrote:
> https://github.com/dl1ksv/gr-ax25
>
> So, I learned about git, and cmake, and make, and tons of other linux
> stuff, tried to download and install, but no
Further to some suggestions here a few months ago, I've switched gnuradio from
my Windows laptop to a dedicated desktop computer running Ubuntu. It is setup
in the attic with the receivers and antenna. I use my laptop and Remote Desktop
Connection to run the desktop in a 'headless' fashion. So n
