`pcmCapabilities` Parameter

[theresalech]

We need to ensure the Protocol Spec calls out that for an audio streaming service, the default parameters are 16khz and 16 bit.

This was decided during the August 22 Steering Committee Meeting.

Additional details:

smartdevicelink/sdl_core@88e0560

This parameter is an extension of AudioPassThru capabilities used for mobile navigation. The system sends separate capabilities in case the channel has something different than AudioPassThru. Core does send this information back, but the mobile SDK is not consuming and/or making available. By default, the expectation with moblile navigation partners is 16khz and 16 bit. Ford recommends formally exposing this through APIs in SDKs.

[joeljfischer]

Wouldn't this be on the rpc spec? Thanks, Joel Fischer

…

________________________________ From: theresalech <notifications@github.com> Sent: Monday, August 28, 2017 3:56:44 PM To: smartdevicelink/protocol_spec Cc: Subscribed Subject: [smartdevicelink/protocol_spec] Expose `pcmCapabilities` Parameter (#14) We need to expose the pcmCapabilities parameter from the RegisterAppInterface response. This was decided during the August 22 Steering Committee Meeting. Additional details: smartdevicelink/sdl_core@88e0560<smartdevicelink/sdl_core@88e0560> This parameter is an extension of AudioPassThru capabilities used for mobile navigation. The system sends separate capabilities in case the channel has something different than AudioPassThru. Core does send this information back, but the mobile SDK is not consuming and/or making available. By default, the expectation with moblile navigation partners is 16khz and 16 bit. Ford recommends formally exposing this through APIs in SDKs. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#14>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABr2l5DX8nSgEOkpMVB3elyCtEZa_meuks5scxt7gaJpZM4PE_PJ>.

[joeygrover]

There should be a default included in the protocol spec.