Update: I checked upload times, the 1.7GB file was done on version 7.2.3 so it is possible the issue already were up after it.
I did upgraded from 7.2.3 to 8.1.4 on 4/4 15:07 (file was uploaded on 4/4 12:40) and then to 8.1.5 on april,16 11:19
Edited the previous messages to avoid version confusion. (note: will be nice to have the ~strikethrough~ for deleted text in forum markup )
it is only a little more than the original transcode (861.8MB on 8.1.5 vs 837.9 on 7.2.3) but it is ok, the transcoding was done.
It seems if the original file has the same resolution of the transcode, it is skipped altogether, stripping only the audio.
The GitHub issue is about a possible new option for admins, but I’m not sure whether I correctly understand the technical background.
We use the “PeerTube transcoding custom quality” plugin to render videos in high quality while keeping data usage manageable (CRF = 19).
As far as I know, videos used to be re-encoded in all formats. If someone uploaded a 1080p video in extremely high quality (which can mean 50 GB or more for one hour of footage), then when watching the video even in 1080p, only about 2 GB per hour would be transferred. Playback bandwidth was capped by the transcoded versions, which ensured that watching videos did not consume large amounts of data.
Am I correct in understanding that this is no longer the case in PeerTube 8.1.5?
This is still the case if PeerTube considers the input file’s bandwidth to be too high. However, PeerTube considers the input file bitrate of @Bly to be acceptable.