What voodoo makes ppro export?

Report · May 23, 2017

I'm just curious what clearing the media cache does.

Also why does rebooting seem to help with projects that wont export?

These are my steps with failed renders/exports:

1. Set the sequence previews to a decent spec (like cinfeorm 10 bit) and try to render previews. Then export using previews

If that fails

2. quit premiere, restart, try #1 again

if that fails

3. quit premiere, delete media cache, try #1 again.

If that fails

4. Reboot, clear media cache, try #1 again

If that fails

5. break sequence up into sections by changing in and out points and try to render them out one at a time (which usually leads to)

6. Finding an offending section and rendering it out in some other way (removing some effects and doing an interim render)

If that fails

7. Perform dance to the gods of Adobe, sacrifice goat, mash head into keyboard, have a valium and a lie down.

I very rarely get to #7

Are there any other arcane rights I should add to this list?

Report · May 23, 2017

So since I wrote this, now all my comments are being moderated? Was it the goat? I don't really see what warrants it, maybe the moderator who did that could let me know.

This is a serious post, and my list could possibly help people who are finding renders difficult. I was genuinely asking for other people to contribute to it. If it seems frivoulous, thats just an attempt to lighten the mood - because the level of frustration is large.

Report · May 24, 2017

I got the frustration, and also the humor in item #7 ... I've had times when something in this app wasn't working for me, and gee ... all items seem rather familiar for those moments.

But they've normally been rather short periods. And I and most others are exporting out regularly without any issues ... or at least, rarely an issue on exports. So let's try and puzzle out some things here.

Here's an odd first step ... if you've got Microsoft Office on the machine, and that "OneDrive" app is loaded ... exit it. Find the settings and tell it to not start on startup. Some other users have posted here that they were having issues, and ... on deleting that, immediately got "peace". Today, my PrPro suddenly wasn't performing sweetly ... I found that I now also had OneDrive installed ... stopped it ... and right away, PrPro was back to sweetness and light.

Back to our regularly scheduled process!

First, hardware, media, effects, and third-party apps/plugins can all matter. So ... OS/CPU/RAM/GPU/vRAM, the number-dot-number version of PrPro, how many drives on the machine, and ... how full is the drive you're exporting to?

What's your media ... type (codec/wrapper), frame-sizes & rates, made by what device ... touched by any third-party apps, plugins, and ... what effects are applied in your timelines?

Exporting direct from PrPro or queuing to Media Encoder? Both?

How about a screen-grab of your sequence settings box, and another of your export settings dialog box?

Neil

Report · May 24, 2017

Hi mr R Neil,

thanks! One drive eh? I'll give it whirl. IT wouldnt' surprise me, I really liked one drive when I first used it, then found some clients couldn't access shared folders, then microsoft borked it. They really do know how to pull defeat from the jaws of victory.

The rendering thing is not specific to one project. I know that I throw a *lot* of $h1t at premiere, and I'm constantly happily surprised when it *does* render You name it I do it: several lumetri effects, masks, adjustment layers with masks and lumetri, h.264 4k mixed with 1080, mp4s, quicktimes, backwards clips, speed ramped clips, 3rd party transitions and a different 3rd party effects suite.

I guess the post came from the weirdness of the randomness of it. Why ppro has it's good days and it's bad. Me learning premiere has been as much about learning its moods as techniques - and I'm genuinely interested in what magic clearing the cache does! It's generally my universal panacea.

Report · May 24, 2017

With that wonderfully diverse list of things typically on a sequence, well ... there might be the occasional grumpiness of PrPro. Ah well. We can hope, right?

PrPro seems to get ittle bits of odd or corrupted data in the cache files now & then, or it "keeps" an earlier reference not the newest one or something, so clearly the cleaning of the cache fixes a lot of just general "Huh?" -ness.

Neil

Report · May 24, 2017

getho wrote
So since I wrote this, now all my comments are being moderated? Was it the goat? I don't really see what warrants it, maybe the moderator who did that could let me know.

Moderators don't decide which post gets moderated and which does not. Its the way the forum software is programmed.

We do deicide which one gets approved and which one does not.

Report · May 29, 2017

Ann Bens I could've sworn my posts were posting without moderation before?!

R Neil Haugen thanks. I think as technology progresses we'll see more and more and this sort of grumpiness. Maybe literally:

Report · May 29, 2017

Jim Simon thanks jim, most excellent alternative to dead goats in there

Report · Jun 02, 2017

getho wrote
https://forums.adobe.com/people/Ann+Bens I could've sworn my posts were posting without moderation before?!

I sometimes have no idea what make Jive tick. I think it also has to do with links posted in the thread; not sure.

But moderators here are lightning fast, your posts wont stay in moderation for long.

Report · Jun 02, 2017

NO one is quite sure how Jive picks the post to send to moderation. Even mods get totally innocuous reply posts dumped in the mod queue every once in a while. Links can increase the possibility, but ... some of the links that 'pass' Jive's scanning are rather amazing ... and some that don't are totally clean & pertinent.

Who knows ... Jive knows!

Report · Sep 14, 2017

Just found a new workaround which I thought I should add to the list. It makes things sooooo much quicker. And It needs to go near the top (1a)

1. Set the sequence previews to a decent spec (like cinfeorm 10 bit) and try to render previews. Then export using previews

If that fails...

1a. quit premiere, [windows] go to device manager and disable and re enable your display adapter.

If that fails

2. quit premiere, restart premiere, try #1 again

if that fails

3. quit premiere, delete media cache, try #1 again.

If that fails

4. Reboot, clear media cache, try #1 again

If that fails

5. break sequence up into sections by changing in and out points and try to render them out one at a time (which usually leads to)

6. Finding an offending section and rendering it out in some other way (removing some effects and doing an interim render)

If that fails

7. Perform dance to the gods of Adobe, sacrifice goat, mash head into keyboard, have a valium and a lie down.

Report · Sep 14, 2017

Ahhh ... there are times that item 7 is the only thing that seems to work.

At least if the goat is facing the right direction... what's the right direction? ... test. Retest. Test again.

Report · May 24, 2017

Are there any other arcane rights I should add to this list?

Unofficial Premiere Pro Troubleshooting Guide

Report · Dec 27, 2017

I have done lots of steps like this and more. Including sacrificing different animals and vegetables for item #7.

One step that people and Adobe 'Experts' always mention is to turn off GPU rendering.

It is true that, usually, it renders...

But then, Premiere is now implementing a new set of 'Essential Graphics' to replace the archaic Titler - and it turns out that, when using Software Renderer (either in Premiere or Media Encoder), many of these graphics get misaligned or scrambled. No deal...

It's very frustrating indeed.