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?
Camomile : An audio plugin that loads Pure Data patches
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.
Another video for Christmas
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.
- 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.
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:
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!
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)?
#122 is not implemented yet