type - 47 errors

[leon milo]

Hello,

I have started to get type - 47 errors "Can not save file. Try saving with a different name or disk..." Have tried repairing permissions, throwing away prefs., putting master files on different disks, etc. but continue to get this error. Is this a known problem to anyone?

Thanks for the help.

Leon.

D9 4.5.2 sys 10.3.9

[TheHopiWay]

I have the same issue on occasion. Renaming the file works fine for me every time and I'v encountered no problems with the saved files.
I've been told it's tied to a problem with the stealth modem adaptor I'm using as a serial port but as I only use MIDI for TC lock to my mixer I'm not concerned.

[leon milo]

Thanks for the reply. I have not had problems with the files either but have not been able to pin down the cause. I see that you are in System 10.3.8 and I have a suspicion that it might be related to somthing obscure in sys. 10.3.9

Best,
Leon.

[leon milo]

Just an addition:
Found the error codes page at apple. <http://docs.info.apple.com/article.html?artnum=9805>
and this for error -47: "-47 fBsyErr File is busy (delete); Section doing I/O"
L.

[BobK]

I've been getting this error a lot recently, and the files only have three mono audio tracks. I even get the error after doing something as simple as renaming markers.

Have not found a particular pattern - it doesn't happen all the time. Repairing permissions doesn't solve it, though that's what MOTU suggested when I first got this error last summer.

I recently ran Tech Tool Pro intermediate tests and found no problems. Also optimized the disk and did directory repair with TTP, and still got the errors afterward.

While the re-named files seem to be fine, it's a real pain to have to rename them every time I save. I save often while working, and this is a real nuisance.

<small>[ May 30, 2005, 10:15 PM: Message edited by: bobk ]</small>

[laurence]

i had this problem and found it related to using markers... ie; as my marker usage grew the error reared its ugly head... but as i started getting by without markers it also seemed the problem disappears... i also found having many markers and resizing the tracks view caused the system to beachball lots..in fact doing it during playback was quite unacceptable to DP ! hmmmph i've grown to love working without markers

[Weekendshooter]

I encounter this problem only when the project resides on an external drive and it seems to clear after bringing the project onto the internal drive.

Wierd...

[BobK]

Like Apollo, I've had this problem a lot (though not exclusively) when adding, moving, or renaming markers and then saving.

It's not an option for me to stop using markers - they're an essential tool. If this is realy related to markers, then MOTU should fix it fast.

[magicd]

Hello all!

I have been working with bobk to see if we can solve this problem. Bob sent me a file that reproduced the save problem and on my computer and a second machine at MOTU the file consistently showed as "read-only" in it's permissions (Get Info on the file to check or change permissions). When we changed the file permission to read/write, the error went away and we could modify and save the file with no problems. However, Bob tells me that on his computer the file permission shows up as read/write (!). I'm corresponding directly with Bob but I thought it would be useful to get feedback from others who have similar symptoms.

We don't think this problem has anything to do with markers. With the test file I was sent, any change to the file would cause the save error.

We do think this is a permissions related problem. When we changed permissions at our end, the problem went away and we found no other problems with the file.

Disk Utility (or other disk maintanance programs) would not see "read-only" as a problem for an application file, so there's no surprise that Disk Utility didn't solve the problem.

DP does not change file permissions. When you Save As in DP, you are creating a new version of the file. When DP creates a file, permissions are set by default to read/write.

We think it's unlikely that the permission problem is happening in DP. We think it's more likely that third party software or the OS is somehow changing the file permission. Obviously we'd like to find out exactly how this happens.

If you have a file that exhibits the -47 or -5000 error message, can you please check permissions on that file? If you see permissions (and there are three permissions to check - Owner, Group, and Other) set to read-only, does changing that to read/write then allow the file to be modified and saved? Does anybody else find that the file is already set to read/write? If so, please feel free to email that file to me (no audio data please) at magicd@motu.com

I'll post further as we get more specific info for you.

Thanks
Magic Dave

[BobK]

There's an interesting twist to the story:

I found one file which had permissions set to 'read only' for 'group' and 'other.' (This is not the file I sent to Magic D, but an earlier version, which I'd kept even after I had to save it with a different name.)

I changed the input assignment to an audio track in this file, chose 'Save', and got the error dialog box. I chose 'Cancel' instead of renaming the file. I then quit DP, and noticed that DP did NOT prompt me 'do you want to save changes?', as you'd expect.

When I launched DP again and opened the file, I was surprised to find that the changes HAD been saved. I repeated these steps to verify, and sure enough, it happened again.

I got the same results with the latest version of the file, which had read/write access for all.

I opened the file, deleted four empty MIDI tracks (this is an audio-only project) and got the type -47 error dialog box when I tried to save; but in fact it saved the file. After I clicked 'cancel', I noticed the 'Save' was grayed out in the File menu. I relaunched DP, and the change was still there.

So I'm getting the error box, even though DP is saving. Will see if this happens with other projects.

<small>[ June 03, 2005, 12:01 AM: Message edited by: bobk ]</small>

[BobK]

I seem to have found a solution.

I continued to get the same error prompt, even though DP was in fact saving the files.

I tried more diagnostics and found no problems (Tech Tool Pro 4 surface scan; Apple Hardware Test).

I reinstalled DP, but that didn't help.

Reluctantly, I decided to reinstall the OS, as Magic D suggested. So far, this appears to have cleared up the problem.

1. I did an 'Archive and Install' using the install CDs that came with my G5. I installed the OS on the same disk (the internal hard disk), which has only one partition. I checked the box 'Preserve Users and Settings.'

2. Then I ran Software Update twice to bring things up to date (10.3.9).

3. I downloaded and installed the MOTU PCI and MIDI drivers. I did NOT re-install DP.

4. After launching DP and realizing I had no plug-ins or MIDI devices, I quit DP and dragged the 'MOTU' folder from Previous System->Library->Audio->MIDI Devices to the same folder in the newly installed system. Same with the folder 'Library->Audio->Plug Ins'.

Then I opened a couple of versions of the file which had been giving me the errors. I made changes and saved - no problems. I'm confident that with the previous OS, I would have gotten the error by now.

Re-installing the OS is a pain, but if I continue to be save-error-free, it's worth it. I'm going to be doing a big project soon, and this gives me peace of mind.

I hope this helps.

[ricebean]

i found the problem to be the file was corrupted. to save i used the save a copy as dialog = replace, to save the file/song.

i made a new file template, made a copy of that, and use the copy to work from when i start a new song. problem all gone.

it happened to three of my file/songs before i figured it out.

[BobK]

I hadn't tried 'Save a copy as...' Sounds good, but if I kept getting corrupted files, I'd wonder why/how that happened and try to stop it!

Having re-installed the OS, I can now open files which previously gave me that save error, and I'm not getting the error. That suggests the problem was with my OS, not the files. Of course, your situation may be different.

I also noticed that with the old OS, the hard disk would chatter a few seconds before I got the error message. Now the saves happen much more quickly.

(sigh of relief...)

[dpdan]

Just the other day for the first time, I too had experienced this problem of not being able to save, except my error was ID= -43.

"An error occured while writing to the disk, the file blah blah blah was not saved."

Like the other posters here, I could only save by renaming the file blah.05 blah.06 blah.07 etc.

I decided to use "Save A Copy As", I also duplicated audio data and this new file worked fine.

I just now opend the older file that I could not save to, and now it works fine.
Weird!

dp4.52
G5 dual 2.0
3.5 gigs ram
OSX 10.3.8

no markers at all.

Hope this additional info helps
dpDan

<small>[ June 08, 2005, 07:28 PM: Message edited by: dpdan ]</small>