VST plugins with MIDI produce hundreds of controls

Screen Shot 2018-05-09 at 5.45.30 PM (2).png (347.77 KiB) Viewed 2727 times

Arturia PreAmps / 1973 Pre V1.0.0.265 applied as VST in mixer

this plugin has options for MIDI control

in R15b2 inspector panel, the first 15 controls match the GUI of the plugin, then there are hundreds of MIDI CC Helper controls created. this caused app to. beachball looking like it locked up but was actually creating all the controls. this appeared the first time I appleid the filter with its GUI open. I clicked off the plugin, onto built in dynamiccs and the inspector panel went blank. I have not been able to get the controls to show up now in the inspector. I'd suggest you get at least a Demo copy of these filters or others that are capable of MIDI control and see what happens.

UPDATE : all the extra controls show up. on first application of the filter. one control for each CC 0-127 X 16 MIDI channels is 2048 controls ! no wonder it takes to long, generates beachball... but hey it doesn't crash please fix ! I have screen shot if you want it.

10.13.4

S

This bug remains in R15b3 public release, . a more specific way to repro now

apply Arturia 1973-Pre or other effect from that series with option for MIDI automation
filter UI opens, but inspector is empty
double click native dynamics
beachball
native dynamics opens up and _now_ the inspector is filled with the 2048 extra MIDI controls for the 1973 Pre

can't attach digs log as its 1.1m, attachment limit is 1m. I'll send PM with dropbox link

S

bug still present in B5

Bug remains in public beta 6

It's not a bug and it's not DR. It's how this plugin behaves; all the MIDI CCs are used for automation control of it's parameters.

it is a bug, or bad design which didn't anticipate the problem.

first, all those MIDI CC params are normally driven by an EXTERNAL midi control surface. as they are, they aren't connected to anything. its only if the user sets up the plugin within the plugin UI to listen to an external controller and maps the controllers on the external hardware back to controls in the plugin that they do anything. the plugin itself has maybe 20 controls or so, plus 2048 MIDI CC controls. One would never actually keyframe the MIDI controls. you would key frame the actual controls in the plugin that do something even if you did it via external controller.

this is of course assuming you even have a suitable external controller set up. if you don't have an external controller, the MIDI CC's are totally useless and a resource hog.

second is that creating all those useless controls beachballs the app for a solid 10+ secs or more. R doesn't crash which is good, but its wasting a huge amount of space for stuff thats not going to be used.

so not generating and displaying the MIDI CC controls would be the best behavior since they are basically useless for all users. I mean if you have a need and use, please explain.

I don’t think that Fairlight will have all DAW features but If I were the BMD Boss I would buy Bitwig or Image Line company to make Resolve the all in one solution for audio, video, 3d special fx and music production.

regards

it is a bug, or bad design which didn't anticipate the problem.

first, all those MIDI CC params are normally driven by an EXTERNAL midi control surface. as they are, they aren't connected to anything. its only if the user sets up the plugin within the plugin UI to listen to an external controller and maps the controllers on the external hardware back to controls in the plugin that they do anything. the plugin itself has maybe 20 controls or so, plus 2048 MIDI CC controls. One would never actually keyframe the MIDI controls....

...so not generating and displaying the MIDI CC controls would be the best behavior since they are basically useless for all users. I mean if you have a need and use, please explain.

Steve, I'm attempting to wrap my head around the erroneous, sweeping generalization above, which presupposes that DaVinci Resolve's included potential for MIDI mapping is useless -- and worse -- that it's useless to all users!?

What kind of anti-MIDI CC (Control-Change) campaign are you *on*, Boss? Why disparage the feature-set, despite its value to music video producers, soundtrack designers, and the like? Come on, Man, don't screw us over just because its half-baked, yet memory resource intensive (so you say) MIDI mapping implementation stinks to no end.

Sent from my P00I using Tapatalk

sorry, but 2048 MIDI CC params for a SINGLE filter is ok ?

it IS a resource hog AND it does bloat the project size. the app beachballs on a 24core machine for a good 10+ secs creating all the resources for those controls that are basically useless, or put another way, simply won't ever be used in anyone's wildest imagination.

the particular set of filters I have found this bug with, there are about 20 actual controls for the filter. you can map an external controller to each filter control. that uses the controls themselves for key framing. 20 keyframed params is reasonable, 2048 is not times every instance of the filter. You can still use a MIDI controller to keyframe filter controls as much as you want via mapping, and without generating a large amount of overhead to do so.

if you are working on a music video, the track is already mixed and locked. I don't think you will find that Resolve is going down the path of a full DAW designed for composing, its for mixing recorded tracks. Even a DAW creates MIDI tracks that you map to whatever.... which isn't 2048 seperate param tracks, its 1. What you are asking for is 2048 tracks, one per MIDI CC instead of one MIDI track that holds all the CC info.

In fact, these same filters in Logic produce ONLY keyframes for the normal controls and the only way you can MIDI control them is via mapping the controller to filter controls. So if its good enough for Logic and everyone is ok, well its more than good enough for resolve.

S

[#FriendlyRant]
Just because a piece of software's controls are poorly coded relative to resource intensity ought not give one license to deem the pertinent features, functions and benefits of said controls worthless and of no interest to any Resolve user. That's a nonsensical, fatalistically-contrived #sweepinggeneralization to the extent of utter silliness.

Such discrimination against us music/video producers and other users of MIDI Control Change paramaters afforded us by Blackmagic DaVinci Resolve EDIT and FAIRLIGHT pages is tantamount to decrying automatic transmissions -- or air conditiining in automobiles because such technologies "continually drain resources".

To think the detractor has not relented -- but doubled-down on the deplorable false notion that MIDI CC (Control Change) espevially in Resolve is both useless and is not at all utilized is presumptuous at best and way, way wrong, and strikes as inconsiderate. Such strident cries suggest the detractor is unwilling to even concede Blackmagic Design development team may very well need to hire coders who know how best MIDI ought to be implemented in software.

Contrariwise, SOFTUBE http://softube.com does a massively impressive job with their plug-ins architecture, making for an amazing multichannel plus multi-buss plugins solution for extensive, and awesome audio tweaking with their CONSOLE 1 Mk ii hardware/software dolution at just $499 USD -- it's a Solid State Logic 4000E channel strip emulator we use with DaVinci Resolve (while the setup instructions insist that users place an instance of that plug-in on every possible channel (even unused ones) and every possible buss (yes even unused busses) that the user will ever need -- including MAIN OUT Buss -- then saving that Project for use as a Template when instantiating/launching any future/new projects in the plugin's host -- i.e., the DAW (Digital Audio Workstation (e.g. DaVinci Resolve)/NLE.

The result? Smooth, seamless integration with DAWS and yes -- within Resolve's EDIT and FAIRLIGHT pages, with no annoying drag on the system whatsoever -- even with hordes of instances of that plugin operating across the multitude of channels and buses plus the MAIN output Buss -- combined!

Blackmagic Design's weakest link for RESOLVE might well be its coding method for the audio plug-ins architecture -- perhaps borrowed from the old company known as Fairlight. before Blackmagic Design acquired it?)

Relatively awkward if not incomplete MIDI mapping implementation, and being shockingly lacking in the realm of process(or) efficiency and user-friendliness in MIDI Mapping, MIDI CC setup and behavior is apparently somewhat of a sore-spot for some not using Console 1 Mk ii fir audio sweetening (live. or for EDIT page. FAIRLIGHT page mixing/mastering and Delivery page scenarios).

If the "detractor" has cited any true problems on the MIDI CC section of Resolve, Blackmagic Design would do well to address any quirkiness. or resource hog dynamics at the programming code level -- if for no other reason, than to keep at bay unlearned, wildly speculative hyperbole by some, who being inconsiderate of other users, have set out to twist Blackmagic Design's will into killing off otherwise-fantastic MIDI Auto Mapping and CC (Control Change) potential that simply lies in wait of further refinement, under Resolve's expansive hood.[#FriendlyRant /OFF]

ResolveStudio 14.3...014 | MiniMonitor | DTV 10.9.7 | Win8.1 x64 | ROG G751JL, 2.8GHz Intel i7HQ, 24GB DDR4, 1TB HD, 500GB EVO 850, 2GB GTX965M | Mackie MCU Pro | Softube Console 1 Mkii | Shuttle Pro 2

Constructive posts for either improvement or potential bugs are allowed however, if any posts are going to be directed towards other users that are inflammatory, we will act accordingly with the offenders.