 |
Changes have been checked into GIT. See BT 0000591. |
 |
@Andrea_Paz, thank you for testing. That file ladspa_plugins.CINGG_20211010_173317 looks good to me. Note that if you want to include both CinGG's and external ladspa plugins, you have to set the LADSPA_PATH environment variable. And you'll get an separate ladspa index file for each ladspa directory. |
 |
For me it formed a "ladspa_plugin..." inside .bcast5. I deleted this file and starting the new appimage, a similar file forms.I attach the file if you are interested.... ladspa_plugins.CINGG_20211010_173317 (8,494 bytes) |
|
|
Fix available, see BT591: https://www.cinelerra-gg.org/bugtracker/view.php?id=591#c5017 |
|
|
The problem occurs because CinGG uses the complete path of the built-in ladspa plugins to form the file name. On an AppImage, the path is different each time. In itself, this makes sense, if you have multiple versions of CinGG on your system. But I don't think that is a typical use case. Have to see if there is a way to detect we're running as an AppImage. |
|
|
@MatN BUT now I noticed that on past days, I even have multiple with built CinGG. Let me see if I can figure out when a new one is created. |
|
|
@MatN Weird. It looks like every single time the AppImage is started there is a new one but not when you run a built CinGG. It must have something to do with the job id. |
- Anonymous
