administrators

Great news. Does it work in Logic (or whatever DAW was also not working correctly)?

Are you sure you installed IPP correctly? The linker error complains that the IPP library files can't be found at the usual location. Check what's at:

opt/intel/ipp/lib/

Well the reason behind this step is probably that the VST3 technology has a better API if you look under the hood and actually it‘s already 10 years old so it‘s not all of a sudden.

However the main problem remains that there is still a considerable amount of DAWs that don‘t support VST3 so Steinberg is effectively pushing people away from possible customers which is a rather bold move for somebody that is offering a platform API.

Yeah, you‘re in illegal territory until I manage to add VST3 support, but even then Ableton will not support it. However I have a license for VST2 (I got it September 28th, LOL), so if this gets a real legal problem, I can act as plugin distributer for you until we back into clear area.

This is one of the major fuckups in the history of software licensing.

Yes this was removed but like two years ago

how does the buffer determine which noteOn/noteOff belongs to which event ID.

Well, FIFO means First in First out, so the earlier note would automatically get the note off. The other model would be a LIFO (Last in, first out" stack), but I think the result would be super weird.

They draw in midi for basic drum beats, then drop a midi note right on top of another note to create their flams. Every. Single. One.

It will probably come down to a preprocessor definition that customizes this behaviour on a per project basis. This problem is more apparent on drum based projects, because you don't need your super VA style Saw synth to flam

Yes, but the problem that you can't apply filters on a Container remains since I've removed the monophonic filter.

@Dominik-Mayer said in Missing Widgets?:

I think the easiest approach towards a value-setter could be to add a No-Skin option to the standard Slider UIComponent, that would only display its value.

Good idea, this would also remove the necessity for an empty image for our empty filmstrip hack (just set the textColour property to something transparent).

I think the easiest approach towards a value-setter could be to add a No-Skin option to the standard Slider UIComponent, that would only display its value.

This value could then be dragged up/down and restricted towards a range with its min/max/stepsize properties. Adding additional up&down buttons should be pretty easy then.

An additional prefix-property in addition to suffix could also make it possible to change 1/8, 1/16 values with dragging. Plus, when prefix and/or suffix could be restricted to only show in ValuePopups (LFOSpeed 1.45 Hz), this could make up for some pretty compact and minimal UI Elements.

best,d

The synthesiser class in JUCE is only partly relevant, I think the culprit is the way I am generating event IDs from the MIDI input. The problem is that there is no "correct" solution, as soon as MIDI notes with the same channel and note number overlap, things get into undefined territory.

Currently I have only a single slot per note number, the first way would be to change that to a FIFO queue, but there are performance implications that have to be evaluated against the edge case of people not using their piano roll correctly