The easiest is probably to use https://github.com/x42/jack_midi_clock to create MIDI realtime messages based on the jack transport.

@donnerbono I tried this first one using heavylib abstractions and your expr~ line.

Pretty clean and easy to patch. And you should be able to build it for OWL and Daisy and such.

@oid Cool, I'll see if I can work that in and see if that helps with the latch.

Theoretically greater/smaller should indeed work better, so will try soon!

@bocanegra said:

Besides float, bool and trig, are there any other assignable types for DPF parameters? (is a drop down list selection possible?)

I have implemented enumerated parameters via the metadata json in the latest release (v0.9.0)
Here is an example plugin that uses it: https://github.com/Wasted-Audio/wstd-dlay/blob/main/wstd_dlay.json#L16

This results in a 0 to n-1 integer being output by the selector, but on the plugin/host side you can get a dropdown with the configured strings instead.

@ytt Midi is available in the integration with plugdata.

Try the latest nightly builds to test the upcoming 0.8.0 release!

@oid Nice, this inspired me to try and scale this up to many additional "layers" of parameters (8 right now).

The latching feature is really something I wanted to implement soon as well, so this came in quite handy.

I'm also using Daisy btw. testing on the Field. What I'm currently doing is scaling the 0-1 float to 512 integers instead. Larger might be possible, but I found that it's harder to hit the latching value as precision of the received value goes down and you may over-shoot.

Other than that this setup works reasonably well. I've tweaked it a little bit so that each latching parameter can be represented with a single abstraction taking an id to initialize.

@ddw_music Yup, exactly!

So they still use Macs, but pirate all the software for it? Kind of odd.

But yeah the "max4live except everywhere" is the narrative that I've been telling people as well.
The advantage over RNBO is that we don't need to use some online compiler either. The toolchain we use with Plugdata is all integrated!

So you can build a VST or program a microcontroller straight from the DAW

Oh I'm sorry. I am referring to https://github.com/Wasted-Audio/hvcc which we have integrated in PlugData:

https://plugdata.org/images/hvcc.png

From there you can then output a plugin binary of your patch (VST2/VST3/LV2/CLAP).

@ddw_music Have you tried the DPF plugin export using Heavy inside of PlugData yet?

I've implemented DAW synchronization using midi messages start/continue/stop/reset and 24 ppqn clockticks (that should get scheduled quite precisely).

However in current development is a simple [r _hv_dpf_bpm] receiver for the current BPM value, that I am now using for synchronized delay effects.

Any ideas to improve DAW integration here are appreciated

You should probably take a look at https://github.com/timothyschoen/PlugData/
which is a distro of Pd that can run as a plugin inside the DAW (and comes with a unique editor/interface).