13 Jan
2020
13 Jan
'20
12:38 p.m.
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
13 Jan
13 Jan
1:44 p.m.
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/
2:18 p.m.
On 13/01/2020 20:38, Sojo Gold wrote:
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.
G'day,
Here is out tx command:
/usr/bin/python /usr/local/bin/openob redis st_just_tx st_just_stl tx
heliades -ajack -b 256 --jack_name st_just_stl --jack_port_pattern
system:capture
and here is the corresponding rx command:
/usr/bin/python /usr/local/bin/openob 10.222.0.26 st_just_rx st_just_stl rx
Note that we use jack at the tx end but not the rx end. Only because we
have various other audio things hanging of the audio input, like ROT and
silence detection.
Here is another link used for OB, tx is:
/usr/bin/python /usr/local/bin/openob redis ob_tx ob_inbound tx tantive
-aalsa -d hw:1,0 -b 256
rx is:
/usr/bin/python /usr/local/bin/openob redis ob_rx ob_inbound rx
No jack in use here.
I would suggest you try recording something use arecord and see if the
input you have is mono which could point to a cable issue or soundcard
issue.
I don't know how it knows the audio is mono.
What does alsamixer show?
Did you search for uca202 and mono? Seems to be a common problem.
Seems that it thinks a microphone is in use... maybe
arecord -L or arecord -l may give other devices to use. (I think this is
most likely reason you have mono, you are using the wrong hardware device.)
--
Mike Phillips
Coast FM.
1956
days inactive
1956
days old
openob-users@lists.talkunafraid.co.uk
2 comments
3 participants
participants (3)
-
drew Roberts -
Mike Phillips -
Sojo Gold