WineHQ

FL Studio





Professional-quality DAW and Editing software from Image-Line. Has a large number of features, most notably ease-of-use and a large number of supported VST Plugin formats. Can export to .mp3, .mp4, .wav, and .ogg.


Most users say that the main selling point of FL Studio is the workflow and interface, which is geared towards putting the user's creativity first.

Application Details:

Version: 12.4.2
License: Retail
URL: http://www.flstudio.com
Votes: 5
Latest Rating: Platinum
Latest Wine Version Tested: 2.13-staging

Maintainers: About Maintainership

Link Image-Line Homepage (including Demo version)

Test Results

Old test results
The test results for this version are very old, and as such they may not represent the current state of Wine. Please consider submitting a new test report.
Selected Test Results

What works

- The FL Studio ASIO driver is nothing short of spectacular ... performance is quite acceptable, but users running a DE that employs Compositing will run into some overruns on underpowered systems (such as Unity, Cinnamon, etc), like a clash is going on between the audio driver and the compositing manager itself. Read more about that below on how to mitigate this issue.

- IL Downloader functions perfectly.

- Patcher's good to go!


- Plugin Manager works well too, aside from a child window issue that chops off slightly at the bottom of the VST list after scanning.


- Everything else that came with FL Studio (VST Plugins, etc) functions as expected and intended. Some, however, impact CPU performance more than others; especially Compression (Maximus) and Delay (Fruity Delay 2, Fruity Delay Bank), etc., but careful use (and reuse) of these effects can mitigate this particular caveat. The Image-Line Developers have been working very diligently to optimize their VST's as much as possible, and the FL ASIO Driver is MUCH more robust than before also; those two things have helped a great deal.


(Updated 7-16-2017 | FL Studio 12.4.2 | Wine 2.12-staging) 

What does not

- The included ASIO4All is known to not work. In fact, it is unnecessary to install it.


- ILBridge (Bridged Process for VST Plugins) is not working correctly. The plugin that this is applied to (notably ones in Patcher) will not appear, although the ILBridge parent window *does*. Please avoid bridging plugins or you'll need to force_end both ILBridge.exe and FL.exe processes before you'll be able to use them again.


- Some VST's need .Net to function. The solution is *not* in WINE, but in the Distro itself. Installing the "mono-vbnc" and then "mono-complete" metapackages will provide this functionality. (This solution was found by trial-and-error, and solves ALL issues except in rare cases where the VST's are doing things they really shouldn't be doing anyway.)

(Updated 7-25-2017 | FL Studio 12.4.2 | Wine 2.13-staging) 

Workarounds

What was not tested

- Flowstone is now a separate download, and as such was not downloaded or tested.

(Updated 7-16-2017 | FL Studio 12.4.2 | Wine 2.12-staging) 

Hardware tested

Graphics:

  • GPU:
  • Driver:

Additional Comments

------------------------------------ Pre-and Post-Install Procedures: ------------------------------------ In the past, there was a lengthy procedure on getting additional libraries installed through Winetricks. Those are by and large no longer necessary, I'm happy to say. The Image-Line Developers have done us a GREAT service -- nearly ALL outstanding Wine + FL Studio issues have been resolved as of FL Studio 12.3 and Wine 1.9.19. In the installer routine you'll want to deselect the ASIO4All entry, since you won't need it. ---------------------- Post-Installation: ---------------------- - If you see "Can't find xxx.wav" samples, here's what you do to resolve it. Navigate to the (FL Studio installation folder)\System\Installers\VorbisACM\codec, copy the file 'vorbis.acm' to .wine/(etc)/Windows/System32. Then in notepad, load up the system.ini file and add 'MSACM.vorbis=vorbis.acm' (without the tick marks) in the [Drivers 32] section, then save it. Modify this procedure if you're using the 64-bit version of FL Studio, you'll need to add the 64-bit codec instead from the VorbisACM-x64 folder. - IF the FL Studio ASIO Driver didn't register or wasn't installed properly, there's a fix. Users encountering an error that reads 'Cannot load FLStudio ASIO Driver' can check that it has been registered correctly by using wine regedit and navigating to HKEY_CURRENT_USER/Software/Image-Line/FL Studio 12/Devices/Audio output and making sure that the following String Values have been set: Buffer length (DS) REG_SZ (any acceptable value, set it to from 32 to 2048) Device name REG_SZ 1FL Studio ASIO (the '1' is present in mine and it works perfectly) Sample rate REG_SZ 44100 If the above isn't present, reinstalling FL Studio 12 (or performing a clean install from scratch) should fix the issue. ----- Tips: ----- - It's no longer necessary to force-kill FL Studio in the System Monitor as of 12.3 when we exit the application. - Significant performance increases will be achieved if the user sets the Generic ASIO latency to 1024 and enables Triple Buffering in the Audio Settings. Also, deselecting "Safe Overloads" results in the Audio Driver performing at maximum efficiency now, since in Linux the Window Manager (even in Wine) handles that stuff. Then, on the General Settings under Effects, select 'Don't distract me', and deselect the option for 'Ultrasmooth' and activate 'Force Refreshes' if you're using a desktop environment that uses compositing. Cinnamon, Gnome, KDE, Compiz, Unity and XFCE users will generally want to activate this, MATE users will know whether they need to or not. This will also help with the WINE Pulseaudio driver clashing with your WM. Early on this resulted in a nearly 100% improvement in how capable and resilient the new ASIO Driver was regarding heavier and more instrument-laden projects; ie, where it would clip and stutter before the changes, the project would play all instruments without the clipping and stuttering. This indicates that while the some of the issues experienced in FL Studio 11.x and 12.x regarding compositing are still present, the developers are aware of it and have taken measures to mitigate it within the new version. It is highly recommended that Wine users take advantage of this feature, from a performance standpoint. Compiz-based Window Managers (Unity and MATE in Compiz Mode) and Mutter/Clutter ones (Gnome-Shell and Cinnamon) are more susceptible to this GUI Overrun problem at high CPU levels, but it does not affect typical use. Delay and Compression effects seem to cause the most stutter of all in Patcher (if you're using it), so use them sparingly. Efficient use of effects will minimize the impact the GUI Overrun problem has upon your experience. - For best results during direct input recording that utilizes Edison, users should choose 64 or 128 samples for lag-free "realtime" (or very close to it) buffer speed. CPU usage would occasionally spike to 85% on my AMD Athlon II 5200+ but not stutter if using the 'Tools -> Macros -> Toggle smart switch disable/enable for all plugins' and careful selection of active plugins and effects afterward. - The clash between Compositing and Audio Driver in previous versions of FL 12 (and FL 11) which caused overruns have been mostly addressed and dealt with. Compositing-based Window Managers can still cause this issue sometimes when CPU use is above 85%. The best thing to do at those times is simply do not move your mouse cursor over the Piano Roll/Playlist during playback. Pressing the "Stop" button several times will force the buffers to cease whatever they are doing, and the user should wait a few seconds for the CPU use to decrease down to idle before continuing. Another way to mitigate this is to use non-effect-heavy WM's like MATE and XFCE; but in my experience XFWM didn't play well at ALL with Wine windows. So, ultimately, MATE was the DE of choice for my needs. This situation is improving with each FL Studio release, and in 12.4.2 this problem can be mitigated for the most part. ------------------------- The upgrade to the current 12.x series has been a true game-changer for FL Studio on Wine. I send my appreciation (as should ALL users of FL Studio on Wine) for supporting us and fixing 99.9% of the outstanding issues in version 12. Plenty more to come. (Updated 7-16-2017 | FL Studio 12.4.2 | Wine 2.12-staging)

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
CurrentLinux Mint 18.2 "Sonya" x86_64Jul 16 20172.13-stagingYes Yes PlatinumUnobscured Vision 
ShowLinux Mint 17.3 "Rosa" x86_64Apr 05 20172.4Yes Yes PlatinumCory 
ShowGentoo Linux x86_64Mar 26 20172.3Yes Yes GarbageEvi1 M4chine 
ShowUbuntu 16.10 "Yakkety" amd64 (+ variants like Kubuntu)Nov 24 20161.9.23Yes Yes Goldan anonymous user 
ShowUbuntu 16.04 "Xenial" amd64 (+ variants like Kubuntu)Jun 17 20161.9.12Yes Yes Goldan anonymous user 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs

HowTo / Notes

Set a virtual desktop for FL Studio to better support window managers, and workspaces.

The FL Studio UI can sometimes go haywire if you workspaces in your desktop environment - the audio engine works and events are handled (for example, space still plays/pauses the project) but the UI is frozen.

Comments

The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

regkey
by MOS420 on Sunday October 22nd 2017, 17:34
I installed the regkey for producer edition but it still says it's the demo, any help???
Almost there...
by pich on Friday July 21st 2017, 21:39
Everything runs fine, except FL ASIO has horrible, but working, latency and WineASIO is giving "Division by zero" error when selected. Any ideas?
Right now, (wine 2.3), this is needed:
by Evi1 M4chine on Sunday March 26th 2017, 17:41
WINEPREFIX=~/yourPrefix winetricks corefonts

…for it to be usable.
Otherwise… no text in the menus.

(Actually, only Arial suffices, but that is more complicated.)

See this bug: bugs.winehq.org/show_bug.cgi?id=33482
FL Studio 12.4 on Ubuntu 16.10 64bit, Wine 2.2 staging - PCM audio issues
by michael on Sunday March 5th 2017, 5:59
With wine 2.2 almost everything installs and runs perfectly.

My only major problem is that I cannot play wav files that are PCM encoded. Vorbis wav files play fine, as do all other file formats. Only PCM audio is an issue. I have searched high and low but cannot find a solution to this. I am having to convert all my wav samples to ogg just to use them.

Any help would be appreciated :-)
Anyone know if this works if you buy it in a box, instead of buying online?
by ThomasLadson on Thursday January 19th 2017, 10:18
Trial works fine on my PC, it's significantly cheaper for me to purchase it in a box. I am considering buying Windows incase it doesn't.
0x0eedfade
by Go Away on Monday January 9th 2017, 12:58
For anyone *not* getting 0x0eedfade error when installing, but instead when launching FL for the first time, make sure you have a 32-bit wineprefix. "Pure" wine apparently defaults to 64-bit if available.
RE: 0x0eedfade
by youleemerida on Monday February 6th 2017, 15:54
How do you change the wineprefix?
I got a laptop with Linux from a friend of mine, and have pretty much no experience using it.
RE: 0x0eedfade
by Deryn L on Monday February 20th 2017, 10:59
I'm still getting this error when launching it in various combinations of fresh 32 and 64-bit prefixes. Are there any .NET packages I need to install?
RE: 0x0eedfade
by Jacob Juric on Saturday April 22nd 2017, 2:35
Another solution is to make sure the Windows version is set to XP in winecfg. For some reason, it defaulted to 7 for me, and changing to XP made FL start successfully.
"Missing" Samples ....
by Unobscured Vision on Thursday December 22nd 2016, 14:27
On my VERY thorough installation and configuration walkthrough (which *has* been the "Gold Standard" of FL Studio on WINE walkthroughs for a year now) there's a section specifically dealing with this. It's an easy fix and it'll take someone maybe, *maybe* three minutes to apply. Seriously, please look at it.

I keep the walkthrough updated on a regular basis, and pride myself on doing so.
Fix for 0x0eedfade exceptions running installer
by Jacob Juric on Tuesday December 13th 2016, 4:55
If anyone is getting an unhandled 0x0eedfade exception in the installer after "unpacking files", try opening winecfg, and adding an override for webdll set to disable. This solved the problem for me.
RE: Fix for 0x0eedfade exceptions running installer
by Jacob Juric on Tuesday December 13th 2016, 5:57
However, the exception still occurs with starting FL.exe, and I've yet to find a fix for it. I've put the log from wine in this pastebin: pastebin.com/qwCfRBVg
RE: Fix for 0x0eedfade exceptions running installer
by Nathan Graule on Tuesday December 20th 2016, 15:30
I hit that unhandled exception under 1.9.23 but with 2.0-rc2 it's fixed. Not the best solution but it works.
I'm working on testing FL 12.4 under that version of wine, and so far so good!
RE: Fix for 0x0eedfade exceptions running installer
by Jacob Juric on Friday December 23rd 2016, 23:27
Neither 2.0-rc2 or 2.0-rc3 fixes this issue for me, in a 32 or 64-bit wineprefix. I'm starting to think sonething's up with my system.
Fix Resolution of polapp
by César on Thursday December 1st 2016, 20:31
Hi again, for fix the problem of resolution, you need go to playonlinux -> fl studio 12.4 -> configure -> wine tab -> configure wine -> graphics tab -> Emulate virtual Desktop - > change the resolution to fit with your screen.
RE: Fix Resolution of polapp
by César on Thursday December 1st 2016, 20:32
You need check "Emulate virtual Desktop" and change the resolution. Missing info. :P
Fl Studio 12.4 polapp
by César on Sunday November 27th 2016, 14:16
Hey guys, i was packed fl studio 12.4 demo version . it is legal becouse it is without license. Enjoy.
sourceforge.net/projects/unidockynapse/files/flstudio_12.4-latest.polApp/download
RE: Fl Studio 12.4 polapp
by César on Monday November 28th 2016, 6:05
For it works with multicore support you need install wine staging and run wine configuration - > staging -> Enable CSMT.
FLStudio 12.4 installer crashes on Ubuntu 16.10, wine 1.9.23
by Jack on Thursday November 17th 2016, 22:37
I followed the instructions (installing fonts), download and launch flstudio_12.4.exe. It verifies the installer, unpacks the data, then crashes, with the output below.

Any thoughts?

-Jack




Unhandled exception: 0x0eedfade in 32-bit code (0x7b43e2a2).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:7b43e2a2 ESP:0033f624 EBP:0033f698 EFLAGS:00200287( - -- I S - -P-C)
EAX:7b428af9 EBX:7b640000 ECX:0000001c EDX:0033f644
ESI:00000007 EDI:0033f700
Stack dump:
0x0033f624: 0033f6bc 0000001c eb82f900 0eedfade
0x0033f634: 00000001 00000000 7b43e2a2 00000007
0x0033f644: 0107c4dc 012050e0 0121a960 010c82e8
0x0033f654: 0033f700 0033f6f0 0033f6d8 7e93b000
0x0033f664: 7ffd8bf8 7e8e2149 7e8f767f 00000000
0x0033f674: 00000024 0033f6e4 01063c00 0033f6a4
000c: sel=0067 base=00000000 limit=00000000 16-bit r--
Backtrace:
=>0 0x7b43e2a2 in kernel32 (+0x2e2a2) (0x0033f698)
1 0x0107c4dc in webdll (+0x1c4db) (0x0033f6f0)
2 0x0107c46c in webdll (+0x1c46b) (0x0033f754)
3 0x010c84e7 in webdll (+0x684e6) (0x0033f77c)
4 0x010c8359 in webdll (+0x68358) (0x0033f798)
5 0x010c975d in webdll (+0x6975c) (0x0033f8f0)
6 0x00401fe0 in flstudio_12.4 (+0x1fdf) (0x0033fabc)
7 0x004013a8 in flstudio_12.4 (+0x13a7) (0x0033fc88)
8 0x004013a8 in flstudio_12.4 (+0x13a7) (0x00429400)
0x7b43e2a2: movl 0xfffffff4(%ebp),%ecx
Modules:
Module Address Debug info Name (85 modules)
PE 3d0000- 3ee000 Deferred usermgr
PE 3f0000- 3f6000 Deferred system
PE 400000- 43e000 Export flstudio_12.4
PE 1060000- 10e3000 Export webdll
PE 10000000-10007000 Deferred uac
ELF 7b400000-7b7e9000 Dwarf kernel32
\-PE 7b410000-7b7e9000 \ kernel32
ELF 7bc00000-7bcf8000 Deferred ntdll
\-PE 7bc10000-7bcf8000 \ ntdll
ELF 7c000000-7c004000 Deferred
ELF 7d843000-7d988000 Deferred oleaut32
\-PE 7d860000-7d988000 \ oleaut32
ELF 7d988000-7da14000 Deferred libgmp.so.10
ELF 7da14000-7da49000 Deferred libhogweed.so.4
ELF 7da49000-7da85000 Deferred libnettle.so.6
ELF 7da85000-7da9a000 Deferred libtasn1.so.6
ELF 7da9a000-7dace000 Deferred libidn.so.11
ELF 7dace000-7db2f000 Deferred libp11-kit.so.0
ELF 7db2f000-7dcb6000 Deferred libgnutls.so.30
ELF 7dcc0000-7dcd9000 Deferred userenv
\-PE 7dcd0000-7dcd9000 \ userenv
ELF 7dcd9000-7dd16000 Deferred ws2_32
\-PE 7dce0000-7dd16000 \ ws2_32
ELF 7dd16000-7dd3f000 Deferred iphlpapi
\-PE 7dd20000-7dd3f000 \ iphlpapi
ELF 7dd3f000-7dd70000 Deferred netapi32
\-PE 7dd50000-7dd70000 \ netapi32
ELF 7dd70000-7dda5000 Deferred secur32
\-PE 7dd80000-7dda5000 \ secur32
ELF 7de0a000-7de43000 Deferred uxtheme
\-PE 7de10000-7de43000 \ uxtheme
ELF 7de43000-7de4a000 Deferred libxfixes.so.3
ELF 7de4a000-7de55000 Deferred libxcursor.so.1
ELF 7de55000-7de68000 Deferred libxi.so.6
ELF 7de68000-7de6c000 Deferred libxcomposite.so.1
ELF 7de6c000-7de79000 Deferred libxrandr.so.2
ELF 7de79000-7de85000 Deferred libxrender.so.1
ELF 7de85000-7de8c000 Deferred libxxf86vm.so.1
ELF 7de8c000-7de90000 Deferred libxinerama.so.1
ELF 7de90000-7de97000 Deferred libxdmcp.so.6
ELF 7de97000-7de9b000 Deferred libxau.so.6
ELF 7de9b000-7dec1000 Deferred libxcb.so.1
ELF 7dec1000-7e00c000 Deferred libx11.so.6
ELF 7e00c000-7e021000 Deferred libxext.so.6
ELF 7e025000-7e02e000 Deferred libffi.so.6
ELF 7e02e000-7e042000 Deferred shfolder
\-PE 7e030000-7e042000 \ shfolder
ELF 7e044000-7e0d6000 Deferred winex11
\-PE 7e050000-7e0d6000 \ winex11
ELF 7e0d6000-7e0fc000 Deferred imm32
\-PE 7e0e0000-7e0fc000 \ imm32
ELF 7e180000-7e1aa000 Deferred libexpat.so.1
ELF 7e1aa000-7e1f3000 Deferred libfontconfig.so.1
ELF 7e1f3000-7e22d000 Deferred libpng16.so.16
ELF 7e22d000-7e248000 Deferred libz.so.1
ELF 7e248000-7e2fb000 Deferred libfreetype.so.6
ELF 7e31e000-7e3a5000 Deferred rpcrt4
\-PE 7e330000-7e3a5000 \ rpcrt4
ELF 7e3a5000-7e4ee000 Deferred ole32
\-PE 7e3c0000-7e4ee000 \ ole32
ELF 7e4ee000-7e5fa000 Deferred comctl32
\-PE 7e500000-7e5fa000 \ comctl32
ELF 7e5fa000-7e675000 Deferred shlwapi
\-PE 7e610000-7e675000 \ shlwapi
ELF 7e675000-7e8c5000 Deferred shell32
\-PE 7e680000-7e8c5000 \ shell32
ELF 7e8c5000-7e941000 Deferred advapi32
\-PE 7e8d0000-7e941000 \ advapi32
ELF 7e941000-7ea77000 Deferred gdi32
\-PE 7e950000-7ea77000 \ gdi32
ELF 7ea77000-7ebda000 Deferred user32
\-PE 7ea90000-7ebda000 \ user32
ELF 7ebda000-7ebed000 Deferred libnss_files.so.2
ELF 7ebed000-7ec08000 Deferred libnsl.so.1
ELF 7ef87000-7efdd000 Deferred libm.so.6
ELF 7efe6000-7f000000 Deferred version
\-PE 7eff0000-7f000000 \ version
ELF f7361000-f736e000 Deferred libnss_nis.so.2
ELF f7370000-f7375000 Deferred libdl.so.2
ELF f7375000-f752f000 Deferred libc.so.6
ELF f752f000-f754c000 Deferred libpthread.so.0
ELF f7564000-f756e000 Deferred libnss_compat.so.2
ELF f756f000-f7726000 Dwarf libwine.so.1
ELF f7729000-f774e000 Deferred ld-linux.so.2
ELF f7750000-f7751000 Deferred [vdso].so
Threads:
process tid prio (all id:s are in hex)
0000000e services.exe
00000020 0
0000001f 0
00000014 0
00000010 0
0000000f 0
00000012 winedevice.exe
0000001e 0
00000019 0
00000018 0
00000013 0
0000001c plugplay.exe
00000022 0
00000021 0
0000001d 0
00000023 explorer.exe
00000028 0
00000027 0
00000026 0
00000025 0
00000024 0
00000029 (D) Z:\home\jack\Desktop\flstudio_12.4.exe
0000002b 0
0000002a 0
Multicore with wine staging
by César on Sunday September 11th 2016, 15:32
Hello all, i was installed latest version 12.3 in playonlinux with wine staging 1.9.18 version. By default wine runs only with 1 cpu core , if you want a better performance. do the follow:
1.- in playonlinux -> configure -> wine -> enable CSMT for better performance.
2.- Edit your FL studio shortcut in the folder .Playonlinux->Shortcuts
Add all Exports as the following example:
Change the path user with your owns.
3-Save the file (do it with playonlinux closed)
4.Open playonlinux and you will have fl studio with a great performance.
5.-If you want tunning your os with lowlatency improvements.: wiki.linuxaudio.org/wiki/system_configuration
I have my own linux distribution with all these patches applied.
sourceforge.net/projects/unidockynapse/
Feel free to test it if you want. Enjoy
#!/usr/bin/env playonlinux-bash
########### Fl studio Shortcut ################
[ "$PLAYONLINUX" = '' ] && exit 0
source "$PLAYONLINUX/lib/sources"
export WINEPREFIX="/home/cesarin/.PlayOnLinux/wineprefix/fl_studio"
export env LD_PRELOAD="${LD_PRELOAD} libpthread.so.0 libGL.so.1"
export __GL_THREADED_OPTIMIZATIONS=0
export STAGING_SHARED_MEMORY=1
export STAGING_WRITECOPY=1
export STAGING_RT_PRIORITY_SERVER=86
export STAGING_RT_PRIORITY_BASE=86
export WINEDEBUG="-all"
cd "/home/cesarin/.PlayOnLinux/wineprefix/fl_studio/drive_c/./Program Files/Image-Line/FL Studio 12"
POL_Wine FL.exe "$@"
############# end Fl studio Shortcut #############
RE: Multicore with wine staging
by Unobscured Vision on Saturday October 1st 2016, 2:55
Nice, looks good. I'll have to give this a go myself.
RE: Multicore with wine staging
by César on Saturday October 1st 2016, 16:20
Yes, you will have better performance that in MS Windows. The only problem is some VSTs did not work fine in Linux. I use only free stuff like synth1 with presets, fluid soundfont . I am very happy with the performance. I spend a lot time optimizing unidockynapse for low latency operation, thinking that the problem was in the CPU governer, but the real solution was the above solution, the problem was that not all threads of the cpu were using. greetings.
RE: Multicore with wine staging
by Unobscured Vision on Wednesday October 5th 2016, 20:35
Here's one for non-PlayOnLinux users. Make executable when done, change menu entries, make launchers. Go to town. You know what you need to change here to make it work.

#!/bin/sh
########### Fl studio Shortcut ################
env WINEPREFIX="/home/[your username]/.wine"
export env LD_PRELOAD="${LD_PRELOAD} libpthread.so.0 libGL.so.1"
export __GL_THREADED_OPTIMIZATIONS=0
export STAGING_SHARED_MEMORY=1
export STAGING_WRITECOPY=1
export STAGING_RT_PRIORITY_SERVER=86
export STAGING_RT_PRIORITY_BASE=86
export WINEDEBUG="-all"
cd "/home/[your username]/.wine/drive_c/Program Files (x86)/Image-Line/FL Studio 12/"
wine FL.exe
midi import and lsd vst crash crash
by satyrcorn on Friday September 9th 2016, 4:39
Hi

I have a crash when i import à midi file or i use native vst "lsd "
Anyone ça help me ?
RE: midi import and lsd vst crash crash
by Unobscured Vision on Saturday October 1st 2016, 2:56
Yeah. Some VST's are still crashy. Nothing I've been able to figure out to stop it from happening. Most annoying indeed. :(
No sound in VSTs
by MrHudson on Sunday April 3rd 2016, 15:10
I don't know why but VSTs in FL Studio produce no sound. I installed it through PlayOnLinux, installed mono-complete through apt-get and still can't get it to work.

Tested with NeoPiano and Sylenth1. They all load well into the wrapper, but they don't output any sound.
RE: No sound in VSTs
by Unobscured Vision on Sunday April 3rd 2016, 22:56
PlayOnLinux shouldn't do anything weird that could cause this.

1) Are you using the FLStudio ASIO Driver in FLStudio's Audio Options?

2) Have you *made sure* that mono-visualbasic and mono-vbnc packages are installed? (use Synaptic to install these; and yes, you'll likely need to install Synaptic -- but I can't think of a single good reason why anyone *wouldn't* need Synaptic) make sure that the visualbasic symbols and visualbasic-debugging stuff is installed too). Usually anything .Net and Mono that isn't installed that *should* be when Windows programs are expecting it to be there will cause unusual behavior, and it's our job to be prepared for those contingencies.

3) Check other VST Plugins (like OBXD and others) .. I can't imagine that Sylenth and NeoPlano are the only ones affected. I *have* run into instances where some VST's wouldn't work, maybe those VST's are among those that just "won't work". I'll try them myself and see.
RE: No sound in VSTs
by MrHudson on Monday April 4th 2016, 11:19
1) I don't have that option - it's only Primary Sound Driver and Pulseaudio.

2) I have installed the following:
* monodevelop
* mono-complete
* mono-dbg
* mono-basic-dbg
* mono-vbnc
* libmono-microsoft-visualbasic*

3) I do use both of them on a regular basis though on my Windows PC and have gotten used to them. I'd rather not have to make compromises in this regard.
RE: No sound in VSTs
by Unobscured Vision on Monday April 4th 2016, 11:32
Hmm. Try reinstalling FLStudio (don't uninstall it, just reinstall) and make sure the FLStudio ASIO Driver is checked in the install options. There's a glitch where it isn't installed and/or registered properly sometimes, and usually reinstalling will fix it.

Regarding the VST's, I haven't tried them yet. I'll do that shortly.
RE: No sound in VSTs
by MrHudson on Thursday April 14th 2016, 12:58
I did reinstall FL and the problem still persists, even with using the FL ASIO.
RE: No sound in VSTs
by Unobscured Vision on Saturday April 16th 2016, 2:58
I installed the plugins myself and I can't even get them to load, much less find out why they won't generate sound. They're registered in the Plugin Manager as they should be; they just won't load up in FL Studio. It's a frustrating problem, I agree with you.

Regarding *all* VST's not generating sound; are you using the 32-bit or the 64-bit FL Studio? And if you're using 64-bit, try the 32-bit exe. If the results are the same, try using the "compatible memory" executable in the FL Studio folder (~/.wine/drive_c/Program Files (x86)/Image-Line/FL Studio*/). Sometimes that will work, sometimes not.

What I think is going on is there's a problem with the VST Bridge not communicating with FL Studio properly with some plugins; and the way WINE works is it actually *prevents* things from working in an incorrect, unsafe or unsecure way (buffer over/underruns, memory leaks, etc). In a nutshell, it handles Win32/Win64 stuff the way Microsoft *should* be coding Windows.

I'm going to keep trying your VST Plugins on my end with the different .exe's and see which one works, and I'll get back to you. I haven't run out of tricks yet.
RE: No sound in VSTs
by MrHudson on Friday May 27th 2016, 12:21
Any updates to this? FL plugins are currently the only thing preventing me from switching to Linux full time :\
RE: No sound in VSTs
by Unobscured Vision on Friday May 27th 2016, 12:52
Well *I* can't figure it out. The 64-bit bridged VST's and the old Synthmaker-based ones are still flaky sometimes. The ones you'd reported about I couldn't get working. There are some new changes and additions to the DirectSound API's in WINE 1.9.11; so there are known deficiencies that *are* being addressed. These things take time to get sorted, so let's not lose hope. I suggest another year or so of Dev time on WINE. And yes, it's frustrating and annoying to wait.
.Net-based VST problems now have a fix!
by Unobscured Vision on Saturday December 12th 2015, 20:15
Onward and upward! All the relevant information needed to get .net-based VST plugins working has been added to the Testing Report. Please refer to my maintained testing information above to read about it.
RE: .Net-based VST problems now have a fix!
by Olivier Rojon on Monday December 14th 2015, 2:34
Hey man,

this is totally not related to the ".net-based" stuff, but maybe noteworthy nonetheless.

I thought it might be helpful to add to the guide that wine need be installed as staging ppa (not softwarecenter, not custom-built) and that winetricks is not to be installed via the software center or else but downloaded online. And as soon as installed, it is to be "handled" by the terminal, say "sh winetricks XXXX". While I'm not sure if it would've eliminated my initial problems on Ubuntu MATE, it sure helped a lot applying all the relevant changes to winetricks and made all these lame "sha1sum"-errors disappear. In this way, it was even possible to copy&paste the whole list indicated in the pre-installation guide and just let winetricks do its magic.
RE: .Net-based VST problems now have a fix!
by Unobscured Vision on Monday December 14th 2015, 11:50
That's probably a good idea. The procedure is quite involved, and users are going to be put off seeing all of this stuff for sure. Seems like the best way to go about this would be to submit a PlayOnLinux Script to automate most of the stuff, and have some user interaction to install the mono-complete bits, but that WILL draw some ire from the "purists" who hate anything .Net -- but having said that, the purists aren't going to be using WINE. :)

I'll see about making a POL Script and submitting it. I happen to use POL, but I'm not a member of that community as of the current time so we'll see how that goes.

Thanks for the suggestion. :)
ASIO Error: CoCreateInstance failed; Code: -2147221164
by Olivier Rojon on Friday November 20th 2015, 2:31
Hello!

I am on Ubuntu MATE 15.10. I followed your (sort of) installation guide indicated above: I have manually compiled wine1.7.54, added fonts etc in winetricks, moved vorbis, made registry changes.

However, one problem always persisted: when launching, I am getting a "FL Studio ASIO Error: CoCreateInstance failed. Code: -2147221164". Being relatively new to Ubuntu and Linux, I have not the slightest inkling of a clue what is going on, but the result of this error is quite simple: there is no sound. Do you have an idea how to go about it?
RE: ASIO Error: CoCreateInstance failed; Code: -2147221164
by Unobscured Vision on Tuesday December 1st 2015, 1:48
You should *never* have to compile WINE from source on any modern Linux distro. The WINE Devs are suggesting everyone use the wine-staging ppa for the latest WINE (and related tools like Winetricks). It really *is* easier and faster than compiling yourself.

Sounds to me like you're missing some linked libraries somewhere. Usually with WINE it's something simple and fixable, so I suggest you try the wine-staging ppa next. If that doesn't fix you, we'll explore those avenues. I don't mind helping out. :)
RE: ASIO Error: CoCreateInstance failed; Code: -2147221164
by Olivier Rojon on Thursday December 10th 2015, 13:41
Hey there,

thats very nice of you. I've configured the wine staging ppa as indicated here (github.com/wine-compholio/wine-staging/wiki/Installation#-ubuntulinux-mint). I've tried to download all the packages indicated on the list, but those couldn't be found:
msflxgrd
mshflxgd
msmask
richtx32
tabctl32
vcrun2015 (this one isn't even shown in the install list).

I'm a bit puzzled. I tried downloading and manually putting those *.exe and *.ocx files in the winetricks directory (./cache/winetricks/msflxgrd...etc) and launching FLS afterwards - but without success, the error remains the same.

One thing I came up: maybe we are using different wine versions: from the wine staging ppa, I "received" wine 1.7.54, which appears to be different from the version that you are using.

Any idea :s?
RE: ASIO Error: CoCreateInstance failed; Code: -2147221164
by Unobscured Vision on Thursday December 10th 2015, 13:55
At first I was on wine-staging-1.7.54, and I didn't have any problems aside from .Net-based VST's not loading (not unexpected, though vexing since they had worked previously) -- now I'm on wine-staging-1.8rc2, and winetricks is constantly being updated. It's possible you've got a version clash going on, where winetricks isn't updating properly.

I had this overall problem happen with wine before, and I wasn't able to fix it (where *nothing* worked). My only recourse was to reinstall my Distro (annoying as that is), and start over.

This could be a similar problem you've run in to. I've also moved to Linux Mint from straight Ubuntu, and it's treating me a LOT better but it can still be funny sometimes.

No reward without risk, eh? :)
RE: ASIO Error: CoCreateInstance failed; Code: -2147221164
by Olivier Rojon on Friday December 11th 2015, 7:09
Hey again,

so I reinstalled my computer and switched to Linux Mint. I configured wine staging ppa and installed both wine and winetricks (--version outputs: wine=wine-1.8-rc3; winetricks=20140302). I tried getting all the listed packages, but its pretty much the same ones I can't seem to get: allcodecs msflxgrd mshflxgd msmask richtx32 tabctl32 vcrun2015.

Additionally, droid and tahoma fonts don't seem to install properly.

Now: do you know where I can safely download the above listed packages? What is the right way to install them, just putting files in the .\cache\winetricks\msflxgrd(example)\ folder and running "winetricks msflxgrd" again?
RE: ASIO Error: CoCreateInstance failed; Code: -2147221164
by Olivier Rojon on Friday December 11th 2015, 11:19
Re-hi,

it took me quite a while to understand that winetricks isnt a "program" in the same way wine is. I downloaded the latest winetricks and was able to install all the named packages and fonts. I then followed the other instructions and tips and - voilà, FL Studio runs :-)!!!

Thanks a lot dear sir (or madam), you made my life better by about 30% :-)
RE: ASIO Error: CoCreateInstance failed; Code: -2147221164
by Unobscured Vision on Friday December 11th 2015, 12:29
Wonderful! Now all that's left to really worry about is getting .Net and VB-based VST's running properly *all* the time, not just *sometimes*.

I'll continue to experiment and find the answers we all need. :)
RE: ASIO Error: CoCreateInstance failed; Code: -2147221164
by Unobscured Vision on Saturday December 12th 2015, 20:12
... aaaaaand now that's fixed. :) I've added the relevant information to the Testing Report.
RE: ASIO Error: CoCreateInstance failed; Code: -2147221164
by dan on Thursday March 10th 2016, 12:26
Hi, I'm on Ubuntu 14.04 , 64 bits , have FL 10 installed with wineasio and works perfect, but the FL 12 version is not recognizing the asio driver, it doesn't appear in the Audio Settings options, any clues?, please?
Thnx
RE: ASIO Error: CoCreateInstance failed; Code: -2147221164
by Unobscured Vision on Thursday March 10th 2016, 12:34
Is this the FL Studio ASIO Driver that is giving the error or the WINE ASIO Driver?
ASIO Error
by Domantas on Saturday October 24th 2015, 10:54
This is the output when ran through terminal:

i.imgur.com/NEmtMZS.jpg

As I understand, there is some problem with ALSA, but I'm not really sure how to fix it.
RE: ASIO Error
by Unobscured Vision on Tuesday November 17th 2015, 0:22
Looks like it's a problem with the Alsa-Pulseaudio Bridge. As in it wants it and can't find it.

Additionally, you're missing some fonts that the application wants. But that's secondary.

The FL Studio ASIO Driver was built to accommodate WINE-Pulseaudio, and nearly all distributions these days use Pulseaudio by default so it made sense.

Additionally, you have Skype running. That can *and will, sometimes* completely take over your audio subsystem. If the audio subsystem is locked down by Skype, obviously WINE (and FL) can't access it and will throw an exception followed by a buffer over/underrun. I suggest that you don't mix Skype and FL Studio in the future.
ASIO Error
by Domantas on Sunday October 18th 2015, 5:36
I'm getting this ASIO failed activating render device error:

i.imgur.com/0LdnmfN.png

I manually changed buffer length (DS) in regedit from 4096 to 1024, but the problem still persists
cmd line installation of vorbisacm
by Pony Cannon on Saturday October 17th 2015, 7:44
I had problems installing the vorbisacm on my system.

Manually copying the acm files into the system directories and editing the system.ini file didn't seem to work.

I found a way to install the 32 bit vorbisacm using command line.

Type wine cmd to run wine command line.

cd C:\Program Files (x86)\Image-Line\FL Studio 12\System\Installers\VorbisACM\codec>

enter command:

rundll32 setupapi,InstallHinfSection DefaultInstall 132 .\vorbisacm.inf

This allowed the 32 bit version to load the vorbis codec.

It didn't affect the 64 bit version.
Back