GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Since nobody has responded about the article I linked regarding making GIMP behave more like Photoshop, and since I think it applies to most software let me expand on that specifically now.
When a clone or near clone is coded it is common to make it appear as different as possible to avoid claims, even litigation, for piracy. Consider that GNU is an acronym for "Gnu Not Unix" and WINE, "Wine Is Not Emulation". Regardless of whether we conclude that this is good or bad, it is fact that developers work to avoid too deep of an association and possible prosecution. One of the ways this is done, besides just the name, is by using different keystroke shortcuts and a selection of formats. Any decent software that doesn't attempt to be proprietary embraces some sort of universal or raw format and keystrokes can be re-assigned. Don't forget that in the beginning General Motors in it's fight to grab a piece of the Ford pie fostered a joke advertising campaign simply saying "Ours isn't black!"
Anecdotally all I can offer is that over time every single application, driver or whatever form of monolithic code that I thought kept me shackled to Windows has had a workable Linux substitute. I don't work professionally with Graphics so maybe I'm mistaken in this comparison but the hardest transition for me has been that I do semi-profesional audio recording and editing. Mt PC is a DAW and that seems to me more timing critical and complicated than manipulating graphics and it took a long time to mature in Linux but it has.
That said, in my field, some bands won't even consider hiring you if you don't have/use ProTools even if that is the sum total of what they think they know about modern recording. So I keep a ProTools machine and do a side-by-side and let them choose. Granted a few still insist on ProTools but most go with what sounds the best and the timing is just smoother and tighter in Linux so they go for Linux. A few even love the idea of being a little more Hi Tech and geeky and a little bit unique. It seems to balance out rather nicely and over the past 3 years, the need for side-by-side has diminished because word of mouth has done more than advertise "Me Too". It's worthy of note that not too many years ago in media recording/editing if it wasn't done on a Mac, it was "no go". Things change.
Thanks for the good tutorial, but I am not bound to PS as much as I am to ACR and I can't work with LR because it won't be that good as ACR, IMHO. What I need is a handy RAW developer, with the power of automatic treatments done by ACR. The shortcuts were never my issue. But I might have a question: in how many ways you can write a "for" loop to avoid breaking copyrights? Now, seriously, where can I find such simple and powerful panorama tool as in ACR/PS?
Last edited by msdobrescu; 08-22-2018 at 11:38 AM.
Addendum. Regarding RawTherapee, it is a great tool for me now. WHy I have had issues with it in the past? One reason only: I was not aware of a major requisite - the dual illuminant DCP profiles. It had none for my camera and I did not know that. Now, somebody added it. This should be advertised more. Now, RT performs closely to ACR in auto levels for me. So, in order to get the best experience with RT, if the profile is missing for that camera, must get a colour table card and take the shots as RT creators request it and send those to them. More, read here, on RT's forum: https://discuss.pixls.us/t/first-tim...reatment/10992.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.