Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/28/25 in all areas

  1. Yes it is. Thank You for telling me so quickly. I didn't notice anything funny happening. I will now just ignore that warning. Have a good day. Larry Jones
    2 points
  2. Yes - to h264 if on the stable release, or the option of h265 (experimental) on the beta. Either way, the AV1 transcode on those clients will lose quality - but it will play.
    2 points
  3. This works for HD trailers from the trailer button on each media page: Turn on .nfo files in local directories. If you have not had this turned on, you may need to reload the media again to get the .nfo files into the local directories. Find the <trailer>plugin://... line in all .nfo files Replace </trailer> with this at the end of each <trailer> line: ?iv_load_policy=3</trailer> So the trailer lines change from the old version to a new version: Example is 'Mickey 17' (2025) <trailer>plugin://plugin.video.youtube/play/?video_id=osYpGSz_0i4</trailer> <trailer>plugin://plugin.video.youtube/play/?video_id=tA1s65o_kYM</trailer> <trailer>plugin://plugin.video.youtube/play/?video_id=osYpGSz_0i4?iv_load_policy=3</trailer> <trailer>plugin://plugin.video.youtube/play/?video_id=tA1s65o_kYM?iv_load_policy=3</trailer> You can do this by finding all the .nfo files. Windows let's you do this using Windows Explorer, search for: *.nfo -"<trailer>". Open all these .nfo files in a good text editor like edit+, or your favorite, full featured, text editor. Step #2 above... search and replace through all the open .nfo files. If you do it correctly, you should be able to change 1000+ media trailers to HD trailers, (if a HD quality trailer is available), with a couple of minutes work. Enjoy.
    2 points
  4. Let me preface this by saying that I have been running a Windows server for quite a while with no issues (same file paths). Although, now that I think of it, I didn't use the optional network path on the Windows server. I recently (yesterday) converted my Emby server over to Linux. I have a SMB server that I use for my media. My TV library has 2 different folders: local mounts are /media/TV and /media/TV2 Optional Network mount points are: \\10.3.0.140\TV\TV and \\10.3.0.140\TV2 (as mentioned above, I didn't need this when I was running Windows) No matter what I did the network mount points for TV2 were being created as \\10.3.0.140\TV\TV2. Which doesn't exist, so I couldn't watch the episodes when the network path was required. I did fix it by changing TV2 to /media/alt_tv and \\10.3.0.140\alt_tv (obviously I changed my SMB server mount points as well). But I thought I should report it just in case it wasn't just a glitch in my system, but maybe a bug.
    1 point
  5. Hello, Perhaps I am not the first one to ask this question but it will be very cool if this feature could be implemented. I have 2 servers one at home and the other at work. ( and soon a third one...) So I have a movies library called movies on each server. I would like to see all the movies from a single 'virtual server location' when I use the app (ios or android ) where I will see only one movies library containing movies informations from the movie library at work and the movie library at home. It's an aggregation of movies informations from the movie library at work and the movie library at home. In fact when a user have multiple servers it will be perfect if another choice in the server list called "all servers" for example appears automatically with a merge of media informations from librairies with the same name on different servers.
    1 point
  6. Usually h265 or h264, so lossy to lossy, so there will be some quality loss, but I doubt I'll notice it and if the filesizes are a large difference I'm willing to accept that loss
    1 point
  7. Salut, je regarde ça demain et je te dis Merci encore !
    1 point
  8. Hi @Lukedo you have any info on when you'll compile ffmpeg with the proper lib supported? If you want I can do some testings
    1 point
  9. I'm not sure why that would be flagged as a virus, that JSON just has a bunch of links to images for covers, it looks like it's related to the Whitesnake album Slip of the Tongue. Is that in your library? https://musicbrainz.org/release/06fc6074-eb8c-3d18-9244-aea3353d071d It also looks like coverartarchive.org becomes ia601000.us.archive.org or ia801000.us.archive.org (maybe others) since I see a 307 and 302 redirect before it loads the image.
    1 point
  10. Thank you, I thought that would be the case but wanted to double check before setting up all my library to get re encoded to AV1.
    1 point
  11. I will share an update on this in this thread when I have one.
    1 point
  12. 1 point
  13. I am on the latest beta now (since this week I think). Now it seems to work again. I will test wether this is permanent.
    1 point
  14. Since upgrading to Emby 4.8.11.0 on my Windows server, Emby Server CPU usage is at 12 to 14% when there are no active streams or any significant activity going on. Clients are slow to load images and information. I could see a lot of entries for Iconic Image Enhancer in the logs, so I disabled it, and after doing that, things returned to normal. There might be a compatibility issue with this plugin and the new version of Emby? Example of a log entry: 2025-04-28 10:03:23.249 Error ImageProcessor: Error in image enhancer: ImageEnhancer *** Error Report *** Version: 4.8.11.0 Command line: C:\Users\user\AppData\Roaming\Emby-Server\system\EmbyServer.dll -noautorunwebapp Operating system: Microsoft Windows 10.0.19045 Framework: .NET 6.0.36 OS/Process: x64/x64 Runtime: C:/Users/user/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll Processor count: 12 Data path: C:\Users\user\AppData\Roaming\Emby-Server\programdata Application path: C:\Users\user\AppData\Roaming\Emby-Server\system System.ObjectDisposedException: System.ObjectDisposedException: Cannot access a disposed object. Object name: 'SqliteItemRepository'. at Emby.Sqlite.BaseSqliteRepository.CheckDisposed() at Emby.Sqlite.BaseSqliteRepository.CreateConnection(Boolean isReadOnly) at Emby.Server.Implementations.Data.SqliteItemRepository.GetItemById(Int64 id) at Iconic.Main.ImageEnhancer.GetIcons(BaseItem item, Boolean forceRefresh) at Iconic.Main.ImageEnhancer.DoProcess(BaseItem item) at Iconic.Main.ImageEnhancer.MediaBrowser.Controller.Providers.IImageEnhancer.Supports(BaseItem item, ImageType imageType) at Emby.Drawing.ImageProcessor.GetSupportedEnhancers(BaseItem item, ImageType imageType) Source: Emby.Sqlite TargetSite: Void CheckDisposed()
    1 point
  15. The article has now been removed from the index and amended to mention that the functionality is now within Emby Server Thanks for reporting this
    1 point
  16. I added some color gradient backgrounds, made a "Live TV" icon and figured I'd include a photoshop template in case anyone wants to make some edits easily. Font is "Nexa Bold" SimpleEmbyIcons.zip EmbyIconsPSTemplate.zip
    1 point
  17. Just adding my support for 2fa. Was kinda surprised that it wasn't already available. I have had so many users get phished in the past (not so much emby users, but at my work) that I really hate having anything that doesn't utilize 2fa. With that said, I agree that there has to be a balance between security and convenience.
    1 point
  18. I can't figure out how to edit my post for some reason, but I was going to add that something I didn't think about was that my Backups also go to a remote SMB drive, so I had to also do the same thing for that mount. [EDIT: Weird, this post shows me as the author and lets me edit. the OP doesn't.]
    1 point
  19. Stopped me from accessing library. Redoing it right now. Have to finish. Has to be from a data site for covers etc.
    1 point
  20. This isn't just affecting iOS (iPhone) videos. Have the exact same issue with videos taken on multiple Android devices (Samsung S24+ and Samsung S25) and played back via Emby on Samsung TV app. Running Emby server 4.8.8.0 on Synology NAS. Playing the videos via Emby on a Windows PC or Android phone, orientation is correct for all videos. Playing them via Emby on Samsung 2022 TV model QA75Q70CAWXXY close to half of all videos taken from the above phones have incorrect orientation. Interestingly, all video thumbnails have correct orientation. But when played they go sideways and sometimes even upside down.
    1 point
  21. AppleTV doesn’t do Atmos, so it’s no go for me. If that doens’t matter to you, aTV with Infuse app is a solid option. (I’ve tried it briefly at home under the misapprehension that it did support Atmos.)
    1 point
  22. Hi, there is currently no way, but more options are possible for future updates. Thanks.
    1 point
  23. Thanks sa2000 (And I assume this is the same sa2000 that helped out in the Plex forums! Helped me a few times over there many years ago!). Hopefully you can sort it out sooner than later. I have over 600GB on the SD, so clearing the app and starting over is a pain (and impossible when in the road).
    1 point
  24. 1 point
  25. Emby for Apple TV 1.9.8 has been released. Here are the highlights: Fix video player back button behavior when paused Fix movie trailers tab only showing one item
    1 point
  26. Emby for Apple TV 1.9.8 has been released. Here are the highlights: Fix video player back button behavior when paused Fix movie trailers tab only showing one item View the full article
    1 point
  27. There are some more good things to say about TV Maze! Let's start with the one drawback they have opposed to others: The data is English only, they have no multi-language information. But the things on the good side are weighing strong: There's no other metadata provider from which we get so much information at once - from a single API call That's something I had negotiated with them and they made it possible: From a single invocation, we get the complete data for a season, means all episodes, each with complete data. With every other metadata provider, we need to make one call for each episode - with TV Maze, it's just one call for each season. So for example when a series as 4 seasons, each with 25 episodes, we need to make 4 API calls to TV Maze but 100 API calls to every other metadata provider. The TV Maze metadata provider has a new and different caching approach which makes sure that no unnecessary API calls are made. Advanced Data Update Mechanism No other metadata service tells you which data has changed (and needs to be updated) - with all other services, you need to re-query the data for every single item one-by-one, one after another because you have no idea about what's changed and what's not, so you need to re-query. In Emby's library configuration, that's the setting whether to update metadata regularly ("After the initial import, update ..." - like every 30 days, 60, 90 or never). That setting exists, because it normally causes a lot of API calls to refresh metadata from those services. But with TV Maze as the primary provider, you can set this to "30 days" without any worries! And that's because of the update mechanism. You might have seen the "TV Maze update" task running after re-starting the server (or on interval). It doesn't take long and what happens there is as follows: The TV Maze metadata providers sends a list of all the series for which it has/wants data for plus the date/time of the most recent update it did Then, TV Maze responds with a list of the series that have changed data since the specified date The metadata provider loads that changed data into its cache When Emby Server wants to update the metadata for certain items via TV Maze - the provider doesn't even need to make an API call - it already has the latest data in its cache Cache Persistence The cache of the Emby provider is a disk-cache, not a memory cache, so it survives reboots. So all in all: TV Maze is the most efficient and economic metdata provider that is currently avaiable for Emby.
    1 point
  28. hm... ok I've been talking to a few people recently who, like me, have said goodbye to Emby Premiere and the app. And the way things are going here, we won't be the only ones. That would have been a great option, with the information instead of the slogans.
    1 point
  29. Truncating file names to at most 255 bytes helped. All file names, that needed to be truncated, contained russian or other characters, that take up 2 bytes Requesting for long paths feature in linux
    1 point
  30. I would avoid a variable bit-rate encoding of the video. This can cause stuttering if any packets are received out of order across a TCP connection. Also, the user's CPU needs to work harder to combine TCP packets that probably do not aline with the variable bit rate I frames. This means info inside a single TCP packet will most of the time not include an I Frame. So, any follow-up packets have to be stored in cache waiting for the I-Frame info on what variable bit-rate is needed for the next 8 seconds or so. With Internet, packets can get out of order, fail and need to be requested again. This happens mostly with remote connections. If the I frame and following B frames have to wait to be processed to make the variable bit rate work, then you will get agressive stuttering on video playback, depending on the Internet connection to a remote user. The user's mobile or computer usually can wait a while for out of order packets. At some point if they don't show up, the end user's mobile or computer discards the previous packets and asks for all of them again. Variable bit rates (VBR) make this happen more often while constant bit rate (CBR) dosn't have this issue. CBR is much eaiser to handle with a TCP packet delivery. Out of order packets are not so critical. I hope that makes sense. This is why social media video platforms are not, I believe, using VVC with a variable bit rate, rather everything is sent with a constant bit rate, CBR. In order to get the best look on a CBR encoded video, it is best to make the encoding settings very high - Example for MP4 h.264 encoding with AVIDemux 1080P at 1920 x 1040 (1.85) original 25 fps, 24 fps or 23.976 fps Constant Bitrate (Single Pass) Target Bitrate 2400 kbit/s Frametyp look ahead 40 frames Motion Estimation Hexagonal Subpixel Refinement 11 best Direct predicition Spatial Weighted Prediction for P -frames: Weighted references + duplicates Partition Search 8x8 DVT Spatial Transfor, 4x4, 4x8 and 8x4 P-Frame Intra-predicted Blocks, 8x8 Intra-predicted Blocks, 4x4 Intra predicted Blocks (these higher settings for blocks helps reduce pixel artifacts in moving action, but take a lot longer) Frame Encoding CABAC B-frames Maximum consecutive b-frames 3 Adaptive B-frame Decision Optimal B-frames as References - Non-strict (Not Blu-ray Compatible) I Frames GOP size Minimum 16, Maximum 120 I-Frame threshold 40 Analysis: Mixed References Chroma Motion Estimation Trellis Qauntization - Always On Fast Skip Detection on P-frames DCT Decimation on P-Frames Psychovisual Rate Distortion Optimisation 1, Psychovisual Trellis 0 Luma Quantisation Deadzone: Intra Luma Quantisation Deadzone 11, Inter Luma Quantisation Deadzone 21 Quantiser control, Minimum 10, Maximum 51 Maximum Quantiser Step 4 Average Bitrate Tolerance 100% I and P-Frame Quantiser ratio 1.4 P and B-frame Quantiser ratio 1.3 Chroma to Luna Quantiser offset 0 Adaptive Quantisation Variane AQ Auto Variance, Strength 1. This config takes a lot longer to encode. Without hardware, encoding can easily take 4 to 5 hours for 1080P typical 90 minute film on an average Intel Core 7. The thing I have noticed, is that everyone tends to set the encoding level to go faster and this results in much large file sizes for a similar quality. High quality .mp4 1080P at around 2200 kbps, looks very nice and will be around 1.3 GB per hour. If you have high end hardware encoding, you might be able to reach that live, but usually not. As a result, most all hardware encoding that goes live tends to make larger file sizes in .mp4 and this is why people have preferred storage in h.265 .mkv. AV1 looks good. I have not used. I would still try to set it for highest quality encoding and a CBR, if possible. It does take more CPU power to playback compared to H.264. Here is a nice comparison page: https://www.fastpix.io/blog/av1-vs-h-264-vs-h-265-best-codec-for-video-streaming I think a better answer is slower, high quality encoding, CBR and get the file size down and not try to make it happen live. When you store the results that can play back direct, the video will look good, constant bit rate has less sutttering issues and direct play works for all users. Hope that made sense. Ha...
    1 point
  31. @raptorjrand @bobo99If you need pre-created subs look into Bazarr it can use whisper as an subtitle provider and create english subs from any audio tracks. Then I use Lingarr to translate them into other languages. Using whisper with CPU is slow. Did some testing. 45min episode. CPU time : around 50min too far behind real time. 13th Gen Intel® Core™ i5-13500 @ 2475 MHz using all cores. GPU time : around 3 min really great. GeForce GTX 1080 at 100% usage, but only for those 3 min. I short real time with only a CPU will get you in trouble, even with 1 stream Hope this info is useful
    1 point
  32. I would love the ability to allow a user to create collections (and edit item metadata and images). I would call those power-user features where a user can be allowed to edit but not delete nor have access to the full admin console. In my use case, I am the admin and I spend a good deal of time making collections or editing metadata for home home movies and video clips for which metadata is not available. For security reasons I would like to create a user who is able to create collections and do those things remotely, but restrict most of sensitive admin tasks to LAN only. Right now it's all or nothing. Either a user has access to the entire admin console, or they can't create collections, update metadata, or replace a poster image on a playlist they just made.
    1 point
×
×
  • Create New...