Leaderboard

I don't know if the request has been made, or if it might already be there, but I can't find it. Is it possible, if I am going to listen to an album or an artist, and I add, for example, three Albums, or artist more to the queue, that this queue can also be played as random? I do know that I can save this queue as a playlist and then choose after which I can random play. but that's a bit cumbersome. would like to hear Ron

On closer inspection I see that now.. was just a bit frustrated with the side scroll, makes looking up items in collections like Marvel Universe a pain. Hope to see that toggle in the future. Thanks again!!

It‘s work in HWA,all OK.

It's not how that checkbox works on any other site on the entire internet.

In the 4.8.7 release that is currently rolling out, you should only be seeing Collections side scroll if they contain multiple types. So for example, if a collection has only Movies, then it will just be one vertical list. If there are multiple types, then there will be the horizontal categories. If you prefer just to have one large mixed list like before, then for the next release we'll add a user option to control that. Thanks.

These images were inspired from many of the Libary images posted by members. These were made by 1 of my Sons.

I need to show the most recent season series from newest>oldest. I have one show that has 385 episodes and 195 seasons. So browsing to the latest season is untennable. Is there a setting to reverse the array of seasons to newest>oldest?

The Emby team wanted to say thank you again to everyone that took the time to ask various questions during our Q&A session. Here are a few more answers to questions that a lot of our users were asking about. 1) How is beta functionality success measured? Often times people are curious about the process we use internally here at Emby as we go through the Beta process. We do rely heavily on the forum feedback and beta-tester feedback relating to open issues. It is also important that we take into account the overall experience of the beta release compared to the current stable release, especially when we are making large changes as we did from 4.7 to 4.8. We may be perfectionists at heart but we also understand that we can't spend forever chasing perfection on the release so we do our best to balance stability and functionality throughout the whole process. To reiterate what we shared in previous blog posts, we also understand that a tighter release window with smaller goals allows us to hone in on the stability of the beta and get releases out to the public. It is something that we here at Emby are striving to get to. 2) What is the split of time between actual development and forum duties? We get this question asked often so we thought we would give a little run down on this. Some of our developers such as @Lukeand @ebrand others split their time between development and the forums as things demand. Other developers we have on staff actually do not even engage in the forums at all as to solely focus on the development of Emby moving forward. This allows us to offer quick and prompt customer service and also focus on development at the same time. We thought it was important to answer this one at this point in time, because we do want people to know that there is more to the development team than simply what you see here on the forums. 3) What would help the Emby team the most to improve the overall product from the community? This is another question that gets asked often and it's something that a lot of you are already doing. Keep up the feedback! The more the better! Everything that's posted on these forums is invaluable to us. From pain points, feature requests, how you're using the server, what apps you prefer and anything else that people share with us about how they utilize Emby. Everything that you share is heard and taken into account by the developers. That doesn't always mean that things can get implemented right away or worked on immediately, but the value of your feedback is paramount to our work. We know that it doesn't always seem like it to everyone, but we 100% listen to everything people say and value the thoughts and opinions of our user base! 4) What are some of the biggest obstacles that the Emby team faces throughout development? A lot of the challenges we face throughout development are based on resource allocation from the sheer amount of hardware and software options that Emby runs on. Keeping in mind that Emby runs on everything from an old windows laptop, to Linux distros, NAS, server systems and more, we have to make sure that the program works on all of these systems. Also development of the apps falls under that same category. With so many options for our users to choose from dedicated media players such as Roku, Amazon Fire Sticks, Nvidia Shields, Apple TV Smart TV's, mobile devices such as Android and iOS, there are a lot of different platforms that we need to develop on and do our best to make sure everything is up to the standard that our users expect from Emby.

Thank you to everyone who took the time to ask the Emby team questions across all of the different platforms including here on the forums. There were a lot of great questions that were thrown our way and we've been excited to get the answers out to you. While some of the questions we were not able to answer, we did our best to give you the most accurate and clear answers possible. Now without further ado, here is the first series of questions and answers for you to look over! Please keep in mind more questions and answers will be coming in additional blog posts in the coming days, so not all questions are being answered today. Who owns Emby? Emby LLC owns the Emby product and is a private entity. The owners are undisclosed but note that the development team has full control over the direction of the product. We are not beholden to or under the influence of any investor or investment group. What is the history of Emby? Emby grew out of an open source project called MediaBrowser. Emby's origin in concept came out of that project but there is actually none of that code base still within it. Emby ended up being completely built from the ground up to be a server-based ecosystem as opposed to just a single app as the old MediaBrowser was. Around 2011 what is now the core development team for Emby were contributors to MediaBrowser. We saw the opportunity to build something more flexible than the WMC environment would allow and embarked on creating what we then called MB 3. The core developers spent over a year furiously writing code before anything was released to the public. It was then probably another two years of dedicated development before anything was truly usable as a system. In 2015 it was decided that we had moved so far away from what MB originally was that we needed a new name. A few of the devs got together and came up with "Emby". There are a few reasons behind that name but one of the main ones was that you needed something that wasn't already trademarked and domained. Emby fit that bill and has the benefit of sounding like "MB" when you say it. With the new name, we needed a new logo and we actually held a contest in the forum taking contributions from users and that finally landed us on the logo you see now. Since 2015 we have expanded the team and worked diligently to try and continue to craft the best truly personal media server system we can. We still have a long way to go but have also come a long way to where we are. What are the most popular Emby clients? We do not have exact data on this, due to sideloading and the such, but through the app store platforms we can gain general ideas. Android is the most popular amongst our userbase (both mobile and TV) with iOS in second place as the most downloaded app. What Emby clients do the development team use most for personal use? Our development team uses a wide variety of apps just as our user base does. We have people on the team using Android on mobile and TV, iOS, Apple TV, Roku and Xbox as well. As you can see our dev team really is as diverse as our user base when it comes to how we use the server. These were just a few of the questions about Emby as a product and who we are. In the next blog post we will be covering a few different things such as some of the future goals of Emby as well as release schedules and more!

I will also add that I never had this problem until a few months ago and with the most recent update (4.8.7.0), I didn't have this issue this time.

OK we'll look into why this might be happening. Thanks.

I think I may have figured it out. I may have just needed to update Emby to specify what external ports it was telling the client to use. I'm doing some testing. **I get it now. I was testing in a browser with http://tv.mydomain.com I didn't realize the Emby apps stored a local and remote config. Now that I realize that and put in the correct port for remote access, it looks like all is good. Thank you.

We will, it's planned, not just a hopeful.

Thanks

I did a quick and dirty update to work with githubs new json output. I filter the output with jq So this update would need you to have the jq package installed. emby_updater.sh

I created a script you can run within the container I shared, should be a GitHub link. Run the whole thing.

Yes exactly, session stacking of same user in UI.

Good to hear, thanks again!

Alright, this new DLNA plugin version indeed fixed the issue! Thanks! Will this fix be applied to the regular releases now?

Messed around a with it a little bit. Got it to work with the Android app but still not with a web browser. Noticed the "Include adult metadata" is also missing

@Noel-Mapologies for the delay. This should be resolved in the upcoming 4.8.8 Emby Server maintenance release. If you need immediate relief, the fix should be on the beta channel by tomorrow. Thanks !

@Abobadermay be able to help. But what do you mean by can't access your old/original account?

Now on my device I can install it, but it's asking me to buy, since I had already paid for the other app, it doesn't make sense to have to pay again...

Nothing, it's definitely the way to go! ABS is also tag driven. You just need to support more relevant tags for audiobooks and add a scraper like audible.

Personally, I think there is nothing wrong with being tag driven. I continue to suggest that emby needs to import and respect the additional tags mentioned in this thread (Narrator, type, part, series, release group, description, etc) and refine the UX to leverage this data. Many of us have already tagged our collections, but we need emby to import and utilize those specialty tags. Once these tags are imported the pages and OSD need to reflect the differences between audio books and the music library type. Yes, they can use the same containers and import tags, but the user requirements are different. It doesn't need to be a complete rework from the ground up. Emby needs to properly display narrator, author, ("author" read by "narrator") for audio book media pages. It should not say "songs" or "artists" anywhere. Further, chapters should be listed as lines of text without the same image over and over. It should have navigation for book, authors, narrators, series, collections, genre, continue listening, next up (series), and other things mentioned here. The OSD should have chapter lists if there are chapters in the media (again, without the repeated images - just text). The tricky bit is to elegantly craft a UX that support books that are albums with individual chapter tracks and m4b files with embedded chapters. My comments about audio series/podcasts/radio being a different library type are I related to my belief that they can best be displayed in a media info page that has a layout more like TV Shows with seasons and episodes and Cast/People instead of artists. It should include"people" as they are often tv/movie talent as opposed to music which are "artists." It can still be tag driven, but the UX is slightly different than music, tv, or audiobooks. All of this is akin to how the music video library type is designed to have metadata for both artists and people. It displays navigation elements that support things like albums, artist images and logos like a music library but also cast, directors, descriptions, and an OSD like movies. It's a separate library type, but it's just mashup of two other types so it can accommodate a specific use case. That said, it shows images correctly and displays the important navigation and metadata correctly (artist, director, cast, year, release date, genre, etc.). Audio books needs more help than music videos at this point.

I would consider it more than a workaround. I personally think it makes a dedicated guest feature unnecessary.

What is the problem with being tag driven for audio books?

So wie ich das sehe, scheinen Sie keine Antwort zu erhalten. Das ist schade - sah so vielversprechend aus - hätte ansonsten nämlich mal einen Test Monat mit Emby Premiere gemacht. Aber scheint ja so vieles nicht zu laufen.

These things are hard to find as barely anyone does the testing. The 1060 might be a bit faster, but again you need the driver hack. The A310 will produce better quality encodes, and doesn't need a power adapter to do so. You might also want to look at the A380 as it is also available in a bus powered version, and has more VRAM than the A310, and is roughly the same price as the A310.

@Luke- Hi - so are we any closer to Home Screen Smart rows/libraries/channels - based on smartlists ? I halted my own efforts to get this 'working' (hacked) but stopped as you advised it was something you were hopefully working on back in August of last year post the 4.8 release... Its now 9 months later - 4.8 has been and gone - Is it even on the cards ? If not, then I'll carry on with my own 'hack' (and now wish I had just carried on with it..) as my own users are now fed up waiting for this essential missing feature ...

Here is the next round of answers from our Emby Q&A session. The feedback from our previous blog post was exciting to see from all of you, and we are excited to share even more answers. The next round of questions and answers will be released next week as well! 1) What are some of the future goals of Emby? Emby wants to continue to grow and be the best media server option available for our users. We hope to move to a quicker release schedule than in previous iterations that is both more efficient from a development standpoint and exciting for our users. We love what we do here at Emby and we want our users and potential users to see that! 2) Would the Emby team ever consider moniterary "bounties" to help offset the development cost. We have actually seen this question a lot lately. We do not believe that this is the best way to decide what goes into development for a few reasons. First and foremost, we do not want people who have more money than others to decide what goes into production while others who may not be able to afford to donate or contribute go unheard. 3) How does the Emby team decide on what's next for Emby? The answer to this is deeper than most people probably think. Feature requests is one place that we look at to form our roadmap of future goals. Sometimes it's as simple as user feedback that something is not working as intended or could be implemented in an easier way to use etc. Other times our development staff has ideas based on industry trends as well as their own experience that they believe should be implemented. We take all of that and as a team decide what should be added and when. 4) In what areas can Emby improve? We as a team are always seeking to improve. We fully acknowledge that as a small company we are sometimes stretched "thin" but we do our best to always be both proactive and reactive with all of you. As mentioned above we hope to move to a quicker release schedule with a more agile methodology that allows us do so. We think we do a pretty great job at communication with everyone here on the forums, but we continue to strive to be even better here as well. Being able to give more flushed out answers and as much information as we can. Our goal is to always continue improving.

You guys are doing great. For me, Emby has been working great and with very very very few issues for several years. From that perspective, the current release cadence with a sufficiently long QA period seems to work well. Be wary of growing the team; more coders require more revenue and that may require bigger adjustments to the business model than discussed elsewhere in the forum.

Mistake: Do not set Emby to listen on 443 - that's Caddy's job, and if they're on the same machine you have a conflict. Mistake: Do not set the router to forward port 443 to 8096 - it goes to port 443 in Caddy; it is Caddy that then contacts 8096 in Emby, which the router doesn't know about in any way. Your clients all talk to Caddy, not Emby. It's right to set Emby to accept remote connections, because Caddy passes the remote client's address through for it to assess. You haven't shown the setting in Emby for "Secure connection mode", which should be set to "Handled by reverse proxy". Paul

That's a lot of drives to connect via USB, most USB drive connectors are junk. Some present the actual drives to the operating system, some appear as individual USB devices with absolutely no reference to the drives connected to them. While convenient I don't trust them as far as I can throw them, I've seen them throw constant errors for a drive or all the drives (4 drive enclosure) that work without error in a different enclosure. An HBA would be much better suited to address that many drives and would likely result in higher throughput as well, though you'd probably need 2 of them depending on the model as I believe most have 2 SFF-8087 connectors and those typically only break out into 4 SATA each, and would need a case that supports holding that many drives. eSATA is also a decent option though I don't really have any experience with it, would need an enclosure that supports it. I've had months of uptime on my server before without a reboot, which is great for stability and uptime but definitely a bad security practice.