Photoshop :: Black Areas In Image Appear Oddly In File Open For Long Time?
Mar 5, 2012
There's probably a simple explanation, but if I have a file open for a long time in Photoshop the blacks will start to appear oversaturated/blocked up. If I close and reopen file it looks normal again.
I am using OS X Lion, Photoshop 5, Apple 30" Cinema display. My monitor is calibrated with a i1 Display by X-Rite and resets according to amibent light.
I recently installed Corel paintshop pro x4 in my computer and when I go to open it, it takes a long time for it to open. My mouse keeps spinning. When I first installed it, everything worked fine. I added a couple of plug ins. Should I uninstall paintshop and re-install? If so, would I lose the plug-ins?
A few of my design drawings are taking a long time to open from cold. They are not particularly complex drawings and all the files / assembly etc. that are referenced on them are correctly stored and are not corrupt or 'sick'. Why are these drawings taking so long to open? waiting for them is slowing me down considerably.
Product Design Suite Ultimate 2013 64-bit HP Z400, Intel Xeon W3550 3.07GHz
12.0GB RAM, ATI FirePro V4800 (FireGL) Autodesk Inventor Professional 2013 SP2 64-Bit Edition Windows 7 HP Z400, Intel Xeon W3550 3.07GHz 12.0GB RAM, ATI FirePro V4800 (FireGL)
Have open a old max scene. And it take a very long time to save. That can have multiple reasons. Found a new (for me):
My old scene has a "render output" path to a no longer exists netzwork drive. This slow down max on save. Don't know why max access the output path on save ;( Slow down is also the Assert Tracking dialogue and "Render Output/Files..." Dialogue... Maybe max always tries to access the not existing network drive, every time ;(
I am having a huge issue with Photoshop CS5.5. The gradients and colors are acting crazy. When I bring in a image with a gradient it gets black spots all in the dark areas. Even when I use the default gradient selection this is what happens. When I bring in a picture that should have a white background it turns to black. Now apparently, when I save it out as a JPEG saves correctly without the black line or messed up gradients. So it seems to only be an issue when I am working in Photoshop, the gradients appear messed up. What is wrong with my display?
We have a data folder on the server mapped as network drive to the clients. The data folder contains all cad data stored from productstream professional.
Due to an over 10 year old environment the data folder contains a huge amount of cad files, library parts, iParts and so on.
Due to historical growth of the environment there are some missing parts (not available on the file system anymore), because they were deleted, are corrupt, and so on. At the root of the data folder there is located the typical cmpinv11.ipj inventor project file.
If you open an assembly either from productstream or via inventor (without productstream) directly from the data folder and the assembly has an unresolved child component because the file isn't there anymore it takes a very very long time until the dialog box for unresolved link comes up (waiting time several minutes 1...10min). Once reached this point one can skip and repair the assembly, of course.
But the question is, how to speed up the time for getting the unresolved link dialog?
The network connection itself is quite OK und the project file itself is also OK. The project file list of every user is pretty small (only cmpinv11.ipj and some standard ipj's).
We think inventor internally scans the whole project-file folders to ensure that the component is really missing but due to the huge environment this takes many minutes and is annoying.
Any bypass for that? Is it possible to apply a temporär setting before opening a potential inconsistent assembly? Or is there a setting like skip unresolved components by default or by a defined timeout?
Because it is Inventor 2010 (Productstream PRO 210) there is no File open Option Auto-Skip unresolved components (like in 2012) but even if it was I guess it wouldn't reduce the time to get the dialog either.
Whenever I drag an image off the web into Photoshop it seems like some colors gets pixels, large black areas inside the image. This only occurs in 8-bit mode, when I turn the image to 32-bit it show all colors correctly. But in 32-bit mode I cannot save to web. If I finish the image in 32-bit and then downgrade it to 8-bit, the black parts return.
What I see in 8-bit mode: What it should look like, and does in 32-bit mode:
If you need any technical specs apart from knowing that I use Photoshop CS5,
In the image below I have an aerial photo of an Island. I need to make it so as water areas are black and land areas are white (not greyscale) almost like a silhouette. My first plan was to draw round the island with a black paint brush and then use the "bucket fill" with a suitable threshold to fill all of the areas up to the black outline with black, however this doesn't work as the bucket fill either breaks through the black line or when I reduce the threshold, doesn't color the water areas solidly.
I got some psd files and when I open them it says "Reading Photoshop Format",and takes long time showing the progress status. It was not like that before.I always open that kind file every day and never get that message. Now I am getting. Why?
Windows 7, Photoshop CS6 13.0.1 x64. I updated from CS5 and all was well. Photoshop came up very fast when it was started. One day for a reason I've forgotten, I had to delete and reinstall CS6 and ever since then it's taken I'd estimate maybe 20 seconds to come up. If I shut CS6 down and restart it without rebooting the computer, it comes up relatively fast.
I'm assuming there is a file that should be starting on boot and apparently it got lost along the way. But I see nothing unusual in my startup file.
Every time I open a RAW file in CS6 (at 16-bit depth) it crashes, so I am unable to open RAW files after editing in Camera Raw. The RAW files open OK in Camera Raw and I can edit them, but then opening them from Camera Raw into Photoshop (by clicking on Open Image) causes a crash.
Further background: I also had CS3 (the entire suite concurrently) installed. Thinking that might be a problem, I removed all of CS3 using the Adobe Uninstaller tool to see if that would work. Then I re-installed Photoshop CS6 from scratch and then downloaded and installed all updates.
CS6 still crashes every time I open a RAW file if I open it as 16-bit. If I open a .DNG file directly from Photshop (without using Camera Raw), that crashes too. I'm opening them into Photoshop using Adobe RGB (1998), 16-bit, 3456 x 5184 (17.9 MP), 300DPI.
Thinking it might be a memory issue, I checked free RAM using Activity Monitor and I see it has 3.4 GB free with both CS6 and Bridge open, which should be plenty. However I do see by looking in the crash report from the system log (portion included below), that it appears the crash may have resulted from a failed MALLOC (memory allocation).
Here's the kicker: oddly, when I open the file up in Photoshop at 8-bit depth, it works fine.
Software and Hardware versions: Photoshop CS6 Extended (13.0.4 x64) Camera Raw 7.3 Bridge CS6 (22.214.171.124) Mac OS X 10.8.2 (Mountain Lion) 8 GB RAM 27" iMac with 2.66 Ghz Intel Core i5 ATI Radeon HD 4850 graphics card with 512 MB RAM 1 Terabyte HD with 750GB free Canon EOS Rebel T3i Canon EF75-300mm f/4-5.6 Lense
Top portion of System Log file with the crash data in it: Process: Adobe Photoshop CS6  Path: /Applications/Adobe Photoshop CS6/Adobe Photoshop CS6.app/Contents/MacOS/Adobe Photoshop CS6 Identifier: com.adobe.Photoshop
I have been running PSCS3 for quite a while. I just installed it into a new system. Just about every time I try to shut it down, it takes 5 minutes or more to shut. Often I need to use the task manager to close and it takes several attempts to close.
FWIW, Bridge CS3 can have the same problem.
I have 3 GB RAM. 3.00 gigahertz AMD Athlon 64 X2 Dual Core.
I was wondering if anyone knew what is wrong with my smudge tool. When I go to use it and apply it to my image, it takes a while to show the affect. Everything else in my photoshop works fine. Oh yeah, I use PS CS if that makes any difference.
When I have 2 files open, one minimized and the other visible on the screen, when I quit the file showing on the screen and then open the one that was minimized, it comes up w/a blank black screen. There is no way I have found to get the info in the file to display.
Then, if I save the blank screenof previously minimized file, close it then reopen it the info is back on screen with changes made to the file intact.
I just purchased a new computer which is running Windows 7 and has an AMD Radeon graphics card. I loaded my Photoshop CS4 on this new computer. I previously had CS4 loaded on a Dell Inspiration laptop that died. I never had any problems with CS4 on my laptop. I have always used a working color profile of sRGB IEC61966-2.1 as that is the color profile that my digital camera uses. Now when I open photos in CS4 using this color profile, there are black pixelated areas on many of the photos. I can get rid of this in two ways, 1. by dropping the saturation down to around -8 or 2. changing my working space profile to Adobe RGB 1998 and then converting the documents color profile to the working space. I have to convert every photo that I bring in to Photoshop.Is the graphics card not compatible with CS4?
Tonight I created my first DVD disk (ie authored a DVD) using X4 which I purchased last year.It seemed to take a much longer time to complete especially the creation of the title (menu?) than what I am used to using VS10.
Is this normal?
Is this a known 'problem' with X4?
What are others using to author a DVD?
Should I use VS10 to 'create disk'?
BTW I authored using the same characteristics as I used when I created my DVD file (create video file) so I don't think that it re-rendered.Also I am creating a 'standard definition' DVD not high def.
Is it normal for VSX4 to take a long time to save a project? I am finding that it is taking about 20 minutes for X4 to save my project each time, which has a running time of about 45 minutes. This is an excessive amount of time wasted in waiting for it to do its thing, as I can't proceed with anything else while it is saving.