Hello,
EDIT 3 : problem is resolved by sugar bytes
EDIT2 : I found solution to my problem, it's in the title : if I activate midi out global AND per preset together, DAW crash at next set loading
(maybe it can help some users experiencing crashes)
I noticed that 8.4b3 always crash when loading a set containing sugar bytes turnado 1.5 (latest - bought some days ago).
I am able to save a set with it (but LIve always crash when I try to load the set previously saved).
I tested with a set containing only a wav file and this plugin -> problem always occurs.
Configuration:
Windows 7x64
Core i7 / 6GB RAM
turnado 1.5
Edirol ua-101 soundcard
Midi controllers : APC40, APC20, KOrg Padkontrol, edirol PCR-800
I use native kontrol utilities to drive APC40 and PadKontrol (no problem with it)
Does anyone have this problem, plz ?
thx
EDIT : same problem occurs with Live 8.2.3 (stable) -> crash report will be sent in some minutes
Resolved - Turnado crashes Live
Resolved - Turnado crashes Live
Last edited by BioMech on Sun Aug 05, 2012 7:20 pm, edited 5 times in total.
Windows 11 - Core i7 13700K - Focusrite Clarett+ 8 pre - Ableton Push 2 - Roli seaboard rise - Ni komplete kontrol S61 - Akai APC40 - Akai APC20
Re: Live crash when loading a set containing sugar bytes turnado
I tested it with FL studio too, it seems to be a problem with turnado 1.5 because FL studio crash in the same way than Live.
Windows 11 - Core i7 13700K - Focusrite Clarett+ 8 pre - Ableton Push 2 - Roli seaboard rise - Ni komplete kontrol S61 - Akai APC40 - Akai APC20
Re: Resolved - Turnado: crash (not a Live problem)
For information, Sugar bytes has fixed this bug -> congratulation to sugar bytes team for quick support and bugfix!
Windows 11 - Core i7 13700K - Focusrite Clarett+ 8 pre - Ableton Push 2 - Roli seaboard rise - Ni komplete kontrol S61 - Akai APC40 - Akai APC20
Re: Resolved - Turnado crashes Live
Hi Biomech,
Thanks for confirming the fix and for sending in the reports. Going to lock this thread since the problem is resolved.
Best,
Mads
Thanks for confirming the fix and for sending in the reports. Going to lock this thread since the problem is resolved.
Best,
Mads