All Activity

The only other lossless audio format you can convert it to, and Samsung supports, is wav and that would double or triple the size of the file. My suggestion (if the devs agree) would be for Emby to temporarily transcode FLAC to mp3 for users on Tizen 9. There would be some loss in quality, but you wouldn't have to change anything and the devs could put things right after Samsung fixes it. This way you can at least play your music which is better than nothing.

It won't - at least not in the TV app because the Volley system doesn't follow the 308. We recently had someone run into that. Make sure you've set the server to require it and, if entering the address manually in the app there is now a simple check box to click to use SSL.

There will always be a loss of quality when transcoding, Flac is a lossless format and transcoding it will make it lossy so there will always be something missing in the conversion. It's not always noticeable, specially not when not using some VERY high end headphones. For example, MP3 is a lossy format but most people don't complain about hearing any degradation in quality.

Out of curiosity may i ask why you want it to loop through the internet instead of just using local address?

The new version fixed my problem. Thanks!

You have every individual movie folder defined in your library? If so, you don't want to do that. Just designate the parent folder of all of those folders in the library and the system will find them.

How do you do it, and is there any loss of quality? comment faire et perd t'on de la qualité ?

It's okay. I understand BTW, has there been any progress on separating Cast & Crew in the Emby universal App and Emby Web?

@chuwzwe cannot verify what that APK does so cannot allow its distribution here. Thanks.

Moving to Developer API section as this is not a user-facing feature.

That's simply what capitalism is, which is why not everyone is in love with it. Paul

if you delete theme.mp3 or theme.mp4 they will be regenerated, as long as you ran a libary scan beforehand. If you decide to manually upload one from youtube or any other source my plugin skips it, since it already exist. My Plugin only uses what is already present on the server. No external calls, so if emby has at least one intro-marker set for a show this will be used to cut the themes. PS: Plugin arrived in the Emby Plugin Cataloge

Thank you - you were right, I had someone staying with me last month & they speak Ukrainian & must have added that filter, so I have been missing a pile of movies this past month & never noticed

Amazing, this has worked! Thank you for persisting with this!

Oh ya, lots of posts out there about FLAC playback being broken with Tizen 9. Temp solution might be to just transcode music also after checking if TV is running Tizen 9.

Not really the issue here. The problem is that the server will still publish it's own local IP and http port to certain clients even if they are connected using a domain name. If the client is on the local network it will prefer to use the local IP of the server and it's http port if they are available and not blocked by a firewall. I know for a fact this happens on android, and i believe the windows and xbox apps as well, possibly others too. The Roku app is the only one that I'm aware of that doesn't seem to switch to the server's IP address and http port if you use a domain name when first connecting when you're on a local network. This is easily verifiable by checking emby server as well as reverse proxy logs if you're using one. If you manually enter the domain name, the app will connect through the reverse proxy using the domain name. As soon as you close and re-open the app it will connect straight to the server's IP and HTTP port unless blocked. This happens even if you block the server's discovery port (UDP 7359) or even if the client and server are on separate VLAN's where the UDP discovery service doesn't even come into play. So there's 2 things that would need to be addressed. The server needs to be able to advertise a domain on the UDP 7359 discovery service for first time connections as well as advertise a domain URL locally to clients that have the ability to switch between internal/external URL's based on whether or not they are in a local network.

Great news - thanks, so I wait and hope I hope that an update will then recognize and update my manually installed file. I didn't rename it; I left everything as is. One more thing – my owner is set to "emby.emby," meaning all plugins have this owner. Your owner seems to be "EmbyServer.EmbyServer" I don't know if that's important. Another question about the tool, since it might be relevant: 1. If I manually delete a "theme.mp3" or "theme.mp4," will it be regenerated the next time I run the program? 2. If I don't like the search results, can I manually create a theme.mp3 or theme.mp4 file with the program? (I just noticed that for some series, it simply used a segment from the series as the theme, even though there's an intro. It would be nice to be able to correct that manually, if possible.) 3. Is a list planned for the plugin that shows me all series that have a theme.mp3 or theme.mp4 file, so that I can edit/delete them directly there? (This is how it works, for example, in the "TV Theme Songs" plugin (which doesn't work with the beta version, and that's how I came across your solution, which seems to be independent of it)

I’ve encountered a significant bug that requires a full rebuild. I apologize for the delay and will keep you updated on our progress.

Fantastic, that works exactly how it used to. Thank you so much for persisting with this!

"NAT Hairpinning" is probably what you are looking for. If i understand want you want correctly. It's something that needs to be enabled in the router.

Blocking 7359 solves the problem for the first time connection as the server isn't being advertised. The problem is that the server will still publish the internal IP and http port to clients once they have been connected and signed in. Clients that are aware of both the internal and external url of the server seem to prefer the internal url when on the internal network. Also blocking 8096 on the server's Firewall is the only way to force clients to not auto switch to the server's internal IP:8096 as it will fallback to the external domain. The problem with doing this is that this also breaks DLNA only devices or reverse proxies not on the same machine that emby is running on that need that http only connection. Blocking connections at server's OS firewall level may also either be extremely convoluted or not possible in some setups. I use Windows, so it's fairly trivial there, but doing so in certain deployment types like docker with host networking, macvlan, etc may not be even be possible. The real solution is to just have an officially supported option to have the emby server advertise a URL for internal connections rather than just advertising the IP and the server's internal http port. Ideally a separate internal domain field similar to what we have for specifying the external domain along with specifying the protocol and port. It could just advertise the external domain as a simpler solution, but having the additional options would be nice for those that have different internal/external access urls and more elaborate reverse proxy configs. This would completely solve the problem for app clients that switch between the external and internal URL's to have https everywhere while not breaking other functionality or setups that still need the http connection directly to the emby server. Devs may want to add a fallback to just the server's IP and http port in case of DNS resolution issues, but I would assume that anyone wanting to force clients to use https connections locally with a domain name should know that they will need local DNS records for everything to work anyways.

Googling this. It seems Samsung only allows Flac from it's USB via internal player. Any network and/or third party app will be blocked from Flac playback. Bunch of people complaining on Reddit and Github about it. Don't have a Samsung my self or i could test it.

Hello thx for the Help it worked now i wait till the 4.10 version is out of the beta now im using 4.9.5.0 and the plugin i want need the new version you now when the 4.10 version is completly out?

I already requested access to the emby plugin repository. So it will soon be in it.

Yes I found and all work! This is the proof - the problem is not the programm, the problem was a stupid user Never touch a running system - but - How important would the update to version 1.03 be? I would have to repeat the entire procedure, just like with the initial installation, because an update directly through Emby, like with other plugins in the repository, isn't possible—logically. So first, I'd have to delete the old .DLL (because overwriting it wouldn't be so easy, since I'd have two .dll files in the plugin folder after the import, one of them being the old one located at: empy.emby EmbyThemeMaker.dll New after import, before changing the owner: root.root EmbyThemeMaker.dll Will you help me one last time (I know it was never your intention to explain the basics of Linux to complete beginners) to solve this problem?