fix: AFV improvements, volume + mute radio controls, better top-bar & minor fixes

[GeorgeBarlow]

Improvements:

• AFV better event handling in main.cpp
• Volume + mute support (incorporates: Add volume bar per station #242, courtesy of @GeheimagentNr1)
  • Support added in the SDK (example: Add dial support for managing station volume neilenns/streamdeck-trackaudio#312)
• Other useful minor fixes

SDK Changes

New Properties

• outputVolume: Controls individual station volume (0-100)
• isOutputMuted: Controls muting state per station
• mainOutputVolume: Controls global output volume (0-100)

New Inbound Events

Event	Description	Data Structure
kChangeStationVolume	Adjust volume for station	{"amount": number, "frequency": number}
kGetMainOutputVolume	Requests the current main volume
kChangeMainOutputVolume	Adjust global volume	{"amount": number}

Volume Change Amounts

kChangeStationVolume: amount can be positive/negative to increase/decrease volume
kChangeMainOutputVolume: amount can be positive/negative to increase/decrease volume

New Outbound Events

Event	Description	Data Structure
kMainOutputVolumeChange	Global volume changed/requested	{"volume": number}

Modified Events

Station State Updates

Station state messages now include additional audio control fields:

{
 "type": "kStationStateUpdate",
 "value": {
   "outputVolume": number,  // 0-100
   "isOutputMuted": boolean,
   ...
 }
}

Station States Response

The kStationStates response array includes the new audio control fields for each station:

{
  "type": "kStationStates",  
  "value": {
    "stations": [
      {
        "outputVolume": number,
        "isOutputMuted": boolean,
        ...existing fields
      }
    ]
  }
}

RxEnd Updates

The kRxEnd response now includes lastRx array of station callsigns:

{
  "type": "kRxEnd",
  "value": {
    "callsign": string,
    "lastRx": string[],
    "pFrequencyHz": number
  }
}

[neilenns]

Messing around with this and I've noticed a couple of things:

1. I'm always getting two kRxBegin messages when a pilot calls up
2. I can mute UNICOM and GUARD via the websocket interface, however the TrackAudio UI doesn't show the Rx button in red for those frequencies like it does for regular stations

[GeorgeBarlow]

1. I'm always getting two kRxBegin messages when a pilot calls up

Think this has always been the case?

2. I can mute UNICOM and GUARD via the websocket interface, however the TrackAudio UI doesn't show the Rx button in red for those frequencies like it does for regular stations

Resolved

[GeheimagentNr1]

I just tested the current main branch (commit cb5776d) state, with the new volume system.
If I use the mouse wheel, a JavaScript error is shown in the console:

If I change the main volume below 50% the frequency is muted.

[neilenns]

@GeheimagentNr1 Since it already got merged might as well open a bug for those

[GeorgeBarlow]

I just tested the current main branch (commit cb5776d) state, with the new volume system. If I use the mouse wheel, a JavaScript error is shown in the console: If I change the main volume below 50% the frequency is muted.

Fixed