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
Currently, all newly uploaded videos are failing transcoding with the message, "Output format mp4 is not available." I've attempted to do a simple re-encode and output to mp4 using ffmpeg but it does not fail, it only seems to fail when PeerTube processes them.
I was running version 6.0.1 but upgraded to version 6.1.0 hoping that would fix this issue but it did not have any effect.
Job: 8ce294ce-86b9-41b2-ab72-a221b1cc1868 Type: video-transcoding Processed on 5/30/24, 3:01:18.619 PM Finished on 5/30/24, 3:01:18.761 PM
--
{ "type": "new-resolution-to-hls", "videoUUID": "388582ab-3dc0-4157-8a12-83702d0a6306", "resolution": 360, "fps": 25, "copyCodecs": false, "isNewVideo": false, "deleteWebVideoFiles": false }
Error: Output format mp4 is not available
at /var/www/peertube/versions/peertube-v6.1.0/node_modules/fluent-ffmpeg/lib/capabilities.js:589:21
at nextTask (/var/www/peertube/versions/peertube-v6.1.0/node_modules/async/dist/async.js:5791:13)
at next (/var/www/peertube/versions/peertube-v6.1.0/node_modules/async/dist/async.js:5799:13)
at /var/www/peertube/versions/peertube-v6.1.0/node_modules/async/dist/async.js:329:20
at proto.availableFormats.proto.getAvailableFormats (/var/www/peertube/versions/peertube-v6.1.0/node_modules/fluent-ffmpeg/lib/capabilities.js:513:14)
at /var/www/peertube/versions/peertube-v6.1.0/node_modules/fluent-ffmpeg/lib/capabilities.js:568:14
at nextTask (/var/www/peertube/versions/peertube-v6.1.0/node_modules/async/dist/async.js:5791:13)
at Object.waterfall (/var/www/peertube/versions/peertube-v6.1.0/node_modules/async/dist/async.js:5802:9)
at Object.awaitable [as waterfall] (/var/www/peertube/versions/peertube-v6.1.0/node_modules/async/dist/async.js:212:32)
at proto._checkCapabilities (/var/www/peertube/versions/peertube-v6.1.0/node_modules/fluent-ffmpeg/lib/capabilities.js:565:11)
at /var/www/peertube/versions/peertube-v6.1.0/node_modules/fluent-ffmpeg/lib/processor.js:298:14
at nextTask (/var/www/peertube/versions/peertube-v6.1.0/node_modules/async/dist/async.js:5791:13)
at Object.waterfall (/var/www/peertube/versions/peertube-v6.1.0/node_modules/async/dist/async.js:5802:9)
at Object.awaitable [as waterfall] (/var/www/peertube/versions/peertube-v6.1.0/node_modules/async/dist/async.js:212:32)
at proto._prepare (/var/www/peertube/versions/peertube-v6.1.0/node_modules/fluent-ffmpeg/lib/processor.js:295:11)
at proto.exec.proto.execute.proto.run (/var/www/peertube/versions/peertube-v6.1.0/node_modules/fluent-ffmpeg/lib/processor.js:431:10)
Ffmpeg version: N-70079-gdf868bae23-static May 4 build (downgraded to this suspecting it was the issue, but it was not; issue also occurred in May 24 build)
Browser name, version and platforms on which you could reproduce the bug:
Link to browser console log if relevant:
Link to server log if relevant (journalctl or /var/www/peertube/storage/logs/):
The text was updated successfully, but these errors were encountered:
Is it possible peertube somehow caches something to do with ffmpeg?
Upon restarting the peertube process to load the updated log.level parameter, it began working again.
Describe the current behavior
Currently, all newly uploaded videos are failing transcoding with the message, "Output format mp4 is not available." I've attempted to do a simple re-encode and output to mp4 using ffmpeg but it does not fail, it only seems to fail when PeerTube processes them.
I was running version 6.0.1 but upgraded to version 6.1.0 hoping that would fix this issue but it did not have any effect.
Steps to reproduce
Describe the expected behavior
Transcoding succeeds
Additional information
PeerTube instance:
Browser name, version and platforms on which you could reproduce the bug:
Link to browser console log if relevant:
Link to server log if relevant (
journalctl
or/var/www/peertube/storage/logs/
):The text was updated successfully, but these errors were encountered: