corrupted wav files from FLStudio @ Windows 7 HomePremium 64bit

Please report Windows related issues here

Return to “Technical Support (Windows)”

Forum rules
WE NEED DETAILS: Your problems will be addressed faster if you follow these suggestions:
  1. Specific information - a) FL Studio version & build number, b) what you are doing and what happens exactly, c) step-by-step instructions how reproduce the problem.
  2. Screenshots - Another great way to demonstrate issues. Get a free screenshot app here. Include images using the 'Attachments' tab, at the bottom of the post edit window.
  3. A video - The best way of demonstrating many issues. Get a free recorder here. Include mp4 videos to your post from the 'Attachments' tab, at the bottom of the post edit window.
  4. Use English - Google Translate your post. Short simple sentences in your original language translate best. We are happy to work this way, no need to worry.
NOTE: Technical Support is ONLY available Monday - Friday (9 am to 5 pm Central European Time), thank you.
[You can only see part of this thread as you are not logged in to the forums]
FidelityMusic (IL)
Mon Mar 13, 2017 2:25 pm

x

Re: corrupted wav files from FLStudio @ Windows 7 HomePremium 64bit

doctea wrote:This problem still exists and seems even worse for me now on Windows 10 and FLS 12.4.1 [build 4] - as soon as I click on the file in Explorer the process locks up. The registry fixes supplied above for Win7 don't seem to fix Windows 10
It does still exist, Microsoft has yet to correct the bug. If you've properly attempted the registry fix noted HERE and it doesn't work, I can only suggest the following:

1. Restart your computer.
2. Open FL Studio.
3. Open an instance of Edison.
4. Open the .WAV files in Edison, one at a time. You she see a large number of slice markers in Edison.
5. Press 'Ctrl + A' to select all.
6. Select the 'Regions' button Image followed by 'Delete' to delete all markers within the selection.
7. Save the file.

Other users have also reported being able to successfully delete the files using the Command Prompt as long as they do not access the folder containing the problematic .WAV files via Windows File Explorer, but we have yet to confirm if that works.




Return to “Technical Support (Windows)”