Al, That's exactly what my FreeDV application does except 1. It uses a general purpose voip protocol (Mumble) which can be extended with arbitrary codecs including Codec2 2. It doesn't use the cloud. It uses a simple TCP server which can be hosted anywhere and which allows multiple rooms to carry different physical radio channels.
Mumble is very well known in the gaming community for its high audio quality and high performance. In addition, it's completely open source and the protocol is well documented. Regards, Adrian On October 26, 2020 11:16:14 AM UTC, Al Beard via Freetel-codec2 <freetel-codec2@lists.sourceforge.net> wrote: >Hi David VK2DWG, > >Consider a HF "hot spot". Can receive say mode 700D which uses the mode >700C codec. > >adds the hot-spot callsign and sends to the cloud talk group HF1 and >listeners treat it like any other > >talk group except, in his radio, his radio recognises it is mode 700C >data and de-codecs it accordingly. > >Seemless. > >His radio then recognises, to reply, use the same codec. > >No need to "reinvent" the wheel. > >In the DMR world, they do exactly the same thing except it's with >encryption keys. They have a set, not just one. > >Alan VK2ZIW > >On Mon, 26 Oct 2020 13:42:52 +1100, David Grove wrote >> Thanks Walter >> >> Unfortunately, as published, M17 is double the bandwidth that would >be feasible on Amateur HF using commonly available equipment. >> >> However, imagine the possibilities if the M17 protocol could be also >be adapted to operate on HF as well on higher RF frequencies. Perhaps >with a slower sample rate (say 4800) and carriers that would be >compatible with standard HF transceivers (eg 400, 800, 1200, 1600, >2200). My theory on symbol rates and bandwidth is rusty, so happy to be >corrected. >> >> It might be possible to receive on VHF at high quality/speed and >rebroadcast on HF at lower quality (of course, data rebroadcast on HF >would take longer). The M17 protocol could incorporate routing data to >indicate what to repeat/rebroadcast and where. >> >> Just a thought for what [UTF-8?]itâs worth. >> >> Comments anyone? >> >> >> Regards >> >> >> Dave [UTF-8?]â VK2DWG >> >> >> From: walt...@k5wh.net <walt...@k5wh.net> >> Sent: Monday, 26 October 2020 12:47 >> To: freetel-codec2@lists.sourceforge.net >> Subject: Re: [Freetel-codec2] Comments on the M17 project >> >> Here ya go Alan. See if this can answer some if your questions on >that. >> >> https://m17-protocol-specification.readthedocs.io/en/latest/ >> >> all the best.. >> >> >> Walter/K5WH >> >> >> From: Al Beard via Freetel-codec2 ><freetel-codec2@lists.sourceforge.net> >> Sent: Sunday, October 25, 2020 3:27 PM >> To: freetel-codec2@lists.sourceforge.net >> Cc: Al Beard <bear...@unixservice.com.au> >> Subject: Re: [Freetel-codec2] Comments on the M17 project >> >> Hi all, >> >> >> >> What about the "connection" to HF? >> >> >> >> HF where we have bandwidth restrictions hence low bit-rate codecs. >> >> >> >> That's why I asked the question: >> >> >> >> In the M17 protocol, is there a "codec specifier" ? >> >> >> >> Many more questions but one is enough. >> >> >> >> Alan VK2ZIW >> >> >> >> >> >> On Sun, 25 Oct 2020 10:30:17 -0500, walterh wrote >> > Good to see you Gerhard.. >> > >> > I just heard last night that Doug should have his Dude Star >application for Android devices released maybe as early as today, that >supports M17. Like it does for all the other digital modes. >> > >> > I heard him using it last night and it sounded great. >> > >> > >> > Lots of great work happening in just the past week. >> > >> > Walter/K5WH >> > >> > >> > From: gerh...@oe3gbb.eu <gerh...@oe3gbb.eu> >> > Sent: Sunday, October 25, 2020 2:33 AM >> > To: freetel-codec2@lists.sourceforge.net >> > Subject: Re: [Freetel-codec2] Comments on the M17 project >> > >> > Hello Walter and all others, >> > Very interesting project. >> > I think a step in between could be to connect the M17-Client to a >Gnu-Radio / Adalm Pluto TRX setup and use MMDVM / M17. That would >proove the audio quality best. >> > I am goint to setup the M17-Client next days. Could also install a >M17 repeater at OE3XNK using LimeSDR or Pluto as soon some software is >ready. >> > Regards >> > Gerhard OE3GBB >> > >> > >> > >> > Am 25.10.2020 02:24, schrieb walt...@k5wh.net: >> >> > >> > I honestly don't see how that claim could be made at this time, as >there is NO radio on the air at this point to demonstrate that. >😊 >> > >> > Perhaps it's a theoretical performance based on the current design, >and it would certainly be incredible to see that. >> > >> > Right now, we are ONLY using software on linux to connect to the >backend reflectors. >> > >> > So hopefully we will know about the true results when the guys get >their radios going in a week or two, as their components are still >coming in from vendors. >> > >> > Walter/K5WH >> > >> > -----Original Message----- >> > From: David Rowe <da...@rowetel.com> >> > Sent: Saturday, October 24, 2020 7:28 PM >> > To: freetel-codec2@lists.sourceforge.net >> > Subject: Re: [Freetel-codec2] Comments on the M17 project >> > >> > Thanks Walter. I was wondering about this statement on the M17 >page: >> > >> > "M17 uses Codec2, written and developed by David Rowe. Codec2 >outperforms existing proprietary and patented (non-free) vocoders >currently available." >> > >> > Do you (or others on this list) think Codec 2 at 3200 bits/ >outperforms the codecs used for DMR/DStar and friends? >> > >> > - David >> > >> > On 25/10/20 10:01 am, walt...@k5wh.net wrote: >> > > Here's a few notes I sent to someone else earlier today. >> > > >> > > >> > > >> > > >> > > >> > > M17 is a very NEW project with a great deal of traction just >recently. >> > > >> > > >> > > >> > > https://m17project.org/faq/ has some details about what is >happening. >> > > >> > > >> > > >> > > This is a completely open source project using David Rowe's >Codec2 for >> > > the encoding scheme. Much like the FreeDV for HF we have been >using >> > > for many years. >> > > >> > > >> > > >> > > They have modified the back-end around Dstar for the reflectors >and >> > > modules, using a very slightly modified version of the xlxd >software >> > > for building reflectors. >> > > >> > > >> > > >> > > Seems that the reflector count has risen from 3 to 12 in the past >3 >> > > days, so the word is still getting out to others. >> > > https://m17project.org/reflector/ >> > > >> > > >> > > >> > > There is no commercially available radio, but the TR-9 is the >radio >> > > that has been designed for it today. I understand they just got >their >> > > alpha pc-boards barely a week ago, and are still sourcing the >> > > components for it. But there should be some RF available in a >week or so. >> > > >> > > >> > > >> > > Jonathon Naylor has just updated the MMDVM code to support M17, >and >> > > the hotspot devices and the gateway components are being worked >next. >> > > His early comment below. >> > > >> > > >> > > >> > > Hi All >> > > >> > > I've just finished the first round of developing M17 support for >the >> > > MMDVM. It is based on the current specification of M17, but it is >a >> > > dynamic protocol so it may well change before long. I've raised >some >> > > issue with the M17 developers which may mean changes to address >those >> > > issues. >> > > >> > > Currently M17 won't work with MMDVM hotspots based on the chip >> > > modem/radio, only those systems based on MMDVM modem boards. In >theory >> > > the levels are correct and you should be able to load the modem >code, >> > > and the MMDVM Host from the M17 branch and off you go. I don't >know if >> > > it works as I have no M17 radios. Once we get hotspot support for >M17 >> > > then I think it'll be possible to use them as low powered M17 >transceivers. >> > > >> > > On the networking side, it only connects to one M17 reflector, >and >> > > that is set in the ini file. Currently it's set to M17-USA module >A. >> > > If things move on with M17 then I will create a proper M17 >Gateway >> > > program with echo functionality to allow for dynamic control of >the >> > > reflector, but that is far off at the moment. >> > > >> > > I have tested my code against itself, and most of it seems to >work, >> > > some corners have not been tested yet, but they will be in due >course. >> > > >> > > If anyone has an M17 transceiver and wishes to play with the >code, I'd >> > > be interested in what happens. >> > > >> > > Jonathan G4KLX >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > So it is early in the development stages, but things are indeed >moving >> > > fast, as of just the ast few weeks. >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > Walter/K5WH >> > > >> > > >> > > >> > > *From:* Adrian Musceac <kanto...@gmail.com> >> > > *Sent:* Saturday, October 24, 2020 3:27 PM >> > > *To:* freetel-codec2@lists.sourceforge.net >> > > *Subject:* Re: [Freetel-codec2] Comments on the M17 project >> > > >> > > >> > > >> > > Hi Walter, >> > > >> > > Is there like a mailing list of the project or something? >> > > >> > > Adrian >> > > >> > > On October 24, 2020 4:13:56 PM UTC, walt...@k5wh.net >> > > <mailto:walt...@k5wh.net> wrote: >> > > >> > > Several of us have been working with M17 for the past week, >using >> > > the Mvoice linux client, and it's working quite well with the >> > > reflectors they have in place today. >> > > >> > > >> > > >> > > The number of reflectors have increased from 3 early last >week to 9 >> > > as of this morning, with a couple more that should show up >today. >> > > >> > > >> > > >> > > Since it uses the Dstar concept for reflectors, each one can >support >> > > modules A-Z, so 26 different sets of qso's if it ever gets >that >> > > busy. 😊 >> > > >> > > >> > > >> > > I am greatly looking forward to seeing the TR-9 radio on the >air >> > > before too long, to really exercise the mode, as the MMDVM >and >> > > hotspot code gets updated by Jonathan. >> > > >> > > >> > > >> > > Once the gateway option is available, then cross-modes of >DMR/Fusion >> > > etc.. to M17 should will ramp things up until more radios are > >> > > available. >> > > >> > > >> > > >> > > It's really exciting for me to see yet another opportunity >for >> > > David's Codec2 to truly shine for us. >> > > >> > > >> > > >> > > M17 is another great victory for the Open Source World! >> > > >> > > >> > > >> > > Walter/K5WH >> > > >> > > >> > > >> > > -----Original Message----- >> > > From: Al Beard <bear...@unixservice.com.au >> > > <mailto:bear...@unixservice.com.au>> >> > > Sent: Saturday, October 24, 2020 12:52 AM >> > > To: freetel-codec2@lists.sourceforge.net >> > > <mailto:freetel-codec2@lists.sourceforge.net> >> > > Subject: [Freetel-codec2] Comments on the M17 project >> > > >> > > >> > > >> > > Hi all, >> > > >> > > >> > > >> > > I was looking at the M17 project and noticing their >discussion on >> > > callsign sending. Suggesting in 48 bits for Src and Dest, >packing >> > > the characters as RT11 filenames used to do. (Digital PDP-11 >of >> > > 1975) >> > > >> > > >> > > >> > > What I notice in our HF mode 700D, it has quite poor data >> > > reliability particularly in the "Txt MSG" which is where the >Src and >> > > Dest data may well be. >> > > >> > > >> > > >> > > Adding 96 bits to every frame is in my view way too many >bits. >> > > >> > > In our current modes eg. 700D, could we sacrifice every tenth >frame >> > > for source and destination? >> > > >> > > >> > > >> > > Thoughts? >> > > >> > > >> > > >> > > --------------------------------------------------- >> > > >> > > Alan VK2ZIW >> > > >> > > Before the Big Bang, God, Sela. >> > > >> > > OpenWebMail 2.53, nothing in the cloud. >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > _______________________________________________ >> > > >> > > Freetel-codec2 mailing list >> > > >> > > Freetel-codec2@lists.sourceforge.net >> > > <mailto:Freetel-codec2@lists.sourceforge.net> >> > > >> > > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 >> > > >> > > >> > > >> > > _______________________________________________ >> > > Freetel-codec2 mailing list >> > > Freetel-codec2@lists.sourceforge.net >> > > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 >> > > >> > >> > >> > _______________________________________________ >> > Freetel-codec2 mailing list >> > Freetel-codec2@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 >> > >> > >> > _______________________________________________ >> > Freetel-codec2 mailing list >> > Freetel-codec2@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/freetel-codec2 >> >> >> --------------------------------------------------- >> Alan VK2ZIW >> Before the Big Bang, God, Sela. >> OpenWebMail 2.53, nothing in the cloud. > >--------------------------------------------------- >Alan VK2ZIW >Before the Big Bang, God, Sela. >OpenWebMail 2.53, nothing in the cloud. > >
_______________________________________________ Freetel-codec2 mailing list Freetel-codec2@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freetel-codec2
