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
nextcloud was installed via Docker AIO, for some time transcoding via integrated graphics worked well, both with and without a external transcoder container (with the addition of the launch parameter --env NEXTCLOUD_ADDITIONAL_APKS="intel-media-driver ffmpeg" ). After some update, both methods stopped working.
Steps To Reproduce
Go to memories with transcoding enabled via VA-API
without external transcoding container:
Since nextcloud is installed via docker, it is problematic to look at specific logs; the server log contains the following error: Transcode failed: Transcoder returned 408
The text was updated successfully, but these errors were encountered:
Describe the bug
nextcloud was installed via Docker AIO, for some time transcoding via integrated graphics worked well, both with and without a external transcoder container (with the addition of the launch parameter --env NEXTCLOUD_ADDITIONAL_APKS="intel-media-driver ffmpeg" ). After some update, both methods stopped working.
Steps To Reproduce
Platform
Screenshots
No response
Additional context
-When the external transcoding container is enabled:
Logs inside the container:
without external transcoding container:
Since nextcloud is installed via docker, it is problematic to look at specific logs; the server log contains the following error: Transcode failed: Transcoder returned 408
The text was updated successfully, but these errors were encountered: