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

New AI powered Denoise not functioning

Community Beginner ,
Apr 28, 2023 Apr 28, 2023

Copy link to clipboard

Copied

Which GPU benchmark is for the new AI Denoise in development module necessary?????

With my GPU NVIDIA GeForce MX 250 (Average Benchmark is 2462) it is not functioning!!!!

 

Thinkpad notebook:
Prozessor: Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz 1.99 GHz
Installierter RAM: 40,0 GB
Grafikkarte: NVIDIA GeForce MX 250

TOPICS
Windows

Views

3.3K

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
Community Expert ,
Apr 28, 2023 Apr 28, 2023

Copy link to clipboard

Copied

I think it depends more on the amount of memory that your GPU has. I believe that a minimum of 2GB is required, though Adobe recommends at least 8GB for Denoise. The MX 250 apparently supports up to a maximum of 4GB, so how much does your GPU have?

 

Also, Denoise only works on mosaic raw files from Bayer and X-trans sensors.

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
Community Beginner ,
Apr 28, 2023 Apr 28, 2023

Copy link to clipboard

Copied

I do not know where to find the memory of the GPU???
I am using Nikon D850 for underwater images, I think it is Bayer sensor!
<removed for Privacy>

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 ,
Apr 28, 2023 Apr 28, 2023

Copy link to clipboard

Copied

Please do the LR menu command Help > System Info and copy/paste the entire contents here so we can 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
Community Beginner ,
Apr 28, 2023 Apr 28, 2023

Copy link to clipboard

Copied

Lightroom Classic-Version: 12.3 [ 202304101834-a085245c ]
Lizenz: Creative Cloud
Spracheinstellung: de
Betriebssystem: Windows 10 - Business Edition
Version: 10.0.19045
Anwendungsarchitektur: x64
Systemarchitektur: x64
Anzahl logischer Prozessoren: 8
Prozessorgeschwindigkeit: 1,9GHz
SQLite-Version: 3.36.0
CPU-Auslastung: 14,0%
Integrierter Speicher: 40707,7 MB
Dedizierter GPU-Speicher, der von Lightroom verwendet wird: 310,0MB / 1982,4MB (15%)
Für Lightroom verfügbarer phys. Speicher: 40707,7 MB
Von Lightroom verwendeter phys. Speicher: 1207,6 MB (2,9%)
Von Lightroom verwendeter virtueller Speicher: 1641,4 MB
Anzahl GDI-Objekte: 766
Anzahl BENUTZER-Objekte: 2853
Anzahl Prozess-Handles: 2541
Cache-Speichergröße: 99,1MB
Interne Camera Raw-Version: 15.3 [ 1451 ]
Maximale Anzahl Threads, die Camera Raw verwendet: 5
Camera Raw SIMD-Optimierung: SSE2,AVX,AVX2
Virtueller Speicher in Camera Raw: 88MB / 20353MB (0%)
Physischer Speicher in Camera Raw: 89MB / 40707MB (0%)
DPI-Einstellung des Systems: 96 DPI
Desktop-Komposition aktiviert: Ja
Standardvorschaugröße: 1920 Pixel
Monitore/Anzeigegeräte: 1) 1920x1200
Eingabetypen: Multitouch: Nein, integrierte Toucheingabe: Nein, integrierter Stift: Nein, externe Toucheingabe: Nein, externer Stift: Nein, Tastatur: Nein

Informationen zum Grafikprozessor:
DirectX: NVIDIA GeForce MX250 (31.0.15.3141)
Anfangsstatus: GPU wird standardmäßig für die Bildverarbeitung unterstützt
Benutzerpräferenz: Automatisch

Anwendungsordner: C:\Program Files\Adobe\Adobe Lightroom Classic
Bibliothekspfad: C:\Daten\Bilder\Lightroom\Lightroom Catalog-2-2-2-2-2-2-2-v12.lrcat
Einstellungen-Ordner: C:\Users\Thomas\AppData\Roaming\Adobe\Lightroom

Installierte Zusatzmodule:
1) AdobeStock
2) DxO PureRAW 3
3) DxO PureRAW 3 Importer
4) Flickr
5) LogiOptions
6) Nikon Tether-Zusatzmodul

Config.lua-Flags: None

Adapter Nr. 1: Anbieter : 10de
Gerät : 1d13
Subsystem : 227817aa
Version : a1
Grafikspeicher : 1982
Adapter Nr. 2: Anbieter : 8086
Gerät : 3ea0
Subsystem : 227817aa
Version : 0
Grafikspeicher : 80
Adapter Nr. 3: Anbieter : 8086
Gerät : 3ea0
Subsystem : 227817aa
Version : 0
Grafikspeicher : 80
Adapter Nr. 4: Anbieter : 1414
Gerät : 8c
Subsystem : 0
Version : 0
Grafikspeicher : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: $$$/dvaaudiodevice/SystemDefaultAndEffectiveDeviceName=System Default - Lautsprecher (Realtek(R) Audio)#{comment}DVAAU-4201250: Open the audio hardware preferences page.
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: LR5x19
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 MX250/PCIe/SSE2
GL_SHADING_LANGUAGE_VERSION: 4.60 NVIDIA
GL_STENCIL_BITS: 8
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.6.0 NVIDIA 531.41
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_conditional_render GL_NV_conservative_raster GL_NV_conservative_raster_dilate GL_NV_conservative_raster_pre_snap_triangles 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_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_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_memory_attachment 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_sample_locations GL_NV_sample_mask_override_coverage 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_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

<removed for Privacy>

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 ,
Apr 28, 2023 Apr 28, 2023

Copy link to clipboard

Copied

What do you mean by "not functioning"? Is it too slow? Is it not doing the proper de-noise? Is the Enhance button greyed out? Something else? What do you mean? Please explain.

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
Community Beginner ,
Apr 28, 2023 Apr 28, 2023

Copy link to clipboard

Copied

It try to render but when you press denoise, it is just inserting an error message on the image!!!
I also tried the new AI Denoise from DxO pure raw and there it is only possible with the CPU and not with GPU!!!
<removed for privacy>

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 ,
Apr 28, 2023 Apr 28, 2023

Copy link to clipboard

Copied

Why is because of the GPU's processing power (at least modern GPUs). Adobe engineer Eric Chan suggests 8GB of GPU RAM. 

DxO is moot; no one here knows how it's coded, if it uses GPU or not. If you prefer the results and speed, use it. 

As asked: not functioning or too slow? One is easy to fix; upgrade your GPU. Mine processes a 24MP raw in 12 seconds, start to finish. Part of that processing, which isn't using GPU is creating the new DNG. 

 

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"

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
Community Beginner ,
Apr 28, 2023 Apr 28, 2023

Copy link to clipboard

Copied

Can you tell me which GPU you are using, which need just 12 seconds for processing a 24MP raw image?


<removed for Privacy>

 

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 ,
Apr 28, 2023 Apr 28, 2023

Copy link to clipboard

Copied

MBP Pro 16" 2022 32-Core GPU | 16-Core Neural Engine/64GB

Canon R6 Mark II raws. 

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"

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 ,
Apr 28, 2023 Apr 28, 2023

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 ,
Apr 29, 2023 Apr 29, 2023

Copy link to clipboard

Copied

[removed the personal info block]

Are these infomercials really necessary with every post you make?

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
Community Expert ,
Apr 29, 2023 Apr 29, 2023

Copy link to clipboard

Copied

No, and a moderator (I'm not) should remove it ASAP. Perhaps he thinks this is e-mail support and not an open website? In any case, it's an open invitation to bots and hacking.

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 ,
Apr 29, 2023 Apr 29, 2023

Copy link to clipboard

Copied

The forum software usually removes signatures from email replies but sometimes fails to do so.

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
Community Beginner ,
Apr 29, 2023 Apr 29, 2023

Copy link to clipboard

Copied

Sorry, for sending always my data with the emails!
There is really nothing behind and I did not try to use the community to send infomercials!!!
I really just forget to put it away!!!!!
The reason is that I use my email account private and for business and I was not careful enough regarding this subject.
So, sorry again, I just put it away!!!!

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
Enthusiast ,
Apr 29, 2023 Apr 29, 2023

Copy link to clipboard

Copied

I wonder if it's just slow. The following article talks about how slow denoise can be compared to it's competition. In the article the author talks about taking 14 minutes in LrC Denoise on an older configuration compare to almost immediate by others. https://fstoppers.com/reviews/adobe-lightroom-classics-new-ai-denoise-scratch-review-631061

 

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
Community Beginner ,
Apr 29, 2023 Apr 29, 2023

Copy link to clipboard

Copied

I would like to know if also the interaction of GPU with a special hardware system configuration is necessary for speeding up the AI denoise!
It would be great to get information which combination of hardware is important (or the best) to optimize the speed of AI denoise?

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
Community Expert ,
Apr 29, 2023 Apr 29, 2023

Copy link to clipboard

Copied

Denoise runs entirely in the GPU, and depends entirely on the GPU performance. It also relies heavily on newer GPU technologies that came on the market in the last two or three years. On newer GPUs it generally runs well, provided the GPU meets some basic performance standards.

 

To get Denoise to run at the "advertised" speed, like 12-15 seconds on a 24MP file as mentioned, you would need something like an RTX 3050 or 3060 or above - not super expensive high-end, but fairly decent. To get an idea of where that is in terms of performance, check here: https://www.videocardbenchmark.net/directCompute.html 

 

How the MX250 measures up in this I have no idea, but I see it was released in 2019, which probably puts it on the "old" side that doesn't take full advantage of new GPU technologies.

 

In short - it'll work, but it may be slow.

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
Community Beginner ,
Apr 29, 2023 Apr 29, 2023

Copy link to clipboard

Copied

I just tried to load an image (24MP) in AI Denoise

It was permanently loading showed processing time 59 minutes.

It doesnt finish with loading after more than I hour!!!!!!

Then I activated the enhance button and it shows unrecognized failure (1)

My old MX250 had a benchmark of 2400 and lightroom says it should be at least 2000.

What I mean it doesnt work at all, it is not only slow!!!!!

Therefore I wonder if there is also something else than the GPU.

But maybe it is only the memory of the GPU which counts?

The only suspect thing is that the AI denoise doesnt work at all and all other development tools are working also the AI super resolution and new masking before the new version AI denoise were coming!!!!!

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
Community Expert ,
Apr 29, 2023 Apr 29, 2023

Copy link to clipboard

Copied

Sorry, that's the wrong number. The MX250 scores about 1000 ops/sec in the benchmark Adobe refer to in the link above:

 

MX250_1.png

 

But I'm not even sure that number is relevant anymore. That's the recommendation they've given out for Photoshop for a while. Denoise is brand new, apparently something different and probably pushing things even further. The RTX 3060, which I know works well, scores over 9000 ops/sec by the same criteria.

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
Community Beginner ,
Apr 30, 2023 Apr 30, 2023

Copy link to clipboard

Copied

I decided  now to make a bigger investment in a new Thinkpad laptop particularly to be ready for more AI coming in lightroom in the future!

I am thinking of the new ThinkPad P1 Gen 5, with Intel® Core™ i9-12900H vPro, with 64 GB DDR5 4800 MHz (2 x 32 GB SODIMM),  with NVIDIA® GeForce RTX™ 3080 Ti 16 GB GDDR6.

That configuration is also available with an 4 Gb internal hard drive (4 TB SSD, M.2 2280, PCIe 4.0, TLC, OPAL 2.0).

Hitherto I have all my images (over 30 000) on an external hard drive and the catalog on the internal hard drive.

At the moment with my old system configuration all my  images over the last 20 years are about 1 terabyte (images extern, catalog intern, processing is with new masking quite slow and with AI denoise not working). With 4Tb intern there would be much room for future images .My question is now, is there a significant speed advantage regarding development of images when I have all the images and catalog on the internal hard drive ????

 

 

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
Community Expert ,
Apr 30, 2023 Apr 30, 2023

Copy link to clipboard

Copied

Those specs sound very good, and on the face of it, that should work very well..

 

Now, I'm always a little wary about laptops, mainly because everything comes as an off-the-shelf hard package, and you have very little room for customization or later upgrades to the system. When something stops working, you have to ditch it and get a new one. I'm not happy with that.

 

In addition, laptop vendors tend to go to great lengths to put their brand on the machine, often filling it up with all kinds of OS modifications and additional software and various utilities. Most of this just gets in the way.

 

Specifically, there is one thing that often causes problems with laptops: dual GPUs. That sounds like a good idea, but in reality it only works as advertised with simple applications that send data one way downstream. Photoshop/ACR/Lightroom are different. They use the GPU for actual data processing, and the result returned to the application for further processing. Two GPUs in the system mess that up. You can't send data to one GPU and get it back from the other.

 

So with a laptop, you often need to disable the integrated GPU so that the dedicated GPU can do its job.

 

If you look around the forum, you'll find that easily 90% of all problems people have, are on laptops. Just something to keep in mind.

 

Now, I'm not saying a laptop can't work splendidly. But a little caution is required. Don't let the marketing big words impress you. Get one that is as clean as possible. Good specs, but clean.

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
Community Beginner ,
May 07, 2023 May 07, 2023

Copy link to clipboard

Copied

I decided to invest in a stationary new workstation for LC!

Regarding the GPU I found following statement in the community!

"Lightroom Classic uses about 5.5GB memory through most of AI Denoise processing, but that more than doubles to 12–13GB near the end of AI Denoise"

From whom is that statement????

Is anyone else who made such tests with AI-Denoise????

I am wondering to buy the Geforce RTX 4070 with 12 Gb memory or the RTX 4080 with 16Gb, which is of course more expensive!!!!

.

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 ,
May 07, 2023 May 07, 2023

Copy link to clipboard

Copied

LATEST

https://blog.adobe.com/en/publish/2023/04/18/denoise-demystified

Need for speed. Denoise is by far the most advanced of the three Enhance features and makes very intensive use of the GPU. For best performance, use a GPU with a large amount of memory, ideally at least 8 GB. On macOS, prefer an Apple silicon machine with lots of memory. On Windows, use GPUs with ML acceleration hardware, such as NVIDIA RTX with TensorCores. A faster GPU means faster results.

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"

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
Community Expert ,
Apr 30, 2023 Apr 30, 2023

Copy link to clipboard

Copied

quote

My question is now, is there a significant speed advantage regarding development of images when I have all the images and catalog on the internal hard drive ????

 

 


By @Thomas29641998u6h3

 

Probably not. Sure, it's always recommended that the catalog is placed on the fastest drive, as that will provide the optimum LrC performance when doing catalog-intensive tasks (so mainly Library functions). But having the images on the fastest drive will likely not provide any significant performace advantage compared with images on an external drive. Imports will be a little quicker, but little else would be.

 

Having said that, if you have the space on the internal drive, no harm in having the images stored there as well. And of course that would be one less thing to carry when travelling.

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