Missing track fields in metadataChanged message

[david-luksch-nangu]

I didn't find any mention of some track fields being optional in OCast protocol v1.9 description, but metadataChanged message has some fields missing for audio tracks (and video, too).

E.g. when I cast a video:

{
  "dst": "browser",
  "src": "0e528c71-5163-445c-8bbe-ae67533e2786",
  "type": "command",
  "id": 1,
  "message": {
    "service": "org.ocast.media",
    "data": {
      "options": {
        
      },
      "name": "prepare",
      "params": {
        "url": "https://sales-ssl-streamer.nangu.tv:8485/126-pc.mpd",
        "frequency": 1,
        "title": "Dead cast entity 1",
        "subtitle": "Test entity for non-linear DASH playback",
        "logo": "https://placeholder.com",
        "mediaType": "video",
        "transferMode": "streamed",
        "autoplay": true
      }
    }
  }
}

the next metadataChanged message looks like this:

{
  "name": "metadataChanged",
  "options": null,
  "params": {
    "title": "Dead cast entity 1",
    "subtitle": "Test entity for non-linear DASH playback",
    "logo": "https://placeholder.com",
    "mediaType": "video",
    "transferMode": "streamed",
    "textTracks": [
      {
        "type": "text",
        "trackId": "0",
        "enabled": false,
        "language": "",
        "label": "Shaka Player TextTrack"
      }
    ],
    "audioTracks": [
      {
        "type": "audio",
        "trackId": "0"
      }
    ],
    "videoTracks": [
      {
        "type": "video",
        "trackId": "0"
      }
    ]
  }
}

Since enabled, language and label fields are missing completely and OCast-Java assumes (in compliance with the protocol) that the fields are required, it fails to process the message.

Thank you,
David

[juliendelage]

fixed in v1.0.7