All Activity

Emby can show one active recording while multiple upstream tuner/provider connections remain actively in use. I caught this live tonight and was able to verify both Emby’s internal consumer state and the actual network traffic while it was happening. Environment: Emby Server 4.10.0.40 on macOS using an M3U tuner. At the recording boundary, the server log showed three recording timers firing for the same program on three different channels: 19:00:00.104 Recording timer fired ... [PROGRAM] (3 times) 19:00:00.111 Getting media sources ... [CHANNEL A] 19:00:00.111 Getting media sources ... [CHANNEL B] 19:00:00.112 Getting media sources ... [CHANNEL C] Those recording jobs attached to existing shared streams, bringing each stream to two consumers. When the previous recordings ended, Emby removed those consumers, but the three affected streams only dropped back to one consumer each, so all three remained open: Live stream [A] consumer count is now 1 Live stream [B] consumer count is now 1 Live stream [C] consumer count is now 1 A separate stream behaved normally: Live stream [D] consumer count is now 0 Closing live stream [D] I also verified the three remaining connections at the TCP level. They were ESTABLISHED and actively transferring MPEG-TS data, so these were not stale sockets. The shared-stream/tuner logic itself appears to be behaving correctly: Emby still believed each stream had an active consumer. The issue therefore appears to be higher up in the recording/timer state rather than in tuner release itself. The practical concern is that the UI showed one active recording while three provider/tuner connections were actually in use. This matters for IPTV users with concurrent-stream limits. If a provider allows two connections, for example, a hidden consumer can occupy one of those slots and cause another recording or Live TV session to fail even though Emby appears to show available capacity. Main question: why were multiple recording consumers created for one logical airing while the UI represented only one active recording?

OK we are looking into it. Thanks.

@rax_ydoes this resolve it for you?

Hi, please show the complete file names. Thanks.

I have 4.10.1.0 x86_64 on DSM 7.4.1. I started using the Radeon theme media plugins and there are a handful of movies where both theme.mp3 and theme.mp4 are present, but neither of them get triggered. 99% of them work without issues, but there is a handful of them that just won't work. The files are there, the naming convention is exactly the same as the rest of the movies... yet they won't reproduce, either on web, on Windows, or on Android... I've tried removing identification, then doing a library scan... refresh metadata... and for these particular movies it doesn't refresh: I have to manually identify them... but still neither the mp3 nor the mp4 get picked up. The files are there, but they don't play. Interestingly enough, it seem that this is happening with the movies that gave me issues HERE. I had to rename folders, reorder stuff, etc. to put them as I wanted again, but got it fixed after some work. But now those files are giving me issues with themes... Example: The theme.mp4 is inside backdrops. At some point I thought that the issue was that the theme music/video weren't working on movies that had more than one version, but then I checked a recently added movie with 2 versions in it, and that one worked OK. Due to this, I believe that it might be that the database entries for those specific movies got corrupted at some point, and now just don't work very well, even when removing the movie identification, and re-adding it. I have removed the identification of a movie, moved its folder out of Emby, did a library scan, then a vacuum with reboot, then a library scan again, then moved that movie back in, scanned it... it detected it... but still theme.mp3 is not playing! Is there a way to remove those specific movies "more completely" from the database, so as to try to re-add them "as new" and get those themes working? I'll put logs here at a later date, once I've experimented a bit more, but yeah... just wanted to know if anyone else was having similar issues. Cheers!

@SamES

Indeed. Good to know, and I guess it leads us back to the original problem. If there's any logs or ffmpeg calls I can run to help debug the transcoding start time offset, let me know.

@ColinPostsHeretry refreshing the metadata on the album. if the issue persists after that, then please attach the emby server log. Thanks.

How does one get this to appear on the posters?

Yeah I know the Aliens are coming Emby.mp4

It’s possible that they are supported in some fashion. But they don’t publish those details beyond just saying that a certain format is supported.

Very, VERY simply explained at its core, AI is just a massive collection of weights (numbers) that adjust how information flows through a system. Basically a word weight machine. What i mean is, let's say you write "Let's go for a ...." the AI will then look for words that could match by giving them a weight, the higher weight the more likely the next words is. So in this case "walk" will most likely weigh the highest because it comes next to the sentence the most in it's database and will there for be used by the AI as the next word. Basically a fancy algoritme. There is no intelligence behind it. If i remember right the first programs that could guess the next number in a "2 - 4 - 6 - x" using that method was actually made in the late 50's. Think chess computers. After that it was mostly a question of more powerful CPU's and enough storage for it to work. Of cause there is more to it than that but that is just a VERY simple explanation. If you want truly amazing stuff in computers then look at how they make chips today. "Any sufficiently advanced technology is indistinguishable from magic" Just because you can't explain it or imagine how it works doesn't mean it's magic or indeed alien.

No matter what anyone says I can never believe we as humans made this AI tech, no way not doable not under any way shape or forum we just are not there yet.

There is no way in hell us Humans made AI just no way, we arent smart enough this is tech from another world

Same. It seems Opus has always been transcoded to this TV. It made me curious so I tried to play both Opus and Vorbis through the stock LG Music app too and both file types threw errors that they were not supported, even though I was fairly certain at least Vorbis was officially supported for webOS24.

I don't believe AI was made by us we just are not told the real story, there is no way we are smart enough to make this Ai no way We just can't build this we can't, this is Alien AI.mp4

Working on another video cost like $30 a video hopefully it looks ok when is done

Installed it today been on it all day you get hooked easy, suck at making videos but whatever Video.mp4

The ideal will be to have extras at: Show Level Season Level Episode Level

@Lukeadditionally: Imagine doing it on Shows with hundreds of official Specials like Doctor Who 2005 with 169. I have to scroll down to the bottom to find an Extra ? When maybe I only have 3 of them that no one has put in TheTVDB ? Or the opposite, I configure no Season Folders and I see 169 Specials + 3 Extras in a row. Has no sense at all.

How difficult is to understand that: A Season 0 Episode (Aka Special): Can be: a) Episodic Special b) An OVA c) A Movie d) Season Recap e) Webisodes and Shorts f) Uncategorized All the above is from TheTVDB Rules on Episode Categorization for Season 0 (Aka Special), that can be matched and retrieve it's metadata to feed emby: An Extra has it's own categories and are not included in 99.9% of the cases in any Metadata Source that Emby is using: a) shorts b) scenes c) featurettes d) behind the scenes e) deleted scenes f) interviews g) trailers h) Openings i) Endings j) etc So why mixing it ?????? Specially when you have it already solved in Movies:

Did someone else setup your server installation?

OK that is not true. Collections are still fully supported and a major part of Emby Server.

If you're showing the Season folders, then you can click Season 0. Isn't the specials line redundant at that point?

That generalized approach is really the main thing I’m hoping for. I completely understand the concern about allowing plugins to provide arbitrary custom UI inside the official apps, especially if Emby needs to maintain control over what can be exposed through clients distributed through the various app stores. I don’t think plugins necessarily need the ability to create their own UI, though. What I’d love to see is a small set of Emby-controlled extension points that any plugin could use, where the official client still owns and renders 100% of the interface. The report-system example @yocker mentioned is actually a perfect example. A generic plugin action could potentially support: Report Problem Missing Subtitles Incorrect Metadata Refresh Metadata Add to External Watchlist Request or any number of other plugin functions without the plugin actually injecting a custom interface into the client. The plugin could essentially tell Emby: I have an action available for this item called “Report Problem.” Emby decides where/how that action is displayed using its normal UI components. When the user selects it, Emby passes the action back to the server plugin. That keeps the UI entirely under Emby’s control. The same concept could potentially apply to plugin-provided media rows. That part is particularly useful for something I already have working in my modified Emby Web client that has nothing to do with content acquisition. I currently classify music releases using MusicBrainz and separate an artist page into: Albums Singles & EPs Live Compilations Other Releases instead of putting everything together under Albums. The classification and presentation are already working on my server/Web client. What I’m missing is a way for the server/plugin to tell the native apps something as simple as: Title: Singles & EPs Type: Media Row Items: [existing Emby item IDs] The Android TV/iOS/Android client could then render that with the exact same media-row component it already uses everywhere else. The plugin wouldn’t provide HTML, JavaScript, Android layouts, Swift UI, CSS, or any other custom UI. It would just provide the title and existing Emby items. Emby would retain complete control over how it looks and behaves. So I think even two generalized extension points could open up a lot of possibilities: 1. Plugin Actions Allow a plugin to register an action for certain Emby item types/users, with Emby rendering the action using its own native UI and sending the interaction back to the plugin. 2. Plugin Media Sections Allow a plugin to provide a title and list of existing Emby item IDs for an additional row on supported detail pages, with Emby rendering the row using its normal native components. Neither one would require giving plugins arbitrary access to the client UI. And both could benefit plugins completely unrelated to acquisition. A reporting plugin is a great example for actions. My Albums / Singles & EPs / Live separation is a good example for media sections. Other developers could probably come up with quite a few uses neither of us has thought of yet. That’s really the part of my original request I’d be most excited to see explored. If something like a generic Plugin Action were the easiest place to start, even just that would be a really useful extension point. I’m also happy to share screenshots or details of my current Web implementation if seeing a working example of the music sections or actions would be useful.