At 1/27/13 08:06 PM, ChainsawPolice wrote:
At 1/27/13 07:53 PM, LichLordMusic wrote:
- Stick with Windows 7 Professional 64-bit. Windows 8 still does weird things to FL and not all plug-ins are supported on Win8 at the momentAs an avid Win8 user, I can safely assure you that there are no plugin conflicts, and there'd be no reason for the plugins to not work. It's quite the same as Windows 7.
I use Reason, Ableton and FL on my rig, with a bunch of plugins - both popular and not-so-popular. No conflicts yet!
At 1/27/13 07:53 PM, LichLordMusic wrote:
(plus I hate it anyway).Oh come on. That's no reason to shoot it down for others - just because you don't like it. Who knows, he might not like the look at first but eventually find nothing wrong with it after using it?
Everyone's wired differently.
Unfortonatly, myself and a few of my friends along with my co-workers all have had some form of bad experience with Win8. I understand fully that there are still alot of bugs which are mainly present on release and will probably be patched over in the next Service pack but for now I'm avoiding it unless I feel like giving it another go.
I have tested Win8 dual-booted on my current machine, running it off of one of my backup HDD's. The installation procedure ran smoothly and it's surprisingly quick in general considering it's running on a HDD instead of my Striped SSD array I use for Win7. I don't even mind the change in GUI that much, it's pretty easy to pick up and probably takes a few hours tops to get around it.
Where the problems mainly began for me was after I installed FL Studio 10 onto it. It runs fine and I can run most of my plug-ins with no issues. Everything seems well at first but then I start getting to points where EWQL Synphonic Choirs, Omnisphere and Tone2 Gladiator each present weird error codes. Eventually, I managed to get EWQL to recognise the latest version of PLAY and run the libraries, got Wordbuilder working eventually.
Omnisphere was an annoying one. No matter whatever I tried to do, the box which contains the challenge code which you have to copy and paste into the Spectrasonic website to get the authorisation code from appeared blank. Usually this is a common problem if you authorise through FL first and then try to bridge it afterwards, this time though the white-box-of-doom hung there. After a complete reinstall, bridging it straight away and then licensing it while bridged, it just works. I still do get a horrible crackling sound and high CPU usage if Pro-Verb is used in the FX rack in FL on Win8, no idea why though.
Gladiator simply refused to run. First of all V2.2 refused to run at all, I get runtime errors and FL crashes out completely. Grabbing the newer version (V2.4), I manage to get it installed and run. The funny thing about it is that it works... in a sense. You could only see the top bar where you can select, load/save patches along with the rest on the top but everything else in the plug-in simply didn't even exist. Even the fruity wrapper ended at the bottom of the top bar. I even contacted Tone2 and explained I'm testing Gladiator2 out on Win8 and explained the problem and after a 1 hour session of trying to break down what it possibly could be they admitted they don't really know what it possibly could be and they would get back to me with a solution. Funnily enough they never did.
After dealing with what I could (minus Gladiator), I tried composing a test composition, running pretty much a sound from each of my plugins and using a minimal amount of FX plugins while making it, just to be on the safe side. All I experienced is a painful process of random freezing, the audio repeating and glitching constantly and the occasional full-out crash. I get none of this back on Win7 thankfully.
On the positive side Ableton Lite runs pretty much flawlessly, Adobe Audition CS6 is stabler than on Win7 and my M-Audio sound card has an even lower latency (from 9ms on win7 to 6ms on win8) but that's about the only pro's at the moment. There's too many negatives which have hit me running FL Studio and some of the more heavyweight plug-ins in FL to recommend it. That's just the Audio/Production side, other people have pretty much bombarded me with their woes of how simple administrative tasks are now annoying and more long-winded to do and how more of their legacy software simply doesn't work although like you said Win8 runs a modified back end from Win7.
If I have the motivation I might have to run a Virtual Machine running Win8 on and see if I get any different results. All I can really sum up is that Win8 is bothersome, glitchy and not worth going out-of-the-way to get. If it's pre-installed on a consumer machine and sold then that's though really, you either like it and thrive or hate it and get stuck in an enviroment which will quickly put you off.
I honestly can't wait for SP1 to be released for Win8. It might fix all of my issues and I could give it another chance.