• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

P: Color artifacts in JPEG XL ProPhoto RGB

Community Beginner ,
Jun 13, 2024 Jun 13, 2024

Copy link to clipboard

Copied

JPEG XL files with the ProPhoro RGB color space exported from Lightroom contain color compression artifacts. They appear in quality 100% and lower. Other color spaces do not have this problem.

Krzysztof37569275vhjb_0-1718264330886.pngexpand image

 

Lightroom version 13.3.1

Windows 11 23H2 version 22631.3593

TOPICS
Windows

Views

1.9K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Jun 27, 2024 Jun 27, 2024

 

Update:  Recommendations:

  • If using lossy compression, prefer using JXL-native color spaces such as sRGB, Display P3, or Rec 2020.
  • If you must use non-native color spaces such as Adobe RGB or ProPhoto, consider using Lossless (quality 13).

Votes

Translate

Translate
LEGEND ,
Jun 13, 2024 Jun 13, 2024

Copy link to clipboard

Copied

I see similar artifacts when exporting to JXL with these options in LR 13.3.1 / Mac OS 14.5:

 

Prophoto, 100%, 16 bits/component

Adobe RGB, 100%, 16 bits/component

 

I don't see the artifacts with these options:

 

Display P3, 100%, 16 bits/component

Rec 2020, 100%, 16 bits/component

Prophoto, Lossless, 16 bits/component 

 

You can download the original DNG and exported JXLs from here -- the files are perspicuously named:

https://www.dropbox.com/s/93agakaa94zsns6/export-jxl-artifacts.2024-06-13.zip?dl=0

 

johnrellis_0-1718325484263.pngexpand image johnrellis_1-1718325556826.pngexpand image 

johnrellis_2-1718325620167.pngexpand image johnrellis_3-1718325822739.pngexpand image

 

 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jun 13, 2024 Jun 13, 2024

Copy link to clipboard

Copied

@Rikk Flohr: Photography@Rick Spaulding -, please consider moving to bugs. I've uploaded a sample file that exhibits the problem (see above).

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Jun 27, 2024 Jun 27, 2024

Copy link to clipboard

Copied

 

Update:  Recommendations:

  • If using lossy compression, prefer using JXL-native color spaces such as sRGB, Display P3, or Rec 2020.
  • If you must use non-native color spaces such as Adobe RGB or ProPhoto, consider using Lossless (quality 13).

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 19, 2025 Jan 19, 2025

Copy link to clipboard

Copied

I'm seeing artifacts I've not seen before when exporting in the JPEG XL lossy format. (90%) quality)

These a red blocks (I think 8x8 pixels size) around a strong blue colored bird. 
See areas indicated by yellow areas on the picture below.
I compared it to TIFF and JPEG (90%) of identical of identical size (pixels), both are looking fine.
Increasing the JPEG XL quality to 100% doesn't solve it. Going to Lossless does.

When I started using JPEG XL, I have evaluated it and saw superior quality compared to JPEG of similar file size. These artifacts are new to me.

I'm using LR 14.1.1, Windows 11 computer.
See attached picture at 300% for easy vieweing. Unfortunately the artifacts are visible at 100% too.

Is this normal for JPEG XL? Have I overlooked it in the past? Is the contents of my picture so specific and causing this? is it a bug ? Are a few of the questions I have.
Can share the DNG file if you like.




 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 19, 2025 Jan 19, 2025

Copy link to clipboard

Copied

Looks like a bug to me.  

 

As a test, try setting Preferences > Performance > Use Graphics Processor to Off. Do the artifacts occur?  If so, try updating your graphics driver by going directly to the manufacturer's web site:
https://helpx.adobe.com/lightroom-classic/kb/troubleshoot-gpu.html#solution-4

If that doesn't help, please copy/paste here the entire contents of the LR menu command Help > System Info -- that will let us see exactly which versions of hardware and software LR thinks you're running.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 19, 2025 Jan 19, 2025

Copy link to clipboard

Copied

Hi, 

With Graphics processor off, restart LR gives the same result : artificacs as reported above for the JPEG XL
My system is / was up to date with the latest graphics driver from Nvidia : 566.36 (Dec.2024)
LR system info:

Lightroom Classic version: 14.1.1 [ 202412150940-551fb044 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 11 - Home Premium Edition
Version: 11.0.26100
Application architecture: x64
System architecture: x64
Logical processor count: 12
Processor speed: 2.5GHz
SqLite Version: 3.36.0
CPU Utilisation: 2.0%
Power Source: Plugged In
Built-in memory: 32678.1 MB
Dedicated GPU memory used by Lightroom: 16.0MB / 5966.0MB (0%)
Real memory available to Lightroom: 32678.1 MB
Real memory used by Lightroom: 1865.7 MB (5.7%)
Virtual memory used by Lightroom: 2049.2 MB
GDI objects count: 996
USER objects count: 2545
Process handles count: 2484
Memory cache size: 0.0MB
Internal Camera Raw version: 17.1 [ 2098 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 269MB / 16339MB (1%)
Camera Raw real memory: 123MB / 32678MB (0%)
 
Cache1: 
NT- RAM:0.0MB, VRAM:0.0MB, Combined:0.0MB
 
Cache2: 
m:0.0MB, n:0.0MB
 
U-main: 87.0MB
 
System DPI setting: 144 DPI (high DPI mode)
Desktop composition enabled: Yes
Standard Preview Size: 3840 pixels
Displays: 1) 3840x2160
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No
 
Graphics Processor Info: 
DirectX: NVIDIA GeForce GTX 1660 Ti (32.0.15.6636)
Init State: GPU for Image Processing supported by default
User Preference: Auto
Enable HDR in Library: OFF
 
Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: C:\Users\ruudu\Pictures\Lightroom\LR2023\LR2023-v13-3.lrcat
Settings Folder: C:\Users\ruudu\AppData\Roaming\Adobe\Lightroom
 
Installed Plugins: 
1) AdobeStock
2) Epson Print Layout
3) Flickr
4) Helicon Focus Export
5) Topaz Photo AI
 
Config.lua flags: 
 
Adapter #1: Vendor : 10de
Device : 2191
Subsystem : 3ffc17aa
Revision : a1
Video Memory : 5966
Adapter #2: Vendor : 1414
Device : 8c
Subsystem : 0
Revision : 0
Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: System Default - Luidsprekers (Realtek(R) Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: LR5x26
Direct2DEnabled: false
GL_ACCUM_ALPHA_BITS: 16
GL_ACCUM_BLUE_BITS: 16
GL_ACCUM_GREEN_BITS: 16
GL_ACCUM_RED_BITS: 16
GL_ALPHA_BITS: 0
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_SIZE: 32768
GL_MAX_TEXTURE_UNITS: 4
GL_MAX_VIEWPORT_DIMS: 32768,32768
GL_RED_BITS: 8
GL_RENDERER: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 4.60 NVIDIA
GL_STENCIL_BITS: 8
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.6.0 NVIDIA 566.36
GPUDeviceEnabled: false
OGLEnabled: true
GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_AMD_vertex_shader_viewport_index GL_AMD_vertex_shader_layer GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_fragment_shader_interlock GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_polygon_offset_clamp GL_ARB_post_depth_coverage GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_locations GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shader_viewport_layer_array GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_sparse_texture2 GL_ARB_sparse_texture_clamp GL_ARB_spirv_extensions GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_filter_anisotropic GL_ARB_texture_filter_minmax GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_multiview_texture_multisample GL_EXT_multiview_timer_query GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_post_depth_coverage GL_EXT_provoking_vertex GL_EXT_raster_multisample GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_formatted GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_sparse_texture2 GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_filter_minmax GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shadow_lod GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_R8 GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_EXT_memory_object GL_EXT_memory_object_win32 GL_NV_memory_object_sparse GL_EXT_win32_keyed_mutex GL_KHR_parallel_shader_compile GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_EXT_semaphore GL_EXT_semaphore_win32 GL_NV_timeline_semaphore GL_KHR_shader_subgroup GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_equation_advanced_coherent GL_NVX_blend_equation_advanced_multi_draw_buffers GL_NV_blend_minmax_factor GL_NV_blend_square GL_NV_clip_space_w_scaling GL_NV_command_list GL_NV_compute_program5 GL_NV_compute_shader_derivatives GL_NV_conditional_render GL_NV_conservative_raster GL_NV_conservative_raster_dilate GL_NV_conservative_raster_pre_snap GL_NV_conservative_raster_pre_snap_triangles GL_NV_conservative_raster_underestimation GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_feature_query GL_NV_fence GL_NV_fill_rectangle GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_coverage_to_color GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_fragment_shader_barycentric GL_NV_fragment_shader_interlock GL_NV_framebuffer_mixed_samples GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_geometry_shader_passthrough GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_program_multiview GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_memory_attachment GL_NV_mesh_shader GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_path_rendering_shared_edge GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_query_resource GL_NV_query_resource_tag GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_representative_fragment_test GL_NV_sample_locations GL_NV_sample_mask_override_coverage GL_NV_scissor_exclusive GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_atomic_float64 GL_NV_shader_atomic_fp16_vector GL_NV_shader_atomic_int64 GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_shader_subgroup_partitioned GL_NV_shader_texture_footprint GL_NV_shading_rate_image GL_NV_stereo_view_rendering GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_rectangle_compressed GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_uniform_buffer_std430_layout GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NV_viewport_array2 GL_NV_viewport_swizzle GL_NVX_conditional_render GL_NVX_linked_gpu_multicast GL_NV_gpu_multicast GL_NVX_gpu_multicast2 GL_NVX_progress_fence GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_OVR_multiview GL_OVR_multiview2 GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 20, 2025 Jan 20, 2025

Copy link to clipboard

Copied

I forgot that there is an existing bug report about this from last June, acknowledged by Adobe, when exporting to JPEG XL with Prophoto or Adobe RGB color spaces:

https://community.adobe.com/t5/lightroom-classic-bugs/p-color-artifacts-in-jpeg-xl-prophoto-rgb/idi-...

 

A workaround is to use Display P3 or Rec 20202, or switch to AVIF.

 

LR also has bugs exporting JPEG XLs at sizes that are way too large:

https://community.adobe.com/t5/camera-raw-bugs/p-certain-raw-files-export-unusually-large-with-jpeg-...

 

Overall, I don't think LR export of JPEG XL is ready for prime time -- best to stay away from it until/if Adobe decides to fix the bugs.

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 20, 2025 Jan 20, 2025

Copy link to clipboard

Copied

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 20, 2025 Jan 20, 2025

Copy link to clipboard

Copied

@Rikk Flohr: Photography, it looks like this thread was just moved from Bugs to Discussions (after I posted my last reply above).  Are the artifacts now considered as-designed rather than as a bug?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jan 21, 2025 Jan 21, 2025

Copy link to clipboard

Copied

@johnrellis 

It is not as designed but rather a design limitation with the JPEG-XL.  Comments from the engineers

"This is a quality limitation of JPEG XL when used with non-native color spaces in lossy mode." 

I updated Rick Spaulding's post to reflect the correct workflow. 

Rikk Flohr: Adobe Photography Org

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 21, 2025 Jan 21, 2025

Copy link to clipboard

Copied

@Rikk Flohr: Photography after reading your commens from the engineers, the idea from @reproo2773183 might not be a bad idea: 

would it be worth limiting the user's choices of color space when exporting from Lightroom. eg remove or grey-out AdobeRGB and ProPhoto, when selecting JXL lossy? 

Ruud

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 21, 2025 Jan 21, 2025

Copy link to clipboard

Copied

Agreed that if there are going to be problems with using deprecated color spaces with JPEG XL export, LR should give some kind of warning.  Prophoto in particular is a popular wide color space (not least because its primaries are the same as LR uses internally), so if that's not fully supported, LR should at a minimum warn the user.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 22, 2025 Jan 22, 2025

Copy link to clipboard

Copied

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

 

I wrote, "Prophoto in particular is a popular wide color space (not least because its primaries are the same as LR uses internally)".   LR itself tells users that "16-bit ProPhoto RGB is the recommended choice for best preserving color details from Lightroom":

 

johnrellis_0-1737616056648.pngexpand image

 

So little wonder that people will try to use Prophoto with JPEG XL export!

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 23, 2025 Jan 23, 2025

Copy link to clipboard

Copied

This is exactly why I was using ProPhoto colour space.


Because most of my work is with converted negatives, I like to have a positive copy saved for editing work. TIFF is way too large and traditional JPEGs lose too much information for my liking. I was hoping JXL would be the answer for a space convenient 16bit file. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 24, 2025 Jan 24, 2025

Copy link to clipboard

Copied

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

 

@Rikk Flohr: Photography: "It is not as designed but rather a design limitation with the JPEG-XL.  Comments from the engineers: "This is a quality limitation of JPEG XL when used with non-native color spaces in lossy mode.""

 

@Rikk Flohr: Photography, the "cjxl" program from the libjxl JPEG XL reference implementation doesn't produce these artifacts with ProPhoto RGB and lossy mode. So this points to a bug in LR's implementation rather than a limitation of JPEG XL. It would be interesting to get the engineers' perspective on why "cjxl" doesn't generate the artifacts.

 

To demonstrate with LR 14.1.1 / Mac OS 15.2:

 

1. I used LR to export a denoised DNG to the file x.png.

 

2. I exported x.png to x.jxl, with the options Image Format: JPEG XL, Quality: 100, Color Space: ProPhoto RGB, Bit Depth: 16 bits/component.

 

3. I used "cjxl" to generate x-cjxl.png  from x.png, with the option --quality=99:

 

cjxl x.png x-cjxl.jxl --quality=99

 

 

The screenshot below shows x.jxl, x.png, and x-cjxl.jxl.   There is no visual difference between x.png and x-cjxl.jxl, though there are quite noticeable artifacts in x.jxl:

Screenshot 2025-01-24 at 1.17.39 PM.jpgexpand image

 

You can download a catalog with all the images from here:

https://www.dropbox.com/s/q2kssve7f16gpt4/jxl-artifacts.2025-01-24.zip?dl=0 

 

The exact "cjxl" command:

 

$ cjxl x.png x-cjxl.jxl --quality=99
JPEG XL encoder v0.11.0 [NEON]
libpng warning: iCCP: profile 'ProPhoto RGB': 0h: PCS illuminant is not D50
Encoding [VarDCT, d0.190, effort: 7]
Compressed to 30494.7 kB including container (5.369 bpp).
5504 x 8256,  14.558 MP/s [14.56, 14.56], , 1 reps, 12 threads.

 

 

 

 

The "jxlinfo" command shows that the image is lossy and in ProPhoto:

 

 

 

$ jxlinfo x-cjxl.jxl 
JPEG XL file format container (ISO/IEC 18181-2)
JPEG XL image, 5504x8256, lossy, 16-bit RGB
Color space: RGB, Custom, white_point(x=0.345705,y=0.358540), Custom primaries: red(x=0.734699,y=0.265302),  green(x=0.159600,y=0.840399),  blue(x=0.036597,y=0.000106)gamma(0.555315) transfer function, rendering intent: Perceptual
Brotli-compressed xml  metadata: 3381 compressed bytes

 

 

 

 

The warning "PCS illuminant is not D50" arises because "cjxl" thinks the white point of x.png's colorspace has x=0.345705, whereas ProPhoto's D50 white point has x=0.345704 -- probably a rounding error somewhere.


But otherwise, "jxlinfo" shows the colorspace of x-cjxl.jxl is identical to Prophoto RGB.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 21, 2025 Jan 21, 2025

Copy link to clipboard

Copied

Hi John,
Agree, the color artifacts on my small blue bird is similar to June bug report.
When I assign the Display P3 color profile, the artifacts are gone, so confirmed.

Sound advice to stay away from JPEG XL for critical work or archiving my finished edits, but I do believe that the JPEG XL compression is also the standard format for Lightroom merged panorama and HDR files? 
No problems (expected)?
Ruud

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 21, 2025 Jan 21, 2025

Copy link to clipboard

Copied

@reproo2773183: "I do believe that the JPEG XL compression is also the standard format for Lightroom merged panorama and HDR files? No problems (expected)?"

 

That's a good question. There certainly haven't been any reports here about artifacts in Photo Merge DNGs since JPEG XL was introduced 1.5 years ago.  But I don't know much about JPEG XL (the ISO foolishly charges hundreds of dollars for the privilege to read the specs).  But the Photo Merge DNGs and exported JPEG XLs are much different beasts.

 

The DNGs produced by Photo Merge represent the merged photo as "linear raw", with the Bayer color-filter array pixels demosaiced into three separate RGB channels. But there's no change in the color space -- the values of the pixels are what comes from the camera's sensor (demosaiced).  Those three channels are then compressed with lossy JPEG XL compression.

 

But an exported JPEG XL contains pixels rendered by the Camera Raw engine into the selected color space and then compressed.  I don't know what it is about the JPEG XL standard that would cause these artifacts for some color spaces.

 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Jan 22, 2025 Jan 22, 2025

Copy link to clipboard

Copied

@johnrellis Thanks for clarifying, I learned something new! 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Jan 22, 2025 Jan 22, 2025

Copy link to clipboard

Copied

quoteThat's a good question. There certainly haven't been any reports here about artifacts in Photo Merge DNGs since JPEG XL was introduced 1.5 years ago.  But I don't know much about JPEG XL (the ISO foolishly charges hundreds of dollars for the privilege to read the specs).  But the Photo Merge DNGs and exported JPEG XLs are much different beasts.

 

The DNGs produced by Photo Merge represent the merged photo as "linear raw", with the Bayer color-filter array pixels demosaiced into three separate RGB channels. But there's no change in the color space -- the values of the pixels are what comes from the camera's sensor (demosaiced).  Those three channels are then compressed with lossy JPEG XL compression.

 

But an exported JPEG XL contains pixels rendered by the Camera Raw engine into the selected color space and then compressed.  I don't know what it is about the JPEG XL standard that would cause these artifacts for some color spaces.

By johnrellis

 

My Thoughts: I think "linear raw" is the sensor values, possibly "Linear Light" or "intensity", there are 3 values but none of this is RGB.

A "camera profile" (dcm) converts the Linear Light values to RGB (Display Code Values) eventually but I think there has to be an interim step or two involving CIExyz.

RGB values are meaningless without a Colour Profile (icc). Lightroom is always dealing with its Working Space and your monitor's profile. When it comes to Export; Lightroom does not need to consider the Monitor Profile?

 

I also don't know where the Adobe engineers are hitting this limitation with  "non native profiles". Perhaps its and HDR thing?

Its not likely to become any clearer since there are too many unknowns.

 

I can't remember which RGB Profiles are available to Affinity Photo when it Exports to JPEG XL but they are much smaller files and I've not seen any of these artifacts.

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 22, 2025 Jan 22, 2025

Copy link to clipboard

Copied

@reproo2773183: "I think "linear raw" is the sensor values, possibly "Linear Light" or "intensity", there are 3 values but none of this is RGB."

 

The term "RGB" has different meanings in different contexts, but it most definitely is used in the DNG spec to describe raw sensor values.

 

In the DNG spec, un-demosaiced sensor data from the camera's color filter arrays are stored in the DNG. This sensor data consists of red, green, and blue samples from the CFA, sometimes abbreviated as RGB. The spec variously calls these "native camera RGB values", "RGB camera values",  "reference camera native space values".  The values are in what the spec calls "camera color space", "camera native color space", "camera space", "same color space as the raw image data".

 

It's also common outside of the DNG spec to refer to color filter arrays samples as RGB:

https://en.wikipedia.org/wiki/Bayer_filter 

 

DNGs store the output from Denoise as de-moasaiced raw data to which the denoise algorithm has been applied, using an alternate raw representation the spec calls LinearRaw.  LinearRaw stores three "color planes" (channels) of red, green, and blue samples, in the same color space as the CFA representation ("camera color space").

 

It is the job of DNG camera profiles to map RGB values in the camera color space to the ICC color connection space and then to particular color profiles such as Prophoto RGB or Adobe RGB.

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Jan 24, 2025 Jan 24, 2025

Copy link to clipboard

Copied

@johnrellis 

Thank you for your explanation and links.

When you say "In the DNG spec, un-demosaiced sensor data from the camera's color filter arrays are stored in the DNG" this is optional or always?

 IF you have (DNG) output from DeNoise or Pano Merge which is de-mosaiced but still "camera color space" LinearRaw would you need the un-mosaiced? 

from reading the DNG spec I think I get that its the de-mosaiced data that can be JPEG XL, I'm also thinking that this is still "camera color space" LinearRaw; so still has full flexibilty to be manipulated/converted by camera profiles the ICC color connection space.

 

So IF (Big IF) I have the above right, then When you Export Lightroom tries to go back to the de-mosaiced linear raw JPEG XL and convert that to JPEG XL (but unsupported ICC) its going wrong in a manner that doesn't go wrong when going through Lightroom's internal ProPhoto (D50) to screen.

 

I'm also wondering if for Adobe JPEG XL is limited to Linear Raw, which would explain why it opens in ACR rather than Photoshop?

 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 24, 2025 Jan 24, 2025

Copy link to clipboard

Copied

@reproo2773183: "When you say "In the DNG spec, un-demosaiced sensor data from the camera's color filter arrays are stored in the DNG", this is optional or always?"

 

Raws coming straight from cameras always contain color-filter array samples (un-demosaiced).

 

DNGs produced by LR's Photo Merge and Enhance commands store the merged/enhanced image as linear raw (demosaiced). But they also store the original, unmodified CFA samples in a separate section of the file.

 

"If you have (DNG) output from DeNoise or Pano Merge which is de-mosaiced but still "camera color space" LinearRaw would you need the un- [de]mosaiced?"

 

As mentioned above, the DNGs produced by Photo Merge and Enhance also contain the original CFA samples (un-demosaiced), but I don't know of any parts of LR or Camera Raw that actually uses it. Adobe said a couple years ago they included the original CFA data in anticipation of possible future enhancements, though they haven't provided more details.  If you retain the original from-the-camera raw, you'll still have access to the original, unmodified image.

 

"from reading the DNG spec I think I get that its the de-mosaiced data that can be JPEG XL, I'm also thinking that this is still "camera color space" LinearRaw; so still has full flexibilty to be manipulated/converted by camera profiles the ICC color connection space."

 

That's correct. The linear raw (demosaiced) pixels are still in camera color space.  They are usually compressed using the JPEG XL compression algorithm, though they could also be compressed with JPEG compression or uncompressed, as allowed by earlier versions of the DNG spec.  But only the compression algorithms of JPEG XL and JPEG are involved with linear raw data -- no other aspect of the JPEG XL or JPEG file formats are used with linear raw.

 

"When you Export Lightroom tries to go back to the de-mosaiced linear raw JPEG XL and convert that to JPEG XL (but unsupported ICC) its going wrong in a manner that doesn't go wrong when going through Lightroom's internal ProPhoto (D50) to screen."

 

The different uses of the term "JPEG XL" are causing confusion here.

 

The linear raw DNGs produced by Photo Merge and Enhance use JPEG XL compression to store the linear raw pixels (in camera color space), but they are full raws.

 

When you export any file to JPEG XL file format, the output file is in full JPEG XL format ("JXL") , and the output pixels are in the specific color space (e.g. sRGB or Prophoto), not in camera color space.  The problem with artifacts in the output JXL file is, according to Adobe, caused by the use of certain color spaces (Prophoto and Adobe RGB), which are called "non-native" for as-yet unexplained reasons. The implication is that JPEG XL format doesn't really support those color spaces somehow. It's hard for me to learn more, since the ISO charges hundreds of dollars for the privilege of reading their specs.

 

"I'm also wondering if for Adobe JPEG XL is limited to Linear Raw, which would explain why it opens in ACR rather than Photoshop?"

 

When you open a DNG stored in linear-raw format in Photoshop, it opens in CR because the DNG is a full-fledged raw file.

 

But when you open a JXL exported from LR in Photoshop, it too opens in CR. I think that's a small Photoshop bug. Opening JXLs in PS should behave the same as opening JPGs.

 

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jan 24, 2025 Jan 24, 2025

Copy link to clipboard

Copied

I wrote, "But when you open a JXL exported from LR in Photoshop, it too opens in CR. I think that's a small Photoshop bug. Opening JXLs in PS should behave the same as opening JPGs."

 

After a little poking around, I think this is "as-designed" behavior.  Photoshop proper can't read or write JXL files, but Camera Raw can read JXL files.  So Adobe allows Photoshop to open JXL files by having them open first in Camera Raw, from which you can open the image in full Photoshop.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Feb 03, 2025 Feb 03, 2025

Copy link to clipboard

Copied

"The implication is that JPEG XL format doesn't really support those color spaces somehow."

Its only when you add in lossy compression that you get the artifacts.

I'm now thinking its during the conversion from the native space to the non-native space some of the maths/rounding doesn't allow for a number bigger than 1  or smaller than 0 and you get a blown or clipping artifact in one or more of the channels.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines