https://bugs.kde.org/show_bug.cgi?id=514086
--- Comment #19 from [email protected] --- I chatted a little with an AI chatbot and I think I now understand a little more about the process. I think I understand that: - MLT is responsible for managing the plugins in Kdenlive. - For example, Jack logic is used for VST2. - In some cases, ‘effEditOpen’ is called, which generates the GUI. - Some older plugins are not ‘headless-friendly’ and initialise the graphics resources already at ‘effOpen’. As a simple user, it would be enough for me if I had the option to intervene (since the number of VST plugins I would use for video editing is limited), e.g. - Do not initialise any VST plugins by default. - Manually activate the VST plugins. - If necessary, select a directory from which to load the VST plugins. - If necessary, choose between the default path (env VST_PATH) or the user path (no env VST_PATH). I would certainly not use instrument plugins in video editing as I would in a DAW :) That would be a big help. It would be nice to have: - A plugin management system that, when or before activating the plugin function - Searches through the plugins with a progress bar. - Makes the plugins activatable/deactivatable. Don't be angry, these are just the thoughts of a simple user, and AI is not necessarily the best expert to ask :) -- You are receiving this mail because: You are watching all bug changes.
