All Activity

What's funny is, http://localhost:8096/web/index.html#!/dashboard/ doesn't seem to get me to the admin section. If I add "settings", then it works. http://localhost:8096/web/index.html#!/dashboard/settings I'll keep playing with it. My server is located in a very inconvenient place of the house where it is a pain to get at.

In Plex you can merge anything, and it becomes one item with as many parts as it had before. So for example, if you have one video in multiple parts and it is for some reason showing as multiple videos, you can merge it and it becomes one video with multiple parts and you'll see them in order. In Emby you can group videos, but they become different versions of the same video, so if it has part 1 and part 2 you group them, when you watch it you'll only see one of the two parts (which you select from the menu). Grouping is a good feature in that you might want to group different versions of the same thing - like if I have a 3D movie and the 2D version of it, I can group them and they show as one item in content and I select which version I want to see at time of playback - but you can't group everything, so even when I have 3 versions of the same book I can't group them. However, we digress. My problem was that Emby shows individual albums as multiple albums, and I wanted a way to put the album together. Apparently this is caused by the metadata, and correcting the metadata corrects the problem. This does not deal with my underlying issue, that my music collection was created mostly with iTunes, the most popular mp3 program, so if Emby can't deal with that, Emby is failing. Also while I can edit the metadata for a video, I can't edit much of the metadata for a song, and I have to use a third party program to "fix" the metadata for my music collection to make Emby deal with it, which from the perspective of a software engineer means that Emby is being inconsistent (I can do it with videos but I can't do it with audio) so that's another failure.

Seems when I get above 300+ish items in a collection, created using the api, it fails

You peps are over complicating this, this takes care of the gear cog allowing admin stuff or not: and besides CSS stuff only works on web browsers...

You will have to Refresh with replace images but please retest in 4.8.6.0. Extract video images at full resolution

You will have to Refresh with replace images but please retest in 4.8.6.0. Extract video images at full resolution

Thanks, I'm all about FOSS (for my projects anyway). Not in terms of not receiving an OK 200 response. I have found if I start making the rule sets for a collection too specific, I don't get any results back (typically 7-8 rules in a set), however, that seems to be the breadth of my library.

Ok thanks to you @RanmaCanada@qyour answer so I think I will take the i7-14700k because there is a difference of 200 euro for 4 e cores more and yes it is to do 9-10 transcoding at the same time with Tdarr and other we agree that the i7-14700k is sufficient or is it better to take the i9 (I know it's the same igpu)? Even if later I do several vm? (I'm sorry to ask so many questions, but I want to be sure before ordering that it's a big one)

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. View the full article

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.

OT: Glad you figured it out as that is odd as the dlna.xml is part of the full backup.

That was it. I guess not ALL settings transferred over. DLNA control was not enabled on the server.

User account Gear and user icon are the same. admin account Gear takes you to dashboard

OT: Not entirely sure but would suggest discoverability issues. But if clients are still able to connect I am out of ideas.

But users do not have admin functionality and is restricted by default. So you would need to clarify functionality as you are hiding user config sort of. As all css is circumventable via console. But yes assuming you are logged in with admin user "Configure Emby" via tray is an option as it is the same as I already said via direct url http://localhost:8091/web/index.html#!/dashboard.

Tried logging into the server on a different browser and can cast to one another which is interesting but not the TVs that are logged in.

OK, I found a way to get in on the host machine using the tray icon. As I want to be able to administer the server from different machines, I can take the CSS out that hiding the wheel for the time being. However, it's not a perfect solution as I want admin functions hidden to users.

@GrimReapercan you move this to FreeBSD for better visibility as it is beyond General/Windows

Hi there, I read a post recently that mentioned that Emby is going to be updating the forums soon to a newer version? Perhaps Emby could therefore consider including some sort of dividing of Feature Requests into Media Categories, i.e.: Movies Music TV Shows Audiobooks Books Games Music Videos Home Videos & Photos Mixed Content as per the current Library Categories that are available to set up now. If this was too many categories (it probably is), then perhaps a limited (more popular) set would be better, e.g.: Movies Music TV Shows Other These could possibly be separate Sections or perhaps a fixed Official Tags approach (not the arbitrary ones available now). this could make it easier for members to view the relevant topics of interest, grouped together, and less likely to repeat a request. this would likely make it easier for Emby to review requests (individual or combined) for a given media type. I am imagining a tagging approach could be somewhat similar to the current Feature Request Status Tags: but this would depend on the format of any forum updates, of course. If this was relatively easy to set up (short-term) it would have increased future benefit (long-term) as the forums grow much larger with increased content. Thanks for considering. P.S. A similar Official Tags approach could also be useful across the forums, in general, not just Feature Requests.

That's what you said two years ago, and still do.

Yep. It's a simple pkg update && pkg upgrade from the jail's console. Tried again but it said everything was up-to-date.

Okay yes drawer options have been removed per all the redundancy (drawer, user icon, gear). No you still have options but what if you went to the connection you already have ie http://192.168.0.5:8096/web/index.html#!/dashboard (unauthenticated sessions will bounce to login screen so you would reauthenticate and go to dashboard url if using localhost) But have you brought up the browser console and selected a near element to get to actual hidden element as shown in image? To me that would be the easiest route but will need a understanding of that console. Last resort delete/edit the branding.xml and restart Emby. path will be platform prevalent. C:\Users\username\AppData\Roaming\Emby-Server\programdata\config\branding.xml

Have you tried updating 3.8.5.0 again as those logs are from 4.7.14.0. But am not familiar with the platform at all.

Now as for identification since folder and file do not match here the actual queries area the issue with Special edition returning result from api while Theatrical does not. &query=Alien Resurrection - Special Edition&language=en-US query=Alien Resurrection - Theatrical Release&language=en-US

Noted. @Luke, attached the output from my console for the most recent testing yesterday and some of the day prior. Emby Server Log 1.txt Emby Server Log 2.txt