I always disable WiFi when I'm producing too! I have Focusrite Clarett 4Pre USB (Type-C) - the same interface I was using without issue on ABL10.Īlso, when I look at performance in TaskManager, it's never above 8%, and all the cores look mostly idle, save one or two showing maybe 10 - 15%. I have all power management disabled too, ultra performance, no link state power management, no USB selective suspend, no system sleep states, etc. Ableton and Push2 display process eating up most of the CPU, and nothing else, really, some Wave service, but was running before with AB10. When I look in TaskManager, there's nothing out of the ordinary. I have the top of the line Dell XPS 17, with 8 cores, 32GB extremely fast RAM, 2TB NVMe, etc., and I'm also a 20 year Windows software developer, who eliminates all extra services, Windows Defender, Firewalls, update, etc., and religiously check that no mystery services etc., are spiking in my TaskManager details.īut, since updating to 11, with only two tracks, and a few effects, I am getting dropouts?! I've been fighting similar issues since updating. Sometimes what seems like a good idea doesn't survive in the field! We released an update to our UI and the feedback is that it's less user friendly than it used to be. I've just had to do something similar at work. Perhaps there is another way that can be used to communicate what the CPU meter is doing now? As you say the actual peaks don't matter that much unless there's audio drop outs, but it's fairly clear that's not how users are seeing it. Whilst the new approach is functioning as intending, it's only causing concern and confusion amongst a fair number of users. Whilst I understand what the new CPU functionality does, the sheer number of reports by confused users should be a red flag to the team. Jur - I'm not sure if it's a live discussion amongst the product managers and the devs, but if it's not it's worth raising as an issue with the appropriate person(s).
If you find that L11 performs worse than L10 with the same set, then this is wrong, and in this case we need to nail it down. These CPU spikes when e.g loading a device are also happening in previous Live versions, but the "old" cpu meter just doesn't show them.Īs long as you're not getting audio dropouts too then everything's fine. As said, the new CPU meter now also displays peaks.
0 kommentar(er)
