I have something weird. I got a new PC - it’s a i9, latest generation, 32G, should be more than plenty fast. Which it is according to LatencyMon. In Cantabile I get audio glitches in Keyscape. Even at buffersizes of 512. Both on a Focusrite and on a Steinberg audio card. And it’s only Keyscape. AND when I run Keyscape standalone, I can go as low as buffersize 32 (!) without audio glitches. It does glitch at buffersize 16 but I can live with that
So it seems related to the combination of Cantabile and Keyscape.
My previous PC never had that issue with Keyscape/Cantable - that was an i7, 3 generations older.
Anybody else have similar issues? @brad : how do w go about figuring out what is going on? Is there any logging I can do to see what’s up?
I know this was mentioned somewhere on the forum recently but sometimes faster/newer can be a problem. We once had a SQL server procedure that created a unique value based on timestamp as records were imported that got tripped up because a new server was so fast that two records in a row got the same timestamp down to the millisecond.
I’m assuming that your drive is a fast SSD? The large number of samples that Keyscape uses demand a fast drive. (Also did you check the settings within Keyscape? Not on my music PC at the moment, so I can’t remember the exact settings.)
Apart from the GPU setting that we discussed in another thread, then an obvious candidate is CPU throttling, so make sure that you are on the High Performance power plan (or similar settings).
@TorstenH ; yes I am on hi performance plan; all Windows settings tweaked for audio @Roland_Robertson: yes, fast SSD, yes played with the Keyscape settings - makes no difference @Torsten; yes, played with all Cantabile multiprocessor settings, makes no difference
I ran the performance profiler and it’s ridiculous - seems related to the damper pedal - when I release that, Keyscape goes through the roof.
Guess I’ll have to repurpose that machine for other duties c’se I am out of things to try.
I am getting suspicious…
New machines with faster processors seem to behave worse than older ones.
It is connected to some Intel new strategy to slow down devices to save energy and decrease produced heat?
Any idea from experienced programmers here?
My first thought on this is some sort of multi-core interaction causing both Cantabile and Keyscape to compete for CPU cores.
Try:
disabling Cantabile’s multi-core support (Options -> Audio Engine -> Number of Audio Threads -> 1 and see if that makes a difference).
playing with Cantabile’s thread affinity settings
disabling hyper-threading (generally a BIOS setting)
running the profiler (View -> Profiler) and check if the load spikes are actually occurring in the processing of the plugin and not somewhere in Cantabile.
Hi @brad - it’s certainly (indeed) a multi-core interaction causing both Cantabile and Keyscape to compete for CPU cores. Keyscape solo (running as app, not plugin) does fine and I get extremely low latencies.
Couple of things:
I ran the profiler - it’s Keyscape that runs over 100% - not Cantabile.
I played with Cantabile’s thread affinity - no difference.
I played with number of audio threads - no difference. BUT I did not go down as low as 1 - I will try that today.
I’ll try and disable hyperthreading.
I’ll ping back when I know more.
I also found something else that is strange, and I see it on both systems (my old one that works fine and the new one that doesn’t). Here’s the story:
I have a piano rack, with 8-ish different pianos, including 3 Keyscape instances. Those are on different midi channels.
Which piano is in use depends on a state - and the state enables/disables the midi channel used.
So really, when I play piano, I would expect only 1 Keyscape instance to use cpu. Because only 1 midi channel is active.
BUT - all 3 do!!! even though only 1 is really playing.
I noticed because on my misbehaving system, those 3 instances go RED.
I checked my well-behaving system, and I see the same there (be it that none of the Keyscapes get to the red line - but they all use CPU if I hit the keyboard, even though only one receives midi).
Instead of making MIDI channels active, maybe try to enable/disable the instances you need or do not need for each state. That should lower CPU usage.
Just a thought.
Just guessing, but I wonder if this is just a display quirk where all 3 instances are reporting load from a shared audio processing engine. If you compare the three instances in the profiler are they all burning time?
If you’re sure only one is synthesizing sound, but they’re all consuming load then I’d be getting in touch with Spectrasonics about it.
fwiw: I have seen multiple instance issues with this plugin before where the second instance doesn’t load sounds correctly if the first instance is unloaded at the same time (or something like that) so it wouldn’t surprise me if something isn’t quite right here.
@Jtoth : tx for that tip. When I disable plugin instances that are not supposed to produce sound it does save significant CPU! @brad : that said, I tried the following, all to no effect: tell Cantabile to use only 1 core, tell windows to use less cores (advanced boot option).
As far as I can see it’s only Keyscape that misbehaves. I have other instances (Kontakt, Arturia Piano V, various effects) running and those hardly consume CPU (which makes sense on such a fast system). I’m in touch with Keyscape but since I can only reproduce the issue in a cantabile rack they are blaming it on contabile (of course)
All this just confirms my decision to stay the h*** away from Spectrasonics plugins for live use. Eric Persing and the team seem to have no respect for PC resources at all - his stuff sounds super-sweet, but all his plugins are resource hogs…
OK, I did some more experimenting. It’s definitely Keyscape misbehaving, not Cantabile. All other plugins perform fine. Keyscape even misbehaves when there is only one instance, in one song (and no setlist loaded).
Did you try to play Keyscape instruments from Omnisphere interface? The Keyscape plug is a simplified version of the Omnisphere one, both sounds the same. Just a though.
- his stuff sounds super-sweet, but all his plugins are resource hogs…