Muehle 1 Posted June 24 Posted June 24 Hello emby Team, my setting: 2024-06-24 03:09:44.236 Operating System: FreeBSD 13.1-RELEASE-p9 n245429-296d095698e TRUENAS OS/Process: x64/x64 Emby Server version: 4.8.8.0 Operating system: Unix 13.1.9.0 my problem: Since updating to X, all new audio and video files are not indexed. When you open files the error message appears: Playback error - There are currently no compatible streams available. Please try again later or contact your system administrator for more information. the protocol: http://192.168.118.8:8096/emby/videos/2596/live.m3u8?DeviceId=bdc4569d-2784-4377-a0ea-28cffa6ac3e8&MediaSourceId=df52a89d072cfedf6cfdeba5955f8bf6&PlaySessionId=1d63de950b3842e8ae1c93a179588128&api_key=x_secret1_x&VideoCodec=h264,av1&VideoBitrate=200000000&MaxWidth=3840&TranscodingMaxAudioChannels=2&SegmentContainer=ts&MinSegments=1&BreakOnNonKeyFrames=True&SubtitleStreamIndexes=-1&ManifestSubtitles=vtt&h264-profile=high,main,baseline,constrainedbaseline&h264-level=52&TranscodeReasons=VideoCodecNotSupported,DirectPlayError&allowVideoStreamCopy=false&allowAudioStreamCopy=false {"Protocol":"File","Id":"df52a89d072cfedf6cfdeba5955f8bf6","Path":"/media/Video/Anleitung/Handwerk/Heimwerker-Silikonfugen_2024.mp4","Type":"Default","Container":"mp4","Size":0,"Name":"Heimwerker-Silikonfugen_2024","IsRemote":false,"HasMixedProtocols":false,"SupportsTranscoding":true,"SupportsDirectStream":true,"SupportsDirectPlay":true,"IsInfiniteStream":false,"RequiresOpening":false,"RequiresClosing":false,"RequiresLooping":false,"SupportsProbing":false,"MediaStreams":[],"Formats":[],"RequiredHttpHeaders":{},"AddApiKeyToDirectStreamUrl":false,"ReadAtNativeFramerate":false,"ItemId":"2596"} Activating the Jails Update in TrueNAS is not updating the FreeBSD Version of the Jail. After the update the version is 13.1-RELEASE-p9 but should be 13.2-RELEASE-p11. It looks to me like the Emby Server version: 4.8.8.0 update doesn't work on FreeBSD 13.1-RELEASE-p9. A workaround could be a manual update of FreeBSD via the jail shell, but this hasn't worked for me so far. my question: 1. Can someone with TrueNAS experience tell me the necessary shell commands so that I can update the BSD 2. Can the team update the jail so that a current BSD is installed during an update and the errors no longer occur? thanks for answers!
Happy2Play 9060 Posted June 24 Posted June 24 Know nothing about this platform but there are serveral topics on No Compatible Streams with upgrade instructions. Does this help?
Muehle 1 Posted June 25 Author Posted June 25 I executed the command Quote whereis iocage and got: iocage: /usr/local/iocage /usr/local/man/man8/iocage.8.gz than i run the following command Quote iocage upgrade -r 13.2-RELEASE emby and got: Branch 13.3-RELEASE does not exist at https://github.com/freenas/iocage-plugin-emby.git! Using "master" branch for plugin, this may not work with your RELEASE running upgrade... 13.2-RELEASE is missing src.txt, please refetch! Question: How can I create the refetch and how can I set the repository to truenas?
Luke 38499 Posted July 18 Posted July 18 @Muehlewere you able to figure this out? Are you still having an issue with this?
Muehle 1 Posted July 19 Author Posted July 19 @LukeI made an update by changing emby to the beta-channel. Since I made the Beta update the ffmeg error is gone - but - Emby is no longer able to add trailer pictures to the indexed films independently. I use Emby as a TrueNas extension. Maybe you can update the TrueNas Emby jail so that I get a fully functioning version again when I update?
Luke 38499 Posted July 20 Posted July 20 8 hours ago, Muehle said: @LukeI made an update by changing emby to the beta-channel. Since I made the Beta update the ffmeg error is gone - but - Emby is no longer able to add trailer pictures to the indexed films independently. I use Emby as a TrueNas extension. Maybe you can update the TrueNas Emby jail so that I get a fully functioning version again when I update? Hi there, can you please provide a specific example? Thanks.
Muehle 1 Posted July 22 Author Posted July 22 @Lukehere you can see the indexing before the update (orange high.). Emby automatically creates an image from the video for the overview. Since the update this function is no longer working. Now the content image is missing and new videos have an icon. You can add the content image manually but I would like it to be as good as it was before the update when Emby did it independently. I have the same error with all updates I have made.
Luke 38499 Posted July 22 Posted July 22 8 hours ago, Muehle said: @Lukehere you can see the indexing before the update (orange high.). Emby automatically creates an image from the video for the overview. Since the update this function is no longer working. Now the content image is missing and new videos have an icon. You can add the content image manually but I would like it to be as good as it was before the update when Emby did it independently. I have the same error with all updates I have made. Hi, what image fetchers are enabled on the library?
Muehle 1 Posted July 23 Author Posted July 23 tump graphics are automatically added. The scan is also set to automatically add to new media. I hadn't changed the configuration since the update and the problem has been there since the ffmpeg error. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now