Log in to your Gumlet account to give feedback

Feature Requests

HDR Support
Is your feature request related to a problem? Please describe. HDR (high dynamic range) is a significant leap forward in image quality on supporting monitors. One of the challenges is to create an image which shows as an ideal HDR where possible, but safely falls back to showing SDR (standard dynamic range) where not supported. A new "gain map" standard ( https://helpx.adobe.com/camera-raw/using/gain-map.html ) offers this and is already supported by Chrome, Apple devices (iOS 18), Android Devices (on Android jpg with gain maps are called Ultra HDR https://developer.android.com/media/platform/hdr-image-format ) When images are reprocessed (such as by Gumlet for posting on a Wordpress site via the media library), it is important that the gain map meta data and auxiliary image are retained. And if the image is resized/cropped, the secondary image should be altered in a consistent way. Describe the solution Metadata and color profile of the base image are retained Auxiliary image is retained, including its metadata Auxiliary image is rescaled as needed to match any alteration of the primary image. This should be the same percent reduction (as the gain map itself may be at 1/2 or 1/4 resolution of the original to save space in the file). Solution should at a minimum support JPG gain maps encoded with an SDR base image (as this offers full backwards compatibility). It should ideally support AVIF gain maps (as this offers much smaller files with AVIF). Gain map support for JXL may be helpful, though the format lacks critical support to be important in the foreseeable future. Describe alternatives you've considered Direct posting of the image without support for derivative assets like thumbnails or use of the media library. This could broadly affect a wide range of sites managing such images, so lack of support is very limiting and would require exporting multiple versions of images (if the platform even supports bypassing asset management which may reprocess the file). Additional context See https://gregbenzphotography.com/hdr/ for examples, monitor tests, and more info on HDR images. See https://helpx.adobe.com/camera-raw/using/gain-map.html for sample gain map images in JPG, AVIF, and JXL formats. Sample images to test with by Adobe: https://www.adobe.com/go/gainmap_sample_photos
1
·
Image Processing
·
planned
Firefox (macOS) — black highlights/image washed out when chrome media-chrome disappears
Type: Embed bug player Environment Firefox 155.0 MacOS Chrome and Safari: rendering correctly on the same embed Uploaded sources: 8-bit SDR only (no client-side HDR) Behavior On the Gumlet embed ( play.gumlet.io ), the image is correct as long as the cursor is on the player (chrome visible). When the cursor leaves the player and the controls disappear after autohide (~1 s), the image becomes lighter: black raised, like a semi-transparent veil. The problem affects all of our embed videos, not just one. Example page https://www.loisplagnard.com/film-ecole-comestible .html Embed example https://play.gumlet.io/embed/69ee6cb34779ed7c8b81154d?background=false&autoplay=true&loop=true&muted=true&playsinline=true&disable_player_controls=false&start_high_res=true&captions=true&cookie=false Isolation test (support suggestion) With disable_player_controls=true, the bug does not disappear: it becomes constant (image always washed). Firefox Render Config Active controls Correct on hover; lag after mouseleave disable_player_controls=true Continuously lagging Hypothesis The media-chrome player hides inactive chrome with opacity: 0 (userinactive) rather than removing it from the rendering. On Firefox, this seems to switch to <video>a different compositing path (hardware overlay), with black lift. Not correctable from the parent page (cross-origin iframe). Correction track Hide inactive chrome with visibility: hidden/display: none instead of opacity: 0 Or expose noautohide/option to avoid this path on Firefox Attachments [Capture 1: cursor on the player — correct rendering] [Capture 2: Cursor off the player - black raised] [Capture 3: disable_player_controls=true — washed constantly]
0
·
Image Processing