Independent volume control for bi-directional communication

I have a pair of SDKs and have them working bi-directionally in both walkie-talkie mode (microphone) and line-in (I2S). The volume control on both headset and gateway only control the volume on the headset. I would like to be able to control the headset volume on the headset and gateway volume on the gateway. Must be something simple right?

Thanks!

Rich

Parents
  • Hi Rich,

    Thanks for checking with us. This could potenionally be a new feature reqest.

    I will check with out developer if we could make it works as this when walkie-talkie mode is enabled.

    I will send you an update if any feedback is avaliable.

    Best regards,

    Charlie

  • Thanks. Implementing for bi-directional mode (not walkie-talkie mode) is preferred because then it is adjustable for both microphone and line-in.

  • Hi Rich,

    I got explaination about volume control services and local volume control:

    The volume control services  are intended to adjust volume on the remote device. That is, the Volume Controller (the VCS client) controls the volume on the Volume Renderer (the VCS server, the device playing back the audio).

    It is expected that on the Volume Renderer there may in addition also be local volume control. 

    Local volume control is outside the scope of the specs, so how this is done is up to the implementation. Developer can use the local buttons and the API to do volume changes. 

    In usual client/server cases, if local volume control is used, the local changes should be notified to the Controller, to allow the Controller to be in sync with the actual volume state.)

    All that being said, using VCS may not make sense for a walkie-talkie. The volume control specs are typically used when there is one device playing back audio and another device used to control the volume - asymmetrical situations but with the same user using both devices. A walkie talke is more or less the opposite of this - this is a symmetric situation, and there are two users, each having their own end of the conversation. Controlling the volume of the other user's device is typically not what one wants.

    So the solution may be to just remove the volume control services and use only local volume control, please try to call the API from hw_codec.c to control the codec chip to change volume in the local side.

    Best regards,

    Charlie

Reply
  • Hi Rich,

    I got explaination about volume control services and local volume control:

    The volume control services  are intended to adjust volume on the remote device. That is, the Volume Controller (the VCS client) controls the volume on the Volume Renderer (the VCS server, the device playing back the audio).

    It is expected that on the Volume Renderer there may in addition also be local volume control. 

    Local volume control is outside the scope of the specs, so how this is done is up to the implementation. Developer can use the local buttons and the API to do volume changes. 

    In usual client/server cases, if local volume control is used, the local changes should be notified to the Controller, to allow the Controller to be in sync with the actual volume state.)

    All that being said, using VCS may not make sense for a walkie-talkie. The volume control specs are typically used when there is one device playing back audio and another device used to control the volume - asymmetrical situations but with the same user using both devices. A walkie talke is more or less the opposite of this - this is a symmetric situation, and there are two users, each having their own end of the conversation. Controlling the volume of the other user's device is typically not what one wants.

    So the solution may be to just remove the volume control services and use only local volume control, please try to call the API from hw_codec.c to control the codec chip to change volume in the local side.

    Best regards,

    Charlie

Children
No Data
Related