I just got my hands on 2 Pi 4 kits.
One setup, one just nearing completion of initial setup. The first thing I
want to test is openob on both ends.
Has anyone doe this yet? If so, same procedure as for Pi 3 or are there any
quirks?
all the best,
drew
--
Enjoy the *Paradise Island Cam* playing
*Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
Chris,
On Wed, Jan 15, 2020 at 5:24 AM Sojo Gold <sojogold(a)gmail.com> wrote:
> Hi Drew,
> I will try and catch you on IRC ...but not today.
>
WHen you can then.
>
> I have setup jack as you indicated and copied your openOB command line to
> both TX and RX.
> Now I have openOB reporting a stereo transmission..but I have no sound
> from the RX pc.
> Using Audacity to show recording on both TX & RX pc's.
>
So, if you try and record *input* audio on each pc with audacity and no
openob running, do you see stereo in on both? (That is a stereo waveform in
the display, not a mono display?) As an additional check, if you record a
stereo signal that has obvious left right sides, do they show up in the
recording?
> I can record the input audio on the TX pc however not on the RX ie no
> sound out.
>
I don't understand exactly what you mean by this. Is this your audacity
test? Of something you are trying with openob now in the mix? Did you set
jack instead of alsa to the right of the mic as the sound system to record
on each machine when testing?
> The RX pc will play out a local saved audio file okay.
>
> Could you confirm the pulseaudio control (pavucontrol) settings... as when
> comparing TX with RX ...RX I appear to have the same settings in both.
>
Sorry, I don't think I can. I only have access to the one side for about
another week. I will poke around and see if I can find a backup tx machine
if I get some time.
> Audacity devices on TX is simply shows as "default" but on RX for some
> reason "default" cannot be found in the list.
>
Check that you are using jack and not alsa in audacity.
> Hmm...
> pavucontrol - output devices - on RX pc shows..
> PCM2902 Audio Codec Analogue Stereo - port: Analogue Output
> Jack sink (PulseAudio JACK Sink) as fallback.
>
I am showing Built in ... (HDMI)
and
PCM2902 Audio Codec Analogue Stereo - port: Analogue Output
Not seeing anything like Jack sink (PulseAudio JACK Sink) as fallback.
>
> pavucontrol - output devices - on TX pc shows.. exactly the same.
>
> hope this makes sense..I will try and setup a time slot to IRC you in the
> next few days.
>
If you look at qjackctl connections window when openob is up, is openob
connected sensibly on each end? Does it even show up in the jack graph on
both ends?
>
> Thanks and much appreciated.
> Chris P.
>
all the best,
drew
>
>
>
>
> On 14/01/2020 15:21, drew Roberts wrote:
>
> Chris,
>
> This might be easier to do interactively. I am in the IRC channel
> #rivendell on freenode. Look for zotz.
> You could try #openob as well...
>
> I use xchat on linux. If you use a different os, find a client for your os.
>
> Or you could try this web client:
> https://webchat.freenode.net/
>
> Freenode's main page:
> https://freenode.net/
>
> Some hints below in case you miss me there...
>
> On Tue, Jan 14, 2020 at 8:40 AM Sojo Gold <sojogold(a)gmail.com> wrote:
>
>> Hi Drew,
>>
>> I have installed Jack on both TX and RX PC's. Have used pavucontrol to
>> disable the built-in sound card of both PC's.
>>
>
> First things first. We will leave openob out of the equation.
>
> I suggest you use qjackctl to do this.
>
> Start qjackctl. Make sure jack is stopped. Go to setup. On the settings
> tab, choose the alsa driver, choose the correct interface, my uca222/uca202
> (front / back) shows as hw:CODEC, choose you sample rate, I have 48000,
> chose your frames/period, I have 2048, choose your periods/buffer, I have 3.
>
> Save the changes. Click start on the main qjackctl window.
>
> Start something that can record audio from jack. audacity, jack time
> machine, ardour, whatever. Record some audio and make sure you have stereo.
>
> Do this at both ends to ensure you have jack capable of doing stereo at
> each end.
>
> Now try and get openob working correctly at each end.
>
> This may give a clue as to what your receive end might look like:
>
> /usr/local/bin/openob 10.8.0.1 test-rx-node test-link rx -a jack -jn
> openob -aj -jp jack_mixer:ICh2
>
>
> all the best,
>
> drew
>
>
>> Jack Audio Connection Kit - Connections - Audio tab show Out's as
>> PulseAudio JACK Sink, front left/front right, to -----> IN's as PulseAudio
>> JACK Source - System - playback_1/playback_2 receptively.
>>
>> OpenOB still sends audio okay but is till Mono.
>>
>> I'm pretty convinced the TX Opus capability parameters has been
>> misconfigured..
>> i.e.. the log at startup shows sprop-stereo-(string)0 which is Mono.
>>
>> see here:
>>
>> *2020-01-13 19:29:55,538 - openob.link.STUDIO-link.config - DEBUG - Set
>> openob:STUDIO-link:caps to application/x-rtp, media=(string)audio,
>> clock-rate=(int)48000, encoding-name=(string)OPUS,
>> sprop-maxcapturerate=(string)48000, sprop-stereo=(string)0,
>> payload=(int)96, encoding-params=(string)2, ssrc=(uint)1869211510,
>> timestamp-offset=(uint)2778079888, seqnum-offset=(uint)6787*
>>
>> *2020-01-13 19:29:56,452 - openob.node.test-tx-node.link.STUDIO-link.tx -
>> INFO - Started mono audio transmission*
>>
>>
>> *well still getting my head around JACK.. do I need to set parameters in
>> the openOB command line..??*
>>
>> *cheers for you input, much appreciated.*
>>
>>
>> *Chris P. *
>>
>>
>>
>> On 13/01/2020 23:01, drew Roberts wrote:
>>
>> Chris,
>>
>> if you machine is "strong" enough to run jack, it should get you up and
>> running until you figure things out and it may be a final solution as well.
>>
>> If you need any further help, ask me on list and I would be happy to see
>> what help I can provide.
>>
>> drew
>>
>> On Mon, Jan 13, 2020 at 12:12 PM Sojo Gold <sojogold(a)gmail.com> wrote:
>>
>>> Hi Drew,
>>> Thanks for the feedback...hmmm will need to look at JACK then..
>>> Chris.
>>>
>>> On 13/01/2020 13:44, drew Roberts wrote:
>>>
>>> I can't give you a solution but I can tell you what I did as a
>>> workaround when time was running short for me.
>>>
>>> I put jack in the mix on both ends.
>>>
>>> Someone had suggested that I edit an alsa config file. I can't remember
>>> the results of that. My setup was perhaps not exactly parallel to the
>>> suggested fix and I did not have time to dig deeper. You can perhaps search
>>> the list archive for the discussion.
>>>
>>> In any case, once I had jack in the mix, I got stereo where I had mono
>>> before.
>>>
>>> all the best,
>>>
>>> drew
>>>
>>> On Mon, Jan 13, 2020 at 7:38 AM Sojo Gold <sojogold(a)gmail.com> wrote:
>>>
>>>> Hi,
>>>> Thanks to the amazing work and dedication to this wonderful project
>>>> from some awesome engineers, I, as one of the somewhat inexperienced , have
>>>> managed to create a working link using two Linux Mint v19.3 PC's for our
>>>> cash strapped community radio station. Thank you.
>>>> I have a small query and a related question.
>>>>
>>>> Using the default test command line on both PC's, INFO on the TX PC
>>>> reports "Started mono audio transmission"* BEFORE* I had started the
>>>> RX PC link. This was a bit confusing, however, there was no audio until the
>>>> RX link was started.
>>>>
>>>> I tested the link once established, for separation and found it is
>>>> actually Mono!. I'm using default ALSA driver and two Behringer UCA-202's.
>>>> I appreciate this is only the default settings and probably should use
>>>> command line configuration options but in a previous version OpenOB worked
>>>> as stereo "out of the box" using defaults. Has something changed in this
>>>> regard.
>>>>
>>>> So, is there any sort of tutorial on using the CL parameters. I am
>>>> aware of the "Further Usage" paragraph referring to '*openob -h*' etc
>>>> but wondered if there was something more in depth to help me fix the Mono
>>>> problem.
>>>>
>>>> Anything much appreciated.
>>>>
>>>> Chris Perkins
>>>> Flame Radio
>>>> Wirral
>>>>
>>>>
>>>> _______________________________________________
>>>> openob-users mailing list -- openob-users(a)lists.talkunafraid.co.uk
>>>> To unsubscribe send an email to
>>>> openob-users-leave(a)lists.talkunafraid.co.uk
>>>>
>>>
>>>
>>> --
>>> Enjoy the *Paradise Island Cam* playing
>>> *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
>>>
>>>
>>>
>>
>> --
>> Enjoy the *Paradise Island Cam* playing
>> *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
>>
>>
>>
>
> --
> Enjoy the *Paradise Island Cam* playing
> *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
>
>
>
--
Enjoy the *Paradise Island Cam* playing
*Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
Hi,
Thanks to the amazing work and dedication to this wonderful project from
some awesome engineers, I, as one of the somewhat inexperienced , have
managed to create a working link using two Linux Mint v19.3 PC's for our
cash strapped community radio station. Thank you.
I have a small query and a related question.
Using the default test command line on both PC's, INFO on the TX PC
reports "Started mono audio transmission"/BEFORE/ I had started the RX
PC link. This was a bit confusing, however, there was no audio until the
RX link was started.
I tested the link once established, for separation and found it is
actually Mono!. I'm using default ALSA driver and two Behringer
UCA-202's. I appreciate this is only the default settings and probably
should use command line configuration options but in a previous version
OpenOB worked as stereo "out of the box" using defaults. Has something
changed in this regard.
So, is there any sort of tutorial on using the CL parameters. I am aware
of the "Further Usage" paragraph referring to '*openob -h*' etc but
wondered if there was something more in depth to help me fix the Mono
problem.
Anything much appreciated.
Chris Perkins
Flame Radio
Wirral
