Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: davidgp on October 15, 2018, 09:36:33 am
-
Hi,
New version of Lightroom, still wondering why they even bother increasing the first number with this release: https://helpx.adobe.com/lightroom/help/whats-new.html
Regards,
David
-
good that you posted the topic. I was about to do so myself. It will be interesting to collect user experience here with this upgrade as it accumulates.
-
Yes, that it is a good idea, I'm leaving for a work meeting for the next days and I will probably no update until Friday, I will others have the pleasure to find if it has some critical bug :)
-
It's merely a rounding up. I'm sure there must be a reason for calling it 8.0, but don't imagine that I know what it may be, and I don't really consider it an upgrade in the way we've understood it before. In fact, you can open your 7.5 catalogue in 8.0 without any catalogue upgrade, and you can open the same catalogue again in 7.5 without any impact.
I scribbled more here (http://lightroomsolutions.com/lightroom-8-0/) but I have liked what they've recently done with LR Web (http://lightroomsolutions.com/lightroom-web-sharing-grows-up/).
-
There seems to be a new process version.
-
And that may explain the rounding up.
-
Does not appear that AutoTone was changed (different thread discussion)
-
I tried Auto Tone and I agree. No change yet
-
This happens so seldom. How does the process version change work? Does it automatically select 5 for new imports?
-
Doesn't let me sign in with the app. It's been annoyingly asking me to sign in almost every time I open it on desktop, phone, or tablet as of lately (upgrade to Mojave?). But now doesn't let me sign in at all... I even changed the password, at their request, still...
And it appears it is not because of the wrong password or that I initially forgot it. When I enter a wrong password, the message is different:
-
I have used this when having CC App issues but I don't want to be responsible for messing anyone up. You will have to re-install LR and PS. The catalogue was fine and pretests were all there. I did this about 2 weeks ago and had to fix my Topaz links and a few plugins in both LR and PS.
Read carefully and back everything up.
https://helpx.adobe.com/creative-cloud/kb/cc-cleaner-tool-installation-problems.html
-
You will be installing a new PS anyway. Todays updates come with PS 2019 (version 20) and plugins some of my plugins are missing.
-
If anyone is using Jeffrey Friedl's plug-ins there are updates for LR8.
-
Doesn't let me sign in with the app. It's been annoyingly asking me to sign in almost every time I open it on desktop, phone, or tablet as of lately (upgrade to Mojave?). But now doesn't let me sign in at all... I even changed the password, at their request, still...
And it appears it is not because of the wrong password or that I initially forgot it. When I enter a wrong password, the message is different:
Before uninstalling LR and ps, try uninstalling the cloud app (which you show) and reinstall it.
Can you sign on to adobe in the browser?
-
I upgraded to version 8.0 on Windows 10 desktop with no problems; via the Adobe Cloud app.
-
Before uninstalling LR and ps, try uninstalling the cloud app (which you show) and reinstall it.
Can you sign on to adobe in the browser?
The reason I used the cleaner is because the CC app on my iMac only kept telling me there was an update. When I tried to it just a at 0%. A re-install didn't work but it may for this situation.
-
I also upgraded without problems via the CC app. It seems a little bit snappier. The new HDR Pano feature is welcome (and it has worked well in an old problematic image of mine) but, yes, few new features for a new release.
-
I'll have to pay attention to the snappier part.
-
I'll have to pay attention to the snappier part.
Scrolling in Grid on this end (Mac OS) does seem snappier with far, far less gray preview thumbs.
-
Adobe Bridge seems minutely more responsive as well.
-
PSB Support? Higher file size limitations? Any news on these topics?
Sent from my iPhone using Tapatalk
-
PSB Support? Higher file size limitations? Any news on these topics?
Not that I've seen but that's a good reminder how long it's taking for something that seems simple and necessary (PSB support).
-
Tethering has been mildly updated, but it's still missing a critical feature for professionals which is to 'copy from last' or 'copy from primary' the develop settings to the new capture.
So ridiculous.
-
Tethering has been mildly updated, but it's still missing a critical feature for professionals which is to 'copy from last' or 'copy from primary' the develop settings to the new capture.
So ridiculous.
The 'Same as previous' function in the Develop drop-down setting of the tether task bar is of no help to you in that respect?
-
Before uninstalling LR and ps, try uninstalling the cloud app (which you show) and reinstall it...
Thanks for the tip, that worked. During the attempt to uninstall it, it offered the option to "repair" it first. I opted for that and it worked. Thanks again.
-
There seems to be a new process version.
I have upgraded it and found the latest process version does not stay. It goes back to v 4 even though I restart LR.
-
I have upgraded it and found the latest process version does not stay. It goes back to v 4 even though I restart LR.
Previously imported images will use the process version that was active when they were imported. Import some new files and you should see them come up using process version 5.
-
Yes. Any new files I have tried are set to 5. For previous files just set one to 5 and sync the rest.
-
I was not seeing the update on my laptop. Then I realized that you have to be running Windows 10 to get it. Fortunately, the update works fine on my Mac desktop where I do most of my editing.
-
I was not seeing the update on my laptop. Then I realized that you have to be running Windows 10 to get it. Fortunately, the update works fine on my Mac desktop where I do most of my editing.
Update does NOT support macOS 10.11 El Capitan or Windows 8.1.
-
Yes. Any new files I have tried are set to 5. For previous files just set one to 5 and sync the rest.
Actually once you create the preset go to the Library module, select all and apply it using quick develop.
-
The 'Same as previous' function in the Develop drop-down setting of the tether task bar is of no help to you in that respect?
Well I stand corrected! How long has this been there? I've been using Capture One to tether for too long and never saw this added to LR. Now all they need to do is support Sony A series cameras and I can use LR again to tether. Currently I tether using C1 when clients are in the room but process the files in LR after my shoots.
-
I can after using it since yesterday everything is faster.
-
Well I stand corrected! How long has this been there? I've been using Capture One to tether for too long and never saw this added to LR. Now all they need to do is support Sony A series cameras and I can use LR again to tether. Currently I tether using C1 when clients are in the room but process the files in LR after my shoots.
The are possible alternatives. In 2019, “CamRanger 2 will also support select Sony and Fujifilm cameras.” This could be combined with the “folder watch” function of LR or Jeffrey Friedl’s plug in. Actually, either of the “watch” functions could be used with C1 to get and process in LR
-
Well I stand corrected! How long has this been there?
Since near the very beginning of the tether feature in Lightroom ... at least as far back as v4, maybe earlier. I can't recall off the top of my head when it first came about ... though it seems I've been using it forever.
-
Actually, yes, I remember this has been there for a while now I think about it.
What I would actually benefit from is if the 'Same as Previous' option was available for auto import.
So people like me who have to use third party apps and a watched folder to use unsupported cameras can have the same functionality as tethered capture.
I sent in a feature request years ago but it hasn't been added as yet.
-
Big high ISO difference between Process Versions 4 and 5. ISO 32,000 and I only changed the version. 1st image is version 4. I didn't do any additional editing with the original.
-
Big high ISO difference between Process Versions 4 and 5. ISO 32,000 and I only changed the version. 1st image is version 4. I didn't do any additional editing with the original.
[/quote
Scary! Second image (v5?) looks very "agressive" to me!
-
So people like me who have to use third party apps and a watched folder to use unsupported cameras can have the same functionality as tethered capture.
Yes, but not with all the features of Lr-tether.
In Lr, if you select the AUTO IN "Destination" folder (sort Capture Time) and view the last photo in Loupe view (or with panels hidden Shift+Tab), any image you place in the "Watched" Folder from any source (3rd party tether) will 'pop-up' in the Loupe view. Try it by moving a file with file browser.
-
So people like me who have to use third party apps and a watched folder to use unsupported cameras can have the same functionality as tethered capture.
There's nothing to stop an industrious third party from offering a Lightroom plugin for tethering from your brand of camera ... that's how the first tethering option was offered, then Adobe added the feature themselves for the 2 major brands at the time.
It's all based upon the manufacturer's SDK for tethering ... does your camera maker offer such an SDK?
-
Big high ISO difference between Process Versions 4 and 5. ISO 32,000 and I only changed the version. 1st image is version 4. I didn't do any additional editing with the original.
[/quote
Scary! Second image (v5?) looks very "agressive" to me!
Describe aggressive.
-
The noise is harsh and more distinguished, i think...
-
Might be. Exports were from the same file. I really didn't look at that closely. i was interested to see if this update actually made that much of a difference. I don't often cop 100% for 32,000 ISO shot.
-
Might be. Exports were from the same file. I really didn't look at that closely. i was interested to see if this update actually made that much of a difference. I don't often cop 100% for 32,000 ISO shot.
It seems the only thing it does is it darkens the deepest shadows and removes the purple cast. In other words, it seems that the previous version tried too hard to open up areas that should have stayed black, resulting in a purple tint.
-
There was a thread at Fred Miranda about this. Canon vs LR. Canon kicked LR around. A welcome fix IMO.
-
Can you share the link, please?
-
Hi,
New version of Lightroom, still wondering why they even bother increasing the first number with this release: https://helpx.adobe.com/lightroom/help/whats-new.html
Regards,
David
This is a very fair question and one we've discussed internally quite a bit. The Lightroom products (Classic or CC) on desktop no longer include branding based on version number or year. It's just Lightroom CC or Lightroom Classic. This is not a new standard in modern software development. If you need to know the version number it's available in the About Box. You might need that to check camera support compatibility or if you call tech support to find out if a bug fix is available in version N.X.Y. From my perspective the most important number for our desktop products is the one to the right of the decimal place. ACR, LrCC and LrClassic will keep the decimal place in sync in order to give guidance on equivalent camera support. For example, 2.1 for LrCC, 11.1 for ACR and 8.1 for LrClassic will all have equivalent camera support. We could just keep moving the decimal up to .9 then roll the integer but rolling the integer once a year seems to make it more consistent and predictable. We've clearly moved away from the prior model of big version number updates that require an incremental upgrade payment to a model where we try to deliver value in every release. So that integer is merely "housekeeping" at this point.
Regards,
Tom Hogarty
Adobe Inc.
-
Can you share the link, please?
I'll try to find it.
-
Sorry. Must have been over a year ago. Archives only go back a year. Best I can do.
https://www.fredmiranda.com/forum/topic/1566626/#14633481
-
There's nothing to stop an industrious third party from offering a Lightroom plugin for tethering from your brand of camera ... that's how the first tethering option was offered, then Adobe added the feature themselves for the 2 major brands at the time.
It's all based upon the manufacturer's SDK for tethering ... does your camera maker offer such an SDK?
Yes, I think Sony have an SDK. They have a little app for tethering, and I know I could get pdseudo tethering by using an app in the background and LR's auto import. But 1, it's slower, and 2, you can't have 'same as previous' develop settings applied to new images as they are imported. You have to make a preset very time you change something minor then specify that to be applied on import. Very clunky and impractical.
-
Yes, I think Sony have an SDK. They have a little app for tethering, and I know I could get pdseudo tethering by using an app in the background and LR's auto import. But 1, it's slower, and 2, you can't have 'same as previous' develop settings applied to new images as they are imported. You have to make a preset very time you change something minor then specify that to be applied on import. Very clunky and impractical.
Have you tried this ...
http://dslrsoftware.com/tethered_shot.php (http://dslrsoftware.com/tethered_shot.php)
-
Have you tried this ...
http://dslrsoftware.com/tethered_shot.php (http://dslrsoftware.com/tethered_shot.php)
Thanks, this might be a solution. It seems a little out of date, with no mention of A7rIII or LR 8.0. I installed it but it doesn't seem to work - just says No Camera Detected. I have contacted the developer.
-
Sony tethers with full functionality and ease with C1 so it could and should work with LR.
-
Sony tethers with full functionality and ease with C1 so it could and should work with LR.
I wish.
Adobe only supports Canon and Nikon, and 3 Leica cameras. The connection is usually flaky (last time I owned a Canon) and there is no live video, so lots of reasons to use C1 instead for tethering.
However I'm so much faster processing a large number of files in LR and prefer the look. I will continue to tether in C1 and process in LR unless things change and Adobe wants to get serious about supporting the presumably small percentage of users who want professional level tethering.
-
However I'm so much faster processing a large number of files in LR and prefer the look. I will continue to tether in C1 and process in LR unless things change and Adobe wants to get serious about supporting the presumably small percentage of users who want professional level tethering.
That's what I usually do, and I feel you're right about the level of demand. C1 is very good at tethering, not least because it simply has to be strong in this niche.
-
My workflow exactly. Tether in Capture 1. Import into LR. The sessions in C1’s a very convenient envelope for a Reuter’s commercial shoot.
Personal work isn’t tethered and is processed in C1 rather than LR. Prefer the tools.
-
Sorry. Must have been over a year ago. Archives only go back a year. Best I can do.
https://www.fredmiranda.com/forum/topic/1566626/#14633481
Thank you anyway. :)
-
This is a very fair question and one we've discussed internally quite a bit. The Lightroom products (Classic or CC) on desktop no longer include branding based on version number or year. It's just Lightroom CC or Lightroom Classic. This is not a new standard in modern software development. If you need to know the version number it's available in the About Box. You might need that to check camera support compatibility or if you call tech support to find out if a bug fix is available in version N.X.Y. From my perspective the most important number for our desktop products is the one to the right of the decimal place. ACR, LrCC and LrClassic will keep the decimal place in sync in order to give guidance on equivalent camera support. For example, 2.1 for LrCC, 11.1 for ACR and 8.1 for LrClassic will all have equivalent camera support. We could just keep moving the decimal up to .9 then roll the integer but rolling the integer once a year seems to make it more consistent and predictable. We've clearly moved away from the prior model of big version number updates that require an incremental upgrade payment to a model where we try to deliver value in every release. So that integer is merely "housekeeping" at this point.
Regards,
Tom Hogarty
Adobe Inc.
Dear Tom Hogarty,
First, I was really surprised to see that you replied to my comment, many thanks for that :)
I still think it is quite important for the user to know which version is running. It is easier to understand why you have a functionality or not, but more important, to know if a version is going to have problems with some hardware, OS, printing process and report back to you (and by you I mean Adobe) or to discuss it here in the forums. After all, I'm quite sure you always try not to have new bugs or regression bugs in your software, but as a software developer myself, I know how difficult it can be.
Anyway, I get your point. You (Adobe) will release several versions of Lightroom Classic per year, some of them will have more "important", "more visual", "more eye attraction" updates, and other will be just minor new things (I suppose that depends in each user), bugfixes and camera and lens support. Not to expect because you increase the first number to have lots of new features like in the past.
Regards,
David
-
I still think it is quite important for the user to know which version is running
I agree. But as Tom points out, it's pretty easy to do so. With the 'About' screen for one. Now at least on the Mac, they could (could they?) make it easier using Get Info? This shown below isn't at all intuitive Tom.
The other guys? Easy.
-
Thanks Andrew. That's a good point. Just filed bugs against LrCC and LrClassic to get the version number added.
Regards,
Tom Hogarty
Adobe Inc.
-
Thanks Andrew. That's a good point. Just filed bugs against LrCC and LrClassic to get the version number added.
Regards,
Tom Hogarty
Adobe Inc.
I suppose maybe it really is, considering what Bridge and PS show (is PS really up to version 20? How time flies):
-
That's what I usually do, and I feel you're right about the level of demand. C1 is very good at tethering, not least because it simply has to be strong in this niche.
"C1 is very good at tethering, not least because it simply has to be strong in this niche."
I am not sure what this comment means? Does this suggest that it is inferior to LR/ACR at its other core feature e.g an application for processing raw digital files from digital cameras? That is a matter of opinion as far as I am concerned.
Processing of raw data from digital cameras has its benefits in that there are multiple applications that utilise different processes and "recipes" for producing the results that appeal to the user, there is no best, accurate, correct etc. In the film days you had the choice of the likes of Agfa, Kodak, Fujifilm, and many other brands.
-
Thanks Andrew. That's a good point. Just filed bugs against LrCC and LrClassic to get the version number added.
Regards,
Tom Hogarty
Adobe Inc.
Hi! Since you are here is it possible in the print module alongside the image cell dimensions to have also visible the paper size-dimensions? Now I have to open the printer properties to check what custom size of paper I printed onto. Thanks!
-
Tom any chance for PSB and larger file support? It’s getting really annoying and I don’t get why it’s not done already...
Sent from my iPhone using Tapatalk
-
Hi! Since you are here is it possible in the print module alongside the image cell dimensions to have also visible the paper size-dimensions? Now I have to open the printer properties to check what custom size of paper I printed onto. Thanks!
Can you not achieve this by simply having the rulers turned on?
Rand
-
Can you not achieve this by simply having the rulers turned on?
Rand
Sure but having something like "320 x 480 mm @ 251 ppi, paper size 432 x 520 mm" would be much simpler and faster to read.
-
Sure but having something like "320 x 480 mm @ 251 ppi, paper size 432 x 520 mm" would be much simpler and faster to read.
Rand, yes.
Panagiotis: Yes, you already have this. Turn on the print dimensions that appear in the upper left corner of the print in the Print Module, and turn off the choice of Resolution in the lower right panel, and you will get exactly what you are asking for. See illustration.
-
Mark thanks for your input! I was asking for the paper dimensions also after the image size and resolution information.
Rand, yes.
Panagiotis: Yes, you already have this. Turn on the print dimensions that appear in the upper left corner of the print in the Print Module, and turn off the choice of Resolution in the lower right panel, and you will get exactly what you are asking for. See illustration.
Sent from my Redmi 4X using Tapatalk
-
Mark thanks for your input! I was asking for the paper dimensions also after the image size and resolution information.
Sent from my Redmi 4X using Tapatalk
OK, but don't you now what paper size you are using without seeing this information presented? Can't do any harm of course to add it, but I'm not sure it would tell us anything we don't know already, perhaps thus creating unnecessary information?
-
OK, but don't you now what paper size you are using without seeing this information presented? Can't do any harm of course to add it, but I'm not sure it would tell us anything we don't know already, perhaps thus creating unnecessary information?
Hi Mark,
Suppose you have multiple (same model) printers, or one with multiple drawers, loaded with different sheet sizes?
Cheers,
Bart
-
Hi Mark,
Suppose you have multiple (same model) printers, or one with multiple drawers, loaded with different sheet sizes?
Cheers,
Bart
I hear you, but I have a hard time imagining that one would not know what paper size one is working with at any one moment when the application is being called upon to make a print.
-
When I reprint a photograph I go to the print collection I select it and click on the small arrow to open the print. Now the only thing I need to know before I hit the print button is what paper size (most of the times is a custom size) I have to load in the printer. Currently to do this I open the printer properties to read the exact size because I found difficult to accurately read the rulers.
OK, but don't you now what paper size you are using without seeing this information presented? Can't do any harm of course to add it, but I'm not sure it would tell us anything we don't know already, perhaps thus creating unnecessary information?
Sent from my Redmi 4X using Tapatalk
-
When I reprint a photograph I go to the print collection I select it and click on the small arrow to open the print. Now the only thing I need to know before I hit the print button is what paper size (most of the times is a custom size) I have to load in the printer. Currently to do this I open the printer properties to read the exact size because I found difficult to accurately read the rulers.
Sent from my Redmi 4X using Tapatalk
OK, that makes sense now. Thanks.
-
OK, that makes sense now. Thanks.
Mark something like this (I made it in PS :) )
-
Lr Splash screen - Version # easy to spot:
(http://i63.tinypic.com/294i1yx.jpg)
-
Mark something like this (I made it in PS :) )
They should be able to do that. For the situation you mention it's useful. Why not post it to Adobe as a feature request?
-
You are right, I will do that.
They should be able to do that. For the situation you mention it's useful. Why not post it to Adobe as a feature request?
Sent from my Redmi 4X using Tapatalk
-
I hope this isn't something super obvious that I'm missing BUT I can't seem to open my images in Photoshop since the upgrade. When I select open PSD as smart object, I just get a page of thumb nails of my past work. What am I doing wrong?
-
There is a PS icon on the top bar. Click on that.
-
Hi! Since you are here is it possible in the print module alongside the image cell dimensions to have also visible the paper size-dimensions?
Has nobody mentioned Information on the top left of the print window? Keyboard
It is not "alongside" cell dimensions but rather obvious.
-
There is a PS icon on the top bar. Click on that.
Thanks!
-
Has nobody mentioned Information on the top left of the print window? Keyboard
It is not "alongside" cell dimensions but rather obvious.
Not "rather obvious" to me - in fact non-existent in Lr 7.1 for OSX. The command does nothing here.
-
When I construct my Print module presets, they are by:
- Printer
- Paper / ICC
- Paper size
- Image quality / paper thickness settings, etc. in the driver (some even for ABW)
- And typically with 1/4” borders as starting place, with image cell just slightly smaller than that
As a practical matter, after I’ve soft-proofed I simply go to “Print” select the preset that corresponds to the paper I’ve soft-proofed to, and paper size I desire. One button. I have the presets w/ the image resolution box unchecked so that the first thing I see is the native resolution at the image size (per Mark’s illustration of the upper left of the image window). Then I check the resolution box and adjust to either 360 or 720 per Jeff Schewe’s recommendations for my Epson printers. Other than that I only have to assure that the rendering intent chosen during soft-proof is properly selected in the Print module.
So, bottom line for me is that paper size is something I already have designed into my flow - including many “user defined” sizes “which size” is indicated in the name of the preset. E.g. a preset name will look something like “5000 IGFS 17x25 L ARP.” Signifying: Epson SCP 5000, Ilford Gold Fibre Silk, 17x25” sheet in Landscape orientation, with Andrew Rodney custom ICC profile.” This makes for lots of presets, but they are easy to build after the first one for any given printer/paper/ICC has been built. I have them organized by my favorite paper types. Drop downs give me by printer and paper size.
Rand
-
Has nobody mentioned Information on the top left of the print window? Keyboard
It is not "alongside" cell dimensions but rather obvious.
The image information overlay, which is invoked by pressing the "I" button, only shows standard paper sizes not Custom.
After Mark Segal recommendation I posted this request as a possible "idea" in the Adobe LR Classic feedback forum.
An Adobe employee (which is a lead software engineer I believe) responded and said that they will look into this with her team! Link to thread:
=19815836#reply_19815836]https://feedback.photoshop.com/photoshop_family/topics/custom-paper-size-dimensions-in-print-module?utm_source=notification&utm_medium=email&utm_campaign=new_reply&utm_content=reply_button&reply[id]=19815836#reply_19815836 (https://feedback.photoshop.com/photoshop_family/topics/custom-paper-size-dimensions-in-print-module?utm_source=notification&utm_medium=email&utm_campaign=new_reply&utm_content=reply_button&reply[id)
-
Good feedback. Let us now see whether they do it.
As I mentioned, when I activate that info command I get nothing (Lr 7.1 on OSX).