[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 [email protected] changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #21 from [email protected] --- Excuse me, did I overlook something or react incorrectly? Can I provide any further information? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #20 from Bug Janitor Service --- đ𧚠â ď¸ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
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.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #18 from [email protected] --- Yes, if I only have a few plugins in the folder, then Kdenlive starts. As the number of plugins increases, so does the loading time and memory usage. I would just find it a shame if I had to change the logic that works for all other programs. After all, all programs find the plugins in the VST_PATH. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #17 from mrfantastic --- Well in the scan for VST2, ladspa and other old plugin formats there must be code that run to define the plugin for the host (but some newer plugin formats might use XML or JSON file to define it such as LV2) so there could be a problematic plugins as you described. But if you try to limit VST2 plugins in your vst2 path folder does kdenlive work for you? does plugins function then? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #16 from [email protected] --- (In reply to mrfantastic from comment #13) > When you lunch kdenlive in windows the plugins UI appear? No, there is no plugin window. What you see in the screens is all what appears and with a klick on "New Projekt" the magic starts :) > Is it because you have too much plugins it stuck or there is specific > plugin/s need to be blacklisted? Yes, there are quite a few plugins. If I compare the process to Ardour, for example, the following happens in Ardour: - A window appears that scans for plugins. - After a few seconds, an overview of all plugins is displayed, with incompatible or inactive ones shown as inactive. - However, the actual plugin is only initialized when I use it in the project. This works in a similar way in all the programs I use, so the number of plugins isn't really a problem. I have a feeling the problem might arise because each individual plugin is initialized during the scan? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #15 from mrfantastic --- Maybe you can rename folder and make new one just copy one or two simple plugins into the new folder (The VST_PATH I mean ofcourse) and see if it will crash. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #14 from mrfantastic --- Created attachment 190177 --> https://bugs.kde.org/attachment.cgi?id=190177&action=edit VST2 SwankyAmp in kdenlive -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 mrfantastic changed: What|Removed |Added CC||[email protected] --- Comment #13 from mrfantastic --- When you lunch kdenlive in windows the plugins UI appear? Is it because you have too much plugins it stuck or there is specific plugin/s need to be blacklisted? I implemented VST2 and LV2 support for mlt and to my knowledge it is working only with generic UI in kdenlive because I don't think there is progress in getting Custom GUI yet on my GNU/Linux machine many VST2 plugins works just fine such as SwankyAmp. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #12 from [email protected] --- Created attachment 190090 --> https://bugs.kde.org/attachment.cgi?id=190090&action=edit Screenshot from the startup process -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #11 from [email protected] --- Created attachment 190089 --> https://bugs.kde.org/attachment.cgi?id=190089&action=edit Screenshot from the startup process -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #10 from [email protected] --- Created attachment 190088 --> https://bugs.kde.org/attachment.cgi?id=190088&action=edit Screenshot from the startup process -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #9 from [email protected] --- Created attachment 190086 --> https://bugs.kde.org/attachment.cgi?id=190086&action=edit Screenshot from the startup process -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #8 from [email protected] --- (In reply to Bernd from comment #6) > Ok, I could have deduced it from that. My bad. Still, I am wondering why the > variable being available makes Kdenlive parse that directory and ingest .dll > or other library files for processing. Well, I'm afraid I can't answer that. I don't know why Kdenlive does the things it does :) > > It doesn't matter which one set or sets it, apparently Kdenlive parses the > directory set by it. No idea why it does it and what it does with the > filters and how it exposes them in the UI. Do you have any screenshots? It's a bit difficult to take screenshots because the GUI only flashes very briefly. I recorded a video, but it's a bit too large. So perhaps a few screenshots from the video will do. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #7 from [email protected] --- Created attachment 190083 --> https://bugs.kde.org/attachment.cgi?id=190083&action=edit Screenshopt from startup prozess -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #6 from Bernd --- (In reply to blackcat00 from comment #5) > Well, I'm not entirely sure I understand the question correctly. As > mentioned, two environment variables are set on my system: > > VST_PATH and VST3_PATH. > > Since removing these paths seems to help not to load the VST files, I assume > that's why Kdenlive sees these plugins. Ok, I could have deduced it from that. My bad. Still, I am wondering why the variable being available makes Kdenlive parse that directory and ingest .dll or other library files for processing. > I have several programs installed on my system that use VST plugins, but I > can't say which one of them has set these environment variables. It doesn't matter which one set or sets it, apparently Kdenlive parses the directory set by it. No idea why it does it and what it does with the filters and how it exposes them in the UI. Do you have any screenshots? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #5 from [email protected] --- Well, I'm not entirely sure I understand the question correctly. As mentioned, two environment variables are set on my system: VST_PATH and VST3_PATH. Since removing these paths seems to help not to load the VST files, I assume that's why Kdenlive sees these plugins. I have several programs installed on my system that use VST plugins, but I can't say which one of them has set these environment variables. Possible candidates are Mixcraft Pro Studio 10, MPC Beats, Ableton Live, Audacity, Ardour, and LMMS. May be More. All of them work fine. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 Bernd changed: What|Removed |Added CC||[email protected] Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Bernd --- How did you get Kdenlive to see those VST Plugins? Where did you get them from? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #3 from [email protected] --- Hello, I've been testing 25.12.2. Currently, the loading time on the first launch seems to have increased (around 5-10 Minutes). Subsequent launches appear to be a little faster. After clicking "New Project," I repeatedly see windows flash briefly, which seem to be the individual VST plugin GUIs. After a very long time, i see a Kdenlive window and a window for a VST plugin, but I can't input anything in the program or the VST window; it seems to be frozen. In the Task Manager, I see two child processes: rundll32.exe Windows Host Process (Rundll32): rundll32 "E:VST\Steinberg\vstplugins\MPC Beats64.dll", ProxyMidiPort 7580 rundll32 "E:VST\Steinberg\vstplugins\MPC Beats64.dll", ProxyMutex 7580 (The individual processes seem to vary with each launch.) If I kill these two processes, another process, "Window Name," appears. If I kill that one too, everything seems to work, but it doesn't. The newly started Kdenlive then currently uses about 13.5 GB of RAM. Currently, I'm using a workaround startup script: Kdenlive_NoVST.bat @echo off rem Hide VST paths for this process only set VST_PATH= set VST3_PATH= rem Start Kdenlive .\kdenlive.exe This version, started this way, comes up in seconds and then uses about 350 MB of RAM. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 [email protected] changed: What|Removed |Added CC||[email protected] --- Comment #2 from [email protected] --- Has this changed at all for you since 25.12.2 since you reported ? If not, this issue should be elevated in priority. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 514086] kdenlive startup problems with VST Plugins (crash, Memory Leak)
https://bugs.kde.org/show_bug.cgi?id=514086 --- Comment #1 from [email protected] --- Since Kdenlive only starts the plugin scan after the intro dialog, wouldn't it be possible to programmatically reset the VST path or set it to a user-defined path from the Kdenlive configuration? Something like ``` _setenv("VST_PATH", config_vst_path.c_str(), 1); _setenv("VST3_PATH", config_vst3_path.c_str(), 1); initializeMLT(); ``` -- You are receiving this mail because: You are watching all bug changes.
