All Activity

Which Windows app version - I don't see it?

However, it says it's complete and it's not. Should say in progress as Atmos, DTSX, etc haven't been added yet.

On Emby 4.9.5.0, requesting an audio HLS stream with fMP4 segments produces a correct playlist whose segments cannot be fetched. Every segment request — and the init segment — returns: HTTP 500 "Object reference not set to an instance of an object." The same request with TranscodingContainer=ts works. Same code, same token, same track; the only thing that changes is the container. GET /Audio/{itemId}/universal ?UserId={userId}&DeviceId={deviceId} &MaxStreamingBitrate=192000 &Container=mp3,aac,m4a,flac &AudioCodec=aac &TranscodingProtocol=hls &TranscodingContainer=mp4 <-- ts works, mp4 does not &MaxSampleRate=48000 &PlaySessionId={uuid} &api_key={token} Follow the master playlist to main.m3u8, then request either the #EXT-X-MAP init segment or any hls1/main/N.mp4, carrying the auth query params through as usual. Retried over several seconds in case it was a transcoder warm-up: it is not, the 500 is immediate and consistent. Worth saying plainly: the playlist itself is authored correctly — version 7, an EXT-X-MAP pointing at init.mp4, segment durations, the lot. Whatever is missing looks like it sits between the playlist writer and the segment handler. Two small things that might narrow it down, or might be irrelevant — you'll know which: The ts and mp4 playlists are generated from the same request and differ exactly as you'd expect (version 3 vs 7, EXT-X-MAP present only on the second), so playlist generation looks complete. The 500 is identical for init.mp4 and for every media segment, which suggests it's one path rather than a per-segment condition. That's the whole report. I'm not asking for a feature here — just flagging that a route the server advertises can't be followed.

i found out that when i play the video via Emby App it's displayed correctly. but when i use the web link it rotates to the side. What do you need from me to investigate the issue?

Yes it is. However, I think that before I created a dummy playlist in Emby itself, it wasn't there. There seems to be a bug in Emby: the playlists are read and displayed within the music library (see the first image I attached), but they aren't actually added to the library until you create one within Emby.

Is it possible to add a feature to detect the EAC3+JOC (EAC3+Atmos) audio codec? Currently, they are identified simply as standard EAC3. Screenshot from Emby Screenshot from MediaInfo app

So back to square 1: Today even more posters are missing. In the log at at 04:30:34 when "Scan media library" happened: (I could not find any overlapping scheduled task which might interfered with volume2) Removing item from database, Type: Movie, Name: Ice Age - Surviving Sid, Path: /volume2/HyperActive/Video/Movies/Animation/... Removing item from database, Type: Movie, Name: Alice.In.Wonderland, Path: /volume2/HyperActive/Video/Movies/Animation/... Removing item from database, Type: Movie, Name: Bambi, Path: /volume2/HyperActive/Video/Movies/Animation/... Removing item from database, Type: Movie, Name: Finding Nemo, Path: /volume2/HyperActive/Video/Movies/Animation/... Removing item from database, Type: Movie, Name: Finding Dory, Path: /volume2/HyperActive/Video/Movies/Animation/... It seams that the Scheduled Task Scan media library deletes the movies and then reads them and probably runs in to an api block when scraping for cover art (its a big library). Any idea on why this is happening? Should I reinstall emby? embyserver (1).txt

I uninstalled EMBYIcons and restarted EMBY. I cleared the database. Then I restarted EMBY again. I ran all my scheduled tasks, and so far, no problems. I'll keep doing this throughout the week and let you know how it goes.

How can I help?

- the new version in Play Store - the transcoded target bit rate for audio

Hi @Luke — a couple of things worth flagging ahead of the new ffmpeg build, since they've come up in this thread: the root cause of the QSV 39 Mbps cap was traced (see jesposito's write-up and GitHub issue) to the model layer mapping the reported HEVC Level 5.1 to the wrong bitrate — the actual hardware supports much higher, as confirmed by direct ffmpeg testing. Separately, 10-bit HEVC hardware encoding via QuickSync also isn't currently offered in my case on my Intel 265K CPU, even though Arrow Lake-S's media engine officially supports 10-bit HEVC hardware encoding up to 8K/120Hz per Intel's own spec. Would it be worth someone on the team doing a full pass over the level/profile/bitrate mapping table rather than just these two spots, in case there are other entries that are similarly off or overly conservative? Is that mapping logic something that's getting revisited alongside the ffmpeg version bump, or is the beta build mainly a version update for now? Appreciate all of the hard work.

Thank goodness it’s not me, I’ve been restarting the server, computers all sorts and it persists.

0.0.0.6 uploaded Added username to logs to see who added Tidied Logging

The plugin is being worked on the first version was a bit crude, it had no progress bars and the settings page had some minor bugs. I have a better version here. EmbyVisionCredits.dll

HI, yes we are looking into it. Thanks.

Please check if the Playlist are available under Emby's libraries

1.1.50.0 Resolve playback error on some 2018-2019 models Merge Movies and Shows into a new Movies & Shows tab in mixed content libraries

Emby for LG: A new Release version is available Changes 1.1.50.0 Resolve playback error on some 2018-2019 models Merge Movies and Shows into a new Movies & Shows tab in mixed content libraries

Yes, the web client works. I see the bug which was introduced in 4.9.5.14. Looks like the same logic was shared between ET legacy and windows app version. It's not a show stopper but just wanted to flag it for the dev team.

Emby Android: A new Beta version is available Changes Cumulative Changes Since Stable Release Fix for some devices showing a gray video background instead of black Improve folder icon in folder views Various fixes related to submitted crash and error reports Support cancellation of initial connection process Add new spotlight home screen section option (requires Emby Server 4.10+) Fixes for initial connection process Support cancelling server connections while waiting Improve data refreshing when leaving the app and returning Fixes for Samsung Dex Support cancelling server connections while waiting Fixes for Samsung Dex Fixes for Samsung Dex Various subtitle rendering fixes

Hey that started happening for me yesterday with the latest beta windows app in all menus, movies, tv, collections. Trying to figure out whats happening. Web server shows them correctly.

Looking at the release notes on git, looks like 4.9.1.80 was the introduction of the fuzzy-search changes (Improve results of multi-word searches), so I'm assuming any version previous to this one will not have the issue. https://github.com/MediaBrowser/Emby.Releases/releases#release-4.9.1.80

Will what be fixed? Have you tried this on detail screens?

Then this should currently be working on detail screens

Will this issue be fixed in the next beta?