if Kirnu Cream Swing value was changed during playback MuLab crashes
this could be occour during playback of a Cream sequence or manualy changed by user
only MUX instruments crashes if Swing value is not 0 - no problems with other VST instruments!
Kirnu Cream v1.0.6 (32 bit)
MuLab 5.1.5 (32 bit)
Windows 8 (64 bit)
RAM 4 GB
Intel Core 2 Duo 8400
Solved: MuLab 5.1.5 crashes if Kirnu Cream Swing value was changed during playback
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
The next MuLab version has protection against VSTs that send events that are outside the valid time range, which is not allowed iirc. Which is the case when Kirnu uses swing. I've reported this to Kirnu.
-
- KVRist
- Topic Starter
- 332 posts since 26 Jul, 2012
thanks, solved in MuLab 5.2.6mutools wrote:The next MuLab version has protection against VSTs that send events that are outside the valid time range, which is not allowed iirc. Which is the case when Kirnu uses swing. I've reported this to Kirnu.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Note: There is an update of Kirnu coming as well which fixes the issue. It's recommended to install that update too because the protection in MuLab is simply limiting events that are in an invalid time range, which could eventually lead to unexpected artifacts (sound-wise, but no crashes) because the timing of the invalid events is changed so they're inside the valid range. The issue should be handled at the source i.e. inside Kirnu.