Watermark is shown anywhere
Hi Community,
I'm new to C1, previously LR user for years, and find several things I can't understand.
As final step of my editing in the process of exporting the finished image, in the processing recipe, I want to add a graphic watermark on the image, and I've found how to do it.
The problem is that with the watermark active in the processing recipe, it is displayed on EVERY photo in every place, when I browse them or when I edit them. Is this the 'normal' working for this feature? Why it's not only applied on the output image when processed?
thanks.
-
This is because the watermark is not a separate process in C1, it is part of the recipe. It is not applied to individual images. It is applied to whatever you are looking at after you select it (maybe a picture you are working on right now, or a picture your are looking at now from 3 years ago...).
You can duplicate a recipe and turn off the watermarking so you do not see it while working on the images. Only when ready to export, change the recipe to one with the watermark.
0 -
In addition to Rob's suggestion, using your existing recipe you can set the opacity of the Watermark to zero and you will not see it.
0 -
Thank you very much for your comments, strange way of working, out of my comprehension.
0 -
Most people probably want to see how it will look before they export.
Work with it a while and try to turn off the LR mindset to see if it starts to make sense. (Especially for mass production batch processing via the Output Recipe concept.)
0 -
Work with it a while and try to turn off the LR mindset to see if it starts to make sense
Thanks, I'm trying to get into the different way of working :)
0 -
I know it can be difficult to change habits.
When I first started to use Capture One my preferred raw convertor and editor at the time provided a workflow that was quite similar to a Sessions workflow technically but without the Session structure control.
At the time C1 did not have a Catalog option and I was happy with that because it was the need for a catalog that I found annoying using Lightroom.
Probably around a year after moving most of my editing to C1 I decided it was time to consider whether I could improve my workflow by better understanding the potential of the session structure. I did not think I needed it but I was seeing a growing library (not a very structured library but quite acceptable up to that point) of images and it was becoming more difficult to "manage" it based entirely on my memory!
It took me a little while switch off my habits as "must have" requirements and see how making use of the bits of the session structure that I found useful could then lead to a much easier way of working and organising things - at which point some of the other rather odd and useless looking features and functions in sessions ans C1 in general suddenly started to make a lot of sense.
Of course, the thing that first attracted me to C1 was that the look of the conversions from RAW files looked better as soon as they appeared. I could save a lot of time immediately although the old application could also produce great results and in some ways do even more when necessary. It just took more effort, a lot more time and had the potential to offer much more complexity to lead one down a time consuming path with a few dead ends along the way when chasing the sort of results that C1 seemed to produce straight away.
I just had to re-learn what to trust and how to make it work for me.
0
投稿コメントは受け付けていません。
コメント
6件のコメント