System crashing with FL

[Debutante]

Here's what I get when I open one particular flp:

1st - Stack Overflow
2nd - System Error. Code: 1400. Invalid Window Handle


Any ideas? CHEERS!

[speccyteccy]

Using 3rd party VSTs? If so, try pointing your VST directory somewhere else then loading the flp - it should moan that it can find them, but the flp should still load. If it does, point your VST directory back, but remove all the VSTs except one in use in the flp, then try reloading it. Replace the VSTs back into the directory one by one until the problem reccurs.

[grymmjack]

Here's what I get when I open one particular flp:

1st - Stack Overflow
2nd - System Error. Code: 1400. Invalid Window Handle


Any ideas? CHEERS!

Send us, or imageline via looptalk the FLP.

[Debutante]

Thanks for the responses guys. The flp loads fine, and I can even hit the play button and have the sequence running. The 2 error messages show up when I try to do anything else, like hit F12 or try to tweak a plugin. The problem is not opening the flp, it's a crash that occurs once the flp is open.

I know the stack overflow problem is memory related, and at 512 mb, I'm not too surprised I could be taxing it too heaviily. It's the second error I'd like to find out about. I'll first try to find the plugin that might be causing it as suggested. I have a couple of betas I'm a little suspicious of if that's the case. If I can't then I'll have to go straight to Looptalk. Thanks again as always guys!

[Debutante]

SWEEET! I found and isolated the plugin that was causing the crash. It wasn't one of my betas as I had suspected. In fact it was GVST's chorus, which I like so much.

Whenever I opened the flp, as usual FL loads with the plugin GUIs open, so the first thing I normally do is hit F12, and that's when it would crash. So I decided to close the plugin GUIs one at a time, and when I got to GVST's chorus the computer locked again. To isolate it, I tried it a couple of times and it worked repeatedly. So I then changed the name of the plugin, and when FL couldn't find it, the flp opened up with no problems at all.

I ran Tobybears VST Spy to see if maybe plugin ID's were being shared, just as a long shot, but found that's not the case. What else could it be? Anyway, I'm glad I was able to find the source of the problem myself. It's one for the books should it happen again. I'll just have to get rid of that one plugin and send the author a note. Thank you kindly for that plugin suggestion speccyteccy.

[grymmjack]

SWEEET! I found and isolated the plugin that was causing the crash. It wasn't one of my betas as I had suspected. In fact it was GVST's chorus, which I like so much.

Whenever I opened the flp, as usual FL loads with the plugin GUIs open, so the first thing I normally do is hit F12, and that's when it would crash. So I decided to close the plugin GUIs one at a time, and when I got to GVST's chorus the computer locked again. To isolate it, I tried it a couple of times and it worked repeatedly. So I then changed the name of the plugin, and when FL couldn't find it, the flp opened up with no problems at all.

I ran Tobybears VST Spy to see if maybe plugin ID's were being shared, just as a long shot, but found that's not the case. What else could it be? Anyway, I'm glad I was able to find the source of the problem myself. It's one for the books should it happen again. I'll just have to get rid of that one plugin and send the author a note. Thank you kindly for that plugin suggestion speccyteccy.

Great man! Good to see you found the culprit and glad to see you take matters into your own hands without pointing fingers or whining

[The Chase]

Here's what I get when I open one particular flp:

1st - Stack Overflow
2nd - System Error. Code: 1400. Invalid Window Handle


Any ideas? CHEERS!

oh shit!!!!!!!!!!!!

that's what i got, and all i got form support was either silence or "wtf"

Fortunately the latest version fixed my issue.

here's my thread about it:
http://www.kvraudio.com/forum/viewtopic ... highlight=

[The Chase]

oops too late