Photoshop Doubling my jpeg when saving

So when i save a Jpeg, even if i dont edit anything it will double the size..... if i use ViewNX2 to save it it will be about 10MB ... but then i go to photoshop and save it without editing it it becomes about 20MB ... but that same file i can go back to ViewNX2 and save it and it will bring it back down to 10MB .... What is the deal? Whats going on.....

What's going on is the compression rate varies each time you save it depending entirely on your settings.
Let's say you save a JPEG with ViewNX2 at maximum compression, then decompress it by opening it in Photoshop.  It will of course balloon in size.  Now you compress it by saving in Photoshop at maximum quality, which means minimum compression.  Of course it will be MUCH bigger than the original ViewNX2 JPEG.
There are a bunch of possible variations between these two examples, always according to your settings.
It's perfectly normal and expected behavior.

Similar Messages

  • Externally edited Photoshop files are huge when saved back into Aperture 3

    I start with an 8MB JPEG photo. I externally edit it in Photoshop Elements 6, and hit "Save". The edited image is saved back into Aperture, but it's now 34MB PSD. Ouch! My hard disk is big but this is over the top. The intent of me moving to Aperture from iPhoto had been to reduce file sizes (masters and versions), not to hugely increase them.
    If I use "Save As" and convert it to a JPEG, the saved edited photo vanishes--it isn't in Aperture. I can't find it. If it is saved in some unknown location it is taking up hard disk space uselessly.
    Can you help me do this better? I would be most grateful.
    Message was edited by: shep222

    shep222 wrote:>...even if I do zero Photoshop editing I still get this >3 times increase in file size.
    Yup. That is how big such files are when not compressed and image data has not been discarded.
    It's an Aperture vs. iPhoto thing: When I did Photoshop External Editing in iPhoto (before I switched to Aperture) the original JPEG stays a JPEG when exported to Photoshop. The file size problem does not occur in iPhoto.
    That is correct, and is why few if any pros use iPhoto. iPhoto is by definition +low end,+ dumping image files into lossy JPEG by default. A RAW file imported into iPhoto is saved in JPEG unless the user takes special action to export it as TIFF or PSD.
    Aperture won't allow it--it seems to insist on converting to PSD for external editing.
    Also correct. Aperture is a professional app, and intentionally and repeatedly discarding image data would not be professional workflow.
    My JPEG's are top-notch low-compression ones, using the least compression settings in my Olympus micro-4/3 camera (super fine, large image, with 1/2.7 compression). JPEG artefacts have not been an issue even after extensive Photoshop editing.
    Agreed, top quality JPEGs can be very useful even though image information has been discarded. Back when RAW DSLR capture was unusably slow I shot many full-page magazine ads using JPEG Fine. But once the (fast) Nikon D2x came out I have always captured RAW and would no way ever again consider far inferior JPEG-only capture.
    Perhaps Aperture is not for me, if we can't overcome this issue.
    Perhaps. However IMO a far better approach is to shoot RAW and embrace a professional lossless workflow using Aperture. Mass storage is cheap and the benefits of RAW capture are very significant.
    Already my Aperture Library is 70GB and I have barely started with it.
    The issue of huge Library is due to using a Managed-Masters Library. Switch to RAW capture and a Referenced-Masters Library with the Library on an internal drive and the Masters referenced on external drives and the Library will no longer grow ridiculously large. IMO discarding image data via JPEG compression just to save hard drive space is inappropriate in 2011.
    HTH
    -Allen Wicks

  • An issue whereby Photoshop .PSD files disappear when saved to a network file share

    It has been reported and reproduced by Support, an issue whereby Photoshop .PSD files disappear when they’re saved to a network file share.
    Upon initial investigations Support have observed the following behaviour when saving a Photoshop file.
    The document is initially saved as a new file on the file share.
    The original  .PSD file is deleted on the file share.
    The newly created file is renamed to the same name as the original file.
    An issue often arises when steps 1 and 2 complete however step 3 fails. When a file is reported by users as having disappeared, the new file created in step 1 can be renamed from  .00_ to the original *.PSD file name on the server as the *.00_ files are normally hidden by the desktop operating system. This allows people to see and open the file from both PC’s and MAC’s using AFP and SMB protocols.
    A related issue often reported by users is that they receive an error message “Could not save as” when trying to save a .PSD file. Troubleshooting the issue confirms that the user is able to save the file if they perform a “Save As” operation in Photoshop.
    From the reported problems and observations there is clearly an issue with how Photoshop performs a file save operation further exacerbated by the fact the process doesn’t fail safely.

    Sounds like you're hitting one of the known MacOS filesystem bugs - worst when working with SMB volumes.
    Apple knows about this, and we are pursuing workarounds to the OS bugs.
    Yeah, if you value your files, don't save directly to servers, especially on MacOS.

  • Why does photoshop (cs5) 'hang/stall' when saving as jpeg?

    i've been noticing that the program has seemed to run slower than it was a few months ago - taking longer to load up, buttons being unresponsive for a few seconds, etc.  recently i noticed if i'm saving my psd file as a jpeg it will 'hang' for several seconds with the "ok" button greyed out.  after several seconds it will turn blue but when i click it, it acts unresponsive but after a few more seconds it saves the document.  but there's no click animation or whatever you might call it.
    like i said it just recently started running generally slower.. laggier. 
    if anyone has any clues or advice, it would be much appreciated.
    some specs - intel core i3/ 3.06GHz/ 4MB/ ATI Radeon HD 4670

    While you're interacting with the Save As dialog, you're really working with Windows Explorer, rather than with Photoshop.  The dialog is part of the OS.
    I suggest that you must have installed a Shell Extension that's somehow causing stalls or failures behind the scenes.
    A great freeware program you can use to both enumerate and ultimately disable Shell Extensions you don't want running is the Shell Extensions Manager by Nir Sofer:
    http://www.nirsoft.net/utils/shexview.html
    An effective strategy, if a bit time consuming, is to disable non-Microsoft plug-ins one at a time, followed by a logout and login, then test.  Once you've disabled the one that's causing the problem you should see your Explorer dialogs speed up.
    Good luck.
    -Noel

  • Photoshop Latency Issues? when saving....1.5min to open 5.5 min to save same file.

    I am struggling to optimize my computer for Photoshop.
    An example file opens in 85 seconds. Same file saves in 340 seconds.
    PhotoShop CS6 (13.0.1)
    File is 21000 x 21000 - 50 layers (5.8gb .psb saved)
    Why so big? - 5k.com/C.jpg
    When I open image, I see 2 swap files 67gb & 8.5gb
    Hard drives
    C: Samsung 830 256 ssd boot drive.
    Raid0 SSD Samsung 840Pro 256x2 (512total) PSswap/temp (Tests @1100mb/s read @880mb/sec write)(Z77 intel RST v11.0+ raid0 trim)
    Samsung 830 ssd media drive (open & save)
    File opens in 90 seconds. Saves in 340 seconds.
    stays at 0% saved for 270 secs
    INTEL I7 3770K 3.5G 8M R8 - CPUs utilization - about 12%+- overall - no one cpu above 50%
    ASUS SABERTOOTH Z77 lga 1155 MoBo
    32gb MEM 8Gx4 GSKILL F3-1866C10Q-32GXL R
    variables:
    tried video card at (Adv, int, basic) no change.
    Toyed with an NVIDIA QUADRO 6000 PCI-E 6GB - did not see performance change.
    Tried opening&saving to raid0 SSD no change.
    switched PSswap & media drives - slowed it down on open & close +- 100sec.
    I don't understand why it would take so much longer to save than open....
    Would a better video card (4gb or 6gb) make a difference?
    Would 64gb ram (dif mobo) or 6 core i7-39*0K CPU make a difference?
    Unrelated - When I pan to bottom-right of image there is a major lag in display. Up to 20 sec. regardless of video settings.
    Is there an easy way to calculate video ram needs based on image size? Prefer ATI - was looking at trying v9800 4gb.
    Tried NVIDIA QUADRO 6000 PCI-E 6GB - didn't seem better.
    I recall reading that with SSD drives, having seperate drives for OS, TMP, Media is no longer adventageous....True/False?
    I am grasping at straws to figure out what my bottlenecks are and how to elliminate them.
    Thanks in advance for any suggestions/advice.
    SysInfo
    Adobe Photoshop Version: 13.0.1 (13.0.1 20120808.r.519 2012/08/08:21:00:00) x64
    Operating System: Windows 7 64-bit
    Version: 6.1 Service Pack 1
    System architecture: Intel CPU Family:6, Model:10, Stepping:9 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
    Physical processor count: 4
    Logical processor count: 8
    Processor speed: 3510 MHz
    Built-in memory: 32723 MB
    Free memory: 5709 MB
    Memory available to Photoshop: 29745 MB
    Memory used by Photoshop: 84 %
    Image tile size: 128K
    Image cache levels: 4
    OpenGL Drawing: Enabled.
    OpenGL Drawing Mode: Basic
    OpenGL Allow Normal Mode: True.
    OpenGL Allow Advanced Mode: True.
    OpenGL Allow Old GPUs: Not Detected.
    Video Card Vendor: ATI Technologies Inc.
    Video Card Renderer: ATI FirePro V8800 (FireGL)
    Display: 2
    Display Bounds:=  top: 0, left: 0, bottom: 1600, right: 2560
    Display: 1
    Display Bounds:=  top: 0, left: -2560, bottom: 1600, right: 0
    Video Card Number: 1
    Video Card: ATI FirePro V8800 (FireGL)
    OpenCL Unavailable
    Driver Version: 8.911.3.3000
    Driver Date: 20120309000000.000000-000
    Video Card Driver:
    aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dl l,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
    Video Mode: 2560 x 1600 x 4294967296 colors
    Video Card Caption: ATI FirePro V8800 (FireGL)
    Video Card Memory: 2048 MB
    Video Rect Texture Size: 16384
    Serial number: 90148609589462100194
    Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
    Temporary file path: C:\Users\Ivy1\AppData\Local\Temp\
    Photoshop scratch has async I/O enabled
    Scratch volume(s):
      E:\, 238.5G, 154.4G free
    Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
    Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
    Additional Plug-ins folder: not set
    (shortened)
    Optional and third party plug-ins: NONE
    Plug-ins that failed to load: NONE
    Flash:
       Mini Bridge
       Kuler
    Installed TWAIN devices: NONE
    I am struggling to optimize my computer for Photoshop.
    This example file opens in 85 seconds. Same file saves in 340 seconds.
    PhotoShop CS6 (13.0.1)
    File is 21000 x 21000 - 50 layers (5.8gb .psb saved)
    Why so big? - 5k.com/C.jpg
    When open image, I see 2 swap files 67gb & 8.5gb
    Hard drives
    c: Samsung 830 256 ssd boot drive.
    Raid0 SSD Samsung 840Pro 256x2 (512total) PSswap/temp (Tests @1100mb/s read @880mb/sec write)(Z77 intel RST v11.0+ raid0 trim)
    Samsung 830 ssd media drive (open & save)
    File opens in 90 seconds. Saves in 340 seconds.
    stays at 0% saved for 270 secs
    INTEL I7 3770K 3.5G 8M R8 - CPUs utilization - about 12%+- overall - no one cpu above 50%
    ASUS SABERTOOTH Z77 lga 1155 MoBo
    MEM 8Gx4|GSKILL F3-1866C10Q-32GXL R
    variables:
    tried video card at (Adv, int, basic) no change.
    Toyed with an NVIDIA QUADRO 6000 PCI-E 6GB - did not see performance change.
    Tried opening&saving to raid0 SSD no change.
    switched PSswap & media drives - slowed it down on open & close +- 100sec.
    I don't understand why it would take so much longer to save than open....
    Would a better video card (4gb or 6gb) make a difference?
    Would 64gb ram (dif mobo) or 6 core i7-39*0K CPU make a difference?
    When I pan to bottom-right of image there is a major lag in display. Up to 20 sec. regardless of video settings.
    Is there an easy way to calculate video ram needs based on image size? Prefer ATI - was looking at trying v9800 4gb.
    I recall reading that with SSD drives, having seperate drives for OS, TMP, Media is no longer adventageous....True/False?
    I am grasping at straws to figure out what my bottlenecks are and how to elliminate them.
    SysInfo
    Adobe Photoshop Version: 13.0.1 (13.0.1 20120808.r.519 2012/08/08:21:00:00) x64
    Operating System: Windows 7 64-bit
    Version: 6.1 Service Pack 1
    System architecture: Intel CPU Family:6, Model:10, Stepping:9 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
    Physical processor count: 4
    Logical processor count: 8
    Processor speed: 3510 MHz
    Built-in memory: 32723 MB
    Free memory: 5709 MB
    Memory available to Photoshop: 29745 MB
    Memory used by Photoshop: 84 %
    Image tile size: 128K
    Image cache levels: 4
    OpenGL Drawing: Enabled.
    OpenGL Drawing Mode: Basic
    OpenGL Allow Normal Mode: True.
    OpenGL Allow Advanced Mode: True.
    OpenGL Allow Old GPUs: Not Detected.
    Video Card Vendor: ATI Technologies Inc.
    Video Card Renderer: ATI FirePro V8800 (FireGL)
    Display: 2
    Display Bounds:=  top: 0, left: 0, bottom: 1600, right: 2560
    Display: 1
    Display Bounds:=  top: 0, left: -2560, bottom: 1600, right: 0
    Video Card Number: 1
    Video Card: ATI FirePro V8800 (FireGL)
    OpenCL Unavailable
    Driver Version: 8.911.3.3000
    Driver Date: 20120309000000.000000-000
    Video Card Driver:
    aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dl l,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
    Video Mode: 2560 x 1600 x 4294967296 colors
    Video Card Caption: ATI FirePro V8800 (FireGL)
    Video Card Memory: 2048 MB
    Video Rect Texture Size: 16384
    Serial number: 90148609589462100194
    Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
    Temporary file path: C:\Users\Ivy1\AppData\Local\Temp\
    Photoshop scratch has async I/O enabled
    Scratch volume(s):
      E:\, 238.5G, 154.4G free
    Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
    Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
    Additional Plug-ins folder: not set
    (shortened)
    Optional and third party plug-ins: NONE
    Plug-ins that failed to load: NONE
    Flash:
       Mini Bridge
       Kuler
    Installed TWAIN devices: NONE
    Message was edited by: PECourtejoie

    That sounds like a pretty big document considering all the layers.  What's the nature of all those layers?  Pixel data edge to edge, or some vector data, some adjustment layers, a mix?  Do the layers have masks?
    I was curious, so I timed the saving of a very large image I have on hand, with 32009 x 21000 pixels, 16 bits/channel, 42 layers, some pixels, some adjustment layers, most layers with masks.  I have "Maximize Compatibility" set to "Never" and I enabled Flate compression.  The save was to a high bandwidth SSD array, and like you I have Windows 7 x64.
    The save went like this:
    It started at 0%
    Jumped to 25% at 8 seconds into the save.
    26% at 0:35
    27% at 1:30
    28% at 3:15
    etc. at long intervals.  The file psA3B2.tmp grew incrementally all during that time.
    It seemed to stop at 73% for a few minutes.
    The save completed in 22 minutes 10 seconds and the .psb file was ultimately 6.6 GB in size.
    Since I have Background saving enabled in Photoshop CS6 I was able to interact with Photoshop and could potentially have been continuing editing during that time.  Also I had no problem doing other things, like type up this message, chat on Skype, etc.
    I have 48GB of RAM and actual usage rose to 43.4 GB.  Photoshop created a 58GB scratch file.
    It busied one logical processor (of 24) pretty much to the max the entire time (showing a total of 4% usage).  As I understand it data compression is not something easily multi-threaded (though I wonder whether it could be done by multiple threads on a layer by layer basis).  Your core speed is faster than mine with that i7-3770K processor (as compared to my Xeon X5690 CPUs), and who knows how different our documents are, but I'd say your system did rather well given that you have compression enabled.
    The real workaround that could make it more usable for you is what Chris said above - for a document at this magnitude in size, disable the Flate compression and it will get right to the task of saving to disk.  And yes, it will make the file HUGE - so you trade size for speed.
    As a test I disabled compression and saved again.  This time the save completed in 1 minute 29 seconds and the .psb file ended up being 36.5 GB in size.
    -Noel

  • Problem with Photoshop CS6 Freezing up when saving OSX Mavericks 10.9

    I have a iMac we purchased last year (27inch, 32GB Ram, 512GB Flash Storage, OSX 10.9 Mavericks) with Adobe CS6 installed on it. About 2 months ago our Graphic Designer started having problems where when she went to save a Photoshop file the Mac would freeze up and just show the spinning pinwheel, after this happens we are unable to to even shut the system down and have to resort to holding the power button until it shuts off. Now this doesn't happen every time and we went almost a month with a problem but it has started back up and is happening multiple times a day. We have tried re installing CS6, creating a new profile for the user, deleting the library folder, saving to the desktop instead of a network location but nothing has seemed to do the trick. I'm a Windows Sysadmin so I'm out of my depths here and my poor Graphics Designer is getting really upset. Has anyone out there every had something like this happen??
                             Forever Grateful for any help that could be given -Giles Marsha

    You are in the wrong forum;  You actually need Photoshop forum at this link:
    <http://forums.adobe.com/community/photoshop?view=discussions>
    Hope you can repost your question at the correct link.

  • Photoshop & InDesign CS3 Crashing when Saving to Network

    Hi,
    Photoshop & InDesign CS3 crashes whenever I try to save a file over the network to a shared computer we are using as a server.
    SPECIFICS
    I'm running Leopard 10.5.2
    - I have tried reinstalling the entire Creative Suite
    - I did not reinstall Version Cue
    - Tried deleting the com.adobe.mediabrowser.p.ist and Photoshop.plist preferences.
    ALSO:
    - If I create a new file on my computer and then immediately save it, it usually does not crash on the first save. But after I do a few things to the file and then try to save again, it hangs up.
    -I am unable to force quit Photoshop; I have to do a hard reboot.
    Adobe tech support believes it is a network problem. If so, what needs to be done to fix the network?
    Thanks in advance for your help.

    I've heard rumors of the "don't work from the server" thing from our IT department a few times but now I'm seeing it for myself. They are now using this thread as the reason our machines are experiencing so many crashes and errors again. Basically chalking it up to us working off the network is the culprit since they can't find anything else wrong. and since it's not supported by Adobe then were doing it wrong. But none of the workflow solutions we've looked seem faster than just saving to a network. So I'm a bit at a loss...
    How are people dealing with the time it takes to copy files from the server to local and back again. How are people integrating this into workflow's where multiple people need to see and work in the same document multiple times a day?
    A large part of our workload is sometimes thousand page catalogs, mostly our files are 15-25 meg InDesign files and might get up around 50 megs or so and be linked to as much as 5 gigs of image data in the extreme. I can't imagine how much time that would take to copy and work and then copy back, then if someone else were to copy and work and copy back, etc... It's almost like we'd have to copy each section to one computer and make everyone play musical chairs to come and work on the file when they needed too so we only had to copy it from the server once!
    I've done a few catalog covers where the working files sometimes got up over 4 gigs, (and yes with something like this I was working local), but there were days where saving my work back to the server was like 45 minutes, a few times I had issues with the save and I'd be there screwing around for an hour and a half to make sure my work was backed up on the server. I can't imagine having to go through that every time I needed to work on a large Indesgn file that had 4-5 gigs of linked images.
    Does everybody really work this way...? Or is there a magic network setup that allows a sane server side workflow? I know my IT people are compotent profesionals, but perhaps they just haven't heard the latest and greatest for Network CS Suite set up???
    Personally, every time we get new boxes on our desks everything runs great for 6-8? months and then slowly but surely things get buggy and the next thing you know there's smoke coming out of your Dell. They say they fixed it and replaced the damage but the errors continue...
    Anyway, I'm really shocked that working over the server is a no no. Unless you had a very small work group I think this must be a nightmare!!!

  • Photoshop Elements 8 crashes when saving/opening file

    Hello,
    Since a day or two my PSE 8 crashes when i want to save or open a file.
    It just closes without a crash reporter.
    Is there anyone who can help me with this?
    Regards,
    Djmaster329

    I am using a macbook pro running OS version 10.9.  My version of Adobe Elements 8 came free with my purchase of a Wacom Bamboo drawing tablet.
    I have the exact same problem.
    - Creating a new blank image and saving it causes a crash.  However, saving an existing image does not.
    - Using the (File > Open), (File > Save) and (File > Save as) menu options causes a crash.
    - Using the File > Save for web causes a crash as soon as I confirm.
    So, I create a new blank image in Gimp with the dimensions that I want, export it as a .psd file, and open it by right clicking the blank .psd and selecting (Open with: Adobe Photoshop Elements 8).  At this point, (File > Save) and (Command-S) save the image without causing crashes.
    However, it's anoying that I have to use two programs to make one image.  PSE 8 synergises well with my drawing tablet, but Gimp can create new images.  It's really frustrating.
    I think I reset my PSE preferences properly, but I'm not sure.  Is there supposed to be a dialogue box confirming that my preferences have been reset?  I'm not seeing one.
    I'd really appreciate some help regarding this issue.  Perhaps I should submit a ticket to Adobe support.  Can I do that?  I'm new here.
    Thanks everyone for taking the time to read this long post.

  • Photoshop over-saturating images when saving for web

    I've spent most of the day recalibrating my monitor.
    I now use a gamma setting of 2.2, and target white point of D65.
    My color workspace is sRGB IE661966-2.1.
    I'm using Photoshop CS3.
    So I've tried converting an image (even though I am already working in the same color workspace) to sRGB IE661966-2.1 and when I do a Save-for-web, Adobe gives me an over-saturated image.
    Now, while in Photoshop I move the save-for-web window lower so I can visually compare the image in photoshop to the one presented in the save-for-web dialog, and they are still different.
    I am at loss.
    I could understand if I went to another computer and viewed the image, or went to another browser and viewed the image, but even in Photoshop, I'm seeing oversaturation.
    To compensate, I've been desaturating my images, but this is frustrating, as I feel it should work.
    Can anyone shed some light on this matter?
    I'm running OS X v. 10.4.11
    a dual processor Intel dual-core 2.66GHZ zeon
    2 GB RAM
    Monitor is a Dell 2407WFPHC

    >> I wouldn't want the other apps to assume sRGB for an untagged image, because
    That's a fair opinion...[I] would want an option to set an RGB Default profile in ColorSync, though, because the 'high-gamut' monitor I had here whacked out Finder, Preview, iPhoto color, and that setting would 'fix' the problem across the Mac OS.
    The last time I saw this ColorSync RGB Default option was in 10.3x
    http://www.gballard.net/psd/cswfi/panthercs.jpg
    But according to Apple's John Gnaegy, when I asked him WHY that setting wasn't working here:
    He said, "The ColorSync panel> Default Profiles tab headline is wrong.
    "I certainly understand why you would think (that ColorSync's RGB Default setting is Assigned to iPHOTO documents that do not contain embedded profiles), but that's not what happens. Untagged images are instead represented by the profile of the preferred (Default) display," said John.
    It appears some people at Apple understand the issues -- default 1.8 gamma, default monitor RGB, trying to set up ColorSync option to set a Default RGB -- but it also seems like Apple is very slow and stubborn to change...

  • Why do I get corrupted JPEGs when saving images in Camera Raw, CS6, Mac 0S Mavericks

    I occasionally get corrupted JPEG files when processing RAW files in Camera Raw. The images will have lines of pixels that ar out of line, and or whole sections will be truncated and show white or black. I'm using PS CS6, Camera Raw 8.6 on a Mac with OSx Mavericks. Not sure, but it might have something to do with the Bridge Cache, which also acts up when it's getting full. Anyone else have this problem, or any advice.
    Thanks!

    right click on the jpeg (the other mouse button then you use to click with) or on trackpad, hold down control and click, in the menu that pops up, click on "get info" next, if the box labeled "locked" is checked, uncheck it. Down at the bottom, there should be a box with your user name, "staff" and "everyone". to the right of this are options to change these you may need to click the small padlock icon and enter in your password. then change all of the permissions to read and write.

  • Photoshop CS3 suddenly freezing when Saving

    Can someone help me? I've been running photoshop cs3 successfully up until yesterday when after working on layers and cropping etc, i go to SAVE and suddenly it freezes up. I've got 4 RAM, plenty of space on my harddrive. (i use external drives) I did a few small steps yesterday under preferences, and even uninstalled an reinstalled. Still doing same thing. Any advice? thank you.

    Try resetting your preferences as described in the FAQ.
    http://forums.adobe.com/thread/375776?tstart=0
    You either have to physically delete (or rename) the preference files or, if using the Alt, Ctrl, and Shift method, be sure that you get a confirmation dialog.
    This resets all settings in Photoshop to factory defaults.
    (A complete uninstall/re-install will not affect the preferences and a corrupt file there may be causing the problem.)

  • Why Such a Huge Photoshop File Size Increase When Saving In CC from other versions?

    Hello,
    I have limited experience in Photoshop, and am working with a file with two other people.  We are creating web comic pages.  The line artist and colorist are both using CS 6.  I have CC.  The file I receive from them is around 238MB.  If I open it and make even the slightest edit, Photoshop will not save it as it warns that the file size is too large (greater than 2GB!).  How does this happen?  Is it something in my preferences that causes 10x increase in file size?
    Any help is appreciated.
    Thanks!

    Thanks for replying. First I didn't have this problem in the beginning. I do the same in CS5 and I can do it with no problem.

  • Photoshop CS4 "Freezes" when saving as a JPEG

    I have been using Photoshop CS4 with SnowLeopard and my MacPro for months now without a problem. I save multiple images everyday, often as JPEGs for the Web. But today, out of the blue with nothing changing (no new updates, or plugins), Photoshop "locks up" when saving a JPEG. I can still move the curser arrow, but everything is dead and the file did not save. I have to hit ESC just to get PS back online. I can save other file types, no problem.
    Has anyone experienced this? Any help or solutions? I have the latest version of PS CS4.
    (Note: If I go under Save for Web & Devices I can save it as a JPEG, but seems like an less than timely run-around)

    I have not experienced that problem, but with all unexplainable Photoshop-problems You might try trashing the prefs (after making sure all customized presets like Actions, Patterns, Brushes etc. have been saved and making a note of the Preferences You’ve changed) by pressing command-alt-shift on starting the program or starting from a new user-account.
    System Maintenance (repairing permissions, purging PRAM, running cron-scripts, etc.) might also be beneficial.

  • Resolution Issues in Jpeg Options when Saving

    Hi, I am suddenly experiencing an issue when saving Jpeg files in photoshop CS4. I work on hundreds of files at a time. I open the Jpeg photo, edit it and when ready hit 'save' and 'return' to accept the settings which are usually set by default to 12. But recently Photoshop is randomly selecting a lower compression in the Jpeg options when saving. It is only on a few random images though. If I open the original, re-edit the image and save it again, then it usually saves at 12 on the second attempt which is even more strange... Can I lock the settings to by default save all files at level 12 to avoid having to re-edit the shots I happen to miss spotting the change in compression on?
    And doesn anyone know what would prompt photoshop to suddenly save certain images in a lower res automatically? I am wasting hours re-editing and double checking files which is very frustrating. Please help!!
    Thank you in advance for any asdvice.

    Hi Mark, thanks for your reply but the images I'm working on are all shot with the same settings and exported out of iPhoto with the same settings before imported into Photoshop for editing. So they haven't yet been saved in Photoshop. My problem is when I save the file after editing, photoshop is automatically selecting 0 Jpeg image quality rather than 12, which is what it generally selects, except now on these few select images? It's all a bit bizarre because I have used this method for 4 years and now all of a sudden I am having this problem. I assumed I had hit a shortcut somewhere and adjusted the parameters unintentionally. It's rather hard to explain  but I hope that makes more sense. Thanks again to anyone who can help, I'm deseperate to get to the bottom of this....

  • JPEG is corrupted when saved in B&W from RAW

    Hi,
    today I ran into this issue when saving black and white pictures from Raw file.
    Camera RAw 7.3 opens normally just like always and lets me save picture in color.
    It lets me save picture in BW, but the JPEG tha comes out is corrupted file that looks like this (see below):
    When i try to open that corrupted JPEG in Photoshop 6 I get an error message saying:
    "The embedded ICC profile cannot be used because ICC profile is invalid. Ignoring the profile. "
    After clicking "continue" on the error message I am able to load the picture in PS6- however when i go to Image>Mode picture is appearing a RGB, not a Greyscale as it should be.
    Any ideas why this is gappening an how to fix it?
    It seems that new Raw Plug In is casuing it- I uninstalled Photoshop, installed Camera Raw 7.2 and its seemed to be OK. As soon I upgraded to 7.3 I get the same error.
    is there a way to downgrade it to 7.2 without uninstalling PS6? Manual download and rewriting 7.2 over .3 doesn't seem to work.
    Thanks!

    I can confirm the issue...it's been reported. In the meantime, actually opening the image into Photoshop and saving as a JPEG works...you could simply open the image into Photoshop to save as JPEG or adjust the images in ACR and then use Image Processor from Bridge. And no, you can't easily install 7.2 over 7.3. Since both are not currently offered as seperate downloads (updater only) you would have to find the 7.2 download...the Mac and Windows downloas are mentioned in this thread.

Maybe you are looking for

  • In RG1 ,Unit of measurement is KG,User want to change as MR

    Hi Experts, In RG1,user want to change unit of measurement as KG to MR.Now its showing KG but in billing there is unit of measurement is MR .I have checked material master.I found following: base unit of measurement is KG sales Unit: SM while creatin

  • Please help me about Work Schedule.

    Dear all, On my client have schedules are below : -   Form Monday to Friday: Is working day for all employees except IS department and Driver Group and  Saturday, Sunday are  Holiday. -   IS Department : Employees work 5 days a week with rotating bas

  • What is the audio throughput via usb on the new macbook air?

    I just purchased a new macbook air and was wondering what kind of audio that I would get as output from the computer via usb. In particular I am interested what kind of audio I am sending as output to my Bose T1 Tonematch Mixer?

  • P/N, S/N, and other battery numbers - 0A36303 for W510 70++

    I recently bought a 9-cell/70++ replacement battery for my 4318 W510, so I'm trying to confirm that it's proper for the system and a legitimate Lenovo product. I don't see any obvious errors, but I can only find one Lenovo document (an environmental

  • Pub and Sub question

    I am in the process of developing interface where source system will pubish the data in Que and target system will subscribe it. The question I have when I create a Que in source system how this que become visible to target system. When I am creating