No changes during repeated saving to the same .pdf from .mscz.
MuseScore 1.3, WinXP 2013 edition.
Is this a known promblem? How can I help to fix this if I got it with every sheets?
MuseScore 1.3, WinXP 2013 edition.
Is this a known promblem? How can I help to fix this if I got it with every sheets?
Do you still have an unanswered question? Please log in first to post your question.
Comments
Compile a score and save it as PDF;
Edit score (for example, add notes) and save it as PDF.
Do you mean that the new PDF is exactly the same?
I did this, and I got two different PDF (I have not saved the changes to *. Mscz).
In reply to Tell me more: by Shoichi
no
In reply to No by Kolridg
Attach the PDF 1;
Attach the score changed.
Can I try on Vista (+ 1.3)
...
Maybe I find.
Save as PDF but by a different name (eg test/test1)
In reply to Then the usual request: by Shoichi
Do you mean that the new PDF is exactly the same?
I meant that there is no changes in the same PDF, not in new.
I have not saved the changes to *. Mscz
In any way.
Maybe I find.
Save as PDF but by a different name (eg test/test1)
I'm not so silly.
About attachment:
Re note wasn't saved to pdf during repeated saving.
In reply to Here you are. by Kolridg
is the result (1_0.mscz saved as PDF 1_0A)
In reply to This by Shoichi
I see.
In reply to Yours works. by Kolridg
If you need, in case of an emergency, you can attach the file and one of us can convert it.
But, I hope, will find a way to overcome the obstacles that sometimes the pc wreaks on our way
Maybe saving a copy of *. Mscz in a folder created for the purpose, and then saving as PDF.
If we do not find out other solutions consider "case closed"?
Good music.
In reply to Here you are. by Kolridg
You need to close your PDF viewer or MuseScore can't write to the PDF file.
In reply to You need to close your PDF by [DELETED] 5
Thanks for support gentlemen.
I have seen a weird bug on Windows on very rare occasions where files in certain folders don't appear to be updated if you re-save them. Some sort of caching bug, I guess. I've never tracked down what causes it exactly, but it always goes away after a while - suddenly, the update version of the file just appears. Workaround is to save under a different filename until Windows wakes up and realizes the file has changed.
In reply to I have seen a weird bug on by Marc Sabatella
Aha, that explains why I was getting the same behaviour whilst compiling my PDF version of Bach's Eight Little Preludes & Fugues.
It was taking 2 or three saves before the PDF would update - my solution was to delete the PDF in question before exporting it again.