All Activity

A new Traxx Tester build is available: 1.0.14-tester This version focuses mainly on shuffle behaviour, library reliability, Android Auto navigation and improved diagnostics. Shuffle rounds Shuffle now creates a real, finite playback order: Every song in the selected source is included once. A song will not be repeated within the same shuffle round. After all songs have played, Traxx generates a new shuffled round automatically. Where possible, the new round will not begin with the final song from the previous round. This applies to Shuffle All, playlists and artists on both the phone and Android Auto. Album shuffle remains finite and stops after the album has finished. Duplicate entries in a playlist are preserved as separate entries. Library and Android Auto navigation Returning from an album now restores the album you selected instead of jumping back to the beginning of the library. Phone album and artist list/grid positions are preserved when the app is temporarily recreated. Android Auto library browsing is now more stable when switching to Maps and returning to Traxx. Android Auto no longer unnecessarily rebuilds the complete browse hierarchy when the phone’s List/Grid preference changes. Background Android Auto requests can no longer accidentally switch the saved List/Grid preference. Android Auto ultimately controls its own visible scroll position, so feedback from different head units is especially welcome. Large-library synchronisation Library loading has been redesigned for larger Emby libraries: Phone, Android Auto and background library updates now share one active refresh instead of potentially downloading the same catalogue several times. Songs are downloaded in larger pages, reducing the number of Emby requests considerably. Downloaded pages are stored in a temporary staging area. The existing complete library remains available until the replacement is fully downloaded and verified. An interrupted refresh can resume from its most recent page for up to 30 minutes. Traxx verifies the item count and checks for inconsistencies before activating the new snapshot. This should prevent an interrupted initial scan from leaving Android Auto with an empty song library and starting again from zero. Network and artwork handling Traxx now responds more carefully to temporary DNS, Tailscale and connection problems: Artwork preloading pauses after a server-wide connection failure. Retries use increasing delays rather than continuing with hundreds of requests. A successful server response immediately clears the temporary block. A temporary server outage no longer marks hundreds of individual covers as failed for 24 hours. Genuine missing artwork and individual HTTP errors retain their existing retry protection. Improved diagnostic logs The tester log should now be considerably smaller and more useful: Routine fast HTTP 200/204 responses are no longer logged individually. Errors, slow requests, stream responses and network recovery remain visible. Library synchronisation reports compact progress updates. Expected request cancellations no longer produce full stack traces. Thousands of successful artwork writes are no longer recorded individually. Log trimming no longer begins halfway through a line. Testing requested Please pay particular attention to: Shuffle continuing into a new round without repeating songs within the current round. Switching from Traxx to Maps in Android Auto and returning to the same library area. Opening an album and then returning to the previous album position. Initial loading of a large library. Temporarily disconnecting Tailscale or changing networks and checking whether artwork loading recovers normally Important for existing testers: The test period lasts 14 days from the first installation. Installing an update over an expired Traxx Tester does not restart this period. Please uninstall the existing Traxx Tester app before installing this new APK. You will need to sign in to Emby again. This starts a new 14-day testing period. app-beta.apk

Recently Infuse added the option to request transcoded streams from Emby. For me (Ugreen DXP2800 N100 iGPU) it seemed to work very randomly on some files and on some not. The reason to prefer Infuse over native Emby when transcoding is, that Infuse requests an h265 transcode instead of h264. Looking at the logs in Emby revealed that the issue was that the subtitle burn-in request by Infuse failed. After some trying and working with ChatGPT on the issue I found a solution. I downloaded the "Diagnostics Options" plugin and found out that when I unticked "Disable Subtitle Filtering", the burn-in request is being processed correctly and a working transcoded stream is sent to Infuse. I reason it's just a workaround and not a true solution is that burn-in can lead to unintended results. I've seen files where subtitles were absurdly huge and others where they were not burned in at all. Therefore the only real solution has to come from the Infuse devs to not work with burned in subtitles but rather use HLS/WebVTT subtitles. I will send a report/request to FireCore. I hope this helps other Infuse users.

First of all nice work and the plugin seems to work so far. I have just one issue with the duplicate remover. Would it be possible to give us an option to select our preferred region to keep the correct one while removing/moving duplicates? Other than the region, how does the plugin decide based on the naming of the ROM files which ones to keep? For me it seemed like it just selects the first one in the folder with US region but correct me if I'm wrong. Would be nice to have some insights into that and maybe even more option to keep the best/most favorited versions of the ROMs in a library. On the phone (iPhone Safari) I realized it zooms in on the area of the button if you repeatedly press a button quickly. Is this an issue on Emulator.js?

Just like my thread that is about the desktop app not ever getting proper search. A million and one little thing peeps didn't request, but features peeps have repeatedly requested being igonore.

I've tried Nuvio and WuPlay android players (Stremio alternatives, for those who never heard about it), and the covers look amazing on my 4k TV! So, I don't think this is some Android limitation like you said, I think this is Emby's bad design or something. You can all try, install one of those apps and see for yourself. Then open Emby. It's night and day.

thanks @Pasithea but how / when will the plugin request the runtime if needed?

Lucky you!

Zero.

At least for my part it's finished, because i do not have any control about what's happening in the app. My plugin only tells the app to play something and that's it.

Well, is there any way t trigger the user selection other than adding it to, and selecting it from, the home screen?

Since it is reproducible, should I file a bug report?

@Luke@pünktchen What now? if tv guide works so that's it? we not going to make anything?

Then I need a kodi.log please. Enable debug mode for the plugin (not kodi debug log) and send me the log via PM. The log must include a file playback that should include the skin intro. btw, I still think it's a sync issue, not a plugin issue, however. Could also be a skin issue, but in this case skip intro should never show up. Did you trigger a repair sync in the plugin?

Think of any user on any system that has to contact the Admin because there is no synopsis, or missing images for a movie, TV show or the like. Emby doesn't always get the correct, or any, metadata the first time it is added. Sometimes it can take a few goes, depending what is available online. How many times have you had to refresh metdata to fill-in the gaps? Imagine this for your users seeing something with loads of stuff missing? They then have to contact you to put it right, where possible. Now imagine if they had the option to "refresh missing metadata" - you wouldn't be contacted, unless @Lukecould add an Admin-only nootification that an item was refreshed. Think of the bigger picture, not just your own ecosystem!

The skip intro button that fails to show up on kodi shows up on my browser and v11. It just fails to show up on the latest v12 beta. Also that marker option is broken on the stable version, you need the beta .24 for that to be fixed.

Hello, The next song issue appears to happen if the songs are 10+ minutes where the next song doesn't queue up when you tell it next song, and it just stops. If you let it play all the way, it automatically moves to the next song. If I say next song after a couple minutes on the long songs, it starts the next song perfectly. Hopefully that makes senses lol Appreciate the support from Emby!

Looking at the Devices list, I see this: Samsung Smart TV (UN65AU8000FXZA) Emby for Samsung 2.2.8 Luke, I'll need them to reproduce the error again so I can grab the logs before they roll off. Will post a proper play issue report at that time, thanks!

ok, if it doesn't appear at all, you probably need a resync. Emby does not report marker updates, when the markers are added after the content was synced (Emby task). Also you can adjust the library settings to add makers on new content and not only as a task.

It seems to be suggested here:

the first item pops up a user selection dialog the second item shows a list of users and can be used in menu and node setups to integrate directly into a skin widget. I dont know anything about Home Assist sorry.

Hi, we’re still looking at it. Does it happen with lower bitrate content?

Any update?

I really hope Emby doesn’t spend any of their resources on this. Why would any Emby server admin want to let a child curate their libraries? Lazybones No they are not just ‘your’ daughter's libraries; they are for any-one YOU (or any admin) choose to share it with! Think of the bigger picture, not just your own ecosystem!

Looks like the latest update (26.0.6) fixed the Folder card issue. It now looks like the original card prior to the missing images. I'm calling this issue resolved.

Mise à jour du script V38 https://github.com/pmspr4100/Encodage_Emby