7/28/2023 0 Comments Streamlabs obs quicksync green![]() As I see, there is two versions of recorded footage with B-Pictures (VCE2, VCE3) and without B-Pictures (VCE1, VCE3.4) - last marked as NoBPictures. Speed preset has lower overall quality and thus this keyframes appearance are smoother, but still bad (well noticeable at timeline from 00:01:01 to 00:01:18, when hero "landing"). When overall quality is better, this bad keyframes insertion completed in timeline makes video even worse than it was for Speed preset (maybe keyframes size or time are bad?). Second, Quality presets for AMD I excluded because of this dammit temporal degradation. But temporal artifacts (there I mean visible keyframes insertion - whole image just replaced with same picture but different quality) are make AMD videos out of the list in comparison to other hw based encoders at 2000. Result close to simple - stream - QSV_Skylake bitrate=2000 preset=speed.mp4 (7) - I didn't place it in the chart table because Quality preset is better for Intel as it was mentioned by me earlier. Less blocking, same range and color space. Respect to all who helped and points you.). Want to say a few words about AMD encoder (as it arrived last and from the second try).įirst, AMD_VCE1415_NoBPictures (9) and AMD_VCE1415 (8) files - results are much better, than first examples I saw (thanks to !!! Well done. Now the rating is (almost the same as previous):Īll tests results is by my own perception of the footage.Īll previous comments are still true. simple - stream - QSV_Skylake bitrate=2000 preset=speed.mp4.simple - stream - QSV_Skylake bitrate=2000 preset=quality.mp4.simple - stream - QSV_IvyBridge bitrate=2000 preset=balanced.mp4.simple - stream - QSV_Skylake bitrate=2000 preset=balanced.mp4. ![]() simple - stream - NVENC_Kepler bitrate=2000 preset=highquality.mp4.simple - stream - NVENC_Pascal bitrate=2000 preset=highquality.mp4. ![]() simple - stream - x264 bitrate=2000 preset=veryfast.mp4.It just currently takes way to long to do these manually, it would be ideal if I somehow could tell OBS to only record x seconds using the commandline. I can provide these for 1280x720xx1080x30 too if needed. One of them has the VBV Buffer Bug, but I'm not sure if it's decoding or encoding that has the bug - needless to say it will probably rank at the bottom, being the worst of them all.ġ280x720x30, without B-Pictures (VCE1, VCE3.4)ġ280x720x30, with B-Pictures (VCE2, VCE3) Here are files with Partial range, both with and without B-Pictures to represent the full range of AMD hardware capable of encoding. The comparison and rating of my script is correct regardless the full range, because ffmpeg correctly takes the color range in account. If your videos were partial and the media players process them as full, the darker parts would be too light instead of too dark. Your videos are definitely full range, otherwise the media players would not make the darker parts too dark. The same frame displayed with the media players give wrong colors. Ffmpeg, on the other hand, correctly identifies and processes as full range, which you can see by the fact that if you export a frame as png with ffmpeg, the png has correct colors. They both black out the darker parts, which means they process the footage as partial, while it is in fact full color range. Media Player Classic and the "Movie & TV" app from Windows 10 cannot display the colors from your videos correctly. Intended? MediaInfo says this, and ffprobe as well. ![]() The color range is still full, not partial. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |