Desktop video player doesn't play first audio track in mp4

[algielen]

Steps to reproduce

1. Create video file with two audio tracks, in my case MP4 created with Shadowplay and the feature "Separate both tracks"
2. Send video file to a Telegram conversation
3. Play the video on desktop in the integrated video player

ffprobe gives the following info for the file

Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '.\filename.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    creation_time   : 2023-09-03T17:37:52.000000Z
    date            : 2023
  Duration: 00:00:30.22, start: 0.000000, bitrate: 34165 kb/s
  Stream #0:0[0x1](und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, smpte170m, progressive), 1920x1080 [SAR 1:1 DAR 16:9], 33768 kb/s, 60 fps, 60 tbr, 90k tbn (default)
    Metadata:
      creation_time   : 2023-09-03T17:37:52.000000Z
      handler_name    : VideoHandle
      vendor_id       : [0][0][0][0]
  Stream #0:1[0x2](und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 192 kb/s (default)
    Metadata:
      creation_time   : 2023-09-03T17:37:52.000000Z
      handler_name    : SoundHandle
      vendor_id       : [0][0][0][0]
  Stream #0:2[0x3](und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 192 kb/s (default)
    Metadata:
      creation_time   : 2023-09-03T17:37:52.000000Z
      handler_name    : SoundHandle
      vendor_id       : [0][0][0][0]

Expected behaviour

Video player should load the first audio track, as on Telegram mobile, or as in VLC and mpv

Actual behaviour

Video player loads the second audio track, which is not the intended one

Operating system

Windows 11 (22H2)

Version of Telegram Desktop

4.9.4 x64

Installation source

Static binary from official website

Crash ID

No response

Logs

No response

[github-actions[bot]]

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!