Reset the positions of all elements
I'm opening some 2.0 files in 3.0 and I get a Reset dialog. Can I just make my selection as a default, or will I have to choose every time I open a 2.0 file in 3.0? When I reset the position and go to save, I have to use the Save dialog and search for a place to save it. If I can choose a default, I'll be able to skip these additional tasks.
Comments
You can't set a default.
A score opened from 2.0 is treated as an import, so as to not by default overwrite the existing score. As once saved in 3.x it can't be opened by 2.x anymore.
In reply to You can't set a default. A… by jeetee
Good idea.
See #301600: Option to disable the pop-up "Reset the positions of all elements?" , which is in 3.5
In reply to See #301600: Option to… by Jojo-Schmitz
I've installed 3.4.2 on Linux using AppImage. I don't know if I can install 3.5, but I might find that to be useful in converting all my old 2.0 files.
In reply to I've installed 3.4.2 on… by Rockhoven
You sure can, same procedure as for the 3.4.2 AppImage
It is an Alpha version though, and does have known bugs, and most probably yet unknown ones too
In reply to You sure can by Jojo-Schmitz
I might as well wait. It's not an A1 priority now. When will that be out and available in an AppImage file?
In reply to I might as well wait. It's… by Rockhoven
When it is ready ;-) but then at the same time as the Windows and macOS version.
Next step is Beta, maybe more than one, then a release candidate, then the release.
In reply to When it is ready ;-) but… by Jojo-Schmitz
I might be able to help test the Beta.
I'm getting that reset notice on some old files. I choose Yes and save, but when I reopen the file, it gives me the reset notice again.
In reply to I'm getting that reset… by Rockhoven
Did you overwrite the file after saving? If not, the original is left untouched and indeed will be re-imported when opening that one instead of the newly saved version.
In reply to Did you overwrite the file… by jeetee
Yes, it's overwritten. It asked if I wanted to replace the existing file.
In reply to Yes, it's overwritten. It… by Rockhoven
Bad plan IMHO, better save under a different name or on a different folder
In reply to Yes, it's overwritten. It… by Rockhoven
Use menu item: File -> Score Properties... to verify the file's parent (MuseScore version).
In reply to Use menu item: File -> Score… by Jm6stringer
If it is overwritten, then it should indeed be in the new format. Thus the import dialog should not be showing up at all and saving it should work without a "Save As" effect 2nd time around.
If you can find steps to reproduce such behavior, please share them.
In reply to If it is overwritten, then… by jeetee
I'm familiar with overwrite for most programs. MS Word simply overwrites the file. Audacity does not. The file should be saved with a new name or in another folder. Of course, that might change in a future edition of Audacity. This program also should meet regular standards for overwriting.
In reply to I'm familiar with overwrite… by Rockhoven
And it does for me and at least a few thousand other users..
So again, if you can give us steps to reproduce the wrong behavior, please share them.
In reply to I'm getting that reset… by Rockhoven
Almost certainly, you aren't opening the newly saved file, but instead, you are simply reopening the old file. You would need to explicitly overwrite the old file when saving - and confirm you really want to, when MuseScore asks - in order for this not to be so. You say you did, but my guess is you actually had another copy of the file and that is what you actually opened - you overwrite a different file.
If you believe you have a file saved with MuseScore 3 that still asks you to reset, check the modified date on the file to see if you really truly just saved it today., If you still think this is the right file, and opening this exact file (check the date on it while opening it) gives you the dialog - please attach the file so we can check.
In reply to Almost certainly, you aren't… by Marc Sabatella
Linux was not registering the name of the file correctly. It was using some file name that it remembered and not the file name that I was working with at the moment. So, I was overwriting to the same file repeatedly. When I saw that, I had to stop and rewrite the file name into the field. Now it's solved. Most of my problems are due to this Mint Cinnamon program that I have. I don't recommend it. It's extremely clunky compared to Windows or Mint 12 or 13. I'm going to have to reinstall my OS sometime.
In reply to Linux was not registering… by Rockhoven
If the filename looked like sczr67104.mscz, not that's something your OS is making up, that's the type of filename MuseScore gives to its autosave files. Normally you'd never see that name anywhere, but it can appear if there is a crash and you restart MuseScore and restore the last session and look at the filename before you get around to saving again.
In reply to If the filename looked like… by Marc Sabatella
Nah. It's a problem with my OS remembering a previous file name. I just didn't notice it. Now that I saw it, I can save and it opens OK. I think. Let's see what happens tomorrow.
In reply to Nah. It's a problem with my… by Rockhoven
OS's don't remember or not remember filenmames, but the file dialog within MuseScore does indeed remember the name of the file and folder you loaded and offer it as the suggestion when using Save As. It seems you may be confused about some aspect of what is going on here, but I absolutely guarantee neither MuseScore nor your OS are doing anything but perfectly ordinary file management. Bugs like that wouldn't go unnoticed, they'd have been fixed long before a program was ever released. But all of us users - including me - sometimes make careless errors and get confused.