Here's a quick video I mostly made for fun:
https://youtu.be/PqJcU4vje2Q
#Carla #FOSSaudio #LinuxAudio #FullBridgeRectifier #unfa

@unfa I saw you were having issues there finding newly added plugins. I just fixed that! https://github.com/falkTX/Carla/commit/c986c868602c7c3fa7e90ae2747074aa8341608d

@falktx Ah, that's great! Thank you! I think I'll make a video about Carla soon. I've finally checked out the new CV stuff.

@unfa cool, let me know if you find any issues! You got VST3 now on Linux too btw 😎

@falktx Another issue: re-opening the Carla-Patchbay internal plug-in's interface messes up the node layout of that patchbay. Reloading from a saved carxp file fixes that layout.

@unfa ah yes, because the canvas positions are saved in the json file, not the main carla project file.
it is an architecture/design problem. the plugin version has some state, but the UI is something that needs to be saved as well, even though the DSP/backend side has no use for it.
I can add a canvas->save-positions action, but having that automatic is tricky. we do not want to keep sending position data all the time, and we dont want to wait for UI stuff when saving host session. thoughts?

@unfa hmm thinking more about this, perhaps the UI can just tell the DSP/engine when a plugin position in the canvas changes, just caching values for saving in the project. the engine side of things has no use for it whatsoever, but it is just too useful and worth the small memory usage.
I will try this!

@falktx That sounds like a solution! So the canvas layout would then be stored inside the carxp file along the processing data? It would also be easier from a user's point of view to have one file instead of two.

@unfa Yes! I am working on this right now as I type.

@falktx Fantastic, thank you!

@unfa now on latest git/develop of carla. Though I need to do some more testing to see if I find some edge cases or bugs. If you try it, let me know how it goes.