First release

[atom]

mac and windows are up on the page. looks like candy, don't puke on your keyboard from using it:

[Tijs]

You should drop a mail to Manfred Fricke. I think he would highly appreciate the fact that you build this ctrlrs for his synth & drumboxes.

[skweeegor]

Wow that was fast - will try it out soon.

Thanks

[skweeegor]

Hmm, strange - Ableton doesn't see it when I scan for plug-ins. Tried renaming it with no luck.

Tested the standalone and everything works great!

[atom]

you are right, there is something wrong, i'm fixing it right now.

[skweeegor]

Got a chance to try the VST...so it works but something strange is happening. When I make a midi clip to trigger the drum machine, after I draw enough notes, it starts making a glitchy clicking sound similar to what would happen if I tried to trigger two toms at the same time (since only one at a time can sound) or playing a project with too high CPU usage. I tried altering note lengths and that helped a bit, but once there's enough notes drawn in the clip it starts doing it even with 1/128th notes.

When I take the exact same clip and trigger the drum machine using a regular midi track (no ctrlr) it works perfectly no matter the note length as long as toms and such don't overlap.

[atom]

Are you passing midi daw->ctrlr->daw or daw->ctrlr->midi hardware ?

[skweeegor]

daw->ctrlr>mfb 503

The MFB is at the end of a long midi thru chain (4 devices), but as I said it works fine with no ctrlr. Could the ctrlr be adding enough latency to mess things up?

[atom]

Yes, this is the problem and it's something i wrote about.

there is no way to sync midi output in a VST/AU/RTAS plugin with the hosts audio/midi output. There is no way to assign time information to midi events that go directly to midi devices, this is just not possible. In terms of controllers it's usually fine cause you just edit some params and leave them at that. But with notes it has to be PERFECT timing, sample accurate, and this can be achieved only if Ctrlr sends out MIDI back to HOST (VST Output).

I have an idea that i'll implement. A small routing option. It will let you choose where to send each type of midi messages. The best way would be

1) Midi notes to host (perfect time sync)
2) Midi CCs to host (perfect automation, but only for synths that support CC/RPN/NRPN/AFT)
3) Midi SysEx direct to device, cause DAWs don't forward those messages

granted this will only work where the MIDI driver has the ability to be opened/used by more then one application. But maybe it will help.

[skweeegor]

Hmm interesting. Both midi interfaces I've used so far only allow use in one application at a time - I assumed this was a limitation of all midi interfaces. Are there any you know of that can be used in more than one app at a time?

[atom]

it's a matter of the driver not the hardware, midi yoke for example can be opened in many apps. on mac it's not a problem.