reproducible bugs with 5.2
Posted: Mon Apr 24, 2006 7:24 pm
After extensive rehearsing of a new live show, i have come across these issues with 5.2
1. I have a large set (>500 clips) that will crash Live every time i open 5.2
--> open 5.2 --> open Set --> Live Crashes,
If I do this:
--> open 5.2 --> open a different set --> then open the large set, live does NOT crash. I can open the set in 5.0.3 first time without crashing.
2. Program Change numbers are still off by 1.
If i make a MIDI clip to change a VSTi program. eg Prog 10 Bank 10 Patch 10.
Then I change the program on the vsti.
Then i trigger the midi clip, the vsti gets set to Prog 10 Bank 10 Patch 9
The Live prog #s are mapped incorrectly to the VSTi Prog #s.
I thought i read someone had reported this before in the Beta stage and i thought it was fixed.
3. When Morping between some ensembles in Reaktor5, my CPU usage shoots up to 200%
CPU is fine if i do not morph.
anyone else got any reproducible bugs to add to this list?
1. I have a large set (>500 clips) that will crash Live every time i open 5.2
--> open 5.2 --> open Set --> Live Crashes,
If I do this:
--> open 5.2 --> open a different set --> then open the large set, live does NOT crash. I can open the set in 5.0.3 first time without crashing.
2. Program Change numbers are still off by 1.
If i make a MIDI clip to change a VSTi program. eg Prog 10 Bank 10 Patch 10.
Then I change the program on the vsti.
Then i trigger the midi clip, the vsti gets set to Prog 10 Bank 10 Patch 9
The Live prog #s are mapped incorrectly to the VSTi Prog #s.
I thought i read someone had reported this before in the Beta stage and i thought it was fixed.
3. When Morping between some ensembles in Reaktor5, my CPU usage shoots up to 200%
CPU is fine if i do not morph.
anyone else got any reproducible bugs to add to this list?