https://bugs.kde.org/show_bug.cgi?id=498160
--- Comment #6 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 wi
https://bugs.kde.org/show_bug.cgi?id=498160
Jean-Baptiste Mardelle changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|CONF
https://bugs.kde.org/show_bug.cgi?id=498160
emohr changed:
What|Removed |Added
Keywords||triaged
--
You are receiving this mail because:
You ar
https://bugs.kde.org/show_bug.cgi?id=498160
emohr changed:
What|Removed |Added
Priority|NOR |HI
CC||frit
https://bugs.kde.org/show_bug.cgi?id=498160
--- Comment #3 from S. Christian Collins ---
After working through a number of issues trying to get Kdenlive to start, here
is a summary of the issues that I'm seeing with the startup VST plugin scan:
1. The VST scan is fragile. If an element of the pl
https://bugs.kde.org/show_bug.cgi?id=498160
--- Comment #2 from S. Christian Collins ---
I was able to use yabridge's blacklist feature to blacklist any VSTs that would
crash kdenlive when scanned. The offending VST plugins all seem to have the
same thing in common: they can't be used outside of
https://bugs.kde.org/show_bug.cgi?id=498160
--- Comment #1 from S. Christian Collins ---
Created attachment 177045
--> https://bugs.kde.org/attachment.cgi?id=177045&action=edit
terminal output
--
You are receiving this mail because:
You are watching all bug changes.
