iPad version Save function

When saving a preset which has already been given a name, the user must re-type the name every time the file is saved. If the app is closed without saving, the work is lost without warning.

Hi @dwcrook I don’t think this is a bug but an improvement required in that you should be able to overwrite a preset. We will integrate this into an up and coming update in Scaler 3.3

How can I update a preset after editing without entering the name? Here’s my scenario:

  • Add some chords to the Main track, etc.
  • Click on the Save icon to Save Preset, enter a name
  • Make some further changes
  • Click on the Save icon
  • Do not enter a name, just click Save
  • No changes are saved
  • Enter the name of the open preset or a new name
  • Changes are saved

Unless I am missing something it seems like the only way to save edits to an open preset is to re-enter the name of the preset again, which doesn’t make sense. Any advice would be appreciated.

Hi @EdZbflat See above. We are working on this now whilst also working on iPad <> Desktop interoperability. Coming in Scaler 3.3

I’m wondering the same thing, esp. for iPad. What, exactly is being ā€œsaved?ā€ MIDI?

Any relesease date, yet? Something that needs to be included (iPad) is a better way to get both MIDI and audio into a DAW, like Cubasis 3. Steinberg says the way to import MIDI to Cubasis 3 is to use Dropbox! I quit using Dropbox years ago, but reinstalled it, temporarily, to see if it works as a way to get MIDI into Cubasis 3. It doesn’t. Total failure, so I uninstalled Dropbox…again.

While Scaler 3.3 exposes the file system which allows some management of the files outside Scaler, there are still improvements that need to be made to allow managing files within Scaler. For the purpose of this post, I’ll focus on just one: the ability to overwrite files, When the user chooses to save a file, the current file name is populated into the save dialog, which is a big improvement. Then when the user proceeds to save, a warning is shown that the file exists and asks for verification that the existing file should be overwritten. That’s good. But if the user selects to overwrite, the existing file is not overwritten. Instead, the existing file is renamed and a new file is created. This happens every time the file is saved, creating an endless collection of file versions that the user may or may not want. The result is a cluttered file list. My suggestion would be give the user the option to truly overwrite the existing file without creating another file.

Hi @dwcrook thanks for the report. This is not the correct or intended functionality so we have lodged this to be addressed in a coming update. Hopefully this can be resolved soon so the ā€˜overwrite’ option does indeed overwrite the existing preset file as intended rather than creating a new file. Thanks again.