• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support General Questions Casting to Chromecast Ultra not working via docker/Synology

     
    • 0 Vote(s) - 0 Average

    Casting to Chromecast Ultra not working via docker/Synology

    Video encoding profile + video resolution = no playback
    zutroi67
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2023 Dec
    Reputation: 0
    Country:Australia
    #1
    2024-07-07, 09:36 AM
    Sorry, I'm not sure where to start.
    I'm running Jellyfin in a docker container on my Synology NAS.
    I'm no genius, so setting this up to run was a bit of a personal nightmare. But thanks to excellent guides online, I managed to set it up and get it running nicely.

    After a recent upgrade (I'll list my versions below) I noticed that my Rick and Morty episodes were not playing. I have watched all of the episodes many, many times. I now get a weird error in a message box on my Samsung Galaxy S4 pad: "Playback Error: MessagePlaybackErrorundefined"

    My setup:
    Jellyfin 10.9.5 on Synology DS411+II (DSM6.2.4-2556 update 7) via docker (20.10.3-0554) container.
    FFMpeg4 (4.4.4-49)
    Chromecast Ultra (firmware 1.56.281627) via wifi
    Running from Samsung Galaxy Tab S4 tablet, Android 10
    Jellyfin Android app 2.6.1 with data on an external SSD for speed.

    I have narrowed down the problem: the video encoding profile and hence, the video resolution.

    To simplify, this WILL play:
    Format                                : AVC
    Format/Info                         : Advanced Video Codec
    Format profile                      : Constrained Baseline@L3.1
    Codec ID                             : V_MPEG4/ISO/AVC
    Bit rate                                : 1 889 kb/s
    Width                                  : 1 280 pixels
    Height                                 : 720 pixels

    And this WILL NOT play:
    Format                                : AVC
    Format/Info                         : Advanced Video Codec
    Format profile                      : Constrained Baseline@L4.1
    Codec ID                             : V_MPEG4/ISO/AVC
    Bit rate                                : 1 500 kb/s
    Width                                  : 1 920 pixels
    Height                                 : 1 080 pixels

    The same video, encoded with a different profile (maximum of HIGH@3.1) will play. Anything at level 4 or higher won't cast/play. This means that I can't play anything at a higher resolution than 720P. Videos I have always watched are no longer viewable, and the Jellyfin logs are as clear as mud.

    I have transcoding turned off as my Synology hardware isn't up to the task.

    This only started happening after the recent Jelly upgrade.
    I have been searching everywhere for help or to find others with my problem, but I cannot find help anywhere.

    Any ideas? As far as I can tell, the Jellyfin log doesn't list this error, or if it doesn't, I can't find it.
    zutroi
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2024-07-07, 02:31 PM
    The Chromecast Ultra supports up to, at least 1080P H264@level 4.2. So the codec level is not the problem.

    Can you share your jellyfin logs via pastebin?
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    theguymadmax
    Offline

    Community Moderator

    Posts: 1,210
    Threads: 0
    Joined: 2024 Jun
    Reputation: 62
    #3
    2024-07-07, 05:10 PM
    (2024-07-07, 09:36 AM)zutroi67 Wrote: My setup:
    Jellyfin 10.9.5 on Synology DS411+II (DSM6.2.4-2556 update 7) via docker (20.10.3-0554) container.
    FFMpeg4 (4.4.4-49)

    Your FFmpeg version is too old. Update to the latest.
    zutroi67
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2023 Dec
    Reputation: 0
    Country:Australia
    #4
    2024-07-08, 12:35 AM
    Sorry, the Jellyfin logs state:
    ffmpeg version 6.0.1-Jellyfin Copyright © 2000-2023 the FFmpeg developers

    The FFMpeg4 version is the Synology version installed (I've since updated that too.)
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #5
    2024-07-08, 02:32 AM
    I think 4.4 is new enough. But I'd still like to see the full logs so I can see what it is doing.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    zutroi67
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2023 Dec
    Reputation: 0
    Country:Australia
    #6
    2024-07-09, 01:29 AM
    Moat of the playing errors don't make it into the Jellyfin logs. I don't understand this. Is it the Android app failing to even start the send to the Jellyfin docker? Anyway, here is the log from yesterday that actually features a successful play of a file and several failed attempts. Further to my video profile theory, Jellyfin played a "high@41" profile 720P video yet failed to play another video of the same profile in the same video release series (same encoding, same settings.) I am completely at a loss. Thanks.

    https://pastebin.com/H1yEqwMU
    theguymadmax
    Offline

    Community Moderator

    Posts: 1,210
    Threads: 0
    Joined: 2024 Jun
    Reputation: 62
    #7
    2024-07-09, 02:23 AM
    Post your ffmpeg logs as well.

    You have the below error in your log, I don't think that's the cause of your issue, but you should go ahead and fix it.

    System.IO.IOException:The configured user limit (8192) on the number of inotify watches has been reached, or the operating system failed to allocate a required resource.
    • Go to Control Panel > Task Scheduler.
    • Create a New Task > Triggered Task > User-defined script.
    • In General Settings tab: give it a name (e.g. “sysctl inotify fix”) and Event = Boot-up.
    • In the Task Settings tab: enter this in the Run Command box:
      Code:
      sh -c '(sleep 90 && echo 204800 > /proc/sys/fs/inotify/max_user_watches)&'

    Source
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #8
    2024-07-09, 03:01 AM
    So you are using the ffmpeg built into Jellyfin. Good.

    Code:
    [2024-07-08 11:23:05.438 +00:00] [INF] [1] MediaBrowser.MediaEncoding.Encoder.MediaEncoder: Found ffmpeg version "6.0.1"

    Can you try turning on remuxing? A potato can remux, so your NAS should be able to handle that.

    Code:
    [2024-07-08 11:33:29.543 +00:00] [INF] [12] Jellyfin.Api.Helpers.MediaInfoHelper: User policy for "zutroi67". EnablePlaybackRemuxing: False
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    knorssman
    Offline

    Junior Member

    Posts: 1
    Threads: 0
    Joined: 2025 Jul
    Reputation: 0
    Country:United States
    #9
    2025-07-19, 08:15 PM
    I'm getting the same behavior.

    I don't have my jellyfin and android app version on hand, but I just recently installed and setup jellyfin for the first time and getting the android app to cast to my chromecast over the last few days, but i'm inconsistently able to detect the chromecast as a device i can cast to in the android app but i can detect and cast to the chromecast with youtube and google home just fine.

    it seems to me like the issue is related to the multicast system Sender -> Receiver communication to establish a session according to the chromecast dev guide diagram https://developers.google.com/cast/docs/overview
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode