wont let me export? | FL Studio Community | Page 1

charred surge Jan 9, 2026, 8:04 PM

#

Ive never had any issues before until recently. last project i made had a veary simalar issue. this one is having the same/simalar issue, everything works great up until time to export


Crash log saved to C:\Users\Admin\Documents\Image-Line\FL Studio\Support\Logs\Crash\ folder.

Please use Ctrl+C to copy this message and report to support.

OS Version:
Windows 10 (Version 22H2, OS Build 19045.2604, 64-bit Edition)

Exception:
Access violation at address 00000000696EF62B in module 'Fruity WaveShaper_x64.dll' (offset 42F62B). Read of address 0000000CCB3C2988

Callstack:
00000000692C0000:00000000696EF62B: Fruity WaveShaper_x64.dll
00000000692C0000:00000000696EE00C: Fruity WaveShaper_x64.dll
000000000C830000:000000000CBEC1C7: Engine_x64.dll
000000000C830000:000000000CC186B1: Engine_x64.dll
0000000069E10000:000000006A1BA49B: FLEX_x64.dll
000000006A890000:000000006B6CB004: FLEngine_x64.dll
000000006A890000:000000006B6C9BBD: FLEngine_x64.dll
000000006A890000:000000006B703885: FLEngine_x64.dll
000000006A890000:000000006B0C61AD: FLEngine_x64.dll
000000006A890000:000000006B0C91BB: FLEngine_x64.dll
000000006A890000:000000006AA64CF2: FLEngine_x64.dll
000000006A890000:000000006ABAD799: FLEngine_x64.dll
000000006A890000:000000006ABB1F98: FLEngine_x64.dll
000000006A890000:000000006ABACE9E: FLEngine_x64.dll
000000006A890000:000000006ABB2053: FLEngine_x64.dll
000000006A890000:000000006AA65595: FLEngine_x64.dll
000000006A890000:000000006AA65658: FLEngine_x64.dll
000000006A890000:000000006A8A0134:```

#

000000006A890000:000000006ACCCA67: FLEngine_x64.dll
000000006A890000:000000006AC78AD3: FLEngine_x64.dll
000000006A890000:000000006B0C9A9E: FLEngine_x64.dll
000000006A890000:000000006B57DC60: FLEngine_x64.dll
000000006A890000:000000006B0F3D1B: FLEngine_x64.dll
000000006A890000:000000006B17C12F: FLEngine_x64.dll
000000006A890000:000000006B17BFDD: FLEngine_x64.dll
000000006A890000:000000006A9B7292: FLEngine_x64.dll
000000006A890000:000000006AA3672A: FLEngine_x64.dll
000000006A890000:000000006A9B6E6C: FLEngine_x64.dll
000000006A890000:000000006ACAFB08: FLEngine_x64.dll
000000006A890000:000000006AB9F52B: FLEngine_x64.dll
000000006A890000:000000006ACB20A9: FLEngine_x64.dll
000000006A890000:000000006ACB3DC4: FLEngine_x64.dll
000000006A890000:000000006ACB3CB8: FLEngine_x64.dll
000000006A890000:000000006A9B87B6: FLEngine_x64.dll
00007FFE7AF70000:00007FFE7AF7E7E8: USER32.dll
00007FFE7AF70000:00007FFE7AF7E229: USER32.dll
000000006A890000:000000006ACD3456: FLEngine_x64.dll
000000006A890000:000000006ACD34C8: FLEngine_x64.dll
000000006A890000:000000006ACD399A: FLEngine_x64.dll
000000006A890000:000000006B70D01F: FLEngine_x64.dll
000000006A890000:000000006B70DC39: FLEngine_x64.dll
00007FF697D60000:00007FF697E3722D: FL64.exe

Modules:
Fruity WaveShaper_x64.dll: C:\Users\Admin\Dropbox\PC\FL Studio 2025\Plugins\Fruity\Effects\Fruity WaveShaper\Fruity WaveShaper_x64.dll
Engine_x64.dll: C:\Users\Admin\Dropbox\PC\FL Studio 2025\Plugins\Fruity\Generators\FLEX\Engine_x64.dll
FLEX_x64.dll: C:\Users\Admin\Dropbox\PC\FL Studio 2025\Plugins\Fruity\Generators\FLEX\FLEX_x64.dll
FLEngine_x64.dll: C:\Users\Admin\Dropbox\PC\FL Studio 2025\FLEngine_x64.dll
USER32.dll: C:\WINDOWS\System32\USER32.dll
FL64.exe: C:\Users\Admin\Dropbox\PC\FL Studio 2025\FL64.exe


Undo:
Mute/unmute/solo playlist track(s)
Mute/unmute/solo playlist track(s)
Mute/unmute/solo playlist track(s)
Mute/unmute/solo playlist track(s)
Last reset```

gleaming estuary Jan 10, 2026, 5:38 AM

#

charred surge ```000000006A890000:000000006ACD34C8: FLEngine_x64.dll 000000006A890000:00000000...

Okay I'm not a coding expert but ig it's a problem with the WaveShaper.

I didn't encourage that problem before, but is it possible that you have automation tracks linked to your waveshaper? If yes, delete them just to look if it fixes the problem.

It could also be a offline rendering problem... but I'm not really sure

#

And do not load old mixer states if you used them

#

Rebuild the mixer states manually

charred surge Jan 10, 2026, 6:08 AM

#

gleaming estuary Okay I'm not a coding expert but ig it's a problem with the WaveShaper. I didn...

Thats the weird thing I'm not even using wave shaper 😭 last time it was saying fruity love something and I wasnt using that either. Its tweeking. I reinstalled fl studio aswell. Still bugged

gleaming estuary Jan 10, 2026, 10:45 AM

#

charred surge Thats the weird thing I'm not even using wave shaper 😭 last time it was saying ...

I think your files may be corrupted. because if you haven't used the fruity love filter at all, that indicates defective dll files. Did you change anything?

#

So generally in the settings or something similar?

charred surge Jan 10, 2026, 7:45 PM

#

gleaming estuary I think your files may be corrupted. because if you haven't used the fruity love...

I dont think so? Is litterly a fresh install 💔

#

Aghhh

gleaming estuary Jan 10, 2026, 8:32 PM

#

charred surge I dont think so? Is litterly a fresh install 💔

...This means that FL Studio tried to access an invalid memory address when running the distortion effect. Such crashes with the WaveShaper are known (for example, a similar bug occurred during rendering), and Image-Line corrected the error in a later update...

post from image line on theier website

#

Official FL Studio documentation and support recommendations advise you to always keep FL Studio and the plugins up to date and, if necessary, reinstall them if problems arise. The Image-Line Knowledge Base also describes diagnostic tools and the procedure for a clean reinstallation as standard troubleshooting in the event of crashes

charred surge Jan 10, 2026, 10:19 PM

#

I reinstalled it with a slightly newer version. That fixed it. I genuinly dont know why but I'm not complaining

#wont let me export?