@elden Thank you sir! Now I understand, so you can drive the synth by using a note loop (in your video quite short C3) and Ewolverine is then mapped to CC for this synth.

I'll try it soon.
Cheers

@elden Again me, asking for either a sound demo or even better recording a session (screengrab via OBS for example). Your user doesn't exist anymore on soundcloud. Would love to see this patch in action!

@timothyschoen said:

Thanks! You can set up your own keyboard shortcuts in the settings menu, that might help!

Will do!

Unfortunately there's no way to sync to DAW tempo currently, but I'm planning to add that very soon, as it's obviously needed.

Presets are also broken on the releases, it should be fixed if you build from the latest source.

In a perfect universe, loading the plugin would load also the last patch used. So that you can save your session in your DAW and when reopening you have PlugData ready to go.

Use [adc~] and [dac~] for audio input/output. You can use things like [dac~ 3] to output on channel 3 if you need to use more channels.

Of course! Make sense!

Automation is received with [receive param1], where 1 is to be replaced with the parameter number.

Thanks!

Nice work! Here's some questions. When you have time, no rush.

The first thing I did was to use it inside Bitwig on Ubuntu 20.04. Both Standalone and VST are working. I tried to Ctrl+1 to create object, but it's "n" for new, ok no problem - but my brain refuse to switch

Tested midi in (the "led" is flashing), neat! Here's one question, how to sync to a DAW (start / stop / BPM)?

I tested the FX~ VST with a very simple patch:
[inlet~]
|
[outlet~]
Doesn't work (no input sound)

All the best!

@jameslo Thank you so much!! I will test your solution soon. Overkill? I don't think so, well implemented (and vanilla) for the win. Cheers~

Really basic implementation, just as a POC. I will test soon.

@jameslo In my mind, adc~ 1 is the master metronome (for example, an old drum machine that you cannot offset the clock). adc~ 2 is another metronome but this one you can offset the clock (ie: ableton link~, midi clock with offset).

So if adc~ 2 metronome click is before adc~ 1, I will get a huge offset in ms (ie 455), but if adc~ 2 click is just after adc~ 1 click (by ear), then I will know but how much I need to adjust the offset (ie: 20ms). That's the theory.

I need to have a look at jacktrip / quacktrip, but without fiber, the latency is simply too high ~50ms. I know that some people said that with 5G it would be possible, well... time will tell. For now, I am using ninjam (not realtime, offset).

Hi PD community!

I have this "simple" idea (in quote yes) that it would be "easy" (in quote also) to compare 2 metronome audio signal (similar but not identical) in pd: 1 source ADC1 and another metronome on ADC2. I need to get the latency between the 2, or the syncness (if this term exist in english) between source 1 and source 2. So maybe they are 20ms apart (+ or - would be fantastic but would be happy with just + for now).

It's not for testing my soundcard round-trip latency (for that I am using the excellent patch from Katja). I want to jam with someone and we are using ableton link pd external - we can manage the offset by ear, but would like to have the exact MS.

Found this python library, but it works with a specific sound signal, I have in mind a more relax metronome signal (ie coming from a midi drum machine (snare, hihat x3)).

I have a feeling that a patch like that is already coded...
Thanks!

If you have the money: https://blokas.io/pisound/

Neat product works well with pd!

@zepadovani the forum is always trying to embed video from youtube, I modified the link... not the best but at least the credit is there. nice contribution! thank you!!

I recall using it on linux:
https://danieliglesia.com/mobmuplat/MobMuPlatDistribution_1.82iOS_0.34Android.zip

In a terminal:
java -jar ~/Downloads/MobMuPlatDistribution_1.82iOS_0.34Android/Editor/CrossPlatformJava/MobMuPlatEditor.jar