jamesie said:
fremen said:
Although I don't have any issue on what the modifications does to my presets, I went back to 7.16. Too many of my presets are now above excessive CPU range, and I don't have time to alter all of them before my next gig, which is tomorrow. Cliff, are some CPU optimisations scheduled for next firmware ?
i had not time to install 7.17 (i`m on 7.16) - is the cpu load with 7.17 really that much more?
I think it is... When I updated to 7.16, with the bigger CPU consumption from the noise gate, only one of my presets was unusable, and all I had to do to be able to use it again was to turn off the gate (it was a clean patch so it wasn't a problem)
Now with 7.17, I tested half of the 40 or so presets I use live with my cover band, and 4/5 of them had this CPU warning thingy. Even replacing a Parametric EQ by a shunt and shutting off the noise gate wasn't enough one one of them. So I went back to 7.16. I will test 7.17 again after my next gig, right now I don't have the time to alter all my presets. I suppose that using mono low res instead of hi res in the cabinet will be enough. But I really hope for more CPU consumption improvements, like in some previous firmwares