Knowledge Base

views: 172978

Once upon a time, the answer was no. The answer is now, maybe. Never say never we suppose...

At this moment we have the FL Studio Mac OS X BETA (Crossover Wrapped) available for direct installation on Mac OS X. Note that this program is still a Windows emulation, not a native OS X program.

 

Our developers are right now working on native Mac OS X versions for some of our Windows only plugins. Edison, Gross Beat, Harmless, Harmor, Maximus, Ogun, Slicex, Sytrus, Vocodex. More information on how to get these here. You can see this as a first small step towards FL Studio native OS X compatibility as these plugins use the same code-base as FL Studio itself. If and when we can get these working to specification on OS X, FL Studio will likely follow soon after. You can help speed up this process by testing these plugins on your Mac and reporting issues.

 

Here are some of the problems porting FL Studio to native Mac OS X:

  1. Delphi:

    FL Studio is written in Delphi with in-line assembly for the DSP code. This is one reason why FL Studio and its graphics are so fast and fluid.

    Delphi is Windows / PC only is virtually impossible to port to Mac. However there are changes in this area. We need to wait for the compiler to be stable and bug free before we can progress. 

    Some people have mentioned FreePascal but (providing we could get it compiled for Windows) we'd still have to solve the other issues below.

  2. Windows API:

    FL Studio is completely dependent on the Windows API that takes care of moving, minimizing, maximizing windows, detecting cursor position, drag & drop, opening windows dialogs, clipboard functions, decoding MP3s, ... so a port would require all system dependent calls to be isolated & replaced by bi-platform dependent functions.

    Instead of calling a function called 'WindowsGiveMeTheMousePostion' you call a function called 'GiveMeTheMousePosition' which is a generic function that has the system dependent code to get the mouse position for each of the OSs you support.

    Just getting all this system dependent code from Deckadance (which was created more or less with porting in mind) and replacing it with bi-platform versions took almost 6 months. So we could multiply this by 50 for FL Studio with well over 1 million lines of code. 
     

  3. Historical growth:

    FL Studio grew from a simple, midi only drum sequencer to the fully fledged sequencer it is now.

    FL Studio was started 15 years ago at a time when wav files were considered 'hi-tech' and VSTi plugins didn't even exist yet then.

    We are not convinced of the logic of dragging along (porting) decisions that were made over a decade ago in a new project.

 

The FL studio Support Team