flowblade
flowblade copied to clipboard
jliljebl
Select specific audio track from source file?
Flowblade 2.4.0 MLT 6.18.0 Flatpak package
I poked around the UI a lot, but I couldn't find what I was looking for. I automatically record gameplay footage and like to make gameplay clips, and would like the ability to select a specific audio track from source files. I record three tracks: game audio, mic audio, and a blend of the two.
It might be overkill to use Flowblade for that, but it seemed intuitive enough to figure out and use up until the point where I wanted to pick which audio track from the source file would get used, and I couldn't find that at all. Am I missing something, or is that not possible yet?
Thanks kindly. :)
Hi, that is not possible yet. There is a limited workaround using an MLT XML export and a shell script, but that workaround only allows you to select 1 specific audio track for the entire project. I expect you want to select the audio track for every segment on the timeline. I have done some work on that, but it's far from complete, as I'm currently working on something else. It IS possible to do it using the MLT XML export, but it would require manually modifying the XML, which is rather complex. Another workaround could be to create a new clip with the correct audio for each clip you want to use using the export method ed and my script and then using those clips in your final project. Only clips with audio track 2 or 3 need to be created, because the default used by Flowblade is 1.If you want more info on my script let me know.
Hey there, thanks for responding.
EDIT: Oops, forgot which issue I was commenting on! I'm using LosslessCut for now to handle this, and I appreciate your earnest response. Do you want to leave this issue open to track eventual implementation?
I'll add this into feature queue, this surely a useful feature. Not sure about immediate prospects but I'll look around in next cycle and update here.
This was a duplicate of another Issue I just closed after doing some programming tests for it. There seems to be no plausible way forward with this issue, so I'm closing this as 'wotfix'.