

I can't offer much help other than a possible clue there. Good you figured out the issue but whooooooooooooooa holy shit dude damn.Īs for the Shreddage thing - maybe that could've been an issue in the registry? I've heard that's where Kontakt keeps its data on whether your product is locked in demo mode or unlocked in paid mode. The bigger and more stuff you have attached to it, the more complications it has room to accrue and still create issues like this - or such is my experience. It makes me think of Serial Experiments Lain's flooded bedroom, or a guy so loaded up steroids that he's about to explode. That's a disgusting level of computer-tech porn that probably wouldn't be standard for another 15 years at least. In principle, I don't really agree with that. So it shouldn't be the computers hardware causing this. 5 monitors, 20TB of space, 32 gigs of ram, and i7 processor. Keep testing it and retesting it to see if you can isolate the variables that cause it, and then you'll be able to Google it from there or take it to Image Line's support team. I've never had this happen anywhere else and the only thing to say about it is "well, these things just don't like each other." Sometimes I get a complete video after restarting, sometimes I just get a giant. This laptop I'm on right now has a weird problem where if I'm cutting videos with Windows Movie Maker, if there's a video with a certain codec in it (and I haven't been able to determine which one), even if it allows me to import it in, cut it and start saving it, it will completely restart the computer RIGHT as it finishes. Sometimes programs, operating systems, computer components and so on come into a weird conflict and just don't work. The option for the latter is just to restart FL Studio and try again, the former requires isolating that it's the VST or something more pinpoint (samples chosen, some option flipped on, etc.) to see what's causing it. It's either been a conflict with the VST itself (just something in the program, computer and VST all combined together causes it) or FL Studio being buggy. I don't have the version you have, but I've had FL Studio do this or something similar to this to me a few times in the past.
