Lightroom 5.3 bug with export images

Hi,
I can't export single images in Lightroom anymore. When I choose an image including the watermark the system exports all the latest imported images, but not a single one. Can anyone help me with that?
-jo

in your lr5.2, click help>updates...
bug fixes:
Issues when upgrading catalog from previous versions of Lightroom.
Incorrect photos are displayed after switching away from a Publish Collection.
Catalog optimization did not finish, and was not optimizing the catalog
Feather of clone spots is set to 0 after upgrading catalog to Lightroom 5.
Auto White Balance settings are not saved to Snapshots.
Sony 18-55mm lens is detected as the Hasselblad 18-55mm lens for lens correction.
Increased Update Spot Removal history steps when in Before and After view.
Slideshows start playing automatically even when the Manual Slideshow option is enabled.
Video playback stops when dragging on the scrubber.
Errors when publishing photos to Flickr through the Publish Service.
Option + drag on Edit Pin behavior is functioning incorrectly.
Black border appears around the exported slideshow video.
Catalog containing images processed with PV2003 were adding a post-crop vignette when catalog upgraded to Lightroom 5.
Pressing the “Reset” button while holding down the Shift key caused Lightroom to exit abruptly.
Output Sharpening and Noise Reduction were not applied to exported images that were resized to less than 1/3 of the original image size.
The Esc key did not exit the slideshow after right clicking screen with mouse during slideshow playing.
Import dialog remained blank for folders that contain PNG files with XMP sidecars.
Metadata panel displayed incorrect information after modifying published photo.  Please note that this only occurred when metadata was changed after the photo was published.

Similar Messages

  • Lightroom 5.0 is not exporting images properly

    Recently I upgraded to Lightroom 5.0. I have been noticing that when I export images at 1000px max and 100% quality, the image is very grainy. I can open that same image in Photoshop CC from Lightroom, resize the image to 1000px max, and save, and the image looks great. Below is an example. The first photo is the Lightroom 5.0 export. The second is the Photoshop CC resize and save. Does anyone know what the problem is? I never had this issue with any earlier version of Lightroom and I have been using it since version 1.0.

    Download the Lr 5.2RC from Adobelabs. There was a bug in exporting which is fixed in this release candidate.
    http://labs.adobe.com
    Finch1055 wrote:
    Recently I upgraded to Lightroom 5.0. I have been noticing that when I export images at 1000px max and 100% quality, the image is very grainy. I can open that same image in Photoshop CC from Lightroom, resize the image to 1000px max, and save, and the image looks great. Below is an example. The first photo is the Lightroom 5.0 export. The second is the Photoshop CC resize and save. Does anyone know what the problem is? I never had this issue with any earlier version of Lightroom and I have been using it since version 1.0.

  • Help with exporting images

    HI
    I have recently shot a wedding with two bodies.  Forgot to sync the bodies before hand and so left with images at massively different times.  in lightroom i then changed to view by capture time and amended all the wrongly timed images.  i am then left with all images in order and looking as i want.  I then put them in a catalogue and a collection to be on the safe side and exported both.  Whatever i do i see the exported images in my pictures in the same order they were in before i changed the capture time.  i have tried to research this until im sick of it.  I just cant figure out what is going wrong.  Just tried to save to dvd instead and saved but again in the order pre correction?  please help

    Hi did that this morning .  I'm viewing in the exported named file in a
    folder on the mac ... I've tried re naming , sort by capture time but the
    minute I export , the exported file looks just the same as before I made
    the capute time amendments .
    Thanks
    Kim

  • Problem with Export - Image Sizing

    Hello, I'm running LR3 on a relatively new iMac.  I am using LR to edit RAW photos from my Nikon D700 and one of the things I do is export to .jpg to put some photos on my website.  To do this, each photo must be the same width and height, or it causes issues with the website.
    For awhile, I was exporting images at dimensions of 960x636 with no issues.  All of a sudden, when I use the export feature, and put in the Image Sizing section the 960x636 resolution, the exported file is at a resolution of 956x636 and therefore is not the same size as previously exported photos.  I've tried changing some of the settings in the Image Sizing section (check/uncheck Don't Enlarge, Dimensions vs. Width & Height, etc.) and nothing seems to work.  Any advice why LR3 is overriding my image size settings would be greatly appreciated.

    When you specify the width and height on export, you are specifying a "box" that Lightroom will fit the image into. It will do the best it can, but if your cropped image doesn't have the same aspect ratio as the "box", then one dimension will be short. As an example, if you had cropped your picture into a square, how could Lightroom possibly completely fill a rectangle with it?
    You need to crop your images to the same ratio as the 956 : 636 that you're specifying on Export.
    Hal

  • Critical issue with exporting images in iPhoto 08?

    I have been exporting selected photos to a thumb drive under iPhoto 06. I then take the thumb drive and put it in a pioneer palsma and go to GALLERY mode. Works fantastic and I can then review the images with my clients. Never had a problem with iPhoto 06. I upgraded to iPhoto 08 recently and export selected photos to the thumbdrive under the new upgrade. When I go to Gallery mode on the plasma the photos do not come up and it hangs up the plasma..... ??? Seems to be a problem somewhere with what "08" does with the photos? I ran a number of different test with two different thumb drives using photos from iPhoto 08 and cannot get them to work. I go back to an old iMac that was not upgraded to iPhoto 08 and both thumb drives they work fine on the plasma. In fact it is almost impossible to mess the operation up with "06". I have tried to export the photos in "08" in all the various size options and still no success. I would appreciate any help to this critical problem I am facing since I use this function of showing my images on a plasma on a daily basis . After about 10 to 12 hours of working htis problem I am totally loss as what to do. Thanks for your time.

    Thanks for your reply.
    1. I select the photos from iPhoto - varied between 5 and 20 (ran different test)
    2. Click on FILE
    3. Select EXPORT
    4. Under the FILE EXPORT tab I have tried all the various options with no success
    5. KIND - I make sure they are JPEG files - I have tried the Original also which is actually JPEG files
    6. JPEG QUALITY - I have tried all 4 options from LOW to MAX
    7. SIZE - I tried all 4 size options from SMALL to FULL
    8. FILE NAME - I use filename
    9. Select EXPORT tab
    10. I export to the thumbdrive and I chcek and they are on the thumbdrive
    11. I also tried to EXPORT to the desktop and copy them to the thumbdrive
    I click on the photos on the exported images I placed on the thumb drive and they come up fine on PREVIEW on my MAC. No prroblem with the images until I try to use them on the plasma. I go back and use images from iPhoto 06 that I did not call up with the "08" program and they work fine.
    Hope that explains what I do. Thanks again

  • Problem with exported images

    When I export images from any fla, they are very slightly cropped on the right side and bottom. I don't want them to be cropped. Here's how I'm exporting: I paste the image in a blank fla, select Export, Export image, and choose the filename and location. Am I missing something? Thanks for any help.

    hi kayjs ,please ensure size of the document is similar to picture & exporting time include:full document size. i think this workable for you

  • Bug with exporting project to java source

    Hi,
    This is in TopLink 9.0.4.2 (Build 040311).
    We're in the process of trying to determine if we should upgrade our TopLink from 2.5 to 9.0.4, and have not yet purchased a support contract because we haven't made the final decision yet, so I'm posting this bug here in hopes that someone can submit the bug.
    In one of our projects, we have an AggregateObjectMapping (AOM) for a Measurement object that is owned by 2 different objects, each with 2 to 4 instances of this Measurement class. I set up the instances of the AOM in the workbench just fine, and looking at the XML descriptors that are written out, it appears fine. Exporting the project session XML file works fine as well. However, when it is exported to a Java file, the instances of the AOM are exported incorrectly as described below.
    Here is the abbreviated mapping of the attributes of the Measurement class:
    <mappings>
    <mapping>
    <inherited>false</inherited>
    <instance-variable-name>mPrecision</instance-variable-name>
    <default-field-names>
    <default-field-name>direct field=yPrecision</default-field-name>
    </default-field-names>
    <uses-method-accessing>false</uses-method-accessing>
    <read-only>false</read-only>
    <mapping-class>MWDirectToFieldMapping</mapping-class>
    </mapping>
    <mapping>
    <inherited>false</inherited>
    <instance-variable-name>mQuantity</instance-variable-name>
    <default-field-names>
    <default-field-name>direct field=y</default-field-name>
    </default-field-names>
    <uses-method-accessing>false</uses-method-accessing>
    <read-only>false</read-only>
    <mapping-class>MWDirectToFieldMapping</mapping-class>
    </mapping>
    <mapping>
    <inherited>false</inherited>
    <instance-variable-name>mUnit</instance-variable-name>
    <uses-method-accessing>false</uses-method-accessing>
    <read-only>false</read-only>
    <reference-descriptor>com.cimsoft.lws.units.Unit.ClassDescriptor</reference-descriptor>
    <private-owned>false</private-owned>
    <uses-batch-reading>false</uses-batch-reading>
    <table-reference-mapping-reference-handle>
    <reference-handle>
    <reference-table>csrSlotGenericValue</reference-table>
    <reference-name>csrSlotGenericValue_csdUnit</reference-name>
    </reference-handle>
    </table-reference-mapping-reference-handle>
    <uses-joining>false</uses-joining>
    <one-to-one-mapping-indirection-policy>
    <indirection-policy>
    <uses-indirection>false</uses-indirection>
    </indirection-policy>
    </one-to-one-mapping-indirection-policy>
    <mapping-class>MWOneToOneMapping</mapping-class>
    </mapping>
    <mapping>
    <inherited>false</inherited>
    <instance-variable-name>UNDEFINED_MEASUREMENT</instance-variable-name>
    <mapping-class>MWUnmappedMapping</mapping-class>
    </mapping>
    </mappings>
    Notice that there are two direct to field mappings (mPrecision and mQuantity) and one OneToOneMapping (mUnit). The exported sessions XML file has the correct XML for instances of this object. Here is an example from a class that has 3 instances of this Measurement object mapped:
    <database-mapping>
    <attribute-name>mAlarmSize</attribute-name>
    <read-only>false</read-only>
    <reference-class>com.cimsoft.lws.units.Measurement</reference-class>
    <is-null-allowed>true</is-null-allowed>
    <aggregate-to-source-field-name-associations>
    <association>
    <association-key>unitId</association-key>
    <association-value>csrStock.alarmSizeUnitId</association-value>
    </association>
    <association>
    <association-key>y</association-key>
    <association-value>csrStock.alarmSize</association-value>
    </association>
    <association>
    <association-key>yPrecision</association-key>
    <association-value>csrStock.alarmSizePrecision</association-value>
    </association>
    </aggregate-to-source-field-name-associations>
    <type>oracle.toplink.mappings.AggregateObjectMapping</type>
    </database-mapping>
    <database-mapping>
    <attribute-name>mCurrentSize</attribute-name>
    <read-only>false</read-only>
    <reference-class>com.cimsoft.lws.units.Measurement</reference-class>
    <is-null-allowed>true</is-null-allowed>
    <aggregate-to-source-field-name-associations>
    <association>
    <association-key>unitId</association-key>
    <association-value>csrStock.currentSizeUnitId</association-value>
    </association>
    <association>
    <association-key>y</association-key>
    <association-value>csrStock.currentSize</association-value>
    </association>
    <association>
    <association-key>yPrecision</association-key>
    <association-value>csrStock.currentSizePrecision</association-value>
    </association>
    </aggregate-to-source-field-name-associations>
    <type>oracle.toplink.mappings.AggregateObjectMapping</type>
    </database-mapping>
    <database-mapping>
    <attribute-name>mLotSize</attribute-name>
    <read-only>false</read-only>
    <reference-class>com.cimsoft.lws.units.Measurement</reference-class>
    <is-null-allowed>true</is-null-allowed>
    <aggregate-to-source-field-name-associations>
    <association>
    <association-key>unitId</association-key>
    <association-value>csrStock.lotSizeUnitId</association-value>
    </association>
    <association>
    <association-key>y</association-key>
    <association-value>csrStock.lotSize</association-value>
    </association>
    <association>
    <association-key>yPrecision</association-key>
    <association-value>csrStock.lotSizePrecision</association-value>
    </association>
    </aggregate-to-source-field-name-associations>
    <type>oracle.toplink.mappings.AggregateObjectMapping</type>
    </database-mapping>
    However, here are the corresponding mappings in the exported Java file (with what it really should be manually inserted by me in comments):
         AggregateObjectMapping mAlarmSizeMapping = new AggregateObjectMapping();
         mAlarmSizeMapping.setAttributeName("mAlarmSize");
         mAlarmSizeMapping.setReferenceClass(com.cimsoft.lws.units.Measurement.class);
         mAlarmSizeMapping.setIsNullAllowed(true);
         mAlarmSizeMapping.addFieldNameTranslation("csrStock.alarmSizeUnitId", "unitId");
         mAlarmSizeMapping.addFieldNameTranslation("csrStock.alarmSize", "y");
         mAlarmSizeMapping.addFieldNameTranslation("csrStock.alarmSizePrecision", "yPrecision");
         descriptor.addMapping(mAlarmSizeMapping);
         AggregateObjectMapping mCurrentSizeMapping = new AggregateObjectMapping();
         mCurrentSizeMapping.setAttributeName("mCurrentSize");
         mCurrentSizeMapping.setReferenceClass(com.cimsoft.lws.units.Measurement.class);
         mCurrentSizeMapping.setIsNullAllowed(true);
         mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSize", "alarmSize");
         mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSizeUnitId", "unitId");
         mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSizePrecision", "alarmSizePrecision");
         // should be: mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSize", "y");
         // should be: mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSizePrecision", "yPrecision");
         descriptor.addMapping(mCurrentSizeMapping);
         AggregateObjectMapping mLotSizeMapping = new AggregateObjectMapping();
         mLotSizeMapping.setAttributeName("mLotSize");
         mLotSizeMapping.setReferenceClass(com.cimsoft.lws.units.Measurement.class);
         mLotSizeMapping.setIsNullAllowed(true);
         mLotSizeMapping.addFieldNameTranslation("csrStock.lotSizeUnitId", "unitId");
         mLotSizeMapping.addFieldNameTranslation("csrStock.lotSize", "currentSize");
         mLotSizeMapping.addFieldNameTranslation("csrStock.lotSizePrecision", "currentSizePrecision");
         // should be: mLotSizeMapping.addFieldNameTranslation("csrStock.lotSize", "y");
         // should be: mLotSizeMapping.addFieldNameTranslation("csrStock.lotSizePrecision", "yPrecision");
         descriptor.addMapping(mLotSizeMapping);
    It appears that the actual Measurement descriptor is being modified accidentally as it's being exported, as you'll notice that the first mapping (for mAlarmSize) correctly maps the default "y" to "alarmSize", and then the next mapping (for mCurrentSize) instead of mapping "y" to "currentSize" maps "alarmSize" to "currentSize", and the next AOM maps "currentSize" to "lotSize" instead of "y" to "lotSize".
    Thanks,
    Greg

    No one ever responded, so I'm commenting to bring it up again. It turns out that the error happens not just exporting to Java, but anytime the command-line project generation is used. If the Workbench is used to export either to XML or to a Java file, the file is generated correctly. It is not generated correctly if you try to do it from the commandline (e.g. from a build environment).
    This has happened with 9.0.4.2 through the current 9.0.4.5.
    Here are different ways I've tried doing it from the commandline, and they all generate the erroneous XML and Java files:
    java oracle.toplink.workbench.external.api.JavaSourceGenerator inputMWP outputJava.java
    and
    java oracle.toplink.workbench.external.api.DeploymentXMLGenerator inputMWP outputXML.xml
    which are recommended by the documentation. Also recommended by the documentation:
    JavaSourceGenerator.generate( inputFile, outputFile )
    and
    DeploymentXMLGenerator.generate( inputFile, outputFile ).
    From decompiling the management workbench to see what it was doing differently:
    MWProject project = WorkbenchSession.instance().openProject( inputFile );
    if ( doXML )
    project.setProjectDeploymentXmlDirectory( directory );
    project.setProjectDeploymentXmlFileName( filename );
    project.exportDeploymentXml();
    else
    project.setProjectSourceRootDirectory( directory );
    project.setProjectClassName( classname );
    project.exportJavaSource( outputFile );
    //Also tried plain old project.exportJavaSource(); which appears to actually do something different.
    Any ideas? It looks like a bug to me, particularly that different java or XML deployment files are generated when run from the commandline versus run from the UI. Obviously, the commandline is very important because it is what the build system needs.
    Thanks,
    Greg

  • LIGHTROOM CC 2015 Bug with Intuos

    LIGHTROOM CC 2015
    Mac Pro mi-2010 and Macbook Pro mi-2010 - Yosemite 10.3.3
    When you put an overlay, it is possible to change the settings with apple mouse or trackpad, using command key. It’s impossible to change this with Wacom Intuos 4 or Intros Pro (driver 6.3.11-3). all was OK in Lightroom 5.7.1
    Other bug : Pentax 20-40 exif don’t be displayed even when the correct profil is selected.
    Please, share this with developers. Thanks

    Well what do you know ... this might just be a combination of buggy coding on both Adobe's and Wacom's parts.
    One of the problem areas in LR CC or 6.0.1 is as said curves adjustments ... erratic behaviour and unresponsive pen action from using the Pro M tablet made me roll back various drivers, each time clearing the preferences etc. Until I found out that using the latest 6.3.11-3 driver and turning Touch input ON it actually is as instant and smooth action as you'd wish for, if you pick an adjustment point and then two-finger-click-drag.
    Furthermore the general laggy and unresponsive feeling of sliders, and in particular using scrubby sliders, is gone if you choose to use touch input. Place the cursor over the desired slider or value and two-finger-click-drag or respectively three-finger-drag.
    Even scrolling in grid view using touch input works as well! We just can't use the pens for now in Adobe LR CC.
    Please note that in general I've been very satisfied with Wacom tablets and their performance for more than seven years. This is somewhat of a hickup that has been intruduced since OS X Yosemite in combination with newer Adobe applications. None the less it is utterly important to solve these bugs as it makes work frustrating.
    Best,
    Henrik

  • Lightroom 4: Massive BUG with White Balance / Quick Develop. Totally Unreliable!

    I just recently updated from LR3 and just now found a massive bug concerning the white balance adjustments in the quick develop module.
    After a studio shooting and especially after weddings I use the "make warmer" adjustment in the quick develop panel to give all (a few thousand NEFs) a nicer look all at once.
    The great thing about this is - like all quick developments - that it increases the color temperature relative to each image's starting white balance.
    Yesterday I wanted to edit my first wedding in LR4 and like in LR3 applied one click "make warmer" to all images at once (previously WB was "as shot").
    While I browsed through the images to rate them I noticed some of them were very "pinkish".
    After closer inspection it came out that a lot of images (50%-60%) had the following custom WB set: 5316, Tint: +10.
    It is always this exact combination no matter what the "as shot" WB was.
    That setting of course applies way too much magenta to a lot of images.
    After resetting the WB of single images to "as shot" and selecting "make warmer" once again the images look fine and get appropriate WB values.
    But every time I select more than one image to apply "make warmer" a lot of them get the strange value of 5316 and +10.
    Sometimes it's even just the first few images of the selection that get correct values and all the following ones get the off value. It appears to be totally random.
    I tried completely resetting all images prior to "make warmer", setting them to different camera profiles first and even switched them to Process 2010 again. But absolutely no luck!  :-(
    The "make warmer" tool gives me totally unusable results.
    I find it strange, that I couldn't find anything about that on the net.
    PLEASE fix this ASAP.
    To apply WB to thousands of images individually is a real pain.
    I would be glad to support you fixing the issue.
    My setup:
    Nikon D700
    Nikon D300s
    (Both cameras affected, I only shoot NEF)
    Win7 x64
    LR4.1 as well as LR4.2 RC

    @ssprengel
    I get your point but that is exactly my problem.
    Not only is there no pattern but also once I reset a file that got 5316+10 to "as shot" and select "make warmer" for it again it does get the correct value! As long as I select it as a single file without others.
    So just to simplify my findings and explain what I have been doing all night:
    - SELECT 5 files in Library View (all freshly imported, no settings altered, WB "as shot")
    File 1: 5700 / -8
    File 2: 5500 / -8
    File 3: 5550 / -8
    File 4: 5450 / -6
    File 5: 5500 / -7
    - CLICK "make warmer" once
    Result:
    File 1: 6089 / -8
    File 2: 5867 / -8
    File 3: 5316 / +10
    File 4: 5316 / +10
    File 5: 5316 / +10
    1 and 2 are okay!
    - SELECT 3-5
    - RESET THEM
    Result:
    File 3: 5550 / -8
    File 4: 5450 / -6
    File 5: 5500 / -7
    - CLICK "make warmer" again
    Result:
    File 3: 5316 / +10
    File 4: 5812 / -6
    File 5: 5867 / -7
    File 4 and 5 are okay!
    - SELECT File 3 again
    - RESET IT
    - CLICK "make warmer"
    Result:
    File 3: 5923 / -8
    now File 3 is okay, too.
    It is completely random!
    But that is no way to work, of course.
    I have two weddings from last week and am going nuts already.

  • Floating Dialog bug with multiple image selection?

    The selectionChangeObserver fuction of the LrDialogs.presentFloatingDialog command is not being triggered in all cases.
    It does not trigger when you have mulitple images selected and switch the main focus from one of the selected image to another seleted image.
    Anyone else run into this? or is it something I am doing wrong.
    function getSelectedImage()
            LrTasks.startAsyncTask( function ()
                 local selectedPhoto = catalog:getTargetPhoto()
                 props.PhotoNew = selectedPhoto
             end )
    end
    local result = LrDialogs.presentFloatingDialog (_PLUGIN, {
            title = "Thumbnail test",
            background_color = LrColor ("white"),
            contents = c,
            selectionChangeObserver = function(  )
                            getSelectedImage()
                    end,

    I reported this as a bug here:
    http://feedback.photoshop.com/photoshop_family/topics/lightroom_5_2_sdk_selection_change_c allback_not_called_by_change_in_most_selected_photo?rfm=1

  • Bridge bug with DICOM images

    Photoshop supports DICOM images, but Bridge does not show DICOM image thumbnails, and I have not figured out how to open DICOM images in PS from Bridge.
    It seems the only way to open DICOM images is from the File..Open.. menu in Photoshop.
    TomS

    It looks like I need to add a .dcm suffix and change the "Open with" property of .dcm to Photoshop to image thumbnails.
    I'm using OS X 10.6.8.
    The files have no suffix.
    The icon displayed in Bridge is a, top to bottom, dark grey to light grey gradient with the word "exec" in green text in the upper left hand corner.
    Apple's finder also displays the same icon.
    Bridge wants to open the file in Terminal.
    If I change the "open with" property of the file to PS, I can make Bridge open it in Photoshop, but I still get no thumbnail in Bridge.
    If I change the "open with" property to PS and I add a .dcm suffix, then Bridge creates a proper thumbnail.
    OS X is generally not very picky about suffixes so I never thought of adding .dcm.
    Thanks
    TomS

  • Has anyone seen this bug with embedded images?

    If I embed a wide image in this post and you click on it to zoom it up, is it centered in the safari window or center WRT the monitor?  Basically can you see all of it?

    It looks like this, here. It's done that for a long time, unless Safari extensions are switched off, regardless of there being any installed.

  • Java 6, 10 produces a bug with overlapping images

    Hi,
    I have a program which draws an image ontop of another image, using 6, 06 and 6, 07 it seems to work OK using 6, 10 it doesn't. I am not sure which version it stops working in though.
    In 6, 06 and 6, 07 the image flashes but in 6, 10 it flashes for one second then disappears, dragging another window ontop of the image reveals it while you're dragging the window but it then disappears again.
    This is the code:
    gameGraphics.drawImage(aGraphics936, windowWidth / 2 - 127, 230, image);
    public void drawImage(Graphics g, int x, int y, Image img) {
    g.drawImage(img, x, y, this);
    I'm a bit of a noob so go easy :/
    Thanks.
    Edited by: KO9 on Nov 2, 2008 7:13 AM

    aGraphics936 = getGraphics();
            public final Graphics getGraphics() {
                    if (GameWindow.gameFrame != null) {
                            return GameWindow.gameFrame.getGraphics();
                    return super.getGraphics();
            }gameFrame:
        public Graphics getGraphics()
            Graphics g = super.getGraphics();
            if(graphicsTranslate == 0)
                g.translate(0, 24 + yOffset);
            else
                g.translate(-5, 0);
            return g;
        }Hope this helps, thanks.

  • Recently updated Lightroom 5, now when I export images they come out 'grainy'. How do I fix this?

    How do I fix this?

    What you are seeing is a windows folder option.
    In Windows 7 click the start button, choose computer then open your C drive.
    From there you will see something similar to this,
    Click on the sort options and choose list. Now we need to make it the default so when you look in photoshop it remains as a list.
    to  do that from this same window choose tools then folder options.  A new window will pop up called folder options on the second tab called View is an all folders button, this will apply this view to all folders. if you have Photo shop open close it re-open it and how you will always get the view you want.

  • Possible Bug in ID5.5 When Exporting Images to ePub

    Just wanted to relate my experience with exporting images to ePub in InDesign CS5.5. I've already spent the better part of two weeks trying to find a resolution for the problem with Adobe's customer service techs in India. Nice guys, but so far not of much help.
    Here's the problem. when exporting ID documents to ePub, and you're selecting your options in the "Image" export dialog box, you are offered two choices: "Fixed" and "Relative to Page." In theory, "Relative to Page" is the best choice because this means your images will be automatically scaled for the different viewing devices (i.e. iPad, Kindle, mobile phone, laptop). If you select "Relative to Page," however, your images will export with pixilation.
    This may not happen to everyone, but it happened to me, as well as the last tech I spoke in India. I'm using a MacBook Pro running 10.6.7. Don't know what he was using, but he got the same results on his end when exporting an image to ePub using "Relative to Page." For me, the fonts look especially horrible in Adobe Editions. If you select "Fixed," they'll export just fine, (looked great in Adobe Editions and Kindle Previewer), but don't know how fixed size renders in the different devices.
    This particular exchange was last Friday. The tech verified that we had a problem he couldn't solve and told me he had to speak with his "senior," who had already gone home for the weekend. I received an email today informing me that all I had to do was select the high quality performance settings in ID, and the image would look "pretty" while the file was open in the program. Really? I mean, duh. What does that have to do with the EXPORT problem?
    And yes, I know to select the maximum quality setting in export. I'm a photographer who has used Photoshop since the 1990s. Used InDesign, QuarkXpress, and Pagemaker, in reverse order for that long as well, so I know how to prepare a file for print and the web. The techs I've spoken with have assured me I'm selecting the correct settings. Program has not only been uninstalled and reinstalled, but I went the extra drastic step of wiping my harddrive and starting over. No third-party plug-ins installed that didn't come with the original Adobe software. Have the latest ID update. The problem simply doesn't have a solution in my case.
    Oh, well. As I say, nice guys, but this is my third time speaking with tech support about a problem with Adobe software. Not going to try again. IMHO, the customer service system/process could use some work.

    As I said, it may not happen to everyone. Perhaps with a different operating platform or system version it may not happen. I was only reporting it because it happened to not just myself, but to the tech half a world away who shared my screen, saw the problem, and recreated it on his own machine/system.
    Here are the selections in the ePub Export dialog box that caused the problem. I can't imagine that what is selected for TOC settings or other non-image settings would have to do with it, but here they are.
    1. File > Export > Choose ePub as Format
    2. In ePub dialog box: General Settings
    Include Document Metadata checked
    ePub Cover, you can select Rasterize first page or Use Existing Image File, makes no difference
    Ordering, Based on Articles Panel
    Formatting Options: Leave as Default
    3. In ePub dialog box: Image
    Preserve Appearance from Layout checked
    Resolution, doesn't matter what you select, all produces the same result
    Everything in the first section below this is as default
    Image Conversion: JPEG (I've been using JPEG, but also tried it with a TIFF, and even a Photoshop file, no difference)
    JPEG Options: Maximum, Progressive
    Ignore Object Export Settings: I usually have this checked, but have tried it unchecked, and it made no difference
    4. In the ePub dialog box: Contents
    Format ePub Content: XHTML
    Use InDesign TOC Style checked (I've tried the default, and my own TOC style, no difference)
    CSS Options: I've tried Generate CSS and Use existing CSS template, never used Styles only. Made no difference
    5. Click OK.
    If you need what I do from the beginning...
    1. New file: Print (not web, which tends to not honor the HTML tags on export). I typically chose 1024 x 768 because that's the screen resolution for an iPad.
    2. Command-D, place file. I've tried JPG, TIFF, even Photoshop files of varying resolutions from 72 to 300. Files sizes from 800x600 to 1024x768 to sizes approximately double this. No difference.
    3. Drag cover to Articles Panel and name.
    4. Layout rest of eBook, etc.
    5. Display performance settings while in ID are set to High Quality.
    6. Triple check for errors (always a green light before exporting).
    These are ePub files that have validated, after fiddling with the CSS and XHTML file, as necessary, of course. I don't mess with any image coding.
    That's the steps!

Maybe you are looking for

  • How to copy files from a color classic w/broken floppy drive to an i-book ?

    How to copy files from a color classic w/broken floppy drive to an i-book ? I have a Coplor Classic with a system 7. There is no ethernet on color classic. The floppy drive is dead. I need some important files I have on the color classic... How do I

  • Calling all Guru's!!

    I've got a 90 min. Doc that I am trying to render at the highest quality. So in the sequence settings: video processing tab I toggled "Render all YUV material in High-Precision YUV" and motion filter quality is at BEST. And in Render Control: framera

  • Disntinguish between functional area and cost center

    Hello,      what's the real pupose of defining func. areas and assigning to cost centers. ok, we can capture all the costs of all cost centers , fine, but even the cost center will do that and we can report at cost center grp level or at any grp leve

  • Xcelsius with XMLA or XML Query Result Set

    Hi Experts, I want a direct connection from Xcelsius to my BW-Data. Because the new connection, coming with Fix Pack 2.1 is only avaiable for EHP 1 for NW 7.0 I tried to configure with XMLA and XML Query Result Set. This Document tells the necessary

  • Substitution Rule - CO

    Hi, I need to create a substitution rule in CO, but I don't know how to do it. I need to post a material in different cost element that is setup on valuation class - transaction GBB / Account modification VBR. Does anybody have a documentation about