'This forum was intended to be the continuation of the tough conversations we as a community have been having about topics that impact people's sense of safety and well-being,' said a Duluth police news release. 'We acknowledge police don't have all the answers, which is why community engagement is essential to this process.' The Duluth police, in partnership with the FBI, U.S. Attorney's Office, state Bureau of Criminal Apprehension, St. Louis County Sheriff's Office and Superior Police Department, had planned to host the 'Use of Force in Minnesota' forum — subtitled, 'a dialogue between law enforcement and communities of inclusion' — and said it invited more than 100 community members, including members of the NAACP. The police say they increased invitations to the event from the 30 members invited to similar engagements around the state. 'Even in doubling this invite, we knew there would be more interest than space,' the police said.

'Friday was not intended to be the end of the conversation, but rather a continuation.' The president of the local NAACP, Stephan Witherspoon, seemed to appreciate the decision. He released a statement, saying, 'We commend the DPD for postponing the meeting for transparency sake. The NAACP will continue to work with the DPD in addressing and taking action on the policing issues that heavily impact the African American community and the community at large. We will work together to get the results we desire.'

In calling for the postponement of the forum, versions of which had previously been held in St. Cloud and Rochester, the Duluth NAACP concluded the event was flawed for not bringing in outside groups during the planning process. 'We feel that any law enforcement policies, trainings or meetings that directly impact our safety, particularly policies and practices regarding use of force, should have ample community input, which this meeting lacks,' an NAACP news release said. The NAACP acknowledged 'recent efforts (by law enforcement) to increase community outreach.' But the NAACP also drew on the roiling national conversation about use of force by law enforcement. The tense national conversation has best been illustrated by players kneeling in the NFL during the pregame playing of the national anthem.

The protesting players say they're objecting to the disproportionate targeting of black people by police. 'People of color have been surveilled, profiled, controlled, threatened and killed by the police since the days of slavery,' the NAACP said. The Duluth police will reschedule the event shortly, they said, and 'invite members of the NAACP and other communities of inclusions to help us plan the next event.' Witherspoon said the NAACP will participate in the planning of the rescheduled event. 'The NAACP will be at the table when planning a symposium for this dialogue,' he said.

In objecting to the now canceled event, the NAACP also brought up the Duluth Police Department's intention to purchase protective gear — a measure it put on hold last December after community groups objected to what can also be referred to as 'riot gear.' 'We believe the Duluth Police Department's request for riot gear will only erode public trust,' the NAACP news release said, harkening to the 2014 unrest between a predominantly black community and armored police in Ferguson, Mo. 'We have seen the devastating impact an overly-militarized police force has on communities of color.' The police did not address the protective gear in canceling the event. At last report, the police were meeting regularly with community groups before moving forward with their request for $125,000 in protective gear.

Lightroom 5.6 is now available as a final release on Adobe.com and through the update mechanism in Lightroom 5. The goal of this release is to provide support for additional camera raw support, lens profile support and address bugs that were introduced in previous releases of Lightroom. I have same problem on a brand new iMac 27″ with 3.5GHz, 32GB RAM, 512 flash disk, GTX780M.

Adjustment brush is like dodging in PS v1.0 (NOT CS) when computers had less disk-space than we have cpu-cache today. Changing from “current” raw file to next could take between 1-5 seconds, even if 1:1 and standard size previews is built! The Raid-5 disk has stopped spinning before image turn up on monitor!!!! Culling down images takes forever, and I’m just hours away from installing LR 3.6 and CS6 and getting off the cloud!

Generally slow LR performance on OS X Maverics compared to Win7 (my other workstation). Which has less hardware than iMac.

I’m now working from same disk as before, Raid-5 USB-3. I have tried reinstalling LR. I have tried removing LR preferences. I have reinstalled Mavericks. I have fixed permissions. I have followed Adobe’s tips (the huge list).

For Mac Ver5 Adobe Community Center

I’ve also diagnosed the iMac with checkdisk, memcheck, logs, etc It’s either Adobe, Windows or Apple’s fault this Making software or operating system which is compatible with each other is not easy, apparently! I don’t like Adobes approchement either, adding fancy selling features (SH.T) is more important than making software work like it should. That´s´s just more BS. Adobe has added features in point releases before. New Features in Lightroom 5.2 ◾A Smoothness adjustment slider has been added to the Detail Panel under Color Noise Reduction.

This helps to reduce low-frequency color mottling artifacts ◾Refinements to the Spot Healing Tool: ◾New Feather control ◾Auto find source method now works better for images with textured areas like rocks, bark, and foliage ◾Auto find source method now prefers source areas within the crop rectangle ◾Auto Exposure has been improved to be more consistent across images and across different image sizes. ◾Smart Preview size has been updated to 2560 pixels on the long edge. ◾Refinements to the Local Adjustment Brush: ◾Right Click (PC) / Control-click (Mac) on a brush adjustment pin to bring up a context menu to duplicate or delete ◾Control+Alt+Drag (PC) / Command+Option+Drag (Mac) on a brush adjustment pin to clone (duplicate) that adjustment. Well it´s just BS. Just look ate past releases.

Of course they have added new features. For example 5.2: New Features in Lightroom 5.2 ◾A Smoothness adjustment slider has been added to the Detail Panel under Color Noise Reduction. This helps to reduce low-frequency color mottling artifacts ◾Refinements to the Spot Healing Tool: ◾New Feather control ◾Auto find source method now works better for images with textured areas like rocks, bark, and foliage ◾Auto find source method now prefers source areas within the crop rectangle ◾Auto Exposure has been improved to be more consistent across images and across different image sizes.

◾Smart Preview size has been updated to 2560 pixels on the long edge. ◾Refinements to the Local Adjustment Brush: ◾Right Click (PC) / Control-click (Mac) on a brush adjustment pin to bring up a context menu to duplicate or delete ◾Control+Alt+Drag (PC) / Command+Option+Drag (Mac) on a brush adjustment pin to clone (duplicate) that adjustment. Something is amiss with the update process. From within LR, Check for Updates tells me there is an update available and when I choose “Download”, I get a message saying “To update to the latest version of Lightroom for use with your Creative Cloud membership, please quit Lightroom, launch the Creative Cloud app, and click the “Install” button next to Lightroom 5.” I’ve quit and relaunched the CC app as well as signing out and back in.

LR only shows as available to Install in the Find New Apps section. It does not appear as an installed app in the first section as it used to do.

Something has changed since the last update. After talking to Creative Cloud Support, I’ve got this resolved and will post in case it helps others with the same problem. Evidently, the CC app was not offering me the update to LR 5.6 because the LR version I had installed was the perpetually licensed version of LR 5.5. Because I also have the Photographer’s CC Plan, I needed to install LR from within the CC app before I could update to 5.6.

I’m not sure why it is like this since folks who do NOT have the CC could update their perpetually licensed versions of LR to 5.6. Seems kind of screwball that because I have the Photographer’s CC I need to use LR within the CC even if I have a perpetually licensed version.