Bruce, This is probably outside the scope of this thread, but if we do implement linking of repeaters, I think we should go with a totally open structure without any requirement to register user callsigns. I am also thinking of doing an open-source repeater/Echolink conference server package (with client) that utilizes Codec2 between compatible software; this will have the added bonus that the Echolink client can be routed to, since the callsign of the repeater will be available for the client to use. The above software will likely include a way to interconnect with D-Star via ircDDB.
Matthew Pitts N8OHU ------------------------------ On Wed, Apr 18, 2012 7:56 PM EDT Bruce Perens wrote: >On 04/18/2012 04:18 PM, Peter wrote: > I understand why this is good. The issue I can see is that the FEC/Payload > would likely be different depending on codec bitrate and target bitrate. >Codec bitrate should be part of whatever field identifies the codec. If you >get voice messages at different rates over some high-speed transport, you >should be able to decode them all. > >Yes, please do more layers as you describe. Given the interest in linked >repeaters, etc., we can expect to have a lot done to the transport other than >our usual VHF/UHF link. > > Thanks > > Bruce ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Freetel-codec2 mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freetel-codec2
