VSTi Export Best Practices: Unsuccessfully Parsing Exported VSTi

[unityconstruct]

Looking for VSTi Export Best Practices

• on latest Ctrlr, can export dll, but Memory spikes to max immediately when DAW scans the dll
• suspecting something along the lines of:
  • my mod count is obnoxious ( but saw a post from Atom alluding that this happens frequently so shouldn't be a problem in itself)
  • init code going rogue (though not sure if lua is even involved in scanning the DLL)
  • lua code in general causing some issue during scanning
• opened/exported/used an XStation DLL panel without issue, so seems to be something specific with my panel

Memory spike steps

• In DAW: export VSTi instance

  • open CtrlrX VST in DAW
  • open panelz and use normally without issue
  • export instance -> dll

• In DAW: scan created DLL

  • scan plugin directory
  • finds new DLL and starts scan
  • memory immediately gets consumed to system MAX of 16G
  • CPU not really throttled.

• Panel Details

  • upwards of 1000 params
  • modulatorVstNameFormat = %n

• had a hard time finding anything on Ctrlr.org but nearly certain I came across threads discussing some practices around prepare a panel for export.

• the ones I'm finding are more centered around obfuscation of the CtrlrUI(hiding menu, right-click access, authorization,restriction, etc)

• I see Menu > Edit > Preferences

  • use the Editor Wrapper for VST Plugins ( is currently Enabled )
  • Max exported VST params ( currently 64, but will need to drastically increase to ~1000)

• think I saw comments around explicitly setting Export param to VST host = FALSE for everything, save
  • then go back and explicitly set ONLY the mods to be exposed to VST host
    

[unityconstruct]

This has been resolved. Root cause is vstIndex values being insanely high. Assuming that the host allocates resources for empty vstIndex ids, and in this case, it was allocating for 333335160 controllers before getting to the actual panel controls.

• Reset indices, starting at 1 and host able to quickly scan my panels. The smaller one has ~400 and my larger one has about 1400.
• There's a separate issue that causes crashes when opening the panel in the DAW host. When exporting, ope the panel in an editor and set panelIsDirty=1 and save, THEN export.

#676 (reply in thread)

Been wondering about this for a while, but my VSTIndex values are retarded big.. I noticed yours started at 1 a few days ago. So just created a NEW panel and added one mod and its VSTIndex is 333335160, so going to set mine back starting at 1. I suspect when VSTHost is parsing the panel, its mapping these ids and perhaps it has to map from 1-whatever my first index is... 333+ million might explain my memory issue.