[App_rpt-users] AMBE question (was: DIAL Question)

Thu Oct 29 13:33:00 UTC 2015

David,

The MBE (mbelib) code you are thinking about is both patent encumbered at
this point and only decodes AMBE frames.  It does not implement the
encoder.  I have extensive experience with that code base and the audio
quality as compared to the chipset is not acceptable.  It is good for
experimentation, but I would never deploy a solution with it.

However, on the subject of adding new codecs in order to not transcode, you
are correct.  Raw encoded frames should be transferred by the network, only
to be decoded at the end node.

Mike

On Thu, Oct 29, 2015 at 8:03 AM, David McGough <kb4fxc at inttek.net> wrote:

>
> Guys,
>
> I haven't looked carefully as to which variants of AMBE are in use by
> D-STAR, Fusion, etc...Doesn't the original AMBE patent expire fairly soon?
>
> The reason I'm asking is that I know there are some fledgling open-source
> AMBE implementations out there.  A couple years ago I hacked CODEC2 into
> Asterisk for experimentation, thinking about directly linking to HF via
> the FreeDV project--and, not wanting to transcode from one low-bandwidth
> CODEC to another, making truly awful audio!
>
> After playing with it a few weeks, I didn't do much more...(I've still
> got that code and it still works, if anyone wants to play with it?)
>
> ...Just wondering.
>
> 73, David KB4FXC
>
>
> On Thu, 29 Oct 2015, Matthew Pitts wrote:
>
> > Mike,
> >
> > You are correct in the statement that the DV4mini needs additional
> hardware to handle the transcoding from a digital radio. Once I get my
> nodes back up on my Raspberry Pi, I will work on an updated version of
> the D-STAR channel driver that supports DMR and Fusion AMBE encoding and
> decoding as well as radio control functionality for the DV4mini.
> >
> > Matthew Pitts
> > N8OHU
> >
> > On October 28, 2015 6:18:34 PM EDT, Mike Zingman <mike.zingman at gmail.com>
> wrote:
> > >Actually the DV4Mini alone does not help tie Allstar into Wires-X.  In
> > >order to do that one must:
> > >
> > >1) Have an interface to the YSF network protocol
> > >2) Decode and extract the AMBE frames from the streamed protocol
> > >3) Transcode the frames to PCM at the proper sample rate using the DVSI
> > >AMBE3000 chipset
> > >4) Send those frames to something like the already created USRP channel
> > >driver
> > >
> > >In reverse, 4, 3, 2, 1 to send data back to the YSF network.  In
> > >addition
> > >to the simple outline above, you would want to
> > >a) Add audio filtering/shaping to make the AMBE audio more acceptable
> > >to
> > >what we are used to on Allstar (one of the single greatest aspects of
> > >Allstar is the audio quality)
> > >b) Transfer of as much metadata between the networks as possible
> > >
> > >The DV4Mini is a radio module + digital modulator (DStar/DMR/YSF).  It
> > >has
> > >no AMBE encode/decode hardware so there is no way to transcode the
> > >audio
> > >content.  For that a "ThumbDV" or a DV3000 would be the hardware of
> > >choice.  The DV4Mini could be used as a user radio on an existing RF
> > >network, but one would still need the AMBE3K to do the transcode.
> > >
> > >Mike
> > >
> > >
> > >On Wed, Oct 28, 2015 at 5:48 PM, Neil k8it <k8it at cac.net> wrote:
> > >
> > >> I have been waiting a bit before I start playing with DIAL on a RPI2.
> > >> I still have two questions
> > >> 1. Does the RPI2 DIAL  version solve the tx echo buffer issue that
> > >the
> > >> current version of Asterisk RPI2 code has. The fix to this issue
> > >seems to
> > >> be taking a long time.
> > >> 2. Some users have reorted that a lot of modules have been disabled,
> > >such
> > >> as the Echolink channel driver and others.
> > >> 3. With the new Mini-DV4  dongle $125  and the amount of capability,
> > >has
> > >> anybody wrote a channel driver to tie the Yaesu Fusion Wires-X
> > >network into
> > >> DIAL. It appears that most of the documentation is out there, we just
> > >need
> > >> someone to write the channel driver
> > >>
> > >>
> > >> Thanks
> > >> 73 Neil Sablatzky  K8IT
> > >> Allstar Node 41838 KITLINK
> > >> Allstar Node 42087 KITLINK HUB
> > >> IRLP Node exp0068
> > >> Echolink K8IT-L
> > >> WIRES-X K8IT 11479 Room 21479
> > >>
> > >> *From:* Steve N4IRS <szingman at msgstor.com>
> > >> *Sent:* Tuesday, October 27, 2015 10:35 AM
> > >> *To:* N7MTC . <n7mtc at outlook.com> ; app_rpt-users at ohnosec.org
> > >> *Subject:* Re: [App_rpt-users] Procedure for loading DIAL on a R-Pi2
> > >or a
> > >> PC
> > >>
> > >> Mac,
> > >> The RPi2 install is pretty much download the image, burn it to SD
> > >card,.
> > >> Once the Pi boots, you can login on the HDMI / USB console, or SSH
> > >into
> > >> the board on port 222.
> > >> The board is setup for DHCP so check your DHCP (router) server for
> > >address.
> > >> If you want, you can login via the built in serial port at 115,200
> > >> System will walk you through setup.
> > >>
> > >> FAQ for DIAL is at:
> > >> <http://docs.allstarlink.org/drupal/node/170>
> > >> <http://docs.allstarlink.org/drupal/node/170%3E>
> > >>
> > >> 73, Steve N4IRS
> > >>
> > >>
> > >> On 10/27/2015 10:20 AM, N7MTC . wrote:
> > >>
> > >> Is there a procedure for loading the "new" DIAL version of asterisk
> > >for
> > >> Raspberry pi2?
> > >>
> > >>
> > >>
> > >> I am looking to connect either a Pi2 or an intel NUC to a Yaesu Dr-1x
> > >> using the Arcom RC-210 and  the Arcom ADR.  I noticed DIAL has
> > >replaced
> > >> ACID as the latest flavor of asterisk for both PC and PI2.  I have
> > >not
> > >> found any install write-ups or YouTubes showing a DIAL install.
> > >>
> > >>
> > >>
> > >> Regardless of which platform I will need to use an USB to Serial
> > >adapter
> > >> to connect the ALLSTAR node to the repeater controller.  It will be
> > >of
> > >> the FTDI chipset either a trendnet Tu-s9 or a GearMo USB RS-232.
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> /73
> > >>
> > >> Mac, N7MTC
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> Benjamin Franklin - "Those who surrender freedom for security will
> > >not
> > >> have, nor do they deserve, either one."
> > >>
> > >>
> > >>
> > >> _______________________________________________
> > >> App_rpt-users mailing
> > >listApp_rpt-users at ohnosec.orghttp://
> ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> > >>
> > >> To unsubscribe from this list please visit
> > >http://ohnosec.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 at ohnosec.org
> > >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> > >>
> > >> To unsubscribe from this list please visit
> > >> http://ohnosec.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 virus found in this message.
> > >> Checked by AVG - www.avg.com
> > >> Version: 2015.0.6173 / Virus Database: 4455/10900 - Release Date:
> > >10/27/15
> > >>
> > >>
> > >> _______________________________________________
> > >> App_rpt-users mailing list
> > >> App_rpt-users at ohnosec.org
> > >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> > >>
> > >> To unsubscribe from this list please visit
> > >> http://ohnosec.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 at ohnosec.org
> > >http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> > >
> > >To unsubscribe from this list please visit
> > >http://ohnosec.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 at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit
> http://ohnosec.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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20151029/ee4f8963/attachment.html>