<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Rob,<div><br></div><div>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. </div><div><br></div><div>Eric</div><div>Af6ep<br><br><div id="AppleMailSignature" dir="ltr">Sent using SMTP.</div><div dir="ltr"><br>On Mar 31, 2019, at 10:01 AM, Rob Noll <<a href="mailto:rob@nollmail.com">rob@nollmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.emailstyle17
{mso-style-name:emailstyle17;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--><div class="WordSection1"><p class="MsoNormal">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.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">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.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">That said, here are some answers to your questions:<o:p></o:p></p><p class="MsoNormal">>>> why does it seem that most everyone has gone this route against the above sage wisdom<o:p></o:p></p><p class="MsoNormal">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.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">>>> rather than using something more akin an e&m interface like the pci radio cards Jim designed<o:p></o:p></p><p class="MsoNormal">I don’t know Jim, don’t know where to buy his products, and there are no PCI interfaces on a Raspberry Pi.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">>>> the interface boards that plugged into an fxs? Port and broke out e&m, providing keying by polarity reversal of the battery voltage<o:p></o:p></p><p class="MsoNormal">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.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">>>> Apparently usb not so much and apparently this is a long standing problem with usb<o:p></o:p></p><p class="MsoNormal">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.<o:p></o:p></p><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><o:p> </o:p></p><div><div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b>From:</b> App_rpt-users <<a href="mailto:app_rpt-users-bounces@lists.allstarlink.org">app_rpt-users-bounces@lists.allstarlink.org</a>> <b>On Behalf Of </b>Eric Fort<br><b>Sent:</b> Sunday, March 31, 2019 12:49<br><b>To:</b> Users of Asterisk app_rpt <<a href="mailto:app_rpt-users@lists.allstarlink.org">app_rpt-users@lists.allstarlink.org</a>><br><b>Subject:</b> Re: [App_rpt-users] USB fob choppy/stuttering audio<o:p></o:p></p></div></div><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal"><o:p> </o:p></p><div><p class="MsoNormal" style="margin-bottom:12.0pt">On Mar 31, 2019, at 9:08 AM, Bob Pyke <<a href="mailto:k6ecm1@gmail.com">k6ecm1@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><p class="MsoNormal">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.<o:p></o:p></p><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal" style="margin-bottom:12.0pt">As Jim has said many times, “friends don’t let friends do USB” :-)<o:p></o:p></p><div id="AppleMailSignature"><div><p class="MsoNormal">Thanks,<o:p></o:p></p></div><div><p class="MsoNormal">Bob<o:p></o:p></p></div><div><p class="MsoNormal">K6ECM<o:p></o:p></p></div><div><p class="MsoNormal">73<o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div></div><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div><div><div id="aqm-original"><div><div><table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0"><tbody><tr><td valign="top" style="padding:.75pt .75pt .75pt .75pt"></td><td valign="top" style="padding:.75pt .75pt .75pt .75pt"></td></tr></tbody></table></div></div></div></div></div></blockquote></div></div></blockquote><p class="MsoNormal"><o:p> </o:p></p><div><p class="MsoNormal">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. <o:p></o:p></p></div><div><p class="MsoNormal"><o:p> </o:p></p></div><div><p class="MsoNormal">Eric <o:p></o:p></p></div><div><p class="MsoNormal">Af6ep <o:p></o:p></p></div></div></div></blockquote><blockquote type="cite"><div dir="ltr"><span>_______________________________________________</span><br><span>App_rpt-users mailing list</span><br><span><a href="mailto:App_rpt-users@lists.allstarlink.org">App_rpt-users@lists.allstarlink.org</a></span><br><span><a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a></span><br><span></span><br><span>To unsubscribe from this list please visit <a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"</span><br><span>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. </span><br></div></blockquote></div></body></html>