Jump to content

Search the Community

Showing results for tags 'image extraction'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support


  • Emby Blog

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 5 results

  1. As far as i know emby is capable of extracting images from series and movies. Especially on older tv series the images for episodes provided by the moviedb are often b*******. But because they exist, emby won't extract them from the media file and take the one from moviedb. Even if i delete them, emby won't extract an image anymore. I would highly appreciate to have a button to manually trigger the extraction of an episode image from media file. The same goes for music. Often the images embedded are better than the ones provided by audiodb. I would like to have a button to choose the embedded image over the one provided by audiodb. Thanks in advance!
  2. I'd like to a address a question here that is coming up regularly and sometimes getting into the focus of user desire as a must-have feature with apparent benefits. Obviously it's an evident conception that some graphics acceleration hardware should be able to accelerate graphics related operations like image extraction. But in this case that doesn't quite apply. The short answer to the subject question is:It wouldn't make a lot of sense. That answer is not really convincing, so let's get into depth.. Most of you will have noticed that we've taken great effort in the area of hardware acceleration for real-time media conversion (transcoding), so from a technical perspective it's not that we couldn't apply that to image extraction. But it doesn't fit well because image extraction is quite a different process. So, what's different here compared to transcoding? - Quite a few things: No Video Encoder Required In case you didn't know: In transcoding situations it's always the Encoder doing the hard part of the job. Situations differ, but to name some figures, you may imagine something like from 90%<>10% to 70%<>30% for Encoder<>Decoder processing requirements. In case of image extraction, it's just about a few hundred still images (jpg) to be saved - as opposed to thousands of video frames having inter-frame dependencies, so no video encoding needs to be done No video encoder also means, that there's no 70, 80,90% percent of the process that could be hardware accelerated. . There's no hardware acceleration for encoding jpg images The encoding of jpg images will always be done by the CPU. (Intel and Nvidia have an MJPEG encoder but that would require an additional processing step that might just slow down things altogether) . Decoding could be done by Hardware Right. That's the only part that could in fact be performed by using hardware decoders. But the simple question here is: Why? What would be the benefit? Getting the Job done faster? We still have the output jpg encoder running on CPU resources which is also limited to a single thread. So, that is the limiting factor actually - no matter how fast the GPU might be . => Would hardly be faster (at least not in magnitudes that would be of interest - e.g. 5x, 10x, 100x) . Saving Resources? When the GPU does the decoding, then there's less processing for the CPU, but the CPU will also have some additional load to handle:Copying video stream data to GPU memory A CPU based decoder can read the stream from a memory-mapped file without copying Copying decoded uncompressed(!) frames back to system memory Uncompressed video frames means huge amounts of data We need to copy those back to system memory in full size uncompressed, even though we just want to create rather small images from it . ​=> Would not save resources (significantly) Emby High-Speed Extraction Quite recently we've introduced a new mechanism for image extraction. This procedure requires only a minimal amount of frames to be decoded, many of them being keyframes. Previously we had to decode every single frame of a video for thumbnail extraction. With an extraction interval of 10s and a framerate of 25 fps that means we had to decode 250 frames for a single thumbnail image. Now, we're seeking to the position, decode 0-20 frames for accuracy (from keyframe to desired position), might be about 10 frames average. That means, with the new image extraction we need to decode only 4% of all video frames instead of 100%. => There isn't much work left to do for a hw decoder . Acceleration Potential Test's have shown that using hw acceleration with the new extraction method can achieve performance gains ranging from 1.0 (same speed) to 2.0 (double speed) only. But that usually at the cost of high consumption of system resources (CPU for JPG encoding) And that leads to the question: Why? There's no hurry and no need to get the extraction done a bit faster. Instead, this is meant to be a Background Operation that shouldn't interrupt your Emby Server's availability (and also not occupy your GPU resources) . Maintenance At the time of writing, Emby supports 8 different hardware acceleration variants each supporting a bunch of decoders all with different specifics. Making sure that all those are working with image extraction would be a huge effort for no practical benefit at all.
  3. Hello.. I'm running Emby server on a Raspberry PI and my media is stored on a NAS device. Is there a way to use another system (say Emby installed on a PC) for Chapter Image Extraction and then copy the resulting images to the PI Emby server for its use? Or will this not work since the metadata between the PI and PC installation will be different for the media? Thank you..
  4. Hi, and thanks for taking the time to read my feature request. What I would really like to see is a toggle option to enable/disable chapter image extraction during normal library scans. I spent some time reading through the forums on the subject, and saw that this was actually added as an ease-of-use feature back in July, but it has the opposite effect for me: I tend to add media to my system on a fairly regular basis (usually 1-2x a day, ranging between a handful to several dozen episodes), and tend to do so in preparation to watching some of it using MBT. The problem is that if Chapter Image Extraction is enabled, the Library Scan moves at a snail's pace, and taxes my puny little CPU enough that media playback is a stuttering mess for the duration, which can be up to 15-20 mins (vs. 20-30 secs with it disabled). However if it is disabled, I don't get any chapter images whatsoever. I have a task set to extract them daily starting at 2AM, but as it stands I have to remember to disable extraction every morning and re-enable it before going to sleep for it to it to work. The item description for the toggle even specifically recommends not running the extraction during peak usage, but as it stands there is no easy way to do so. If you could create a toggle for this function, you would really be taking a huge weight off of my shoulders - I'll be changing servers soon as I am presently using a laptop as a temp, and as such will have to run the extraction on all of my media again, and it would be really helpful to not have the system freeze up all day because I forgot to hit the switch in the morning (Last extraction took 12 days of running 6 hrs a day, hopefully it will go faster this time on a desktop CPU...). Thanks again for taking the time to listen to my petty problems:-)
  5. Chapter image extraction is a great feature and works on most of my MKV files. However, I have a bunch of MKVs in my Movie library on which chapter image extraction fails. There are a number of reasons why this might occur, including the case where some chapter markers are beyond the end (or right at the end) of a video file. I have already fixed those in my library. However, I still have other MKV files on which chapter image extraction fails and I haven’t been able to determine the root cause (~100 MKV files). I decided to look through the MediaBrowser server code to see what ffmpeg command is used to generate the images. After stitching together the various pieces of the command, I ran it from the command line in both Windows 7 and OS X Mavericks. The command I issued from the Windows command line is below: C:\Program Files\ffmpeg\bin>ffmpeg.exe -ss 260 -i “\\Media\Movies\Moon (2009)\Moon (2009).mkv" -threads 0 -vframes 1 -vf "thumbnail,crop=min(iw\,ih*dar):min(ih\,iw/dar):(iw-min(iw\,iw*sar))/2:(ih - min(ih\,ih/sar))/2,scale=600:600/dar" -f image2 "C:\Users\HTPC\Desktop\tmp.jpg" Oddly enough, the command works fine when I run it from the command line. However, it still fails when run behind the scenes by MediaBrowser3 on the same video file. Would it be possible for a future release of MediaBrowser3 server to log the exact command passed to ffmpeg and the output of ffmpeg for any file that fails chapter image extraction? Currently, the log file simply reports that chapter image extraction failed (first using the i-frame method and subsequently using the standard method). Logging ffmpegs output would really help in determining why image extraction seems to work when I run it manually, but not when MediaBrowser3 runs the command. Final notes: I am running the latest beta release of MB3. I am running the latest version of ffmpeg [build Version: git-785dc14 (2014-01-15)] MKV files were all generated using MakeMKV and run through mkvmerge. ALL MKV files that have chapter image extraction issues in MediaBrowser3 seem to have been processed with mkvmerge v5.0.0 or earlier. Of course, remember that I can successfully extract chapter images from these very same MKVs when running ffmpeg manually.
  • Create New...