Hello,
many plug-ins fail VST3 validation or crash/show weird control values. in latest DP (win & mac), while these are working in many/all other DAWs. When debugging my own plug-ins, it appears, that the vst3 implementation of the host is buggy. I have also sent this to motu a few days ago:
as an echo digital performer reports back ui vst3 parameter changes of int/enum types in nonnormalized Format - instead of normalized (0. - 1.) format (in process method / inputParameterChanges). Could you please confirm/fix this ? DP is the only DAW behaving like this, VST3 standard says, the host has to report normalized values. Seems that this affects parameters where the stepcount is set > 1 in ParameterInfo structure. Things start working when the step count is 0, but this is only a workaround.
Maybe somebody (developer ?) could confirm this.
VST3 implementation bugs
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
-
corbo-billy
- Posts: 1043
- Joined: Fri Nov 11, 2005 1:33 am
- Primary DAW OS: MacOS
- Location: France
Re: VST3 implementation bugs
I'm just an user; same finding for the VST 3 format on an Apple computer _
Imac M4 24" under Sequoia 15.3.1 & Kontakt 8.2. _ Fireface800 X 2 _ FilterBank2 Sherman & Gibson Explorer Pro _ Virus C Desktop _ Adrenalinn III & Voyager Moog _ SpeakerPhone 2 _ PolyEvolver Keyboard _ Tempest _ D.P. 11.34 _