All Activity

I see the same on 3.5.36. And to cut through the unnecessary back-and-forth: SVID_20260619_183247_1.mp4

Alright, everything works as expected with an unblocked Internet connection. What's the reasoning here?

The video will simply show the playlist scrolling, so I'm not sure what you think that will achieve.

It's possible @Lukemeans it will be fixed in .16.

Works fine for me, so a video would be helpful.

I am on the latest beta (.15) and I am still seeing empty genre entries. Do we need to do a full metadata refresh?

What I'm seeing is my playlist. I press the grab handles. I drag. The list scrolls, as it would do if I was pressing and dragging somewhere on the screen other than the grab handles. Basically, the grab handles don't seem to do anything.

@softworkzis around. He will take a look at it. Thanks.

Well it would help us visualize what you are seeing and what is happening.

HI, try also adding the field AlternateMediaSources to the url. This is recommended anyway. The only reason it is there is because some insist that they want it, and they're going to do it anyway despite our recommendation. But pulling down this information in bulk is not going to be optimal because many database queries will be one at a time for each item. It is best to wait and do /playbackinfo prior to playback of each episode. No it does not. The typical usage of a bulk endpoint is to display items in a list. When you're displaying in a list, you're not typically going to be displaying this level of detail. The same idea applies to requesting things like Chapters and People. It is there in case you're going to insist that you need it, but some things are going to happen one at a time and it's not going to be optimal.

The official Emby Docker image has wget, not curl.

Of what? Nothing happening?

It doesn't appear that @softworkzis around...

Looks to work fine, only issue I have with it so far is that if I add my guide xml to the plugin nothing populates, but if I add it via the emby normal setup it works fine. I will give the new version ago, as it looks to fix the issue i was going to report

Hi, what about now?

Hi, do you have any latest recordings?

No, not yet.

The docker exec fails: And I cant pull v2.1.5 right now, it says pulled newer image, but —force-recreate still builds 2.1.4. PS. You should check naming of releases, some have v2.x.x other without v. EDIT: Even though, after testing connection, refreshing and saving libraries again with 2.1.4.all Looks fine now

Will just add that if I use "Playback Correction" the sun is showing afterwards. So in my opinion now, this is a server issue that don't understand what works or not. And there should be an option for burn in of subs.

Okay, was just a guess as the plugin only works with what Emby gives it, so I sadly have little idea

I believe I have identified and solved your issue. I have adjusted the backend logic identifying libraries based on -arr source selection for the library media counter. Version 2.1.5 contains the fix and is available now. Thanks for all your help/feedback. The fix is much cleaner logic than I was using.

I have English set as my preferred language fetcher settings. I'll probably create a new post about it and see if anyone else is having issues. Thank you again!

The plugin takes the posters that emby gives it and draws on them, it does not dictate what to download. If I had to guess you don't use English and the posters for your language might be poor quality.

Emby.FastIptv.dll @Phyrate Added new version with scrollbar!

Thanks, this is very helpful. Based on the output, MediaSync is currently storing: Filme = movies Serien = unknown Kids = unknown Sabrina = unknown MediaSync isn’t identifying “Serien” as a movie library. It’s actually identifying it as unknown, and the dashboard count is falling back to a movie count. The next thing I want to check is what Emby is actually reporting back to MediaSync for your libraries. Can you run the following command and paste the output? docker exec mediasync python -c ‘from app.providers.media_servers.emby import EmbyProvider; import sqlite3,pprint; c=sqlite3.connect(”/config/mediasync.db”); row=c.execute(“select server_url, api_key from media_server limit 1”).fetchone(); p=EmbyProvider(row[0], row[1]); pprint.pp(p.get_libraries())’ This will show us exactly what Emby is returning for each library. Once we see that output, we’ll know whether this is an Emby library configuration issue, an Emby API behavior difference, or something MediaSync needs to handle differently.