Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Hi,

I'm on v0.3.1 and using the latest version of fl studio. I had to turn on fixed buffer to help prevent clicks though pitching down still breaks up.

The lfos and macros will not stick to their destinations. I can add the modulation, though the control does not animate as no modulation is being applied. If I click away from the selected modulator the modulation indicators disappear. Even just mousing over the modulator button will remove the destinations. Oddly modulations from presets or randomly generated do work. 

If I double click any control fl studio crashes. Here's the log:

FL Studio (20.9.2.2963) [64Bit] r27090 has encountered an error and needs to restart.

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

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

Exception: 

Access violation at address 00007FFC2B1D33A8 in module 'Emergence.vst3'. Read of address 0000000000000F80

Callstack: 

00007FFC2AF50000:00007FFC2B1D33A8: Emergence.vst3

00007FFC2AF50000:00007FFC2B113C50: Emergence.vst3

00007FFC2AF50000:00007FFC2B08F2E8: Emergence.vst3

00007FFC2AF50000:00007FFC2B15323A: Emergence.vst3

00007FFC2AF50000:00007FFC2B13B678: Emergence.vst3

00007FFC2AF50000:00007FFC2B087ADE: Emergence.vst3

00007FFC2AF50000:00007FFC2B0D28F1: Emergence.vst3

00007FFC2AF50000:00007FFC2B12F712: Emergence.vst3

00007FFC2AF50000:00007FFC2B12F9FA: Emergence.vst3

00007FFC2AF50000:00007FFC2B14DF17: Emergence.vst3

00007FFC2AF50000:00007FFC2B15A0A9: Emergence.vst3

00007FFC79590000:00007FFC7959E858: USER32.dll

00007FFC79590000:00007FFC7959E299: USER32.dll

0000000003490000:00000000039A342A: FLEngine_x64.dll

0000000003490000:00000000039A3498: FLEngine_x64.dll

0000000003490000:00000000039A396A: FLEngine_x64.dll

0000000003490000:000000000413BEA4: FLEngine_x64.dll

00007FF6124E0000:00007FF6124E3A66: FL64.exe

00007FF6124E0000:00007FF6124E3DEB: FL64.exe

00007FF6124E0000:00007FF6124E50C6: FL64.exe

00007FFC7A090000:00007FFC7A0A7034: KERNEL32.DLL

00007FFC7AF50000:00007FFC7AFA2651: ntdll.dll

Hi,

Thanks for reporting this. I'm currently working towards a patch release for emergence with some fixes and minor improvements, I'll look into this one as well.

I did some quick tests in the latest version of FL, but everything seems to work fine on my machine so far, I'll need some more time to figure this out.


In the meantime you can also try the latest beta. I would be interested in seeing whether that has the same issues on your system or not.

I had a bit of a play, this might help. If a modulation already exists then double clicking clears it without the crash (also modulations can be added back to just those controls). A rough guess the crash is due to the app trying to remove an element from an array that is not there or maybe the array has not been  created correctly?

Oddly there appeared fairly random behaviours, I could remove the two modulations from stream 1 time and pitch and then add modulations only to stream 2 balance and stream 3 balance. It seemed to be set to only allowing 2 modulations at a time. I found a similar one where random 2 will allow any modulation destination but only 4 at a time.


I'll check out the beta, thanks Daniel

Tried the beta and the lfo issue is fixed. I did however have an instance just click and cut out. The buffer became full of what looks like a dc signal maybe.  In the attached screenshot you can see the buffer display is fully white and the signal out has maxed even though there is no noise to be heard, I'll see if I can reproduce it. Could be an fl studio thing, I've seen reaktor do something similar with feedback buffers,


One thing of note the lfo rates and stream rates feel like they are reversed, Normally I'd expect speed to increase by turning up the dials.

Hi!

Thanks for the feedback! Not sure what the dc/noise thing could be, If you know a reliable way to make that happen please let me know!

I also recently released version 0.3.2 with some bugfixes that might help with some of these issues.

One thing of note the lfo rates and stream rates feel like they are reversed, Normally I’d expect speed to increase by turning up the dials.

In the 1.0 beta you can select different units of measurement for time-based parameters (like seconds, Hz, quarter notes, etc.) If you set the lfo rate in seconds then you will see the speed decrease as you increase the knob. You can select a different timebase by clicking the little ‘T’ button next to the knob. (I guess Hz would indeed be a better default here)