The problem with Unknown Errors is that their cause is unknown. Without knowing a cause, we can't really provide a solution.
Try rendering small segments. Perhaps 10% of the timeline each time. That might lead you to the section of the timeline that is causing you the problem.
I tried rendering another project and, while it doesn't say "failed", it doesn't render either.
if I render it under premiere, it says the same "unknown error" message.
if I render it under Media Encoder, after a while, it simply stops doing anything. doesn't fail, but doesn't finish either.
Maybe I should note that both projects have a "lumitri fx" on an adjustment layer.
Try it without that.
The problem seems to be in the new Lumetri effect.
I removed that and did a render from witin premiere and it finished without any problem.
Also, it's rendering under media encoder with same settings and so far, so good... it goes slow as a sheet of paper, though; but at least works
So... where should I complaint bitterly about this?
I would try in a sample project with a small video file. If that fails, you can post a link to that sample file - we can take a look and see if we can determine the cause of the failure.
I'm so nice that I've actually prepared a complete project, with video, sequence and all that fancy stuff
I use the following settings to render it:
If you render it from within Premiere, it gives you the error message at about 35 to 40%; the actual position is random.
Also, after the error message is shown, if you click "export" again, it immediately gives you the "unknown error" message, and it won't render anything until you quit Premiere.
When you quit Premiere, sometimes it crashes, sometimes it doesnt.
So, to me, the evidence points to a lost pointer in the Lumetri effect. If you tell those symptoms to a programmer, I'm sure will agree with it.
Please download the project from here:
Also, please let me know when I can delete the file, since it takes too much space of google drive.
Hope this helps to solve the problem ASAP, since the Lumetri effect is my TOP favorite new feature of Premiere CC .
I've had no trouble rendering several of the Lumetri Looks so far on two different machines, applied both to the clips directly and to ALs, using both the MPEG I-Frame codec and the DNxHD codec. I've also had no issues exporting the effect under any circumstances.
I am using a custom look file. Maybe it's a combination of some of the settings and/or uncompressed avi files.
Could you try with the project I uploaded, please?
I tried that same project using one of the integrated looks, and it crashed too.
Maybe I should mention that I'm using the "Use maximum render quality" option, which makes the render take a lot more time.
Also, my GPU is an ATI Radeon HD 6990
Maybe you are using an nVidia?
Rendered fine here, and yes I'm using nVidia.
Max Render Quality won't do anything but slow you down when using GPU acceleration. I turned it off before rendering.
So, it seems to be a problem with the Lumetri effect AND AMD GPUs
Lets go through two examples that show the difference here:
1. A HD clip in a SD timeline with scale-to-framesize and accelerated 3-way effect
CPU: Gaussian low-pass sampled with bilinear
CPU MRQ: Variable-radius bicubic
GPU: Lanczos 2 low-pass sampled with bicubic
GPU MRQ: Lanczos 2 low-pass sampled with bicubic
In this case the MRQ setting will only affect CPU based renders.
2. A HD clip in a SD timeline with scale-to-framesize and a non-accelerated twirl effect
CPU: Gaussian low-pass sampled with bilinear
CPU MRQ: Variable-radius bicubic
GPU: Gaussian low-pass sampled with bilinear
GPU MRQ: Variable-radius bicubic
Because scale-to-framesize happens before effects and there is a non-accelerated effect, here the scaling will be done in software during a GPU render. During a GPU render the MRQ setting will thus apply to any software rendering done as part of the GPU render, determined on a segment-by-segment basis.
Then please explain why it fails in my ATI GPU, but not on Jum's nVidia GPU.
Also, please explain why it doesn't crash when I disable the Lumetri effect.
OK, yes...there may be situations where rendering falls back to the CPU and MRQ will help.
In this case, that didn't apply.
Because scale-to-framesize happens before effects and there is a non-accelerated effect, here the scaling will be done in software during a GPU render.
What makes you think that?
Should I report this bug to Adobe..?
Or will they look at it automatically..?
Not sure it's a bug yet. Given the other issue, it may just be something wrong on your machine. Finding someone else with AMD graphics to test would help.
Hey, I'm having the same problems when I apply Lumetri Looks to clips and then render out with gpu acceleration I get the exact same error messages you do. I am using an AMD FirePro V7900, a cadilac in the graphics cards world. So this is a definte bug.
I never had this problem in Speed Grade CS6 but I hated having to export from Pr to Sp, then back to Pr and Export again for En and render yet again to IMG files. Adding Lumetri Looks to Pr was a great idea and a big time saver. When I heard Adobe was optimizing Pr for AMD cards I was real excited. But this glitch really slows down my work flow again. If Adobe could add a patch for this it would be great.
Im getting the same error with nvidia 680
Tony: Because the error is generic and provides no pointers to the cause of the problem, the fact the you hit the same error means almost nothing. In other words, a variety of issues can lead to the same error message. Therefore, it's best to treat each case separately. Once enough details are on the table, it may turn out that your case is a dead ringer for a known scenario.
So I suggest that you start a separate thread and provide as much detail as possible.
One point to clarify right out of the gate: are you exporting a sequence or rendering it within Premiere? If you're exporting, then you'll probably be better off posting on the AME forum rather than Premiere's. Regardless, this page for AME will be a better guide to what information to provide than PPRO's: http://forums.adobe.com/thread/1011883.
DId you ever find a resolution to this alraz? AMD FirePro M5950 and I am running into a very similar issue. I'm exporting a sequence from Premiere Pro CC using the Sepia Lumetri Look.
If I do a project of less than 1 minute it will render at but the video usually gets garbeled after 45 seconds or so. If the project is more than 1 minute long it does not usually complete the render or if it happens to I will gradually lose all video clips with the effect applied to it after 1 minute and be left with a nice bright green screen.
These wonderfully helpful "unknown error" things are a joy to track down.
EDIT: Found some notes pertaining to render Max Bit Depth and Max Render Quality. Trying those options now...
Message was edited by: JesseYost
Sadly, I never found a solution
Up to this day, I'm still unable to use the lumitry filter in premiere
I've changed the video card (from Radeon HD 6970 to Radeon HD7990), the motherboard, the cpu (from AMD to higgher level AMD), windows (from 7 to 8) but still nothing seems to work
Looks like a problem with Premiere itself and not my computer.
I might be misstaking but I think the culprit for me was bad gpu drivers.. But I have nvidia, they came with an update and things was running again. Maybe you can try an older version of the drivers to your gpu.
The only solution I found is to stop using lumetri effects in PrePro.
The problem is Adobe claimed that PrePro CC was developed for AMD graphics cards. Sadly, that hasn't proved true. For whatever reason Adobe hasn't made this issue a priority or haven't found a solution.
It's annoying that Nvidia cards work fine but AMD do not. If I were AMD I would be very angry.
How come Andrew Kramer from Videocopilot can make a plugin for Ae that fully exploits any graphics card render engine(both AMD and Nvidia) yet has no issues but Adobe can't make one effect work with AMD cards?
I know one thing for sure; we don't have the full story.
I wonder if this is even in Adobe's bug list...
Hope they actually read that
They do read them all. Doesn't mean you'll get immediate or even timely satisfaction, but they do read them.
here is a quick update:
I manged to workaround this bug by changing the audio codec before exporting.
If you use MPEG for audio instead of AAC, the render should succeed. The only problem now would be that Windows Media Player will refuse to play the exported file.
However, Media Player Home Classic plays it just fine.
I hope someone at Adobe is reading this and works on figuring out what part of the AAC codec is conflicting with the Lumitri effect.
Another quick update:
By selecting AAC as audio format and AAC+ Version 1 as audio codec, I was able to make it work too.
AAC+ Version 2 also worked, but in my case, it introduced some weird artifacts in the sound and also made windows media player refuse to play the file.
So, you may want to give both options a try and see if they work for you.
Adobe, please work up on this and help is fix it!
I had the same issue. Tried it every way I could think of but it always failed and failed at the same point. I watched it render in Adobe Media Encoder and looked at the clip it was failing on and it had Lumetri Color Effects added. I removed the Lumetri color effect from every clip that had them and it exported fine. I really like the Lumetri effects, Being a heavy Lightroom user I can understand what I am doing.
Ok, Now that all us CC members are paying to test for bugs in every drop of every piece of software that is released and for some of us editing video with sound, which is not an odd thing to do by the way, we need Adobe to step up and fix their issues with audio transcode on render or what ever the problem is. I rendered an hour long short film last night at 8:00pm, took till 10:00 to complete. Its a flattened Multicam edit, (problems with multicam too but different thread), with a lot of sound effect so the audio has 43 tracks. Watched the render and everything looked ok to add titles and credits which I created in After Effects and rendered out. Brought these 2 rendered files into PP, (both were H264, 44100, 720p), started a new sequence, placed them both in, started a final render with the exact same setting both files were in and off to the races. Walked away for 30 min, yeehaa, it's done but with a little warning on the file in media encoder and the file wont play. Tried again, same problem. Now my Hard drive is full even though scratch is not on C. Tried to clean and delete manually, helped a little. Put AE rendered file into original PP file with film and tried to render, same problem. After this ONE render attempt my hard drive full again. Went through the cleaning process again on the drives and freed up only 50gig, tried render again, File corrupt again and hard drive COMPLETELY full. What the heck is going on? I don't even have PP or After effects pointing at the C drive for cashing or scratch but now I cant render anything without the error. this is the 2015 version of PP. Bottom line. I MISSED MY DEAD LINE AND LOST OVER 2 THOUSAND DOLLARS ADOBE!!!!!!!!!!!!!!!!!!!!! Adobe products have caused me more issues and lost revenue than I care to mention and if Adobe reads these things, GET THIS STUFF FIXED or lose customers, (or software tester is what it seems we are) Tell you the truth, I think Adobe has gotten to big to fail so they don't really care about their customers anymore unless they are a major studio who will endorse them in credits.
we need Adobe to step up and fix their issues with audio transcode on render or what ever the problem is....
GET THIS STUFF FIXED or lose customers, (or software tester is what it seems we are)...
Tell you the truth, I think Adobe has gotten to big to fail...
Sorry for all the trouble you're having. First of all, if you want to make complaints to Adobe, the best advice I can give you is to fill out a bug report for your specific issues. If your'e not receiving help on these forums, contact support M-F 5A-7P PST here.
I am having the same issue. But only after selecting "Use Maximum Render Quality". I rendered the same project out 3 different times last night, made that one change this morning and it fails everytime.
Ok, I think I found a solution. It's a workaround, but you'll end up having a movie with full bit depth and scaling. You should not use the H.264 codec. I've tried rendering into "mov" file with YUV 8 bit uncompressed output. IT WORKED! Yes, you'll have a gazillion gigabytes movie, but then all you have to do is run it through ffmpeg (simplest of all) and you'll get what you want.
Just had this same issue.
Worked with support and it turned out to be the project file!
So just create new project file and import the old one into it.