Draw Mask (Auto-mask) Problem with Wacom tablet

Commentaires

33 commentaires

  • Kaweeno
    Mine does that too. Very frustrating. Can't figure out what causes this.
    0
    Actions pour les commentaires Permalien
  • SFA
    The video indicates that the solution is to roll back the Wacom driver.

    Did that work for you?

    I assume not unless the video has been very recently updated.

    Grant
    0
    Actions pour les commentaires Permalien
  • HansB
    Did you see this discussion in this forum? It sounds similar, and it offers a workaround.
    viewtopic.php?f=72&t=27180


    Regards,
    Hans
    0
    Actions pour les commentaires Permalien
  • James McCarthy
    I did find a solution!
    I simply had to enable "Windows Ink" in the Wacom Tablet settings application specific for Capture Pro One. Haven't had any problems since doing that.

    Thanks!
    0
    Actions pour les commentaires Permalien
  • CCWH
    I've gived the answer in this video:

    Richard OLIER
    Hi,I think the problem is not the driver version.You can enable or not windows ink in the wacom settings. If you enable this function, all features of the tablet are working with C1 (pressure control, no glitch) but you have the long press = right click bug (a bad new feature....).If you disable windows ink option in driver, you lose pressure control, and you have your drawing glitches in c1.Could you try again ?
    0
    Actions pour les commentaires Permalien
  • Chad Dahlquist
    recently moved to windows and wacom support flat out is horrid

    that link to the other post in this forum worked for me

    you basically end up here and do this
    https://www.reddit.com/r/wacom/comments ... sure_turn/

    the guy has some swearing and stuff in his pic at the bottom so beware of that 😊
    0
    Actions pour les commentaires Permalien
  • cdc
    I also have this super annoying bug.

    I followed the steps in the swearing filled suggestion from reddit but it still happens.
    If I enable windows ink in the wacom tablet properties the problem goes away but now alt/ctrl/shift tags show up next to the cursor every time I press those key. Trading one annoyance for another, smaller, annoyance.
    0
    Actions pour les commentaires Permalien
  • Chad Dahlquist
    bummer to hear for ya still having issue cdc

    I can say I recently moved to windows and things like this are why I am glad I did so I know how bad it is on this side 😊 hahahahahahah my mac never had all the little issues like this 😊

    I also did a complete uninstall and reinstall of the drivers etc..
    0
    Actions pour les commentaires Permalien
  • C-M-B
    Same thing with the modifing keys (alt, shift,..) happens with Adobe Photoshop but there's a .txt you can modify to stop it from doing that.
    With CaptureOne it's slightly annoying but generally you don't use alt/ctrl/shift as much.
    0
    Actions pour les commentaires Permalien
  • JH-Photo
    It is frustrated! For me the workarounds doesn't fix the problem.
    Who can be support this? Microsoft or Phase One?
    0
    Actions pour les commentaires Permalien
  • Michael_Madsen
    Exactly same problem - just so frustrating - it really is a dealbreaker for me.
    Ive been testing this extensively with little luck until I discovered something odd... the sudden drawing of lines happens ONLY in the upper left quadrant of the screen - (if your on dual monitor it happens on the entire upper half of the screen 1. To be more precise - it happens when your mouse is crossing THE BORDER between the upper left quadrant of the screen and the rest of the screen area. Now this got me suspious - this exact error has been observed previously in other apps and was linked to "Get Mouse Move Points Ex"
    https://msdn.microsoft.com/en-us/librar ... 59(v=vs.85).aspx
    https://forums.getpaint.net/topic/28852 ... e-drawing/
    I think this is too much of a coincidence - and Ive tried EVERYTHING to no avail - windows ink on and off - tablet mode changes, disabling all pen and touch functionality, diff versions of COP, diff wacom drivers etc. Ive fiddle with every concieveable (i think) setting possible and NOTHING works.
    This ONLY and consistently happens in all tested versions of COP we have at hand. We have had no other issues with any other software and/or windows ink/wacom settings.
    I suspect Phaseone is using an outdated or erroneous protocol or whatever in the communication with the input devices.
    It should be fairly easy to replicate and something that PhaseOne urgent needs to look into. For me as a retoucher its a dealbreaker.
    0
    Actions pour les commentaires Permalien
  • SFA
    [quote="NN635194248201089352UL" wrote:
    Exactly same problem - just so frustrating - it really is a dealbreaker for me.
    Ive been testing this extensively with little luck until I discovered something odd... the sudden drawing of lines happens ONLY in the upper left quadrant of the screen - (if your on dual monitor it happens on the entire upper half of the screen 1. To be more precise - it happens when your mouse is crossing THE BORDER between the upper left quadrant of the screen and the rest of the screen area. Now this got me suspious - this exact error has been observed previously in other apps and was linked to "Get Mouse Move Points Ex"
    https://msdn.microsoft.com/en-us/librar ... 59(v=vs.85).aspx
    https://forums.getpaint.net/topic/28852 ... e-drawing/
    I think this is too much of a coincidence - and Ive tried EVERYTHING to no avail - windows ink on and off - tablet mode changes, disabling all pen and touch functionality, diff versions of COP, diff wacom drivers etc. Ive fiddle with every concieveable (i think) setting possible and NOTHING works.
    This ONLY and consistently happens in all tested versions of COP we have at hand. We have had no other issues with any other software and/or windows ink/wacom settings.
    I suspect Phaseone is using an outdated or erroneous protocol or whatever in the communication with the input devices.
    It should be fairly easy to replicate and something that PhaseOne urgent needs to look into. For me as a retoucher its a dealbreaker.


    Have you reported this observation to Phase One using a Support Case? That way it is sure to receive attention.

    This is primarily intended to be a user to user forum. On that basis information exchange is less certain.


    Grant
    0
    Actions pour les commentaires Permalien
  • don maclean
    This issue has been reported to support for many years now, I first reported with v8, then v9 and then v10.
    0
    Actions pour les commentaires Permalien
  • SFA
    [quote="AiDon" wrote:
    This issue has been reported to support for many years now, I first reported with v8, then v9 and then v10.


    But has the specific observation made in the previous post been communicated to C1 tech support?


    Grant
    0
    Actions pour les commentaires Permalien
  • C-M-B
    I too have reported this among other issues with Wacom tablets in January this year, made a video which I was told was being forwarded to the development team.

    Honestly I think this is extremely embarrassing for PhaseOne/CaptureOne.

    Working with a tablet is a major aspect of professional photography and image editing/retouching, and it's hard to understand why there's an unwillingness to address this issue. I don't believe for a second that the people who work there are incompetent.

    But maybe they don't care about Windows users as much as Mac users and since they don't have a problem it's not a concern. 😭
    0
    Actions pour les commentaires Permalien
  • don maclean
    [quote="SFA" wrote:
    [quote="AiDon" wrote:
    This issue has been reported to support for many years now, I first reported with v8, then v9 and then v10.


    But has the specific observation made in the previous post been communicated to C1 tech support?


    Grant


    Hi Grant,

    Specifically this issue has been reported.
    0
    Actions pour les commentaires Permalien
  • SFA
    [quote="AiDon" wrote:
    [quote="SFA" wrote:
    [quote="AiDon" wrote:
    This issue has been reported to support for many years now, I first reported with v8, then v9 and then v10.


    But has the specific observation made in the previous post been communicated to C1 tech support?


    Grant


    Hi Grant,

    Specifically this issue has been reported.


    So the information provided by Michael Madsen in his post has been sent to the C1 Support Team using a Support Case?
    0
    Actions pour les commentaires Permalien
  • Richard Allen
    It has 😊
    0
    Actions pour les commentaires Permalien
  • SFA
    [quote="Richard Allen" wrote:
    It has 😊



    Excellent!
    0
    Actions pour les commentaires Permalien
  • Michael_Madsen
    Hi Grant !
    yes, I just posted a bug report to Phase One and will be monitoring the progress closely.

    Its mindblowing that a bug this severe haven't been addressed for so long. I guess now when so many jumps ship from Mac to Windows this will get noticed a lot more.

    Im trying to spread awareness on facebook and youtube to get a clearer image of the problem and to get people affected to actually file bug reports!

    In the meantime COP is just a no-go on Windows
    0
    Actions pour les commentaires Permalien
  • Andrew Paquette
    Same problem here, with version 11.01
    0
    Actions pour les commentaires Permalien
  • Michael_Madsen
    Could somebody from PO chime in - is anybody taking this serious ?
    0
    Actions pour les commentaires Permalien
  • Robert Whetton
    using 6.3.14-1 and can't replicate that problem 😕
    0
    Actions pour les commentaires Permalien
  • Grant Hodgeon
    [quote="SFA" wrote:
    [quote="Richard Allen" wrote:
    It has 😊



    Excellent!


    Hi, SFA.

    I see you often on the forums and it's great that you're directing folks to submit feedback to Phase One directly in order for these bugs to be fixed -- unfortunately I don't know how helpful this repetitive line is, as quite often, we have. And quite often, it's fixed, and quite often, it's reintroduced, and quite often, we're all repeating ourselves.
    0
    Actions pour les commentaires Permalien
  • SFA
    [quote="photoGrant" wrote:
    [quote="SFA" wrote:
    [quote="Richard Allen" wrote:
    It has 😊



    Excellent!


    Hi, SFA.

    I see you often on the forums and it's great that you're directing folks to submit feedback to Phase One directly in order for these bugs to be fixed -- unfortunately I don't know how helpful this repetitive line is, as quite often, we have. And quite often, it's fixed, and quite often, it's reintroduced, and quite often, we're all repeating ourselves.


    Well, you have to start somewhere - preferably somewhere that fits in with a company's management controls as presented to the wider world.

    Dodge that and there is no reason whatsoever to expect anything other than chaos, confusion and disappointment. Or worse if you are very unlucky. Maybe better if you are very lucky but realistically the balance of a varied set of expectations from a wide array of people with different primary interests will almost always go unfulfilled. (The counter intuitive inverse of that is a liking for the responsive sole developer and the acceptance of risk that the sole developer or their interest level wanes at some point if they don't pass away first. If costs are low, or preferably zero, we tend not to have much of a problem with that risk.)

    If, having cleanly and clearly presented problems and recurring problems through the vendor's advised and expected channels the problems continue or re-occur without explanation or urgent attention then I would agree that there comes a time to take the vendor to task about it and at least obtain a detailed statement about whether or not it is something under their control.

    Here's a case from this weekend. My machine suddenly appeared to be greatly slowed using C1 for some reason as I was working on a new shoot. Co-incidentally I had a problem with the power supply (my fault entirely) and needed a new one to be certain of a long term reliable repair. Meanwhile I made use of a PSU (notebook type) from an older less powerful device. The machine complained about the PSU specification as expected but worked and would charge the battery. I tried a few different power settings but all of the were slow so obviously it was a C1 problem and the small OpenCL assistance I can get with this device was apparently not working - or not much.

    I filed a Support Case accordingly.

    Yesterday the replacement PSU arrived. With 180Watts available once again and no other changes everything is back to normal. The machine is happier and so C1 is happy. Whose problem is that?

    I immediately thought of all of those reports of terrible performance - especially prevalent in the large part of the community here - the Mac users - where for some reason people using what appear to be the same specification machines have sometimes excellent performance that matches their expectations yet others experience situations that, to them, are unusable - which is very close to what I was experiencing for some days with the much lower Wattage PSU even without putting it under pressure. That must have been hardware restrictions. Difficult to see how it was a software problem in this context.

    The Free Technical support service and then the information requests on the developers (for any organisation in software development) can put a lot of inefficient support load on the technical teams. And of course costs.

    If we could find a way to eliminate that overhead and allow developers (any developers, I'm not personalising this here) to identify and concentrate on only the real problems and the best solutions the whole software industry could benefit. It might even be able to get Agile Development to work effectively in a mass market.

    So you still need a properly managed problem reporting system and it helps no one to go outside it at the first sight (for them) of a problem. The process collects data for analysis, should ensure a response and intended to provide an initial personal service though solutions, in the mass market, most likely need to be delivered in bulk rather then bespoke methods.

    If that process can be seen to be repeatedly missing or re-introducing the same problems for the same reasons then clearly something is wrong and it ought to be addressed. A structured support system is likely to be the best approach we have right now although maybe at some future point some deep AI options might take over fully. Whether that would be a good thing or not from the perspective of the average user - pro or hobbyist - remains to be seen.

    Personally I don't think an unstructured free-for-all, such as using forum posts as the sole basis of Support should people adopt that approach, works for anything other than, perhaps, ideas for social media oriented applications. Even then I'm not optimistic about them. It's a bit like crowd funding - a great concept until it isn't.

    Influence through a structured support system should be a far better option.

    If, for some reason, it appears not to be a good option then why it fails should be investigated and if there seems to be no way to fix it the choice is to walk away if the situation is unacceptable. Of course that assumes that there is somewhere better to walk to and that it's a freely available choice.

    Just my thoughts for what they are worth.


    Grant
    0
    Actions pour les commentaires Permalien
  • Grant Hodgeon
    [quote="SFA" wrote:

    Well, you have to start somewhere - preferably somewhere that fits in with a company's management controls as presented to the wider world.


    Correct, and it has been mentioned that this was submitted accordingly.

    Dodge that and there is no reason whatsoever to expect anything other than chaos, confusion and disappointment.


    To infer we've dodged anything isn't accurate.

    If, having cleanly and clearly presented problems and recurring problems through the vendor's advised and expected channels the problems continue or re-occur without explanation or urgent attention then I would agree that there comes a time to take the vendor to task about it and at least obtain a detailed statement about whether or not it is something under their control.


    I'm glad we agree.

    I immediately thought of all of those reports of terrible performance - especially prevalent in the large part of the community here - the Mac users - where for some reason people using what appear to be the same specification machines have sometimes excellent performance that matches their expectations yet others experience situations that, to them, are unusable - which is very close to what I was experiencing for some days with the much lower Wattage PSU even without putting it under pressure. That must have been hardware restrictions. Difficult to see how it was a software problem in this context.


    It's a shame you thought of Mac users and their complaints of terrible performance when you were having issues. It appears you're conflating your problems with Mac users, who do not dictate their PSU.

    The Free Technical support service


    It's not free

    If we could find a way to eliminate that overhead and allow developers


    We can. Don't assume the two platforms cannot co-exist. The pressure of a public facing forum and a collective voice of users can do far more than slinging a penny down a Well. I think it's important to note there's many ways to 'eliminate' the 'overhead' that you think there is, I could show you countless examples but your argument will circle around the fact that Phase One is their own company and they can do things however they'd like. Which is correct, but irrelevant.

    So you still need a properly managed problem reporting system and it helps no one to go outside it at the first sight (for them) of a problem.


    Unfortunately again you're conflating reality with expectations. You're expecting people to come to the forums first and complain, I'm explaining that this isn't necessarily always the case and to reduce their problem to 'submit a report' can be counter to helpful. We all agree that bugs should be fixed, shouldn't return, and shouldn't exist. We all agree that this is an impossibility with regards to software development -- but what we don't have to do, is rest on the laurels of a development release cycle that may well be dictated by the dollar more than the user.

    You state this yourself often enough, this is a User to User forum. But it is hosted and operated by Phase One. Phase One can, have and will lock, delete and prune topics that are against their ethos or company direction. Phase One have included information on these forums that you can't even find in a KB article. To assume Phase One staff not only actively ignore the forums, but take zero stakes in what occurs here is not accurate, and I think it just as valid to air frustrations and garner a 'group' of individuals in order to help dictate that change.

    Influence through a structured support system should be a far better option.


    Yes, we get it. You want to shut down the conversation because it detracts from true progress and is a relegated baby step to social media and crowd funding. A concept you personally find great, until it isn't. That's okay but isn't necessarily helpful on a topic asking about a bug that at this rate may outlast religion. Irrespective of how blue your face was when submitting the report. Again.

    I think there's validity in all platforms of feedback and this isn't a subsection on luminous landscape or dpreview. We're under the nose of Phase One. Let us smell.
    0
    Actions pour les commentaires Permalien
  • SFA
    Grant,

    My original comment that you picked up on a few hours ago was made some weeks ago and I'm not the only person around here that offers guidance to people who may not know how Phase, rightly or wrongly depending upon ones personal opinions, intend that their process should work. It seems reasonable to offer the repeated advice despite how frustrating it is sometimes to have to do so.

    Do you have a problem with that?

    Why have you decided to choose now to comment on it and then follow up with implied criticism of such attempts to help people?

    You also seem to have mostly missed the point of what I wrote in response and indeed seem to have completely misunderstood some if not all of them.

    I'm not sure if it's worth responding further - frankly discussions like this in a forum are usually a little pointless - but if I do it may not be for a day or so. I have more personally important matters to pay attention to at the moment.

    Meanwhile you might re-read what I wrote rather than what you seem to think I wrote.


    Grant
    0
    Actions pour les commentaires Permalien
  • Grant Hodgeon
    [quote="SFA" wrote:
    Grant,

    My original comment that you picked up on a few hours ago was made some weeks ago and I'm not the only person around here that offers guidance to people who may not know how Phase, rightly or wrongly depending upon ones personal opinions, intend that their process should work. It seems reasonable to offer the repeated advice despite how frustrating it is sometimes to have to do so.


    I agree, I just disagree with some of your opinions.

    Do you have a problem with that?


    No sir, just an opinion.

    Why have you decided to choose now to comment on it and then follow up with implied criticism of such attempts to help people?


    I replied when I read what I saw, especially given the repeated bug report questioning despite already being told the answer.

    You also seem to have mostly missed the point of what I wrote in response and indeed seem to have completely misunderstood some if not all of them.


    I'm sorry, I'll gladly respond to whatever points you think I missed.


    I'm not sure if it's worth responding further - frankly discussions like this in a forum are usually a little pointless - but if I do it may not be for a day or so. I have more personally important matters to pay attention to at the moment.


    Perhaps. No rush on the matter, there's no baited breath. Sorry you've taken this personally.

    Meanwhile you might re-read what I wrote rather than what you seem to think I wrote.


    I did so and responded quite carefully and respectfully. If we're offering unsolicited advice, I'd ask you take your own.

    Grant
    0
    Actions pour les commentaires Permalien
  • Oka Morikawa
    Please, PLEASE!!!! FIX THIS.

    On latests 11.1 things are getting so BAD that I can't create proper masks with or without Windows Ink. I use more time fixing the "straight lines" than drawing proper masks.

    I have been on talks with support but current response is only, update the drivers (which doesn't work). I have tried different Windows 10 versions (now on 1803) and the problem is same.

    I don't care about the new features, use all the resources to fix this damn thing!
    0
    Actions pour les commentaires Permalien
  • Michael_Madsen
    UPDATE :
    I think I've finally figured this one out. I discovered that windows ink would work for the first moment of using CP1 but then after app switching windows ink would simply stop working and then CP1 would default to the solution of apperantly treating the pen input as mouse inputs via Get Mouse Move Points Ex.
    Finally got windows ink working stable after uninstalling WACOM and reinstalling the older DRIVER 6.3.15-3.
    Next problem is that right clicking is not working.
    You need to do the following :
    Control panel > pen and touch > Change tablet pen settings
    settings...
    Press and hold > "Settings"
    UNCHECK "Enable press and hold for right-clicking"

    Pen options :
    Pen buttons : ENABLE "Use the pen as a right-click equivalent"

    if you dont you can't assign a right click to the pen in the Wacom panel. It will make a ctrl-click instead - which is totally diff thing.
    So in all honesty it's not a bug pr se and i understand the difficulties in fixing this problem. BUT :
    I would strongly suggest the development team at capture one to make this problems clear to customers in manuals etc.
    Also make it possible to default to wintab same as we normally do i photoshop
    The # Use WinTab UseSystemStylus 0 /w PSUserConfig.txt has for a long time been a commonly known hack to circumvent all the problems with ink in PS, and we need phaseone to either implement wintab or roll their own tablet solution.
    Relying on Windows Ink for such a critical functionality as pen input is a bit too sketchy imho.
    Hope it helps
    0
    Actions pour les commentaires Permalien

Vous devez vous connecter pour laisser un commentaire.