-
General Error 48
So I searched the forums and a couple people asked this questions but in the last 5 years no one gave an answer.
Does anyone know what this error means or more importantly, how to fix it?
This error comes up with I try and render footage, any footage.
Thanks for any advice,
Will Keir
-
5 Replies
-
It may be a naming issue; try quitting FCP and restarting it.
I found this error reference:
“error -48 dupFNErr: duplicate filename (rename)”If nothing else works, try creating a different area for FCP to place its renders, so that its NOT possibly trying to write a file using an existing name. Render filenames are made by FCP – sometimes it tries to use an existing name.
Neil.
-
Interesting answer Neil. All that anyone seems to know for sure about it is that it points to corruption in the project file, render file or media.
Try a previous autosaved version of the project to see if the issue persists. Clear the existing render files for the sequence that will not render, and see if that clears it. Also, you could try rendering sections of the timeline to see if you can isolate the dodgy media file, but it sounds likely your issue is with the project or render files.
Hope that helps a bit – I have no idea why there is no Apple support letting us know what the error number means, but I guess it is OSX related, rather than FCP specific – maybe. Who knows…
Ben
Editec Broadcast Editing Ltd
EVS & FCP specialists for live broadcast.
OB Server 1 HD – Mobile FCP editing done right.
https://www.editecuk.com/OBServer2.html -
for anyone with error 48 , after many hour of shouting at the computer error 48 in my case applies to Final Cut Pro and .SWF files. Quicktime seem to change what file types it supports from time to time and the error reading a file within a sequnce causes an erroe 48 this is not generally a bad file but one that is no longer readable format and need removing and replacing. As pre the update it worked and post update is doesn’t — go figure.
-
Hi,
Indeed the General error 48 in my case was also due to a .swf file that final cut pro could no longer read. This happened after I updated my applications and I think quicktime was in the updates.
After my updates, Final cut pro had no problem reading the .swf files that I had already placed in the time line, (before the updates), as long as I did not try to change any part of the time line with the files. When I did try to do somehting with the .swf files, the general error 48 would appear and my timeline was gone for good.
As Ben Holmes said in his post, the best thing is to look in your autosave vault to find the last one that doesn’t give a general error when opening it and then erase the .swf files. If you’re lucky close the project without saving it as soon as you have the general error sign, when you reopen your project you should be able to read your time line normally, and you can get rid of the swf files.
Hope this helps!
Catherine -
Hey Guys! I just came across what might be the solution.
I ran into the same thing, started rendering clip after clip, and came across a “culprit”
It was a jpg – opened in Photoshop and discovered that this image had a pixel size of larger than 4000 pixels.I was on a project before where I learned that FCP can’t really play with images over 4K px. So I bumped it down and was good on one image (tried with the *next one* in the time line – had some difficulty on that one (FCP would only render flat GREEN?!) — but fortunately in my case, both images were of the same event so I nixed my trouble-maker and just massaged the lengths of the others and kept truckin’)
Entire time line is now rendered.
Motivation is what gets you started. Habit is what keeps you going.
Reply to this Discussion! Login or Sign Up