Hi,
I would like to share my plugin : Camomile.
Camomile is a dynamic plugin made with Juce that allows to load and control Pure Data patches inside a digital audio workstation.

Feature :

• Support for multiple plugin instances.
• Automatic creation of GUIs (toggle, slider and numbox) toggle, slider, radio, comment, numbox
• Automatic recognition of parameters (name, label, range, minimum, maximum, etc.)
• Up to 8 channels 16 channels
• Up to 32 parameters 64 parameters
• Support for MIDI in and out
• Support for play head position
• Support for BPM

This is a beta version, only available for Mac, but
The last version release is available for Linux, Mac and Windows.
I'll be happy to receive your feedback.
Further information on the wiki.
Cheers

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.

The version 1.0.7 released
https://github.com/pierreguillot/Camomile/releases/tag/v1.0.7

Hello there!

I just discover this amazing post do you think is it possible to use automatonism (complex modular patch) into a software like cubase, ableton,...
here a link if you don't know automatonism:
https://www.google.com/search?q=automatonism+pure+data&rlz=1C1CHBF_frFR877FR878&sxsrf=ALeKk03I5Heb6vRL5j_vzsLLKNwzMXjpxw:1599125466083&source=lnms&sa=X&ved=0ahUKEwjEr-3K1szrAhXwyIUKHRikCNsQ_AUICigA&biw=1522&bih=706&dpr=1.25

If Automatism doesn't use externals and is made with abstractions, I guess it will be possible to generate a plug-in using a patch created with Automatism (but it will not be possible to edit the patch in the DAW).

Okok interesting !
That's a really good project Thanks!

Hi Pierre!

I'm not active by any means in the community at all but I'm following your work (and the work of CICM) with a big passion. I really want to thank you and all of the CICM people for your contributions.

I'm composing some works using faust and pd (and faustgen has been really nice for development) and it was really nice to be able to bundle some of the stuff that I've made in LV2 and VST using Camomile and hook it up for more commercial or recording oriented projects.

I had no problems including externals, at least the ones that I've tried. I was thinking of hacking some wrapper scripts to do some of the chores associated with them, such as modifying the jucer stuff, automatically.

I haven't played with this yet and I have essentially no experience with jucer but from doing diffs on the jucer files it seems somewhat straightforward on paper. If I can get this to reliably work, would you be interested in it? It won't solve dependency problems for some more elaborate externals but it might help newbies somewhat and offer some convenience for other users.

Lastly, I'm a composer by background but I've always been writing software, with my day-job being in software development. I'm unfamiliar with the code bases but I would be really interested to contribute in some of these projects. Is there interest or possibility for outsiders to contribute?

Again, thanks a lot for your work and having it open to the world! It really does mean a lot.

@starchild Thank you! I'm pleased these projects are useful to you.

Yes, of course, anybody can contribute by creating issues, merge requests, or writing documentation on the GitHub repositories. You should have a look at this document. In general, I just try to avoid to do things that will complicate the maintenance of the projects because I've already difficulties to find time to work on them. So, it's often better to start a discussion on a subject before starting to develop, this way we could avoid conflicts, see if contributing directly to a project is suitable or if creating a side project would be more appropriate, etc.

BTW, I keep the affiliation with the CICM because I started these projects there and it was great, now I'm working at Ircam for 2 years, so perhaps I will put a double affiliation .

@Pierre-Guillot Yeah, maintenance is always a pain. I'm a bit busy at the moment but I'll open an issue about this. There are multiple things that can be done, including me maintaining a fork that includes popular externals. I guess we'll discuss

As for IRCAM, the work there has had a huge impact on me in general. I first listened to the music of Gérard Grisey when I was a young teenager studying harmony and counterpoint and it completely blew my mind. Then I got more into frequential composition, Open Music and so on. This was basically my gateway to computer music. For a long time I was saying that one day I'd want to work there but my French got rustier and rustier and life took me in different places

I haven't caught up with what IRCAM has been doing recently, unfortunately. I think the last thing that I've used was Orchidée which was great but I've stopped using it due to switching to using Linux boxes. I still spin up Open Music, even though my lisp code always ends up being a mess

Keep up the good work!

I published a new temporary version 1.0.8-beta4. This beta version should be stable (at least not less stable than the release 1.0.7) but I didn't manage to do all the features and fixes that I wanted to do for the version 1.0.8 yet. You can find the list of the fixes and improvements that are already done on the release section.

Your feedback would be much appreciated!

And here is a little demo of live patching in Reaper with Camomile and the object pd~:

@Pierre-Guillot Thanks Pierre -- all my plugins build and work well with this beta release. Glad you kept the JUCE dialogs for openpanel and savepanel.

Is there any documentation for the new image properties capabilities mentioned in issue #122 (size, anchor, level, etc)?

Thank you!
#122 is not implemented yet

@Pierre-Guillot
Oops, sorry, when I saw "enhancement" and "removed from to do in 1.0.7" I thought it was done. My bad.

Hello, I have some very basic questions about Camomile.

Following the documentation, I have successfully loaded AlmondOrgan into my DAW (Cakewalk by Bandlab). I copied Camomile.vst3 from the Camomile folder to the AlmondOrgan folder, changed the file's name to AlmondOrgan.vst3, and copied the AlmondOrgan folder from the Examples folder to C:/Users/Program Files/Common Files/VST3, and Cakewalk then found and loaded the patch. I also got MiniMock to work using the same process.

However, I cannot get a Pure Data patch other than the patches in the Examples folder to work. I have been following a YouTube series showing the development of a Pure Data synthesizer, and wanted to load that synthesizer into Cakewalk. I downloaded and unzipped the zip file (it is the final version, lesson_16.zip, on this website: http://lwmmusic.com/learning-lswpd-1.html), copied Camomile.vst3 from the Camomile folder to the lwm_fam2_synthesizer folder (which is what's inside the lesson_16 download), changed the file's name to lwm_fam2_synthesizer.vst3, and copied the lwm_fam2_synthesizer folder to C:/Users/Program Files/Common Files/VST3. When I then try to use the synthesizer in Cakewalk, the GUI is replaced with a "Plugin Not Valid" message, and the console warns that Camomile can't find configuration files. I also tried the same process except renaming the Camomile.vst3 file as modules.vst3 (corresponding to modules.pd, the name of the synthesizer file), with the same erroneous result. I am unable to determine how much, if any, of the "How to create new plugins" page of the documentation applies here. It's just a bit too much technicality without context for me to understand what parts of it are required just to get going and what parts are customization options.

My first question is, are patches created using Camomile itself, or are they created independently using Pure Data, with Camomile being applied to them only after they are already created? In other words, do I need to copy the contents of the downloaded synthesizer files and paste them into new Camomile patches?

My second question is, what other steps are required to load the downloaded synthesizer files into Cakewalk using Camomile?

I found this https://github.com/pierreguillot/Camomile/discussions/233#discussioncomment-344215 on github and managed to make the Camomile Playground work on windows.
I couldnt find the information need for this on the forum before so i'll share it here
I did some test and to try midi in and ouput and some externals and everything worked, that's so cool!

Hi,

[New beta version 1.0.8-beta10

I published a new temporary version 1.0.8-beta10. This beta version should be stable but again, I didn't manage to do all the features and fixes that I wanted to do for the version 1.0.8 yet.

Your feedback would be much appreciated!