![]() ![]() I've been using 2 pass Average Bitrate but would much prefer to use VBR 2 pass.Īm I doing something wrong? Can anyone shed an light on this for me please, I thought that using H.264 should give me this option. However, there does not seem to be an option for VBR for H.264 (MKV). Has some great features such as cropping, cutting, inserting chapters, direct copy, audio/video sync, pause, just to name a few. I found that XMedia Recode suits me the best at the moment - to convert Blu-ray TS movies to MKV - H.264. Tried just about every combination of settings to know avail. Handbrake and Media Coder (using High/advanced settings) converts won't play on my Blu-ray player. So far I've found that the commercial ones find it difficult to produce a full HD movie at a very small size with excellent quality. That sample is the original broadcast, untouched.I've tried just about every commercial video encoder on the net. Fox is shooting this in 1080p and upscaling in 4K, and I think the upscaling algorithm is going crazy and that's causing the blockiness. ![]() Ps - if you notice there's blockiness of the patches of grass before the play even starts (no one is moving on the field), that's not your imagination. I've noticed that even when I encode with x264 and give it a high bitrate, there's blockiness in fast motion scenes with football palyers. My question - what Xmedia Recode settings (using HEVC) can I use that will insert a new keyframe every 0.5 seconds and preserve the HLG in the file? Also, bonus points if you can recommend encoding settings that are good with fast motion. Just wanted to provide a sample of the type of video I'm working with). Here is a two minute sample file (this isn't the bad/temperamental file, this is actually the best recording I have, it has consistent iframes + I was able to edit it directly in avidemux without having to reencode it first. In any case, here are the are the Xmedia Recode HEVC and x264 settings I've tried. It's as if no new keyframes were ever added during the re-encode, the file is still damaged.ĭoing some more Googling, it seems that HEVC/x265 has an Open GOP by default.is this the issue that's causing the unsuccessful HEVC reencodes vs. When I've tried using Xmedia Recode with HEVC encoding settings, I do not get the same results vs x264 - no new keyframes are added to the re-encoded file, am not able to seek through the video in VLC/open and advance per keyframe via Avidemux. When I try to open this same damaged file in handbrake to see if handbrake can encode the original via x264, handbrake just crashes. ![]() That basically inserts new keyframes every 0.5 seconds - the file is basically repaired and I can remove commercials with avidemux. Other HEVC recordings come out fine and I can edit the files (without having to reencode the file) / advance to the next keyframe in avidemux without issue.Īnyways, the one solution I've found for even the most damaged file is just to reencode the damn thing with Xmedia Recode via x264, and tweaking the settings for Xmedia Recode to set 'Keyframe Interval' & 'Min GOP Size' to 30. Not all the recordings are like this, but some of them are. Some these recordings can be extremely temperamental - if you play it back in VLC, it plays fine, but if you try to open the file and seek through it, either in avidemux or VLC, it just crashes. I've done some Googling and it seems that HEVC supports HDR (and consequently - HLG?) while x264 does not. These broadcasts happen to utilize HLG, which is the dimentary form of HDR. Ah, memories.Īnyways, here is my conundrum - I have HEVC 2160p HLG files I've recorded (via Silicon Dust HDHomeRun). Hello - It's been a long damn time since I've been in the encoding world - I remember reading threads on Doom9 when x264 was first taking off back in 2006, and using MeGUI back in the day. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |