Adobe Community : All Content - All Communities

NIK HDR Efex Pro 2 anomaly with Photoshop CC

forums_noreply@adobe.com — Tue, 17 Jun 2014 01:30:34 GMT

Every time I use HDR Efex Pro 2 to create a HDR when I return to Photoshop CC the preview in brush size/hardness is missing.

To recreate the error, execute Photoshop CC, open 5 files to create a HDR. Select one of the files and while pressing Control and Option click and drag on the image. Notice that the brush outline also displays a pattern, default is red, showing the brush area.

Execute HDR Efex from Photoshop CC, create the HDR, select vignette from the Landscape set of presets. Return to Photoshop CC. Select any brush and while pressing Control and Option click and drag on the image. Notice that the brush outline shows but the brush pattern is no longer presented.

The only way I've found to restore the pattern is to either delete the Photoshop CC presets or copy a good preset file over the faulty one.

Anyone have an idea on how to fix this problem without copying a file? I've already reported this to Google, but haven't received an answer from them yet.

LR 5.4 Develop Full screen glitch.

forums_noreply@adobe.com — Sun, 11 May 2014 00:02:30 GMT

This is a minor issue for me. So minor that I've never experienced it before today. I did a bit of searching but didn't find a reference to this particular problem...

This glitch is very apparent if the image is displayed 1:1 so assume that for all of the following. If I first display an image in the Library and then switch to develop there are no differences between the full screen view "F" and the normal view except for the amount of the image shown. If I have not visited the library module to view a particular image since the last time I started LR the image in full screen mode is slightly blurry, just as if the focus was off. Switch back to normal view by again pressing "F" and the picture is in focus.

I have found a way to observe the glitch 100% of the time on my system. Here is the procedure:

1. In the Develop module display any image. Select 1:1 display mode. Exit Lightroom.

2. Restart LR. The image will still be 1:1. Press the F key. The display will switch to full screen mode and the image will be blurry when compared to the normal view. Repeatedly pressing F goes from the normal view with the image in focus to the full screen mode with the image not in focus.

3. From the normal window select the library module. Reselect the Develop module. Toggling to full screen will now show the same image as in the normal window, i.e. both in focus.

Is this a known glitch--one I just wasn't successful in locating during my searches?

My system:

27" late 2012 iMac; 3TB Fusion Drive' 32GB DRAM; 3.4 GHz i7 CPU. OS X 10.9.2

Display 'flashes', edits lost -- UPDATE

forums_noreply@adobe.com — Sat, 28 May 2011 21:34:52 GMT

Original thread: http://forums.adobe.com/thread/856834?tstart=0

I have now tracked down the cause of the flashes and they are definitely caused by using the Nik software directly from Lightroom.

If I send a dng image to Photoshop using LR external edit, modify the image in Photoshop using the Nik plugin(s), and then return it to LR by saving it in Photoshop everything is OK.

If I send the photo to Nik directly from Lightroom then the flashes and other problems appear. It is apparently tied to images sent through the Nik software directly from LR. I can manipulate any image not sent to the Nik software from LR without difficulty. Returning the the image sent to and returned from Nik again causes the flashes.

The annoying flashes happen quite often in the develop mode when working on an image edited directly in Nik software from LR. This makes the develop module virtually unusable after sending an image to a Nik plug-in.

I've placed a video clip showing the bug:

http://gpsinformation.org/ronh/images/Lightroom - Nik bug.m4v

I will be reporting this to Nik.

The video file will be removed from the web page on or after June 4, 2011.

CR in CS6 Released version does not support the 5D Mark III

forums_noreply@adobe.com — Mon, 07 May 2012 06:41:37 GMT

Subject says it all.

Nik Efex Pro 4 very slow from LR 3.5 & 3.6

forums_noreply@adobe.com — Thu, 02 Feb 2012 06:22:48 GMT

My computer is a 27" iMac 2.93 GHz i7 with 16GB DRAM running OS X Lion (10.7.2).

Versions of software used in testing: Aperture 3.2.2, Lightroom 3.5 x64, Lightroom 3.6 x64, Photoshop CS5 12.0.4 x64, Color Efex Pro 4.001 x64.

I am finding that Nik Color Efex Pro 4 is very slow when "Edit In" from Lightroom is used to access the plug-in or the standalone app. Below is a technical question I submitted to Nik support. I haven't heard back from them yet, but I thought it might be a good idea to post here. Perhaps someone has this same problem and knows of a solution...

=== message to Nik Tech Support ===

Image used in testing is an 8MP image from a Digital Rebel XT. The image was taken in 2006.

If I select "Edit In" in Lightroom, chose Color Efex Pro 4, wait for the preview to show then select the Fog filter it takes 2 minutes and 39 seconds for the 'Calculating' to go away and the image to be presented.

If I select "Edit In" and chose Color Efex Pro 4 app the time delay is similar, i.e. VERY long.

At no time did my Free RAM drop below 10GB. At no time did my CPU usage go over 20%.

If I select "Edit In" and chose Photoshop CS5 and then use the plug-in from CS5 it takes less than 3 seconds for the calculating to go away.

If I use the Color Efex Pro 4 plug-in from Aperture, version 3.2.2, the times are similar to those in Photoshop CS5, i.e. very quick.

The time interval is too short to get an accurate measurement of Memory and CPU usage in CS5 and Aperture

What is causing this discrepancy? This excessive time delay--which exists whenever a filter is adjusted, changed, etc. makes many of the filters essentially useless from Lightroom.

Is Nik working on this problem? Do you have a solution? If not can I expect a resolution in the near future? Surely this has been reported before.

===

CS6 is now available for download.

forums_noreply@adobe.com — Mon, 07 May 2012 06:19:21 GMT

I've installed it (CS6 Extended) w/o a problem.

Oops--one very annoying problem...

Camera Raw in the released version of CS6 does not support the 5D Mark III.

Map Module annoyances

forums_noreply@adobe.com — Sun, 06 May 2012 03:58:02 GMT

I've been using the Map Module quite a bit to add GPS co-ords to old pictures taken before I began tracking my locations via GPS--so I have no tracklogs to use, otherwise I'd just use Jeffrey's plug-in. In my use of the Map Module I've come across a few annoyances and wonder if any other users have experienced any of them and/or knows of a 'fix'.

My typical work flow is to select a few--up to a few hundred--photos using a filter in the Library module or at times a smart collection. I then activate the Map Module and select multiple images taken at the same location and drag those images to the map to geo-encode them. The geo-encoding goes well and most of the 'Time and Place' fields are set with the text being light grey. The text for the GPS value is set to full brightness.

The 'annoyances':

1. For the 'Time and Place' metadata to become 'active' each item (City, State/Province, etc.) label must be clicked on and the current greyed location selected by clicking on the proper value in the pop-up that appears when the label is clicked. The problem is that if I have more than a few images selected--so I can set the 'Time and Place' information for all of them at once--after entering the first item, say for example City, all of the entries will go blank for a few seconds and then re-appear with City now non-grey and active. Sometimes the other entries remain greyed out and sometimes they totally disappear and I have to remember the spelling, etc., of the blank item and manually type it in for the pop-up does not always contain the entry that disappeared. Sometimes this 'flashing' of the metadata fields happens more than once per entry. Major annoyance.

2. When manually entering an entry because it became blank when setting a different field the metadata entries will blank out while I am typing and the characters I am typing are then interpreted as command characters for LR proper, not as entries in the text box I'm trying to type into. This is not acceptable behavior. Sometimes the sequence of letters when interpreted as commands to LR can really muck things up.

In 1&2 it is as if the program is writing the changed data to the catalog for every image. While this write operation is taking place the data in the right panel is blanked and the focus changed from an item in the right panel to the main LR window.

One other observation, since LR 4.0 was released with the Map Module I've had a few dozen crashes. Every single one of them has happened while working in the Map Module. I've never had LR 4.x crash at any other time.

It is my belief that the Map Module is poorly written and in need of major bug fixes.

My system is a mid-2010 27" i7 iMac @ 2.93 GHz and 16 GB DRAM. I have over 600 GB remaining on my system drive. My raw cache files reside on an external drive connected via FW800 which has over 1.5TB free. I am using Lion (OS X 10.7.3) and the system was installed fresh, not an update from Snow Leopard.

Ideas anyone?

Reverse geocoding

forums_noreply@adobe.com — Tue, 06 Mar 2012 10:34:29 GMT

Now that it's enabled, does anyone have any knowledge of how it is supposed to work? The downloadable LR manual doesn't even mention it and so far I've not found any tutorials that mention it, either. It isn't a big issue for me but I am curious as to just how it works.

Crash in soft-proof

forums_noreply@adobe.com — Fri, 02 Mar 2012 21:11:10 GMT

I have submitted the crash report to Adobe, but I'm posting it here, too.

I recently replaced my aging HP B9180 printer with an Epson 3880 and also removed the driver and profiles from my 27" iMac.

I was in the develop module and selected soft-proofing. As it happens the last image I used the soft-proof on was with the HP Advanced Photo Glossy profile. The soft proof image came up totally black. I then realized that the wrong and missing profile was being used so I selected one from Epson and the image returned.

As I was checking the soft-proofing for several paper profiles I accidentally selected another HP B9180 profile, I don't remember which one, and the app immediately crashed.

I suspect LR4 needs to be modified to either remove missing profiles from the soft-proof list or at least not allow a missing profile to be selected.

Soft Proofing & Print questions

forums_noreply@adobe.com — Tue, 21 Feb 2012 23:48:22 GMT

My system is a mid-2010 27" iMac, CPU is an i7 @ 2.93GHz, 16GB DRAM. My display has been calibrated with ColorEyes Display Pro using a Spyder 3 puck.

I have an image that has one color range that my B9180 refuses to print properly using Lightroom. I've tried Vendor Matching, Lightroom controls color using the proper printer paper profile, both relative and perceptual, etc., etc., and still that one color refuses to print properly. It always comes across as de-saturated. I've always assumed it was out of gamut and didn't worry about it as all other colors were correct as far as I could tell by eye.

With the release of LR4 and it's softproofing capabilities I decided to throw that image into the mix. I found that the color that refuses to print is not marked as out of gamut by LR4's soft proofing feature yet it still prints washed out. However, the image fit to the 4x6 borderless paper perfectly when I set borderless expansion to minimum in the driver. As a check I loaded up Photoshop CS5 and gave it a try. It, too, did not show the image as out of gamut and it also printed the image in exactly the same way LR4 printed it, i.e. the troubling color range was de-saturated.

Just for further data I tried printing the image on HP Premium Photo paper. I know, HP Premium Paper doesn't play nice with pigment inks but as a test of the color I gave it a try. The colors came out perfectly (though the ink still hasn't dried and it's been a couple of hours!). This leads me to believe that there is either something wrong with my paper or the profile. If anyone has any other ideas I'd be open to suggestion.

I decided to give my wife's all-in-one HP D110a a try. I set the D110a up to use vendor matching and set the paper in the printer driver to HP Premium Photo Paper. I set the paper type to 4x6 borderless with tab in the Page Setup. I printed a PDF preview and all appeared to be ok so I then sent it to the printer.

All of the colors in the D110a print matched the iMac display colors as close as my eye could tell, even the range that was so troubling on the B9180. I couldn't see any color differences between the display and the photo. There was one glaring problem, though. About 1/4" of the image was missing. I have a watermark on the image that is about 1/8" above the bottom edge and is about 1/8" high. 95% of the watermark was missing, i.e. off the paper and it was obvious that the other three sides were 'cropped' a similar amount as well.

My assumption here is that the 'cropping' is caused by the printer driver 'expanding' the image to ensure that there isn't a white 'sliver' in a borderless print. If so, this amount of expansion seems to me to be excessive yet there is no mechanism to change the amount of borderless expansion in the D110a as there is in the B9180 so I'm stuck. If I print the image with borders all is well.

Anyone have any ideas about how I could get a proper borderless print from the D110a using LR? I'm not sure what is involved but is it possible that some setting or sequence of settings in LR could 'fake' the printer driver into printing a properly sized borderless image?

Display 'flashes', edits lost.

forums_noreply@adobe.com — Wed, 25 May 2011 20:46:41 GMT

I've been away from photo editing/LR for a while and am now back using LR and I've noticed a couple of things that confuse me. I'm wondering if anyone else has the same experiences or if they are particular to my setup. This happened with LR 3.4 and now with 3.4.1

I have a late 2010 27" iMac with i7 @ 2.93GHz, 16GB DRAM, Lightroom is on the internal 1TB drive which has 600GB free. I also have 30GB assigned to the Camera Raw cache on the same drive. My images are on an external FW800 drive.

Here's the first symptom: If I execute LR, enter Develop mode, select a photo I have previously edited, go to the history, select a step somewhere within the history 'tree', the display will flash and quickly settle on the image at that step. If I then select another step within the tree, the display will again flash and 5-8 seconds later flash again. The question is what is causing this to happen? It is disturbing and interrupts thought processes. By 'flash' I mean the LR display blanks out--the image area goes grey--and the image re-appears a fraction of a second later.

Another thing also includes the 'display flashing'. I can be using the brush in develop to change the aspect of an image. I will be brushing along watching the edits take place and suddenly the brush will just stop as if it is frozen, a few seconds later the display will flash and when it stabilizes it is as if I never started that particular brush stroke. Every change from the beginning of that brush stroke has vanished. Often (about 1/3 of the time) I will notice that a 'step' in the history tree labelled 'Camera Raw Settings' has been created. I have never seen that happen before. I don't believe any of this is 'normal' but I wonder just what I can do about it. The only thing I have done so far is optimize the catalog and increase the camera raw buffer from 15GB to 30GB and purge the cache and still have the 'problem'.

Anyone with any ideas?

LR 3.2 bug? LR shows incorrect date on an imported iPhone 4 movie clip

forums_noreply@adobe.com — Sat, 11 Sep 2010 03:00:47 GMT

I imported a movie clip I captured on my iPhone 4 ver 4.1 to my iMac. I then examined the clip using MediaInfo Mac which shows both the video and audio streams to have been recorded at the correct date/time so the correct time of original recording information is stored in the clips metadata. I then drag an drop the clip onto LR 3.2 bringing up the import dialog. Before completing the import process I hover the mouse over the clip and the LR popup tool window shows the correct recording date and time. I then press the 'Import' button.

After completion of the import I examine the clip metadata in the LR library and find that the original recording date has been changed to 12/31/03 04:00:00 PM.

This 'date transformation' takes place for every clip I capture on my iPhone 4 and then import to LR. I don't know if LR is expecting date/time info to be somewhere else, but if so why would hovering the mouse over the clip produce the correct date?

How do I get PrE 9 Online Plus content to appear?

forums_noreply@adobe.com — Tue, 28 Sep 2010 08:03:23 GMT

I purchased PrE 9 Plus and have downloaded and installed the extra content. If I load in a clip, select the Edit tab, then select Plus Members Only from the drop down list on the left side of the Organize/Edit/Disc Menus/Share panel nothing shows up. The same is true for all of the items: Effect, transitions, Titles, Themes, Clip Art.

Why doesn't the Plus content show up? Is it perhaps because none has been released yet? Or ... ?

What about older content for PrE 8? Should any of that show up in PrE 9?

PrE9 loses preview render

forums_noreply@adobe.com — Thu, 07 Oct 2010 06:39:11 GMT

I can render a clip using RETURN or Timeline->Render Work Area and I can see the .mov file created under Documents-Adobe-Premiere Elements-9.0-Adobe Premiere Elements Preview Files-Test Project. At the end of the render the line turns from red to green and previewing the clip is smooth.

If I immediately save the project using Command-S then exit using Command-Q, then execute PrE9 and reload "Test Project" the line has reverted to red and preview is once again jerky. The .mov file still exists but for some reason apparently isn't being used.

Any idea why?

Update...I totally uninstalled PrE9, removed all prefs, all user files, all items in the library and re-installed. It is now tracking the rendered clips correctly.

Since I am just learning the software and haven't started a serious project yet I can afford to remove and re-install. Later on I won't be able to do that so if this is a bug I hope Adobe fixes it soon.

Anyone downloaded Premiere Elements 9 MacContent1 successfully?

forums_noreply@adobe.com — Thu, 23 Sep 2010 04:22:17 GMT

I downloaded the trial onto my iMac and upon starting as a trial I was offered the option of downloading the extra content for the Mac. I selected 'Yes' and was taken to the following page:

http://www.adobe.com/special/premiereel/downloads/

Under the For MAC OS area I clicked on the Download now link which is supposed to be 3.66GB. However, the link points to the download .dmg file for Premier 9 and not to the 'content'.

Does anyone know the correct link for the Premiere Elements 9 Content1 file?