The Verdict 2021
Downloaded the trial today and I can confirm it is definitely NOT faster than 2020. Still takes a while to render RAW files and takes just as long to add presets. It's just the same speed as 2020, They have not made anything faster, just added a few tweaks, but nothing major. No need to upgrade.
I have to agree I'm afraid. I see good improvements to the movement of the adjustment sliders, and the full screen mode is a much needed addition (even though it is not full, full screen!). Apart from that, there is nothing new that I need so I can't justify the cost of an upgrade (or risk introducing new performance issues, as happened in the past). Slightly disappointing, but I guess I can wait for next year...1
So far, all the issues from earlier versions remain in some form or the other, but, the good part is that new bugs have been added :)
Performance is actually slower than 2020 IMO.0
Roger Gough Indeed. I have a top spec PC, 32Ram, 11gb Graphics card, i9... and it hasn't changed at all. it baffles me how other seemingly, smaller S/wares can handle RAW files easily, like ACDsee, fast as a gazelle, and yet ON1 have 3 integrations of their product, and still can't manage it.0
speed or not, ON1 (mostly) gets me to where I want to be, and I'm really enjoying the nature of the work flow0
The speed is not really an issue, it doesn't seem to be any slower. For me the new clone tool is the real deal breaker. This item alone is enough for me to stay with 2020.0
My experience is PR 2021 is more responsive and stable for my workflow. Selectable clone areas a big plus.0
2021 is not faster than 2020. Many of the old bugs persist. Already found a few new ones. I wish there was a public repository of know bugs, a la Github.0
2021 is not faster than 2020. Many of the old bugs persist. Already found a few new ones. I wish there was a public repository of know bugs, a la Github. So that people can chime in on bugs. At the moment I can never tell if I'm the exception or the norm when I run into a big.0
Its so damn frustrating that they won't fix the existing problems, the main being speed of rendering RAW files, and the general speed of the sliders, everything seems to be always lagging behind what you're doing. Great software if they could sort this out, instead they put out a NEW version, with a couple of gimmicks. Certainly NOT worth the upgrade and the price hike. Looks like I'm leaving ON1 behind until they sort their in house dev's to make this software quick, efficient, and intuitive.0
It's a nice toy to have around John Inglis, like Luminar IMO :)
It does work for some and not others...Which is how things are with most such.
ON1 has fundamental design flaws and it is kind of slapped together and I would not expect that to change anytime soon. On paper, ON1 seems to be the dream app for all, but, in reality, it remains a toy to play with, not work with.
Support is also very nice for ON1, they will simply close your tickets w/o even a response.
I paid for the toy and I am playing :)1
The new Colour Range Gradient thing is defeating me. My experience so far is if you move a Gradient which as already had a colour range applied via the picker then if the bigger circle/handle goes over a different colour you edit is goosed. To me it looks like they've not thought this through.
I've watched a couple of Dylans' videos on this and in his examples the colour under the circle is conveniently the one he is targetting. I've raised an issue with support. Is there something I'm missing here?(quite probably)0
I think PR is slowly, very slowly improving in performance. However, I still mostly agree the focus by the dev team is currently on the wrong things. Bugs and performance should be priority 1 and 2. Been saying this for a couple years now.
I use PR because it checks 3 boxes for me:
- It's not Adobe
- it has layers
- the license is perpetual with no requirement for subscriptions.
I'm still waiting for the year when they spend the whole year after release to do nothing more than fix bugs and improve performance instead of adding a few new features in the XXXX.5 version.0
If you need to mask on two different colors you should be using 2 different adjustment layers, one for each color. Dylan did say in yesterday's webinar that there is more work being done on the Color Range Gradient.0
Thanks for the response. I don't want to mask on two different colours, I want to adjust the position of the original mask whilst retaining the original colour range. As it stands it looks to me like that's now not possible.
Because the circle/handle controls the location of the gradient I don't see how it can also be used to pick the colour range point. Unless you do can something like right click on it to select 'colour range picker' mode then the circle can be moved and the gradient doesn't. Right click again to revert.
But, as ever, I may very well be missing the point.0
When you set up a Color Range Mask you are selecting one color. When you apply a Color Range Gradient, unless the gradient's handle is over the exact same color as what you selected with the color range mask you have now selected 2 different colors even if they appear close.
The handle does control the gradient's position but when you turn on the Color Range option it also controls the base color for the range it will apply to. If all you want is a gradient over the color range mask you've already created don't turn on the color range option for the gradient. Don't forget that you can use the Levels slider with a color range mask the same way you can with a luminosity mask.
Perhaps if you show us screenshots of what you're attempting to do and the masks being created I can be more help.
Another option is to apply the Color Range Gradient first, then use the Color Range Mask picker. I don't know if that will work any better for you but it does work when you want to modify a luminosity mask. The luminosity mask overwrites the color range when used 2nd. The color range modifies the luminosity mask when it is applied 2nd.0
I am not religious Matt Dean and I don't have anything against Adobe :)
Looking at how quite a bit is going into the subscription side while the price per annum/release remains consistent, I am reasonable okay with the subscription model now...
Yes, layers and effects! Unfortunately, layers in ON1 defeat the non-destructive editing using a proprietary format which is not good. Luminar does a much better job since it keeps the originals instead of creating a new file. The other point about this is that it takes up as much additional space for the new file as PS and cannot be read by any other app in case of any issues.0
I've always found the speed issues with ON1 are linked to cataloguing and 2021 is no exception. I tried cataloguing just one directory and the speed dropped considerably, and the cursor kept freezing. For cataloguing I use the free copy of Bridge and Luminar 4 which are both glitch-free.0
I could not agree more with Matt Dean above. It is very disappointing to remember that the emails and blogs of Craig Kuedell (On1 CEO) earlier this year, received lots and lots of feedback to the same effect. Either the message was not heard, not believed, or just ignored.0
How happy would you be to pay for a 2022 "upgrade" that contained nothing but bug fixes? Most people would feel ripped off.
How long do you think the company can stay in business if they don't have a product that brings in more money? I doubt it would be long enough to survive a free upgrade after a year of nothing but bug fixes.
There has to be a balance. More frequent bug fix releases between annual upgrades would be a nice step in the right direction.
Not everyone experiences the speed problems some of you are describing. Cataloging my entire photos directory has not impacted the program's performance on my system. I did have some slowdown while working on a photo last night but it was a 443.4MB .onphoto file with half a dozen different Layers with multiple blending modes and masks. When the brushing started slowing down I adjusted the video card strength slider down a bit. Frequent returns to the Browser to flush the scratch space and save my work then right back into editing would return performance after doing a lot of brushing. Every once in a while I would quit the program and use a memory flushing program to return all unused memory to the system then went back to work with improved performance. (Yes, I know that implies a possible memory leak. However, workarounds work. 😉)
I'm running on a 16GB MacBook Pro with only 2GB of VRAM. I'm sure a better GPU would have sped things even more.
Just my 2¢.0
I agree Richard, bug fixes need to be more frequent and not just bundled into next year's release. Topaz releases bug fixes almost on a weekly basis. Very frequent and always free.
Historically there has been a final update to the current year's program after the next year's upgrade version has been released. It will be interesting to see what gets fixed for 2020 assuming another release is made.0
"How happy would you be to pay for a 2022 "upgrade" that contained nothing but bug fixes? Most people would feel ripped off.
How long do you think the company can stay in business if they don't have a product that brings in more money? I doubt it would be long enough to survive a free upgrade after a year of nothing but bug fixes."
Honestly, if they were to do this, how many new customers would they gain?
Also, there is nothing wrong with having people work on new features for the next year release, as long as the priority for all patches for the year are just to fix what is wrong.
When I said "I'm still waiting for the year when they spend the whole year after release to do nothing more than fix bugs and improve performance instead of adding a few new features in the XXXX.5 version." I did not mean they can't put time into new features for the "next version" but XXXX.5 is not the next version. Every update throughout the year should be performance and bug fixes and not new features.
Have a group of people working on bugs and performance and another team working on features. Release bug/performance patches throughout the year and also have those fixes rolled into the new feature build for the other team intended for the next yearly release. Pipe dream? maybe. From what I understand they don't have a lot of employees, but maybe they should look at expanding the team so they have the manpower to fix the problems that have been there for 3 years.
One bug I have seen for a couple years at least is black spots with Luminosity masking... when will that get fixed?0
Here's a new error for PR 2021: PR will rotate your photo in the selected rotation direction times the number of selected photos. Select 1 photo and your photo rotates 90º. Select 2 photos and your 2 photos rotate 180º each. Etc. Ugh!0
I can confirm the above. Select 4 photos and they rotate 360 degrees, back to their original position. Please report to Support.0
I have been using On1 for less than a year but have never been aware of black spots on luminosity masks. Can you upload an example please. Have you reported it if you are convinced it's a real bug?0
I have reported the bug to ON1 Ray Miles using 2021's feedback menu item. If only I could share a link to the bug report so others can chime in.0
Well done Bart. I forgot there is the new feedback item! I have sent a message to support the old-fashioned way...0
Here is a link to a post by another person having the same issue. Also, I use the same dodge/burn presets I created following blake's direction. https://on1help.zendesk.com/hc/en-us/community/posts/360067252291-Local-Adjustment-black-spots-and-clipping?mobile_site=true0
Matt, I've been asking them for a job for 2 years. Even offered to work on commission, pay me when I find and fix the bug.0
James-Thomson, about your color range problem (from 11 hours ago)...
When you turn on color range while using a gradient, the center handle will set the color as you move it around. You can actually see the colors changing in the local adjustments color picker.
If you can't move the handle to select the proper color, then you can use the color picker or eyedropper in the local adjustment to over ride it.
Just be careful to not move the gradient again because it will reset the color as it's moved.0
Interestingly, by contrast...I made my first comment on the Adobe forums (ever) right after the LR 10 release and their support staff was more than keen on getting samples, videos whatever they could and also asked if I could test a beta for the issues under a NDA.
This was so disappointing...They should have ignored comments in their forums...More so for newbies :P
Just to clarify, I only made a comment in the forums about the issues and that I had rolled back to 9.4. No bug report/ticket...Just a public comment in response to another similar comment.0
Please sign in to leave a comment.