[Adrian Tan]

I just had the “Unknown error” message…

Basically, I had a series of photos with a dissolve at the start of the first photo. I nested the sequence (because the photos were all on separate tracks), then added another dissolve to the nest, and Premiere didn’t like that one bit. (Why did I add an additional dissolve? No good reason. Just forgot that there was already one there.)

Removed the dissolve and all was fine.

I doubt if that would have helped the original poster, but anyway…

[Adrian Tan]

Just wanted to report that I’m having flickering gremlins as well. It’s visible inside Premiere Pro before render/export as well as after. Suddenly started happening for no apparent reason.

Pretty sure it’s not related to using auto effects or interlacing or field order. Also, I’m sceptical it’s a graphics card or a PC/Mac thing. Reason: I was working off an external hard drive, moved from one computer to a different system, and the flickering remained.

Story goes… 15-minute video. I rendered it the first time, noticed the flickering, but also noticed I forgot to click “analyze” for warp stabiliser to process additional frames right at the start of the video. So, I clicked that button, rendered again, and, for some reason, that solved half the problem! No idea why. Now the flickering only turned up in the last 8 minutes.

I worked out from which clip the flickering started, and turning off RGB curves on that clip seemed to remove the flickering from that clip and for the next few clips.

But obviously I’d prefer to keep my colour grade intact.

Haven’t yet worked out what the problem is, and had never encountered it before today. Don’t want to do everything over from scratch. What I’m next going to try is removing RGB curves from all problem clips onwards and reinserting.

[Adrian Tan]

Just wanted to add that I was having this issue and pulling my hair out. Green flashes all over the outputted file.

Transcoding original footage (in my case, h.264 from Canon DSLR) didn’t work.

But what did work was simply changing the render output from uncompressed AVI to Quicktime with Animation codec. No idea why. Have exported to uncompressed AVI plenty of times before with no problems.

[Adrian Tan]

Just want to say that this post was a life-saver. My audio recorder got dropped to the floor, and the batteries came out, cutting out the recording after a wedding ceremony. Thanks very much!

[Adrian Tan]

Well, I have my output module at the “lossless” setting, which defaults to an AVI container, but then I normally click on “format options” and change the video codec from “none” to “uncompressed UYVY 422 8-bit”. (Maybe that’s the problem right there?)

Are my settings nuts? I know very, very little about codecs, and these are the settings I’ve somehow defaulted to for years.

You’re probably right that it’s some sort of codec weirdness, since it exports fine as MP4 (or maybe some sort of conflict between source footage and codec). Maybe I should just leave the video codec set to “none”.

Thanks for your reply, Paul!

[Adrian Tan]

Hey Walter, will try to keep your tip in mind in future.

As it turns out, I didn’t find what went wrong! COuldn’t locate the problem in an effect, and I don’t think it was a RAM problem or something like that (full RAM was never used on export).

But I discovered that the problem disappeared if I exported to h264 (rather than uncompressed AVI). Still don’t know why this mess happened, or what the “television static” indicates, but there you have it. And an MP4 export was good enough for this particular job.

Thanks for your help!