File Compression - any relation to Photoshop?

Does anyone know if the 'quality' slide selector in Aperture's export dialogue (eg, create an exported file 2048 px at quality '8') bears any relationship to the file size/file quality box you get when you do a similar thing in Photoshop? In my rough tests it looks like Aperture is doing very little compression compared to Photoshop. The resulting Ap file sizes are waaaay larger than PS. Thanks in advance to anyone who can help me.

Similar Messages

When opening a file of any type in Photoshop (CS4), the windows will not appear in Ps.

When opening a file of any type in Photoshop (CS4), the windows will not appear. Photoshop will open and I can see the layers on the right but the document window will not come up no matter what I try. I try closing down everything, double-clicking a layer, opening multiple windows, etc.. Any thoughts?

Can you post a screenshot of your entire Photoshop screen with a file loaded in and the layers panel showing?
It helps if we see the same problem you are seeing
Gene

File size when jumping to Photoshop

When I open a NEF raw file from my Nikon D700 in Photoshop as 8 bit it opens at 49.5mp, but when in Lightroom, after working on the same file, if I jump to Photoshop, using Command-E, then the file opens at 32.5mp. Any idea why this is, and how can I get the file to 49.5mp when opening it through Lightroom. Thanks, Neil

Alamy's size requirement are rather outdated these days, but is based on the standard sizing for a image printed as a double page spread in a magazine as a guidance for what could be achieved by a scan of a 120 negative or transparency and high quality 35mm negatives. They have never updated it for digital files and just expect people to interpolate from most cameras (which natively produce smaller files) As they offer a range of sizes for all there files they set this as a minimum. The quality control checks then examine for all other factors.
I think Alamy stick with them as it is a good test of the submitting photographers understanding of image formats. I understand from the quality control people that large numbers of people try to upsize files as jpgs until they get to 40 odd MB (which is massive) and then get annoyed when they won't upload! Lots of files also get rejected due to a failure to understand the no sharpening rule and switching off input sharpening......rather than output sharpening.
Alamy sells to a wide range of clients and I suppose many don't want to interpolate themselves.
It is still far more sensible than agencies that still insist on such and such dpi!
By the way, the 95% setting for jpg output with a decent file will always produce a jpg small enough to upload to Alamy and any other agency without any potential deterioration in image quality if correctly processed, so I would suggest this as your standard setting when sending file to agencies. A 50 MB file compressed at 95% in LR will be between 4.5 and 7 MB dependent on the complexity of the image.
I submit to several agencies, magazines and newspapers. All have their own requirements, which I just meet every time. The customer is always right as long as they pay the bills. After a while most agencies know your work meets their quality thresholds and don't bother checking. Alamy is unusual in that the size thing is determined by software, so if this is wrong it doesn't even get to go to quality control. On your first hundred or so submissions every file is checked by a human being. Once you have regularly met the standards they don't usually bother checking any more and just pass the uploads; but I understand they still make the occasional check on random files to make sure. As they are a nice source of regular income and don't undercut proper agencies (unlike the open to all type agencies) I am OK with Alamy's quirky rules. There is even a plug in which does it all for you!

Applescript:: PICT File Compression doesn't work [?]

I have tried many options for getting Pict file compression to work via scripting but to no avail. Can anyone confirm if this works in PS CS4?
PICT file options I am trying to get to work are: {class:PICT file save options, compression:maximum quality JPEG, embed color profile:false, resolution:thirty two, save alpha channels:false}
All option **except compression seem to work.. :/
Example code:
set newPictFilePath to ((path to desktop folder) & "newPictFile.pct") as string
tell application "Adobe Photoshop CS4"
set docRef to current document
set photoshopSaveFormat to PICT file
set photoshopSaveOptions to {class:PICT file save options, compression:maximum quality JPEG, embed color profile:false, resolution:thirty two, save alpha channels:false}
set kSavedDocument to save docRef in file newPictFilePath as photoshopSaveFormat with options photoshopSaveOptions appending no extension with copying
end tell

Hello,
I did not have any problems with the script you posted, but I ran into issues when my document was not flattened, or was not RGB. After I added that to the script, everything seemed to work.
I also have a habit of telling a document to save instead telling the app to save a document, but that might just be my quirk.

Help, i am trying to print my JPEG file that i created in photoshop at a photo lab but it is coming out like an X-ray. I have printed these files before so i have no idea what i am doing wrong.

Help, i am trying to print my JPEG file that i created in photoshop at a photo lab but it is coming out like an X-ray. I have printed these files before so i have no idea what i am doing wrong.
Could it be something i have done in my settings?
or when i am saving the file to JPEG?

Basically you're approaching this the wrong way around. What you need is the extreme sections to be quieter, not louder. The problem with moving the lower end of the audio is that you'll move the noise floor too, and get what's generally referred to as a 'pumping' effect. So what you do is to use a compressor to tame the peaks, and leave the lower level sound alone. When you've done that, you amplify (or normalize to a level you can determine) the whole signal. So the noise floor will be higher, but constant and not pumping. 'Match Volume' is a completely different tool for setting the overall levels of different tracks so that they sound approximately the same - it doesn't even begin to do what you want.
If it's music you are treating, then I'd almost certainly use the multiband compressor, because you get less artefacts with this. You need to experiment with the threshold levels, and almost certainly not use a massive compression ratio - 3:1 or 4:1 should be sufficient (although it's hard to tell without actually hearing the audio). You can tell what it's doing at any given point because the downward meter indicates how hard it's working. In theory you can apply make-up gain with it as well, but personally I leave that until everything's treated and use the 'Normalize' tool to set an absolute max level.

File Compression Problem

Hello all,
I'm having a strange file compression problem with CS5 on our new Mac Pro. We purchased the Mac Pro to scan and process images, but the JPEGs and GIFs we create from this computer are much larger than they should be when closed (e.g. images that should be compressed to 6KB are reading as 60KB, and the file size is often smaller when opened than closed). Furthermore, anytime we use these image files in other programs (e.g. Filemaker Pro) the inflated file size will carry over. What's even more puzzling is that the same files that are reading as 60KB on our Mac Pro will read correctly as 6KB from a PC. Similarly, if we embed these images -- that were created on the Mac Pro -- into Filemaker from a PC, the image file size is correct. We cannot use the compressed files we create on our Mac Pro because the inflated file size will be passed on to whatever application we use on the Mac Pro (except for Photoshop).
We have been processing images for years on a PC and haven't had any troubles with this. We were thinking for a while that the problem was with the Mac operating system, but after many calls with expert Apple advisers it seems like Photoshop for Mac has to be the issue. We have already tried reformatting and re-indexing the hard drive, and at this point there is nothing else that can be done from Apple's end. The last expert I spoke with at Apple said that it sounds like the way Photoshop for Mac compresses files and how Mac reads file sizes is very different from the way Photoshop for PC compresses files and how Windows reads file sizes. If he was correct, and there is no work-around, we'll have no other choice and will have to return our Mac.
Has anyone else experienced this before? The experts at Apple were thoroughly confused by the problem and so are we.
Thanks,
Jenny

This has nothing to do with compression.
Macintosh saves more metadata, and more previews than Windows - that's one part.
Macintosh shows the size of the file on disk, including wasted space due to the disk block size - that's another part. (look at the byte count, not the size in K or MB).
When you upload the files to a server, or use them in most programs, that extra metadata is lost and the file sizes should be identical.
I can't believe that your advisors spent any time on such a trivial issue...

Firefox 3.6.10 crashes each time I try to open a PDF file? Any suggestions?

Each time I try to open a PDF file from any website, Firefox (3.6.10) crashes. No error messages--just closes abruptly. For add-ons, I've got Personas 1.6.1, United States English Dictionary 1.0.0, and WOT. I've got the Adobe Reader 9 and Foxit 3.3.1.0518. The crashes of Firefox occur with both PDF readers. I did go through the posted solutions for PFD related crashes in the FAQ section but those steps did not resolve the problem.

Does that only happen if you open the PDF files in the browser or also if you open the PDF files in the standalone program by disabling the plugin?

Canon CR2 Raw files won't open in Photoshop CS4

I'm using a Canon EOS 600D (aka EOS Kiss X5), Photoshop CS4 (ver 11.0.1) with Camera Raw 5.7.0.213.
CR2 Raw files won't open in Photoshop, though the thumbnails are clearly visible and open in Windows Explorer.
Any suggestions?
Thanks

Yes, absolutely all of the quality and dynamic range is retained in the DNG, because it is still raw data.
Outside of upgrading to Photoshop CS5, which can open your files directly with Camera Raw 6.4.1, your only choice is the extra step of converting the .CR2 files to .DNG with the free DNG converter.
While you'll get all the quality your Camera Raw 5.x converter can deliver, you should keep in mind the Camera Raw 6.x converter has an entirely new, additional "2010 process" for converting raw images, which (depending on your settings) can actually deliver a higher quality conversion than the one you're getting with Photoshop CS4. I think it's worth the cost of the Photoshop upgrade, personally.
-Noel

Image processor: "No source files could be opened by Photoshop."

I am also getting a "There were no source files that could be opened by Photoshop" warning when trying to save jpegs of open images (opened from a PDF) using the image processor.
Here is what I'm doing:
1. Open multiple pages of a PDF into Photoshop
2. Run the Image Processor with settings:
- Use open images
- Save to "select folder location" (choose a valid location)
- Save as jpegs
3. Run
And it gives me the warning. How can the files not be opened by Photoshop. They already are?!?

JJ, thanks for the response, and my guess is you are correct. It would be nice if Adobe would change this. My whole intention of using the Image Processor in this case was to "batch save" all the open files. As far as I know, there isn't another way to do that without creating an action or other such nonsense. ; )
At any rate, thanks for your input and explanation. At this point, I suppose the issue is as good as solved.

Good afternoon ladies and gentlemen! My question concerns the impossibility to open RAW-files directly from the program Adobe Bridge. At the moment when you open a RAW-file from Adobe Bridge by double-clicking, RAW-file is opened only in Photoshop. In t

Good afternoon ladies and gentlemen!
My question concerns the impossibility to open RAW-files directly from the program Adobe Bridge. At the moment when you open a RAW-file from Adobe Bridge by double-clicking, RAW-file is opened only in Photoshop. In the settings Adobe Bridge - in "open RAW-files by double-clicking in Adobe Camera Raw» box is checked. When you try any changes in the settings Adobe Bridge system displays a message:
Bridge's parent application is not active. Bridge requires that a qualifying product has been launched at least once to enable this feature.
The entire line of Adobe products on my computer updated to the latest updates. Previously, a family of products Adobe Photoshop on your computer is not set. Computer - PC, Windows 7 Enterprises.

<moved from Adobe Creative Cloud to Bridge General Discussion>

I cannot open any photo in Photoshop CC 2014 after upgrade the application and drivers of video-card.

Since I have made an upgrade of Photoshop CC 2014 I got a lot of problems.
At first, I could not open any pictures in Photoshop. It works only if I disable "Use Graphic processor". I installed a new driver for my video-card, but it did not help. I use AMD FirePro V4800 for 10-bit colour.
I had to return the system to the restore point (before the upgrade), then it worked somehow, but not stable. ACR from time to time had a blue screen with a white cross.
Now I tried to install drivers for my video-card again, but it resulted in the same issue: Photoshop cannot open any photo. (Other converters and editors and also a new Lightroom work well).
I use Win7x64, i7 2600, 16 Gb RAM, two SSD's, AMD FirePro V4800. I have never had any problems before the upgrade. And I do not want to reinstall Photoshop because I would have to reinstall a lot of plug-ins, I have already lost a whole day.

Glad it's not just me!
Interestingly, when I spoke with Apple, I tried it in a new user account and the problem went away. Apple said to speak to Adobe which I have done and after deleting settings/prefs again the problem remained. Adobe say as it's fine in a new account then it's an Apple issue not Adobe.
I did find a workaround for now though, when using file - open, set it to list view instead of column view - this fixed my problem but sadly I'm used to working in column view so it's not ideal!
I also got the same error message when trying to replace a set of brushes yesterday too. I need to go back to Apple now but just need to schedule some time to sit and troubleshoot!

I get the error message in QuickTime "operation stopped the operation is not supported for this media" most times when I try and export an .AVI file as something else (.m4v). I have not touched the file in any way (no trimming, clipping or other editing)

I get the error message in QuickTime "operation stopped the operation is not supported for this media" most times when I try and export an .AVI file as something else (e.g. .m4v). I have not touched the file in any way (no trimming, clipping or other editing), all I want QuickTime to do is export the file in a compressed format. Bizzarely, if I shutdown and open QuickTime many times I can occasionally export a clip as another format (maybe one in 10 times). I have seen that other users have had a similar problem after clipping files in QuickTime but this seems to be a slightly different bug in that all I do is open the file and then try and export the file as is - either way, this is a very annoying bug

@Z_B-B, thank you for taking the time to respond to my cry for help. However, the link you supplied does not address the problem: I am not trying to export from Final Cut Pro to QuickTime, I am trying to export from QuickTime to the rest of the world (like people's iPhones and Ipads) in .m4v format (so I am not emailing my freinds such huge files).
If I were to spend hundreds of Dollars on a copy of Final Pro I could export directly from there and not have to bother with QuickTime, but I do not take enough video clips to justify the cost. I must say that I never had any of these problems before I decided to switch from Snow Leopard to Mountai Lion.

Occasionally when opening a file (usually a pdf) in Photoshop, in attempt to convert it to a jpg, I

Occasionally when opening a file (usually a pdf) in Photoshop, in attempt to convert it to a jpg, I get an error message that says “Could not complete your request because of a program error.” What does that mean?

Hi there! Because the forum you originally posted in is for beginners trying to learn the basics of Photoshop, I moved your question to the Photoshop General Discussion forum, where you'll get more specialized help.
To help others help you, please read through this article and provide any additional relevant details.

Rasterization of complex postscript-file crashes in 64-bit Photoshop CS5

Rasterization of complex PS-file crashes in 64-bit Photoshop CS5
I have a variety of complex postscript files that were created in Adobe InDesign CS3 and CS5 through "print to postscript file". I try to rasterize these files in Photoshop CS5 (64 bit on Macintosh) and it crashes Photoshop even before the dialog box comes where one has to specify the dpi for rasterizing. If I use Photoshop CS3 or Photoshop CS5 with 32 Bit opening, it does not crash; and in this case I can rasterize a 100cm x 160cm format with 300 dpi.
If I reduce the complexity to near triviality it works with the 64 bit version.
A major reason why I bought CS5 was because I thought that with the 64 bit version I can handle rasterization of large files better: there are a few minor artifacts created by rasterization in Photoshop 32 bit version which are presumably due to some memory problems; I thought the 64 bit version can solve it. But now it turns out that the 64 bit version cannot handle complex files at all.
If I use Distiller to convert the postscript-File into a pdf file, then the 64-bit version does the rasterization, but there are some reasons why I prefer the rasterization directly from the postscript file.
Is that a bug of the 64 version?
V.S.

I did a lot of testing in the meantime since we have often the task to printout large charts with complex content on plotters of medium size printing companies who need tiffs since they cannot handle pdfs with complex contents.
It turns out that for large charts with complex content the method to export from Indesign to pdf with PDF/X-1a profile and subsequent rasterization in photoshop to create the tiffs sometimes produces a few minor artifacts; mainly very thin white lines that you see in the printout. Also it is not good if your file contains graphics for which PDF/X-1a profile sometimes does not yield the desired high quality. (In addition the pdf file has a lot of display artifacts visible on screen but not manifesting in the rasterized photoshop file.)
The use of the "High Quality Print" profile (instead of PDF/X-1a profile) makes it worse since sometimes semi-transparent objects are printed as 100 percent solid. The solution in this case is to change the Acrobat 5 compatibility of the "High Quality Print" profile to Acrobat 4 compatibility, this solves the semi-transparent problem, I don't understand why, but it does.
On Macintosh one can print to pdf (instead of export to pdf), this solves all problems with artifacts as far as I can judge; however "print to pdf" has PDF/X-1a profile and I don't see any direct way how to change it to "High Quality Print" profile. Presumably I would have to locate somewhere in the Library > Adobe Application Support > Adobe (on Mac) the presets for "print to pdf" and change it if possible.
The easiest way on Macintosh that gives no artifacts is for large charts with complex content to "print to postscript" (with Adobe PDF 9.0 PPD), then use distiller with any suitable profile, like "PDF/X-1a-2001" profile or "High Quality Print" profile, to produce a pdf. This pdf looks fine on screen and simultaneously when rasterized with Photoshop (for example the 64 bit version of CS5) gives you a good photoshop file.
You may be right that the workflow
Indesign > print to postscript > pdf via distiller > rasterize to photoshop file
is outdated for simple and medium complex projects, but for those really complex large charts this is the only viable way to my knowledge; I also know that some of my colleagues use this sometimes for complex projects when export to pdf creates artifacts.
V.S.

I've encountered saving photo that turnout as a blank file with no picture on Photoshop Elements 9.

I have encountered saving my photos that turnout as blank files with no pictures after some manupilation on Photoshop Elements 9.
Uninstalled and reinstalled the program but still facing the same blank files. Any advice of how to rectify the problem. Thanks.

Are you renaming these files when you save? Are you using a character like a dot or slash in the name (my.photo.jpg, for instance)?

File Compression - any relation to Photoshop?

Similar Messages

Maybe you are looking for