-
Testing the 2014 waters…
Had to reanimate a CC project of a web series just to encode to another format, and decided to test the latest 2014 update combined with the latest Red Giant Magic Bullet Looks update, since trying to import a CC project in the original release of 2014 didn’t go so well, and if MB Looks was applied anywhere, well, forget it.
So, everything seemed to be going well. The only weirdness initially being that some media was seemingly lost, and when I would click “Locate”, it would open to the exact location of that media, and it was sitting there. Not sure why PPro couldn’t see it without my assistance.
Then, I tried to export via AME 2014 via the ‘Import PPro Sequence method’ so I could batch encode. A couple of the 5 minute sequences encoded without issue, then the 3rd one balked. I tried again, and it would balk at a different spot on the timeline. So, I restarted AME 2014, and that sequence would then encode. So, after several more rounds of this, it seems that AME 2014, at least on my machine, has issues with batch encoding PPro sequences.
Asus P6X58D Premium * Core i7 950 * 24GB RAM * nVidia Quadro 4000 * Windows 7 Premium 64bit * System Drive – WD Caviar Black 500GB * 2nd Drive(Pagefile, Previews) – WD Velociraptor 10K drive 600GB * Media Drive – 2TB RAID0 (4 – WD Caviar Black 500GB drive) * Matrox MX02 Mini * Adobe CC
——————————————-
“98% of all computer issues can be solved by simply pressing ‘F1’.”
Steve Brame
creative illusions Productions -
5 Replies
-
Seems like I’m relegated to spending my weekends troubleshooting software that I pay quite a bit of money for. Don’t get me wrong – I have no problems with being a beta tester, as I have been for other software packages for years. It’s just that it was known ‘up front’ that I was signing up to be a beta tester, and the beta version was provided.
CS6, while it seemed to have it’s share of issues, didn’t require nearly the amount of time troubleshooting problems. Since CC, it seems like that’s about all I do.
Asus P6X58D Premium * Core i7 950 * 24GB RAM * nVidia Quadro 4000 * Windows 7 Premium 64bit * System Drive – WD Caviar Black 500GB * 2nd Drive(Pagefile, Previews) – WD Velociraptor 10K drive 600GB * Media Drive – 2TB RAID0 (4 – WD Caviar Black 500GB drive) * Matrox MX02 Mini * Adobe CC
——————————————-
“98% of all computer issues can be solved by simply pressing ‘F1’.”
Steve Brame
creative illusions Productions -
Sorry I can’t help you but all I can tell you is that CC is much better for us than CS6 was in terms of issues, corruption, etc…. for the most part it’s been rock solid on our 5 edit workstations at the office the my two at home.
Walter Biscardi, Jr.
Editor, Colorist, Director, Writer, Consultant, Author, Chef.
HD Post and Production
Biscardi Creative MediaCraft and Career Advice & Training from real Working Creative Professionals
-
It is strange. CS6 had gotten so that it played our AVCHD footage with ease. Now, neither CC nor CC2014 will play it smoothly even at ¼ resolution if it’s got a Lumetri effect on it. The first few seconds are OK, but from that point it becomes a slideshow. I would hope that it’s a drive issue, but I’ve tried almost every recommended drive setup there is – from Adobe’s own recommendations to Harm Millaard’s!
Wait..I’d forgotten that a lot of the footage in this project was ProRes. I’ve not read of any ramifications of ProRes on a PC. Hmmm…
Asus P6X58D Premium * Core i7 950 * 24GB RAM * nVidia Quadro 4000 * Windows 7 Premium 64bit * System Drive – WD Caviar Black 500GB * 2nd Drive(Pagefile, Previews) – WD Velociraptor 10K drive 600GB * Media Drive – 2TB RAID0 (4 – WD Caviar Black 500GB drive) * Matrox MX02 Mini * Adobe CC
——————————————-
“98% of all computer issues can be solved by simply pressing ‘F1’.”
Steve Brame
creative illusions Productions -
[Steve Brame] “Wait..I’d forgotten that a lot of the footage in this project was ProRes. I’ve not read of any ramifications of ProRes on a PC. Hmmm…”
On a PC, ProRes must be decoded by QuickTime, which means a call to “Adobe QT32Server.exe” (instead of handling it natively via 64-bit MediaCore). The decoded frames are passed back to Premiere Pro via the network stack. There is a performance penalty for all this versus using a format which MediaCore can handle directly.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Thanks Walter! That may explain some of the slowness. We’ve never used ProRes before, but one of my shooters bought a BlackMagic Pocket Cinema Camera.
Asus P6X58D Premium * Core i7 950 * 24GB RAM * nVidia Quadro 4000 * Windows 7 Premium 64bit * System Drive – WD Caviar Black 500GB * 2nd Drive(Pagefile, Previews) – WD Velociraptor 10K drive 600GB * Media Drive – 2TB RAID0 (4 – WD Caviar Black 500GB drive) * Matrox MX02 Mini * Adobe CC
——————————————-
“98% of all computer issues can be solved by simply pressing ‘F1’.”
Steve Brame
creative illusions Productions
Reply to this Discussion! Login or Sign Up