So it’s great that Cub3 has the 3.4 update and Ableton Link is now a feature - I know nothing about it, but was impressed by ‘Monsignor Dom’s’ demonstration (!) video. I am believing you can use another device as a driven synchronised instrument?
Anyway the issue immediately I looked at the ‘system resources’ meters, is they start at 80% when nothing is happening and go up from there, for the DSP. The CPU meter, sits down at 5% to 10%.
The song is like a template thing for me - it’s got 40 iOS/iPadOS Audio Units loaded inside, but all I was doing was tinkering with the built-in classical piano sounds. That, made me notice the ludicrous state of the DSP meter.
So I knocked off the setting for ‘multi-core’, and it seemed to be the case, with multi-core on, (iPad Pro 12.9 2nd gen) the DSP did drop slightly lower, than with single-core set.
Now it used to be this particular song, with multi-core set to OFF ie single core only, hovered around 60% on idle, and went up from there - from memory. When it hit 100% it crackled, and marshmellow said make it be single core and that stops that. He was right.
But now in 3.4, despite hitting 100% (obviously - it starts at 83% or so just idling), bumping into 100% does NOT make crackling happen!
Conclusion - based on the tiny amount of info and knowledge I have - is that the DSP meter at least, is wrongly ‘calibrated’. IE it’s not idling at 83% at all, and it’s not smoothly hitting 100% and staying there, yet not uttering a single crackle. It’s much more believable, the real DSP level is about 60%, just like before Cub3 version 3.4 got installed by me two hours ago.
And the CPU not moving at all, that too, is exacerbated compared to before.
Ideas - other people noticing this?
Thanks, take care, and I will hit it a bit harder now I know it doesn’t crackle at a 100% read-out.
ian aka richard getts.