P: Allow Crop Settings in Presets

Hi,

If I set a certain crop ratio in Camera Raw, I would like to save (just) this as a custom preset in Camera Raw, which I could easily apply to many photos at once. 

A couple of times I tried to figure this out in Camera Raw, but it's not possible to save this crop aspect ratio as a custom preset. Aspect ratio is not available to check when saving a new preset. Why?

I can actually save the crop ratio as a personal setting (in Camera Raw clicking on the three dots and 'Save settings'), but this wont appear in the list of presets in Camera Raw.

I work with a Nikon Z6 which (strangely) saves images 6048x4024 pixels, which in fact is not an exact 3:2 aspect ratio. For my workflow I prefer my images to have a standard 3:2 aspect ratio, and it would be truly helpful if I could instantly apply a custom crop preset to all my photos in Adobe Bridge before editing them in Camera Raw.

Hey mikas93267824. I agree totally with you and wish they provided the option to set crop presets. 

[abusive language removed by moderators]

I’m not exactly sure what you are asking.

For you to read, and accept how this works! 

So simple, so factual: 

https://community.adobe.com/t5/lightroom-classic-ideas/how-do-i-write-a-feature-request/idi-p/12386378

After all, I’m not Adobe developer

I am.

And yes, plugins might offer one solution, but unfortunately I don’t think they work in mobile version or do they? And as I do some editing on the road, this feature would be especially useful in mobile, when the cropping manually isn’t that intuitive and fast. So I would need a solution that is compatible both on mobile and desktop.

To make things clear I answer once more.

I’m not exactly sure what you are asking. How am I supposed to know what software/IDE Adobe developers use? Or do you mean what languages I’ve been using?  To my understanding first version of Photoshop was written in Pascal but nowadays it’s C++.

In case you are interested, in high school the first language I came to use was actually Pascal. But mostly I’ve been using C/C++, Java and Python. A little bit PHP and even assembly and so on. I’ve been working with interfaces like OpenGL and DirectX. And IDEs like Visual Studio. With Unity3D I was programming with C Sharp. Krpano uses XML but they have their own scripting language to make actions. Now with 3DVista JavaScript is what should be used to create custom functions in virtual tours.

But I’m not sure how this is relevant. I didn’t say I was a master programmer or specialised to programming features to Photoshop. How could I be? After all, I’m not Adobe developer. But even if syntax, IDE and the level at which you work may differ a lot, the basic principles in programming are the same. Based on my own experience it takes most time to create the functionality, developing algorithms, AI etc. Read and write operations and adding a checkbox to GUI are usually simple basic tasks and it doesn’t depend that much on what kind of software you are developing. When Adobe has great developers doing amazing and advanced complicated things, I can’t see how these simple tasks would take much effort from them.

But now you are providing me some information that helps me to understand how things work with Adobe, thank you. I didn’t know it all depends on requests and upvotes. I thought the votes were more like directional and guidelines. I'm not sure if many people just wandering here from a google search realizes voting is so important and takes time to do it. There was already Adobe employee here asking how people would wish this feature to work. So I thought the votes were not that important at all and Adobe was already advancing/considering this to be implemented. That’s why I was surprised nothing has happened in years.

Recently Adobe regrouped the settings in Copy, Sync and Preset windows. Some people it may disturb but I think it’s clearer now. They had been the same way as long as I remember. So apparently Adobe can change things that have been in the same way for a long time. And I don’t know if there was a request and votes for that change but I thought Adobe was capable to improve their software on their own and not everything depends on votes. It would have been a perfect opportunity to add the Crop there also.

In my view the simplest solution would be that Copy, Sync and Preset were working exactly same way offering the same options. For some reason Adobe has left out Crop and Spot removal settings from Preset. To me that seems like crippling their software. Sure in most cases it’s not a good idea to have spot removal in a preset. Even if you have the same spot in every image, you may need to adjust the source differently. But sometimes that could be very useful also. So why not let users decide if they want to use those settings or not? Now it feels like Adobe giving impression they know better than their customers what their customers want to do.

I have a degree in information technology and my specialisation was software engineering.

What software for the Adobe/Photoshop/Imaging ecosystem have you developed? Do you have any such "specialisation" in that task? 

Perhaps you can engineer a plug-in as others have done to accomplish your goals:

https://johnrellis.com/lightroom/allplugins.htm

Do you understand how feature requests from outside Adobe pre-release work in this forum? They are viewed via the number of upvotes (and the time it takes for them to populate). This request was made in 2011 and there are currently 47 votes. Those are facts, sir. Did you upvote, did you get your friends who subscribe to do the same? Do you accept that a feature you may desire with 47 others that aren't implemented isn't a bug? 

I don't expect answers, but it would be useful if you examine how this all works and accept the current outcome based on the facts and history of this request.

To answer your specific question posted here, YES, and the explanation has been provided multiple times since:  Community Beginner , May 07, 2022:

I have a degree in information technology and my specialisation was software engineering. It is true that I haven’t worked for big companies and nowadays I’m much more interested about photography and media stuff and haven’t done that much developing. But when I do 360 and build virtual tours which are my main interest these days, I still need to do some coding myself, especially when I’m doing a game based on virtual tours. So I would say I have some experience and at least a good understanding about developing a software.

That’s the reason I’m always more interested discussing and hearing about details and why some decisions were made than just simple answers that “it’s not done because it’s decided so and it has to be a good decision because it’s always been like that”.

I’m sorry if I was a little grumpy. It just irritates when someone answers to me telling only self-evident things as I was stupid and wouldn’t be able to understand anything more detailed. Sure I don’t expect those detailed answers from another users but I was thinking there would be Adobe’s employees here also to enlighten things even a little. For me it’s been very difficult to ever get any comment from Adobe to my concerns.

And it always frustrates when with a very little effort something could be made to be easier and faster. But often people spend more time discussing should it be done or not if enough people don’t benefit while it would probably take less time just doing it.

This is how I think and what motivates me as a programmer also: if there is even a small thing that is boring and takes unnecessary time doing it manually again and again, I try to automate it so that I can spend time doing something more interesting. That’s why I use a lot presets and droplets etc. and would hope that there are minimal restrictions with them to be able to use them more effectively.

If I’m wrong and it would be a huge task to make this little tweak, I would be happy to hear it. But I understand if no one here is interested about discussing this and apparently then people don’t care this feature. So I rest my case and won’t bother anymore.

There seems to be strong opinions about how software should be developed, by people (AFAIK) having no experience developing software. 
Lots of guessing and assumptions with far few upvotes!

Hmm, I’m not sure if there was a bug (and this time I mean a real bug) in this forum as I think my last answer got lost. Sorry if this comes multiple times.

Thank you for your time and effort for providing me the answers. Unfortunately, those answers are self-evident and hardly provide any information I was asking for.

Yes, it is a design decision or design flaw. I was asking why on earth that kind of decision/flaw was made. And the answer shouldn’t be “because Adobe just made it and can’t make no mistakes ever”. Sure they can do or not do whatever they want with their products but that doesn’t mean they are above criticism if their decision seems weird/bad.

Ok, not enough votes here. But is Adobe unable to correct bad decisions on it’s own if people don’t vote here and how much votes are needed?

There was Adobe Employee commenting in this thread and asking additional questions how would people expect this functionality to behave. As if you would expect a company that cares it’s customers to do and this was going to progress. So didn’t it already got “the eyes of Adobe”? Or at least one employee. Couldn’t that employee distribute it to the eyes of the other employees if it didn’t got their eyes yet?

I understand that if this was a request that demanded months of work and effort from several developers, Adobe is not going to do it because of a small amount of users. But after all we are talking about only a minor tweak. Very simple task any developer can do in a moment. I guess over the years Adobe has been doing some minor tweaks to their software alongside bigger major updates to improve usability even if people hadn’t voted and requested all of them and not every single user benefits from every tweak. That’s what innovative companies do. So why would this feature/fix be so bad thing? Almost seems like it’s principled and stubborn decision. Does it break something if implemented?

But I guess enough of this if this doesn’t interest anyone else. I don’t need to be underestimated by having the same answer spammed again and again. So let's move on and have a nice day.

I provided the answers: it's a design decision for 11 years +. And, for 11 years here,  there is a grand total of 47 upvotes. That are two big reasons it's not being addressed. Upvotes get the eyes of Adobe.