My exported video have a green line in the bottom of the frame
-
-
- Offizieller Beitrag
Does this also happen with version 2.3?
-
- Offizieller Beitrag
-
I want to do it in 21:9 for a cinematic view, it's fine without Voukoder plugin export. It should work with any optional resolution because I don't want to lose much detail. Anyway, I upload to 2.3 version (and install connector stuff) and log file section disappear
-
Log file can be found in the voukoder tray icon now.
-
Log file can be found in the voukoder tray icon now.
I did not see it
-
You have to open the voukoder settings window, then the icon should appear.
-
Could you explain why my card doesn't support NVENC x265? only available H264 NVENC?
-
-
Thanks
-
Vouk
9. Dezember 2019 um 10:46 Hat das Label In Bearbeitung hinzugefügt. -
Vouk's right about height divisible by 8 requirement (and width divisible by 16). It has to do with macroblocks & compression.
You might get away with resolution that doesn't adhere to these requirements, but it's a bit of a lottery.
Depending on the codec, format and how Youtube's ffmpeg-based encoder processes it, it might end up with a green line too.
I've bumped into this issue myself a couple years back with Cineform codec, which requires width/16 & height/8 rule otherwise it gets that bottom line when played back in anything but Adobe.
3840x1600 is a good choice, it's 2.40:1 which is pretty much the same as 2.39:1 cinemascope (which is just a legacy of analog film/projection era)
21:9 is just a marketing number used for monitors and phones. The existing ultra wide resolutions in things like consumer monitors aren't exactly 21:9 and they still adhere to the rule, like 2560x1080 (2.37:1), 3440x1440 (~2.39:1) and 3840x1600 (2.40:1)
In cinema mastering / intermediate , they don't have to care about conforming to standard resolutions because it's exported as separate frames.
But when delivering, they adjust it to meet requirements.
-
Vouk
9. Dezember 2019 um 15:11 Hat das Label von In Bearbeitung auf Kein Bug geändert. -
Vouk
22. Februar 2022 um 20:59 Hat das Thema aus dem Forum Bug reports nach Closed verschoben.