Bug 475311

Summary:	Video-File with multiple Audio Streams uses only the first one regardless of choice
Product:	[Applications] kdenlive	Reporter:	Bruno DeVries <kde_bug>
Component:	User Interface & Miscellaneous	Assignee:	Jean-Baptiste Mardelle <jb>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	fcicrcm
Priority:	NOR
Version First Reported In:	23.08.1
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Bruno DeVries 2023-10-07 10:28:15 UTC

SUMMARY
***
Probably in same league with 474140 and 474141
When using a  video file with multiple audio streams only the position #0 stream will get a thumbnail/waveform and when inserted into the time, even when #0 is deselected under clip properties, x copies of audio-stream #0 will be used where x is the number of active audio streams. All other audio streams will be ignored.
Tested with OBS records, MKV container files and ogg/vorbis audio
***


STEPS TO REPRODUCE
1. Record Video with multiple audio streams using obs in matroshka container
2. Drag & Drop into kdenlive
3. Drag into timeline

OBSERVED RESULT
One Video appears and x copies of the waveform of audio stream #0, when playing only one audio stream is used (or the same 5 times)

EXPECTED RESULT
Get Video and x waveforms of different audios that can be mixed up

SOFTWARE/OS VERSIONS
Windows: Win10Pro N 22H2
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Tested with only mkv container, created by obs with 5 audio streams in it. This issue does not exist in kdenlive 22.12.3

Comment 1 Svyatoslav 2023-10-10 23:55:23 UTC

Can confirm I also have this bug. I am forced to extract audio tracks with Right Click on Clip -> Extract Audio -> Wav 48000Hz to obtain correct track.

KDE Frameworks: Version 5.109.0
Qt: Version 5.15.10 (built against 5.15.10)
MLT: Version 7.19.0
OS: Windows 10 Pro 21H2 (19044.1645)

Comment 2 Jean-Baptiste Mardelle 2023-10-31 10:17:20 UTC


*** This bug has been marked as a duplicate of bug 475233 ***