Hi,
I just upgraded my Scaler to 3.2 and can no longer load and save state in stand alone scaler. The menu option to load/save state seems to be gone. I can load and save presets, but not state. Did this change?
TBH - I’m not really sure what the difference is supposed to be.
Can someone please clarify?
Thanks!
Hi @outatune, thanks for your post.
As you’ve noticed, saving/loading state files is no longer supported in the Scaler 3.2 standalone app. This was noted in the Scaler 3.2.0 changelog, though it’s completely understandable if you didn’t catch that note.
There’s practically no difference, which is why standalone state file support was discontinued.
If you’d like to preserve states from versions prior to 3.2, the recommended workflow is to roll back to Scaler 3.1.3, save your states as presets, then reinstall 3.2. We can provide a 3.1.3 installer - just submit a support ticket or DM me here on the forum, and we’ll send it over. Cheers.
Thanks Steven! I missed the changelog so appreciate the link.
I was able to rename my old saved states to .s3p (added .s3p) and could then load them into Scaler 3.2. This seems to be working fine, but let me know if you think it could cause issues down the road and I’ll go back a version and save them as presets.
Cheers!
PS - love the new scenes feature.. 
I encountered the same problem. I rolled back to a version before 3.2, individually loaded the states and exported them as presets, then reinstalled the latest version of Scaler. Everything works now, I didn’t lose any work. But I had to waste hours of my time figuring out the problem, downloading huge Scaler installation files for older and latest versions, then individually loading and converting dozens of save files, just to convert to a new format that’s practically no different.
It would have been much more user friendly if 1) the load/import states menu option was kept in new versions of Scaler as a legacy option, 2) more advance notice was given concerning the plans to discontinue this option, perhaps within the software 3) a file conversion tool was provided so users didn’t have to rollback to a previous version to convert save files, then reinstall the latest version, and/or 4) the Scaler team decided early upon the one best method to save work and stuck to it.
I can’t remember any other software I’ve used quietly discontinuing a file saving format in between major versions and then giving users no way to convert their old files on the same device within the same software installation, forcing them to rollback, convert, and reinstall.
Welcome to the community @thehonorableryu
I totally agree with your sentiments and wanted to apologise on behalf of the team.
To be transparent, we didn’t think anyone was using ‘State’. It was a legacy thing from Scaler 2 and shouldn’t have been there from the start so we just assumed no one was saving states. There have been very few reports of other users encountering the same frustrations that you have so agreed, it’s a little presumptuous on our behalf and therefore not considerate. Sorry!
Thanks Davide, I appreciate the transparency.
Yeah, I mainly use Scaler as a “notebook” to quickly record and explore chord progressions. My standard routine is to open Scaler in standalone mode and move through several different states (now sessions or presets) within one open instance of Scaler.
Hence from earlier versions of Scaler I likely relied more on saving states, loading states, and resetting to default states to move between sessions compared to other users that typically open Scaler in their DAW where one specific Scaler state or preset is tied to a track that loads in the DAW project. Thus I naturally thought states were the intended way to save and open Scaler projects. When presets were introduced I figured that presets saved a more specific subset of information than the whole of my Scaler workspace like I was used to states doing (because why would there be two different names or methods to save practically the same thing). Similar to how a Photoshop PSD file saves more of your workspace compared to exporting to a JPG, PNG, or PDF, or how in UVI Falcon a “Program” (.uvip) is more broad than other preset types associated with their soundware. So the first time I opened Scaler 3.2 it took me some time to even realize that states and presets covered the same bases and that states had been discontinued.
Thanks again for the explanation. I enjoy using Scaler and your response makes me more confident recommending Scaler to others.