Since you know how to build from source, you're better off sticking with
that. The trick to multiple installs is just to use
-DCMAKE_INSTALL_PREFIX during the cmake step. For example:
cmake -DCMAKE_INSTALL_PREFIX=/opt/gnuradio-3.7.14 ../
/opt is a better location than /usr/local since you can
Your approach isn’t horrible. I’d stick with it.
Give that the USRP is sampling at a rate much faster than the transition event
you’re describing, I’m wondering if perhaps you don’t really understand how a
high-speed sampled baseband signal “works”. Your “can the USRP handle this”
comment sugg
Hi,
On an Ubuntu 18 system I would like to use multiple gnuradio+uhd instances in
parallel (3.7 with python 2.7, 3.8 with python 3, and a variety of versions
with patches applied, different UHD versions, RFnoc etc).
So far, I have multiple source trees and when I switch I completely delete
/us
I need to be able to grab a couple of samples at after some time after a
recurring event (step 2e below). The current method seems to work at the
moment, but was wondering if there was a better way. I tried to read the
documentation and example of proper use for this scenario, but I still do
Thank you Sylvain:
as this is a new computer, I had not installed pulseaudio. It seems
the "default" Alsa backend indeed drops frames. I installed pulseaudio
and running in debug mode (-) I cannot see frame size updates but most
importantly my records are now continuous, problems solved.
Furth
What audio backend are you using ?
I know Pulse Audio / Alsa can just drop / duplicate samples. They try
to reduce latency by adjusting some buffer size dynamically but those
adjustments will cause discontinuities.
You can for instance run pulse audio in debug mode and you'll see if /
when it doe
Hi!
Thanks for your reply.
While I'll work on installing and working with GRC 3.8, I was just
wondering will the over the air communication be bad enough to not even
receive a single correct packet? Is it to do with loop_bw for FLL, PFB
and Costas_Loop or the digital gain values (a multiply b
Nope, the Qt theme describes the Qt GUI widgets; GRC isn't affected by
it (also, not Qt).
On 18.05.20 23:26, Kyle A Logue wrote:
> I think all these configs are inside the QT theme.
>
> In GRC -> Tools -> Set Default QT Theme
> In $PYBOMBS_PREFIX/share/gnuradio/themes
>
> ***Kyle Logue*
> /Senio
