Banding issue with ON1PR2022
Answered
I have been using ON1PR for a great many years and am a plus pro customer. ON1 support is once again MIA when I need help.
I just installed the ON1PR2022 patch. Still have this new problem. Very noticeable banding on images with clear (boring) no clouds blue sky.
I am exporting long edge 3820px and have tried several ppi settings. Currently at 72 I think. This is how I've been exporting for many years. jpg File sizes in the 1-2 meg range.
Had this same problem with Lightroom ten or more years ago. Got lots of suggestions/opinions but the fix turned out to be something ridiculously simple. Too long ago...can't recall what fixed it.
I really hate it when ON1 adds "features" that break core capabilities that have worked for a long time. Sadly, they seem to do this all too often. My take is that since it's worked correctly for years and now doesn't, it's likely yet another bug. Anyone seeing this and if so is there a work around?
On a wider topic, I really like ON1PR. After investing a lot of time learning how to use it, it is mostly great and does most everything I could ever want. But ON1 support has been and still is really HORRIBLE. I wish ON1 Corporate would do something about this fact since it seriously detracts from the value of ON1 products.
Feel free to move this to another forum if it doesn't belong in "general".
-
I usually get replies from Support within a couple of hours, can't imagine why your response isn't as quick.
The only real solution is to send examples to support for them to identify the problem. I'm assuming that you've already done that so just be patient and they will get back to you.
You can check the status or add new info to the ticket by clicking your name at the top of this page and selecting My Activities.
0 -
FWIW, when you specify the export size in pixels the ppi field is ignored. It is a conversion factor between inches and pixels—PixelsPerInch. When you give the size in pixels no conversion is needed.
The banding is most likely due to the change in colorspace when you export to jpeg. I assume you are exporting to the sRGB colorspace? What you see onscreen is in the much wider ProPhoto colorspace. The program does have the Soft Proofing feature under the View menu which allows you to see how the image will look in different colorspaces. You choose the one you want to view with the View > Profiles command. Turning on the option to Gamut Warning option will show you the colors which are outside of the selected colorspace. Those are the ones that will be changed to fit inside the new colorspace which leads to banding.
0 -
Hi Brian. I very much appreciate your thoughtful feedback.
Yes on sRGB IEC-whatever.
Yes, I turned gamut warning on. Nothing.
As I recall from troubleshooting this on LR many years ago, a fellow I was working with who REALLY knew LR brought this gamut colorspace issue up. Sadly, it turned out to be a rat hole. The fix in that case was something REALLY simple.
The image looks fine on the computer. The banding only shows up in the exported jpg so it's obvious (at least to me) that something got broken (or a feature was added that needs to be changed) that's causing this.
I see nothing that looks promising in the export dialog to fiddle with.
0 -
I'm with Rick then, you'll have to wait for support to get back to you. I'd be interested in hearing what they have to say, especially if they have a fix for you.
0 -
I would LOVE it is ON1 support actually did their job. Unfortuntly, waiting for them to actually help me is not likely to bear results :(
This Stevie character has my ticket and he's been notortious for many years for being unhelpful and unresponsive.
0 -
I submitted a report earlier today and Stevie has already responded. Did you check the box telling them you are a Plus member when you submitted your request? Have you sent a follow up asking politely why you haven't heard back yet? You realize they are probably slammed right now with the new release and its update, right? Unfortunately, sometimes things can fall through the cracks in the system.
0 -
Yes although I shouldn't have to flag myself as a high tier subscriber to get a simple response on what appears to be a software bug. I've been an ON1 customer for many years and Stevie is absolutely the worst support tech on the planet. If I even get a response from him at all it's just a demand for more information (even though I am VERY detailed in my problem description). I posted this ticket several days ago and so far, crickets from Stevie. I politely asked/begged that the ticket be bucked to someone who will actually respond. Crickets.
As I said, I really like ON1PR and I especially WANT to love ON1 since they are a local company, but their support over the years has been nothing short of atrocious.
The ON1 owner has made quite a point that he is intentionally disengaged from the day-to-day operations of the company. And it shows. There are a number of shills on this site who try to make it appear that the issues customers are seeing are non-existent... but there is no way that I could ever use ON1PR if I was a high volume professional photographer. Just too buggy. And each "upgrade" invariably breaks functionality that previously worked.
I suppose the smart play for me is to ditch ON1 and go to a more professional vendor. And I may wind up having to do that. But I'm not looking forward to the steep learning curve with a new app. Plus, ON1 has a lot of features that work very well for me. I would LOVE it if they actually listened to their customer and fixed reported bugs... or ideally fixed the bugs before these "upgrades" we released.
If On1's support group wasn't worst in grade I wouldn't even think about leaving.
I *RARELY* submit a ticket asking for help. The fact that ON1 support is "slammed" due to this latest release says a lot about how truly crappy and buggy On1PR202 is. An SQA manager who actually knew what he was doing and did comprehensive regression testing prior to release would help a lot. I found this bug in under five minutes so I'm guessing that any serious regression testing is non-existent.
All I'm asking for (and that apparently is asking a LOT in ON1 world) is help on what seems to be an obvious bug on their latest "upgrade".
I am a seasoned systems engineer. Upgrades that break core capabilities that have worked for years are not "upgrades" at all.... I would hope that someone at ON1 is professional enough and experienced enough to understand this.
0 -
You've got to do what you've got to do. I'm sorry you've had such a bad experience. It is 180º out of phase from my experience with him.
0 -
For those visiting this forum to find a solution to the banding problem I will update this thread with the "solution".
After some experimentation I found that increasing the export quality resolves this issue. I had to double the quality value which of course doubled the size of the resulting jpg file. This is a problem for me since my ISP is constantly crabbing about disk usage.
It would be nice if ON1 could introduce new features and improvements (which are very welcome) without breaking legacy capabilities that have worked great for years.
0 -
I assumed that you would have the quality setting all the way up. In all of the things that you said you tried, not once did you mention that quality wasn't set at 100%.
0 -
I had this problem too. I tracked it down to an Edit setting. I *think* I just turned off 'Recover Highlight Hue', I've certainly found that problematic in other JPEG exports with bright areas
In support of ON1, I have been using it for several years now and I think the 2022 version is a good step forward, even before considering the noise/sky enhancements (that I haven't tried yet).
0
Please sign in to leave a comment.
Comments
11 comments