Casting / Playback Failures & Encoding Cache
Issue: Casting Failures and Transcode Cache Growth
1. Casting / Playback Failures
Some 4K videos cast fine, while others buffer every 2–3 seconds. The confusing part is that lower-bitrate files sometimes fail while higher-bitrate files play correctly.
What I observed
- ✅ Plays: HEVC Main10, bt709, clean CFR 59.94.
- ❌ Buffers: H.264 High or HEVC HDR10 (bt2020/smpte2084), sometimes variable framerate (~58.5 fps).
- When Immich transcodes:
- ffmpeg runs with Intel Quick Sync (QSV).
- Output is an uncapped CRF 4K60 stream which can still overwhelm Wi-Fi or the cast device.
- Tried adjustments:
- Advanced settings (B-frames 0, GOP 60, keyframe interval 60).
- Forced bitrate caps (10–20 Mbps).
- Lowered resolution (1080p).
- → Playback still inconsistent.
Question: How should Immich handle HDR/VFR files for reliable casting without forcing me to downscale or re-encode my entire library?
---
2. Encoded Video Cache / Storage Growth
- Originals: ~3 TB.
- Immich
2. Encoded cache is ballooning storage usage, so I'm wondering if its even worth doing once casting is fixed? Or maybe I just don't do this and get a device that can handle all formats and plug it in with an HDMI. Looking for guidance on best practices/configuration to solve both.
encoded-video cache already: ~600 GB.
- ~5,400 jobs queued > cache could add 1–2 TB more, nearly doubling total storage.
Concerns
- I don’t want pre-transcoding of the entire library if I can simply trancsode and cast appropriately.
Question: What is the recommended way to disable/prevent massive background transcode jobs and have Immich only generate and store on-demand playback copies? Is this a bad idea? I do have a pretty diverse library.
---
Summary
Two main issues:
1. Casting fails inconsistently (likely HDR/VFR handling, not just bitrate).2. Encoded cache is ballooning storage usage, so I'm wondering if its even worth doing once casting is fixed? Or maybe I just don't do this and get a device that can handle all formats and plug it in with an HDMI. Looking for guidance on best practices/configuration to solve both.
1 Reply
:wave: Hey @Pids,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.