I’m on Win 10, C4 Build 4309. I’ve been away from this PC for a few weeks, just booted it up today and did the Windows Updates.
This only happens on certain songs. And oddly, on 1 song it only happens on certain song states.
The other thing I noticed is that in Windows Explorer all my song files “Type” is “Cantabile3 Song File”. I could have sworn that after I moved from C3 to 4 this summer all those said C4 files.
Also, the files now open in C3, but the same songs have that same Preset error message. IIRC once you move to C4 4100+ those files shouldn’t open on C3.
I tried updating to the latest stable Build 4328, no change. I’m wondering if it’s related to the “Preset Model” options? I never changed any of those after moving to C4.
I have some big gigs starting this Friday, so any ideas are greatly appreciated.
I’ve tried re-saving them, etc. Of course if all else fails I will try to undo the windows update, I did create a restore point before the update. @brad if you have a chance can you shed some light on this? I’ll email my log file in a minute.
Tom
“preset version is not compatible with this software version” - I’m pretty sure that’s not a Cantabile error message so it’s probably coming from a plugin.
Did you update or revert any plugins?
You might be able to narrow this down by:
Go to Tools → Options → Diagnostics
Turn on Console Logger
Reproduce the error
While the error is still displayed, take a look in the separate console logger window and check the last half dozen lines - they’ll probably provide a hint as to what Cantabile was doing when the error occurred.
Also, it sounds like your Windows file associations have been messed up or maybe reverted. Try this:
Start Cantabile 4
Go to Tools menu → Options → Miscellaneous
In the File Associations section, click “Associate”.
That should map file types in Windows Explorer back to this version of Cantabile.
Thanks for the quick reply Brad!. I’ll give that a try.
I did update TH-U plugin, I can try reverting that. I also just noticed that I have a missing plugin (this is my backup rig) so I’ll install that as well. But FWIW neither of those plugins are used in the songs that have the error.
Thanks again!
Tom
I very much assume this is an issue of a specific plugin.
One thing I suspect: you may have used “entire plugin” state behavior or the “snapshots” preset model, then updated the plugin later to a new version. This means that Cantabile will try to load the snapshot into the plugin, with the plugin refusing to accept the snapshot, since it was created by a previous version of the plugin.
To fix this, you will either need to re-create the snapshots in the current version from scratch or revert the plugin to a previous version that accepts the shapshots, then save them using the plugin’s internal preset system, then update the plugin again, hoping it will load saved presets from a previous version (typically works).
But before you can do that, you’ll need to identify the guilty plugin - maybe you can use @brad’s suggestion with the logging feature or brute-force your way with the “remove half” approach illustrated below.
save the song under a new name (“test”)
remove half the plugins / racks, save under new name (“test 1a”), save another with the other half removed under “test 1b”
see which one of these the problem re-appears in
repeat / refine with the one with the problem (“test 2a / test 2b”) until you have identified the plugin that causes the issue
Thanks all, Brad was correct (as almost always!) in that it was a Windows error message. The culprit turned out to be SWAM Saxes, the console logger helped me locate the last plugins that were loading before the problem occurred. I updated the plugin and so far it seems that solved it.
Torsten, I always appreciate your input, you’re right in that the offending plugin was in fact using Entire Plugin Snapshot. I don’t know if I’d changed it if that would have solved the issue, quite possibly. But at least this saved me rebuilding the rack.
Now that I’m more aware of the potential issues with my Preset Model settings I may have to rebuild some racks. SWAM was sometimes a bit slow on state changes (and the console logger showed me the detail on that) so I need to dig into that. I think Clint had a post on that a while back.
Is there a recommended Preset Model that will reduce load times on instruments and amp modelers (non- sample based)? I have some layered horn and guitar songswith heavy plugin counts, that occasionally have certain song states that load too slow. Looks like Parameter Sets would be best to start with?
I’ve always used Rack and Song States and “Entire Bank” state behavior to save. And never changed any Preset Model from their default since C3 first came out years ago.
Again, thanks to all for the help!
Tom
