USB fob choppy/stuttering audio

Joe_C · April 1, 2019, 12:51am

Hi Steve

Very well put, I didn’t know there were two different platforms and i will set up the other platform as well. I do hope going forward the two can work this out. Sorry if I caused unnecessary non sense for my lack of knowledge.

73, 75

Joe

K2OL

···

On Mar 31, 2019, at 8:00 PM, Steve L kb9mwr@gmail.com wrote:

What would be very beneficial to all is when you post a question on any list (be it Allstar or whatever); is to identify and share as much as you can in terms of software you are running as well as hardware.

Example:

ASL 1.01 Raspbian Stretch Image on a Raspberry Pi 2b

Interface:

DMK USB URI

Radio:

Motorola Maxtrac

Issue:

Choppy Transmit audio

Since there are multiple combinations of software and hardware, folks really need to elaborate. No one is a mind reader. It would help if you are running the hamvoip image to post the question to their list at:

http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Since there are a number of differences between the distros and the fact theirs is closed, one cannot even begin to really guess at what the issues might be as as you cannot see what is different at a code level even if you share as much detail about your configs.

In my opinion each can have its place (one for more experienced users which to be able to roll their own/experiment and one for fairly new to Linux), however I would rather at some point see the two groups work together again. Till such a time users just need to realize what they are running, and who to go to for support, else it just creates a guessing game and further hostility.

App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

Rob_Noll · April 1, 2019, 12:51am

Nothing in lsusb’s output is representative of the info in the devstr line in the usb conf file. The device line is a single digit number as is one of the data points displayed by lsusb, however, the device line is commented out in every usb conf file I’ve looked at.

···

**From: **
Steve L kb9mwr@gmail.com
**Sent: **
March 31, 2019 20:48:09
**To: **
Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org
**Subject: **
Re: [App_rpt-users] USB fob choppy/stuttering audio
No problem and for future reference:

lsusb is a utility for displaying information about USB buses in the system and the devices connected to them.

https://linux.die.net/man/8/lsusb

On Sun, Mar 31, 2019 at 7:11 PM Rob Noll rob@nollmail.com wrote:

Thanks for the reply. I didn’t wish to name the USB device as I didn’t want to appear to be giving it a bad name if it was not the culprit. Sorry you feel I didn’t give enough information to begin narrowing down the problem.

At a suggestion I received elsewhere, I tried HamVoIP to see if the issue was the same. The audio is perfect with HamVoIP. Since I’d rather implement this setup on an existing Debian system instead of having a dedicated device, I’d like to try to figure out a way to get ASL working with this device. One gentleman suggested looking into the device ID and making sure it was correct, however, he didn’t know how to determine the correct information. At any rate, some light reading has informed me that there seems to be some serious bad blood between HamVoIP and ASL, so since I’ve gotten to the point where the issues exists in one but not the other, and is therefore in the software and not the hardware (be it the cpu, radio, or interface), I suspect I’m better off trying to figure it out on my own.

Thanks to everyone who took the time to respond.

Rob

**From: **
Steve L kb9mwr@gmail.com
**Sent: **
March 31, 2019 20:01:00
**To: **
Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org
**Subject: **
Re: [App_rpt-users] USB fob choppy/stuttering audio
What would be very beneficial to all is when you post a question on any list (be it Allstar or whatever); is to identify and share as much as you can in terms of software you are running as well as hardware.

Example:

ASL 1.01 Raspbian Stretch Image on a Raspberry Pi 2b

Interface:

DMK USB URI

Radio:

Motorola Maxtrac

Issue:

Choppy Transmit audio

Since there are multiple combinations of software and hardware, folks really need to elaborate. No one is a mind reader. It would help if you are running the hamvoip image to post the question to their list at:

http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Since there are a number of differences between the distros and the fact theirs is closed, one cannot even begin to really guess at what the issues might be as as you cannot see what is different at a code level even if you share as much detail about your configs.

In my opinion each can have its place (one for more experienced users which to be able to roll their own/experiment and one for fairly new to Linux), however I would rather at some point see the two groups work together again. Till such a time users just need to realize what they are running, and who to go to for support, else it just creates a guessing game and further hostility.

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”

You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”

You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”

You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

Mike · April 1, 2019, 1:07am

It denoteds the bus/hub and port on the bus/hub

  Each bus uses one irq line in addressing, so if there is a

problem, switch buses not ports.

There are 2 ports generally, to each bus/hub.

Perhaps this helps :

lsusb

Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  Bus 003 Device 002: ID 0d8c:000c C-Media Electronics, Inc. Audio

Adapter <---------

  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

usbradio_tune_29285.conf

[usb_29285]

  ; name=usb_29285

  ; devicenum=2

  devstr=3-2� <-----------

  rxmixerset=700

  txmixaset=300

  txmixbset=300

  rxvoiceadj=0.950000

  rxctcssadj=1.200000

  txctcssadj=200

  rxsquelchadj=400

…mike/kb8jnm

···

On 3/31/2019 8:51 PM, Rob Noll wrote:

      Nothing in lsusb's output is representative of
the info in the devstr line in the usb conf file. T he device line is a single digit
number as is one of the data points displayed by lsusb,
however, the device line is commented out in every usb conf
file I’ve looked at.

From:�
Steve L
Sent:�
March 31, 2019 20:48:09
To:�
Users of Asterisk app_rpt
Subject:�
Re: [App_rpt-users] USB fob
choppy/stuttering audio
No problem and for future reference:

lsusb is a utility for displaying
information about USB buses in the system and the
devices connected to them.

https://linux.die.net/man/8/lsusb

              On Sun, Mar 31, 2019
at 7:11 PM Rob Noll <rob@nollmail.com >
wrote:

                    Thanks for the reply.� I didn't
wish to name the USB device as I didn’t want to
appear to be giving it a bad name if it was not
the culprit. Sorry you feel I didn’t give enough
information to begin narrowing down the problem.

                    At a suggestion I received
elsewhere, I tried HamVoIP to see if the issue
was the same.� The audio is perfect with
HamVoIP. Since I’d rather implement this setup
on an existing Debian system instead of having a
dedicated device, I’d like to try to figure out
a way to get ASL working with this device.� One
gentleman suggested looking into the device ID
and making sure it was correct, however, he
didn’t know how to determine the correct
information.� At any rate, some light reading
has informed me that there seems to be some
serious bad blood between HamVoIP and ASL, so
since I’ve gotten to the point where the issues
exists in one but not the other, and is
therefore in the software and not the hardware
(be it the cpu, radio, or interface), I suspect
I’m better off trying to figure it out on my
own.

                    Thanks to everyone who took the

time to respond.

Rob

From:�
Steve L kb9mwr@gmail.com
Sent:�
March 31, 2019
20:01:00
To:�
Users of Asterisk
app_rpt app_rpt-users@lists.allstarlink.org
Subject:�
Re: [App_rpt-users]
USB fob choppy/stuttering audio
What would be very beneficial
to all is when you post a question
on any list (be it Allstar or
whatever); is to identify and
share as much as you can in terms
of software you are running as
well as hardware.

Example:

                                  ASL 1.01 Raspbian Stretch Image

on a Raspberry Pi 2b

Interface:

DMK USB URI

Radio:

Motorola Maxtrac

Issue:

Choppy Transmit audio

                                  Since there are multiple
combinations of software and
hardware, folks really need to
elaborate.� No one is a mind
reader.� It would help if you are
running the hamvoip image to post
the question to their list at:

http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

                                  Since there are a number of
differences between the distros
and the fact theirs is closed, one
cannot even begin to really guess
at what the issues might be as as
you cannot see what is different
at a code level even if you share
as much detail about your
configs.�

                                  In my opinion each can have its
place (one for more experienced
users which to be able to roll
their own/experiment and one for
fairly new to Linux), however I
would rather at some point see the
two groups work together again.�
Till such a time users just need
to realize what they are running,
and who to go to for support, else
it just creates a guessing game
and further hostility.

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

                          To unsubscribe from this list please
visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
and scroll down to the bottom of the page.
Enter your email address and press the
“Unsubscribe or edit options button”

                          You do not need a password to
unsubscribe, you can do it via email
confirmation. If you have trouble
unsubscribing, please send a message to
the list detailing the problem.

              App_rpt-users mailing list

              App_rpt-users@lists.allstarlink.org

              [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)



              To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)
              and scroll down to the bottom of the page. Enter your

email address and press the “Unsubscribe or edit
options button”

              You do not need a password to unsubscribe, you can do

it via email confirmation. If you have trouble
unsubscribing, please send a message to the list
detailing the problem.

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
and scroll down to the bottom of the page. Enter your
email address and press the “Unsubscribe or edit options
button”

            You do not need a password to unsubscribe, you can do
it via email confirmation. If you have trouble
unsubscribing, please send a message to the list
detailing the problem.

kb9mwr@gmail.comapp_rpt-users@lists.allstarlink.org


_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

Rob_Noll · April 1, 2019, 1:10am

Perfect, thanks Mike. The auto generated usb conf files also have a decimal point, another numeral, a colon, and another numeral. Any idea what those represent, and if they should be present?

···

On 3/31/2019 8:51 PM, Rob Noll wrote:

      Nothing in lsusb's output is representative of
the info in the devstr line in the usb conf file. T he device line is a single digit
number as is one of the data points displayed by lsusb,
however, the device line is commented out in every usb conf
file I’ve looked at.

**From: **
Steve L
**Sent: **
March 31, 2019 20:48:09
**To: **
Users of Asterisk app_rpt
**Subject: **
Re: [App_rpt-users] USB fob
choppy/stuttering audio
No problem and for future reference:

lsusb is a utility for displaying
information about USB buses in the system and the
devices connected to them.

https://linux.die.net/man/8/lsusb

              On Sun, Mar 31, 2019
at 7:11 PM Rob Noll <rob@nollmail.com >
wrote:

                    Thanks for the reply.  I didn't
wish to name the USB device as I didn’t want to
appear to be giving it a bad name if it was not
the culprit. Sorry you feel I didn’t give enough
information to begin narrowing down the problem.

                    At a suggestion I received
elsewhere, I tried HamVoIP to see if the issue
was the same. The audio is perfect with
HamVoIP. Since I’d rather implement this setup
on an existing Debian system instead of having a
dedicated device, I’d like to try to figure out
a way to get ASL working with this device. One
gentleman suggested looking into the device ID
and making sure it was correct, however, he
didn’t know how to determine the correct
information. At any rate, some light reading
has informed me that there seems to be some
serious bad blood between HamVoIP and ASL, so
since I’ve gotten to the point where the issues
exists in one but not the other, and is
therefore in the software and not the hardware
(be it the cpu, radio, or interface), I suspect
I’m better off trying to figure it out on my
own.

                    Thanks to everyone who took the

time to respond.

Rob

**From: **
Steve L kb9mwr@gmail.com
**Sent: **
March 31, 2019
20:01:00
**To: **
Users of Asterisk
app_rpt app_rpt-users@lists.allstarlink.org
**Subject: **
Re: [App_rpt-users]
USB fob choppy/stuttering audio
What would be very beneficial
to all is when you post a question
on any list (be it Allstar or
whatever); is to identify and
share as much as you can in terms
of software you are running as
well as hardware.

Example:

                                  ASL 1.01 Raspbian Stretch Image

on a Raspberry Pi 2b

Interface:

DMK USB URI

Radio:

Motorola Maxtrac

Issue:

Choppy Transmit audio

                                  Since there are multiple
combinations of software and
hardware, folks really need to
elaborate. No one is a mind
reader. It would help if you are
running the hamvoip image to post
the question to their list at:

http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

                                  Since there are a number of
differences between the distros
and the fact theirs is closed, one
cannot even begin to really guess
at what the issues might be as as
you cannot see what is different
at a code level even if you share
as much detail about your
configs.

                                  In my opinion each can have its
place (one for more experienced
users which to be able to roll
their own/experiment and one for
fairly new to Linux), however I
would rather at some point see the
two groups work together again.
Till such a time users just need
to realize what they are running,
and who to go to for support, else
it just creates a guessing game
and further hostility.

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

                          To unsubscribe from this list please
visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
and scroll down to the bottom of the page.
Enter your email address and press the
“Unsubscribe or edit options button”

                          You do not need a password to
unsubscribe, you can do it via email
confirmation. If you have trouble
unsubscribing, please send a message to
the list detailing the problem.

              App_rpt-users mailing list

              App_rpt-users@lists.allstarlink.org

              [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)



              To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)
              and scroll down to the bottom of the page. Enter your

email address and press the “Unsubscribe or edit
options button”

              You do not need a password to unsubscribe, you can do

it via email confirmation. If you have trouble
unsubscribing, please send a message to the list
detailing the problem.

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
and scroll down to the bottom of the page. Enter your
email address and press the “Unsubscribe or edit options
button”

            You do not need a password to unsubscribe, you can do
it via email confirmation. If you have trouble
unsubscribing, please send a message to the list
detailing the problem.

kb9mwr@gmail.comapp_rpt-users@lists.allstarlink.org


_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”

You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

eric.fort.listmail · April 1, 2019, 5:41am

Rob,

It was not my intent to “dump on” you for what does indeed seem to be a well known but poorly documented problem. I simply was posing a question as to why so many have chosen the path of usb when stable and well engineered solutions that have not these problems came before and worked so well. It was not meant or intended to be directed at you specifically and if it seemed that way I apologize. I realize that the Raspberry pi only leaves us with using usb as an option. I personally look at that and would say that then maybe the Raspberry pi isn’t the best platform to be using and maybe we ought look at better and more robust hardware options such as the single board computers that have multi channel tdm based sound busses and dual programmable real-time subsystem processors where hardware can be built and interfaced based on proven tdm bus concepts. Again this is not a reflection on you, it’s intended as a general query as to why things are as they are. Marshal gave a good reply to that and it seems to be an issue of cost. It also seems to be one gets what they are willing to pay for. Maybe we could document this better, maybe we could work on updating some hardware designs so we have a viable alternative to usb. Theese seem like areas worth looking at. As for your current issue with usb. Again this query is not pointed at you, but more generally why things are as they are, and what may be done about it.

Eric

Af6ep

Sent using SMTP.

···

On Mar 31, 2019, at 10:01 AM, Rob Noll rob@nollmail.com wrote:

I’m looking for assistance solving this issue, and particularly how to check the device string in the configuration file, and/or how to change the sample rate of the audio stream sent to USB.

I’m not sure why you chose to unload on me for what you seem to be claiming is a well known issue, but from my searching does not appear to be well publicized. Nor am I sure what I may have said that would cause antagonization. I was merely looking for some assistance with an issue that I hoped maybe others had encountered and knew of a cause or solution.

That said, here are some answers to your questions:

why does it seem that most everyone has gone this route against the above sage wisdom

Where is this sage wisdom? I’m new to ASL. I read the wiki page. I saw no warnings against USB, in fact, I there were links to USB devices.

rather than using something more akin an e&m interface like the pci radio cards Jim designed

I don’t know Jim, don’t know where to buy his products, and there are no PCI interfaces on a Raspberry Pi.

the interface boards that plugged into an fxs? Port and broke out e&m, providing keying by polarity reversal of the battery voltage

An fxs port is an analog telephone port, isn’t it? Again, not available on a Raspberry Pi, and although I’m sure I could come up with a way to key the transmitter in question based on a reverse polarity battery signal, that does not seem like a very straightforward undertaking.

Apparently usb not so much and apparently this is a long standing problem with usb

I disagree. I’ve used plenty of USB audio devices in the past with no problems whatsoever. In fact, this very device works fine when used as a sound card on a PC. So if there are any longstanding issues, it would appear from a cursory glance to be with asterisk’s passing of the audio.

From: App_rpt-users app_rpt-users-bounces@lists.allstarlink.org On Behalf Of Eric Fort
Sent: Sunday, March 31, 2019 12:49
To: Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] USB fob choppy/stuttering audio

On Mar 31, 2019, at 9:08 AM, Bob Pyke k6ecm1@gmail.com wrote:

Sorry, not with ASL. I found it best to let it set it, but I check to make sure. ASL is much better than the original based on CentOS. I’ve had the Linux mix it up, but not had that issue since DIAL and ASL.

As Jim has said many times, “friends don’t let friends do USB”

Thanks,

Bob

K6ECM

73

I have heard many times of the problems using usb with asterisk and app_rpt. So why does it seem that most everyone has gone this route against the above sage wisdom rather than using something more akin an e&m interface like the pci radio cards Jim designed and built or the interface boards that plugged into an fxs? Port and broke out e&m, providing keying by polarity reversal of the battery voltage. Both solutions work rock solid with no issues. Apparently usb not so much and apparently this is a long standing problem with usb. In thinking about this I’m also curious if the design files for the pci radio interface boards may be available as they’d likely be a good start for an update to a more current interface standard.

Eric

Af6ep

App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

Rob_Noll · April 1, 2019, 9:27am

Good morning Eric,

Thank you for the clarification. Apology accepted.

Yes, generally you get what you pay for, no argument there. However, since I’m just working on a side project that may or may not take off, it wasn’t worth sinking much money into. It was something inexpensive, or nothing. This is ham radio - sometimes experimentation and overcoming hurdles is better than throwing money at a prepackaged solution.

I had thought that perhaps I was overlooking something simple and it would be an issue that others had run into and solved before. Given the overall tone of the responses I’ve received, apparently I’ve opened up a can of worms.

Since the USB device works fine when tested as a sound card, and also works fine with the HamVoIP software, I think it’s safe to say that the issue lies with the ASL software. But since that is it’s own can of worms, I’m just going to go my merry way and hope that it gets fixed some day.

Rob

···

On Mar 31, 2019, at 10:01 AM, Rob Noll rob@nollmail.com wrote:

I’m looking for assistance solving this issue, and particularly how to check the device string in the configuration file, and/or how to change the sample rate of the audio stream sent to USB.

I’m not sure why you chose to unload on me for what you seem to be claiming is a well known issue, but from my searching does not appear to be well publicized. Nor am I sure what I may have said that would cause antagonization. I was merely looking for some assistance with an issue that I hoped maybe others had encountered and knew of a cause or solution.

That said, here are some answers to your questions:

why does it seem that most everyone has gone this route against the above sage wisdom

Where is this sage wisdom? I’m new to ASL. I read the wiki page. I saw no warnings against USB, in fact, I there were links to USB devices.

rather than using something more akin an e&m interface like the pci radio cards Jim designed

I don’t know Jim, don’t know where to buy his products, and there are no PCI interfaces on a Raspberry Pi.

the interface boards that plugged into an fxs? Port and broke out e&m, providing keying by polarity reversal of the battery voltage

An fxs port is an analog telephone port, isn’t it? Again, not available on a Raspberry Pi, and although I’m sure I could come up with a way to key the transmitter in question based on a reverse polarity battery signal, that does not seem like a very straightforward undertaking.

Apparently usb not so much and apparently this is a long standing problem with usb

I disagree. I’ve used plenty of USB audio devices in the past with no problems whatsoever. In fact, this very device works fine when used as a sound card on a PC. So if there are any longstanding issues, it would appear from a cursory glance to be with asterisk’s passing of the audio.

From: App_rpt-users app_rpt-users-bounces@lists.allstarlink.org On Behalf Of Eric Fort
Sent: Sunday, March 31, 2019 12:49
To: Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] USB fob choppy/stuttering audio

On Mar 31, 2019, at 9:08 AM, Bob Pyke k6ecm1@gmail.com wrote:

Sorry, not with ASL. I found it best to let it set it, but I check to make sure. ASL is much better than the original based on CentOS. I’ve had the Linux mix it up, but not had that issue since DIAL and ASL.

As Jim has said many times, “friends don’t let friends do USB”

Thanks,

Bob

K6ECM

73

I have heard many times of the problems using usb with asterisk and app_rpt. So why does it seem that most everyone has gone this route against the above sage wisdom rather than using something more akin an e&m interface like the pci radio cards Jim designed and built or the interface boards that plugged into an fxs? Port and broke out e&m, providing keying by polarity reversal of the battery voltage. Both solutions work rock solid with no issues. Apparently usb not so much and apparently this is a long standing problem with usb. In thinking about this I’m also curious if the design files for the pci radio interface boards may be available as they’d likely be a good start for an update to a more current interface standard.

Eric

Af6ep

App_rpt-users mailing list
App_rpt-users@lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

KE6PCV · April 1, 2019, 8:10pm

Rob,

Based on your comments about the telemetry “not sounding choppy when listening to it over the phone.”

It could be that RF from your transmitter is getting into your sound fob. Do you have a transmitter hooked up to the USB sound fob?

As a test, disable your transmitter and use clip leads to connect a PC amplified computer speaker to your TX audio line and see if you still have choppy audio.

If you do NOT have choppy audio with the amplified speaker, this surely points to some type of RF getting into your sound fob.

Hope this helps.

73

Marshall - ke6pcv

···

From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Rob Noll
Sent: Sunday, March 31, 2019 7:26 AM
To: app_rpt-users@lists.allstarlink.org
Subject: [App_rpt-users] USB fob choppy/stuttering audio

Good morning all,

I’m trying to set up an AllStar node using a USB fob based on the CM119 chip. I’m having issues with choppy/stuttering audio, particularly on telemetry. It’s bad enough that it renders the CW ID meaningless.

My original thought was lack of CPU power, but I have tried it on a Raspberry Pi 2, Pi 3, and several virtual machines on a quad-core PC with identical results. Also, the choppiness is NOT as bad when using the full USB driver instead of SimpleUSB, which I believe conclusively rules out CPU power.

I’ve also tried a powered USB hub, thinking that the USB device was not receiving enough power, with no improvement.

I’ve used the Android mobile app to connect to the node, and the telemetry does not seem to be choppy when listening to it over the app. While I need to do some more testing to say this conclusively, I do believe at this point that my issue is narrowed down to the USB fob itself and/or the specific audio stream being sent to the device.

I’m currently searching for a way to alter the sample rate that ASL is sending the audio to the device in.

Has anyone experienced this, and does anyone have any suggestions?

Thanks and 73,

Rob, WX1N

Rob_Noll · April 1, 2019, 8:14pm

Rob,

Based on your comments about the telemetry “not sounding choppy when listening to it over the phone.”

It could be that RF from your transmitter is getting into your sound fob. Do you have a transmitter hooked up to the USB sound fob?

As a test, disable your transmitter and use clip leads to connect a PC amplified computer speaker to your TX audio line and see if you still have choppy audio.

If you do NOT have choppy audio with the amplified speaker, this surely points to some type of RF getting into your sound fob.

Hope this helps.

73

Marshall - ke6pcv

···

From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Rob Noll
Sent: Sunday, March 31, 2019 7:26 AM
To: app_rpt-users@lists.allstarlink.org
Subject: [App_rpt-users] USB fob choppy/stuttering audio

Good morning all,

I’m trying to set up an AllStar node using a USB fob based on the CM119 chip. I’m having issues with choppy/stuttering audio, particularly on telemetry. It’s bad enough that it renders the CW ID meaningless.

My original thought was lack of CPU power, but I have tried it on a Raspberry Pi 2, Pi 3, and several virtual machines on a quad-core PC with identical results. Also, the choppiness is NOT as bad when using the full USB driver instead of SimpleUSB, which I believe conclusively rules out CPU power.

I’ve also tried a powered USB hub, thinking that the USB device was not receiving enough power, with no improvement.

I’ve used the Android mobile app to connect to the node, and the telemetry does not seem to be choppy when listening to it over the app. While I need to do some more testing to say this conclusively, I do believe at this point that my issue is narrowed down to the USB fob itself and/or the specific audio stream being sent to the device.

I’m currently searching for a way to alter the sample rate that ASL is sending the audio to the device in.

Has anyone experienced this, and does anyone have any suggestions?

Thanks and 73,

Rob, WX1N

Wa1jhk1 · April 2, 2019, 12:16am

Hi Rob,

  Please copy the output from your lsusb command to a reply email.

There may be a clue there.

Thanks.

Dave

    WA1JHK

···

On 4/1/2019 2:14 PM, Rob Noll wrote:

Hi Marshall,

      Thanks for the thought, but it happens with both
a transmitter and with a headset.

Rob

**From: **
Marshall Oldham
**Sent: **
April 1, 2019 16:10:38
**To: **
‘Users of Asterisk app_rpt’
**Subject: **
Re: [App_rpt-users] USB fob
choppy/stuttering audio
Rob,

                Based
on your comments about the telemetry “not sounding
choppy when listening to it over the phone.”

                It
could be that RF from your transmitter is getting
into your sound fob. Do you have a transmitter
hooked up to the USB sound fob?

                As a
test, disable your transmitter and use clip leads to
connect a PC amplified computer speaker to your TX
audio line and see if you still have choppy audio.

                If you
do NOT have choppy audio with the amplified
speaker, this surely points to some type of RF
getting into your sound fob.

                Hope

this helps.

73

                Marshall

ke6pcv

From:
App_rpt-users

Rob Noll
Sunday, March 31, 2019 7:26 AM
[App_rpt-users] USB fob
choppy/stuttering audio

Good morning all,

              I’m trying to set up an AllStar
node using a USB fob based on the CM119 chip. I’m
having issues with choppy/stuttering audio,
particularly on telemetry. It’s bad enough that it
renders the CW ID meaningless.

              My original thought was lack of CPU
power, but I have tried it on a Raspberry Pi 2, Pi 3,
and several virtual machines on a quad-core PC with
identical results. Also, the choppiness is NOT as bad
when using the full USB driver instead of SimpleUSB,
which I believe conclusively rules out CPU power.

              I’ve also tried a powered USB hub,
thinking that the USB device was not receiving enough
power, with no improvement.

              I’ve used the Android mobile app to
connect to the node, and the telemetry does not seem
to be choppy when listening to it over the app. While
I need to do some more testing to say this
conclusively, I do believe at this point that my issue
is narrowed down to the USB fob itself and/or the
specific audio stream being sent to the device.

              I’m currently searching for a way
to alter the sample rate that ASL is sending the audio
to the device in.

              Has anyone experienced this, and

does anyone have any suggestions?

Thanks and 73,

Rob, WX1N

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
and scroll down to the bottom of the page. Enter your
email address and press the “Unsubscribe or edit options
button”

            You do not need a password to unsubscribe, you can do
it via email confirmation. If you have trouble
unsubscribing, please send a message to the list
detailing the problem.

Virus-free. www.avast.com

ke6pcv@cal-net.orgapp_rpt-users@lists.allstarlink.orgmailto:app_rpt-users-bounces@lists.allstarlink.orgOn Behalf Of
Sent:
**To:**app_rpt-users@lists.allstarlink.org
Subject:


_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

Rob_Noll · April 2, 2019, 12:46am

Hi Dave,

As requested, output is below. I’m confused how this might help with audio quality issues – do you mind telling me what sort of clues one would look for?

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 002: ID 0d8c:013a C-Media Electronics, Inc.

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Rob

···

From: App_rpt-users app_rpt-users-bounces@lists.allstarlink.org On Behalf Of Dave Maciorowski
Sent: Monday, April 01, 2019 20:17
To: app_rpt-users@lists.allstarlink.org
Subject: Re: [App_rpt-users] USB fob choppy/stuttering audio

Hi Rob,

Please copy the output from your lsusb command to a reply email. There may be a clue there.

Thanks.

Dave
WA1JHK

On 4/1/2019 2:14 PM, Rob Noll wrote:

Hi Marshall,

Thanks for the thought, but it happens with both a transmitter and with a headset.

Rob

**From: **

Marshall Oldham ke6pcv@cal-net.org

**Sent: **

April 1, 2019 16:10:38

**To: **

‘Users of Asterisk app_rpt’ app_rpt-users@lists.allstarlink.org

**Subject: **

Re: [App_rpt-users] USB fob choppy/stuttering audio

Rob,

Based on your comments about the telemetry “not sounding choppy when listening to it over the phone.”

It could be that RF from your transmitter is getting into your sound fob. Do you have a transmitter hooked up to the USB sound fob?

As a test, disable your transmitter and use clip leads to connect a PC amplified computer speaker to your TX audio line and see if you still have choppy audio.

If you do NOT have choppy audio with the amplified speaker, this surely points to some type of RF getting into your sound fob.

Hope this helps.

73

Marshall - ke6pcv

From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Rob Noll
Sent: Sunday, March 31, 2019 7:26 AM
To: app_rpt-users@lists.allstarlink.org
Subject: [App_rpt-users] USB fob choppy/stuttering audio

Good morning all,

I’m trying to set up an AllStar node using a USB fob based on the CM119 chip. I’m having issues with choppy/stuttering audio, particularly on telemetry. It’s bad enough that it renders the CW ID meaningless.

My original thought was lack of CPU power, but I have tried it on a Raspberry Pi 2, Pi 3, and several virtual machines on a quad-core PC with identical results. Also, the choppiness is NOT as bad when using the full USB driver instead of SimpleUSB, which I believe conclusively rules out CPU power.

I’ve also tried a powered USB hub, thinking that the USB device was not receiving enough power, with no improvement.

I’ve used the Android mobile app to connect to the node, and the telemetry does not seem to be choppy when listening to it over the app. While I need to do some more testing to say this conclusively, I do believe at this point that my issue is narrowed down to the USB fob itself and/or the specific audio stream being sent to the device.

I’m currently searching for a way to alter the sample rate that ASL is sending the audio to the device in.

Has anyone experienced this, and does anyone have any suggestions?

Thanks and 73,

Rob, WX1N

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”

You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

_______________________________________________

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

[http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)

To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"

You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

Virus-free. www.avast.com

w2db · April 14, 2019, 5:01am

Hi guys, this discussion interests me. I’m having a very similar issue with my 28599 node, which is ASL 1.01 and a Pi3. Holes in the audio both ways and not just to/from other nodes but also the repeat audio has it. I can hear it in parrot mode and when doing simple-usb-tune and doing TX audio adjustments toggling sending a tone I hear it . If I re-arrange to make the repeater handle audio and keying as a stand alone repeater it sounds great. I’m using SimpleUSB.

At first I though I had a network problem but it isn’t. I’ve tried four different Pi3’s and five microSD cards. Using a RA-35 CM119 interface. I’ve been using these UDB fobs with allstar for ten years now. I’ve always had some sort of audio holes but this is more severe. It happens at boot, and after days, the effect does not change.

I don’t want to use the other distro. This is the group I prefer. But there’s something to this all.

My lsusb:
root@repeater:/home/repeater# lsusb
Bus 001 Device 004: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I’ve tried lowering audio into the CM119 from the Quantar, made no difference.

In contrast to this I have another node using USBRadio and a home modified CM108 USB fob. It runs Limey Linux with currently compiled app_rpt, etc. It is on an Intel D945 micro ITX board. It has minor holes in audio but not as bad.

As an aside. I’m sure this has been brought up before but since the Pi has become the platform of choice (it seems) has any thought been given to using its on-board audio with the abundant Pi GPIO’s? I wish I were one of you code writing geniuses. Being retired I have the time…but not the know-how.

I can send audio samples if anyone wants. Maybe tackle some of it off-list??

Thanks folks.
GeorgeC W2DB
Nodes 2360, 2428, 28599, 49089

Wa1jhk1 · April 6, 2019, 8:49pm

Hi Rob,

  CM109's show up with a different description.  Here's one that

have:

  Bus 002 Device 014: ID 0d8c:000e C-Media Electronics, Inc. Audio

Adapter (Planet UP-100, Genius G-Talk)

  There were some marked as CM119's.  They cause the same symptom.

It was worth checking.

73,

Dave

    WA1JHK

···

On 4/1/2019 6:46 PM, Rob Noll wrote:

Hi Dave,

        As
requested, output is below. I’m confused how this might
help with audio quality issues – do you mind telling me what
sort of clues one would look for?

        Bus 001
Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

        Bus 002
Device 002: ID 0d8c:013a C-Media Electronics, Inc.

        Bus 002
Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Rob

From: App_rpt-users
Dave Maciorowski
Monday, April 01, 2019 20:17
Re: [App_rpt-users] USB fob
choppy/stuttering audio

Hi Rob,

      Please copy the output from your lsusb command to a reply

email. There may be a clue there.

Thanks.

Dave

        WA1JHK

On 4/1/2019 2:14 PM, Rob Noll wrote:

Hi Marshall,

            Thanks for the thought, but it
happens with both a transmitter and with a headset.

Rob

**From: **

                          Marshall

Oldham ke6pcv@cal-net.org

**Sent: **

                          April

1, 2019 16:10:38

**To: **

                          'Users
of Asterisk app_rpt’ app_rpt-users@lists.allstarlink.org

**Subject: **

                          Re:
[App_rpt-users] USB fob choppy/stuttering
audio

Rob,

                    Based on your comments
about the telemetry “not sounding choppy when
listening to it over the phone.”

                    It could be that RF from
your transmitter is getting into your sound fob.
Do you have a transmitter hooked up to the USB
sound fob?

                    As a test, disable your
transmitter and use clip leads to connect a PC
amplified computer speaker to your TX audio line
and see if you still have choppy audio.

                    If you do  NOT have choppy
audio with the amplified speaker, this surely
points to some type of RF getting into your
sound fob.

Hope this helps.

73

Marshall - ke6pcv

From:
App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org ]
On Behalf Of Rob Noll
Sent: Sunday, March 31, 2019 7:26 AM
To: app_rpt-users@lists.allstarlink.org
Subject: [App_rpt-users] USB fob
choppy/stuttering audio

                  Good

morning all,

                  I’m
trying to set up an AllStar node using a USB fob
based on the CM119 chip. I’m having issues with
choppy/stuttering audio, particularly on
telemetry. It’s bad enough that it renders the CW
ID meaningless.

                  My
original thought was lack of CPU power, but I have
tried it on a Raspberry Pi 2, Pi 3, and several
virtual machines on a quad-core PC with identical
results. Also, the choppiness is NOT as bad when
using the full USB driver instead of SimpleUSB,
which I believe conclusively rules out CPU power.

                  I’ve
also tried a powered USB hub, thinking that the
USB device was not receiving enough power, with no
improvement.

                  I’ve
used the Android mobile app to connect to the
node, and the telemetry does not seem to be choppy
when listening to it over the app. While I need
to do some more testing to say this conclusively,
I do believe at this point that my issue is
narrowed down to the USB fob itself and/or the
specific audio stream being sent to the device.

                  I’m
currently searching for a way to alter the sample
rate that ASL is sending the audio to the device
in.

                  Has
anyone experienced this, and does anyone have any
suggestions?

                  Thanks

and 73,

                  Rob,

WX1N

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

                  To unsubscribe from this list
please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
and scroll down to the bottom of the page. Enter
your email address and press the “Unsubscribe or
edit options button”

                  You do not need a password to
unsubscribe, you can do it via email confirmation.
If you have trouble unsubscribing, please send a
message to the list detailing the problem.

_______________________________________________

App_rpt-users mailing list

App_rpt-users@lists.allstarlink.org

[http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users)

To unsubscribe from this list please visit [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users](http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users) and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"

You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

                  Virus-free.

www.avast.com

app_rpt-users-bounces@lists.allstarlink.org** On
Behalf Of**
Sent:
**To:**app_rpt-users@lists.allstarlink.org
Subject:


_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users

Steve_Arntz · May 16, 2020, 5:22pm

I am having choppy audio as well using a radioless node 50932.

[8 new photos added to shared album] Allstar Radioless Node

The problem is intermittent. If there is any other info I can supply, let me know.

64 bit version of ASL_1.01-20180417-amd64-i386-debian-stretch-netinst.iso

PC - with ASUS P5Q SE motherboard
Pentium Dual Core E5200 @ 2.5 Ghz with 8Gb ram
Kingston 120 GB solid state disk
partitioned with 8GB for system and 8GB for swap

root@km5ht-50932:/home/repeater# lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 002: ID 0458:0024 KYE Systems Corp. (Mouse Systems)
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

; SimpleUSB configuration

[general]

[usb_50932]

eeprom = 0 ; EEPROM installed: 0,1
; 0 = no (default)
; 1 = yes

hdwtype = 0 ; Leave this set to 0 for USB sound fobs modified using
; the instructions from usbfob.pdf. Use a setting of
; 1 is for Dingotel/Sph interfaces.

; Receiver parameters

rxboost = 1 ; SDA 0 = 20db attenuator inserted, 1= 20db attenuator removed
; Set to 1 for additonal gain if using a low-level receiver output

carrierfrom = usbinvert ; no,usb,usbinvert
; no - no carrier detection at all
; usb - from the COR line on the USB sound fob (Active high)
; usbinvert - from the inverted COR line on the USB sound fob (Active low)

ctcssfrom = no ; SDA no,usb,usbinvert
; no - CTCSS decoding, system will be carrier squelch
; usb - CTCSS decoding using input from USB sound fob (Active high)
; usbinvert - from the inverted CTCSS line on the USB sound fob (Active low)

deemphasis = no ; enable de-emphasis (input from discriminator)

plfilter = no ; enable PL filter

;rxondelay = 0 ; number of 20ms intervals to hold off receiver turn-on indication

; Transmitter parameters

txmixa = voice ; Left channel output (A): no,voice
; no - Do not output anything
; voice - output voice only

txmixb = no ; Right channel output (B): no,voice
; no - Do not output anything
; voice - output voice only

txboost = 0

invertptt = 0 ; Invert PTT: 0,1
; 0 - ground to transmit
; 1 - open to transmit

preemphasis = 0 ; Perform standard 6db/octave pre-emphasis

; pager = no ; no,a,b (e.g. pager = b means “put the normal repeat audio on channel A, and the pager audio on channel B”)

; duplex3 = 0 ; duplex 3 gain setting (0 to disable)

duplex = 0 ; Duplex 0,1
; 0 - half duplex
; 1 - full duplex

#includeifexists custom/simpleusb.conf

gw1syg · June 5, 2020, 7:13pm

Interesting reading comments re audio issues , i have been chasing an issue with audio on pi and usb sound interface , the speech audio would be fine no issues ctcss encode good but as soon as the PI generated speech synth be status update or callsign the audio would chop on a receiver the ctcss encode
is being distorted regardless of what audio input is used , after altering the output with a resistor network
the problem went away but now need more drive