[Paul Roper]

I found the solution!

As Todd Kopriva suggested, I looked at his troubleshooting page ( https://blogs.adobe.com/aftereffects/2011/02/troubleshooting-quicktime-errors-with-after-effects.html ) and was interested to read:

“I’ve even seen non-security software such as FileMaker (as well as some malware, as mentioned here) block this communication by taking up the port that is needed.”

Hmmmm…..I use FileMaker Pro a lot, and it’s usually running in the background. So I quit FileMaker, loaded up AE CC, set something to render, and lo and behold it just did it. To double-check, I then loaded up FileMaker, set the same thing to render again, and it failed with the same QuickTime error.

So there you have it. So who is to blame for using that same port? Is it Adobe or FileMaker? I’d bet that whoever is to blame, it would be much easier to get Adobe to change the port rather than FileMaker. Chances of those idiots at Crapple pulling their fingers out and making a 64-bit version of QuickTime? Don’t make me laugh!

– Paul

[Paul Roper]

Thanks Dan!

Incredibly, a Google search for ~~ returns no results. But I managed to find out that ~~ (a double bitwise NOT, apparently) and Math.floor perform the same thing.

– Paul

[Paul Roper]

In case it help track down the problem:

I have no video in/out cards and my After Effects CC install has no 3rd party plug-ins at all. In fact I uninstalled and re-installed it yesterday, so it’s fresh-out-of-the-box, but it didn’t help.

I can import/edit/play QuickTimes in Premiere CC – no problems there.

I have QuickTime 7.6.6 installed (as well as the useless crappy QuickTime X which I never use). I have Final Cut Pro 7 installed, and no FCPX. FCP7 installs the “pro” codecs (such as ProRes) but I suspect that the standard OS install (QuickTime X) does not have those codecs. I’d imagine that an FCPX install would include the pro codecs too.

I used the beta version of AE a couple of months back for a job involving a lot of QuickTime renders, and had no problems…but that was on a different Mac (exactly the same spec, same OS, same RAM, same video cards, but a different physical machine…in a different country).

– Paul

[Paul Roper]

I’m on a Mac Pro. I did a complete uninstall and re-install of AE, but I still have the same problem. Which obviously makes AE CC completely useless for me.

Will submit ANOTHER bug report.

– Paul

[Paul Roper]

Ah – make that any QuickTime format.

It will render image sequences OK, but I’ve tried a few QuickTime codecs and it just gives me an “output module failed” error.

[Paul Roper]

Nope – restart didn’t fix it. Bug report time.

Bah. Back to CS6 for now….

[Paul Roper]

A rather sluggish 10:24 on my Mac Pro:

2x 3.06GHz 6-Core Intel Xeon
64GB 1333MHz DDR3 RAM

2x Nvidia Quadro 4000 (2GB RAM each).

It’ll be interesting to see if After Effects CC makes any improvement.

– Paul

[Paul Roper]

Aha! After some searching around the world of Javascript, I found the rather bizarre:

~~

…so:

n=16.99;
~~n

wound give the desired:

16

– Paul.

[Paul Roper]

THANK YOU! I went through every menu imaginable to get rid of these bloody guides. What a palaver.

– Paul

[Paul Roper]

Always interesting to compare bang-for-your-buck specs. I’m working on a Mac Pro which costs around $8500 excluding the 2x Quadro 4000 cards, which push the price north of $10K. Compared to Darby’s Z820 Cinebench results, my Mac’s running at tortoisesque speeds:

– Paul