For the name field enter screenshot full (or whatever you wish to name it) and in the command section type gnome-screenshot and click on the set shortcut and press the key combination you want to take screenshot of the whole screen. If you want to enable custom shortcuts, then erase the screenshot typed earlier and scroll down to bottom and click the plus sign at the very bottom. Start typing screenshot and shortcuts related to screenshots will appear in front of you. Press super key ( windows button on PC or command button on mac), and type shortcut and select keyboard shortcuts. The default button for screenshot can be checked in settings. With the "screenshot" command on the same mpv instance as the player.Macbook pro does not have a print screen button due to touch bar, which is the default button in case of PC. Int mpv_command_async(mpv_handle` *ctx, uint64_t reply_userdata, const char **args) The software renderer may lack some capabilities, such as HDR rendering.Īll I could find was that IINA just calls In this case, conversion will run in a separate thread and will probably not interrupt playback. If set to yes, the software scaler is used to convert the video to RGB (or whatever the target screenshot requires). (Unless the window mode is used with the screenshot command.) But since the renderer needs to be reinitialized, this can be slow and interrupt playback. The advantage is that this will (probably) always show up as in the video window, because the same code is used for rendering. If set to no, the screenshot will be rendered by the current VO if possible (only vo_gpu currently). This is what the documentation says (emphasis mine): I couldn't find this explicitly in the code but I think libmpv inside IINA is using the software rendering for taking screenshots, similarly to the -screenshot-sw=yes option which is why it looks different/wrong compared to the player window. Note that some browsers (Firefox IIRC) completely ignore embedded ICC profiles in PNGs and just assume a generic RGB profile, so these could look widely different. But I made sure to keep the colors and color profiles intact. I had to scale down the FCPX PNG from 16bit to 8bit and I used -screenshot-high-bit-depth=no with the mpv screenshots because the files would have been larger than GitHub's 10MB limit. I created all of these images on the 16" M1 MacBook Pro on Monterey 12.6.2 using IINA 1.3.1 and mpv 0.35.0 via Homebrew. On my screen this looks basically identical to the macOS screenshot of IINA except that the cloud isn't clipping. Out of these images, I guess this one is probably the most accurate representation of the Dolby Vision source. ✅ macOS screenshot of QuickTime Player (Display P3)Īnd finally here is Final Cut Pro X exporting a PNG out of the Rec. In the IINA and QuickTime screenshots, the cloud in the upper left is slightly clipping (which it isn't in the player's window). Here are screenshots of the player windows taken with macOS screenshot tool which does a way better job. ❌ IINA "Take a Screenshot" (no ICC profile) This looks like it does in the player window (which is a bit darker than IINA).īut if software rendering is enabled with -screenshot-sw=yes, we get the same overexposed result as with the -o and IINA screenshots: ❌ mpv -screenshot-sw=yes "Save Screenshot" (no ICC profile) (note that the -screenshot* and -vo options only have an effect with this latter method, but not with -o) ✅ mpv "Save Screenshot" (sRGB) However, mpv will create correct screenshots if you just start the player with default arguments and use the "Save Screenshot" action from the "File" menu. Mpv is true that screenshots produced with the encoding option -o are equally as overexposed as IINA's. The resulting screenshot is incredibly washed out, as you can see by the first example above. Preferably, the photos would be saved using the same colorspace as the video was in (In this case, Rec. Screenshots taken with IINA for HDR videos are consistent to the HDR colors. It clearly isn't HDR, but it has colors that are more consistent to those of the original video.Īs a second attempt, I downloaded the youtube video manually using yt-dlp with the default settings (Just yt-dlp "") and the resulting screenshot was even more washed out (But a lower filesize, for whatever reason). This is in contrast to this screenshot below, taken via MacOS's default screen capture tool. It is incredibly overexposed, and the colors don't match. As an example, I took a screenshot of this video using the Open in IINA feature, and here is the result (downscaled to fit GitHub's requirements, the colors didn't change): HDR video displays fine on my 2020 MacBook Pro M1, but when I take a screenshot, it shows up horribly overexposed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |