![]() “Background” idling (sequenced input only, ASIO-Guard, 21.3 ms) takes idle down to about 11% in Cubase, but system process load is about the same.CPU load with all instances taking live MIDI input (that is, all running in the lowlatency context, 5.7 ms latency), they consume about 20% / 14% CPU (according to Cubase / for the whole process according to Task Manager) when idling.An extra cumbersome mute button…?Īnyway, quick experiment with Cubase Pro 10.5 on i9 (14 core, all cores locked at 4 GHz), and 128 Kontakt 6 instances, each with Finckenstein Strings (High) Multi from Ark 1, suggests that it’s still working as I expect it to. If that’s not what other DAWs do, I can see why there could be issues - and I’d be wondering what the purpose of the feature is in that case. ![]() (Haven’t used pre 7, except way back in the 90’s.) That, incidentally, is how the Cubase “Disable Track” feature works, at least since a few major releases back. The plugins need to be properly stopped and unloaded, as if the tracks had been deleted from the project, and everything needs to be restored from the project file when enabling these tracks. Looooong overdue, IMHO, but at least, it’s been available for automation data since a few versions back.Īs for deactivated tracks, a host can’t just stop running plugin callbacks whenever it feels like it, so a “deactivate” feature isn’t as trivial as it may seem. Well, it’s been possible to paint, draw lines, scale, “warp” etc for a long time, but it was all discrete points until now - no structured curves with control points or anything.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |