Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/23/22 in Posts

  1. he said " the best personal media server available" not "the perfect media server". they've already achieved the former IMO
    3 points
  2. Is it still your plan to reach this goal? Because there are so many request from 2015 etc. with enough + on it to see user want to have it and if we ask it seems like pre programmed answers luke bound to his keyboard. It is always the same: good idea for future updates, not yet we are working on it, it is planned for the future etc... i hope you can understand this makes people really angry and losing hope, so maybe think about the way you handle and take care of bug reports and feature requests. I am also a programmer and i see a lot stuff could be done easily, not everything ppl want is a huge change. I am using emby now for about 2 years and some of my first requests are still not done yet (security related things) like revamp user permissions, prevent deletion or modification of playlists for non admins etc. This should be something you really need to focus, bugs and security features instead of fixing some visual problems with some subtitles. Emby has a lot of potential but it really looks most devs give a shit on the users, i absolutely understand not every request makes sense and not everything can be implemented. But requests since 2015, its better to say clearly, we dont wanna implement it instead of putting people off again and again. I am really interested if the new stable will have the permission revamps and hide of storage locations for non admins etc.
    3 points
  3. Hi. That simply wasn't the case. JF didn't do anything wrong because we had published our code as open source. But it was all our code. Everything that was closed was created by or contracted (and paid) for by Emby. Actually, I do have one beef with the JF devs - they went in and deliberately removed attributions from code that showed that we originally created it. If that isn't illegal in the OSS world, it certainly isn't within the spirit of what they supposedly stand for.
    2 points
  4. What you consider a theft is what Open Source Software is all about. You can fork it an modify it by your needs. If you take a little twist you could also blame the Emby Devs as thiefs because they took an Open Source product which volunteers contributed to and transfered it into a Close Source commercial product. Also what they did was not illegal. So who to blame. At least there is a free of cost Version of Emby left. I dont like the closed source Character of Emby. There are problems in the Server and the Client persisting for years (eg Wake on Lan on the Android Client, LiveTV cant handle multiple resolution m3u) or feature request which are caught in the "friend zone" forever (customizing new Media Notification, New Media Webhook). Things that could be done by the community with the source code and a bit of documentation. I stick with Emby because i got a Lifetime License time ago. Am I happy with the product? -> Yeah most of the times Am I happy how Emby progresses and how the community is involved? Absolutely not.
    2 points
  5. yep like the last two posts, its like going back in time with emby.. I install it now and then too. Like the wayback machine.. I don't really agree that opensource is better or worse than closed source. Open is nice for getting in and looking around, making custom changes... People like to say "I only use opensource" these are like the Whole Foods shopper of software though... Opensource has it's place. Just like whole foods lol.... I laugh every time I see a new post in this topic.. like "it's still alive?"
    2 points
  6. Here are 4 pre-rolls I created using Motion Array templates. (I have a subscription.) Emby-Dark-Tear.mp4 Emby-Explosion.mp4 Emby-Fire-Explosion.mp4 Emby-Space-Trails.mp4
    1 point
  7. Please bring this back as this was already a feature at some stage?
    1 point
  8. Not sure but that was going to be my next suggestion.
    1 point
  9. You can put hispaxxx.homepc.it in External Domain. But from a WAN address standpoint that is the purpose of Connect as it will auto update your detected address.
    1 point
  10. FYI, issue resolved in SCB v1.4.8.0 update. https://emby.media/community/index.php?/topic/101693-best-practice-for-maintaining-production-and-beta-emby-installations/&do=findComment&comment=1119344
    1 point
  11. You have to understand that we (Emby) have no control of or even knowledge of your private server users. So anything like this will require some setup and maintenance on the individual server owner's part. Plus, Implementing a security measure that only works on one specific platform would be a waste of time for sure. If it cannot be enforced system wide, there really is no point. But this is a digression from this discussion so we should just end it there.
    1 point
  12. Reading this: https://github.com/MediaBrowser/Wiki/wiki/Excluding-files-&-folders Does placing a ".ignore" in a folder apply make emby ignoring all the the subfolders to it? I assume so and if I'm correct I suggest you rephrase that page above to be explicit. Many thanks :-)
    1 point
  13. It's empty, if I click on the arrow I get the local account name of my Windows PC. This was 'Default' and I changed it to 'No subtitles' and now no transcoding happens and the subtitles are shown from the external .srt file. Thanks a lot for your help
    1 point
  14. also to mention, while testing we found that setting this to a high value it is getting less accurate results. We have a few testers with very strong machines but most of us stay at lower values for better results. I also started with 6-8 but went down to 1 for chromaprint and 4 for detection. You would speed it up by having a lower value as it will bring your storage to the limit and if the plugin needs to wait for the storage to read/write the already calculated results it takes much longer.
    1 point
  15. I have great respect for Luke, but I don't think that he will be able to tag content that is outside the Emby environment. He may be able to create a "black list" of names. This would quickly become un-manageable. My guess is that Luke was referring to Emby content only. Vic
    1 point
  16. Fingerprinting is mostly limited by the speed of your storage not your CPU, and putting the Chromaprint setting too high could actually cause it to be slower. Once you get to detection, that's when it will use a lot of CPU power.
    1 point
  17. This will be implemented in the upcoming 4.7 server release. For those on the beta channel, that's 4.7.0.26+. If you run the beta channel and you still see examples where you think it's not picking the highest quality, then please open a topic in the testing area of the community. Thanks.
    1 point
  18. Hi, I think the Shield is probably still the most robust device. I'm sure the issues relating to the recent Shield software updates will get cleared up in time.
    1 point
  19. so...... emby is the best media server for you.......? the online login and tracking of data by plex is a non-negotiable for most users here. there's currently nothing plex does over emby that would make me give that up
    1 point
  20. https://forum.opensubtitles.org/viewtopic.php?t=17020
    1 point
  21. "Best" is up for interpretation by the user I think. If it's not the best for you, that's perfectly okay. Many here think that Emby is the best for the exact same logic of what Plex has done. Many don't want all of those features, tracking, and telemetry. So what is your best available? I'm honestly curious. Fair enough, but writing a script for a single case is far from implementing a feature in a cross platform application. You're script isn't going to work on my official Docker container running on Unraid. So how long would it take you to create that same function, make sure it works on all 4 major server variants, and then test that it behaves as expected in hundreds of combinations of environments and clients? The Emby team is still small for the product that they produce/maintain. I personally think they do a good job balancing bug fixes and new features. No, it's not iterating as fast as Plex with their MUCH larger resource pool. Emby has to carefully balance new features and fixes with demand for those changes. A quick look at the Releases page shows that the team remains very active in adding features and fixes. https://github.com/MediaBrowser/Emby.Releases/releases
    1 point
  22. Some of the requests of users i solved with poweshell scripts in 10-15 mins so it could not be that hard to implement it in emby. i published a lot scripts for other people here, so if the devs have no idea how to do it, they should use those scripts as a template and just migrate it to .net language.
    1 point
  23. Looks like you're trying to delete a video but emby server does have access to delete your files. Can you take a look at this?
    1 point
  24. Our original vision was for it to be open source but, as it developed, we found that we were not going to be able to reach our goal of being the best personal media server available with that model. It was going to require full-time investment and resources. In hindsight, we left the code open for much too long.
    1 point
  25. @Luke FYI - I started an authentication issue over at the repo. If you have any input go ahead and add your insight. Also, if you have any other separate issues you think may be apropos, feel free to open up other issues.
    1 point
  26. You need a case that holds more drives.
    1 point
  27. That done it. Deleted and ran a library scan
    1 point
  28. Dans le menu Emby Premiere, il y a une option pour récupérer la clé
    1 point
  29. You can use Reports plugin and sort by Community rating (stars) and/or export list to sort in external program. @Happy2Playmaybe "Collection" column could be added to Reports plugin for sorting and further export, if needed?
    1 point
  30. USB hubs are inherently unreliable and shouldnt be used in a drive pooling config imo. avoid using a usb hub and your problems will go away. in fact you've pretty much proved this
    1 point
  31. On the users profile page, completely clear the 2nd field "Emby Connect username.." and hit 'Save' Then re-add the Connect username, and hit 'Save' once again. You should see a notification that it's been added successfully.
    1 point
  32. Option to eliminate this stream "buffering" is what I would prefer Example: TiviMate
    1 point
  33. Hi, yes this is coming in the 4.7 release. Thanks.
    1 point
  34. I got one in 6.2.9 - addon mode. Had an episode in 720p which was already indexed by emby and synced to kodi. Did an Upgrade to 1080p, which means 720p version was delete physically and replaced by 1080p version. Emby reindexed and only had 1080p version afterwards as expected, but in kodi both version were in the library. So it seems like the 720p version isn't properly removed from kodi library. On another instance I added emby addon afterwards and the 1080p version was added, so emby db seems to be fine, only removal is a problem.
    1 point
  35. Yes, you have to make a new library. I use filters to select what is in the category, however filters don't work on some iterations of Emby. So, it will show all items in the library when viewing those, some people take the time to sort everything on the drive and don't have that problem.
    1 point
  36. Thanks FrostByte, I'll try watching something again this evening and get the app logs from there. Sorry about my newness here. Like I said, my setup has worked so well, I've never really had to dive into it before!
    1 point
  37. Though the server logs may help, I believe ebr was asking for the logs from the app and the instructions for that is further down in the link he provided. Basically, you click "Enable debug options" in settings and then when the problem occurs again immediately send the logs from within the app either using the cog wheel or the menu under your user icon. If the app crashes then just restart and send the logs right away. After the logs are sent let him know what time you sent them and the user which was logged on. There is limited buffer for logs so try to send the logs as quickly as you can after the problem occurs.
    1 point
  38. Yeah, that turned out to have been it. I had tried it before posting, but I tried again after capitalizing the container name and that seemed to have done it.
    1 point
  39. It was just saying that things are moving, even if we haven't gotten to this specific thing yet. But stay tuned.
    1 point
  40. Performance testing 1: Multithreading and low-resolution decoding I've done quite a bit of performance testing and optimization in the last few days. Herein I present my findings with two comskip parameters mentioned above by @TMCsw: thread_count (specifying the # of processor cores to use at once) and lowres (decoding the video file in "low resolution" mode). Test environment Hardware: Intel NUC10i7FNH NUC 10 Core i7 with 32GB RAM and a 4TB SSD. # of cpu cores: 12 @ 1.10GHz OS: Ubuntu 20.04.3 LTS (64 bit) Test file 61 minute show recorded with my HD Homerun Codec: 1080i MPEG2VIDEO Resolution: 1920x1080 Framerate: 29.97 Bitrate: 8,139 kbps Bit Depth: 8 bit Pixel Format: yuv420p Test procedure and data collection Here are the steps I took for each test. Record the server load by running the following command from a terminal window (terminal A): while true; do uptime >> '/home/username/Downloads/uptime.log'; sleep 1; done In a second terminal window (terminal B), modify comskip.ini by adding the parameters below. In my case, I tested variations and combinations of the following (where X and Y are an integer between 0 and 10): thread_count=X lowres=Y Run comskip in terminal B. When complete, terminate the uptime command in terminal A. Record the following data in a spreadsheet: decode time (from terminal B). peak 1-minute server load (from uptime.log saved in step 1. Delete the contents of uptime.log file and return to step 1 to test a new parameter. Note: Most of the data below is simply the result of one test (n=1). Anecdotally, identical parameters produced very similar results within a few percentage points of each other. Interpreting the results The two metrics I followed in this test were the total time required for comskip to complete (the decode time), and the server load. My server generally operates at a load of 1.2 when not recording a show, detecting commercials, or transcoding video. I have noticed that Emby works well at a load of 4, but I am hesitant to push the load above this for fear of affecting overall server performance. For a full discussion of server loads in Linux, this is a good resource. For most folks, having fast commercial detection without a big impact on server load is ideal (especially true if your server has a loud fan!). My goal is to make commercial detection as fast as possible while keeping the peak server load around 3. Results Note: All the graphs below are color-coded: blue represents decode time and red indicates peak server load. Multithreading I first tested the effect of enabling multithreading, or using multiple CPU cores at once, to detect commercials. As shown below, a significant reduction in decoding time was achieved when thread_count=3 was added to comskip.ini. Only marginal improvements occurred with additional cores/threads, while server loads trended upwards. I concluded from this data that thread_count=3 was best for my system. Lowres I don't really have a clear understanding of how the lowres parameter affects comskip performance, but I imagine it has to do with how carefully it examines each frame of the video. In any case, the data was clear. As shown below, increasing lowres did not increase the server load in a consistent way. However, lowres=2 dropped the decode time by about 30% (remember, thread_count=3 was held constant in these tests). Note that lowres=10 automatically sets this parameter to the best value. In my case, the data using lowres=10 (not shown) was a very close match to lowres=2. I concluded from this data that lowres=10 (i.e. lowres=2) was best for my system. Update 2/25/2022: The lowres=10 is great for performance, but the accuracy was not appropriate. I adjusted to 5 with much improved results, but eventually removed the parameter entirely. Multithreading + lowres As a final test, I compared the individual effects of lowres and thread_count to the combined effect of both. Consistent with the other data presented, thread_count=3 and lowres=10 had signifiant individual impacts on decode time. Together, the two parameters produced a nearly 60% reduction in decode time. Server load increased 44% under the same conditions. However, the peak load was still close to my desired threshold (3). Importantly, the higher load was short-lived. Conclusion I concluded from the data that lowres=10 and thread_count=3 was best for my system and I'll be adding those parameters to my comskip.ini file. Next steps In my next analysis, I'll be looking at server performance when running comskip as a post-recording process compared to running it in real time as recordings occur.
    1 point
  41. That has been the easiest way to give some extra head room to the transcode process making it work a little better. I've personally found for me it's mpeg2 that cause the issues and not h.264 streams. I notice the difference the most for 1080i sports matches. I'm doing a little experiment right now all through the Olympics which I've been watching on NBC (mpeg2) and USA (h.264) from Xfinity/Comcast. So what I'm doing is feeding my hdhomerun through another program converting any mpeg2 stream to h.264 so Emby is only getting h.264 channels. I've not had any of the typical issues I was see before watching sports especially very fast scenes which we've had plenty in the Olympics. This is using the .17 beta release same as my other testing.
    1 point
  42. You’re kidding cnwinger, yes? It seems to me that the Emby team don’t really care about us AppleTV users. This is a (basic) feature that makes Emby completely unusable for large library users on AppleTV and yet it remains ‘on the list’. That’s how important we are to Emby. I held out as long as I could but recently bought a lifetime Plex subscription. I don’t like Plex as much as Emby but they have a product that works. Somehow they managed to do what Emby says is very, very difficult. Hmmmmmmm…..
    1 point
  43. OK, there's a good chance this is improved in the upcoming 4.7 server release if you'd like to try the beta channel. If you still have issues we can work together there to iron them out quicker.
    1 point
  44. Hi, more control over this is planned for the future. Thanks.
    1 point
  45. I've updated the main post with a updated version for Emby Beta (v.4.7.0.20) if anyone is interested It looks the same but with some small fixes here and there.
    1 point
  46. Hi there abegreen, Thank you for your feature suggestion! I've successfully located the core hooks for the event you've requested, along with a bunch of others. So when I 'favorite' or 'like' a media item, emby signals UserDataSaved, which gives a tonne of functionality along with some variables that I will tokenize. The event will be onUserDataSaved. You'll be able to set a condition where %save.reason% equals 'UpdateUserRating' Then you'll be able to check a token %is.media.favorited.or.liked% which will be True or False. I'll finalise the implementation and release it soon. 'Favorite': 2021-09-05 22:12:09.369 Info Emby ScripterX: UserDataSaved > ItemName=SuperTed, SaveReason=UpdateUserRating, Username=anthony, IsFavoriteOrLiked=True 'Remove Favorite': 2021-09-05 22:12:08.433 Info Emby ScripterX: UserDataSaved > ItemName=SuperTed, SaveReason=UpdateUserRating, Username=anthony, IsFavoriteOrLiked=False
    1 point
  47. We Apple TV users have been waiting for this basic feature for a long time now. When we switched to using Apple TVs as our media players, (for reasons unimportant), I was shocked to discover this missing critical feature. It made my large movie database unusable. As a result we abandoned Emby in favour of Plex which DOES include it. I like Emby and would like to return from the Dark Side but until you pay attention to your Apple TV customers I must use what works.
    1 point
  48. 1 point
×
×
  • Create New...