[Discuss-gnuradio] Upgrade pybombs to spesific time

Hi, I'm trying to check out the pybomb code that I've used on May 4th,2016 from git hub. so currently can update to latest by below command : sudo -H pip install --upgrade git+https://github.com/gnuradio/pybombs.git but when trying to upgrade to sepcific time stamp it doesn't work. sudo -H

Re: [Discuss-gnuradio] Portaudio Audio Source in Windows

Yes, Wix is pretty flexible in that regard. It looks like right now some config files are looking in the $HOME directory and some are looking in the $APPDATA directory, so I think we should examine thoroughly what is looking where and aim for consistency. Geof On Monday, May 9, 2016, Marcus

[Discuss-gnuradio] Announcing NEWSDR on Thr/Fri June 2/3 (Updated)

​ * NEWSDR 2016 New England Workshop on Software-Defined Radio Sixth-Annual Workshops Thursday June 2

Re: [Discuss-gnuradio] Run Gnu Radio after installation

Hi Ben, No I tried to install it only through Pybomb but got an error. Wednesday I got it install without an error but for some reason I deleted the linux image and tried to reinstall it on Thursday. I keep getting an error as sounds like they have updated the pybomb source.

[Discuss-gnuradio] Help in FEC example + ofdm modulation

Hello colleagues, I need some help! I am studying the FEC examples and for it I am using the "fecapi_tagged_encoders.grc". I can understand this example but I have problems when I try to simulate some modulation and transmission. I don't receive any information and this is showed in reports

Re: [Discuss-gnuradio] Fwd: Re: Sigh - 16.04 build failure

On Mon, May 9, 2016 at 5:28 PM, Mike wrote: > Found it ! I discovered a duplicate set of headers in /usr/local/include > and /usr/include, fixing this didn't fix the problem. > > After several hours wondering what was wrong with the headers I found > there were two versions

Re: [Discuss-gnuradio] Fwd: Re: Sigh - 16.04 build failure

Hey Mike - Quick question: On Mon, May 9, 2016 at 5:28 PM, Mike wrote: > Found it ! I discovered a duplicate set of headers in /usr/local/include > and /usr/include, fixing this didn't fix the problem. > > After several hours wondering what was wrong with the headers I

Re: [Discuss-gnuradio] Fwd: Re: Sigh - 16.04 build failure

As this is a relatively new option, it only works with the very latest PyBOMBS. Follow Martin's general advice of getting the newest version of it. Best regards, Marcus Am 9. Mai 2016 20:26:22 MESZ, schrieb Mike : >Starting again with a clean install of pybombs > >Why does

Re: [Discuss-gnuradio] Fwd: Re: Sigh - 16.04 build failure

Cool! Can you keep us updated here if there were any other PyBOMBS-related issues with 16.04? https://github.com/gnuradio/pybombs/issues is a good place to jot those down, too. Thanks, Martin On 05/09/2016 02:28 PM, Mike wrote: > Found it ! I discovered a duplicate set of headers in

[Discuss-gnuradio] Fwd: Re: Sigh - 16.04 build failure

Found it ! I discovered a duplicate set of headers in /usr/local/include and /usr/include, fixing this didn't fix the problem. After several hours wondering what was wrong with the headers I found there were two versions of libcppunit. This must have been a leftover of the upgrade to 16.04 as

Re: [Discuss-gnuradio] Sigh - 16.04 build failure

Hi Mike, I'd really like to get 16.04 support stable for the upcoming PyBOMBS 2.1.0 release. Thanks for testing newest code and all -- now we just need to figure out what's actually not working :) It might be PyBOMBS code *or* the recipes. I appreciate any logs! Cheers, M On 05/09/2016 10:54

Re: [Discuss-gnuradio] How do I use formatter in QT GUI Label?

Dan and Marcus (from another thread related to this), I'm trying to do what you say, but I get an error when using *"{0:.3e}".format* in the formatter field. The default value (0) is now formatted properly but it won't ever update and in terminal I get the following error Exception in thread

Re: [Discuss-gnuradio] ORC support on armhf w/ embedded SDK

Oh good to know! I thought the whole thing had disappeared. Thanks, Tom. Cheers, Ben On Mon, May 9, 2016 at 3:07 PM, Tom Tsou wrote: > On Mon, May 9, 2016 at 11:47 AM, Ben Hilburn > wrote: > > ORC (the Oil Runtime Compiler) is abandonware, at this

Re: [Discuss-gnuradio] ORC support on armhf w/ embedded SDK

On Mon, May 9, 2016 at 11:47 AM, Ben Hilburn wrote: > ORC (the Oil Runtime Compiler) is abandonware, at this point. The company > that developed it, EntropyWave, closed up a while ago. I seem to remember > ttsou talking to the founder who said that they were focusing on a

Re: [Discuss-gnuradio] Run Gnu Radio after installation

Hi Shahnaz - Your message is a little confusing. Did you try to install GNU Radio both through PyBOMBS as well as your package manager? If you used PyBOMBS to install GNU Radio, you do not need to install it a second time through your OS. Cheers, Ben On Thu, May 5, 2016 at 1:54 PM, Shahnaz

Re: [Discuss-gnuradio] ORC support on armhf w/ embedded SDK

I know everyone that has responded in this thread already knows this, but just in case anyone following along doesn't know: ORC (the Oil Runtime Compiler) is abandonware, at this point. The company that developed it, EntropyWave, closed up a while ago. I seem to remember ttsou talking to the

[Discuss-gnuradio] Fwd: Re: Sigh - 16.04 build failure

Forwarded Message Subject:Re: [Discuss-gnuradio] Sigh - 16.04 build failure Date: Mon, 9 May 2016 18:36:09 +0100 From: Mike To: marcus.muel...@ettus.com CPPUNIT is installed but is it also one of the first things pybombs builds - is

Re: [Discuss-gnuradio] Sigh - 16.04 build failure

There was a bug (until May 1st) that would effectively disable running make a second time (with makewidth==1). I think you're running a PyBOMBS from before that (not that I'm saying you should have, this is not in the latest release yet), but it would give some better error message than this. Can

Re: [Discuss-gnuradio] Portaudio Audio Source in Windows

Hi Geof, is there a chance to manually specify where the config files go in terms environment variables? I.e., tell the installer to put what is in PREFIX/etc into %APPDATA%? Best regards, Marcus On 09.05.2016 17:37, Geof Nieboer wrote: > Tony, that's good news. > > The nice thing is that the

Re: [Discuss-gnuradio] Portaudio Audio Source in Windows

Tony, that's good news. The nice thing is that the environment variables can generally be made as relative paths, so I should be able include setting that automatically for everyone as part of the msi. The $home directory is probably the best place as Windows doesn't want users changing files in

Re: [Discuss-gnuradio] Portaudio Audio Source in Windows

Thanks Marcus. I just set the environment variable that you mentioned in the run_gr.bat file that Geof mentioned and portaudio now works. I realize it is not a clean solution, but it is a working one. I am happy. Tony On Mon, May 9, 2016 at 9:42 AM, Marcus Müller

Re: [Discuss-gnuradio] Portaudio Audio Source in Windows

Thanks Geof. A Windows audio source would be great. Just to be clear though, because I started down this path by first trying to get GRC to process my config.conf file. I never succeeded. Is this a known problem? Tony On Mon, May 9, 2016 at 9:06 AM, Geof Nieboer

Re: [Discuss-gnuradio] Portaudio Audio Source in Windows

Hi Geof, as I'm currently thinking about how we'd want GNU Radio to /actually behave/ when looking for config files, I'd like to ask you a question regarding generation of the installer: How do you do it? Are you letting CMake install everything in a "clean slate prefix", and then just package

Re: [Discuss-gnuradio] Portaudio Audio Source in Windows

Hi Tony, to be honest, I'll be rewriting GNU Radio's slightly dated and slightly ugly preference system, as it seems, so I'm not 100% giving up on this. So, I hope the spirit of the workaround was clear to you: you can always manually set this particular setting via python (instead of specifying

Re: [Discuss-gnuradio] Portaudio Audio Source in Windows

Tony, Getting the Windows audio source to work is on my "to do" list. I reworked the sink already, so I don't think it will be difficult to do the source either. The hard coded paths are troublesome, as using a Windows installer that allows users to install in any path they desire after

Re: [Discuss-gnuradio] Portaudio Audio Source in Windows

There appear to be some problems with "python module"s in Windows GRC too. I get an error that the editor can't find a particular file. If I add the python block in GRC, then have it generate code and add the code to the corresponding Python file from an external editor - I can then run the top

[Discuss-gnuradio] gr-dsd and gqrx

hello all i see this here https://www.youtube.com/watch?v=yaio4YxwcBg and i want to know how to add the gr-dsd https://github.com/argilo/gr-dsd to the gqrx ,just like the vedio showed are there some instructions or some ways to get this done. thank you

Re: [Discuss-gnuradio] Portaudio Audio Source in Windows

Hi Tony, > The lack of path separators is troubling. I couldn't agree more. But since that just means that the separator get's "eaten" somewhere, and we don't know whether that happens when generating these paths or just when printing, I'm still full of hope… > The fact these directories don't

Re: [Discuss-gnuradio] Sigh - 16.04 build failure

I have built a new 16.04 i386 machine and found no issue, as well have updated existing Ubuntu machine from 15.04 to 16.04 and have everything working fine except gr-fosphor which needs freetype 2. I did have to update pybombs from git to get the updated machine working. Cam On 09/05/16