JPG export issues?

Working with a brochure I have created in Photoshop CS2 v9, I have inserted some pretty high resolution jpgs, but they keep appearing pixelated if I print it, only the jpgs are this way. I open them in another window then drag them in into my layered document set to 300dpi. Am I doing something wrong or is there a workaround?
Thanks,

When you drag the jpegs into your new window I believe they should first appear at a physical size based on the 300ppi of the new window document. Do you then resize the jpeg in the new window layer? This may cause your jpeg to be resampled.
What are the pixel size of your jpegs and what is the new window canvas size.
Ed

Similar Messages

JPGs exported from Lightroom 5.6 will not open in other applications

Recently I have noticed that jpgs exported from Lightroom 5.6 can not be opened in Canon DPP 3.14 and can not be resized using Image Resizer plugin. Both of these I use frequently.
I have seen mention of this issue re other applications also. Does anyone know if there is a solution?
I am using Windows 8.1 64bit. 5D Mark ii

This was an issue with 5.5 (the placement of some of the internal headers of the jpgs was changed and some other applications, including DPP, could not open them), but was corrected in 5.6. I just checked on it by exporting a jpg and opening it with no problem in DPP 3.14.15, Windows 7 x64. Are your jpgs old ones from LR 5.5?

JPG quality issues

I design wedding albums using InDesign CS5. My high res JPGs are about 8x12 inches at 300DPI, and my album page size is 10x15 inches. When I insert a JPG into the layout and resize it to 10x15 and export (maximum quality, 300DPI) there are severe artefacts clearly visible on screen and in print.
However when I just open up the original JPG and resize in Photoshop it is much, much cleaner. See an example here: http://www.photosbyjay.com.au/files/indesign-pain.jpg . There has been some sharpening applied but the artefacts are still just as bad before sharpening.
Can someone tell me what I'm doing wrong? If I don't size the JPGs up larger than their 8x12" size in InDesign they export fine. Is this a limitation of InDesign - does it have bad upscaling algorithms? One would assume they'd use Photoshop technology.
Any help is greatly appreciated.
Jay

@John - I'm not doing the printing myself, I'm exporting and sending to my pro lab. The issue I'm having is the InDesign JPG exported file is showing terrible artefacts
Wait...are you exporting a JPEG from InDesign and sending that to your printer?
No no no no!
This isn't the only problem you'll have if you do that. The only kind of file you should send to your printer is a PDF exported from InDesign. If you save your work as a JPEG, you will certainly lose quality.
(Yes, the method you're using can make it a little bit better. But not really. And there will always be problems with text and lines and things with sharp edges -- because JPEG, by its very nature, cannot express those things without artifact).
Is there some reason you believe you are limited to JPEG? If so, it may be time to find a new printer.

Extremely large jpg exported files - help!

I was previously loving LR3 - used the trial for a month, decided to buy it - had really no problems. The big issue for me is now the jpg export file sizes that are being created. I run all my photos through the develop module to adjust the basics as well as draw in masks, and previously I had no trouble exporting the files as jpg, with the limit of size at 600kb and resized to 960x640 (original photos from 5Dmk2 RAW).
Then I bought the license. From then on it seems that now whenever I do the same exact export it doesn't work! I also used to use the output quality slider and set that at 100% and would get around the same file sizes, but now I'm getting files 2-3x the size of the previous exports. All of the photos have minimal metadata (10 keywords or so, that's it) and the same metadata was present in the exports in the trial version.
Playing around with more export parameters and reading around on this forum led me to try and minimize exif data - this didn't even work - files could not meet the requirements or they still ended up 2-3x the size they used to be.
The interesting part is that when I would delete all development history and set the file back to the original pre-edited RAW and export there would be no problems!
Could it be possible that LR is adding the development data into the metadata that it is attaching to the photo??
This has completely shut down my photo workflow and really is making me regret buying this otherwise wonderful tool.

What I can see in the image is that it contains about (uncompressed) 750KB of XMP data, the major part of it relating to some "PaintCorrection" as follows:
PaintCorrectionWhat             : Correction
PaintCorrectionAmount           : 1.000000
PaintCorrectionActive           : true
PaintCorrectionExposure         : 0.439246
PaintCorrectionSaturation       : 0.000000
PaintCorrectionContrast         : 0.000000
PaintCorrectionClarity          : 0.457077
PaintCorrectionSharpness        : 0.000000
PaintCorrectionBrightness       : 0.361949
PaintCorrectionHue              : 240.000000
PaintCorrectionSaturation       : 0.000000
PaintCorrectionMaskWhat         : Mask/Paint
PaintCorrectionMaskValue        : 0.689655
PaintCorrectionMaskRadius       : 0.005442
PaintCorrectionMaskFlow         : 0.000000
PaintCorrectionMaskCenterWeight : 0.843964
PaintCorrectionMaskDabs         : d 0.689505 0.619480
PaintCorrectionMaskWhat         : Mask/Paint
PaintCorrectionMaskValue        : 0.689655
PaintCorrectionMaskRadius       : 0.005444
PaintCorrectionMaskFlow         : 0.000000
PaintCorrectionMaskCenterWeight : 0.843964
PaintCorrectionMaskDabs         : d 0.689871 0.605390
PaintCorrectionMaskDabs         : r 0.005443
PaintCorrectionMaskDabs         : f 0.0813
PaintCorrectionMaskDabs         : d 0.689749 0.607832
PaintCorrectionMaskDabs         : f 0.1519
PaintCorrectionMaskDabs         : d 0.689626 0.610275
PaintCorrectionMaskDabs         : f 0.1700
PaintCorrectionMaskDabs         : d 0.689590 0.612722
PaintCorrectionMaskDabs         : r 0.005442
PaintCorrectionMaskDabs         : f 0.1759
PaintCorrectionMaskDabs         : d 0.689635 0.615026
PaintCorrectionMaskDabs         : r 0.005443
PaintCorrectionMaskDabs         : f 0.1742
PaintCorrectionMaskDabs         : d 0.689530 0.612581
PaintCorrectionMaskDabs         : f 0.1726
PaintCorrectionMaskDabs         : d 0.689425 0.610137
PaintCorrectionMaskDabs         : r 0.005444
PaintCorrectionMaskDabs         : f 0.1709
PaintCorrectionMaskDabs         : d 0.689320 0.607692
PaintCorrectionMaskDabs         : f 0.1692
PaintCorrectionMaskDabs         : d 0.689214 0.605248
PaintCorrectionMaskDabs         : r 0.005445
PaintCorrectionMaskDabs         : f 0.1678
PaintCorrectionMaskDabs         : d 0.689104 0.602803
PaintCorrectionMaskDabs         : f 0.1460
PaintCorrectionMaskDabs         : d 0.688982 0.602615
PaintCorrectionMaskDabs         : r 0.005444
PaintCorrectionMaskDabs         : f 0.1525
PaintCorrectionMaskDabs         : d 0.689069 0.605061
PaintCorrectionMaskDabs         : f 0.1569
PaintCorrectionMaskDabs         : d 0.689090 0.607511
PaintCorrectionMaskDabs         : r 0.005443
PaintCorrectionMaskDabs         : f 0.1625
PaintCorrectionMaskDabs         : d 0.689100 0.609960
PaintCorrectionMaskDabs         : f 0.1652
PaintCorrectionMaskDabs         : d 0.689195 0.612399
PaintCorrectionMaskDabs         : f 0.1863
PaintCorrectionMaskDabs         : d 0.689113 0.610052
PaintCorrectionMaskDabs         : r 0.005444
PaintCorrectionMaskDabs         : f 0.1845
PaintCorrectionMaskDabs         : d 0.688940 0.607617
PaintCorrectionMaskDabs         : f 0.1839
PaintCorrectionMaskDabs         : d 0.688743 0.605185
PaintCorrectionMaskDabs         : r 0.005445
PaintCorrectionMaskDabs         : f 0.1916
PaintCorrectionMaskDabs         : d 0.688549 0.602753
PaintCorrectionMaskDabs         : f 0.1748
PaintCorrectionMaskDabs         : d 0.688555 0.604775
PaintCorrectionMaskDabs         : r 0.005444
PaintCorrectionMaskDabs         : f 0.1839
PaintCorrectionMaskDabs         : d 0.688622 0.607222
PaintCorrectionMaskDabs         : f 0.2225
This data results from heavy use of the local adjustment brush. Choosing "Minimize Embedded Metadata" upon export really should solve this problem for you. Please try again specifying this option.
But then, by doing so, you lose any other metadata (keywords etc.) also. To have complete control on what metadata gets written into the JPEG upon export, you could use Jeffrey’s “Metadata Wrangler” Lightroom Plugin.
I noticed one strange thing within the XMP data in your JPEG:
The data seems to be formatted differently than what I see with JPEGs I export ("HasExtendedXMP"), which I don't know where it comes from.
For further investigation, would it be possible for you to upload the Raw file and the XMP file belonging to it to somewhere (e.g. www.yousendit.com) and post a link to it here?
Beat Gossweiler
Switzerland

Bizzare export issue

Here is a very weird export issue. Windows XP.
Project is set at h264 1920x1080 mono audio 29.97 fps
I have 30 shots that make up the sequence. Each shot is exactly 90 frames. I exported each sequence at h264 1920x1080 with one channel of audio. The first shot exports just fine and is 5 MB. The second shot exports at 10 MB. The third is 15 MB, the tenth shot is 50MB. But the picture is still 90 frames for each shot. BUT, when I export without audio each exported file is just 5 MB. If I look at the properties of each clip the duration of the video and audio is just 90 frames. If I open one of these clips in QuickTime Pro and re-export it as source then the files size goes back to 5 MB; same video, same audio yet with the correct file size.
Anyone seen this before?
Is there a setting that could be incorrect?
-cablet

Weird, man. Not sure what might cause that.

JPG export preset in InDesign?

Hi all,
Is there a way to save my JPG export selections as a preset? I have to export JPGs of the same document for two different purposes and they have different export requirements. Is there a way to save my selections as a preset the same way I can save my PDF export selections as presets?
InDesign 7.0.4
Mac 10.6.8
Cheers,
Trish

I'm pretty sure it won't be your fault, but I don't seem to be able to fix it. Try this one but it exports the number of pages squared! For example a 4 page document gives you 16 jpegs, 5 = 25 and so on.
What am I doing wrong John? I added in this line: app.jpegExportPreferences.jpegExportRange = ExportRangeOrAllPages.EXPORT_ALL;
//Display a "choose folder" dialog box.
if(app.documents.length != 0){
var myFolder = Folder.selectDialog ("Choose a Folder");
if(myFolder != null){
myExportPages(myFolder);
else{
alert("Please open a document and try again.");
function myExportPages(myFolder){
var myFilePath, myPageName, myFile;
var myDocument = app.activeDocument;
var myDocumentName = myDocument.name;
var myDialog = app.dialogs.add({name:"ExportPages"});
with(myDialog.dialogColumns.add().dialogRows.add()){
staticTexts.add({staticLabel:"Base name:"});
var myBaseNameField = textEditboxes.add({editContents:myDocumentName,
minWidth:160});
var myResult = myDialog.show();
if(myResult == true){
//The name of the exported files will be the base name +
//the page name + ".jpeg".
var myBaseName = myBaseNameField.editContents;
//Remove the dialog box from memory.
myDialog.destroy();
//Generate a file path from the folder name, the base document name,
//page name.
for(var myCounter = 0; myCounter < myDocument.pages.length;
myCounter++){
myPageName = myDocument.pages.item(myCounter).name;
app.jpegExportPreferences.jpegExportRange = ExportRangeOrAllPages.EXPORT_ALL;
//Modify the following to change the Resolution. Enter a figure instead of 300
app.jpegExportPreferences.exportResolution = 300;
//Modify the following to change the colour space. the options are:
//JpegColorSpaceEnum.RGB
//JpegColorSpaceEnum.CMYK
//JpegColorSpaceEnum.GRAY
app.jpegExportPreferences.jpegColorSpace = JpegColorSpaceEnum.CMYK;
//Modify the following to change the jpeg quality. the options are:
//JPEGOptionsQuality.LOW
//JPEGOptionsQuality.MEDIUM
//JPEGOptionsQuality.HIGH
//JPEGOptionsQuality.MAXIMUM
app.jpegExportPreferences.jpegQuality = JPEGOptionsQuality.MAXIMUM;
//Modify the following to change the Rendering Style. the options are:
//JPEGOptionsFormat.BASELINE_ENCODING
//JPEGOptionsFormat.PROGRESSIVE_ENCODING
app.jpegExportPreferences.jpegRenderingStyle = JPEGOptionsFormat.BASELINE_ENCODING;
//The name of the exported files will be the base name +
//the page name + ".jpeg".
//If the page name contains a colon (as it will if the
//document contains sections),
//then remove the colon.
var myRegExp = new RegExp(":","gi");
myPageName = myPageName.replace(myRegExp, "_");
myFilePath = myFolder + "/" + myBaseName + "_" + myPageName + ".jpeg";
myFile = new File(myFilePath);
app.activeDocument.exportFile(ExportFormat.jpg, myFile, false);
else{
myDialog.destroy();

Crystal JRC PDF Export Issue

We are experiencing a PDF export issue with Crystal JRC version 12.2.202. The PDF report shows 1 of 3 pages but ONLY the first page is generated. When this occurs, ALL other users that are exporting to PDF experience the same issue with any multiple page report. I can't find any errors in the log that would indicate what the problem is. To resolve the issue, I have to recycle the WebLogic application server that hosts the JRC, which would indicate something gets "locked" in memory and gets cleared when the app server is bounced.
Any ideas on how to resolve this ?

Hi Ted,
Thanks for the response!
Though, the mentioned Sun JVM Bug explains the root-cause, the Bug status also state that it is not fixed yet.
Also, we are reluctant to change the JVM Option to -Xint due to unknown impacts on JVM optimizations.
Is there a patch released for CrystalReports to deal with this behavior? We are using CRJ runtime 11.5.7.620 and seeking for a patch on this version.
Thanks.

PP CS5.5 FLV To MP4 Export Issues / Problems

I just upgraded from Production Premium CS5 to CS5.5. I do a fair amount of converting/exporting of imported FLV files (downloaded from internet news sites) to H.264/AAC w/ MP4 wrappers using Premiere Pro (PP) and Adobe Media Encoder (AME). My equipment is a 1+ yr. old HP Win 7 Pro w/ an Intel i970 Quadcore, 12 Gb RAM and MSI nVidia GTX 470 GPU. I have never experienced any queue or export issues w/ CS5 (at least that I noticed), but I am experiencing noticeably degraded queue export and direct export problems with these files in CS5.5.
Description: (1) The queue export times for the exact same imported FLV clip(s) using the exact same sequence settings and H.264/MP4 export settings are noticeably slower in CS5.5 (sometimes 2x, depending on the export settings, e.g. using maximum render quality) than in CS5; (2) My MSI Afterburner GPU monitoring software indicates 5-10% GPU usage during queue/export in CS5, while indicating 0% GPU usage (flatline) in CS5.5; and (3) When I attempt to direct export these files using CS5.5 I get the following error message: "The source and output audio channels are not compatible or a conversion does not exist."
I suspect that it may have something to do with "conforming" anomalies when the FLV file is imported into PP, but I would put that squarely in the category of rank speculation on my part.
Has anyone experienced the same or similar problems or have any insight into what may be the problem(s)? Of course, thanks for any help/insight you can provide.
Jim

What do you mean by a better routine?
A better compression routine than H.264.
Is the quality better than H.264?
Yes.
Does this use an MOV wrapper?
Yes.
Also, would it import correctly into PPro?
Yes.
we would import files into PPro exported out of FCP and would get a red pixelated glitch during preview and export. Does this codec solve this problem as well if it is an MOV wrapper?
I don't know anything about FCP.
Sorry for all the questions, just want to get things right before diving into a new codec.
It's harmless, and free.
Download it and run some tests.

Simple flash export issue

hello
I'm trying to export a flash video using Adobe media encoder from Premier Pro, but when I do I get this error " there are no clips to build".
I have another file that I am able to export and it does not have this problem.
They are Windows Media files and play in Premier fine. I am using Premier Pro CS3.
Lastly, I'm not a video expert but I really need to get these up on the web for work, there is a lot of pressure and I need to get it done.
Regards,
Tom

fixed the exporting issue.

Multi-threaded JPG export

The slowest portion of my application is the conversion from a generated INDD file to JPEG. More CPU power seems to be the only solution at this point, but because IDS is single threaded, 3 of the cores on the server sit idle during this.
Is it possible to implement a plugin or Javascript script that exports each page in a separate thread, or similar, thus using all available cores during the export process?

Hi,
I think it is possible in InDesign 5 via "asynchronousExportFile". You can also create multiple server instances and let each instance generate a jpg export.
Message was edited by: 2i_Geert

Exporting ISSUES! Help

I am a relatively new user to lightroom. I haven't had any exporting issues until today. I am attempting to export a photo/photos to a specific folder with a custom name. When I do this it exports the WHOLE library and NOT the edited photo. What am I doing wrong??

Lightroom usually exports all images that are highlighted. If you only want to export one image then make sure it is the only image that is highlighted.

Exporting issues after 4.2 upgrade

Has anyone else experienced exporting issues after installing the 4.2 upgrade? It used to be a breeze but now I keep getting the message that a destination folder has not been specified even though I've done that. Any feedback would be greatly appreciated! Thank you.

Are you using an Export preset, or setting the Export up manually each time?

Reporting Export Issue from Taleo

Can anyone help? We have a work around for the Exporting Issues into Excel 2010 regarding figures and dates only reading as text, however, a new issue has arisen. In one field we have Aggregated Agencies assigned to any particular Job Code. In the legacy reports, every agency name exported into one cell in Excel, now they export into individual rows, this causes a report to be too long and there is no way to amalgamate them into one cell. Has anyone found a workaround for this?

is there someway that it was reformatted by the Iomega drive being daisy chained to it?
No. That is not possible -anyway, reformatting erases everything on a drive.
You would have noticed that first.
You can download the [NTFS-3G driver|http://macntfs-3g.blogspot.com> which will let you read, write and even reformat the clients drive as NTFS on the Mac. All reasonably modern Windows PCs work with this disc format and you won't run into the file size limitations associated with FAT formatted drives.

Keywords missing in LR2.3 jpg exports.

My jpg exports do not contain the keywords and captions that I entered in LR2.3. What am I doing wrong?

DKramer24 wrote:
I'm checking by clicking on the exported/created jpg's properties in WinXP. Minimize metadata is unchecked. I've tried the exports with and without that box checked, same with Write keywords as Lightroom heierarchy.. no keywords or captions.
Personally, I don't trust Win Explorer to always list the metadata correctly. I always check with ExiftoolGUI. It will list all the metadata.

Using 128bit key Blowfish and any export issues

Hi,
I want to use blowfish (symmetric key algorithm) in my product and which will be shipped outside US. Reading Sun's documentation I am bit confused and I am not sure if the jce package is going to be available outside the US.
Has anyone used the default available symmetric key algorithms in the JCE package (javax.crypto.*) and faced any export control issues ?
Please let me know.
Thanks
RT
Here is a sample code
String ks = "123456789123456";
kb = ks.getBytes();
SecretKeySpec key = new SecretKeySpec(kb,"blowfish");
Cipher cipher = Cipher.getInstance("blowfish");
// Initialisation of cipher object for Encryption.
cipher.init(Cipher.ENCRYPT_MODE, key);

1. the issue is rather an import issue for some countries, than an export issue for US as far as you use jre>=1.4 .
you can read the
'Downloading the "Unlimited Strength" Jurisdiction Policy Files'
section of
http://java.sun.com/products/jce/javase.html
2. The restricted (defualt) shipped version already covers Blowfish if you mind that.
3. I use Blowfish with restricted (default) version of JCE in applications deployed in europe and have not heard of customer complaining sofar: they are supposed to use webstart or jre1.5.

JPG export issues?

Similar Messages

Maybe you are looking for