Bill Clark
Forum Replies Created
-
I’m getting the same thing – also on the Filmscribe software plus when I use the meta publisher to convert an AVID AAF file to XML – I get a “Could not load the library AAFFilterJNl.dll” error message.
MacPro 2 x 2.93GHz Quad-Core Intel Xeons
16g RAMBill Clark
Origami Films
http://www.origamifilms.com -
Hi Stacey – what machine, processors, RAM are you running this on?
Bill Clark
Origami Films
http://www.origamifilms.com -
In my experience its either the OS or the RAM. The trouble with windows is that it is limiting on RAM. And I think Vista is awful. We still run XP pro SP3 on a XW8600 and everything runs fine – AE and AVID both at HD res. But we keep the programs open down. Try swapping to XP pro or upgrading the Vista to 7 premium. That’s supposed to be better. I believe you can get more RAM in with Windows 64 bit but I’m a bit out of touch. Mostly we use MacPros for everything now.
Bill Clark
Origami Films
http://www.origamifilms.com -
No idea where your output files are yvonne – but you can set where they go. In preferences in Mac or options in Windows you will see an option to check a box to set up where you want your files to be stored. Set up a folder on your desktop (or wherever you want) called “compression output” check the box in prefs and then browse to the folder you want your files to be stored in. From then on Media encoder will store all your files in that folder. It’s a good programme. Don’t panic! Hope this helps.
Bill Clark
Origami Films
http://www.origamifilms.com -
-
As waves seems to be primarily an audio prog I can’t see how the two would be connected. If you dragged waves into the trash to deinstall then you could drag it back into to your applications folder to see if that helps. If not try a clean re-install of media encoder. I’m sure that if the waves uninstall did accidentally destroy any shared files a re-install would put them back. Good luck.
Bill Clark
Origami Films
http://www.origamifilms.com -
5 minutes later I realised it was something to do with the DNxHD resolution. I’d digitised at DNxHD 60. I transcoded the rushes to DNxHD 90 and DNxHD x 90 to test and everything worked OK.
So there you go. Just writing it all down helped!
Bill Clark
Origami Films
Slate612 -
OK, believe it or not, 5 mins after I posted my rant I managed to solve my problem. It had nothing to do with all the stuff that everybody on the web was suggesting about re-installs and clean scripts. Something much simpler. I have a few plug ins on AE – Sapphire, Magic Bullet etc and I realised that every adobe programme was loading them on start up. And I kept getting an error message from Premiere Pro and Media Encoder about Magic Bullet looks – that it wasn’t registered. It was driving me nuts because it is. I reinstalled everything twice, and during this process spotted that Adobe is now putting all the plug ins in a central folder – which it refers to as media core. This on a Mac is at Macintosh HD/Library/Application Suport/Adobe/Common/Plug ins/CS4. (There might also be a CS3 file as well)
It occurred to me that this might be causing confusion – Media Encoder trying to load plug ins that it doesn’t understand and might not be licensed for in the XML file. So I pulled them out of there and put them straight into the AE CS4 plug in folder. Bingo. All the plug ins run fine – AND SO DOES MEDIA ENCODER! And now, no problems at all with the dynamic links between AE, Premiere Pro and ME.
I’m not saying this is the solution for everyone – but it’s worked for me. Hope it helps somebody.
Over and out.
Bill Clark
Origami Films
Slate612 -
Premiere pro CS4 to Media encoder works on my Macbook pro but not on my Mac Pro. I’ve followed ADOBEs work around, uninstalled CS3 re-installed CS4 yaddda yadda and still nothing!
This is unacceptable – we’ve all paid GOOD MONEY for CS4 – isn’t there anybody out there from ADOBE who can fix this!!!!
Bill Clark
Origami Films
Slate612 -
Bill Clark
July 6, 2008 at 6:50 am in reply to: After Effetcs Crashes 99% of the time — new computerDid this stay fixed? I’ve been having the same problem but believe it is caused by Keylight sucking up too much memory. I’ve tried removing open gl updating keylight to 1.2.8 but it didn’t help. The only thing that worked for me is flicking the 3 gig switch – which messes up the computer in lots of other ways or running nothing else, purging, rendering out the offending scene (3 secs long) and re-importing the render.
Maybe things will get better when AE goes 64bit?
HP8600
Dual Intel quad core
4 gig Ram (why bother?)
Quadro FX 1400 (and I’ve tried a 1700)
XP Service pack 2Bill Clark
Origami Films
Slate612