Is FL Studio 12 really a 64 bit application?

[SampleScience]

I noticed that my FL Studio 12.5 installation files are located in C:\Program Files (x86)\Image-Line\FL Studio 12.5 instead of the normal C:\Program Files for 64 bit software.

If it's 64 bit, why the FL64.exe isn't in the 64 bit Program File folder by default?

[solger]

In general, it doesn't really matter into which folder a 64-bit product is installed to ...

In case of FL Studio you can find the reason here: https://support.image-line.com/knowledg ... 34&ans=415

Why does the 64 Bit version install into Program Files (x86)? - Both the 32 and 64 Bit versions of FL Studio are installed to C:\Program Files (x86)\Image-Line\FL Studio. FL Studio 32 Bit = FL.exe and FL Studio 64 Bit = FL64.exe. This really, absolutely, doesn't matter, but people seem to fret about it, so let's just keep this between us and not start a global panic, OK? Program Files (x86) and Program Files(x64) folders are not really important, you can point installers anywhere. A future release will probably install to the standard Windows locations. We are doing this for two reasons 1. To minimize the FL Studio footprint when both versions are installed as they share a lot of content which takes up disk space. It's an additional 140 MB when combined vs an additional 950 MB if installed separately. 2. For this release we want people to have both 32 and 64 Bit version installed, for technical support & testing purposes.

[planetearth]

In general, it doesn't really matter into which folder a 64-bit product is installed to ...

In case of FL Studio you can find the reason here: https://support.image-line.com/knowledg ... 34&ans=415

Why does the 64 Bit version install into Program Files (x86)? - Both the 32 and 64 Bit versions of FL Studio are installed to C:\Program Files (x86)\Image-Line\FL Studio. FL Studio 32 Bit = FL.exe and FL Studio 64 Bit = FL64.exe. This really, absolutely, doesn't matter, but people seem to fret about it, so let's just keep this between us and not start a global panic, OK? Program Files (x86) and Program Files(x64) folders are not really important, you can point installers anywhere. A future release will probably install to the standard Windows locations. We are doing this for two reasons 1. To minimize the FL Studio footprint when both versions are installed as they share a lot of content which takes up disk space. It's an additional 140 MB when combined vs an additional 950 MB if installed separately. 2. For this release we want people to have both 32 and 64 Bit version installed, for technical support & testing purposes.

It sounds as if they're admitting they shouldn't have done it, but it also raises the question, "If I choose to only install the 64-bit version, why doesn't it just put everything there, including the few bits that are 32-bit? Why put it where no 64-bit user should expect to find it?"

I installed only the 64-bit version (or so I thought, since I unchecked anything that said "32-bit" in the installer), but was rather surprised to find the (otherwise useless) 32-bit version icon on my desktop, and the 64-bit files in the "wrong" folder. I rarely back up the "Program Files (x86)" folder, since I don't have much in it to worry about anymore; almost everything I want to keep is 64-bit.

Image-Line could (and should) separate the installers, and give those who want to install a 64-bit version their own installer. Even if that installs some 32-bit code in the "64-bit Program Files folders", there probably wouldn't be as much space taken up or as much code "shared" between versions, because most of the 32-bit version's files wouldn't be in the installer in the first place. Only the ones necessary for the 64-bit version would be there, even if some are 32-bit files.

That's the way other developers do it, regardless of whether they're developing DAWs, word processors or simple utilities.

And IL's stance that "This really, absolutely, doesn't matter, but people seem to fret about it, so let's just keep this between us and not start a global panic, OK?" is a bit disingenuous. Who are they to tell their customers what "matters"? They should worry about what their customers think, not tell them what matters.

Steve

[VariKusBrainZ]

Just choose the desired location when installing, simples

[planetearth]

Just choose the desired location when installing, simples

You don't know what it's installing (or where) until you've been through the installation process at least once, because you're not notified that there won't be anything going into a "64-bit file folder" during the installation process.

And if you're not extremely thorough when uninstalling it (to then re-install it where you want it to go and where it should have gone in the first place), you'll end up with duplicate files and conflicting Registry entries. This creates a real mess.

Steve

[sfxsound3]

Image-Line could (and should) separate the installers, and give those who want to install a 64-bit version their own installer.

Also they should give an option not to install all the crap FL Studio comes with. This program has become a real bloat over the years! Whoever needs SimSynth, Wasp, FLSlayer, piece of shit effects of 15 years ago, useless samples, demos from some jerks I don't want to know about, a gazillion Browser structures, etc., etc., etc.! Come on!

But no, they're so special, they just can't be arsed!!!

[sfxsound3]

Project Bones, for f**k's sake!!!

[Trancit]

...This program has become a real bloat over the years! Whoever needs SimSynth, Wasp, FLSlayer, piece of shit effects of 15 years ago, useless samples, demos from some jerks ...

Did you ever heard something about backwards compatibilty???

But no, they're so special, they just can't be arsed!!!

If you don´t like it go ahead and stop trolling...

One can say the same about every company on this panet... if you search for something negative you´ll find something negative

[Trancit]

I installed only the 64-bit version (or so I thought, since I unchecked anything that said "32-bit" in the installer), but was rather surprised to find the (otherwise useless) 32-bit version icon on my desktop, and the 64-bit files in the "wrong" folder. I rarely back up the "Program Files (x86)" folder, since I don't have much in it to worry about anymore; almost everything I want to keep is 64-bit.

There is no such option in the installer except for the plugin versions... so don´t be surprised if unchecking the 32bit version just have the effect that you don´t install the 32bit plugins...

In general: I don´t know, what´s all the whining is about... the additional files installed by the "unwanted" version are really not that big sized, that it would make any noticeable difference on nowadays hard disks...

Just delete the shortcut on the desktop from the version you don´t want to use and that´s it...
Much easier for you to do than for image line to offer 2 different installers and manage the tons of claims of people which are to silly to pick up the right one for them...
Everything has 2 sides and a company has to decide which way to go... live with the decision or leave it... very simple...

[chk071]

From what i can say: It absolutely doesn't matter where something is installed. Those folders are simply labelled to separate purely 32-bit from 64-bit programs. So, i wouldn't really care about that. If the executable would be a 32-bit process, you'd see so in the task manager, because 32-bit executables have a "(32-bit)" following the process name. My guess is that FL Studio still has some 32-bit components, which get wrapped for the 64-bit version, or something. If that is even possible.

[VariKusBrainZ]

I guess some people need their mother to wipe their arse

[inkwarp]

today's mitharing thread de jour.. about nothing.. :)

[Googly Smythe]

In response to the original question:
yes.

[Googly Smythe]

Also, too, I don't keep all my documents in My Documents...
-
There was a time when I installed everything (except Windows ) on my D: partition...
-
I don't much care what folder my programs go in, if only bits and pieces of them weren't scattered around in a dozen other locations. Two of the worst offenders being Waves and Valhalla.

[sfxsound3]

...This program has become a real bloat over the years! Whoever needs SimSynth, Wasp, FLSlayer, piece of shit effects of 15 years ago, useless samples, demos from some jerks ...

Did you ever heard something about backwards compatibilty???

But no, they're so special, they just can't be arsed!!!

If you don´t like it go ahead and stop trolling...

One can say the same about every company on this panet... if you search for something negative you´ll find something negative

I am right and you are wrong.