Author Topic: Wrong Bitrate in Radio Control on the Web if  (Read 6445 times)

fnord

  • Newbie
  • *
  • Posts: 21
    • View Profile
    • Email
Wrong Bitrate in Radio Control on the Web if
« on: 2011-05-09, 07:52:59 »
I see always the codec alaw 8KHz on the Status Display.
But i selected Linear 16KHz



Name   Value
Radio   OFF
SIP status   Connected/transfering
Last SIP error   None
RTP Timeout   60
SIP Timeout   0
Rx Jitter buffer size   16
Rx Jitter delay   14
Dual Rx   0
Current audio packet size   20
Current audio quality   0 - alaw 8 kHz
SIP Out port   5060
SIP In port   5060
Audio Out port   11000
Audio In port   11000
Command Out port   12000
Command In port   12000
External SIP In port   5060
External Audio In port   11000
External Cmd In port   12000
Other party   192.168.0.233
Input 1   High
Input 2   High
Output 0   Low
Output 1   Low
Output 2   Low
DynDns status   Unknown
Ping status (watchdog)   OK [0 ms]
Active profile:   Default
PTT status:   OFF

Jan (Microbit)

  • Software Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 1829
    • View Profile
    • Email
Re: Wrong Bitrate in Radio Control on the Web if
« Reply #1 on: 2011-05-09, 08:58:13 »
You have selected "Linear 16KHz" in both control and radio RRC, and still see "codec alaw 8KHz" in the radio RRC?
Always include type of hard/software and version when asking for support.

fnord

  • Newbie
  • *
  • Posts: 21
    • View Profile
    • Email
Re: Wrong Bitrate in Radio Control on the Web if
« Reply #2 on: 2011-05-09, 17:11:21 »
I dont have any selection on the RRC client on PC

Jan (Microbit)

  • Software Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 1829
    • View Profile
    • Email
Re: Wrong Bitrate in Radio Control on the Web if
« Reply #3 on: 2011-05-09, 17:21:06 »
Aha, you have a RRC-Micro! Then it is because the RRC-Micro only supports that codec and so the RRC is configured on the fly to change codec when a RRC-Micro connects.
Always include type of hard/software and version when asking for support.

fnord

  • Newbie
  • *
  • Posts: 21
    • View Profile
    • Email
Re: Wrong Bitrate in Radio Control on the Web if
« Reply #4 on: 2011-05-09, 19:48:12 »
sorry 8KHz alaw is a very poor quality  (less than 4KHz Speech Headroom) thats not suitable for DRM receiving and not even for G3RUH modulation.
so i couldnt use the RRC Micro for some digital modes.
no wonder i got very poor SNR on digital SSTV with alaw, cuz its not even a linear mode!

fnord

  • Newbie
  • *
  • Posts: 21
    • View Profile
    • Email
Re: Wrong Bitrate in Radio Control on the Web if
« Reply #5 on: 2011-05-09, 22:47:11 »
a chance to add at least the linear codecs to the RRC Client in forseeable future?

roland

  • Guest
Re: Wrong Bitrate in Radio Control on the Web if
« Reply #6 on: 2011-05-10, 09:53:34 »
a chance to add at least the linear codecs to the RRC Client in forseeable future?
We will add Linear 16bit 8 kHz.
Can't give any exact date on this as there are some others things in the pipeline.
However it will be within the range of a couple of months.

fnord

  • Newbie
  • *
  • Posts: 21
    • View Profile
    • Email
Re: Wrong Bitrate in Radio Control on the Web if
« Reply #7 on: 2011-05-10, 14:18:33 »
well 16bit and 8KHz gives a little bit more dynamic reserves, but its still limited to 4KHz and thats not transparent for my opinion.
according to nyquist you need at least the double bandwidtdh, but due some AD/DA DA/AD conversions you add additional quantisation noise and this could only be defeated with higher sampling frequencies e.g 24KHz for a 10KHz AM(DRM) signal.

my idea to use the RRC Micro was just the idea behind less wiring in the Audio TX/RX Path with Virtual Audio Cable, so i have less AD/DA conversions.
Another idea is a SP/DIF IN/OUT in future versions of the Remoterig Control, but the best is adding a clock accurate USB Soundmodule into the Remoterig ( e.g dr. dac nano usb soundcard has a -+5ppm tcxo)
Yes that makes it more expensive, but i would pay 100 bucks more for such features, so it should be sold separately.