In addition to the hundreds of included patches, Keyscape offers the amazing versatility of being able to dramatically shape and morph these iconic sounds - something we Sweetwater sound tweakers appreciate. I don’t know if Brad will be able to use this information but I thought it was worth sharing.Custom Controls let you tweak to perfection I’m even using the thinned version of the samples.Īnd here is the strangest observation: if I open VIP as a VST inside Cantabile, hosting itself Keyscape… all my crackling issues disappear magically and time loads are back under 10% when playing the piano sound. Very frustrating and absolutely no reasons for that I/O wise: everything is loaded up in RAM. So back into Cantabile, I open up the Monitor Window and I see Time Loads of 200 or even 450% when I play Keyscape. I’ve tried every combination I could imagine of options in the Audio Engine until, and again pardon me for the constant comparison, I tried yet again this sound in VIP: as always for me, it is working flawlessly in this environment. They begin to start when I play four or five notes at the same time. Now I have very disturbing crackles and glitches with Keyscape, especially with the LA Custom C7 Piano sound.
Sorry for the noise, I did not see those posts at first. I see this is how other people solved it already. It did not solve the sound loading and I still have to use the change preset trick.īy reading other posts from 2 years ago. So I have updated all my Omnisphere and Keyscape products.
Now if restart Cantabile with the Test Set List, having Test 1 by default, Test 1 loads correctly.Īgain, no problem at all if the Set List is in Pre-Load just in case this helps: I can see in Windows Task Manager that when a song is KO, it does not take the usual amount of memory it should take (the Keyscape sounds being several hundreds of MB, it’s easy to spot when they are really loaded) Moving to Test 4 again => KO (same procedure)
Moving to Test 3 again => KO (same procedure)
Moving to Test 4 => KO (no sound, I have to enter Omnisphere’s GUI and double click on the patch to force loading) When I start Cantabile with the Test Set List, having Test 1 by default, Test 1 loads correctly. Test 4 is Omnisphere with a Keyscape patch Test 3 is Omnisphere with a Keyscape patch Test 2 is Omnisphere with a simple patch (not Keyscape) I have a Test set list (not in Pre-Load mode) with 3 songs: Test 1, Test 2, Test 3 and Test 4 It seems that the first time I load a song with an Omnisphere/Keyscape sound, it works. So Keyscape is not really usable for me with Cantabile unless I’m in Pre-Load mode. Now the better part: if I activate “Pre-Load” mode for the set list, everything loads fine in Cantabile! And of course, song switching is instant after that. I have not the issue with other Omnisphere libraries. I have tried changing the preset mode for Omnisphere but I had the same results.
Then it finally enters preview mode instantly. With Cantabile, most of the times, it never comes up… I have to double click on the plugin, which loads its GUI, and there, select again the sound (double click the already highlighted patch). Things get really messy if I take a heavy Keyscape sound such as the LA Custom C7 or the Wurlitzer 200A, it takes 2~3s to load in preview mode in VIP. If I take a very simple sample based patch in Omnisphere, again, it takes <1s to load in VIP and 3~4s in Cantabile. So obviously, it’s more about the plugin itself than the sample payload. This is the default piano sound of the TRITON which is a 16MB sample.
Loading the song in Cantabile takes 3s~4s I saved the same Triton patch as a bare song in Cantabile (with just routing from the main keyboard) and in a simple patch in VIP. So I compare songs loading in Cantabile vs in VIP. I’m on a fast SSD laptop with 16GB of RAM. So I was hinting on the TRITON VST thread that I encountered some issues.įor the context, I’m still transitioning from VIP as my host, taking advantage of the 1 month trial.