All Activity

@ebrDas ist ein berechtigter Ich glaube aber, dass wir hier zwei verschiedene Probleme vermischen. Kodi auf Android kann direkt auf SMB-Freigaben zugreifen und Medien von smb://diesen Pfaden abspielen. Ich nutze genau das selbst, sowohl als eigenständiges Programm als auch in Kombination mit Emby. Meinen Sie also, dass Embys Implementierung des direkten Dateizugriffs diese zusätzliche Android-Berechtigung speziell erfordert , oder dass der direkte SMB-Zugriff selbst sie erfordert ? Denn das sind zwei völlig unterschiedliche Dinge. Was den Nachweis eines Qualitätsvorteils angeht: Nein. Wenn HTTP Direct Play und SMB exakt dieselben Originaldaten an denselben Decoder liefern, gibt es offensichtlich keinen prinzipiellen Unterschied in der Bild- oder Tonqualität. Ich habe mich diesbezüglich bereits korrigiert. Ich verstehe aber nicht, warum Direct File Access eine überlegene Bildqualität oder eine höhere Roheffizienz nachweisen muss, um einen Vorteil zu haben. Mit Direct File Access greift der Player direkt auf die Originaldatei im SMB-Share zu und übernimmt die Datei-E/A, das Positionieren und das Puffern selbst. Der Emby-Server muss sich nicht im Mediendatenpfad befinden. Diese Architektur bevorzuge ich für die lokale Wiedergabe, und genau so nutze ich Emby aktuell mit Kodi/CoreELEC. Kodi unterstützt seit Jahren den direkten SMB-Zugriff. Es funktioniert. Auch Emby selbst unterstützte in der Vergangenheit den direkten Dateizugriff auf dem Shield – ich habe ihn selbst genutzt und sogar mein Shield extra auf Experience 8.x zurückgestuft, um diese Funktion beizubehalten. Meine Frage ist also ganz einfach: Wenn Kodi den direkten SMB-Dateizugriff auf Android implementieren und aufrechterhalten kann, warum wird dasselbe Konzept dann bei einem Emby-Client als so „fragwürdig“ angesehen? Ich stimme vollkommen zu, dass die meisten Emby-Nutzer es nicht benötigen. Aber „die meisten Nutzer benötigen es nicht“ und „es bringt keinen Nutzen“ sind zwei völlig unterschiedliche Aussagen.

@ebr

Thanks! May I ask one quick question regarding the settings? The description says the plugin will check TheIntroDB before processing the video. Does this check happen before or after it verifies whether the file is a .strm file? If it can lookup TheIntroDB prior to checking for .strm files, that would be super helpful!

Setup a webhook that subtracts screen time that my kids earned and is recorded on the site.

v2.7.2.0 still running after starting on a schedule, thanks for those fixes!

Hi! Yes sir, it has been processed and approved Thanks! -N

That is also incorrect. How the file was delivered would have had zero effect on this issue (the one this thread is actually about).

That's not how it works. Part of the changes made by Android are that the store listing calls out certain sets of permissions in the store listing making them look dangerous. Can you provide a specific, detailed example proving any quality or efficiency gain by using SMB file access instead of HTTP?

Hi. Your server is running on an Android device?

You don't want to do that. The network is in your home and should be Private. Public networks have different much more strict firewall rules.

I mean, I’m pretty sure channel changing used to be faster before Emby force enabled live rewind.

Okay, interesting. Any way I can reset them? Some just are called "trailer".

Hi there, please attach the Emby server log from when the problem occurred: How to Report a Problem Thanks!

Hi, did you find any?

@MrGileshas this helped?

It is working for me but they are certainly not making it easy.

@ebrI’d already written that: And I can say with certainty that my proposed solution – Direct File Access – would be the answer, and not just for this particular problem. And for many others. Yes, I keep making things difficult. Because I don’t see why your personal assessment of what is or isn’t worthwhile should be the be-all and end-all. But please, stick to the right thread

I don’t use android only an iPhone. But some bad news, trailers no longer play on my iPhone, it opens a YouTube screen with background and a play icon but it can’t be selected and doesn’t play. @Luketagging you on the above. Damn YouTube!

@ebrthanks, Eric. That is pretty much how I remembered it. But this is also exactly the part of Emby's approach that I find frustrating. Direct File Access worked perfectly well for me on the Shield. I even downgraded to Experience 8.x specifically to keep using it. It wasn't removed because the feature itself didn't work or because the Shield was incapable of doing it. Android changed, the implementation would have needed to be adapted, and Emby decided that the number of users wasn't worth the effort. I can understand the development-effort argument. What I find much harder to understand is the permission argument. If Direct File Access is an optional feature, then surely the additional permission can also be requested only when a user explicitly enables that feature. Users who don't need it never have to see or grant it. Saying that such a permission might scare users away therefore seems like a rather weak reason to remove a useful advanced feature for the users who actually want it. And there is a broader issue here. If every advanced feature is judged mainly by how many users need it, then power users will almost inevitably lose features over time. Direct File Access was never going to be something the average Emby user needed — but for the people with a proper local media setup, that was precisely the point of it. Ironically, I solved the problem by buying a Ugoos and moving my main playback to Kodi/CoreELEC. There I get Direct File Access and the control over local playback that I wanted in the first place. So yes, I understand why Emby made the decision. I just don't think “only a few users need it” automatically makes it a good decision. Sometimes the features used by relatively few people are exactly the features that distinguish a powerful media platform from just another streaming client.

How does the Android app compare in this regard?

What about disabling subtitles and the more videos icon

Yup!

Not seeing any ads but in the bottom right next to the YouTube logo just to the left there is a more videos icon and trailers still have annoying subtitles. Can they be turned off?

Also please show the complete screenshot of the entire user interface. thanks.

Hi there, please attach the Emby server log from when the problem occurred: How to Report a Problem Thanks!