Adobe Premiere Pro Issue - My render gets stuck at 11%
Solvedglandu Posted messages 25506 Registration date Status Contributeur Last intervention -
Hello everyone,
I'm back on this forum after years of absence because I admit I'm quite lost. Here's the context: I made a short sci-fi film with a lot of After Effects media, spaceships going every which way, effects on nearly all the shots, a lot of sound tracks, and a duration of 19 minutes and 50 seconds. I struggled to get a first render on an old PC a few days ago when I wrote these lines; it took over 60 hours to produce an H.264 file... Yes, the PC was very tired. Since then, I've bought a new PC; the old one had a garbage graphics card, it was on Windows 7, 8 GB of RAM, and I couldn't open anything else when I was using Adobe at the end. Anyway, it had to change. Today, this PC is running Windows 11, has 8 GB of RAM, and a 4000 series graphics card, I'm living again.
However! Despite this new PC and the fact that I've reinstalled everything, resynchronized everything, I'm having this rendering issue... I suppose the solution must be quite simple, but I have no idea where it could be coming from... The PC managed to give me a preview in 4 hours with some "Error Compiling movie" issues that I fixed; it gave me the preview in record time (the old PC took 40 hours to give me the preview), I admit I'm desperate and despite the context, I think I'm being quite vague in my explanations... Feel free to ask me questions if you think you can help me! I absolutely need to do a new render; in the first one I did, I noticed two "anomalies" that I've corrected and therefore, I want to do a clean render ^^
Thanks again!
11 réponses
Hello and welcome back to the forum. Before asking you to carefully review your project by extending (enlarging) the timeline to possibly uncover micro files, remnants of cuts revealing lines of 1 to 2 mm, (invisible without this trick) which may block finalization.
PS: The formats of the sources can also cause blockages.
Back to your new PC, it is agreed in the field that when purchasing a new PC, one should aim for a multi-core processor of at least 3 GHz base frequency, 16 GB of memory (8 GB is insufficient) for long projects, an advanced graphics card ('very good, even too much for a 4000 for "affer effect" effects), and finally an SSD for the system, software, and video projects, and another hard drive for storage.
PS: Try a shorter project to test your machine.
"Donkeys change their minds, fools do not."
Remember to mark your message as "resolved" if that is the case.
Sorry, I made a mistake in my previous post, the PC I have now has 32 GB. In the meantime, this morning I managed to increase the blockage from 11% to 33%, I replaced an After Effects media with a PNG sequence of the shot and that unlocked the render, what do you think? Do you think the source of some files could be corrupted?
PS: I also want to point out that to test the project itself, I rendered the end of the short film and managed to produce a complete rendering of the chosen piece.
I've occasionally had this incident; it may be that complicated effects are poorly translated in the rendering. Spot the place and inspect it closely, maybe remove it.
To detect the micro files, you need to use the mouse to stretch the timeline. Place the cursor over the scrollbar of the timer and pull to the right; your thumbnails will elongate.
"Donkeys change their minds, fools don't."
Remember to mark your message as "resolved" if that's the case.
Also, it's quite possible that this is the issue; my old PC struggled quite a bit with some of them, but for sure, if I can identify them, that’s better. However, this solution you're describing doesn't ring a bell...
So, I'm going to zoom in on my plans and with an option, I'll be able to detect anomalies?
I admit that it's a bit fuzzy in my head, I zoom in completely on my timeline, but then if I pull the scrollbar of the timeline to the right, it only scrolls through my edit, do you have a tutorial or a clear image of what I’m supposed to have?
Hello, I'm surprised that this software doesn't offer the option to reduce the display. The thumbnails can be shrunk to less than 1 cm to have an overall view of your project, and the opposite is also possible. This is the only way to detect a tiny file appearing as a short vertical line that is too brief to be considered in the rendering. I call this "debris." It's on this line that the cursor arrow changes to a double-headed arrow. I will try to take a screenshot for you.
Okay, so yes, I want to clarify that Adobe Premiere Pro is the CC 2022 version. If it was available before, it must still be available today, but there has been further development:
Since the response was delayed, I tried some things on my end, particularly by replacing what I thought were the elements with which the software was prone to blocking the rendering. Suddenly, almost all the media linked to Adobe After Effects lost its connection to the project, and it did surprise me that this kind of thing hadn't happened, considering that when I switched to my new PC, I had to transition from an old version of Adobe software to the new versions in 2022. I had to convert the Adobe After Effects projects to the 2022 version, but strangely, the Premiere Pro project hadn't yet linked to the conversion of the projects to 2022; the links remained on my old Adobe After Effects 2018 backup. So right now, I'm doing a preview that should be finishing soon. Maybe relinking the media will solve this problem for me (I hope).
Well, I'm back,
I believed in it, but it was a false hope. I don't know what happened, but to test it, I did half of my film's rendering. The tests I was doing this afternoon were getting stuck around 60%, and now with the media that has been linked again in the correct version of the software, I managed to reach 93% rendering, but from there it gets stuck... I'm keeping my fingers crossed that you can send me a screenshot. I'm trying to figure out how I can tackle these issues because it's becoming really unbearable... This thing has been ruining my life for two days, I had other things to do this week, but as long as it's not resolved, I can't do anything.
Hello, the fact that there is no sync with the project, which is virtual as you know, can complicate things if you have changed PCs.
<pwhat i="" was="" suggesting="" on="" my="" end="" is="" to="" detect="" micro="" files="" so="" checked="checked" the="" cursor="" position="" once="" timeline="" extended="" which="" would="" allow="" us="" spot="" a="" break="" between="" two="" manifested="" by="" line.="">We can extend the timeline to the extreme; the line cannot escape us.
"Donkeys change their minds, imbeciles don't."
Please remember to mark "resolved" on your message if that's the case.
I see the two screenshots you just sent me, but is it really Adobe Premiere Pro in those screens? Because the interface doesn't look familiar at all.
So I'm coming back at this late hour to announce a new development regarding the project. After almost giving up on the fact that the H.264 render couldn't be done, I decided to run a test and render the first part of my short film as a JPEG sequence, and to my big surprise: the render completed in full, for a reason I can't explain. However, it was quite slow, but nevertheless, the render worked perfectly; I don't understand anything anymore... I still think it's a problem related to the project itself because it's not normal for the bug to be so nonsensical, so:
Unless someone finds a solution to address this issue, I believe that the editing of my project is indeed the final cut with indeed the final sound. I plan to render it as a PNG sequence to then associate a .wave audio track in a new folder. The two formats mentioned above are not compressed formats, so this will allow me to have an optimal render. And if for some unknown reason the render in another project doesn't work, I will come back to give you feedback again, but I would be very surprised since the render in MP4 worked very well on some parts of the project. Thank you for trying to help me, Glandu. If you think you know what the problem is with this new information, I remain open!