Select "Remove a plugin that crashes when the file is opened". You would use the 2nd option "Fix an FL Studio file that can't be loaded anymore" Then follow the prompt. Just keep your eye on the cpu meter, as you go. Try even deleting channels, patterns and clips to see if anything else is causing the problem. Try removing all 3rd party plugins and see what happens. My advice is to go through your project with a fine-tooth comb. Did you save the project with dBlue Glitch added? If not, there is really no way it could be the cause. It can't change anything in your project if it's not there. Go here for the latest version of dBlue Glitch Īs LT says, removing a plugin that's causing you problems will fix the problem.
#Dblue glitch resets download
Where did you download dBlue Glitch? You should always go to the author's page to be sure you are getting the latest stable version (and not some beta that may have bugs. But that would be the case with any plugin.
That would only happen if I added I it to an already very cpu heavy project. It increases if there's more going on, but it never maxes out my cpu. When it's playing it goes up by as little as another 1%. When I add it to a project, my cpu goes up by 1%. I have been using every version of DBlue Glitch in every version of FL (including betas) since 2006 and have never had any problems with it.
0 kommentar(er)
