Re: [Discuss-gnuradio] problems with windows binaries and audio

[Achilleas Anastasopoulos]

Thanks Geof,

How exactly can I do what you are suggesting in GRC?
The only available controls on the audio sink is the bit rate and an entry
called "audio device".
What exactly should I enter in this entry?

thanks again,
Achilleas

On Sat, Nov 5, 2016 at 4:05 PM, Geof Nieboer  wrote:

> Achilleas,
>
> There are several others who had had success, so there must be something
> unique in your setup .  Do you have more then one audio device installed?
> If you do perhaps it is being routed to the wrong audio device.  The
> default is the windows wave mapper which normally should send it to your
> default audio device.  You can try specifying the audio device in the block
> settings.
>
> The audio -source- is not yet implemented but it will be in 3.7.10.2 when
> released
>
> Geof
>
>
> On Friday, November 4, 2016, Achilleas Anastasopoulos 
> wrote:
>
>> Hi,
>>
>> I have installed the windows binaries from GCNDevelopment
>> http://www.gcndevelopment.com/gnuradio/
>>
>> A simple test with a wav file and an audio sink does not seem to work.
>> I have changed the config file to use audio - windows but still this is
>> not working.
>> (same grc file works fine on Linux).
>> I have tried this on both Windows 7 and 10 with no success.
>>
>> Can someone report if they had success with audio on Windows with these
>> binaries?
>>
>> Any ideas as to what else I can try?
>>
>> thanks
>> Achilleas
>>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] problems with windows binaries and audio

[Geof Nieboer]

Achilleas,

There are several others who had had success, so there must be something
unique in your setup .  Do you have more then one audio device installed?
If you do perhaps it is being routed to the wrong audio device.  The
default is the windows wave mapper which normally should send it to your
default audio device.  You can try specifying the audio device in the block
settings.

The audio -source- is not yet implemented but it will be in 3.7.10.2 when
released

Geof

On Friday, November 4, 2016, Achilleas Anastasopoulos 
wrote:

> Hi,
>
> I have installed the windows binaries from GCNDevelopment
> http://www.gcndevelopment.com/gnuradio/
>
> A simple test with a wav file and an audio sink does not seem to work.
> I have changed the config file to use audio - windows but still this is
> not working.
> (same grc file works fine on Linux).
> I have tried this on both Windows 7 and 10 with no success.
>
> Can someone report if they had success with audio on Windows with these
> binaries?
>
> Any ideas as to what else I can try?
>
> thanks
> Achilleas
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Debugging ControlPort/Thrift problem (Re: costas ambiguity and correlate-and-sync block in qpsk)

[Andy Walls]

On Sun, 2016-04-03 at 13:01 -0400, Andy Walls wrote:
> >On April 3, 2016 11:31:02 AM EDT, Tom Rondeau wrote:
> >>On Sun, Apr 3, 2016 at 11:27 AM, Landsman, Arik wrote:

[snip]

>  Here is some good info on how GRNURadio's control port works at a
> >>high
>  level:
>  https://gnuradio.org/redmine/projects/gnuradio/wiki/ControlPort
> 
> >>
>  https://gnuradio.org/doc/doxygen/page_ctrlport.html
> 
> >>
> 
>  From that second page, it appears that running two flowgraphs on
> >the
>  same machine has a problem caused by Apache Thrift and GNURadio's
>  configuration of the Control Port network port (default of 9090).
> 
> >>https://gnuradio.org/doc/doxygen/page_ctrlport.html#ctrlport_thrift_issues
> 
> >>
> 
>  So please only run on flowgraph at a time, at first, to
> >troubleshoot
>  this issue.
> 
>  Second, you may want to try setting the GR_CONF_THRIFT_PORT
> >>environment
>  variable to something other than 9090, a port that you know is open
> >>on
>  your machine, for each separate flowgraph that you run.
> 
>  FYI, the modulate_vector block runs a "mini"-flowgraph, before the
> >>main
>  flowgraph actually runs:
> 
> 
> 
> >>https://github.com/gnuradio/gnuradio/blob/master/gr-digital/lib/modulate_vector.cc#L59
> 
> >>
> 
>  Hopefully, there isn't some sort of weird race condition with the
> >>Thrift
>  port being open for the modulate_vector block's mini-flowgraph and
> >>the
>  main flowgraph.
> 
> 
>  Hi Tom,
> 
>  Do you have any comments or insights on Arik's Thrift error message
>  and/or the possibility of modulate_vector's mini-flowgraph causing
>  problems with Thrift's network port and the main flowgraph?
> 
>  Regards,
>  Andy
> 
> >>>
> >>> Andy,
> >>>
> >>> I think you've got it on the Thrift issue. However, running the
> >>modulate
> >>> vector mini flowgraph first should kill itself immediately and free
> >>up the
> >>> port, so I don't think that's the problem. On the other hand, I've
> >>been
> >>> seeing issues recently where every time I launch GRC, it seems to
> >>cause a
> >>> conflict with whatever port I'm setting. Almost as though GRC is
> >>launching
> >>> something and holding on to the port specified in the thrift.conf
> >>file. I
> >>> thought this could just be a problem on my laptop (I've been
> >>traveling a
> >>> lot -- more than usual even -- and developing on my laptop can lead
> >>to me
> >>> doing a lot of crazy things), but I think I've since seen it on my
> >>office
> >>> workstation as well. That could be a problem here, too. We'll have
> >to
> >>track
> >>> that down.
> >>>
> >>> Using the GR_CONF_THRIFT_PORT variable is a good idea to set the
> >port
> >>per
> >>> flowgraph you're running. Another option is to set the port to 0 in
> >>> thrift.conf, which will cause Thrift to open an ephemeral port for
> >>each
> >>> server is creates. You'll just have to pay attention to the message
> >>output
> >>> that announces the ControlPort endpoint to find out what port it's
> >>running
> >>> on.
> >>>
> >>> Tom

OK, some I'm getting this runtime error at flowgraph startup
consistently:

"rpcmanager: Aggregator not in use, and a rpc booter is already registered"

strace shows that when the assetion stops the program, some block
threads have been spawned, but they are all waiting.  It's the main
program thread which emits this.

Running the flowgraph in gdb, and checking some of the relevant
variables in the stack frame:

(gdb) frame 6
#6  0x7fffeacc3376 in rpcmanager::register_booter (booter=)
at 
/home/andy/work/pybombs/src/gnuradio/gnuradio-runtime/lib/controlport/rpcmanager.cc:66
66  throw std::runtime_error("rpcmanager: Aggregator not in use, and a 
rpc booter is already registered\n");
(gdb) info locals
No locals.
(gdb) print rpcmanager::booter_registered
$1 = true
(gdb) print rpcmanager::aggregator_registered
$2 = false
(gdb) print rpcmanager::make_aggregator
$3 = false
(gdb)  print rpcmanager::aggregator
$4 = {_M_ptr = 0x0}
(gdb) print rpcmanager::boot
$5 = {_M_ptr = 0x0}


So two things strike me as a problem here:
1. booter_registered == true, but rpcmanager::boot == NULL
2. make_aggregator == false, and nowhere 

Re: [Discuss-gnuradio] 'cannot deliver port registration request' when using selector with jack

[Sjoerd Leijten]

Hi Marcus,

Thanks for your quick reply. I have attached the flowgraph to this e-mail,
so hopefully you can download it now. I have posted my problem also on the
jack forum, but since the error specifically occurs when I am working with
gnuradio and jack (using the selector and/or hierarchical blocks), I was
hoping for someone who is using gnuradio and jack in a similar manner. If
someone could test my flowgraph using jack as the audio server (and then
test the switching between mode 0 and 1), I would be very grateful.

Kind regards,

Sjoerd

On Sat, Nov 5, 2016 at 2:29 PM, Marcus Müller 
wrote:

> Hi Sjoerd,
>
> because you used Nabble, only half of your mails end up on the mailing
> list. Short: Nabble is a very strange service that you nobody needs if
> you have a mail address, just sign up directly for the mailing list
> under https://lists.gnu.org/mailman/listinfo/discuss-gnuradio .
>
> I couldn't download your GRC file from Nabble – it just kept forwarding
> me to a spam site. Please don't use nabble.
>
> So, anyway, your original question, copy and pasted from Nabble, was
>
> > I am trying to create a multimode receiver flowgraph which uses a
> > selector to switch between am and fm. I use jack to be able to route
> > the audio to other software for further processing. The trouble that I
> > am having is that - as soon as I switch -  jack gives me a "cannot
> > deliver port registration request". I have tried to get around this by
> > creating a python script and unregister the port with
> > "jack_unregister", but that did not work out. In total despair I also
> > tried to pipe the audio via udp to another flowgraph with a jack audio
> > sink, but that caused other problems and it seems like an ugly hack.
>
> Hm, in theory, the Jack sink should handle
> stopping/starting/reconfiguration gracefully. Now, I'm sadly really no
> expert in Jack – maybe it's an easy fix to the Jack sink [1], but maybe
> it isn't. You could have both AM and FM flowgraphs run parallely, and
> multiply one with a constant 0 and the other with a constant 1 and add
> both up – that way, you wouldn't have to reconfigure the flow graph.
>
>
> Best regards,
>
> Marcus
>
>
> [1] https://github.com/gnuradio/gnuradio/tree/master/gr-audio/lib/jack
>
> On 05.11.2016 12:50, Sjoerd wrote:
> > A possible solution could be that the audio sink does not instantiate a
> > normal jack port, but a 'Jack.ownPort' - which has more options and I
> > suspect that I would have control over the registration of the ports.
> Since
> > I don't have experience with editing existing gnuradio blocks - maybe
> > someone could point out to me how to approach this...? What block or
> script
> > should I edit to accomplish this?
> >
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>



-- 
--
+31 642221640
www.sjoerdleijten.nl


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

Re: [Discuss-gnuradio] 'cannot deliver port registration request' when using selector with jack

[Marcus Müller]

Hi Sjoerd,

because you used Nabble, only half of your mails end up on the mailing
list. Short: Nabble is a very strange service that you nobody needs if
you have a mail address, just sign up directly for the mailing list
under https://lists.gnu.org/mailman/listinfo/discuss-gnuradio .

I couldn't download your GRC file from Nabble – it just kept forwarding
me to a spam site. Please don't use nabble.

So, anyway, your original question, copy and pasted from Nabble, was

> I am trying to create a multimode receiver flowgraph which uses a
> selector to switch between am and fm. I use jack to be able to route
> the audio to other software for further processing. The trouble that I
> am having is that - as soon as I switch -  jack gives me a "cannot
> deliver port registration request". I have tried to get around this by
> creating a python script and unregister the port with
> "jack_unregister", but that did not work out. In total despair I also
> tried to pipe the audio via udp to another flowgraph with a jack audio
> sink, but that caused other problems and it seems like an ugly hack.

Hm, in theory, the Jack sink should handle
stopping/starting/reconfiguration gracefully. Now, I'm sadly really no
expert in Jack – maybe it's an easy fix to the Jack sink [1], but maybe
it isn't. You could have both AM and FM flowgraphs run parallely, and
multiply one with a constant 0 and the other with a constant 1 and add
both up – that way, you wouldn't have to reconfigure the flow graph.


Best regards,

Marcus


[1] https://github.com/gnuradio/gnuradio/tree/master/gr-audio/lib/jack

On 05.11.2016 12:50, Sjoerd wrote:
> A possible solution could be that the audio sink does not instantiate a
> normal jack port, but a 'Jack.ownPort' - which has more options and I
> suspect that I would have control over the registration of the ports. Since
> I don't have experience with editing existing gnuradio blocks - maybe
> someone could point out to me how to approach this...? What block or script
> should I edit to accomplish this? 
>

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

Re: [Discuss-gnuradio] 'cannot deliver port registration request' when using selector with jack

[Sjoerd]

A possible solution could be that the audio sink does not instantiate a
normal jack port, but a 'Jack.ownPort' - which has more options and I
suspect that I would have control over the registration of the ports. Since
I don't have experience with editing existing gnuradio blocks - maybe
someone could point out to me how to approach this...? What block or script
should I edit to accomplish this? 



--
View this message in context: 
http://gnuradio.4.n7.nabble.com/cannot-deliver-port-registration-request-when-using-selector-with-jack-tp61899p61900.html
Sent from the GnuRadio mailing list archive at Nabble.com.

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

Re: [Discuss-gnuradio] problems with windows binaries and audio

[Marcus Müller]

Hi Achilleas,

it's nice to be hearing from you :)

So, I know of at least one other person trying [1] to get audio under
Windows to work correctly. At least, he got /choppy/ sound.

I know this isn't great help, but maybe it gives any of you a place to
start :(

Best regards,

Marcus

[1]
http://stackoverflow.com/questions/40367217/gnu-radio-sine-generator-audio-soundcard-intermittent-sound


On 05.11.2016 01:45, Achilleas Anastasopoulos wrote:
> Hi,
>
> I have installed the windows binaries from GCNDevelopment
> http://www.gcndevelopment.com/gnuradio/
>
> A simple test with a wav file and an audio sink does not seem to work.
> I have changed the config file to use audio - windows but still this
> is not working.
> (same grc file works fine on Linux).
> I have tried this on both Windows 7 and 10 with no success.
>
> Can someone report if they had success with audio on Windows with
> these binaries?
>
> Any ideas as to what else I can try?
>
> thanks
> Achilleas
>
>
> ___
> 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