![]() |
Encoding Discussion Megathread (ffmpeg, Handbrake, AV1, etc...) - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Off Topic (https://forum.jellyfin.org/f-off-topic) +--- Forum: General Discussion (https://forum.jellyfin.org/f-general-discussion) +--- Thread: Encoding Discussion Megathread (ffmpeg, Handbrake, AV1, etc...) (/t-encoding-discussion-megathread-ffmpeg-handbrake-av1-etc) |
RE: Encoding Discussion Megathread (ffmpeg, Handbrake, AV1, etc...) - bitmap - 2023-09-04 I mean the LG C1 was the flagship OLED for LG and probably the best rated as far as picture quality goes. Granted, I don't have a 75" screen, so maybe that's where the difference comes in, but I've done a episode to episode comparison and come up pretty empty on what I can spot with an untrained eye. I've never had somebody point out the details I might be missing, though, so could just be I'm not paying attention to the right stuff? I also downmix to stereo because I don't have anything but TV speakers to work with. That's sacrilege to most folks, but until I have something that's going to support 5.1+ I'd rather get a better experience with what I have. Though I should probably add it as a separate track instead...hmmm... RE: Encoding Discussion Megathread (ffmpeg, Handbrake, AV1, etc...) - bitmap - 2023-09-07 I've made things much, much more complicated with a few tricks I'll share tomorrow. Got my A380 running with AV1, doing a three season 4K HDR batch encode, a five-movie 1080p collection, a three-episode anime OVA (new territory), and a 4K HDR DV Remux to stress test and see what happens with some new settings. Added some file naming changes with better bash variable substitution, a temporary way to get a stereo + 5.1 track, metadata replacement, default stream selection, maybe a couple other things... This is getting to the point where putting it in Python might be easier than rewriting the script each time. RE: Encoding Discussion Megathread (ffmpeg, Handbrake, AV1, etc...) - bitmap - 2023-09-07 Okay, so what I figured out after trying out a few things is that our friend nyanmisaka, as always, was right. The -global_quality flag doesn't work and causes issues a failure with the av1_qsv encoder. Works great with the hevc_qsv encoder, particularly when used with the -look_ahead option (suggest playing around there). So I tried -qp and everything worked just fine! Did a few 1080p encodes and the quality was alright and the compression was decent. So I tried a 4K encode and the quality was absolute garbage. I went back and watched through the entire 1080p encode and there were a LOT of issues. So I tried a MUCH lower QP value. And I got -- what I thought was -- roughly the same file size. Turns out it was the exact same file size because -qp has no effect. Same with -crf. So you can only run av1_qsv by specifying bit rates. Which pretty much kills my mass scripting aims, but this can still be used to batch encode series. The documentation for av1_qsv on the ffmpeg docs absolutely sucks. The options they have listed 100% do not work. So if you're looking to do any AV1 encoding with QSV, here are a few tricks I have figured out so far, with some nice ffmpeg and bash tips I threw in because I wanted to know how to do them! Hopefully this is helpful to somebody. I have a few things I want to figure out how to do and there are a few tricks in Python I know how to make happen that I don't know in bash (that might be possible) so I'll see what's up when I have a little free time. Code: for i in *.mkv; do \ RE: Encoding Discussion Megathread (ffmpeg, Handbrake, AV1, etc...) - bitmap - 2023-09-13 Anybody ever seen this message before? Code: [hevc_qsv @ 0x55c66c60ffc0] Space for SEI is not enough. One SEI will be skipped From what I can tell, SEI is generally extra information about encoding that isn't necessary for decoding and shouldn't be used as part of the spec, but I've seen it on a few different files I've encountered. Any way to ensure this data isn't lost when encoding, view it to see if it's even necessary, or drop it when encoding to avoid these messages? RE: Encoding Discussion Megathread (ffmpeg, Handbrake, AV1, etc...) - bitmap - 2023-09-16 Anybody ever deal with VC-1 video? I have some remuxes in VC-1 that I cannot for the life of me figure out how to deal with. Every decoder I've thrown at them fails. I get a seg fault/core dump with vc1_qsv, vaapi hates them as well and says the bit rate control option is unsupported, normal vc1 decoding errors out as well...everything I've found online says it's a weird, niche format and I've literally never run across it before now. Hoping to work through these whether I have to do a hybrid decode/encode or if I can go full hardware accelerated... Not sure if I'm talking to myself in this thread anymore. Might be the case. Occasionally screaming into the void is a good thing... RE: Encoding Discussion Megathread (ffmpeg, Handbrake, AV1, etc...) - TheDreadPirate - 2023-09-16 Intel dropped VC-1 in Arc. Even decoding. RE: Encoding Discussion Megathread (ffmpeg, Handbrake, AV1, etc...) - bitmap - 2023-09-16 Well that's a bummer. Any idea if Raptor Lake/UHD 770 supports it? As an aside...where do you find this info? I've been looking all over Intel's site and while Nvidia has a really simple matrix, Intel's documentation sucks. Guess I'll give the old-fashioned brute-force method a try. I can go back to the tool I was using previously to pay around a bit and see what results I can get. Appreciate the info that I was at a dead end... RE: Encoding Discussion Megathread (ffmpeg, Handbrake, AV1, etc...) - bitmap - 2023-09-16 Okay, well a couple hours of trial and error -- mostly due to me not sleeping -- and I have a working "script" for ab-av1 that I'm throwing at this series. Figured I'd share here. I have one I threw together for ffmpeg prior to this that I was going to try for a whole list of series that I put in a spreadsheet I started, but I need to modify based on what I've found out here... Code: IPATH="/path/to/input/media" && \ RE: Encoding Discussion Megathread (ffmpeg, Handbrake, AV1, etc...) - TheDreadPirate - 2023-09-16 (2023-09-16, 12:48 PM)bitmap Wrote: Well that's a bummer. Any idea if Raptor Lake/UHD 770 supports it? https://en.m.wikipedia.org/wiki/Intel_Quick_Sync_Video The UHD 7XX iGPUs do have VC-1 support. RE: Encoding Discussion Megathread (ffmpeg, Handbrake, AV1, etc...) - bitmap - 2023-09-16 Now why would I ever think good documentation should live on the manufacturer's website? |