Page 1 of 1

Exception loading Editor

Posted: Sun Feb 07, 2016 10:18 am
by a.wedel@freenet.de
Hello,
I am trying to test DSP Trigger 1.6.0.9 but can't get it to work.
I tried with Nuendo 5, Reaper, VST-Host, 32 bit and 64 bit.
When I try to open the Editor GUI it appears empty.
Just some black empty panels on the top, rest black.
VST-Host loads the plugin -> no error, when I try to open the GUI,
the plugin throws an exception (not visible, I see it in the log).

Here you see the editor and the log:
Image

System: Windows 7 ultimate 64bit,
Komplete Audio USB with actual ASIO drivers

DSP Trigger free works.

Do you have any idea?

Re: Exception loading Editor

Posted: Sun Feb 07, 2016 10:20 am
by Rob
.... I'll take a look tonight.

Re: Exception loading Editor

Posted: Sun Feb 07, 2016 11:01 am
by Rob
So I basically recompiled with my updated graphics libraries--there's a good chance this will take care of the issue. Give this a shot and let me know how it goes.

http://www.audiofront.net/DSP_TRIGGER_PC.1.6.0.10.zip

Regards,
Rob

Re: Exception loading Editor

Posted: Mon Feb 08, 2016 6:18 am
by a.wedel@freenet.de
Wow, that's what I call service! I'll give it a try and send you feedback? Thank you a lot Rob.

Re: Exception loading Editor

Posted: Tue Feb 09, 2016 8:04 pm
by a.wedel@freenet.de
Hello Rob,

unfortunately it didn't work.
The same exception as in my recent post.

Best regards,
Andreas

Re: Exception loading Editor

Posted: Tue Feb 16, 2016 12:12 am
by Rob
I just noticed that your screenshot with VSTHost is loading the 32bit version. Perhaps you are experiencing bit bridge issues.

Re: Exception loading Editor

Posted: Tue Feb 16, 2016 2:34 am
by Rob
I guess I should mention that the 64bit version of the plugin is likely stored in.

C:\Program Files (x86)\DSP Trigger\dspTrigger64.dll

Re: Exception loading Editor

Posted: Mon Feb 22, 2016 6:48 pm
by a.wedel@freenet.de
Hello Rob,

sorry for my late reply.
I tried both versions, of course with the corresponding Hosts (Reaper, Nuendo, VST-Host).
Unfortunately the same error.
One remark to your last version: After the exception the log shows some more information
about some parameters, so I guess the code continues after the exception.
I'll try to send you a new screenshot.

Best regards,
Andreas