All Activity

Let's not enter a Windows vs. Linux discussion, we all know how these end There was a very simple reason why the earlier beta was Windows only: A Windows release is very easy to build and I was able to easily provide even 3 updates to the beta group on a single day. Our Linux builds are way more complex (alone due to the wide variety). They have their own build server and there are like two "production lanes": Beta and Stable. Intrroducing a 3rd lane would require an amount of effort that cannot be justified. It would also cause distraction from the actual subject for testing, as we would have to deal with packaging problems as well. For the Linux client, this made sense, because those packages were the ones to be eventually released, but for a TVnext special beta, these would not have any higher-goal purpose. This does not mean that TVnext does not support tuner hardware on Linux. It has a remote tuner feature which allows us to test this in the same way as when Emby Server would be running on the Linux machine itself. During the beta, we even managed to use the tuner from a SAT-TV set-top box with MIPS architecture (running Linux) and a USB tuner plugged into Nvidia Shield. In other words: TVnext does not have any platform limitations, it was (and might again be) merely about the distribution packages we were able to provide during the private beta testing.

@NeminemThanks! Point 2 is resolved. I restored the oringal Season overview. (I cannot edit the first post anymore) @Luke is possible to respect the 'orginal' server settings when adding new features like this? I would love that

Thanks for the explanation @FrostByte. If I understand you correctly, the new Android version is basically the same as the ATV version in regards to passthru of high res codecs? At least in my case, it works differently though. With the same Shield settings, ATV lets Shield do the transcoding and in Emby Server it is direct played. On Android version, it gets downmixed to PCM 2.0 and if I enabled the option to convert it, Emby Server transcodes it and not Shield. This feels counter intuitive and unnecessary. It feels the new Android version works differently internally. This is what I have observed in my testing. I can't fully switch over to the new Android app yet until this is resolved/fixed. Hopefully the ATV version will not be taken down in the foreseeable future.

@LukeYou gave a 'thanks''. I don't understand for what. If you would have the time to respond and share the state or perhaps your view of bringing back this old feature, that would be lovely!

@LukeIn regards to 'point 1', is there a setting I missed that can change the Search overview?

A new stable release is imminent, so that there isn't sufficient time to make a change like this (which cannot go into stable without proper testing). After stable release, there might be a short period for taking care of regressions in the new stable during which the beta remains at the same state, but then the beta will get the transcoding update, which is far more than just an ffmpeg switch, btw.

Funny thing is that the option in AndroidTV was added to support someone else's' SONUS soundbar and prevent everything just being passed through and then a similar option added to the new app at the same person's request. The problem is that when probed the Shield reports that it supports everything because it technically does. It's the audio devices on the other end that may or may not. Those two options in the two apps basically do the same thing though. Before those options were added both apps just passed everything through and let the Shield handle it. Now in AndroidTV it passes everything through by default unless you uncheck codecs to force the server to convert whereas in the new app that isn't necessary because it gets all the information it needs from your Shield's settings and you check the setting in the pic to force server transcoding. However, you can also just allow everything to passthrough and let the Shield do the conversion if you use your TV's speakers and then you get lossless stereo. In the end though they do the same thing if you prefer DD 5.1 from the server instead of PCM 2.0 from the Shield for unsupported audio formats.

Hello, I am running Emby Server 4.9.5.0 on a Synology 1821+ NAS with DSM 7.3. Yesterday I uninstalled the EmbyCredits plugin because scanning all the movies and series was slowing down the server for too long and I realized I didn't need the feature that bad. I then restarted Emby to complete the change. Bad idea... Since then I am unable to login to to the server from a client, and get this error : Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown Since then, I have restarted Emby, restarted the NAS but the error persists. I don't want to break things any further than I have already, so I hope your wisdom will help me fix the issue. I'm adding the server logs from a few minutes ago. Thanks for any help you can provide ! embyserver.txt

Hi Luke, I scanned in new media, turned off the internet, went into a new movie and I had actor images. The fetcher did retrieve actor images in advance OR maybe it was using the cache for actors from other movies with the same actors which is more likely. Are there Emby compatible tools that can download actor images/bio in advance and add them into Emby's main cache, not add them into the individual media directory?

Thanks for the update. I appreciate the explanation. I don't have fancy sound equipment, just plain SONOS playbar with 2 Play One speakers set up as surround sound with a sub mini. I noticed if I didn't turn on the option to Convert unsupported surround audio to Dolby Digital, DTS-HA stream, for example, gets downmixed to PCM 2.0. If I turn this option on, Emby will transcode the audio in the background to Dolby Digital 5.1, whereas the ATV version will just pass thru it to Shield and Emby Server will direct play it instead of transcoding. This is something I don't understand at the moment. Does ATV work differently internally regarding the high res audio? Or do I need to change something in the audio setting in Shield to make it work better? Please advice! I really love the new Android version. Thanks!

Hi everyone, I have an Emby server where I created some users, and I initially gave all of them permission to download media. Now I would like to disable the Download permission for all users. At the moment, it seems that I have to go into each user individually and disable the download permission manually. Is there any way to: Select multiple users or all users and disable the Download permission in bulk? Use an Emby API, script, or another method to change this permission for all existing users at once? I would simply like to avoid having to edit each user individually. Any help or suggestions would be greatly appreciated. Thanks!

It’s not really desired in TV mode. The ones that are there are only there because there’s no other way to get to that list.

Hi, what version of iOS does it run?

0.0.0.4 uploaded Add a user (non admin) interface with simpler wording and duplicate protection. Properly sized plugin thumbnail.

Hello, I use unraid for Emby. On the phone it logged me out. I tried to use my PW but it's not working. So I went to reset it and it makes the file in the conrainer app but the url it gives me doesn't work. it's giving this link "http://172.17.0.3:8096/web/index.html#!/startup/forgotpasswordpin.html" but nothing is at that link. How do I reset my PW? Thanks

When a user in my house tries to play a 4K file on a slightly older iPad, he gets a "no compatible streams available" error. This is on a file that plays fine on several other devices (a newer iPad, a new-ish iPhone, and a Roku TV). I also tried forcing transcoding on one of those devices just to make sure there wasn't some issue going on sever side there; it worked fine. The user has full access to all transcoding/remuxing. Why is the iOS client bailing out of the playback attempt entirely rather than trying to transcode to a compatible format? This happens even if I set the local streaming quality to something low enough to force a transcode from the start. Log of one playback attempt attached, relevant things I'm seeing: Bitrate exceeds DirectPlay/DirectStream limit fires (23,334,642 vs the 10,000,001 cap) — seems reasonable for this device, and I would think the trigger for transcoding. The very next PlaybackInfo call includes EnableDirectPlay=false&EnableDirectStream=false — the client asking for a transcode profile — and gets a 200 back. Then the client immediately calls ActiveEncodings/Delete and reports Sessions/Playing/Stopped at position 0 — no stream request, no ffmpeg process ever spawned, no ffmpeg log from the attempt. ipad playback error.txt

Here is the one with Elle. It is wider than 1920 but still shows as 1080. That is what is throwing Emby off. It isn't the Dolby Digital Plus with Dolby Atmos. That works fine. This file plays fine for me on any 4K device I have. But on the Roku express HD I cannot get this to play. Same error you are having. This can be fixed on the server side. It will get addressed soon.

It slipped my mind; I didn't click save

Yes the text is there, just didn't think it mattered having already donated. But I guess the info got lost somewhere when I updated the NextPVR software. All good now anyway thanks.

That’s interesting. I’ll check tonight after adding new media, scanning then disabling the internet and viewing a movie.

HI there, can you please provide a specific example? How to Report a Problem Thanks !

@kaledi Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

TV mode Actor Page Movies TV Shows Episodes They are all now clickable headers again! They all go to a vertical grid view again! That was one of my biggest gripes back then when you guys removed the "see all button"

Ok we are looking into it. Thanks.

@clock_wizard Hi. Can you try searching for our standard android app (Just "Emby" on Amazon and "Emby for Android on Google) on the same device's app store and see how that compares? Thanks.