Just want to see where im at..

[BWSounds]

@Dalart
I remember once having issues with the ipp, might look into that a bit more..
I had to have changed something, just need to figure out what it was.

Maybe its my project, I'll try to compile one from the HISE tutorial folder.

[Dalart]

@BWSounds said in Just want to see where im at..:

@Dalart
I remember once having issues with the ipp, might look into that a bit more..
I had to have changed something, just need to figure out what it was.

Maybe its my project, I'll try to compile one from the HISE tutorial folder.

Compiling a tutorial to test is a good way to start, it at least lets you see if you can actually compile a working plugin. If successful in that, then you can narrow down what's causing it in your custom project(s).

[Christoph Hart]

There‘s also a minimal project in extras/demo_project directly in the repo.

But the red folder is indeed a mistake, it requires my folder structure to work, I‘ll change it (I almost never compile the plugin version)

[BWSounds]

@Christoph-Hart
ahh ok, thank you.

[BWSounds]

ok peeps, im going crazy..
so ive compiles plugins in HISE since 2019 so I know the ends and outs, but this....

I cant compile a plugin on the standalone or plugin version..
(I can but it wont open)

Ive tries my plugin on multiple daws and same thing, the plugin wont open..

Could I have messed something up in Projuicer?

Everything works fine in HISE and it builds every time in visual studio 17 with no errors.

[Casey Kolb]

When you say it won't open, does the application crash? Does it open with just a blank interface? Does it not even load the app?

My first recommendation is to copy the project folder over to a new folder and trash your Binaries folder.

[BWSounds]

@Lunacy-Audio
it crashes before the interface pops up.

My first recommendation is to copy the project folder over to a new folder and trash your Binaries folder.

i'll try this

[d.healey]

Build a debug standalone version, open it from the command line, tell us what the command line says when it crashes.

You can also try using pluginval to see if it can shed any light on the issue - https://github.com/Tracktion/pluginval

[BWSounds]

Well guys.. After many test im still lost.
I can build and compile plugins off my older commits (July) but not the newer ones.

So my question is... with the latest commits can you export midi files on a compiled project?

Thats all I needed to update for... but if it still cant be done i'll be ok for now.

[Lindon]

@BWSounds well I've been here recently ---- the plugin would compile BUT reaper would tell me it wasnt valid and would reject it and pluginval would crash as soon as it tried to open the plugin.

Turns out there was something (heaven knows what) wrong with one of my samplemaps. I rebuilt them all and it works flawlessly... perhaps its that?

[BWSounds]

@Lindon
worth a try!

[d.healey]

Before rebuilding all your sample maps you could make a new plugin with a single sample and try that.

[BWSounds]

@d-healey
Yep it compiled and open!

@Lindon
so my next question is how do you rebuild samplemaps?

Do I add everything all over again?

[d.healey]

What does pluginval say when you give it a debug build?

[BWSounds]

@d-healey
it kept crashing while I tried to run a scan

[d.healey]

Does standalone run?

[DanH]

@Lindon Urgh sounding familiar! Did you try on any other DAW or just Reaper? My project works on every DAW and Standalone except Logic!

[BWSounds]

@d-healey
Hise does, yes.

[BWSounds]

@DanH
Had logic issues, I had to change my plugin code for it to work .

[d.healey]

@BWSounds said in Just want to see where im at..:

@d-healey
Hise does, yes.

I mean if you build your project as standalone do you get the same issue? If you do you can launch it from a terminal and (assuming it's a debug build) you might get some useful info when it crashes.