Hi Christopher,
You are right about the corruption happening when you try to transfer
the file to another computer or drive. This can happen whenever the
# sign appears in a file name for whatever reason (most often, as you
have discovered, when you are dealing with a long file name but this
can happen too when one deliberately uses the # sign when naming a
file) It has to do with the rename command of the app and the way a
longer file name will be handled. In trying to rename a file with a
filename that is too long, it will take the front of the filename you
gave it, add the hex which is actually a converted representation of
the files inode number (it's "address" if you will in the file
system) and then the extension.
I only know the basics here, but I have a hunch this is a leftover
from the OS 9 days where a file could only have 31 characters in the
name. If an app is still using the old "rules" for keeping a
filename to 31 characters, you will see these hex names coming up as
it tries to cope with the long file name. Just out of curiosity,
does your corrupted file have 31 characters in it? (including the
file extension?)
I haven't had this happen with current OS X apps but since Appleworks
is older and hasn't been updated for OS X, I could see why it would
be a problem.
My rule of thumb is:
Try to keep file names short when naming files in apps that seem to
change to the hex name with longer file names (now we perhaps know
which programs are still getting caught with their shorts down huh?)
Don't use the # sign when naming a file (I used to do this to keep
track of file versions in OS 9 i.e. xyzproject#1...on long projects
I'll do a save as occasionally so if something disastrous happens, I
can go back to a previous version and not lose all my work... I now
use a (-) instead i.e. xyzproject-3.mus)
If you see the hex file name at any point don't try to copy it to
another machine.
If you see a suggested hex name come up when you are doing a Save As
or any other action that will allow you to rename the file, change
the name before saving... preferably to something shorter.
BTW... have you ever experienced a kernel panic during/after trying
to copy one of these files with the # sign? That can happen too.
Hope this helps.
-K
Darcy et al,
I'm starting to see that there might be a connection between the
corrupted filename (only ever starting from the 20th character!)
and having edited the filename from the desktop, or possibly
transferring the file using either an Ethernet protocol (I have a
wireless network to my laptop) or copying it to a thumb drive.
Any of those situations apply to your funny filenames? At least two
of the three apply to all of my corrupted files, in Finale and in
AppleWorks.
Christopher
On Jun 26, 2007, at 12:41 AM, Darcy James Argue wrote:
Hi Chris,
I have only ever seen this when using FinaleScript to batch
convert old files to the latest version. I've never seen it during
normal Finale use, or in any other OS X app.
Cheers,
- Darcy
-----
[EMAIL PROTECTED]
Brooklyn, NY
On 25 Jun 2007, at 8:42 PM, Christopher Smith wrote:
More update, and I need some info from Mac users.
Sometimes in the file save dialogue box, the filename does not
show up correctly. The last few characters could be replaced by
what looks like hexadecimal (that is, "#198AF75" without the
quotes, but always starting with the #). This happens in Finale
from time to time, but also AppleWorks. So it doesn't appear to
be exclusively a Finale bug, and may very well be related to the OS.
Apparently the bug is related to whether or not the funny hex-
looking name shows up when saving an audio file. If the suggested
filename shows up the same as the .mus file (but with .mp3
extension), then all is well. If the last few characters (past
the 20th) show up as hex, then the .mus file WILL BE OVERWRITTEN
by the audio file, which will have the wrong extension (.mus
instead of .mp3).
Does anyone have any experience with hexadecimal code replacing
parts of filenames on Mac OSX? I am on 10.4.9, but I have seen it
in all versions of OSX. It never caused any problems before, and
only ever showed up as display in the File Save dialogue box (the
actual file was named correctly).
We are trying to track this problem down. Any info you have might
be helpful, also, if you have ever found this bug, can you
communicate it to MakeMusic with the file attached?
Thanks all.
Christopher
On Jun 22, 2007, at 4:35 PM, Christopher Smith wrote:
Update on my bug.
Tech support was able to duplicate the problem with my file.
Apparently it had gotten corrupted, and since I was clearing out
the music and using it as the blank for the next tune in the
project, all the files were inheriting the corruption.
This is what Scott at tech support had to say. (my quote starts
off the passage.)
***************************
"I created a template with the Setup Wizard in 2007c. I entered
some
music, completed the project, then saved it under a different
name. I
took the file, erased the contents, changed the title and other
things, and created this file."
The above process can cause numerous issues. This will
eventually break a file and cause it to be corrupted
(snip)
I would recommend copying and pasting this into a new document
as this file may be corrupted. Pasting this into a new document
may clear out whatever corruption is in there.
I tried one other method in which I opened it on Windows and
Exported as an XML file to be imported on the MAC side of my
computer. I saved this as TEST. I then saved as an Audio file
and it worked. So - it seems as though Exporting the XML file
cleared out some corruption (which is what I was expecting). I
have attached that file for you. Things like Staff Styles, etc
did not come across but you should be able to add those back in
if you need. Can you try this file and see if this works for you?
**************************
The XML-laundered file was indeed clean, though some items did
not come through properly. But I was able to achieve the same
result by copying the contents to a clip file and inserting it
before the first measure, then deleting the original measures. I
don't know why my files seem to get corrupted more than anyone
else's. I don't often clear old files and use them as templates,
but apparently that practice is "unsafe computing." I don't know
why.
Christopher
On Jun 20, 2007, at 6:58 AM, Christopher Smith wrote:
Hi, this seems to be a rather severe bug that almost got me bad.
In FinMac2007c, I create a score using the Setup Wizard,
entering notes and saving as I go.
From the File menu I select Save Special>Save as Audio File,
then I hit MP3 and navigate to the same folder as the file is in.
Sometimes the file name shows what looks like hexadecimal
instead of the filename after the 20th character, but I think
this is a Mac issue, not Finale's, as it happens in AppleWorks,
too. The important thing here is; the suggested filename ends
with .mp3 in the dialogue box, which is correct.
But, when I hit Save, the file gets saved with the
extension .mus instead of mp3, which not only causes it not to
open when I double click on it, but it OVERWRITES the .mus file!
I tried to open my lost Finale file from Recent Files, and got
an error message -12 (whatever that means, probably missing
alias.) The .mus file is not accidentally hidden, it is
actually overwritten with the misnamed audio file.
I can salvage the .mp3 by renaming the extension, and
fortunately I was able to recover the .mus file from my Backups
folder (which I have wisely decided to use!)
But this is a disaster waiting to happen. Be warned. Rename
your audio files to be different from your score.
Can anyone duplicate this? It happens to me quite consistently.
Christopher
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
