You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When peertube runners are enabled for VOD transcoding on my 6.3.0 peertube instance, requesting a "Run HLS transcodes" from the videos Overview page causes the peertube runner to download a low quality version of the uploaded video file. This results in the 1080p version in the resulting HLS manifest to have very poor visual quality.
In this screenshot you will see that the 1080p version available for this uploaded video is only a little bit bigger than the 720p, but it should of course be around double the file size.
On a video that was uploaded to my peertube instance prior to 6.3.0, the 1080p version would typically be 2x the 720p file size. This video was the video uploaded prior to the ones that began showing this issue. It was when I was running 6.2.1:
You can see that the input file is low quality when running mediainfo on the file downloaded by the peertube-runner node when requesting the 1080p transcode:
Whereas, the actual uploaded original video's mediainfo output is:
General
Complete name : c6069b37-f678-485c-9f97-b34f1daf05d4-1080.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (mp41/isom)
File size : 5.12 GiB
Duration : 1 h 0 min
Overall bit rate : 12.2 Mb/s
Frame rate : 29.970 FPS
Encoded date : 2024-09-19 17:11:41 UTC
Tagged date : 2024-09-19 17:11:41 UTC
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings : CABAC / 1 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 1 frame
Format settings, GOP : M=1, N=30
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 1 h 0 min
Bit rate : 12.0 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 29.970 FPS
Minimum frame rate : 15.000 FPS
Maximum frame rate : 30.030 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type: Progressive
Bits/(Pixel*Frame) : 0.192
Stream size : 5.04 GiB (98%)
Encoded date : 2024-09-19 17:11:41 UTC
Tagged date : 2024-09-19 17:11:41 UTC
mdhd_Duration : 3619330
Codec configuration box : avcC
Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 1 h 0 min
Bit rate mode : Constant
Bit rate : 192 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 82.8 MiB (2%)
Encoded date : 2024-09-19 17:11:41 UTC
Tagged date : 2024-09-19 17:11:41 UTC
mdhd_Duration : 3619349
Steps to reproduce
Start a peertube-runner server node that is registered with the peertube 6.3.0 instance.
Navigate to videos Overview page on peertube
Select "Run HLS transcode" on an uploaded video where the original video file was preserved in object storage (i.e., uploaded after upgrading to 6.3.0)
Describe the expected behavior
I would instead expect the peertube runners to always download the original source file to use as the FFmpeg input, since this will produce the best quality results. Is there a way to do this in 6.3.0? If not I would personally label the current behavior as a bug, but if this is the intentional I would then be curious if there's documentation on how to prevent this lower quality version from being downloaded, in favor of the originally uploaded file stored on S3?
Additional information
PeerTube instance:
URL: gas.tube.sh
Version: 6.3.0
NodeJS version: v20.11.1
Ffmpeg version: 4.4.2-0ubuntu0.22.04.1
PeerTube Runner version: 0.0.21
The text was updated successfully, but these errors were encountered:
I have found that the problem is resolved if you replace the uploaded file in the video's "Update" page. It can even be the same exact file that was originally uploaded. I can't quite figure out why replacing the video file makes the runners behave properly so far, but I will keep digging.
Describe the current behavior
When peertube runners are enabled for VOD transcoding on my 6.3.0 peertube instance, requesting a "Run HLS transcodes" from the videos Overview page causes the peertube runner to download a low quality version of the uploaded video file. This results in the 1080p version in the resulting HLS manifest to have very poor visual quality.
In this screenshot you will see that the 1080p version available for this uploaded video is only a little bit bigger than the 720p, but it should of course be around double the file size.
On a video that was uploaded to my peertube instance prior to 6.3.0, the 1080p version would typically be 2x the 720p file size. This video was the video uploaded prior to the ones that began showing this issue. It was when I was running 6.2.1:
You can see that the input file is low quality when running
mediainfo
on the file downloaded by the peertube-runner node when requesting the 1080p transcode:Whereas, the actual uploaded original video's mediainfo output is:
Steps to reproduce
Describe the expected behavior
I would instead expect the peertube runners to always download the original source file to use as the FFmpeg input, since this will produce the best quality results. Is there a way to do this in 6.3.0? If not I would personally label the current behavior as a bug, but if this is the intentional I would then be curious if there's documentation on how to prevent this lower quality version from being downloaded, in favor of the originally uploaded file stored on S3?
Additional information
PeerTube instance:
4.4.2-0ubuntu0.22.04.1
PeerTube Runner version:
0.0.21
The text was updated successfully, but these errors were encountered: