Lightroom Classic 7.3 is released today. You will start getting the Update notification soon.
Here is a comprehensive list of major updates went in:
Adobe Lightroom Classic allows you to choose a camera profile option. A camera profile determines the color treatment applied to a raw image after it’s imported into Lightroom. It ensures that all images taken with the same settings look similarly in Lightroom. The default profile used to be Adobe Standard. From Lightroom 7.3 on wards, Adobe Color is going to be the default camera profile.
Adobe Color profile is more contrasty and saturated compared with Adobe Standard.
You are provided with the following profiles as a drop-down list:
These profiles have been moved to a much prominent place in the Basic panel of the Development module.
In addition, you are provided with a set of following Creative Profiles.
These profiles help you to apply a certain style to your photo effortlessly. Applying a creative profile will not update the changes you already applied to an image. In addition, it also provides with an amount slider to change the intensity of the applied profile. Select the Browse button, shown in the previous image, to see the creative profiles.
Import grid performance
On Windows machines, when you connect to a mobile phone (Android / iPhone) and then open the Import window, the images should appear faster. Previously, Lightroom Classic used to display all the images at a time, after the image scanning is complete. In the latest version, 7.3, it displays images in batch wise.
The underlying face detection engine is changed resulting better face detection and face recognition. Now, you can regenerate faces using the Library > Find Faces Again option at any point in time.
The Dehaze slider location
The Dehaze slider is moved to the Basic panel as per your request.
Bigger tone curve Updated the Facebook API that uses for authentication in Facebook plugin. As a part of this change, you won’t be able to add a comment to a photo from Lightroom Classic. Bug Fixes
In the Filename Template Editor, when you insert a token as shown below, it always used to go to the end of the tokens string. Lightroom Classic 7.3 fixes the issue.
This version also fixes an issue on Mac that the Import window doesn’t appear after connecting an SD card while Lightroom is running.
Lightroom Classic 7.2 is released today. Let me introduce some of the changes went in:
In the past, many users have reported that Lightroom becomes slower after a prolonged usage. This issue should have been fixed with this version. Also, resource-intensive activities, such as export, import, preview generation, and HD/panorama merge should be faster if your machine has 12 GM or more RAM.
We, specifically, have implemented changes related to Threading Building Blocks (TBB). This should be effective on machines with 12 GB or more RAM.
You can search for folders.
You can also mark some folders as favorite. And, easily filter them out.
Note that if you select multiple folders and mark them as favorite as a group, you need to unmark them favorite as a group itself. If you don’t remember the folders that you marked favorite as a group, see the same from filmstrip panel.
There are some known issues with this feature:
When you clear the Search field after a search, Lightroom Classic re-calculates the image number; it takes some time to display the image numbers.
At a time, the drives names disappear following a search for a short duration of time.
Sort edited and unedited images
Create collection or collection set quickly
You can create collection or collection set quickly from folders.
If the folder has sub folders, the Create Collection option appears in the context menu. The directory structure is retained while creating the collection set, with all parent directories are retained as collection set.
Lightroom Classic 2018 introduces the embedded preview workflow that helps you to reduce the time to select the right images for developing (culling). While importing the images, select the Embedded and Sidecar option for building the previews.
When you import an image into Lightroom, it creates various previews for you. By default, Lightroom creates a minimal preview, which is the thumbnail that you see in the Library grid view. When you move to the Loupe view, it generates the standard preview. Further, when you zoom the image, it generates the 1:1 preview on the fly. These previews are different from the camera-generated previews. Since Lightroom needs to create these previews, when you navigate through many images in the Loupe view, you see the loading bezel. In other words, images take time to load. One way to overcome this issue is to create standard or 1:1 previews while importing itself; however, this process takes more time, since Lightroom builds previews.
The new feature helps you to overcome both these issues to certain extent. In this workflow, Lightroom, instead of creating its own previews, reads and makes use of the embedded previews in the Library module. This process takes less time in most of the computers.
Embedded preview is a camera preview, which is created by the camera, and is available with the raw image. Latest Nikon and Canon cameras have full size embedded previews. Means, the camera-generated embedded previews can be used for culling. Sony, Olympus, and Fuji cameras don’t have full sized embedded previews. In this case, Lightroom checks if the embedded preview size is 50% of that of the raw image. If not, the standard preview is created instead of reading the embedded preview. Create a jpg sidecar image along with the raw. If the image has the sidecar file, it’s being read for creating the preview in the Library module.
While the importing is in progress, you can start culling, since Lightroom would be responsive while embedded preview is being read, than standard preview is created. Similarly, if you import images into multiple folders, the embedded preview generation is prioritized based on the folder you view. Embedded previews are available only in the Library module. After the culling, when you move to the Develop module, after edit, the standard preview is created. Means, you start seeing the Lightroom preview.
Images with embedded previews are marked by a symbol in both Library and Loupe views. Click it if you wish to convert an embedded preview into standard preview.
There is an option provided in Preferences’ General tab that converts the embedded previews into standard previews when your system is idle.
We hope you will enjoy the new culling experience.
Some of the caveats:
Generating embedded preview, if you convert the raw files into DNGs, may not be a great idea.
If you apply a Develop preset, while importing, you may see two different previews. Library preview won’t have the Develop preset you applied. The preview gets updated after you make a change in the Develop module.
Performance can vary based on the machine configurations.
We will wait for you feedback to improve this further. Thanks for your feedback!!
This is my first post in this year. With my last post, I have completed second series of video tutorials that covers some of the main concepts in AEM development. We didn’t do anything complex; however, it will help you to get a quick start.
If you are learning, see my blog too. It has the transcripts available. Also, you could see the correct order in which you need to progress. The exercise files are available in my GitHub account.
Happy New Year and Happy Learning!!
In this post, we will see how to implement a workflow using AEM. As the name suggests, a workflow represents a step-by-step process to accomplish a common task. For example, author creates the content. Then, the content goes to an editor for approval. After the approval, the content can be published. As usual, we will see a simple implementation.
In this session, we will see how to create a custom event and manage it. A custom event helps you to manage a specific activity happened on an AEM instance. For example, you want to send an e-mail to an editor as soon as an AEM page is created by a content creator; so that the editor is aware that the page needs to be edited at a later stage.
Let us start. We will create a new AEM component for creating a custom event.
Inside com.aemcompany.myproject.impl, create a new class EventManagerImpl.java.
Note that the class is extended by EventListener interface that provides you the methods to manage the event.
In the last session, we have seen how to add a property to a JCR node. We primarily created a resourceResolver object and created a resource using the path to the node where we wanted to set the property. Converted the resource into a Node using the adptTo() method. And, then used the setProperty() method to set the property. Finally, we created a session object in the similar manner, and then saved the property.
In this session, we will see how to perform a basic search option. There are many ways to accomplish the same. We will see the simplest way. The intention is to be cognizant of how a search operation is performed. In the repository, we will search for the page that contains a property author which is set to Sunil.
Go to the SearchService.java interface and add the following method:
public String getResult();
In the SearchServiceImpl class, create a Resource Resolver. We have discussed this in length in of the previous sessions.
Map<String, Object> param = new HashMap<String, Object>();
resourceResolver = resolverFactory.getServiceResourceResolver(param);
In the previous session, we have seen how to obtain a Resource. We later, translated the Resource into a Page object, and then programmatically obtained its title. We will see one more example. Here, using an AEM bundle, we will write a property to the Page we created. In this case too, we need to use a Resource object to obtain a Session object using which we can save what we write.
Let us start:
Create a new interface: SearchService.java.
(There is a reason for using this name. In the next session, we are going to discuss about searching.)
Add the following method.
public void addProperty();.
Create the implementation class: SearchServiceImpl.java
Implement the addProperty() method.
Get the ResourceResolver.
(Visit the previous post to see what the code accomplishes.)
In this session, we will learn about how to access resources using bundles deployed in the Felix console. After all, for Sling, everything is a resource. We will update the bundle we developed with a method that accesses a node and prints its title. Though it sounds very simple, we will learn about a very important interface ResourceResolverFactory, that helps us to get ResourveResolver. ResourceResolver gets the Resource object that provides the functionalities to manipulate the nodes and its properties. We will also learn about the adptTo() method that helps to translate an object into a different object type.
So, let us start:
Add the following method in HelloService interface:
public String getPageTitle();
Add the following ResourceResolveFactory reference:@Reference ResourceResolverFactory resolverFactory;
Implement the getPageTitle() method.
Create a hashmap object with a string & object combination as shown below:
Map<String, Object> param = new HashMap<String, Object>();
Put ResourceResolverFactory.SUBSERVICE and the service associated to the HashMap object.
As I mentioned earlier, for Sling, everything is a resource. Generally, you use Sling APIs for doing any content manipulation. Getting a ResourceResolver object is imperative for accessing the Nodes in Oak, and later doing various operations, such as Create, Read, Update, and Delete (CRUD). You can compare it to creating a connection object in Java to a database.
Now create a resource object using the getResource() method with a path to the company page as argument.
Translate the resource into a Page object using the adaptTo() class.
Page myPage = pageResource.adaptTo(Page.class);
Note that the method takes the class name to which we want to translate the resource as an argument. We do this operation to avail various APIs associated with various objects, such as Node, Page, and so on. In this case, we use the getTitle() method in the Page object. This can throw a null or Login Failed exception, and that’s the reason we added a try catch block.
Use the following Page method to get the resource title.
String title = myPage.getTitle();
Update the bundle service component
Update the bundleservice page, so that we can test if the bundle returns the value.
Login to CRXDE LIte.
Update the bundleservice page.
Create a service user mapper
Login to System console.
In OSGI Configuration, search for Apache Sling Service User Mapper Service.
The first part is the bundle name. Second part is the service name that we used in the method. (Step: 5) Third part is the system user who can access the service.
We are yet to create the system user. Let us do that.
Create a system user and provide access rights
Login to CRX Explorer.
Select User Administration > Create System User.
Enter user ID.
Select Yes for creation.
Provide access to the user to avail the paths.
Search for the user. (myUser)
Provide full access to the content path.
Then, Save the user.
Test the component
Access the page we created.
Note that it displays AEM Company, the title of the node.