ERROR Compiling movie - 9 (possible) fixes - Renderer error Premiere Pro
ERROR Compiling movie - 9 (possible) fixes - Renderer error Premiere Pro
9 ways to fix Error compiling movie, Unknown error, Accelerated Renderer Error, Unable to produce frame in Premiere Pro. ►Sponsor: Download millions of stock videos, music, SFX, templates, and more! Start a 7-day free trial: https://elements.envato.com
►Timestamps:
00:00 - Intro
00:46 - Retry, Reboot
01:12 - Find timestamp and fix effect
02:19 - Export with Media Encoder
03:10 - Create a new project
03:44 - Disable CUDA
04:39 - Export with NVENC
05:18 - Update GPU drivers
05:44 - Copy all to new sequence
06:22 - Change editing mode
► Music used in this video: https://elements.envato.com/calm-elec…
#Storysium #ErrorCompilingMovie #PremiereProTutorial
Content
0.434 -> Hello Premiere Pro users! And welcome to Storysium.
3.53 -> This is an updated version of my video where we talk about possible solutions
7.382 -> for the most common error inside Premiere Pro.
9.63 -> And that is: Error compiling movie.
12.96 -> Although it gets better with every update of Premiere
15.565 -> I still receive this message now and then.
17.6 -> And I know how frustrating it can be, especially at the end of a long export.
22.08 -> There are many reasons why this can happen.
24.148 -> And I won't be able to cover them all inside one video.
27.097 -> So, today, I'll be showing you the most common reasons and possible solutions.
31.062 -> You can find the timestamps for each one in the video description.
34.08 -> Please let us know in the comments
35.668 -> if you fixed the problem with one of the solutions provided in this video.
39.245 -> This way, we can all help each other.
41.325 -> Okay, let's move over to Premiere and look at the first possible solution.
47.657 -> The first one fixed at least 75% of my compiling errors.
51.725 -> It might sound strange but simply try to export the same sequence again.
58.114 -> But in case that doesn't work, save your project
60.891 -> close Premiere, and restart your system.
63.245 -> This might free up some system memory and maybe clean up some temporary files.
67.28 -> I know, it might sound obvious, but most of my errors are fixed after reboot.
74.582 -> Okay, time for the next possible solution.
76.891 -> Sometimes you will find a timestamp in the error message.
80.48 -> And this might be the exact point where you want to search for the cause of the error.
84.022 -> You could go to this exact point on the timeline
86.457 -> and make some small adjustments
87.942 -> like extending a clip for a couple of frames, for example.
90.925 -> In most cases, this will fix the problem.
93.051 -> But, if it doesn't, then you might want to look
95.165 -> into the effects that are applied to this clip.
97.622 -> And, in my case, often the Lumetri Color or the Warp Stabilizer effect caused the issue.
103.085 -> And, if you want to be sure, then you can disable the effect
105.81 -> then make a selection and export that part only
108.365 -> just to test if it will export successfully.
111.348 -> And, if it does finish the export, then you might have found the cause of the issue.
115.542 -> A possible solution might be to remove the effect directly from the clip
119.394 -> and then create an adjustment layer and add the effect to it.
122.674 -> Another option would be to simply change the settings of an effect.
125.92 -> in this case, for the Warp Stabilizer, you could change the Smoothness, for example.
129.988 -> And, if you're still unable to fix it, then the last resort might be to remove the effect entirely.
141.817 -> The third possible solution is exporting your project inside Adobe Media Encoder.
146.982 -> You can do this be selecting Queue in the Export window.
150.434 -> This will open up Media Encoder, and now you can export your video here.
154.24 -> To start the export you need to click on this green icon here, on top.
157.782 -> And then, you can see the progress of your export here on the bottom.
160.651 -> Exporting with Media Encoder solved the error a lot of times for me.
164.228 -> So, definitely worth to give this a try.
166.72 -> Before we move over to the next possible solution
169.405 -> I would like to thank Envato Elements for sponsoring this video.
172.56 -> Envato Elements is a great source for all your creative projects
176.262 -> They offer millions of high quality items like stock photos and videos
180.205 -> but also music and sound effects and fonts and much more.
183.954 -> If you want to try them out, then use the link in the video description
186.754 -> to claim a discount in your first month.
193.291 -> Possible solution number 4 is creating a new project
196.96 -> and then copy your existing project into it.
199.805 -> This means when you start up Premiere you need to select New Project.
203.394 -> After that, you need to go to the Project Panel, then right click and select import.
208.057 -> Then browse through your existing project, select it and click Open.
212.148 -> Select "Import Entire Project" and the option "Create Folder".
216.217 -> And once it is imported you can select the sequence that you would like to export.
220.262 -> And then you're ready to give the export another try.
227.794 -> Number 5 is for anyone who gets the error while Premiere is rendering on the timeline.
232.514 -> please note that this solution will probably slow down the overall performance in Premiere.
237.062 -> But, it's worth to give a try even if it's just temporarily.
240.674 -> If your GPU or video card is powerful enough
243.702 -> then Premiere will use it's power to accelerate encoding.
246.88 -> If you have an NVIDIA Card, then this is known as CUDA.
249.931 -> This all sounds great but sometimes this can cause errors.
253.108 -> So, it might be worth disabling this temporarily.
256.068 -> If you want to do this you need to go to "File", then "Project Settings" and then "General".
260.594 -> And then change the Renderer option to "Software Only".
263.565 -> Maybe this can solve the errors that you get while rendering on the timeline.
267.131 -> And in case you have an older GPU, then this might also help during the export.
271.371 -> But remember to turn Hardware Acceleration back on for the next project
275.428 -> because it will get a lot slower with Software Only.
281.988 -> The next one is related to the previous one but only applicable for newer GPU's
286.377 -> that support NVIDIA Encoder or NVENC, in short.
289.977 -> Other most new high end NVIDIA card should have
292.64 -> dedicated hardware for encoding H.264 and H.265 codex.
297.988 -> So this means that you now have the option to select NVENC for exporting your videos
302.457 -> if you have the right hardware.
304.034 -> So, make sure to select this one, by default, if you have the option.
307.668 -> And, of course, you could try to do the opposite
309.874 -> and choose for Software Only in case your export filled with NVENC on.
313.645 -> But, of course, keep in mind that Software Only exports will take longer.
321.12 -> And another one also related to the previous two is updating your GPU drivers.
326.48 -> Most likely, you have an NVIDIA, AMD or INTEL video card.
330.628 -> You can find your model in the Device Manager, inside Windows.
334.137 -> If you have found the manufacturer and GPU model
336.788 -> you can go to their website and download and install the latest drivers.
340.8 -> And, in some cases, this might also be a solution for rendering errors inside Premiere.
348.445 -> The next one also seemed to work for a lot of people
351.051 -> that watched my previous version of this video.
353.52 -> I don't know why, but sometimes Premiere just screws up a sequence.
356.925 -> In that case, it's best to create a new one and copy the content to it.
360.525 -> So this means that you need to go to the Project Panel
362.788 -> then click on the "New" icon and select "Sequence".
365.554 -> Use the same setting as the original sequence and click OK.
369.142 -> Then go back to the old sequence, select all the items and copy them.
374.102 -> And, after that, you can go to the new sequence and paste all the items there.
378.468 -> And, after that, you're good to go to give the export another try.
384.411 -> The following solution was suggested by one of the viewers
387.565 -> in the comments of the previous version of this video.
389.874 -> It seems like it solved the error for many other users as well.
393.154 -> So that's why I decided to include it here.
395.52 -> His suggestion was to go to the "Sequence Settings" and then change the "Editing Mode".
399.942 -> If you pick one of the default profiles
402.068 -> then make sure that it matches with your current sequence settings
404.925 -> in things like Resolution and Frame Rate.
407.325 -> Then click OK to save the settings and give the export another try.
411.931 -> And that's it guys!
413.085 -> I hope that one of the suggestions helped you to solve the errors inside Premiere.
417.017 -> Please let us know in the comments if it did, or it did not
419.76 -> or maybe you found another solution.
421.794 -> This way we can all help each other.
423.748 -> Anyway, thanks for watching! And, I hope you have a wonderful day.
428.891 -> [Music]
Source: https://www.youtube.com/watch?v=g0PH3F3I97o