Multiple source videos (different cellphone footage) never "yellow" always RED slow export

Here's my settings in Handbrake. This is their latest release, same as always.

MediaEncoder comes as part of the Premiere Pro setup, as it is the main heart of Premiere's export/render capablities, and where you create encoding/proxy presets and such. No extra charge. But it doesn't do a proper job of changing VFR to CFR.

Neil

Does not look like you are editing HD. Sequence is set to SD interlaced.

And then upscaling it to HD 720p.
If you dont have a dedicated videocard then yes all will be red, and will continue to do so after each edit.

Phillip's comments about phone media are key here. That format is recorded in-cams via specially designed chips to cut the amount of data recorded dramatically and to do it fast. It is total garbage to edit with on many systems.

And ... as also noted, it's VFR ... variable frame rate. The audio is recorded 'continuously', but no matter what video frame-rate you set, the camera never shoots that frame rate.

What it does is decide if, due to motion of the image, it really needs to create another frame. Set the camera to say 30fps, and in reality, the number of frames recorded changes every second. So the 'effective' frame-rate may vary between 27.92 and 31.4 fps for one example from my phone.

That's one headache for an NLE, and the app needs to create frames for all the skipped ones, and drop frames where there are too many.

Next, besides that hassle, it's long-GOP. So the vast majority of 'frames' aren't even actual frames, they're just data-sets of parts of a frame. As in, the pixels that have changed since the last actual frame (i-frame), or before the next i-frame, or ... both.

So we're not talking about playing frames here, we're talking about creating them nearly out of whole-cloth, and piecing/mixing/matching bits of multiple frames and data sets to create frames in real-time.

Along with the cuts and other effects you as the editor are adding to the media.

Yea, it's a mess.

So at least converting phone media to "regular" H.264 that is CFR, constant frame rate, is a huge uptick in working process. And can be done easily and quickly in a batch process with the free utility app HandBrake.

As a batch, do it in groups or full folders of media like overnight before you're going to work with it, or while you're at lunch.

Neil

There may be a couple different things going on here.

For starters, is your GPU active as your renderer? (File>Project Settings>General) it should be CUDA and not Software Only.

Do your sequence settings match the source footage? Regardless of performance your export shouldn't be low quality unless something is wrong with your sequence settings or your export settings. Did you have to scale your media up or down when you put it in the sequence? What export settings are you using? It's usually very helpful to post a pic of export settings and be sure to include the summary area.

You should also know that video from a phone is usually plagued by a lot of issues. If it's in the HEVC codec, which most 4k video will be in (usually an .mov container) then it's going to play like garbage. It's a terrible codec for video editing. (H264 isn't great either, but HEVC is worse.) And furthermore, most phones will shoot variable framerate, which is also terrible for editing and causes audio sync issues. It's not uncommon when working with videos from a phone to need to transcode in some way - either via Adobe Media Encoder to get it into a better editing codec, or via Handbrake to correct the variable framerate while preserving audio sync.

Note that when you render in the sequence that's only going to assist with playback in the program and it won't have anything to do with your export unless you check the 'Use Previews' box on exporting. I wouldn't recommend checking that unless you are creating high quality video previews. To learn more about that you can look up "Smart Rendering"

I can't edit the post so I'll reply instead. The final export video is suppose to be 720p, looks like 240p and get this, the size is almost 200MB ...............