Hi Pierre, sorry to push you are you working again on Camomile? I'd really like to have multiple instances and external libraries support. All the best!

Normally, I should be able right now ! I just finished my 3 years long hard work

That's great!

thrilled about new github activity on Camomile! thanks @Pierre-Guillot !

So I'm working on a new major release. It means that there will be a lot of changes ! The plugin will be used as some kind of a meta plugin to create other plugins with specific names (and all the plugins/patches will have their own configurations, their own presets, etc.). Another big change is that the parameters are no more determined depending on the GUI (graphical user interface). You'll still be able to change their values with the GUI if you want but their creation won't depend on it. It's not ready for the moment (I working very hard on it) but I would like to have some of your idea and feedback. My principal issue is how to describe the functionalities of the plugin. So if you want to discuss about it feel free to do so. It would be easier for me on this Github issue and I'll try to integrate the comments left here.
Cheers

Question:

With the next release of Camomile, to generate a new plugin you need to create a folder with the name of the plugin that contains the patches and a small text file that describes the plugins functionalities and options (parameters, presets, MIDI support, etc.). Then you need to use a small script that automatically generates and install all versions of your plugins. It depends on the Camomile versions installed (on MacOS this can be VST, VST3 & AU, on Windows VST & VST3 and on Linux VST only I guess). It also depends if your plugin is an Instrument or an Effect. And to generate the plugins the script will use the instrument or the effect versions of Camomile. So I propose that the names of the plugins should be followed by Fx if the plugin is an effect to distinguish between them. So if your plugin is named MyPlugin it will be an instrument and if the plugin is name MyPluginFx it will be an effect. Does it sound good to you? Otherwise do you have a better idea. Note that it can't be a dynamic option of the plugin. I need to generate the two kinds of plugin with two different binaries.

@Pierre-Guillot Hi Pierre, that sounds good to me. Does this mean that the patch can make use of abstractions? (which will be copied in the folder). And would it work with externals too?

As for other suggestions, I think it would be very helpful to be able for the plug-in to show tables as well as data structures. This would make it possible to design interactive GUIs like sequencers etc. I have no idea if this is feasible though, I'm just throwing it out there.

Thanks for your effort, it's very much appreciated.

Does this mean that the patch can make use of abstractions?

yes, of course. Like for the older versions.

And would it work with externals too?

It seems not, I didn't work on it for the moment. I planned this for 0.1.1 because there are already a lot of things to do.

As for other suggestions, I think it would be very helpful to be able for the plug-in to show tables as well as data structures.

I'd like to but I really need to think on how to implement that. I'd like something that would be sustainable. Perhaps for 0.1.2?

Thanks for feedback!

A short video of the future version: The plugin is a one voice MIDI synthesizer adapted from the Minimoog patch made by Jaime Oliver.

A pre-release is available for MacOS and Linux for tests.

New pre-releases are available for MacOS, Linux and Windows. I compiled everything online because I have neither a Linux nor a Windows machine. I test everything on MacOS, it would be great if some of you could give me feedback on Linux and Windows (and macOS). At least to know if it works.

Hi @Pierre, both the latest Win versions claims for a libpd.dll not found as soon as the DAW scans the new plugins at startup. Should you probably include the libpd.dll into the Camomile.dll Camomile.vst3 CamomileFX.dll and CamomileFX.vst3?

probably we could try a quick test if you upload a compiled libpd.dll somewhere?
i guess that if we put the libpd.dll in the same folder of the compiled plugin we should get some results.

Thanks, I have to investigate why libpd is not included (I think it's a mistake made by the library, the static library seems to be a dynamic library in fact). I prefer not to publish the libpd.dll outside the Camomile distribution because it's a specific version for multi instance support. I'll try to compile the library statically so it will be included in the plugins. And if I don't succeed, I'll rename the libpd.dll something like libpdmulti.dll to avoid future conflicts. I'll keep you informed pretty soon, I planned to have another pre-release in the next few days.

On this Github issue, you can download the plugins with the dlls and I just published a new pre release

Another video for Christmas

A new pre-release beta7 is available! I hope the next one will be the good one! Feedback are welcome.
Cheers

Also if some of you have content about Camomile (videos/tutorials/patches) that may interest the other users, feel free to give me the link and I'll add it to the documentation (just keep in mind that this should be accessible, permanent and a bit didactic if possible).

After more than 2 years, I'm on the way to release a new version of Camomile (v1.0.7)! A beta version is already available, your feedback is welcome! Please, read carefully the documentation. For feature request and bug report, please use the issue section on the Github repository if you can.

Change Log:

• Update Pd version (0.51)
• Update Juce version (6.0.0)
• Remove VST2 support
• Fix PdStalFx - DSP not recompiled (#126)
• Fix PdStalFx - no loadbang (#126)
• Fix PdStalFx - undefined when reloaded (#126)
• Add PdStal - instrument version of PdStalFx (#126)
• Fix openpanel and savepanel methods to use Unix path even on Windows (#131)
• Fix openpanel and savepanel methods to output a symbol instead of a list of 1 element (#137)
• Fix midiin objects support to output all the midi messages (#134)
• Fix midiout objects support for 3 bytes messages and system exclusive messages (#134)
• Fix camomile script to support white space in the path (#136)
• Fix LV2 plugin freeze on Linux (#183)
• Add support for manufacturer (#152)
• Fix support for Logic X (#166)
• Fix default display of parameters of Audio Unit (#153)
• Fix expr objects on Windows (#139)
• Fix MIDI in support for LV2 plugins (#160)
• Minor fixes and improvements

There is a new beta. Here are the other changes:

• Fix object position and margin of GOP (#130)
• Improved dynamic parching support (#128)
• Fix LV2 parameters crash on Ardour (#188)
• Add parameter range support for LV2 (#188)
• Add parameter label support for LV2 (#188)
• Fix one LV2 plugin instance limitation on macOS
• Update AlmondOrgan example
• Add a bundle with pre-compiled examples
  If there is no big issue in the next few weeks, I will release this version. And I'll start to work on the Unity support for the next future.