Close
Menu

Jellyfin

ffmpeg-official-logo

FFmpeg [aac @ ] Using a PCE to encode channel layout “5.1(side)”

, , , , , , , , , 0

If the source file signals a layout of 5.1(side) instead of 5.1, the AAC encoder will throw the error because the AAC spec only supports 5.1 (rear channels instead of side). The general cause of the problem is while transcoding to the AAC codec (Advanced Audio Coding) from various other high quality codecs such as AC3 (Dolby Digital/DD), E-AC-3 (Dolby Digital Plus/DDP/DD+), DTS, TrueHD (24-bit hd audio), it does not auto-select the standard 5.1 channel layout (called 5.1) if the original source has a channel layout of 5.1(side). While the AAC encoder may be able to automatically determine the amount of audio channels, FFmpeg has a hard time determining correct channel layout.

More

Jelly-banner-light_400x133

Jellyfin.Server.Middleware.ExceptionMiddleware: Error processing request: Request does not contain a token. URL GET /socket

, , 0

Problem: Jellyfin.Server.Middleware.ExceptionMiddleware: Error processing request: Request does not contain a token. URL GET /socket Solution: Configure your webserver software to correctly proxy the URI /socket to Jellyfin. Here is an example for NGINX: upstream jellyfin { server 172.18.0.1:8096; } server { location /socket { # Proxy Jellyfin Websockets traffic proxy_pass http://jellyfin/socket; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection “upgrade”; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Protocol $scheme; proxy_set_header X-Forwarded-Host $http_host; } } Full NGINX conf

More