Hi! Thanks for the feedback!
The directory structure is defined by the VST3 format. In theory it could contain other binaries (like a 32-bit version of the plugin), custom icons etc…
Since my plugin only has a single .vst3 file within the directory structure this is not really important. You could copy the whole directory or just the actual .vst3 file, it should work either way
Hi!
Thanks for reporting
I have a few questions that could help me figure this out:
The live crash dump could also be useful (even multiple ones if you had multiple crashes). Could you upload it to some file sharing service and send me the link to this email: 2l1hqq773@mozmail.com
Thanks
hi!
running 0.31...
to trigger a crash, when i first tried emergence, i think the problem was on both on my systems, it crasht (crashed?...) quite easily.
i shall try to make a more step by step approach. but it seems perhaps, that when the UI is open, the problem is bigger, and it suddenly looses the buffer, the granulator/engine of Emergence seems to stop.
emergence i had my eye on, as certified granular addict, grainstreams! wow! (well i have a load of granular synths/effects, or a load, well enough to cover all ground, and of course, the Crusher-X....)
i shall upload the crash dumps, i am at this moment not in my studio, have only my laptop (a kind of second, but smaller studio...), now, and i am sick, as half the people in my country is now, or has been sick... the well known...
so it will take some time, but if i have the energy i shall also put 0.31 on my laptop, 0.3 is on my laptop, and see if it genereates crash dumps, no live 11 suite on my laptop yet.. but other DAW's...
i wanted to report this earlier, but well, so much to do, but i am now 2 digital collabs, and one uses Emergence, it acts up more on my studio desktop, than the one i do the collab with. so... (quite new systems, by the way).
well enough, or too much info.
i will 'troubleshoot', perhaps that is the only thing i can do now, i must troubleshoot for another developer. perhaps i can give more info, and i have file sharing service so...
i repeat; great product! a contribution will be done, in cash...., or digitial cash... (which cash isn't digital nowadays...), i also postponed that because of the problems, but this is a great granular, i will support it.
when i am sick or tired, i write too much, and this is public i don't mind... my reputation is already established, haha..
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)
Maybe your graphics card does not support the OpenGL 3.3 version required by the plugin.
You can check by running gpu-z: https://www.techpowerup.com/download/techpowerup-gpu-z/
You can also try updating your graphics driver
