Exported VST causing Access Violations

[Christoph Hart]

@Adam_G VS Menu -> Project -> Properties (last item) -> Debugging -> Command -> Browse.

[Adam_G]

@Christoph-Hart thank you! on windows vsts dont compile directly to the vst folder. do i need to set that for my working directory ? im using Reaper and the vst isnt showing up when i start debugging

[Adam_G]

anybody out there familiar with debugging in visual studio?

[d.healey]

This should get you started (it's what I used)

[Adam_G]

@d-healey thank you very much

[Adam_G]

i think i managed to make it work thanks to everyones help. no crash in reaper but i replicated it in FL studio. is this what im after?

Exception thrown at 0x00007FFD4CA49F35 (myVST.vst3) in FL64.exe: 0xC0000005: Access violation reading location 0xFFFFFFFFFFFFFFFF.

[Christoph Hart]

@Adam_G No it seems that you're still using the release build in FL Studio - it should break in MSVS with the exact line that causes the crash. Make sure you load the correct plugin version (it should have a Debug postfix).

[Adam_G]

@Christoph-Hart hmm i compiled the vst with the debug version of hise standalone. i must be missing a step, ill try again

[Christoph Hart]

@Adam_G no you must compile the plugin as debug build from within VS. Open the solution you‘ve creates after exporting from HISE, then switch the configuration to Debug and build.

[Adam_G]

@Christoph-Hart i just realized :beaming_face_with_smiling_eyes: thank you Christoph

[Adam_G]

@Christoph-Hart is this what im after?

[Christoph Hart]

@Adam_G nope jasserts are fine, keep on clicking on continue until you hit a access violation ;)

[Adam_G]

@Christoph-Hart took forever to get a crash for some reason haha, this?

[Christoph Hart]

@Adam_G yes that‘s the spot, now show me the callstack (bottom right panel).

[Adam_G]

@Christoph-Hart this?

[Christoph Hart]

@Adam_G nope, callstack. first tab on the right :)

[Adam_G]

@Christoph-Hart sorry found it

[Adam_G]

was that the right panel? @Christoph-Hart

[Christoph Hart]

@Adam_G Yeah, but I can't spot anything wrong in those locations. It appears to crash because you're trying to load a sample map in a scriptnode audio file slot, so maybe double check that you're not passing an invalid sample map ID in there.

Also, is it crashing when you debug the standalone version?

[Adam_G]

@Christoph-Hart that may be the cause as i have a scriptfx granulator that loads the same sample map as the sampler. i will test the standalone today but i havent been able to make it crash at all afaik