The file isn't much bigger than the H.264 files, which is surprising. TMPGEnc looks much better! It's not perfect, but in terms of playback on my PC, it's a lot closer to the source material. ![]() H.264 CBR and VBR have some blocking, but it's not nearly as bad. I looked at these clips several times on my computer. I then exported it in a bunch of different formats: I went ahead and created a 25 second clip where I noticed bad compression. If I don't find a nice exporting format soon, though, I think I will create a small clip and start uploading tests so that I can get feedback. I've been exporting the entire hour-long video each time because I want to get a good "feel" of how long an hour of video takes to process, and how much disk space it will consume. ![]() Question: For the ProRes file, it seems I can either upload the ProRes directly to YouTube (which should be very slow) or compress it to H.264 using Handbrake or something else. I'm now trying TMPGEnc H.264, and then after that I will try ProRes 422 LT. It still adds some blockiness compared to the original GoPro file, but it seems better than the VBR 75-100 Mbps. I suppose this is not surprising, since they're only 40 and 60 Mbps, while my original H.264 test was 70-100 Mbps. The first thing I noticed is that the HEVC (H.265) files have the worst blockiness. I've looked at the exported mp4s from yesterday's tests, focusing on a part of my video which is noticeably "blocky" in the mp4 output. Export to Apple ProRes and use that file in Shutter Encoder/HandBrake. I have not tested and compared all, but Shutter Encoder and HandBrake are both good and free. You can test a free trial version that has no watermarks. I am on Windows and choosed TMPGEnc Movie Plug-in AVC for Premiere Pro so i can export directly from the timeline. If i need H.264 i use a third party encoder. (Hence my recommenation for using Apple ProRes/GoPro CineForm for YT uploads.) Using a higher bitrate won´t solve it either and Adobe seems to ignore the issue or for example add the x.264 codec for pristine exports. It is great for static shots but falls apart quickly for non-static shoths. It fall apart pretty quickly compared to other encoders/codecs.īecause of this issue alone i never use Adobes own H.264 exporter. It has some serious issues when there is fine details and/or lot´s of motion in the image, as you already has encountered. ![]() Another thing to take into consideration is the built in H.264 codec in Premiere Pro. What CBR bit rate do you recommend for 4K 60?īy have not done any testings with 4K but i would start with a minimum of 100. Are there other settings in Premiere Pro I should try? When exporting with Premiere Pro, is a target/max bitrate of 75/100 good for 4K 60fps, or should I go higher? It's already taking multiple days for YouTube to finish the HD processing for my videos, so I haven't tested other bit rates. ![]() How can I decrease the compression artifacts?Īre there settings in the GoPro that can help? I'm using the GoPro's high bit rate setting, and have experimented with different levels of sharpness and other settings, but don't have a feel for which settings work best. So the faster I move, the more artifacts I get. When I am jogging, I get more artifacts than when I am walking. I'm noticing lots of compression artifacts (patches of blurriness) on YouTube, usually on distant trail surfaces, but also sometimes in the underbrush or on distant mountains. I then upload the exported video to YouTube, wait for HD Processing to finish, and view them in my browser on various computers and my 4K TV. I edit the videos in Premiere Pro, and then export them using VBR 2-pass with a target bitrate of 75 and max of 100. It's mostly walks and jogs on trails, nothing really wild in terms of movement. I've been recording 4K 60fps videos on my GoPro.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |