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

Let me write a short document detailing what /should/ go where first. Am 10. Mai 2016 03:30:02 MESZ, schrieb Geof Nieboer : >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

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

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

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] Portaudio Audio Source in Windows

The command: gnuradio-config-info --prefsdir --sysconfdir returns C:gr-buildsrc-stage3staged_installReleaseetc C:gr-buildsrc-stage3staged_installReleaseetcgnuradioconf.d The lack of path separators is troubling. The fact these directories don't exist on my machine (even with

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

Sooo gnuradio-runtime/lib/prefs.cc: 77 // Find if there is a ~/.gnuradio/config.conf file and add this to 78 // the end of the file list to override any preferences in the 79 // installed path config files. 80 fs::path homedir = fs::path(gr::appdata_path()); 81 homedir =

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

The * is actually just an artifact of how that list is generated; it's written by CMake when gathering the enabled audio engines; When running cmake, you'll see something like -- ## -- # Gnuradio enabled components --

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

The * is actually just an artifact of how that list is generated; it's written by CMake when gathering the enabled audio engines; When running cmake, you'll see something like -- ## -- # Gnuradio enabled components --

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

I think I'm making progress with your help Marcus. The output of "gnuradio-config-info --enabled-components" is: python-support;testing-support;volk;doxygen;sphinx;gnuradio-runtime;gr-ctrlport;gr-blocks;gnuradio-companion;gr-fec;gr-fft;gr-filter;gr-analog;gr-digital;gr-dtv;gr-atsc;gr-audio;*

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

Huh, can you verify portaudio is in the output of "gnuradio-config-info --enabled-components" ? Can you add another section, [audio_portaudio] verbose = true Just to verify: you're using the "[..]" section headers correctly, and the rest of the conf file looks ungarbled, right? We might be

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

Thanks, but I've tried that (setting "audio_module = portaudio"). It doesn't appear to have the desired effect. Tony On Thu, May 5, 2016 at 4:26 PM, Marcus Müller wrote: > Sorry, not currently running any Windows VM, but in the spirit of giving > you the info you

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

Sorry, not currently running any Windows VM, but in the spirit of giving you the info you need as fast as possible: Quick lecture of the audio sink/source factory tells me that under windows, by default the windows audio architecture is used. So to use portaudio instead, you need to have a GNU

[Discuss-gnuradio] Portaudio Audio Source in Windows

I'm using the pre-built Win64 binary of GNURadio listed on the gnuradio.org site. The portaudio library was included as part of the Win64 build, but I can't seem to figure out how to use it instead of the default windows audio. (I want an audio source and the windows audio source does not work.)

Re: [Discuss-gnuradio] Portaudio

Perhaps they were confused in that the script doesn't find the install package and then fails when trying to build with that support built in: -- found jack, version 0.121.2 -- Found jack: /usr/lib/i386-linux-gnu/libjack.so -- checking for module 'portaudio' -- package 'portaudio' not found

[Discuss-gnuradio] Portaudio

Under what circumstances will the build be dependent on portaudio? -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org

Re: [Discuss-gnuradio] Portaudio

On Sat, Apr 21, 2012 at 19:03, Marcus D. Leech mle...@ripnet.com wrote: Under what circumstances will the build be dependent on portaudio? If cmake finds portaudio during build, it will compile the portaudio source and sink blocks in gr-audio. If not, it won't. Same for the other audio

Re: [Discuss-gnuradio] Portaudio

On 04/21/2012 10:36 PM, Johnathan Corgan wrote: If cmake finds portaudio during build, it will compile the portaudio source and sink blocks in gr-audio. If not, it won't. Same for the other audio systems. Not sure if this answers your question. Johnathan Had a user complain that

Re: [Discuss-gnuradio] Portaudio

On Sat, Apr 21, 2012 at 19:51, Marcus D. Leech mle...@ripnet.com wrote: Had a user complain that build-gnuradio didn't do portaudio pre-reqs, and so his build failed during portaudio.  Which I found confusing.  So, I wonder if his system had just-enough of portaudio installed to confuse the

Re: [Discuss-gnuradio] portaudio sink, try round 2

Robert McGwier wrote: I am hoping the Windows folks can bring their code up now as well. Portaudio is really solid on Windows as I have been using it there for ASIO, MME, and DirectX for two years and after I helped Eric Wachsman get a leg up (by leaning on my friends for help) he got WDM-KS

Re: [Discuss-gnuradio] portaudio sink, partial succes on windows WARNING

Yes, I believe you are killing the pa threads with this small latency request. I should have remembered this for Windows. In the current sink code, the buffer and latency request are based on 21.3 ms. For Windows MME, this should be at least 100ms on your first try. Be careful and

Re: [Discuss-gnuradio] portaudio sink, partial succes on windows

This is excellent news. I can't believe we have only been attempting this for a little over a week. It will improve. Please change the 10.66 ms interval in check_topology UPWARDS until the crackling stops. I am sure you are not able to handle 11 msec latency with wmme. You will be

Re: [Discuss-gnuradio] portaudio sink updated, fm stereo receive with pa added

On Sat, Mar 18, 2006 at 09:59:28PM -0500, Robert McGwier wrote: After offline discussions with Eric, Frank, and Stephane we decided to check the portaudio sink with 10.6... msec buffers and fixed latency. That code has been checked in and there are a few ways to test it. In

[Discuss-gnuradio] portaudio sink, try round 2

Thanks to tons of grunt work by Eric, we have used the highly tuned ring buffers in the audio_portaudio_sink code and it functions nicely with a little bit of operator help.I can now get solid performance on all Linux hosts with the example code mono_tone_portaudio.py and

[Discuss-gnuradio] portaudio

We are very close with the portaudio but not quite there with the stuff but what I am seeing says to me this is going to be a real winner. We are having the usual ring buffer and other simple arithmetic problems. Stephane made a good start doing 85% of the logical work and 100% of the grunt

[Discuss-gnuradio] Portaudio

Some important fixes have been made in the last two weeks and that group is really starting to come alive since Audacity and Debian both threatened them with removal from their projects if they did not get their V19 version out the door. That has helped tremendously. I am adding