![]() ![]() That is not true they just do not make it available for download. It is fairly well known that YouTube output quality gets better with the most quality you can tolerate to upload. ![]() (h264_nvenc gave me 60 Mb/s.) Some organizations use 100 Mb/s for an intermediate or mezzanine, which is essentially what this is. MediaInfo reports the average bitrate of this as 29 Mb/s, which is not that big IMO. I just made a test from 1080p60 footage using libx264 and it played fine for me in VLC. This jobs runs it through ffmpeg to decode it and report errors, for example: ffmpeg -xerror -err_detect +explode -v info -i I:/testing/test.mp4 -f null pipe: When the job completes, double-click the job to view its log. If you want to check the integrity of a file, open it in Shotcut and choose Properties > menu button > Start Integrity Check Job. I have seen VLC struggle with 4K UHD or other high bitrate on some systems perhaps depending on hardware accelleration. Just because VLC has trouble with throughput does not make it invalid. If a user wants to export a H.264 video with decent quality for his own archive, isn't that what H.264 Main or High Profile with a GOP of 149 is for? Yes, YouTube Video quality is absolute crap for scenes with complex movement, but what is the point in uploading 10 times the data if it doesn't show on the target platform? At 70+GB, size really starts to matter. Is it really wise to do that for an export format that is primarily intended for uploading stuff to a video platform? I mean, YouTube will process the uploaded data so that it comes close to their own recommendations - IIRC only this re-processed video is available for download if the uploader ever chose to do that, they don't keep the original data. (I didn't report this as a bug since the YouTube preset video size seemed impractical anyway.)Ģ.) The YouTube preset takes up even MORE space than H.264 Main Profile, since YouTube recommends GOP 15. ![]() ![]() I can try to reproduce this and put up an example+project+VLC messages if you're willing to look into this. The problem only went away once I reduced quality to get about half the original bitrate. VLC complained about various issues in the video data stream. video players would only play the first few seconds of a gigantic 70GB+ export. I understand your intention, but I would kindly ask you to reconsider this decision for the following two reasons:ġ.) I actually ran into serious problems with invalid video being exported using the default YouTube settings i.e. None of the few other codecs I briefly tried came even close to YouTube bitrate recommendations. In order to obtain a resonabl bitrate of ~10Mbit/s for full HD video with h264_qsv, I have to set Quality to about 10% (and in my case, this actually looks close to what YouTube provides). if the global_quality preset 59% is passed to h264_qsv, this results in close to 10 times the desired bitrate, also exceeding the bitrate of the original material by far. Is this a bug in the codec confugration or simply a wrong quality setting?Īfter examining the logs of several exports, I think this may be codec dependent e.g. Other settings of the YouTube preset seem to match YouTube's recommendations exactly. I am not talking about "spikes" in the VBR stream here, but on the average bitrate of the whole file. When exporting a 1080p video with the YouTube preset, the resulting files are ridiculously big - and the video bitrate exceeds recommendatons by far (up to a factor 10) - regardless of the input material (tried in at least 5 different projects). Shotcut 19.07.15 Windows 10 (broken on older versions too)Īs stated on the recommended bitrate for 1080p video SDR is 8 Mbit/s (HDR: 10Mbit/s). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |