All Activity

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.

So you have to choose or have the extras as properly be displayed as IT WAS until YOU REMOVED it or seeing Seasons in folders .... my media YOUR WAY ....

Yes, I am not sure where they're located.

yes That's what I read on discord. At this time, Is what I believe, is what was said.

Hi, this has been resolved in 4.10.1, so please update to that. Thanks.

It would be awesome if plugins could have some sort of UI in the apps for users to play with. Been wanting a report system in Emby for a good while now so users can report things like a broken video or subtitles missing.

With the 4.10 server, if you enable your display option to show all episodes on the series screen, then you should be getting an extra row now: Additionally, individual episodes can have their own extras, and you'll see that on the episode screen.

Amazon sells you that device probably at a loss to them because it is actually a revenue generation mechanism for them. If it weren't it wouldn't be nearly so cheap. Still, I'm surprised an app actually disappeared - unless it became incompatible.

@JJKOMcan you please provide a new log example using the latest version of both the server and the app? Thanks !

It does still work automatically (if turned on) but the times are fairly tight.

Nevermind, just realized you can go into the app's display theme and manually select Halloween theme or Holidays theme. Good enough for me.

Is this the final word on this? On the EMBY fire stick/tv app there is still an option, but it doesn't seem to work. Is there any chance of bringing seasonal back?

Anyhow this is available in 4.11.0.5 beta. The testing thread where you can report issues is here:

I'm sure there are still some generalized things we can do, meaning the kind of things that would benefit all plugins.

You can try and take a look at: