Re: [Discuss-gnuradio] Errors using PyBombs recipe for RFNoC setup

[Andrew Lanez]

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
Installation progress bar showed 100%.

I discovered that if I delete the ~/rfnoc directory I can rerun pybombs
prefix init ~/rfnoc -R rfnoc -a alias without errors. So everytime I do
that now I persistently get:

Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
PyBOMBS.Fetcher.wget - ERROR - hostname 'download.qt.io' doesn't match
either of '*.qt-project.org', 'qt-project.org', 'www.qt-project.org'
PyBOMBS.Packager.source - ERROR - Problem occurred while building package
qt4:
Unable to fetch recipe qt4
PyBOMBS.install_manager - ERROR - Error installing package qt4. Aborting.


What can I do about this?


On Thu, Sep 22, 2016 at 9:16 PM, Andrew Lanez  wrote:

> New Linux user here, I don't mean to anger anyone with my naivete.
>
> I just ran sudo apt-get. That might fix the other non-showstopper errors
> earlier. But I am not sure where to start to address that last error which
> is the show stopper:
>
> checking for BASE_DEPENDENCIES... no
> configure: error: Package requirements (glib-2.0 >= 2.25.10atk >=
> 1.29.2pango >= 1.20cairo >= 1.6gdk-pixbuf-2.0 >= 2.21.0) were
> not met:
>
> No package 'atk' found
> No package 'pango' found
> No package 'cairo' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables
> BASE_DEPENDENCIES_CFLAGS
> and BASE_DEPENDENCIES_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> PyBOMBS.Packager.source - ERROR - Configuration failed after running at
> least twice.
> PyBOMBS.Packager.source - ERROR - Problem occurred while building package
> gtk2:
> Configuration failed
> PyBOMBS.install_manager - ERROR - Error installing package gtk2. Aborting.
>
>
> I tried running the same pybombs command and got:
> $ pybombs prefix init ~/rfnoc -R rfnoc -a alias
> PyBOMBS - INFO - PyBOMBS Version 2.2.0
> PyBOMBS.prefix - ERROR - Ignoring. A prefix already exists in
> `/home/switchlanez/rfnoc'
>
> So I took out what might be prefix-related stuff but these didn't work:
> $ pybombs -R rfnoc -a alias
> $ pybombs rfnoc -a alias
> $ pybombs rfnoc
>
> How do I properly rerun the pybombs script?
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Errors using PyBombs recipe for RFNoC setup

[Andrew Lanez]

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/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I/usr/include/python2.7
-I../../QtCore -I. -I. -o qpycore_chimera.o qpycore_chimera.cpp
qpycore_chimera.cpp: In member function ‘void Chimera::set_flag()’:
qpycore_chimera.cpp:376:50: error: ‘pyqt4ClassTypeDef’ has no member named
‘qt4_flags’
 _is_flag = ((pyqt4ClassTypeDef *)_type)->qt4_flags & 0x01;
  ^
make[2]: *** [qpycore_chimera.o] Error 1
make[2]: Leaving directory `/home/switchlanez/rfnoc/src/pyqt4/qpy/QtCore'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/switchlanez/rfnoc/src/pyqt4/qpy'
make: *** [all] Error 2
PyBOMBS.Packager.source - ERROR - Build failed. See output above for error
messages.
PyBOMBS.Packager.source - ERROR - Problem occurred while building package
pyqt4:
Build failed.
PyBOMBS.install_manager - ERROR - Error installing package pyqt4. Aborting.


I was at GNU Radio Conference last week and remember mention of qt being
deprecated. Could this be why?

On Fri, Sep 23, 2016 at 8:20 AM, Andrew Lanez  wrote:

> 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
> Installation progress bar showed 100%.
>
> I discovered that if I delete the ~/rfnoc directory I can rerun pybombs
> prefix init ~/rfnoc -R rfnoc -a alias without errors. So everytime I do
> that now I persistently get:
>
> Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
> PyBOMBS.Fetcher.wget - ERROR - hostname 'download.qt.io' doesn't match
> either of '*.qt-project.org', 'qt-project.org', 'www.qt-project.org'
> PyBOMBS.Packager.source - ERROR - Problem occurred while building package
> qt4:
> Unable to fetch recipe qt4
> PyBOMBS.install_manager - ERROR - Error installing package qt4. Aborting.
>
>
> What can I do about this?
>
>
> On Thu, Sep 22, 2016 at 9:16 PM, Andrew Lanez  wrote:
>
>> New Linux user here, I don't mean to anger anyone with my naivete.
>>
>> I just ran sudo apt-get. That might fix the other non-showstopper errors
>> earlier. But I am not sure where to start to address that last error which
>> is the show stopper:
>>
>> checking for BASE_DEPENDENCIES... no
>> configure: error: Package requirements (glib-2.0 >= 2.25.10atk >=
>> 1.29.2pango >= 1.20cairo >= 1.6gdk-pixbuf-2.0 >= 2.21.0) were
>> not met:
>>
>> No package 'atk' found
>> No package 'pango' found
>> No package 'cairo' found
>>
>> Consider adjusting the PKG_CONFIG_PATH environment variable if you
>> installed software in a non-standard prefix.
>>
>> Alternatively, you may set the environment variables
>> BASE_DEPENDENCIES_CFLAGS
>> and BASE_DEPENDENCIES_LIBS to avoid the need to call pkg-config.
>> See the pkg-config man page for more details.
>> PyBOMBS.Packager.source - ERROR - Configuration failed after running at
>> least twice.
>> PyBOMBS.Packager.source - ERROR - Problem occurred while building package
>> gtk2:
>> Configuration failed
>> PyBOMBS.install_manager - ERROR - Error installing package gtk2. Aborting.
>>
>>
>> I tried running the same pybombs command and got:
>> $ pybombs prefix init ~/rfnoc -R rfnoc -a alias
>> PyBOMBS - INFO - PyBOMBS Version 2.2.0
>> PyBOMBS.prefix - ERROR - Ignoring. A prefix already exists in
>> `/home/switchlanez/rfnoc'
>>
>> So I took out what might be prefix-related stuff but these didn't work:
>> $ pybombs -R rfnoc -a alias
>> $ pybombs rfnoc -a alias
>> $ pybombs rfnoc
>>
>> How do I properly rerun the pybombs script?
>>
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Errors using PyBombs recipe for RFNoC setup

[Anon Lister]

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 that URL by hand as a start go make sure it's not an issue on your
network. Then someone here can try to reproduce, Incase QT changed
something.

On Sep 23, 2016 11:29 AM, "Andrew Lanez"  wrote:

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/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I/usr/include/python2.7
-I../../QtCore -I. -I. -o qpycore_chimera.o qpycore_chimera.cpp
qpycore_chimera.cpp: In member function ‘void Chimera::set_flag()’:
qpycore_chimera.cpp:376:50: error: ‘pyqt4ClassTypeDef’ has no member named
‘qt4_flags’
 _is_flag = ((pyqt4ClassTypeDef *)_type)->qt4_flags & 0x01;
  ^
make[2]: *** [qpycore_chimera.o] Error 1
make[2]: Leaving directory `/home/switchlanez/rfnoc/src/pyqt4/qpy/QtCore'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/switchlanez/rfnoc/src/pyqt4/qpy'
make: *** [all] Error 2
PyBOMBS.Packager.source - ERROR - Build failed. See output above for error
messages.
PyBOMBS.Packager.source - ERROR - Problem occurred while building package
pyqt4:
Build failed.
PyBOMBS.install_manager - ERROR - Error installing package pyqt4. Aborting.


I was at GNU Radio Conference last week and remember mention of qt being
deprecated. Could this be why?

On Fri, Sep 23, 2016 at 8:20 AM, Andrew Lanez  wrote:

> 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
> Installation progress bar showed 100%.
>
> I discovered that if I delete the ~/rfnoc directory I can rerun pybombs
> prefix init ~/rfnoc -R rfnoc -a alias without errors. So everytime I do
> that now I persistently get:
>
> Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
> PyBOMBS.Fetcher.wget - ERROR - hostname 'download.qt.io' doesn't match
> either of '*.qt-project.org', 'qt-project.org', 'www.qt-project.org'
> PyBOMBS.Packager.source - ERROR - Problem occurred while building package
> qt4:
> Unable to fetch recipe qt4
> PyBOMBS.install_manager - ERROR - Error installing package qt4. Aborting.
>
>
> What can I do about this?
>
>
> On Thu, Sep 22, 2016 at 9:16 PM, Andrew Lanez  wrote:
>
>> New Linux user here, I don't mean to anger anyone with my naivete.
>>
>> I just ran sudo apt-get. That might fix the other non-showstopper errors
>> earlier. But I am not sure where to start to address that last error which
>> is the show stopper:
>>
>> checking for BASE_DEPENDENCIES... no
>> configure: error: Package requirements (glib-2.0 >= 2.25.10atk >=
>> 1.29.2pango >= 1.20cairo >= 1.6gdk-pixbuf-2.0 >= 2.21.0) were
>> not met:
>>
>> No package 'atk' found
>> No package 'pango' found
>> No package 'cairo' found
>>
>> Consider adjusting the PKG_CONFIG_PATH environment variable if you
>> installed software in a non-standard prefix.
>>
>> Alternatively, you may set the environment variables
>> BASE_DEPENDENCIES_CFLAGS
>> and BASE_DEPENDENCIES_LIBS to avoid the need to call pkg-config.
>> See the pkg-config man page for more details.
>> PyBOMBS.Packager.source - ERROR - Configuration failed after running at
>> least twice.
>> PyBOMBS.Packager.source - ERROR - Problem occurred while building package
>> gtk2:
>> Configuration failed
>> PyBOMBS.install_manager - ERROR - Error installing package gtk2. Aborting.
>>
>>
>> I tried running the same pybombs command and got:
>> $ pybombs prefix init ~/rfnoc -R rfnoc -a alias
>> PyBOMBS - INFO - PyBOMBS Version 2.2.0
>> PyBOMBS.prefix - ERROR - Ignoring. A prefix already exists in
>> `/home/switchlanez/rfnoc'
>>
>> So I took out what might be prefix-related stuff but these didn't work:
>> $ pybombs -R rfnoc -a alias
>> $ pybombs rfnoc -a alias
>> $ pybombs rfnoc
>>
>> How do I properly rerun the pybombs script?
>>
>
>

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Errors using PyBombs recipe for RFNoC setup

[Andrew Lanez]

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) to compiling errors with make scripts. This was over my wired home
network and my work's wireless enterprise network but not sure if I should
blame those networks or the servers where these packages live.

On Fri, Sep 23, 2016 at 8:47 AM, Anon Lister  wrote:

> 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 that URL by hand as a start go make sure it's not an issue on your
> network. Then someone here can try to reproduce, Incase QT changed
> something.
>
> On Sep 23, 2016 11:29 AM, "Andrew Lanez"  wrote:
>
> 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/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
> -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I/usr/include/python2.7
> -I../../QtCore -I. -I. -o qpycore_chimera.o qpycore_chimera.cpp
> qpycore_chimera.cpp: In member function ‘void Chimera::set_flag()’:
> qpycore_chimera.cpp:376:50: error: ‘pyqt4ClassTypeDef’ has no member named
> ‘qt4_flags’
>  _is_flag = ((pyqt4ClassTypeDef *)_type)->qt4_flags & 0x01;
>   ^
> make[2]: *** [qpycore_chimera.o] Error 1
> make[2]: Leaving directory `/home/switchlanez/rfnoc/src/pyqt4/qpy/QtCore'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/switchlanez/rfnoc/src/pyqt4/qpy'
> make: *** [all] Error 2
> PyBOMBS.Packager.source - ERROR - Build failed. See output above for error
> messages.
> PyBOMBS.Packager.source - ERROR - Problem occurred while building package
> pyqt4:
> Build failed.
> PyBOMBS.install_manager - ERROR - Error installing package pyqt4. Aborting.
>
>
> I was at GNU Radio Conference last week and remember mention of qt being
> deprecated. Could this be why?
>
> On Fri, Sep 23, 2016 at 8:20 AM, Andrew Lanez  wrote:
>
>> 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
>> Installation progress bar showed 100%.
>>
>> I discovered that if I delete the ~/rfnoc directory I can rerun pybombs
>> prefix init ~/rfnoc -R rfnoc -a alias without errors. So everytime I do
>> that now I persistently get:
>>
>> Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
>> PyBOMBS.Fetcher.wget - ERROR - hostname 'download.qt.io' doesn't match
>> either of '*.qt-project.org', 'qt-project.org', 'www.qt-project.org'
>> PyBOMBS.Packager.source - ERROR - Problem occurred while building package
>> qt4:
>> Unable to fetch recipe qt4
>> PyBOMBS.install_manager - ERROR - Error installing package qt4. Aborting.
>>
>>
>> What can I do about this?
>>
>>
>> On Thu, Sep 22, 2016 at 9:16 PM, Andrew Lanez 
>> wrote:
>>
>>> New Linux user here, I don't mean to anger anyone with my naivete.
>>>
>>> I just ran sudo apt-get. That might fix the other non-showstopper errors
>>> earlier. But I am not sure where to start to address that last error which
>>> is the show stopper:
>>>
>>> checking for BASE_DEPENDENCIES... no
>>> configure: error: Package requirements (glib-2.0 >= 2.25.10atk >=
>>> 1.29.2pango >= 1.20cairo >= 1.6gdk-pixbuf-2.0 >= 2.21.0) were
>>> not met:
>>>
>>> No package 'atk' found
>>> No package 'pango' found
>>> No package 'cairo' found
>>>
>>> Consider adjusting the PKG_CONFIG_PATH environment variable if you
>>> installed software in a non-standard prefix.
>>>
>>> Alternatively, you may set the environment variables
>>> BASE_DEPENDENCIES_CFLAGS
>>> and BASE_DEPENDENCIES_LIBS to avoid the need to call pkg-config.
>>> See the pkg-config man page for more details.
>>> PyBOMBS.Packager.source - ERROR - Configuration failed after running at
>>> least twice.
>>> PyBOMBS.Packager.source - ERROR - Problem occurred while building
>>> package gtk2:
>>> Configuration failed
>>> PyBOMBS.install_manager - ERROR - Error installing package gtk2.
>>> Aborting.
>>>
>>>
>>> I tried running the same pybombs command and got:
>>> $ pybombs prefix init ~/rfnoc -R rfnoc -a alias
>>> PyBOMBS - INFO - PyBOMBS Version 2.2.0
>>> PyBOMBS.prefix - ERROR - Ignoring. A prefix already exists in
>>> `/home/switchl

Re: [Discuss-gnuradio] How to specify Audio Source device_name?

[Cinaed Simson]

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 running.
> 
> That said, I am puzzled about the intended usage of HW:1,0 and and
> similar device names.

It occurred to me last night where hw:1,0 is used - it can be used as
the device in the audio sink in grc.

I just tried it and it works.


> Suppose I create |~/.asoundrc |following the instructions at:
>   http://gnuradio.org/redmine/projects/gnuradio/wiki/ALSAPulseAudio
> |
> |
> |Then should I be able to specify the device name in GRC
> |
> |and not have to rely on the audio setings?
> |
> 
> 
> On 09/21/2016 12:40 PM,Cinaed Simson wrote:
>>
>> On 09/21/2016 09:40 AM, Paul Zander wrote:
>>> Cinaed,
>>>
>>> Your suggestion about testing the audio suggested an new experiment that
>>> may be a work-around.
>>>
>>> With Settings >> Sound >> Input >> Internal Microphone,  my GRC with (QT
>>> GUI Time Sink) shows a signal that responds to the internal microphone.
>>> Speaking or clapping hands causes a response on the graph.
>>>
>>> When I change the Input to Microphone, USB Audio Device, and re-execute
>>> the flowgraph,  the signal is very small and does not respond to
>>> sounds.  Maybe Audio Source only works with the default input from the
>>> system.
>>
>> Use the PulseAudio Volume control to turn up the volume on the input
>> device. You can find the find the input device under Inputs.


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Errors using PyBombs recipe for RFNoC setup

[Martin Braun]

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 this point in time, and
many people run pybombs on there without issues.

Cheers,
M

On 09/23/2016 12:17 PM, Andrew Lanez wrote:
> 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) to compiling errors with make scripts. This was over
> my wired home network and my work's wireless enterprise network but not
> sure if I should blame those networks or the servers where these
> packages live.
> 
> On Fri, Sep 23, 2016 at 8:47 AM, Anon Lister  > wrote:
> 
> 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 that URL by hand as a
> start go make sure it's not an issue on your network. Then someone
> here can try to reproduce, Incase QT changed something.
> 
> 
> On Sep 23, 2016 11:29 AM, "Andrew Lanez"  > wrote:
> 
> 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/mkspecs/linux-g++-64 -I.
> -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui
> -I/usr/include/qt4 -I/usr/include/python2.7 -I../../QtCore -I.
> -I. -o qpycore_chimera.o qpycore_chimera.cpp
> qpycore_chimera.cpp: In member function ‘void Chimera::set_flag()’:
> qpycore_chimera.cpp:376:50: error: ‘pyqt4ClassTypeDef’ has no
> member named ‘qt4_flags’
>  _is_flag = ((pyqt4ClassTypeDef *)_type)->qt4_flags & 0x01;
>   ^
> make[2]: *** [qpycore_chimera.o] Error 1
> make[2]: Leaving directory
> `/home/switchlanez/rfnoc/src/pyqt4/qpy/QtCore'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/switchlanez/rfnoc/src/pyqt4/qpy'
> make: *** [all] Error 2
> PyBOMBS.Packager.source - ERROR - Build failed. See output above
> for error messages.
> PyBOMBS.Packager.source - ERROR - Problem occurred while
> building package pyqt4:
> Build failed.
> PyBOMBS.install_manager - ERROR - Error installing package
> pyqt4. Aborting.
> 
> 
> I was at GNU Radio Conference last week and remember mention of
> qt being deprecated. Could this be why?
> 
> On Fri, Sep 23, 2016 at 8:20 AM, Andrew Lanez
> mailto:ala...@eng.ucsd.edu>> wrote:
> 
> 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 Installation progress bar showed 100%.
> 
> I discovered that if I delete the ~/rfnoc directory I can
> rerun pybombs prefix init ~/rfnoc -R rfnoc -a alias without
> errors. So everytime I do that now I persistently get:
> 
> Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
> PyBOMBS.Fetcher.wget - ERROR - hostname 'download.qt.io
> ' doesn't match either of
> '*.qt-project.org ', 'qt-project.org
> ', 'www.qt-project.org
> '
> PyBOMBS.Packager.source - ERROR - Problem occurred while
> building package qt4:
> Unable to fetch recipe qt4
> PyBOMBS.install_manager - ERROR - Error installing package
> qt4. Aborting.
> 
> 
> What can I do about this?
> 
> 
> On Thu, Sep 22, 2016 at 9:16 PM, Andrew Lanez
> mailto:ala...@eng.ucsd.edu>> wrote:
> 
> New Linux user here, I don't mean to anger anyone with
> my naivete.
> 
> I just ran sudo apt-get. That might fix the other

Re: [Discuss-gnuradio] How to specify Audio Source device_name?

[Paul Zander]

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 one source using "HW:1,0" and another 
"HW:2,0", HW:3,0 ... to have multiple inputs without having to buy a sound card 
with several  "stereo microphone" inputs.   

For now, my one channel input is working very well.

  From: Cinaed Simson 
 To: GNURadio Discussion List  
 Sent: Friday, September 23, 2016 12:56 PM
 Subject: Re: [Discuss-gnuradio] How to specify Audio Source device_name?
   
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 running.
> 
> That said, I am puzzled about the intended usage of HW:1,0 and and
> similar device names.

It occurred to me last night where hw:1,0 is used - it can be used as
the device in the audio sink in grc.

I just tried it and it works.


> Suppose I create |~/.asoundrc |following the instructions at:
>  http://gnuradio.org/redmine/projects/gnuradio/wiki/ALSAPulseAudio
> |
> |
> |Then should I be able to specify the device name in GRC
> |
> |and not have to rely on the audio setings?
> |
> 
> 
> On 09/21/2016 12:40 PM,Cinaed Simson wrote:
>>
>> On 09/21/2016 09:40 AM, Paul Zander wrote:
>>> Cinaed,
>>>
>>> Your suggestion about testing the audio suggested an new experiment that
>>> may be a work-around.
>>>
>>> With Settings >> Sound >> Input >> Internal Microphone,  my GRC with (QT
>>> GUI Time Sink) shows a signal that responds to the internal microphone.
>>> Speaking or clapping hands causes a response on the graph.
>>>
>>> When I change the Input to Microphone, USB Audio Device, and re-execute
>>> the flowgraph,  the signal is very small and does not respond to
>>> sounds.  Maybe Audio Source only works with the default input from the
>>> system.
>>
>> Use the PulseAudio Volume control to turn up the volume on the input
>> device. You can find the find the input device under Inputs.


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


   ___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] slicing up a 'file-sink' capture?

[duane]

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 with it.

I've tried baudline, while helpful - I can a very low level signal,
followed by a huge signal, and back to a low level signal.

My question is: 

Can you suggest a tool that I can use to "slice out" - the sections
of interest?
The closest example I can think of is using "head/tail" - into baud
line ... 
And manually move my start/stop sample number until I get what I
want.

There's got to be a better way...

for example I'd like to zoom in, select the region of interest then save
that region.

Then - these new files as input data for some tests.

Thanks.



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] slicing up a 'file-sink' capture?

[Garjo Slemina]

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 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 with it.
> 
> I've tried baudline, while helpful - I can a very low level signal,
> followed by a huge signal, and back to a low level signal.
> 
> My question is: 
> 
> Can you suggest a tool that I can use to "slice out" - the sections
> of interest?
> The closest example I can think of is using "head/tail" - into baud
> line ... 
> And manually move my start/stop sample number until I get what I
> want.
> 
> There's got to be a better way...


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] slicing up a 'file-sink' capture?

[Kevin Reid]

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 "raw" data (such as Audacity) can be used for this task.
Set the numeric format (e.g for a regular GNU Radio complex output, float,
little endian, 2 channels), ignore the sample rate, and just look at the
waveforms to slice out the parts you want.

What they won't typically do is give you a spectrogram view if you need to
identify the signal of interest by frequency as well as power.

There is also support in GNU Radio for recording signal bursts (the 'Burst
Tagger' block and something else), which of course could also be used on
already-captured data, but I'm not familiar with how to use it myself.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] slicing up a 'file-sink' capture?

[Garver, Paul W]

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...@switchb.org>> wrote:

On Fri, Sep 23, 2016 at 4:02 PM, 
mailto:du...@duaneellis.com>> 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 "raw" data (such as Audacity) can be used for this task. Set the 
numeric format (e.g for a regular GNU Radio complex output, float, little 
endian, 2 channels), ignore the sample rate, and just look at the waveforms to 
slice out the parts you want.

What they won't typically do is give you a spectrogram view if you need to 
identify the signal of interest by frequency as well as power.

There is also support in GNU Radio for recording signal bursts (the 'Burst 
Tagger' block and something else), which of course could also be used on 
already-captured data, but I'm not familiar with how to use it myself.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio