{"id":601,"date":"2016-07-19T04:58:47","date_gmt":"2016-07-19T04:58:47","guid":{"rendered":"http:\/\/www.editspecialists.com\/blog\/?p=601"},"modified":"2016-12-07T00:27:46","modified_gmt":"2016-12-07T00:27:46","slug":"glitchy-buggy2015-3","status":"publish","type":"post","link":"https:\/\/www.editspecialists.com\/blog\/index.php\/glitchy-buggy2015-3\/","title":{"rendered":"Glitchy, Unstable and Unreliable, can’t render or export with Premiere 2015.3"},"content":{"rendered":"
\"image_pdf\"<\/a>\"image_print\"<\/a><\/div>

December 2016: It’s happening again with the 2017 version.\u00a0Get your shit together Adobe, or you’re fired!\"premiere2017-error\"<\/a>Hi all, I’m having some trouble with exports via Adobe Media Encoder in Premiere Pro CC 2017, I’m not exactly sure how to describe the problem but have attached a screenshot from a Media Encoder export.\u00a0This error appears to occur on dissolves and footage dynamically linked to After Effects projects. This error does not occur if I export directly from Premiere Pro.\u00a0I have encountered this error on both my rig (specs below) and a client’s top-spec iMac (2015 27″ 5K). It has occurred on separate projects created on the respective machines.
\n<\/span>OS X 10.11.6
\nPremiere Pro CC 2017 [11.0.1]
\nMac Pro (Mid 2010)
\n2x 3.06 GHz 6-Core Intel Xeon
\n48GB 1333 MHz DDR3 ECC
\n512GB SSD
\nNVIDIA GeFore GTX 980 Ti
\nAnyone else encountered similar problems or can recommend anything to try?<\/p>\n

Update Aug 3 2016,\u00a0the fix is in,<\/a>\u00a0be careful folks, test your workflows before you commit!
\nThey did it\u00a0again, that company that I pay $53.49 every month.
\nA\u00a0few weeks ago, before starting a big project\u00a0(the online of a 3 hour PBS documentary),\u00a0I upgraded to 2015.3 on my 2 Macbook Pro laptops<\/a> that I use to edit. I took the option to remove the old version, more about that later.
\nMy project specs are:
\n3x 53 minute reels with mixed formats ranging from 29.97 XD-CAM to DVCPRO to DV to PAL 25 fps footage on a ProRes-422 Timeline with Previews set to ProRes-422. 1920×1080 interlaced.
\nAll was good the 2 weeks before the job came in on short tests. I liked the proxy workflow, liked the connection to my Tangent panels.<\/a> etc. etc.
\nThen the job came in and it all quickly fell apart…
\n-It didn’t work or was super glitchy and unstable with my Red Giant shooter suite <\/a>and Universe plug ins, even though Red Giant\u00a0announced they were 2015.3 ready.
\n–<\/a>the Lumetri effect was\u00a0unstable, randomly changed sliders I didn’t\u00a0touch and, most important, I couldn’t save my\u00a0presets reliably.
\n-After each crash there were different inconsistencies with all the edit decisions I made. I kept second guessing myself about stuff\u00a0I fixed or fx that I did.
\n-The biggest issue was that after working for 5 days getting this project into premiere from FCP7, I couldn’t render or export!
\n\"PR-error-compiling\"<\/a>The\u00a0stupid new error message that tells me where the render stopped\u00a0is very unhelpful. Because\u00a0there is NOTHING I can do to ever render successfully!<\/p>\n

I re-installed the old version 2015.2\u00a0and re-did the work I did unpaid:
\n-Of course you can’t open a newer project in the old version<\/a>.
\n-I used the video XML’s from FCP 7 to rebuild the timelines.
\n–Using XML out of 2015.3 <\/a>for video with FX\u00a0was glitchy and unreliable, created more crashes.
\n-Luckily I hadn’t worked on audio much so I made audio-only sequences and the “cut’s only” XML out of 2015.3 to 2015.2 worked fine.
\n\"PR-open-with\"<\/a>-The good news was\u00a0that having both 2015.2 & 2015.3 open at the same time using the same video output device (in my case a Ultra studio mini monitor<\/a>) didn’t create any conflicts or crashes!<\/p>\n

Dear Adobe,\u00a0my clients don’t care what software I use to get the job done. If you rush out versions and then force me to stay up all night, unpaid to fix the project, you’re\u00a0not keeping me as a friend!\u00a0 I’ve been using Photoshop\u00a0for 20 plus years and Premiere as my main editing software for almost 3. This is the second time you rolled out a glitchy, buggy version for us \u00a0\"unpaid\"<\/a>beta testers. Please give us a break. I don’t care about any\u00a0new bells and whistles if you keep breaking your\u00a0basic functions.<\/p>\n

This story has a happy ending, because I’ve been working on a stable system for the past 4 days and just did an export of my fully rendered 53 min timeline, using previews, in 2 minutes! That’s 1\/25th realtime!
\nTo me that proves that when software is matched with correct hardware, operating system and project specs, Adobe software can do miracles. Adobe\u00a0should\u00a0write more honest workflows like this<\/a>\u00a0and focus on keeping out bugs when it\u00a0rolls out a new release.
\nOf course\u00a0my experience is based on a specific machine, but I also work on many PC systems and usually experience the same\u00a0glitches.
\nPlease fill out the survey below.
\nFAQ: How to go back from Premiere Pro 2015.3 to Premiere Pro 2015.2
\n<\/a>The fix is in,<\/a> be careful folks, test your workflows before you commit!<\/p>\n