KVR Audio

rifftrax · Post by **rifftrax** » Sat Mar 19, 2016 4:39 am

I've tested like 4 different projects running a slew of totally different (albeit 64bit plugins) with the latest version of FL Studio on a brand spanking new Windows 7 X64 system (i7-6700 w/16gb of memory). After saving and exporting a mixdown each time... guess what?? I can no longer open any of the files. NONE OF THEM. Crashes every goddamn time.

Are you f**king kidding me? So that's it huh? I mean I literally am unable to use this DAW anymore. Stability seemed to peak back at version 9 which is a helluva shame cause you guys then ditched blocks (which was like, the only truly game-changing thing about FL in general) and decided to fancify all the gui elements (oooooh! neato gang! so shiny!) and generally make the thing... well. Poo.

FL is now poo. I'm sorry guys but christ in a handbag what is going on? I mean when I can't even re-open a project with more than 4 x64 plugins then maybe you focused all that lovely energy in the wrong direction. And why can't I load more than like 20 plugins total without hitting 100% CPU? On a i7-6700? I have a half a mind to bench test against my old Q6600 running FL9, which seemingly had no processor ceiling that I could ever reasonably hit.

What a bat-shit weird world we live in where software not only goes backwards but goes so bloody far that direction that it prevents you from using it at all. As a previous IT admin who builds all their own systems and writes a decent amount of embedded system code, I'm just a little heartbroken. I loved this damn DAW. F**king hurts man. I have to switch all the way over to Reaper I guess. I'll miss the hell outta the piano roll (ugh, it is painful just thinking of using a different piano roll honestly).

Not a happy day for me.

Regnas · Post by **Regnas** » Sat Mar 19, 2016 5:08 am

Bad stuff...
It happened with 32 or 64bit version of FL?

rifftrax · Post by **rifftrax** » Sat Mar 19, 2016 5:55 am

64bit version

tooneba · Post by **tooneba** » Sat Mar 19, 2016 8:24 am

ok, now lets move on to reaper

bungle · Post by **bungle** » Sat Mar 19, 2016 9:38 am

You should try running some of the rubbish they release in OSX format, literally the worst plugins ever released on Mac, plugin i used to enjoy using on windows on machines that weren't even a tenth as powerful as the Macs i have, resource hogs, and unstable as ****
This combined with everything else they are up to, definitely a company to avoid.

loungepanda · Post by **loungepanda** » Sat Mar 19, 2016 12:19 pm

brand spanking new Windows 7

That is the opposite of new.

Also, Image-Line got an official forum for support, you know.

chk071 · Post by **chk071** » Sat Mar 19, 2016 12:25 pm

loungepanda wrote:
brand spanking new Windows 7
That is the opposite of new.

Also, Image-Line got an official forum for support, you know.

But where would the fun be to just rant there, where nobody sees it?

murnau · Post by **murnau** » Sat Mar 19, 2016 12:29 pm

After saving and exporting a mixdown each time... guess what?? I can no longer open any of the files. NONE OF THEM. Crashes every goddamn time.

How st*p*d one can be to think that this is a bug of FL Studio in general? So you really believe that every of the countless users of FL Studio have that problem too?

User error: Contacting support is a better idea then turning to a clown here.

core · Post by **core** » Sat Mar 19, 2016 12:39 pm

FL Studio 12 is working just fine for tons of people, me included. Why don't you try IL support if you love FL Studio so much?

Daags · Post by **Daags** » Sat Mar 19, 2016 12:41 pm

OP has convinced me to avoid FL Studio like the plague.

murnau · Post by **murnau** » Sat Mar 19, 2016 12:49 pm

core wrote:FL Studio 12 is working just fine for tons of people, me included. Why don't you try IL support if you love FL Studio so much?

Working fine here too. Now that are shocking news for some.

ATN69 · Post by **ATN69** » Sat Mar 19, 2016 12:57 pm

Working okay here to. Win 7 - 64bit and i7 with 8Gb. Crashes some times but not more than any other software I use.

TheNickC · Post by **TheNickC** » Sat Mar 19, 2016 4:34 pm

Daags wrote:OP has convinced me to avoid FL Studio like the plague.

Yep. The mac betas have issues too, definitely a company to avoid

robotmonkey · Post by **robotmonkey** » Sat Mar 19, 2016 6:41 pm

Even though FL Studio 12 has been working here quite ok it generally tends to be on the more buggy side of DAWs.

rifftrax · Post by **rifftrax** » Sat Mar 19, 2016 11:56 pm

Well, this is a forum. People come to complain about things they see as issues so it shouldn't be a huge surprise that I have done just that. "Oh but you should go to FL's forum and get help there."

Sure absolutely. I plan on doing that as well. You know what else should happen? Software not requiring countless hours of testing on a users end to fix a problem that occurs with a variety of plugins from entirely different developers in a configuration that should be relatively typical. "Oh but you just have to change this setting to that and only load this plugin as VST3 and then you have to edit the .ini file to permit xyz and of course don't forget install this hotfix and turn off bonjour service while you ..."

No. I don't want to jump through hoops to use software. That's shitty UX. I'll just complain and then get used to something else (like the majority of customers who don't have hours and hours to burn on some obnoxious problem).

Seriously WTF FL Studio...? + now with new OS hate underpinnings