2019-11-13: viewtopic.php?t=212833
2023-08-04: viewtopic.php?t=309809
2025-01-21: viewtopic.php?t=331398
This is the most recent one:
2025-03-18: viewtopic.php?t=332649
I've been following this issue since FL Studio 12.5.1 came out with the vector version of DirectWave.
However, I haven't received a solution. I'm aware that for multisampling, the vast majority of your clients use NI Kontakt; perhaps that's why you're not paying attention to DirectWave. I suppose having that plugin working properly doesn't represent a real benefit for you. I would like to ask you to prioritize ensuring that native plugins have as few bugs and programming errors as possible because I've already paid for an FL Studio All Plugins Edition license, and it's irritating to want to use a tool that has bugs. Furthermore, when I bought FL Studio version 11, it had plugins like WASP, WASP XT, TS404, and Fruity SoundFont Player, and now they can't be used. They were very useful, and I know that Fruity SoundFont Player has a new version since version 20.9, but honestly, that version displays the sound banks very differently than the original version, and that's not exactly good. I've been considering switching for some time now. DAW, the free lifetime updates don't compensate me for the times I've had to install external plugins that then cause problems when I want to open the project on another computer.
I'm going to report the DirectWave problem one last time because, honestly, I'm fed up. I hope that now that they're updating DirectWave, they'll pay attention because the compatibility with the third-party formats it's supposed to support is very limited. In some cases, it doesn't even load the instrument, which is the case with Kontakt NKIs, regardless of whether the instrument is encrypted or not. I'm sorry if I'm being a pain, but I've been dealing with this for years and I don't want to continue like this. I haven't seen the slightest interest from them in fixing this. I don't know if I have to be a "power user" or recognized by the industry for them to even look at something that affects the customers who trusted FL Studio to use it as a work tool. I assure you I'm not exaggerating.
"""""BUGS"""""
Errors occur if you try to load, for example, an SFZ file. If the file includes the "/" character, forget it; DirectWave won't do anything.
If the file has samples with long names, DirectWave will truncate them, leaving only a limited number of characters. If you choose to export it as a monolithic file, there won't be a problem. However, if you dare to export it as a multi-sample file, it will only export the first file and overwrite it until it "successfully" completes its task.
If you load a file with multiple instrument layers, and DirectWave decides to load the file as a single layer, you won't be able to control the individual volume of each file/layer. It was arbitrarily decided by who-knows-who that this wasn't necessary.
If everything went well and you want to export your multi-sample file as a FLAC file, you'll find that this option is only available for the monolithic format. Who would want their instrument samples in FLAC format, which means it takes up less storage space?
If you want to work with DirectWave monolithic files, when you save your project, the sum of the size of your FLP file will determine its size. I don't know who decided that monolithic files should be saved in the FLP file instead of as individual files in storage, which would reduce the possibility of your project becoming corrupted and lost. Furthermore, if you have automatic backups enabled, it will save a version of that monster every so often, potentially leaving you with a folder of 100GB or more in a single project with backups, and that's not an exaggeration.
I'd like to know the opinion of FL Studio users on Mac because I know their experience is worse, especially since they're used to having to shut down due to plugins. The DAWs typically used on Macs hardly have any good plugins like FL Studio's, which, despite all the bugs, are good ideas and the main reason I decided to buy a license. You can easily make a good song (well, "easily" is relative). I suppose it's frustrating that if an external plugin fails, the program closes and corrupts your project, even if you have backups, because you can make changes in five minutes that completely alter the sound of a song.
I appreciate you taking the time to read this, if you did. It's things like this that explain why FL Studio still has a reputation as a DAW for beginners, and that's not something I or those of us who use the software believe, but many people from the old school do think so, and they're influencing the minds of new aspiring musicians. That's a shame.
I've included video and image examples, as well as tools for quick solutions if needed.
