After QT7.4, AE error-you do not have permissions to open this file (-54)
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Immediately after installing the QT 7.4 update, I have been unable to render (anything) in After Effects.
I get an error: After Effects error: opening movie - you do not have permissions to open this file (-54)
(44::53)
I have repaired permissions, downloaded the Full QT 7.4 installer, reinstalled, repaired permissions again and still the same problem. Something has changed in QT that has made AE incompatible.
Apple, please fix or offer some assistance on how to fix.
The AE forums are also beginning to fill with everyone having this same issue after an update to QT 7.4
My work has come to a halt. How do I fix this?
I can't find any info on reverting back to QT 10.3.1
15 replies
Sign in or join Beachball Help to reply.
- 0
Baby-Boomer-USofA ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
"Apple, please fix or offer some assistance on how to fix."
Apple does not read these postings. These are
user to user forums whereas everyday folks post questions & offer help to each other."How do I fix this?"
Check out Klaus1 possible solution in the following thread:
http://discussions.apple.com/thread.jspa?threadID=1343184&tstart=0
"I can't find any info on reverting back to QT 10.3.1"
You really mean
7.3.1 right? 😉
Do an archive and install of your OS from the OS disc. Stop at the QT upgrade you need.http://docs.info.apple.com/article.html?artnum=301270 Scroll down to
"Archive and Install”
- 0
YO ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I work at TV station too. And was in shock that it stopped my renders. Our final product is in HD, and it's takes forever for renders. Apple please help, we assume that these updates will work with major programs, such as After Effects.
- 0
Navarro Parker - ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Yes, this is a big issue over on the Adobe boards too.
http://www.adobeforums.com/webx/.3c05d55d/[email protected]@
There was a previous post here about this issue here, but Apple seemingly has deleted it!
- 0
Navarro Parker - ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
The quickest workaround is to render an image sequence out of AE, then import into Quicktime Player Pro and export as a QT movie.
- 0
ijobes ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Im having the same problem too, this is abysmal.....
- 0
Doug Stringham ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Add me to the list of those who are suffering from this incompatibility.
Bug verified on 4 different machines all running AE CS3 8.0.1
2 PPC 2.5Ghz Quad-Cores with 4GB RAM and running 10.4.11
1 Intel 8-core 3Ghz with 8GB RAM and running 10.4.11
1 Intel 8-core 3Ghz with 8GB RAM and running 10.5.1 - 0
kiluridols ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
It seems that Apple has deleted (again) one part of this discussion...
Whatever, the problem isn't solved at all.
OK...
I assume there is a HUGE problem with this QT update seeing the tons of post around the web.
This is certainly a permission problem again.
Hey Apple, wake up!
Not only AE rendering is dead with this update (see also the Adobe forums) but also many video softwares plus many other nonsense issues like in this thread:
http://discussions.apple.com/thread.jspa?threadID=1295478&tstart=0
Also you have so many issues in QT itself like the open image sequence which is totally out of control! And more, the "lost" or "sleepy inactivity" of many codecs.
Apple made a piece of crap with this one...
Hope a quick update is in the pipes. - 0
dlefebvre ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Another one bites the render dust...
I'm running AE CS3 8.0.1 on a PPC 2.5Ghz Quad-Cores with 4GB RAM and running 10.5.1
I'll have to borrow a computer to finish my project because I'm not running into the trouble of reinstalling stuff to get a previous QT version. If there was only a simple way to just revert Quicktime. The last few updates of Quicktime were problematic. It's nice to upgrade to support new features on Apple products and softwares but not at the price of making professional third party softwares useless...
- 0
jsoem ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thank God for Time Machine! It took me almost all of my night, but I was able to reconfigure my machine so that it would run the way it was running before the Quicktime update. It took a couple hours, but I was able to return to 7.3.1...Worth a try if you have time...
- 0
Jeffery Wise ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Same problem here. To say that this ***** is an understatement.
- 0
mk.4 ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
!!!!....seems that apple is becoming more and more ignorant on 3rd party software compatibility.
I remember Quicktime vers 6 as a great tool.
But since version 7 there had been several serious bugs.
- since 7.0 looping a movie seamlessly has become a 'no option' and is still not fixed.
- since 7.2 Quicktime renders rgb colors like red (255/0/0) with one or two black channels with reduced quality in compression codecs.
- since 7.3.1. I surprisingly can't open swf files any more.
- now AE is popping up with with this paralyzing 'permission error' !Apple, where are you going???
....don't harass you own community! - 0
saltbalk ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm having the same problem, but I have found a temporary solution. I simply continue the rendering from the frame where the error occured. Say I have a render that starts at 00:00 and ends at 20:00, and I get an error at 11:09, then I go back to the composition I'm rendering and adjust the work area to start at 11:10 and end at 20:00. I then render this, and if I get the error again I repeat the process until the whole film is rendered. Then I import the parts into AE and place them in a new composition, one after the other, which I then render with the same codec.
Christer
- 0
Charles Chambliss ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I too was bitten by this upgrade in AE. I was just about to do an Archive and Install when this was sent to me:
"I used Pacifist to downgrade QT to 7.3.1 on my Dual-G5, took less than
5 minutes including reboot. My first render tests indicates that the
problem is solved for me too. The only thing that popped up so far was
iTunes that informed me that I needed 7.4 to use movie rentals.Still I can't say that doing the downgrade this way is safe. If you do
it, you do it on !!!your own risk!!! and make sure to backup critical
data before./Nils"
I went to VersionTracker and downloaded this software and then to Apple's downloads site and downloaded the appropriate QT 7.3.1 installer (update). I then ran the Pacifist program and chose the QT 7.3.1 pkg file and it did the rest. I am up and running again with 7.3.1 and all is well, so far.
I am not endorsing this product, nor am I saying you will get the same results, or that it won't mess your stuff up.. just that it worked for me. I have to say, 10 minutes worth of this was much better than the Archive and Install route.
- 0
Oktofianto ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
It worked!! and is safe so far:-)
- 0
Oreckel ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I don't have a Mac in front of me, but you could try fiddling around with the permissions for the directory that you're trying to render to. I don't know if OSX has an interface for doing that (you can do it with Path Finder I know), so if you know how to CHMOD with the terminal you can try that.
For instance, type
chmod 777 "directory name"
And include the quotes. I don't
expect that should hurt anything.But if your renders are getting part way through before failing it probably isn't related to that. Thanks everyone for the heads-up: I haven't upgraded yet.
Message was edited by: Oreckel