https://bugs.kde.org/show_bug.cgi?id=491108
--- Comment #9 from Uwe Dippel <udip...@gmail.com> --- (In reply to Uwe Dippel from comment #3) > It's not illogical nor inconsistent. Video tracks are always composited > together because in any container there is only one video track (AFAIK). On > the other hand, there can be multiple audio tracks or channels, so it makes > perfect sense to handle them differently. That's your opinion. For me it looks the other way round. There are use cases for empty tracks, there are cases (most) where you have a single video track. I myself remember a project, where I had multiple video tracks that needed rendering of more than one separate video tracks. Then, they had to be enabled/disabled, saved under another name, and rendering to be restarted. The topic 'multiple video tracks in a single container' isn't the staple one, but has been discussed for quite some time. MKV for example, does that easily. I do agree, there should be a warning once a user runs into this situation, asking if this is really what he wanted, because players usually do not support this.. The default would always be mixing the streams together. But that's not much different with audio. >From the average user perspective, we always try to construct the UI such that the user doesn't have to know, think, ponder; rather straight forward handling, with as many as possible duplications and similar implementations of an interface. I had started working on, later with, FOSS 25+ years ago. And was so frustrated that all our great stuff wasn't really appreciated by the general public. I've learned why. My favourite editor is still vi. And I know I'd be a bore telling my wife how great it is. HCI must never be seen from the insider perspective. Though I stop before deviating too far off the topic. -- You are receiving this mail because: You are watching all bug changes.
