| Author | Thread |
|
|
02/07/2011 08:40:50 PM · #1 |
So, I've just used it for the first time (whoopie!!!!), and I can't manipulate the image at all in PS after the multiple images have been combined. I can't even "save as"...
I need help. Am I doing something wrong? |
|
|
|
02/07/2011 08:45:40 PM · #2 |
Originally posted by tanguera:
So, I've just used it for the first time (whoopie!!!!), and I can't manipulate the image at all in PS after the multiple images have been combined. I can't even "save as"...
I need help. Am I doing something wrong? |
Check to see what image mode you're in...many PS features don't work until you are down to 16 bit or 8 bit mode. |
|
|
|
02/07/2011 08:51:54 PM · #3 |
Originally posted by nshapiro:
Originally posted by tanguera:
So, I've just used it for the first time (whoopie!!!!), and I can't manipulate the image at all in PS after the multiple images have been combined. I can't even "save as"...
I need help. Am I doing something wrong? |
Check to see what image mode you're in...many PS features don't work until you are down to 16 bit or 8 bit mode. |
I was thinking the constraint was from the other direction. HDR Efex Pro requires a 64-bit version of PS.
 |
|
|
|
02/07/2011 09:05:00 PM · #4 |
Originally posted by nshapiro:
Originally posted by tanguera:
So, I've just used it for the first time (whoopie!!!!), and I can't manipulate the image at all in PS after the multiple images have been combined. I can't even "save as"...
I need help. Am I doing something wrong? |
Check to see what image mode you're in...many PS features don't work until you are down to 16 bit or 8 bit mode. |
I had the same problem with PS Elements. Changing the mode made all the editing features available.
|
|
|
|
02/07/2011 09:18:21 PM · #5 |
| It would have nothing to do with what version you are using...it's image mode menu, there's 8, 16, and 32 bit modes. Little to no editing in 32 bit mode. |
|
|
|
02/07/2011 09:39:46 PM · #6 |
I just downloaded the full functional 15 day trial to run some tests. I'm running Windows 7 Pro 64 bit, on my quad core processor with 8 gig of ram, it installs for all Photoshop versions I have which are 32 and 63 bit versions of Photoshop CS4 and CS5. It also intalls for my Lightroom 2.6 and 3.0 installs which are native 64 bit apps.
I ran HDR Efex Pro under CS4 64 bit, and opened 5 RAW images (.CR2) in the Nik dialog box. The plugin merged them and then opened the preset window for tone mapping. I clicked through some presets, and then made custom tweaks and applied it. It then meged it down into on layer and brought it back into Photoshop. All that I would expect it to do.
I was able to do some test adjustment layers directly on the locked background file (I always make a duplicate of the background, but specifically was trying to isolate issues) and it all worked. I applied a curve layer, levels, exposure adjustment, photo filter 85A etc. All worked.
Not sure what your exact issue is Johanna, but maybe you can give some more info.
The only thing I noticed so far is that my image wasn't showing up in the preview windows of the presets yet they all changed and effected the photo when I selected them. Perhaps I need to reboot or go back into the program a second time.
ETA: I am also able to use layer masks on all my adjustment layers to alter the photo selectively. BTW, just so you know it brought the initial layered file into Photoshop as 16 bit. Check to see if your file is 32 bit or 16 bit. Normally editing options for 32 bit files are very limited, but dropping it to 16 bit solves that.
Also, just tried it with a single exposure (.jpg)in CS4 32 bit and all works well in that mode...including the thumbnails for the preset previews and control points. When I brought it into Photoshop after closing the tone mapping I was once again able to edit at will.
I haven't tried it under CS5 yet though.
Dave
Message edited by author 2011-02-07 22:10:08. |
|
|
|
02/07/2011 10:28:47 PM · #7 |
Johanna, It's the 32-bit business for sure. Go to Image>Mode and select 16-bit (or 8-bit if you prefer) and everything will be fine.
Nutter, the blank previews happens to me sporadically. Reboot of CS3 usually fixes it.
R. |
|
|
|
02/07/2011 11:06:56 PM · #8 |
Johanna,
What version of Photoshop? |
|
|
|
02/07/2011 11:19:33 PM · #9 |
Originally posted by hahn23:
Johanna,
What version of Photoshop? |
I donno about HER, but I'm running it in CS3 and it works fine. But there is that issue of churning out 32-bit results and having to take it down to 16-bit...
R. |
|
|
|
02/07/2011 11:25:10 PM · #10 |
Originally posted by Bear_Music:
Originally posted by hahn23:
Johanna,
What version of Photoshop? |
I donno about HER, but I'm running it in CS3 and it works fine. But there is that issue of churning out 32-bit results and having to take it down to 16-bit...
R. |
More power to you! The minimum system requirements are higher, but what do I know. |
|
|
|
02/07/2011 11:40:19 PM · #11 |
Originally posted by hahn23:
Originally posted by Bear_Music:
Originally posted by hahn23:
Johanna,
What version of Photoshop? |
I donno about HER, but I'm running it in CS3 and it works fine. But there is that issue of churning out 32-bit results and having to take it down to 16-bit...
R. |
More power to you! The minimum system requirements are higher, but what do I know. |
Those are the system requirements to actually USE it at 32-bit and 64-bit, apparently. I have no doubt it will perform better when I upgrade machine and photoshop. But it's still turning my 16-bits into 32-bits when it grabs them, and I have to tweak them back. In theory, CS3 does know how to handle 32-bit, it IS on the menu, but...
R. |
|
|
|
02/08/2011 12:14:02 AM · #12 |
Originally posted by Bear_Music:
Johanna, It's the 32-bit business for sure. Go to Image>Mode and select 16-bit (or 8-bit if you prefer) and everything will be fine.
Nutter, the blank previews happens to me sporadically. Reboot of CS3 usually fixes it.
R. |
Okay Robert, it's good to know that the previews not showing at times have little to do with my computer. Thanks for letting me know.
Dave |
|
|
|
02/08/2011 12:30:55 AM · #13 |
Hi everyone, and thank you so much.
I'm using Windows 7, 64-bit, CS5. The plug-in loaded without issues, and I was able to open three images (after checking the online instructions on how to do that). I used the file, automate (?), then load images for HDR. Everything proceeded as with you, DC. Did some tweaks to the presets, clicked ok, then it loaded into PS. No problems at all. But once it opened in PS it got weird. The file was layer 0, and had a couple of levels below it. I tried to create a copy, and it copied it exactly the same, neither of which was editable. When I tried to save, it wanted to save as an HDR file, not as a PSD document. I chose PSD from the dropdown menu but I was still unable to edit it. I tried various different ways of copying the layer but none made a difference. I did not adjust the mode, but I see that Bear provided some instruction so I'll try that tomorrow. Not that I'll understand the answer, but why would a 64-bit system requires a lower-bit file?
Would it make a difference if I flattened the layer and tried copying that?
Also, please remember, I'm really a newbie at this PS business and everything I know I've learned from DPC and just trial and error. You need to use small words and pictures for me to understand :-) |
|
|
|
02/08/2011 12:50:42 AM · #14 |
Originally posted by tanguera:
Hi everyone, and thank you so much.
I'm using Windows 7, 64-bit, CS5. The plug-in loaded without issues, and I was able to open three images (after checking the online instructions on how to do that). I used the file, automate (?), then load images for HDR. Everything proceeded as with you, DC. Did some tweaks to the presets, clicked ok, then it loaded into PS. No problems at all. But once it opened in PS it got weird. The file was layer 0, and had a couple of levels below it. I tried to create a copy, and it copied it exactly the same, neither of which was editable. When I tried to save, it wanted to save as an HDR file, not as a PSD document. I chose PSD from the dropdown menu but I was still unable to edit it. I tried various different ways of copying the layer but none made a difference. I did not adjust the mode, but I see that Bear provided some instruction so I'll try that tomorrow. Not that I'll understand the answer, but why would a 64-bit system requires a lower-bit file?
Would it make a difference if I flattened the layer and tried copying that?
Also, please remember, I'm really a newbie at this PS business and everything I know I've learned from DPC and just trial and error. You need to use small words and pictures for me to understand :-) |
Ok, that is odd. I think you may have selected the option to creat a Smart Object when the final photo is brought into Photshop. Don't do that. Mine came in as a single flattened layer and I DID NOT select that box. What you describe is how a Smart Layer looks with a hierarchy of layer and effects that are staggered underneath a main layer.
So, when you select the files for your initial exposures make sure that box is unchecked right under the filename box. The one that asks if you want to create a smart object. Many filters and effects will still not work on a Smart Object or filter.
ETA... I might also point out that even if this box is left unchecked during the initial merge of the RAW files Efex HDR Pro will still convert those files into smart objects to create the merged image ready for tone mapping or the application of a preset. You can see this if you watch the process bar during the merge. It's ONLY AFTER you do your tone mapping and click ok to bring it back into Photoshop that it converts back into one single rasterized and locked layer.
ETA 2: Ok Johanna, I just confirmed my suspicions and ran a couple more tests. I opened 5 RAW files (.CR2) through the Efex HDR Pro select file dialog box and then did what I recommended you NOT do....I checked the box to open as a smart object. After it went through and merged the files I got the tone mapping window, applied a preset and selected ok. Instead of it being one layer in Photoshop I got a main layer "Layer 0" with two sub layers beneath. One labeled "Smart Filters" and the bottom layered something Efex HDR Pro etc. It also brings these into Photoshop as 32 bit. So if you tried to apply an adjustment layer for instance you would see most grayed out. This is normal under the circumstances. So please make sure that when you bring the select the files to merge that you UNCHECK or leave unchecked the box asking you if you want to create a smart object. You don't at this point. If you are new to Photoshop then Smart Objects and filters will only frustrate you right now. They can be very powerful and useful, but with that there are always concessions and the inability to use certain filters or effects if one of them.
Dave
Message edited by author 2011-02-08 01:25:00. |
|
|
|
02/08/2011 02:12:53 AM · #15 |
Originally posted by tanguera:
...Not that I'll understand the answer, but why would a 64-bit system requires a lower-bit file?
. |
Two separate animals. Your operating system (Windows 7 64-bit in your case) can communicate and work with your motherboard, hardware and processor because it's designed around a 64 bit architecture. So you couldn't for instance run a 64 bit operating system on a motherboard/cpu (processor) configuration that was only supported 32 bit.
Modern day graphics cards and LCD monitors are basically built around a 24 bit RGB architecture so if your graphics card is only sending 24 bit color information to your display you can't see a true 32 bit representation of the image on your display. That is why most filters and effects will be disabled because you can't see them accurately to begin with. It's also why a multi exposure image has to be tone mapped down into a usable format for your display. Data and color information need to be compressed and mapped down to colors that industry standard cards can show. I know it's confusing so don't fret over the technical details and just know that as long as your image is 16 bit or 8 bit you'll have less worries in Photoshop. LOL.
For what it's worth it's also why working in the Lab colorspace system is so funky. The monitor can't display colors in a manner you would expect to see. Again, nothing to worry about. :)
Dave |
|
Home -
Challenges -
Community -
League -
Photos -
Cameras -
Lenses -
Learn -
Help -
Terms of Use -
Privacy -
Top ^
DPChallenge, and website content and design, Copyright © 2001-2025 Challenging Technologies, LLC.
All digital photo copyrights belong to the photographers and may not be used without permission.
Current Server Time: 08/26/2025 01:02:51 AM EDT.
