Exported jpegs not read by CS2

When I export a jpeg to my desktop at level 7, 480x480 size, Preview and Bridge can see it, but Photoshop CS2 cannot open it. I get this message: Could not complete your request because of a program error. Is this normal? Roger

roger
of course this is not normal. at this end, photoshop cs2 and cs3 open a jpg (compression seting 7) without problems. for a test i would output your file with a higher compression setting such as 10 (resulting in lower compression effectively). for image retouching however i would always output tiff or psd.

Similar Messages

Exported Jpegs not readable by Powerpoint via finder

When I export from Indesign CC 2014 as JPEGs the files are greyed out when importing into other applications, i.e. PowerPoint 2011.
It seems indesign isn't creating a proper Jpeg with correct meta Creator & Type data so other programs know its a .jpg.

I've tried all RGB, CMYK & Grey, no luck.
Looks like a bug. There is something wrong with exported jpegs at least on OSX. If I get the file type with AplleScript an exported jpeg returns ????, while a PS jpeg returns JPEG.
tell application "Finder"
set myFile to choose file with prompt "Select a file"
display dialog file type of myFile as string
end tell

IPhoto '11: Export (JPEG) size not working

I keep all my photos taken with iPhone 4 in iPhoto '11 ver 9.42 (710.42).
It is a very excellent app to mange my photos.
Recently I need some photos from iPhoto for the use in my web project.
So I export them in JPEG, choosing "high" quality and "large" size.
Yet, some of the exported JPEG are still in the original size of 2592 x 1936.
I have tried other size options, but those (same) JPEG are always in the original size.
What happened?
I appreciate if gurus here could help me.
Thank you very much.

If the pref file was damaged your test library would have exhibited problems also. Try the following:
Using iPhoto Library Manager to Rebuild Your iPhoto Library
Download iPhoto Library Manager and launch.
Click on the Add Library button,
navigate to your Home/Pictures folder and select your iPhoto Library folder.
Now that the library is listed in the left hand pane of iPLM, click on your library and go to the Library ➙ Rebuild Library menu option
In the next window name the new library and select the location you want it to be placed.
Click on the Create button.
Note: This creates a new library based on the LIbraryData.xml file in the library and will recover Events, Albums, keywords, titles and comments. However, books, calendars, cards and slideshows will be lost.
Note: your current library will be left untouched for further attempts at a fix if so desired.
Also there's a new update for iPhoto, 9.4.3. Wouldn't hurt to update to that version.

LR not reading Canon CR2 and JPEG files

I have been a long time user of Lightroom, now have LR 3.4 installed. No serious problems so far and I love using it. For a computer set up, I use a one year old Apple desktop with Lion installed. My problem is that this past week, my LR 3.4 will not read my Canon files, either CR2 or JPEG format. I have tried two different cameras ( 5d Mark ii and 7D ) two different card readers and several different memory cards. LR sees the files, starts to upload them and then on concluding its routine says it cannot read the file format. I am patching together a solution by importing the files through iphoto, exporting them to a file in my LR hierarchy file and then importing them into LR.
Clearly, this is not good. Has anyone had a similar problem? Can anyone offer a solution?
Thanks

Given I was home today with free time, I called Adobe support. They took charge of my screen and helped me through the issue. It turns out that when downloading, I was not clicking on the specific file location for my photos. All that I had to do to make the download work was to click on the intended file location. Although it was highlighted before I clicked on it, the clicking on it made the downloading work. I don't ever remember clicking on the specific file location in the past but that small step is now going to be in my file importing methodology from here on out.
I would like to send flowers to the woman who helped me through the issue. She was very good.

Not reading Canon Files both RAW ( CR2) and JPEG

I have been a long time user of Lightroom, now have LR 3.4 installed. No serious problems so far and I love using it. For a computer set up, I use a one year old Apple desktop with Lion installed. My problem is that this past week, my LR 3.4 will not read my Canon files, both CR2 and JPEG format. I have tried two different cameras ( 5d Mark ii and 7D ) two different card readers and several different memory cards. LR sees the files, starts to upload them and then on concluding its routine says it cannot read the file format. I am patching together a solution by importing the files through iphoto, exporting them to a file in my LR hierarchy file and then importing them into LR.
Clearly, this is not good. Has anyone had a similar problem? Can anyone offer a solution?
Thanks
Tom

You might get more help in the Lightroom forum than here in the Photoshop forum.

Problem: 'Could not read from source' when exporting project.

Hi everybody
I am using Adobe Premiere CS4 on my MacBook Pro 15'' (i5 processor, 4 GB RAM, 500 GB Harddisc, 256 MB video memory (high-clockspeed))
Everything works well except of one big thing, every time when i try to export my finished project the Media Encoder tells me always the same thing directly after pushing the start button. 'Could not read from the sorce. Please check if it has been removed or deleted'.
I tried removing any offending plugins, i fixed the disk permissions.. But it all doesnt matter anything.
No matter what i try to export, no matter in what file format. It just doesnt work. I even tried exporting a project which only contains a video file of 5 seconds without anything more but it just doesnt work. Its impossible that i have touched or modified or replaced any source files...
Some help would be very very appreciated!!
Martijn

Welcome to the forum.
Perhaps this Adobe KB Article will be able to help you.
Good luck,
Hunt

Premiere Pro CS4 Export fails with Media Encoder CS4 "Encoding Failed"," Could Not Read From Source.

There has never been a history of Adobe CS3 installation on the brand new MAC Pro I am using prior to installing Master Collection CS4, despite other posts claiming that chief cause of this issue is a previous CS3, Beta or trial installations of previous versions. I simply had a straightforward installation of CS4 and have had trouble since day 1.
I have uninstalled and reinstalled Master CS4 three times, two times with the action script cleaner for CS4. I tried changing Adobe Cache folder locations to alternative drives. I ran shift start many times to correct any inconsistencies and corrected for permissions using disk utilities repeatedly. All updates have been installed and I am still getting the same error when exporting my timeline to Media Encoder CS4, be it a large High Definition project or a small one consisting of few stills.
No matter what presets I chose, the job appears as one of the items in the render qeuee of Media Encoder CS4 and sits there with the status WAITING until i hit Start Queue. When I do, it still says WAITING under Status and at the bottom corner of the window it reads : Loading "project name.prproj" and after an average of about 6 minutes, a yellow caution sign appears. No render whatsoever takes place. When I click on the yellow caution sign, it reads a log of all errors in connection with each job, including the ones that have gone before it. Here is one:
Start of the Error Paste
- Source File:/users/myname/Library/Caches/TemporaryItems/test.prproj
- Output File:/ users/my name/Documetns/Adobe/Premiere Pro/4.0/Sequence 01.mov
- Preset used :NTSC DV
- Video:
- Audio:
- Bitrate:
0 Encoding Time: 00:33:01
Sat Mar 21 17:12:25 2009 : Encoding failed
Could not read from the source. Please check if it has moved or been deleted.
END OF ERROR Paste
Please any gurus out there know how to troubleshoot this damn thing on Mac, I really appreciate it. I have not yet encountered any posts of Mac owners with no previous CS3 installation having this issue. I am in the middle of 3 projects with tight deadlines and need your urgent help. THANK YOU!

Hello There,
I resolved the issue through a simple process of elimination. So simple in fact I wonder how I missed it. Since there has been no history of prior CS3 installation on this machine and every conceivable trick was applied to resolve the problem (refer to my original post earlier in the thread) ending in frustration, the problem had to reside in a factor or series of factors that were only present in this machine. Of the two remaining causes different in compare to other machines, I had to look into the possibility of any hardware and/or software conflicts. After all, this very same installation works perfectly fine on my colleague's Apple Macbook Pro and several Windows machines.
It turns out that I had installed Pro Tools on this machine that comes with all kinds of optional plug-ins in the so called ignition pack. One of these optional plug-ins is called IZOTOPE (three varieties include Spectron, Trash and another one that escapes my mind). They were all lite version licenses that would automatically pop up on their own when you would start a program where they had been residing. One such program where an association existed was indeed the Premiere. An annoying dialogue box directing you to buy the full version when you would start the premiere would refuse to go away. Sometimes it would even start on its own culminating in a a permanent dialogue box.
The cause of the problem was right before my eyes and I had overlooked it. Once uninstalled using IZOTOPE clean uninstaller on step 4, the problem was resolved. Projects are now loading very fast into the AME and encoding begins in earnest. I have never had any issues ever since.
Long story short, if you have any plug-ins specially the ones that are loading upon the start of any program or the ones that reside inside the premiere or the ones that start on their own independently, they could be one of the highly probable causes of this error. I have seen other similar posts complaining of plug in folders inside premiere that needed to be moved to resolve the issue for instance the ones that needed to be moved to AE folders. If you are a plug-in admirer, I would suggest to look into them seriously.
On the side note, many combination and causes may lead to the same error. I am not claiming that this is the solution for everyone.
It must also be noted that I applied the trick of creating a shortcut of Premiere (and naming it exactly as such) and dropped it into the Adobe Dynamic LInk folder (even though this was suggested for windows)and have changed the adobe Cache locations to an alternative folder on a separate drive. I haven't been able to establish conclusively if the latter steps are also essential in fixing the error on MAC but I can confirm that since the latter steps were taken before the uninstalling of Izotope plug-ins and i still had issues, probably uninstalling those plug ins or finding a way to move them to a place where they don't interfere (if you absolutely need to keep them) is the one essential step that solved the problem.
Hope this helps.

"Could not read from source" exporting on Mac with CS4

I'm using Premiere CS4 on a MacBook Pro, trying to export a film and getting the "could not read from source" message. I did not have CS3, and I'm not on a pc, so the Windows KB articles and posts don't apply. I've read all the posts I can find on the forums but none of these solutions is helping to date.
Are there any troubleshooting steps someone can recommend to figure out what I need to do here?
Here's the trace, any assistance is MUCH appreciated!
- Source File: /Users/johnchmaj/Library/Caches/TemporaryItems/circle _6.prproj
- Output File: /Users/johnchmaj/Documents/Personal + Projects/Living Universe/Snoqualmie Valley/Valley Breezes Premiere/1circle:introitus/Valley Breezes 6-41.m2v
- Preset Used: NTSC High Quality
- Video:
- Audio:
- Bitrate:
- Encoding Time: 30:44:29
Wed Aug 19 16:52:56 2009 : Encoding Failed
Could not read from the source. Please check if it has moved or been deleted.

I have been having the same issue on my desktop and laptop, although I have Windows XP Professional. Originally had CS3 and then installed CS4. The problem was fixed by uninstalling everything Adobe (even Reader), using the wincs3sclean, and reinstalling the CS4 products. The first time it did't work on my laptop, so I did it a second time and it worked. I don't have Creative Suite, but this still works. Here is the link to wincs3clean:
http://kb2.adobe.com/cps/401/kb401574.html

Installed CS5, now can't export from CS4! Help! "Could not read from the source..."

I installed CS5 but completely ignored the fact plugins were required to be 64-bit. It'll be months before the plugins I require for my projects to be updated!
So I continued editing in CS4 and when I attempted to export with the media encoder it halts instantly with an exclamation mark, the log says :
"Could not read from the source. Please check if it has moved or been deleted."
And yes I'm not stupid, I did my research.
I tried uninstalling CS4 and reinstalling. I tried the shortcut fix. I tried moving my cache files. My extensions are correct.
Right now the only fix seems to be completely removing CS5 and CS4, After Effects just because they share files (?) and all my settings and plugins along with it! I'd rather NOT do that if I can!

Good detective work, and glad that it worked. Now, your cure will be here for us to link to and for others to find. Your title will help direct others to this thread. Job well done.
Thanks,
Hunt

Lightroom 4.1 exported JPEG files are not recognized by Apple Preview App

I just started using Lightroom 4.1 Trial version (coming from Aperture). I exported JPEG versions of some images using an ICC profile. On my iMac running Lion 10.7.5 the pictures do not show a thumbnail, the file on the desktop just shows "JPEG". I could not open the file with the Preview App, but I am able to open it with DPP (Canon software)? Also the file shows that it has 0 x 0 dimentions when I click Get Info even though it is about 25 Megs in size?
The message I get is
"The file “Edit-739820120223Canon EOS 7D.jpg” could not be opened.
It may be damaged or use a file format that Preview doesn’t recognize."
Does anyone know why this is hapening?
Is it a know issue between Adobe and Apple?
Is there a fix for this?
Thanks for help in advance.

25MB is quite a large filesize for a JPG, and this might be either quite a lot of pixels saved at a very "high" quality (not very much compressed), or it may be an extremely large number of pixels saved with medium compression.
While the technical spec of the JPG format imposes an absolute limit on maximum width and height pixel dimensions, some software employs a lower limit above which it considers the file to be invalid. Different programs, different limits, sometimes.
I have encountered this (for example) with pano stitched images using the full resolution of a large number of component shots - where JPG output could not be made, or if made, could not even be viewed as a whole by my standard image viewer (though TIFF was still OK even at still larger sizes).
If Lightroom has been set to a large printed size AND to a high ppi resolution, it is easy to get into very high numbers and very large output files. One should IMO at least question the utility and benefit of using very high ratios of upsampling from a standard digital photo - which may happen in some cases as a result of using the same output settings regardless, when spreading the same data across both small and large scales. If the file that was imported into LR really does provide an unusually high number of pixels expressing lots of detail, then that will better deserve such a capacious output file. Otherwise, each part of the file may merely show a very highly detailed representation, of a very blurry nothing-much-in-particular.
If the JPG has exceeded the viewer's size limits, a reported width and height of 0 may represent an error message, in effect - not actual reality.
regards, RP

CS3 not reading xmp files generated in CS2.

CS3 is not reading xmp files generated in CS2.
If I open a raw file that was adjusted in ACR in PSCS2 with PSCS3 it does not recognize the adjustments that were made to the file.
PSCS3 opens the file in ACR with the default settings and I lose all of the adjustments and crops.
Is anyone else having this problem. If so: is their a fix or a stting I should use?

First. make sure you have updated to Bridge 2.1.0.100.
2nd, Purge the Cache from the TOOLS menu in Bridge.
3rd, Delete and rebuild your Bridge preferences by holding down the Option key (Command+Option, or Command+Option+Shift work as well) immediately after launching the application.
4th, if that doesn't work, make a fresh, new Mac account and log in as a different user.
Then report back.

I have successfully exported subtitles (XML files) from FC version 7 to FC version 6, by choosing Apple XML Interchange Format Version 4. Now the exported subtitles suddenly read in one long line, at the top, not registering any "Enter" keystrokes.

I have successfully exported subtitles (XML files) from FC version 7 to FC version 6, by choosing Apple XML Interchange Format Version 4. Now the exported subtitles suddenly read in one long line, at the top, not registering any "Enter" keystrokes. The same happens even if I re-import the XML file into Final Cut Version 7 (from where I exported the subtitles). Any tips on how to fix this?

You might see if you can bring the xml file into Title Exchange Pro
http://www.spherico.com/filmtools/TitleExchange/
It's a great program and the author was very responsive when I had a problem.
If it reads correctly, you can probably save it back out.
If you want to send it to me, I'll see if it opens.
[email protected]

CS2 Not reading all available fonts

Hello,
I just purchased a new Dell with an XP Professional Downgrade software package and have installed my CS2 Creative Suite on it.
When I open either Photoshop, Illustrator and InDesign, it appears many standard fonts (found in Control Panel / Fonts) , including 'Arial Black' are not available, though on my Adobe Acrobat Professional they are. (They are also available in my Microsoft Word Software).
I have read a few adobe trouble reports of this being a problem in InDesign, but the problems there are not what I am having.
When I open up say Photoshop and create a document, in the available fonts, my first choice begins with 'Agency FB', followed by 'Algerian', then 'Arial', and then 'Arial Rounded'. This is the same in Illustrator and InDesign.
Yet in Adobe Acrobat, missing fonts such as 'Arial Black', 'Arial Narrow' are available.
Also, in Program Files\Common Files\Adobe\Fonts ..... there are fonts there that are available in Adobe Acrobat, but not in my Photoshop, like Adobe Caslon Pro.
Anyone have any ideas as to why my Photoshop, Illustator or InDesign are not reading all available fonts?
Again, I transferred my CS2 from an older computer to a Dell that is equipped with Windows Vista Business with the Downgrade to Windows XP Professional.
I know CS2 is not compatible with Windows Vista, but I was under the understanding that the Downgrade to Windows XP Pro would give me a Windows XP Pro Operating system, avoiding the problem of my CS2 not being compatible with Windows Vista.
Everything else appears to be working properly (as far as I can see)
Thanks in advance for any help / insight / solutions.
Greg

Have you read this?
http://indesignsecrets.com/hotfix-corrects-arial-narrow-problem-on-windows.php
Bob

Exporting Jpegs from Lightroom - DPI question

When I export Jpegs from Lightroom, I set the dpi to 300 pixels per inch. I do not specify a max width or height. When I view these files in Adobe Bridge (CS2 or CS3) the file info says 300dpi. However, when I open the files in Photoshop and select image size, It says 72dpi and has the document size set to very large. I realize that I can enter 300 dpi and uncheck the resample box, I am just confused as to why this is happening.
My concern is, that I upload my images directly to my lab after exporting from Lightroom. Will this cause problems?
Thanks in advance!
David

the image resolution is a combination of the two parameters you mention: size and dpi. a very large size at 72 dpi is equivalent to a small size (like 3x5) at very high dpi. for printing you want at least 240 dpi at the largest size that allows you to keep that resolution. for screen presentations or your web site you want jut 72 dpi. 72 dpi and 2x3 inches will require a very small file size.
I suggest you to export images at TIFF and not JPEG as that will allow you to preserve the image quality when doing editing in PS.
In my case I export TIFF for PS (when I need PS editing) and 72 dpi JPEG for my web site (that way if somebody downloads my image illegally thy get a poor resolution copy). But since LR works very well for me 90% of the images re just kept in raw mode and I print from LR.

Export hot spots for GL CS2

Hi, I've created a simple image with a hotspot but when I
export as a jpeg I loose the hotspot. I've also tried to export
jpeg + html and tried to paste the generated code in the sourcecode
of my GL page but it's not working. What am I missing? I'm using FW
CS3, GL CS2 and OS 10.4.11 all updated to latest versions.

>wow! 100,000 shots...
Really. It's nice to see someone has job security in this economy.
>Everything I have read so far says to avoid using flash. The reasons given were: distraction (for the employees), uneven color (due to "hot spots") and time to recharge the flash between firing.
Flash/strobe as far as I'm concerned, is going to be much more consistent color and exposure wise than tungsten. Flash tubes tend to stay much more constant over time and will certainly last much longer. And you won't have hot spots if you do as Ann says:
>That means having at least two identical units positioned at equal distances on either side between the camera and the blue print and at a 45° angle from the print.
Considering the enormity and apparent historic or other importance---and not knowing what sort of equipment you already have---I certainly wouldn't consider it imprudent to figure in an investment of a few hundred to (more likely) a few thousand dollars in order to make this happen as expeditiously as possible.
And if you're going to be doing 100,000 shots straight down, either make sure you have a comfortable set-up and/or enroll in a yoga class, because that's gonna be tough on the back.
>I still think someone is exaggerating or pulling my leg.
Somehow, I think that as well. Otherwise, we'll see you when you surface in 3.42 years.

Exported jpegs not read by CS2

Similar Messages

Maybe you are looking for