Final product problems

[Sketch]

Hi everyone hope you are having a great day so i recently have been working on my new vst and yesterday i finally finished and exported it everything was great but when i load it into my DAW it keeps loading until the DAW doesn't respond has anyone faced a similar problem your help is apriciated thanks

[TNTHM]

@Sketch Do you mean that the DAW is trying to validate or authenticate your plugin and gets stuck doing that?

Or that when you are in your DAW and you open your plugin it gets stuck trying to open it up?

What DAW? Mac or PC? What operating system?

[Sketch]

@TNTHM when im in your DAW and you open your plugin it gets stuck trying to open it. Im using windows the DAW is Fl studio

[TNTHM]

@Sketch That makes sense. Have you tried compiling and running one of the sample plugins that @Christoph-Hart provided in the Hise tutorial?

It can be found here:

https://github.com/christophhart/hise_tutorial

[ustk]

@Sketch Begin with a very simple plugin, with nothing but a sine generator and an empty interface (ok, with a gain knob if you want )

[Dan Korneff]

You can start by making a simple project as others have said, just to verify the process.
If that works, then the next step is to debug your plugin.

[Sketch]

@ustk thanks for the suggestion i tried it and it works perfecly i also tried re exporting the vst and i get the same problem any more suggestion?

[ustk]

@Sketch It means the issue comes from your instrument, so you have no choice but to debug it I'm afraid
Begin to remove things and test step by step…

[Sketch]

@ustk thanks for the help so i went back into my vst and checked it and found the problem. So i used miltiple images for multiple presets and when i export without loading the pictures into the pool they dont show up into exported version and everything else works fine and when i load them to the pool the vst won't load is there a way to counter at that problem ??

[Lindon]

@Sketch every image that you want to use in your vst MUST be attached (showing) for at least one widget... so if you want to use various (say) slider widgets then you will need hidden sliders each one with one of your desired image strips.

[ustk]

@Lindon What if you just load images into pool one by one? Engine.loadImageIntoPool( string id)

[d.healey]

@ustk Nope

[iamlamprey]

every image that you want to use in your vst MUST be attached (showing) for at least one widget... so if you want to use various (say) slider widgets then you will need hidden sliders each one with one of your desired image strips.

Wait is this still a thing? I just moved my images from the respective expansions into the project folder and I'm getting Missing errors...

What if you just load images into pool one by one? Engine.loadImageIntoPool( string id)

I really think brute-forcing like this should be possible... I don't want to have to make 16 extra invisible panels just to have my jpgs included in the binary...

Edit: Yep just tested and it resolved my mystery errors... still think making a bunch of panels is an ugly way around it but