Well, I wiped everything clearn and started from a fresh image of Linux to
remove any doubt (3rd time doing this). This time I made sure to do sudo
apt-get update liberally before running pybombs prefix init ~/rfnoc -R
rfnoc -a alias
The first time it showed boost failed to install even though the
Here is that output again with more relevant info that I forgot to copy
over:
make[2]: Entering directory `/home/switchlanez/rfnoc/src/pyqt4/qpy/QtCore'
g++ -c -m64 -pipe -fno-strict-aliasing -O2 -fPIC -Wall -W -D_REENTRANT
-DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mksp
It was WX that was mentioned as being deprecated. Sorry I don't have much
to offer for your issue tho, except that you should run the pybombs command
with -v (pybombs -v . -vv works too for very verbose output. At
some point it's trying to fetch a QT installer, but failing. I would try
grabbing tha
I finally got everything installed successfully after doing 30+ attempts
(this is no exaggeration) of rm -rf rfnoc and pybombs prefix init ~/rfnoc
-R rfnoc -a alias. I was getting wildly varying errors from packages not
being found (though I could manually hit those websites and download the
files)
On 09/22/2016 12:06 PM, Paul Zander wrote:
> Problem solved. I used the Sound GUI under the Settingsmenu to select
> the audio source.
> I am not sure if that is PulseAudio, but the selections and gain
> settings do work.
>
> I even found that I could switch the device while the flowgraph was r
Hey Andrew,
sorry for the miserable experience -- not sure why apt-get would be
acting up so badly. Clearly, the point of pybombs is for new users not
to have this kind of trouble.
I'm still a bit surprised that this is happening on 14.04, which is
probably the most popular distro around here at
So HW:1,0 does work on a "sink". Possibly, the documentation was just copied
over to source, but maybe not actually implemented yet... If so, that should
be on the bug list.
BTW, my signals happen to be of audio frequency range, but not really sounds.
I was hoping that I could eventually have o
Hi -
I've setup a front end, and captured about 10 to 20 seconds worth of
data to a file sink (750M data file)
The transmitted data is a small 8millisecond bursts, followed by a very
long delay.
I would like to have some means to 'zoom in and slice out' a few bits of
data so I can do more work
https://github.com/miek/inspectrum
Enable cursors, then right click > export samples
On 24/09/16 11:02, du...@duaneellis.com wrote:
> Hi -
>
> I've setup a front end, and captured about 10 to 20 seconds worth of
> data to a file sink (750M data file)
>
> The transmitted data is a small 8millis
On Fri, Sep 23, 2016 at 4:02 PM, wrote:
>
> Can you suggest a tool that I can use to "slice out" - the sections
> of interest?
I'm not sure about 750MB files but in general if you are just trying to
identify high signal power and slice that out, audio file editing tools
that allow reading "
If you need more advanced processing to detect the burst, you might consider
gr-eventstream [1]. It can chunk up bursts/events based on a trigger and write
to a file,display, or process.
[1] https://github.com/osh/gr-eventstream
Paul Garver
On Sep 23, 2016, at 8:53 PM, Kevin Reid
mailto:kpr.
11 matches
Mail list logo
