Search the Community
Showing results for tags 'render'.
Hi All, I'm was attempting to leave behind H.264 for H.265, but it's not as easy as I originally thought. When rendering out of Premiere 22.5.0 this newer codec seems a bit buggy. I can export a video as long as I don't mess with bit rate settings. and I keep it in VBR Good Quality. CBR is not working for me. I am attempting to render on a MacBook 2017 with Intel Core I7 processor. ( also tried on a newer 2021 M1 MacBook and I got the same results) What I would like to do is change my Bitrate Encoding to CBR and crank the Mbps to max, Change Quality to Highest, to get the best quality H.265 Video possible. However the software will either render to 100% and then freeze. or I will get an error message. Anyone have experience on this, is it time to ditch Premiere for Davinci? I've looked at a bunch of threads and nothing seems to be consistent. Thanks!
Strange problem I'm having. Maybe someone has seen this before and/or has some insight. I'm working on a shoot and did all the editing in FCP, then did my usual routine and sent to Apple Color from FCP. Loads into Color no problem, I do my grade, everything looks good. The render took waaaaaayyyy longer than I thought it should have for a 5 minute clip. But, figured maybe system resources were low or something. Roundtripped to FCP, and everything was black. Dug into the render files in the Color folder in Finder and all the files were black as well. All codecs are the same, settings, etc, as the stuff in FCP and I double checked other projects I've done successfully and all settings match. So I tried popping over a previous project into Color, same method, and just did a quick 4 second clip to check. When I popped that over into Color, nothing even shows up on the viewer. Scopes show everything as black. The clip in the timeline has a thumbnail on it, but not getting anything. I didn't even try to render anything because I just figured it would come back black, but, I've also never seen this happen before, so figured I need to fix something anyway. Is this something I can fix easily in settings somewhere? Or, should I just uninstall/reinstall everything. One weird thing that I did do differently maybe, was I had some graphic slates that we were using for titles, and they were rendering pixelated, so I read up and saw the animation codec is supposed to work better. I duplicated that sequence and tried it and confirmed, but this was not the sequence I sent over to Color. I didn't want to mess with anything just yet. So the Animation codec was only applied to a separate sequence. Could this have changed something in a global FCP setting somewhere? The settings for the sequence in FCP all read ProRes 422, 1080, etc, as well as Color settings. Very confusing and frustrating.