Fruity Loops

From Wine-Wiki

Jump to: navigation, search

Fruity Loops or FL Studio is apparently a full-featured sequencer for creating complex songs and realistic drum loops. The resulting song or loop can be exported to a WAV/MP3 file and all MIDI events can be exported to a standard MIDI file.

Contents

[edit] Wine application database

  • Please consider submitting your test results for running this software under Wine.
Become a Maintainer
Please consider volunteering to be an additional Maintainer for this software.

Regularly Submitting results for installing and running on the latest version of Wine makes a big difference for others considering using Wine. By looking at how well the software runs others can be encouraged to try it themselves and together you can make progress in finding workarounds. By testing the software you will also notice when something breaks and when you make a bug report, the bugzilla team will often point it out to the person who broke it. If you are slightly more technically minded, you are able to regularly compile wine and test it before each fortnightly release then you will catch breakages before each wine release.

  • Who can be a Maintainer? - anyone. no programming experience required.
  • What is required of a Maintainer? - not much, but you do make a real difference.

A big advantage of being a maintainer is that as you quickly become familiar with installing and using wine with your software, you can have a direct hand in improving wine and your software. Many times you will find very handy tips posted by others and by posting a summary many benefit from your work. When you are asked a question you don't know, simply post in the wine-users forum and perhaps someone can help.

Just by being there, you make a difference. A maintainer quickly tests each monthly release of wine, and adds to the application database a rating of how good it runs.. gold/silver/bronze or garbage. Wine is constantly being improved, and occasionally something breaks. When you do spot a breakage, file a bug in bugzilla and if you want to try and fix it you can then post to the wine-devel mailing list for advice. However, if you have a little spare time (usually about 2 hours, in between doing other things) regression testing allows you to identify which patch caused the break. By filling out a bugzilla report, posting the name of the software, and the patch which broke it to the wine-devel mailing list, the developer who broke it can have a look at fixing it.

  • This often results in very quick fixes.


[edit] Current Status

  • Not working well with Wine20050423 (May 2005)
  • version 5 has been said to have partial success with an older version of Wine
  • Further Details currently Unknown

[edit] Links

Wine Links

[edit] (Official) Wine Links

[edit] (Unofficial) Wine-Wiki Links


[edit] External Links

Personal tools