jellyfin / jellyfin-roku

The Official Roku Client for Jellyfin
https://jellyfin.org
GNU General Public License v2.0
451 stars 141 forks source link

MP4s with H264 video and GPAC ISO Audio Handler - AAC audio fail to play #728

Open karimw786 opened 2 years ago

karimw786 commented 2 years ago

Describe the bug Much of my movie library (MP4s with H264 video and GPAC ISO Audio Handler - AAC audio) is stored on Google Cloud and mapped to my Jellyfin server (version 10.8.1) using RClone (version 1.59). Whenever I try to play these files via the web client, they work fine, but whenever I try to play them via the Roku client (version 1.5 build 0), they video appears to buffer for a moment, but then I get an "Error Retrieving Content" error.

To Reproduce

  1. Add movies (MP4s with H264 video and GPAC Audio Handler - AAC audio) on Google Cloud
  2. Map Google Drive drive via rclone and add this drive to a library on the Jellyfin server
  3. Attempt to play any video via the Roku Jellyfin client
  4. See error

Expected behavior The videos should play, as they do the in web client

Logs [2022-08-03 17:42:50.692 +05:00] [INF] User policy for "MyUsername". EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True [2022-08-03 17:42:50.695 +05:00] [INF] StreamBuilder.BuildVideoItem( Profile="Anonymous Profile", Path="/home/myusername/Videos/Online-Movies/GDrive/South Park - Bigger, Longer and Uncut (1999).mp4", AudioStreamIndex=1, SubtitleStreamIndex=-1 ) => ( PlayMethod=DirectPlay, TranscodeReason=0 ) "media:/videos/d03e0627-d69b-7656-f441-4db05fdfec12/stream.mov?MediaSourceId=d03e0627d69b7656f4414db05fdfec12&Static=true&VideoCodec=h264&AudioCodec=aac&AudioStreamIndex=1&api_key=&SubtitleMethod=Encode&Tag=b127a79ef4d9c0c02e993216c98797bf" [2022-08-03 17:42:55.345 +05:00] [INF] Lost 1 WebSockets. [2022-08-03 17:43:12.824 +05:00] [INF] Playback stopped reported by app "Jellyfin Roku" "1.5.0" playing "South Park: Bigger, Longer and Uncut". Stopped at "0" ms

1hitsong commented 9 months ago

@karimw786 Is this still an issue using the latest release?