Leaderboard

Ah, I thought I already had it on debug! I'll do that, it may also be enough for me to figure it out on my own.

That's a different feature than what we're discussing here though and this feature would greatly increase search functionality in general, instead of a per-library basis.

Summary: Emby does not remember where you stopped reading. Reopening an eBook always starts at the beginning. Please persist a per-user last read position and resume from it on all clients. Steps to reproduce: Open any eBook Go to a later page or chapter Close and reopen the book Expected: The book opens at the last read page. Actual: The book opens at page 1. Request: Save and sync last read position per user for all supported formats. Update on page change and on exit. Resume automatically across devices. Optional API endpoint to read and update progress.

Add structured eBook metadata fields to Emby so books can be indexed, searched, filtered, sorted, synced, and surfaced with the same quality as video and audio libraries. Problem Current handling of eBooks in Emby is limited. Important fields are missing or unindexed, which makes large libraries hard to organise. Users who migrate from Calibre or other managers lose rich metadata, reading progress, and annotations. Proposed solution Introduce native models, scanners, UI, and API support for the following fields. Core fields Title. Main identifier for the eBook. Used in listing and searching. Author/Editor. One or many. Essential for grouping and sorting. Language. For filtering and display. Series. Series name and number, sortable. File Format. EPUB, MOBI, PDF, AZW3, CBZ, etc. Drives renderer choice. Identifier. Unique ID next to ISBN, such as, DOI, UUID, or an internal GUID. File Path / Location. Absolute path for local and NAS items. Optional fields Publisher. Useful to separate commercial and indie content. Subject / Genre. Fiction, Non-fiction, Sci-Fi, Thriller, etc. Tags / Keywords. Freeform labels for flexible search and smart lists. Reading Progress. Per user last read location, bookmarks. DRM Status. Enum: Unknown, None, Present. Word Count / Page Count. For size filters. Rating. Per user and external ratings. Last Accessed / Last Read. Per user activity to support “Continue reading”. Annotations / Highlights. Per user notes and highlights, exportable. Data model Add a new BookItem entity that extends the existing BaseItem. Scalars: Title (string), Language (ISO 639-1), SeriesNumber (decimal), DateAdded (datetime), DatePublished (date), Format (enum), DrmStatus (enum), WordCount (int), PageCount (int), RatingExternal (float), RatingUser (float), LastAccessedUtc (datetime). Collections: Authors (list of person refs), Editors (list), Identifiers (list of type:value), Tags (list), Subjects (list). Per-user: ReadingProgress (location plus percent), Bookmarks (list), Annotations (list of location plus text and timestamp). Paths: Path (string), LibraryId (guid). Indexing and search Index Title, Authors, Series, Language, Publisher, Tags, Subjects, Identifiers. Sort keys: Title, Author, SeriesName+SeriesNumber, DatePublished, DateAdded, PageCount, WordCount, Rating. Ingestion and metadata Add an eBook library type in Library Setup with supported extensions and a priority order: EPUB, MOBI, AZW3, PDF, CBZ, CBR. Parse embedded EPUB OPF metadata, PDF XMP, and sidecar .opf files produced by Calibre. Optional metadata providers: Google Books, Open Library, ISBNdb, Goodreads export files. Providers should map cleanly to core fields and never overwrite user edits unless requested. Support Calibre migration: read Calibre library structure, .opf sidecars, and metadata.db when available in read-only mode. UI and UX Library views: Grid, list, and series views with badges for format, language, and DRM. Detail page: Title, series breadcrumb, authors, description, identifiers, subjects, tags, publisher, publication date, format, page count. Actions for “Read”, “Download”, “Mark as finished”, “Add bookmark”. Reader integration: For EPUB and PDF, an in-browser reader that persists per-user progress, bookmarks, and annotations. If a built-in reader is out of scope, expose progress endpoints so external readers can update state. Filters: Language, series, publisher, genre, tags, format, size, DRM, rating, date added, date published. Smart playlists and collections using the new fields. API contracts Extend the public API: GET /Items?IncludeItemTypes=Book with new query filters series, language, publisher, format, drmStatus, minPageCount, maxPageCount, subject, tag. GET /Users/{id}/Books/{itemId}/Progress and POST to update progress, bookmarks, and annotations. POST /Items/{itemId} allows updates to book metadata with field-level overwrite controls. WebSocket events for progress updates to sync multi-device reading. Permissions and privacy Store annotations and progress per user. Do not expose one user’s notes to others unless explicitly shared. Allow metadata locking at the item and field level. Migration and compatibility Backfill DateAdded from file system timestamps if no prior value exists. Detect duplicates by Identifier or by fuzzy match on Title, Author, Series, and Page Count. Do not break existing audio-book flows. Keep AudioBook separate from Book. Performance considerations Defer parsing heavy PDFs until requested or during low-priority background tasks. Cache OPF and XMP reads. Respect library scan schedules. Acceptance criteria A user can import a mixed EPUB, MOBI, and PDF library and see correct Title, Author, Language, Series, Format, Identifier, Path, Date Added, and Date Published without manual edits. A user can filter by Language and Series, sort by Date Published, and search by ISBN. Reading progress persists per user across devices for EPUB. Optional fields are editable in the UI and via API and are indexed for search. Export of per-user annotations to JSON is available. Nice to have, phase 2 OPDS server for books using the new metadata. Goodreads or Open Library sync for ratings and shelves. Calibre two-way sync for edits and progress.

maybe the sup subs cant be played in the browser

Ask your isp

Might need to enable debug logging and also try to capture a time when new media is added.

Yeah, mine all had a generic season type picture.. Emby was getting the picture embedded in the file, but for me it was a generic one. I guess its more of a problem with my files and the picture that got embedded into them.. But removing it, Emby then scraped one fresh from the stream. In case anyone else has files that have had a generic image baked in.

I don't know how to answer. I told you what I know. Refreshing the guide didn't do anything. This morning things look back to normal.

Thank you very much! The plugin works great!

Sure does, as embedded images will take priority if Image Capture enabled (same as if local metadata/artwork present); depending where in the preferred fetchers list Image Capture is placed (if on top), it'll even take priority over online providers, hence it's advisable to have it at the bottom unless you do prefer to use embedded images, as it is usually used as - sort of - last resort image, when all others fetchers fail/images not found. Edit: FWIW, after your second-last post, I've recreated your structure and had no issues getting screengrab as thumb:

All fixed. Something was wrong with my router, so I ended up resetting it within the web portal. Now I'm connecting remotely again! Although I'm not sure what could have happened with the router, it's supplied by my ISP and is only a few months old....

Mungkin ini memang ada konflik resource antara Minecraft Unlimited Items dan Emby di Android TV. Coba cek apakah ada update terbaru untuk Emby atau game-nya, atau tes pakai versi Minecraft apk tanpa mod untuk lihat bedanya. Kadang mod bikin sistem kerja ekstra, jadi UI aplikasi lain ikut lag.

can you make a way to filter devices by the devices that user has logged in with. Example, currently if you go to user settings and uncheck "all" under devices, it shows all devices. Need to filter devices in that list by devices that user has used.

Hi, yes I agree we should add some filters there. Thanks.

Hi we’ll take a look at it. Thanks for reporting.

What is still more important is having the ability to set Emby to only search the library you are in. Same goes for searching within settings. Fix the real issue first.

Summary: Text in eBooks cannot be selected, which blocks copy, highlight, notes, and dictionary lookups. Steps to reproduce: Open any eBook Try to drag to select a word or sentence Expected: You can select text and get a context menu to copy, highlight, add a note, or search. Actual: No text selection is possible. Request: Add text selection for ebooks on all clients, with standard actions (copy, highlight, note, search). Respect DRM no-copy flags and expose selection-based annotations via API.

Vielen Dank für die Liste mit allen Befehlen. Es ist sehr hilfreich, nun genau zu wissen, welche Sprachbefehle Emby versteht, um Lieder, Alben oder Playlists abzuspielen. Ich habe nur ein paar kleine Anmerkungen bzw. Änderungswünsche unten aufgeführt. Insgesamt freue ich mich sehr über die Arbeit, die ihr in den Skill steckt, und helfe gern, wenn ich irgendwie unterstützen kann. Thank you very much for providing the full list of commands. It is very helpful to now know exactly which voice commands Emby understands to play songs, albums, or playlists. I only have a few small comments or suggestions for changes listed below. Overall, I really appreciate the work you put into the skill, and I’m happy to help in any way I can. Hier sind meine Änderungsvorschläge: Here are my suggested changes: spiele die Wiedergabeliste {{playlists}} auf {{devices}} spiele die Wiedergabeliste {{playlists}} spiele das Lied {{AMAZON.MusicRecording}} auf {{devices}} spiele {{AMAZON.MusicRecording}} von {{AMAZON.Artist}} auf {{devices}} spiele das Album {{AMAZON.MusicAlbum}} vom Künstler {{AMAZON.Artist}} spiele den Künstler {{AMAZON.Artist}} auf {{devices}} spiele den Künstler {{AMAZON.Artist}} spiele das Lied {{AMAZON.MusicRecording}} vom Album {{AMAZON.MusicAlbum}} spiele das Lied {{AMAZON.MusicRecording}} von {{AMAZON.Artist}} spiele das Lied {{AMAZON.MusicRecording}} vom Künstler {{AMAZON.Artist}} auf {{devices}} spiele das Album {{AMAZON.MusicAlbum}} spiele den Künstler {{AMAZON.Artist}} von Favoriten spiele {{AMAZON.MusicRecording}} von {{AMAZON.Artist}} von Favoriten spiele das Lied {{AMAZON.MusicRecording}} spiele {{AMAZON.MusicRecording}} vom Künstler {{AMAZON.Artist}} spiele {{AMAZON.MusicRecording}} vom Album {{AMAZON.MusicAlbum}} auf {{devices}} spiele von Favoriten das Album {{AMAZON.MusicAlbum}} spiele das Album {{AMAZON.MusicAlbum}} von {{AMAZON.Artist}} spiele von Favoriten {{AMAZON.MusicRecording}} von {{AMAZON.MusicAlbum}} spiele {{AMAZON.MusicRecording}} von {{AMAZON.MusicAlbum}} "artist_terms": { "Artist": [ "Gruppe", "Band", "die Gruppe", "die Band", "der Sänger", "der Künstler", "der Interpret", "Sänger", "Künstler", "Interpret" ] }, "album_terms": { "Album": [ "Zusammenstellung", "Aufnahme", "das Album", "die Aufnahme", "die Zusammenstellung", "ein Album", "eine Zusammenstellung", "eine Aufnahme", "Album" ] }, "song_terms": { "Song": [ "einen Titel", "Single", "eine Single", "die Single", "ein Lied", "Titel", "Single", "der Titel", "das Lied", "Lied", "Song", "einen Song", "der Song" ] } "action_terms": { "Play": [ "Serienmarathon", "reinhören", "einschalten", "zum Abspielen", "abspielen", "spiele", "spielen" ] } "playlist_terms": { "Playlist": [ "die Wiedergabeliste", "Wiedergabeliste", "Playliste", "die Playliste" ] } "context_terms": { "Favorite": [ "als Favorit", "meine Favoriten", "Favoriten", "von Favoriten", "von meinen Favoriten", "zu meinen Favoriten", "zu Favoriten" ] } Wenn man Emby mit dem Befehl: "Alexa, öffne Emby Zuhause" startet, dann wird vorgeschlagen, man soll z.B. sagen: "Ein paar Lieder zu spielen". Richtig wäre: "Spiele ein paar Lieder", oder: "Spiele ein paar Songs". Ich habe diesen Text in der Liste nicht gefunden und deshalb an dieser Stelle mit dem passenden Änderungsvorschlag ergänzt. Das selbe gilt für die Fehlermeldung, wenn etwas nicht in der Bibliothek gefunden wurde: "Das angefragte Medien konnte nicht in der Bibliothek gefunden werden." Richtig wäre: "Das angefragte Medium konnte nicht in der Bibliothek gefunden werden." Ich hoffe, das hilft weiter. When starting Emby with the command: "Alexa, öffne Emby Zuhause", it suggests saying for example: "Ein paar Lieder zu spielen". The correct phrasing would be: "Spiele ein paar Lieder" or: "Spiele ein paar Songs". I didn’t find this text in the list, so I added the appropriate correction here. The same applies to the error message when something is not found in the library: "Das angefragte Medien konnte nicht in der Bibliothek gefunden werden." The correct phrasing would be: "Das angefragte Medium konnte nicht in der Bibliothek gefunden werden." I hope this is helpful.

thanks

It's good for people who sell logins to emby but for me my emby never goes down unless the power goes out. Still cool idea though. After this is completed and you see a down for maintenance and when it comes back online 70% of the movie posters are still not showing then pull the plug people selling emby logins that can't even make sure that cover art and posters are a must and the live tv section 65% without a guide make sure you fix it No wonder they sell it so cheap, blank movie posters empty tv guide HAHA Keep in mind you get what you pay for and sometimes even less..... If you login to any emby from any server and any of the servers have empty blank movie covers CANCEL With me if I had to use this to say sorry the power is out, everyone who uses my emby would never see it because there power is out to

They said this beta will be shorter

Hello @Luke we dont have any news about it except « we’re working on it ». Could you please tell us if any problem or explain what happens ? Thanks to share news about it, we’re really waiting this features from few months (years ). Have a good day

Wow, I didn't realize you have been working on getting Asustor users back online for 5 years. Those poor users, I had know Idea.

Should be fixed in this one. WatchingEye.dll

Emby CarPlay is simply broken, not much you can do. Dev’s have to fix it, but it has not been a priority, I guess. As far as I can tell, it breaks as it tries to fetch the full library whn tou fire it up and fails.

Thanks for this. At the moment i would have no use for it, but if you would add the possibility to add (one or mulitple) country-flags (to display the language) to the poster this tool would be really useful for me. Looking for a way to do this comfortably for a long time.

hi after 6 months again i make this codes to make users and set permission for access and its great now and work fine for my project : i'll send it here if anyone need to use it leter : # Created: 2024/07/04 12:24:41 # Last modified: 2024/08/15 00:49:27 import requests import sys from config import API_KEY, EMBY_URL # Get user_id and password from command-line arguments if len(sys.argv) != 3: print("Usage: mkuser.py <user_id> <password>") sys.exit(1) user_id = sys.argv[1] password = sys.argv[2] try: # Create a new user create_user_url = f'{EMBY_URL}/Users/New' headers = { 'X-Emby-Token': API_KEY, 'Content-Type': 'application/json' } create_payload = { 'Name': user_id } response = requests.post(create_user_url, headers=headers, json=create_payload) response.raise_for_status() user_id_response = response.json()['Id'] print(f"User '{user_id}' created successfully with ID: {user_id_response}") # Set the password for the created user set_password_url = f'{EMBY_URL}/Users/{user_id_response}/Password' password_payload = { 'CurrentPw': None, # Use None if setting the password for the first time 'NewPw': password } response = requests.post(set_password_url, headers=headers, json=password_payload) response.raise_for_status() print(f"Password for user '{user_id}' set successfully to '{password}'") # Restrict user's access to all libraries user_policy_url = f'{EMBY_URL}/Users/{user_id_response}/Policy' policy_payload = { "IsAdministrator": False, "IsHidden": False, "IsDisabled": False, "BlockedTags": [], "IsTagBlockingModeInclusive": False, "EnableUserPreferenceAccess": True, "AccessSchedules": [], "BlockUnratedItems": [], "EnableRemoteControlOfOtherUsers": False, "EnableSharedDeviceControl": False, "EnableLiveTvManagement": False, "EnableLiveTvAccess": False, "EnableMediaPlayback": True, "EnableAudioPlaybackTranscoding": True, "EnableVideoPlaybackTranscoding": True, "EnablePlaybackRemuxing": True, "EnableContentDeletion": False, "EnableContentDeletionFromFolders": [], "EnableContentDownloading": False, "EnableSyncTranscoding": False, "EnableMediaConversion": False, "EnabledDevices": [], "EnableAllDevices": True, "EnabledChannels": [], "EnableAllChannels": False, "EnabledFolders": False, "EnableAllFolders": False, "InvalidLoginAttemptCount": 0, "EnablePublicSharing": False, "BlockedMediaFolders": [], "BlockedChannels": [], "RemoteClientBitrateLimit": 0, "AuthenticationProviderId": "Emby.Server.Implementations.Library.DefaultAuthenticationProvider" } response = requests.post(user_policy_url, headers=headers, json=policy_payload) response.raise_for_status() print(f"Access to all libraries restricted for user '{user_id}'") except requests.exceptions.HTTPError as e: print(f"HTTP error occurred: {e}") print(f"Response content: {response.text}") sys.exit(1) except Exception as e: print(f"An error occurred: {e}") sys.exit(1)

That’s it. QMusic works fairly well in that way but the UI is so bulky and awkward. It is hard to get non-tech family members to use it. Emby and Plexamp are so great that way. Especially Emby. But CarPlay!!!!!

My comment was positive. You took it as a negative comment. It was not.

Cowgirl, I think you are saying searching within a library is an important feature. Your sentence refers to a mistake = current, option = leaving as is, or option = search "where you happen to be". Perhaps shorter sentences would help you make your points more clearly.

Doesn't take away from the FACT that proper search should come before something that sounds like it will just be a more forgiving version of the search that we already have. I get the merits of fuzzy search, but make no mistake fixing the current search functions to have the option of either leaving as is searching everything or having it only search in the section of Emby you happen to be in is far more important.