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

P: No pressure sensitivity for Wacom Intuos Pro

LEGEND ,
Nov 28, 2019 Nov 28, 2019

Copy link to clipboard

Copied

Hi, I'm using a new Wacom Intuos Pro with latest Firmware. According to Wacom's Diagnosis Tool the pressure sensitivity works fine from 0-100%.However, in LR I cannot use the pressure sensitivity as I'm always getting the full 100% (e.g. when using the adjustemnt brush). I know this was an issue in the past but should be solved by now.
I'm using Windows 10, latest release, on a high perfomance PC.

Does anyone have a clue where I need to search for a solution?
Without that feature the tablet is almost useless....

BTW: It's working in Photoshop without any problems...

Thanks!

Bug Fixed
TOPICS
macOS , Windows

Views

2.2K

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 Correct answer

Adobe Employee , Apr 11, 2022 Apr 11, 2022

Updates to the Adobe Photography Products were released today and contain a fix for this issue. Please install the update via your Creative Cloud Desktop App or your respective App Store. 

 

Note: 

You may need to refresh the Creative Cloud App for desktop software to show an update available.  ([Ctrl/Cmd]+[Alt/Opt]+ [ R ])

For Mobile downloads, it may take several days for the update to appear in your respective App Stores.

 

Thank you for your patience. 

Status Fixed

Votes

Translate

Translate
63 Comments
New Here ,
Nov 07, 2021 Nov 07, 2021

Copy link to clipboard

Copied

I'm having the same issue. Changed settings, reinstalled latest drivers, checked and unchecked with windows lnk, disabled graphics acceleration in lightroom, adjusted pen pressure sensitivity, selected the wacom pressure compatibility for older applications. I'm using Windows 10, a wacom intuis pro small, and lightroom CC v11.

 

Lightroom Classic version: 11.0 [ 202110120910-0bccc70d ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Home Premium Edition
Version: 10.0.19042
Application architecture: x64
System architecture: x64
Logical processor count: 12
Processor speed: 1.6GHz
SqLite Version: 3.36.0
Built-in memory: 16166.7 MB
Real memory available to Lightroom: 16166.7 MB
Real memory used by Lightroom: 2994.6 MB (18.5%)
Virtual memory used by Lightroom: 3567.3 MB
GDI objects count: 714
USER objects count: 2569
Process handles count: 2054
Memory cache size: 23.4MB
Internal Camera Raw version: 14.0 [ 950 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 1260MB / 8083MB (15%)
Camera Raw real memory: 1270MB / 16166MB (7%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 3840x2160, 2) 1920x1080
Input types: Multitouch: Yes, Integrated touch: Yes, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No

Graphics Processor Info:
DirectX: Intel(R) UHD Graphics (27.20.100.9664)

 

Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: C:\Users\peter\OneDrive\Desktop\Lightroom\Lightroom Catalog-2-2-v10-v11.lrcat
Settings Folder: C:\Users\peter\AppData\Roaming\Adobe\Lightroom

Installed Plugins:
1) AdobeStock
2) Facebook
3) Flickr
4) Nikon Tether Plugin

Config.lua flags: None

Adapter #1: Vendor : 8086
Device : 9bca
Subsystem : 9621028
Revision : 4
Video Memory : 128
Adapter #2: Vendor : 1414
Device : 8c
Subsystem : 0
Revision : 0
Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: $$$/dvaaudiodevice/SystemDefaultAndEffectiveDeviceName=System Default - Speakers (Realtek(R) Audio)#{comment}DVAAU-4201250: Open the audio hardware preferences page.
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: LR5x38
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: 8
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 2048
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 8
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: Intel(R) UHD Graphics
GL_SHADING_LANGUAGE_VERSION: 4.60 - Build 27.20.100.9664
GL_STENCIL_BITS: 8
GL_VENDOR: Intel
GL_VERSION: 4.6.0 - Build 27.20.100.9664
GPUDeviceEnabled: false
OGLEnabled: true
GL_EXTENSIONS: GL_3DFX_texture_compression_FXT1 GL_AMD_depth_clamp_separate GL_AMD_vertex_shader_layer GL_AMD_vertex_shader_viewport_index GL_ARB_ES2_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_cl_event 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_compute_shader GL_ARB_conditional_render_inverted GL_ARB_conservative_depth 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_elements_base_vertex GL_ARB_draw_indirect GL_ARB_draw_instanced GL_ARB_enhanced_layouts 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_half_float_pixel GL_ARB_half_float_vertex 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_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_robustness_isolation 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_bit_encoding 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_stencil_export GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_packing GL_ARB_shadow 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_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_separate_stencil GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_compiled_vertex_array GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_polygon_offset_clamp GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shader_framebuffer_fetch GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_compression_s3tc GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod_bias GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_shared_exponent GL_EXT_texture_snorm GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback GL_IBM_texture_mirrored_repeat GL_INTEL_conservative_rasterization GL_INTEL_fragment_shader_ordering GL_INTEL_framebuffer_CMAA GL_INTEL_map_texture GL_INTEL_multi_rate_fragment_shader GL_INTEL_performance_query GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_KHR_context_flush_control GL_KHR_debug GL_KHR_no_error GL_KHR_shader_subgroup GL_KHR_shader_subgroup_arithmetic GL_KHR_shader_subgroup_ballot GL_KHR_shader_subgroup_basic GL_KHR_shader_subgroup_clustered GL_KHR_shader_subgroup_quad GL_KHR_shader_subgroup_shuffle GL_KHR_shader_subgroup_shuffle_relative GL_KHR_shader_subgroup_vote GL_KHR_texture_compression_astc_hdr GL_KHR_texture_compression_astc_ldr GL_NV_blend_square GL_NV_conditional_render GL_NV_primitive_restart GL_NV_texgen_reflection GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_SUN_multi_draw_arrays GL_WIN_swap_hint WGL_EXT_swap_control

Votes

Translate

Translate

Report

Report
New Here ,
Nov 08, 2021 Nov 08, 2021

Copy link to clipboard

Copied

I'm having this problem as well and have tried suggestions from this forum and the web. As an update, pen sensitivity works fine in photoshop but not lightroom classic. With the new layers capabilities in lightroom classic, I suspect more users are going to start complaining about the issue.

Votes

Translate

Translate

Report

Report
New Here ,
Dec 16, 2021 Dec 16, 2021

Copy link to clipboard

Copied

Smae here ! 

Windows, latest driver , latest LrC , pressure is not recognizeed + try and see that the erazer is not recognized too! 

In PS - all working just fine 

I wish Adobe will start listening to people - this is just another reason to switch tools

Votes

Translate

Translate

Report

Report
Community Beginner ,
Mar 01, 2022 Mar 01, 2022

Copy link to clipboard

Copied

Came back to this thread to see if it is worthwhile buying a Wacom again. Over three years of investigation and still not fixed. Just amazing! ....and wacom is still advertising the full Lightroom support.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Apr 11, 2022 Apr 11, 2022

Copy link to clipboard

Copied

Updates to the Adobe Photography Products were released today and contain a fix for this issue. Please install the update via your Creative Cloud Desktop App or your respective App Store. 

 

Note: 

You may need to refresh the Creative Cloud App for desktop software to show an update available.  ([Ctrl/Cmd]+[Alt/Opt]+ [ R ])

For Mobile downloads, it may take several days for the update to appear in your respective App Stores.

 

Thank you for your patience. 

Rikk Flohr - Customer Advocacy: Adobe Photography Products
Status Fixed

Votes

Translate

Translate

Report

Report
New Here ,
Jul 13, 2022 Jul 13, 2022

Copy link to clipboard

Copied

Dear Rikk,

thank you for coming back to us. I believe I have fully updated Lightroom (11.4.1 release) but there is no change whatsoever. Is there anything we need to set to make it work? Otherwise, I am afraid I need to report that the fix was not successful.

Votes

Translate

Translate

Report

Report
Engaged ,
Jul 13, 2022 Jul 13, 2022

Copy link to clipboard

Copied

Anois, if you are on Windows have you tried disabling the "Touch Keyboard and Handwriting Panel" service in services ?, just type services into windows search to get there. 

Votes

Translate

Translate

Report

Report
Advocate ,
Jul 14, 2022 Jul 14, 2022

Copy link to clipboard

Copied

Users can still experience latency (at the start of drag and not), unresponsiveness, poor performance and so on when Windows Ink option is enabled.

It's better than before but it's not fixed.

 

I have confirmation form Wacom as well that this issue is very much Microsoft doing: the Windows Ink API is the problems so even Adobe cant do much about it.

 

.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 08, 2022 Aug 08, 2022

Copy link to clipboard

Copied

You are very much on the spot, C.Cella.  This is a byproduct of the choice to prioritize Windows Ink (which is not optimized for creatives) over Wintab, which is what MOST creative tablet manufacturers would inject by default.  The responsiveness you get when you disable Windows Ink, is how the tablet manufacturers would prefer people experienced their products.  Many years ago MS told App developers that they no longer support Wintab, which is a bit misleading, as they NEVER supported Wintab.  They only meant that because they decided to stop using Wacom hardware for their pens, they were not using Wintab themselves any longer.  Most creative applications have preferences to select which input to prefer, but Adobe has not made that adaptation yet.  Please encourage them to do so.  It would make all tablets perform better in every creative application, and only MS apps would suffer from their lack of investment in the Ink experience. 

I have confirmed that Pressure does not work at all in Lightroom, and unlike the Photoshop PSUserConfig file option PS has, there is no way to allow for LR to prefer  Wintab instead of Windows Ink.  I hope this helps.  I love LR, and have for a decade, but when this broke (roughly the same time MS offered surface Pros to everyone that attended Adobe Max... think about that) My love was tarnished.  LR is such a brilliant app.  If only I could use it without Ink, which I cannot, because it breaks my microsoft apps as well.  I actually go in and turn on Windows Ink, only when I need to use the Adjustment brush (Masking now).  Which is a pain I will only suffer until I can find a better solution.  Rumor has it "others apps" are investigating Wintab, just to leverage this opportunity. 

Votes

Translate

Translate

Report

Report
Advocate ,
Aug 08, 2022 Aug 08, 2022

Copy link to clipboard

Copied

@TechManJoe 

 

For what is worth you can "ease" you pain (big euphemism here) by changing the flow for each brush stroke you do.

 

It gives the same results as with pressure sensitivity BUT it's infinitely more time consuming and complicated.

A terrible solution truly but you will have no slowdowns at least.

 

Or you can use very low flow (less than 10) but that means you will do more brush stokes and that means  trouble, big trouble. 

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 08, 2022 Aug 08, 2022

Copy link to clipboard

Copied

@C.Cella  ugh...  I had not even considered that.  I have just gotten into the habbit of dealing with Ink for as long as I have to, then turn it back off.  The only reason Wacom has it on by default is because MS convinced Adobe to abandon WINTAB by misleading them.  Windows Ink, makes Microsoft teams virtually unusable... did I mention it is a MS product?  I have reached out to the PM team at Adobe, in an effort to help them make creative tablet users have a better experience. (all major tablet users provide a wintab solution).  Let's keep our fingers crossed.  

Votes

Translate

Translate

Report

Report
New Here ,
Aug 08, 2022 Aug 08, 2022

Copy link to clipboard

Copied

This is nuts on the part of MS and Adobe. If they don't fix this, my next
computer will be a mac. No sweat for Adobe I guess, but the pressure tactic
by MS might push some windows users away...

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 08, 2022 Aug 08, 2022

Copy link to clipboard

Copied

LATEST

@peterf6030342  I am right there with you.  I like both platforms (as much as I like any computer, I guess) but the new M1/2s are pretty appealing and Apple finally is hitting a price point where they are genuinely competitive or better for performance/price.  In all transparency, I work/have worked for Wacom for 20+ years and just want to see tablet perform as well as then can (all of them, not just ours).  Wintab is more alive than ever and is the clear performance leader for creative applications on Windows.  In many respects it is easier to control and program for as well.  I am here to help Adobe if they want it and am trying to work with as many team leads as I can, but what is most important is that they hear the request from loyal users.  I am a photographer on the side and I just want this to work as well as I know it could.  I love the Adobe Suite, and other apps are starting to see the logic.  I am the LR and PS teams biggest fan and just want to help where I can.  But I will not let the tablet manufacturers take the fall for Windows Ink any more.  you want to know how well it can work, look to other apps that allow for Wintab (or use the PSUserConfig file for PS) but there is no similar solution for LR and it is crushing my soul.  🙂  Or just check out the same apps on Mac and you will see how well it should work.      

Votes

Translate

Translate

Report

Report