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
I don’t know if this fits your situation, but the only time I’ve had choppy audio is when something in asterisk or Linux is unhappy; most likely asterisk. I’d check your USB related settings (usbradio or simpleusb). Thanks, Bob K6ECM 73
On Mar 31, 2019, at 7:26 AM, Rob Noll <rob@nollmail.com> wrote:
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.
PS. Also make sure the USB interface matches. I’ve had USB issues cause this choppiness, fixed by changing ports. (use lsusb) Thanks, Bob K6ECM 73
On Mar 31, 2019, at 8:58 AM, Bob Pyke <k6ecm1@gmail.com> wrote:
I don’t know if this fits your situation, but the only time I’ve had choppy audio is when something in asterisk or Linux is unhappy; most likely asterisk. I’d check your USB related settings (usbradio or simpleusb).
Thanks, Bob K6ECM 73
On Mar 31, 2019, at 7:26 AM, Rob Noll <rob@nollmail.com> wrote:
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.
On that note Bob, do you know the correct format for the port line in the usb tune config file? From: Bob Pyke k6ecm1@gmail.com Sent: March 31, 2019 12:02:09 To: Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org Subject: Re: [App_rpt-users] USB fob choppy/stuttering audio PS. Also make sure the USB interface matches. I’ve had USB issues cause this choppiness, fixed by changing ports. (use lsusb) Thanks, Bob K6ECM 73 On Mar 31, 2019, at 8:58 AM, Bob Pyke <k6ecm1@gmail.com> wrote:
I don’t know if this fits your situation, but the only time I’ve had choppy audio is when something in asterisk or Linux is unhappy; most likely asterisk. I’d check your USB related settings (usbradio or simpleusb).
Thanks, Bob K6ECM 73
On Mar 31, 2019, at 7:26 AM, Rob Noll <rob@nollmail.com> wrote:
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 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.
Good morning, What radio are you using with your node? I know when I was using the baofeng 82 dual bander I had to have the USB setup on USBinvert where if I used the baofeng 888 it would just be set to USB. So play with that setting and see if it helps. 73, Joe K2OL Sent from my iPhone
On Mar 31, 2019, at 11:58 AM, Bob Pyke <k6ecm1@gmail.com> wrote:
I don’t know if this fits your situation, but the only time I’ve had choppy audio is when something in asterisk or Linux is unhappy; most likely asterisk. I’d check your USB related settings (usbradio or simpleusb).
Thanks, Bob K6ECM 73
On Mar 31, 2019, at 7:26 AM, Rob Noll <rob@nollmail.com> wrote:
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
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.
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
On Mar 31, 2019, at 9:03 AM, Rob Noll <rob@nollmail.com> wrote:
On that note Bob, do you know the correct format for the port line in the usb tune config file?
From: Bob Pyke k6ecm1@gmail.com Sent: March 31, 2019 12:02:09 To: Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org Subject: Re: [App_rpt-users] USB fob choppy/stuttering audio
PS. Also make sure the USB interface matches. I’ve had USB issues cause this choppiness, fixed by changing ports. (use lsusb)
Thanks, Bob K6ECM 73
On Mar 31, 2019, at 8:58 AM, Bob Pyke <k6ecm1@gmail.com> wrote:
I don’t know if this fits your situation, but the only time I’ve had choppy audio is when something in asterisk or Linux is unhappy; most likely asterisk. I’d check your USB related settings (usbradio or simpleusb).
Thanks, Bob K6ECM 73
On Mar 31, 2019, at 7:26 AM, Rob Noll <rob@nollmail.com> wrote:
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
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.
Try other FOB with a cm108 ...mike/kb8jnm On 3/31/2019 11:58 AM, Bob Pyke wrote:
I don’t know if this fits your situation, but the only time I’ve had choppy audio is when something in asterisk or Linux is unhappy; most likely asterisk. I’d check your USB related settings (usbradio or simpleusb).
Thanks, Bob K6ECM 73
On Mar 31, 2019, at 7:26 AM, Rob Noll <rob@nollmail.com <mailto:rob@nollmail.com>> wrote:
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 <mailto: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.
I did let ASL set it, but without knowing the syntax of the string (in my case, “devstr=2-1:1.0”), how do I check it to make sure? I’m confused on how to follow the suggestion to change ports or verify the correct format. As far as not using USB… I’m not aware of any other viable option for the project at hand, but I’m open to any suggestions. From: App_rpt-users <app_rpt-users-bounces@lists.allstarlink.org> On Behalf Of Bob Pyke Sent: Sunday, March 31, 2019 12:09 To: Users of Asterisk app_rpt <app_rpt-users@lists.allstarlink.org> Subject: Red: [App_rpt-users] USB fob choppy/stuttering audio 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 On Mar 31, 2019, at 9:03 AM, Rob Noll <rob@nollmail.com <mailto:rob@nollmail.com> > wrote: On that note Bob, do you know the correct format for the port line in the usb tune config file? _____ From: Bob Pyke <mailto:k6ecm1@gmail.com> k6ecm1@gmail.com Sent: March 31, 2019 12:02:09 To: Users of Asterisk app_rpt <mailto:app_rpt-users@lists.allstarlink.org> app_rpt-users@lists.allstarlink.org Subject: Re: [App_rpt-users] USB fob choppy/stuttering audio PS. Also make sure the USB interface matches. I’ve had USB issues cause this choppiness, fixed by changing ports. (use lsusb) Thanks, Bob K6ECM 73 On Mar 31, 2019, at 8:58 AM, Bob Pyke < <mailto:k6ecm1@gmail.com> k6ecm1@gmail.com> wrote: I don’t know if this fits your situation, but the only time I’ve had choppy audio is when something in asterisk or Linux is unhappy; most likely asterisk. I’d check your USB related settings (usbradio or simpleusb). Thanks, Bob K6ECM 73 On Mar 31, 2019, at 7:26 AM, Rob Noll < <mailto:rob@nollmail.com> rob@nollmail.com> wrote: 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 <mailto:App_rpt-users@lists.allstarlink.org> 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 <mailto:App_rpt-users%40lists.allstarlink.org> 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 <mailto:App_rpt-users@lists.allstarlink.org> 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.
Unfortunately, I don’t have one. I’d rather not start sinking money into replacing things without knowing the root cause. From: App_rpt-users <app_rpt-users-bounces@lists.allstarlink.org> On Behalf Of Mike Sent: Sunday, March 31, 2019 12:15 To: app_rpt-users@lists.allstarlink.org Subject: Re: [App_rpt-users] USB fob choppy/stuttering audio Try other FOB with a cm108 ...mike/kb8jnm On 3/31/2019 11:58 AM, Bob Pyke wrote: I don’t know if this fits your situation, but the only time I’ve had choppy audio is when something in asterisk or Linux is unhappy; most likely asterisk. I’d check your USB related settings (usbradio or simpleusb). Thanks, Bob K6ECM 73 On Mar 31, 2019, at 7:26 AM, Rob Noll <rob@nollmail.com <mailto:rob@nollmail.com> > wrote: 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 <mailto: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 <mailto: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.
If you have put the same FOB in as many machines for a test as you say you have, with same results... ...'it's the FOB'. Use one like it or one different. ...mike/kb8jnm On 3/31/2019 12:18 PM, Rob Noll wrote:
Unfortunately, I don’t have one. I’d rather not start sinking money into replacing things without knowing the root cause.
*From:*App_rpt-users <app_rpt-users-bounces@lists.allstarlink.org> *On Behalf Of *Mike *Sent:* Sunday, March 31, 2019 12:15 *To:* app_rpt-users@lists.allstarlink.org *Subject:* Re: [App_rpt-users] USB fob choppy/stuttering audio
Try other FOB with a cm108
...mike/kb8jnm
On 3/31/2019 11:58 AM, Bob Pyke wrote:
I don’t know if this fits your situation, but the only time I’ve had choppy audio is when something in asterisk or Linux is unhappy; most likely asterisk. I’d check your USB related settings (usbradio or simpleusb).
Thanks,
Bob
K6ECM
73
On Mar 31, 2019, at 7:26 AM, Rob Noll <rob@nollmail.com <mailto:rob@nollmail.com>> wrote:
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 <mailto: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 <mailto:App_rpt-users@lists.allstarlink.org>
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visithttp://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.
Well here’s the odd thing – I put the fob in a Windows machine and used an earpiece while streaming audio to it as a regular sound card. It seemed to handle it fine. So the issue does not seem to be a bad fob, and the issue does not seem to be asterisk (as evidenced by using the Android app to listen to the audio stream, where it sounds fine). It seems to be specifically related to the asterisk audio stream to the USB device. I’d really like to try Bob’s suggestion of double checking the USB port configuration, but I can’t find any info on the syntax of the device string. I’d also like to try changing the sampling rate asterisk is using for the USB audio stream, but I haven’t been able to find any info on how to change it. From: App_rpt-users <app_rpt-users-bounces@lists.allstarlink.org> On Behalf Of Mike Sent: Sunday, March 31, 2019 12:22 To: app_rpt-users@lists.allstarlink.org Subject: Re: [App_rpt-users] USB fob choppy/stuttering audio If you have put the same FOB in as many machines for a test as you say you have, with same results... ...'it's the FOB'. Use one like it or one different. ...mike/kb8jnm On 3/31/2019 12:18 PM, Rob Noll wrote: Unfortunately, I don’t have one. I’d rather not start sinking money into replacing things without knowing the root cause. From: App_rpt-users <mailto:app_rpt-users-bounces@lists.allstarlink.org> <app_rpt-users-bounces@lists.allstarlink.org> On Behalf Of Mike Sent: Sunday, March 31, 2019 12:15 To: app_rpt-users@lists.allstarlink.org <mailto:app_rpt-users@lists.allstarlink.org> Subject: Re: [App_rpt-users] USB fob choppy/stuttering audio Try other FOB with a cm108 ...mike/kb8jnm On 3/31/2019 11:58 AM, Bob Pyke wrote: I don’t know if this fits your situation, but the only time I’ve had choppy audio is when something in asterisk or Linux is unhappy; most likely asterisk. I’d check your USB related settings (usbradio or simpleusb). Thanks, Bob K6ECM 73 On Mar 31, 2019, at 7:26 AM, Rob Noll <rob@nollmail.com <mailto:rob@nollmail.com> > wrote: 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 <mailto: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 <mailto: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 <mailto: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.
CM119A. From: Kevin Custer <kuggie@kuggie.com> Sent: Sunday, March 31, 2019 12:20 To: Users of Asterisk app_rpt <app_rpt-users@lists.allstarlink.org>; Rob Noll <rob@nollmail.com> Subject: Re: [App_rpt-users] USB fob choppy/stuttering audio On 3/31/2019 10:26 AM, Rob Noll wrote: Good morning all, I’m trying to set up an AllStar node using a USB fob based on the CM119 chip. CM119, CM119A, or CM119B?
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
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 <mailto: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
Eric, In the beginning USB was some what flakey with App_rpt. Over the last several years USB it has become much more stable. Given the choice of hardware for stability, the Quad PCI radio card wins, but the quad PCI card is no longer manufactured or sold. This is because of the price point. Hams did not want to spend the money for the 4 port PCI Quad card, when they can buy an $8 dollar USB sound fob and modify it to work. from my iPhone
On Mar 31, 2019, at 9:49 AM, Eric Fort <eric.fort.listmail@fortconsulting.org> wrote:
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.
Okay - Not sure how to help then... Kevin W3KKC On 3/31/2019 12:45 PM, Rob Noll wrote:
CM119A.
*From:*Kevin Custer <kuggie@kuggie.com> *Sent:* Sunday, March 31, 2019 12:20 *To:* Users of Asterisk app_rpt <app_rpt-users@lists.allstarlink.org>; Rob Noll <rob@nollmail.com> *Subject:* Re: [App_rpt-users] USB fob choppy/stuttering audio
On 3/31/2019 10:26 AM, Rob Noll wrote:
Good morning all,
I’m trying to set up an AllStar node using a USB fob based on the CM119 chip.
CM119, CM119A, or CM119B?
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.
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.
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.
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 Sent from my iPhone
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.
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.
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. 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 <mailto: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 <mailto:kb9mwr@gmail.com> *Sent: * March 31, 2019 20:01:00 *To: * Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org <mailto: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 <mailto:App_rpt-users%40lists.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 <mailto: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 <mailto:App_rpt-users%40lists.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.
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? From: Mike mm@midnighteng.com Sent: March 31, 2019 21:08:06 To: app_rpt-users@lists.allstarlink.org Subject: Re: [App_rpt-users] USB fob choppy/stuttering audio 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. 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.
_______________________________________________ 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.
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.
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 From: Eric Fort eric.fort.listmail@fortconsulting.org Sent: April 1, 2019 1:42:11 AM To: Users of Asterisk app_rpt app_rpt-users@lists.allstarlink.org Subject: Re: [App_rpt-users] USB fob choppy/stuttering audio 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.
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, 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
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.
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 <mailto:App_rpt-users%40lists.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.
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
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 <mailto:ke6pcv@cal-net.org> Sent: April 1, 2019 16:10:38 To: 'Users of Asterisk app_rpt' app_rpt-users@lists.allstarlink.org <mailto: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 <mailto: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 <mailto:App_rpt-users%40lists.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 <mailto: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. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon> Virus-free. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link> www.avast.com
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 <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 <mailto:ke6pcv@cal-net.org>
*Sent: *
April 1, 2019 16:10:38
*To: *
'Users of Asterisk app_rpt' app_rpt-users@lists.allstarlink.org <mailto: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 <mailto: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 <mailto:App_rpt-users%40lists.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 <mailto:App_rpt-users@lists.allstarlink.org>
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visithttp://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.
Image removed by sender. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon>
Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link>
_______________________________________________ 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.
participants (10)
-
Bob Pyke -
Dave Maciorowski -
Eric Fort -
Joe C -
Kevin Custer -
Marshall -
Marshall Oldham
-
Mike -
Rob Noll -
Steve L