Bugs I've Encountered In PSE 7

Here are all the reproducible bugs I’ve encountered in PSE 7.  Problems added since my last posting are marked [N].  In the coming weeks, I’ll evaluate PSE 8 to see how many of these have been fixed.
I’ve reported all of these problems to Adobe. Almost all of them are in the Organizer.  Based on all the reports on the forums, it appears that the Editor has far fewer problems than the Organizer.   Perhaps that’s because the Editor shares the same code with the professional Photoshop, while the Organizer appears to be an orphaned consumer product whose development Adobe has moved offshore.
For reference, my computer is a midrange Vista laptop with a dual-core 1.9 GHz processor, 4 GB of memory, and a 7200 RPM disk (the same speed as desktop disks).
File Management and Tagging
Major Problems
[N] The conversion of a catalog from PSE 6 to PSE 7 doesn’t properly handle photos that are stored within the PSE 6 catalog folder (as occurs when PSE 6 was used to restore a catalog from a backup).  As a result, it isn’t possible to save photos in version sets, and PSE 7 will create duplicate thumbnails in the Organizer for an edited file.
File > Backup/Restore Catalog doesn’t backup and restore audio in slide shows.
Using Folder Location view to move a folder containing hidden files imported in the catalog will silently fail to move the hidden files and will leave the unhidden files disconnected in the catalog.
When converting a previous-version catalog whose photos are stored inside the catalog folder, as occurs when you’ve previously used File > Restore Catalog with New Location, PSE 7 needlessly copies all those photos. If you have a very large catalog, this will waste huge amounts of disk space; and if there isn’t enough disk space to do the copy, the conversion will fail instantly with a generic non-explanatory error message.
After reconnecting a file on a network drive, PSE will let you import the file a second time, failing to recognize it as a duplicate.  The catalog is left in an inconsistent state, with two entries in the volume table for the network drive, one upper case and one lower case.
The Organizer fails very ungracefully when two drives have the same volume serial number, e.g. because of the use of a disk-cloning utility.
I’m very disappointed that Adobe didn’t add the three lines of code that would have issued a warning when it discovered two drives with the same number.  While most people will never encounter this, when it strikes someone, its symptoms are very mysterious.
The Reconnect command fails to reconnect when: you move your photos to a new drive, assign the drive the letter of the old drive to the new one, and leave both drives connected to your computer.
If a hard drive containing photos in the catalog gets its drive letter reassigned by Windows, then the left-hand folder pane of Display > Folder Location view shows the old drive letter, not the new one, as containing the photos.
This sounds innocuous, but it led a user on the forums to select the wrong drive when dragging and dropping a folder, permanently deleting some files.  This bug and the previous one with Reconnect have the same underlying cause – the Organizer doesn’t update drive letters in its catalog.
Folder Location view shows incorrect folder contents when more than one keyword tag is selected in the Keyword Tags pane.
Based on reports on the forums, there appear to be other situations where Folder Location view shows incorrect folder contents, but they haven’t been easy to reproduce.
The Restore Catalog command puts the wrong path into the restored catalog for folders whose name starts with the catalog name, and it will mark files in those folders as missing. For example if the catalog is named “houses”, and a folder containing photos in the catalog is named “houses photos”, files in the restored catalog will have the path “houses\ photos\” instead of “houses photos\”.
Minor Problems
In File > Export, the Common Basename can no longer be empty, and a hyphen is added automatically, so you can no longer get files named 1.jpg, 2.jpg, etc.
You can get files named 1.jpg, 2.jpg, etc. but you can’t get files named p1.jpg, p2.jpg, etc. – a hyphen is still added in that case.
Setting the Apply Metadata > Author or Copyright fields or the option Preserve Current Filename In XMP of the advanced options of the Photo Downloader causes duplicate files to be downloaded and imported.
Integration with Photoshop.com
Major problems
[N] Photoshop.com shows an incorrect date/time taken for photos with unknown month, day, or time.
For photos taken in years prior to 1970, the date/time shows as 12/31/1969 08:00 AM.  For photos with year taken 1970 or later, the date/time shows as the the first month/day/minute/second in that time period in UTC that then gets converted to local time; e.g. “7/2/2005” gets shown as “7/1/2005 5:00 PM” for a user in PDT.
[N] Photoshop.com doesn’t obey the EXIF Orientation metadata field and can show photos rotated incorrectly, e.g. if they were rotated with the PSE option Edit > Preferences > Files > Rotate JPEGs/TIFFs Using Orientation Metadata.
Changes to the order of photos in a PSE album aren’t synced to Photoshop.com, and vice versa.
Adding a photo to a second synced album will cause Photoshop.com to lose any changes you’ve made with PSE’s Edit > Adjust Date And Time.
If you you rename a file that’s synced with Photoshop.com, Photoshop.com doesn’t pick up the new name (important if you’re using Photoshop.com as a backup service).
Only the top photo in a version set is synced with Photoshop.com (so you can’t rely on Photoshop.com to backup version sets).
When a stack is synced with Photoshop.com, all the photos in the stack are synced, but the fact that they were in a stack is lost (so you can’t rely on Photoshop.com to backup stacks).
Map View
Major Problems
Map view is unusably slow with more than about 6-8,000 mapped photos.
When I tested PSE 7 by importing 12,000 photos (the size of my catalog) that had GPS locations, the red push-pins didn’t blink uncontrollably as they did in PSE 6.   But the Organizer crashed a number of times when I tried to zoom and pan the Map view until I was able to scroll the map to another country and then back again.   The CPU continued to consume 80% of a single CPU (40% of two), even 10 minutes after I closed Map view. When I selected Limit Search to Map Area, PSE took over a minute to respond.
It takes 5 seconds to assign a keyword tag to a photo if there are 1,000 or more photos with map locations.
In PSE 7, it takes 3 seconds with 1,000 photos, 12 seconds with 8,000 photos, and 18 seconds with 12,000 photos.
Giving a map location to a tag assigned to hundreds of photos makes both the Keywords pane and the Map view unusably slow.
Giving a map location to a tag assigned to 2000 photos makes assigning any keyword tag to a photo very slow (see above).    Searching on keyword tags takes 15 seconds, and a Show All takes 15 seconds.
Removing the map push-pin of a tag assigned to hundreds of photos mistakenly tries to update the metadata of each photo, which can take tens of minutes and fill up your recycle bin.
The weird thing is that assigning a map location to the tag doesn’t try to write the metadata of files with that tag.
Moving map locations always fails, silently (too bad if you want to record backcountry locations not namable via a place name).
If a photo with GPS coordinates is imported, it doesn’t show as a red push-pin on the map.
Scrolling the map or restarting the Organizer causes the pin to appear.
Color Management
Major Problems
The Organizer considers photos produced by cameras set to the color space Adobe RGB as untagged with a color profile, showing their colors incorrectly.
Metadata
Major Problems
When setting the Organizer’s date/time for imported photos containing EXIF:DateTimeOriginal but not XMP:DateTimeOriginal, PSE 7 doesn’t properly handle US Daylight Savings Time in years prior to 2007.
Edit > Adjust Date and Time doesn’t properly handle US Daylight Savings Time when setting date/times many decades ago, e.g. October 5, 1961 12:00 PM.
In Thumbnail View, the Organizer incorrectly orders files that have unknown time. For example, it will show a file dated 12/25/1976 8:00 PM PST after a file dated 12/26/1976 (unknown time) on a computer in time zone PST.
If you set a file's date/time fields to all unknown with Edit > Adjust Date And Time, the value of EXIF:DateTimeOriginal isn't cleared by File > Write Keyword Tag.
The File > Write Keyword Tag command doesn’t create or update .XMP sidecars for Nikon D300 or D80 .NEF raw files (but it does for Canon CR2 raw files).
New dates set by Edit > Adjust Date and Time sometimes get silently lost.
See http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Date/times_of_files for details and workarounds.
[N] Edit > Adjust Date and Time > Shift To New Starting Date And Time and > Shift By Set Number Of Hours writes the time in UTC rather than local time, as required by the standard, causing other tools to show the wrong date/time.
File > Write Keyword Tags and Properties fails to write the map location (GPS coordinates) of TIFFs (tested with TIFFs produced by the PSE Editor and the Nikon Coolscan V, Nikon Coolscan 5000, and Epson 4490 scanners).
File > Write Keyword Tags doesn’t write the map location (GPS coordinates) into the .xmp sidecar files of Nikon D80 or Canon G9 raw photos.
[N] The Organizer ignores correctly formatted EXIF GPS locations in some files that many other programs can read without trouble; this may be because the EXIF is encoded in little-endian byte order.
Minor Problems
[N] Deselecting the option Use “Last Modified” Date If EXIF Date Is Not Found does not work – the last-modified date is always used for an imported file that doesn’t contain an EXIF date.
The Properties – Metadata window shows the wrong value for Date Time Original when the month, day, or time is unknown.
Edit > Adjust Date and Time applied to a file with time “unknown” decrements the date by one day.
When you save an edited photo as a new file but not in a version set, the edited version picks up the date/time and caption of the original but not the keyword tags, star rating, or notes.
With the Import EXIF Caption option turned off, captions pre-existing in a file’s EXIF:ImageDescription metadata field reappear in the Organizer after invoking the Full Editor.
Searching
Major Problems
The timeline doesn’t correctly display date ranges spanning many years.
Using the Keyword Tags pane, you can no longer exclude a parent category from a search, e.g. exclude all photos tagged with any tag in the People category.
The User Guide gives two examples of how to use category exclusion that just don’t work in PSE 6 or 7.  Interestingly, you can almost work around this by doing a text search of “not <category tag>”, e.g. “not People”.   But this will also exclude photos that happen to have the word “people” in their filenames, captions, or notes, probably not what you want.
Find > By History > Imported On sorts the photo dates alphabetically, rather than by date/time, and it takes a couple of minutes on a large catalog, making the command almost useless; and it shows a scary message “Deleting Keyword Tags”.
[N] Searching with the Find Bar for “1 star and lower” doesn’t show photos with 0 stars.
Find > By Details > Rating Is Lower Than 1 Star does work.
Searching for “0 stars only” doesn’t work for photos in a catalog converted from PSE 5.
Searching with date ranges doesn’t properly handle time “unknown”.
Minor Problems
The Show All button sometimes doesn’t appear if you quickly type a query into the Search text box and hit Enter.
Setting a date range and then excluding two tags from the search clears the date range.
Show All doesn’t clear a date range set by Find > Set Date Range (can be very confusing).
Save Search Criteria As Smart Album isn’t available if a date range has been set but no other search criteria have been.
When searching, you can exclude a keyword tag and then include an album, but you can’t do it in the other order.
User Interface
Major Problems
On 1024x768 displays, and sometimes at higher resolutions, the Editor Print window is positioned to perfectly obscure the scroll bar of the drop-down list of printer profiles, leading people to think their printer’s profiles aren’t available.
This bug occurred with higher-resolution displays in PSE 6.
The menu bars don’t display if you have changed the screen DPI to be larger than 96 (as many people do on today’s ubiquitous high-res displays).
There is a workaround for both PSE 6 and 7. Set the option > Edit > Preferences > General > Use System Font.  The result isn’t that pretty, since some of the application text will be large and some will be small, but it’s functional, and you’ll still be able to use the higher DPI with all your other applications.
Minor Problems
In the Properties window of Full Screen mode, if you click in the Notes field and do Ctrl-A to select all the text, then click in the Caption field and do Ctrl-A to select its text, the notes remain highlighted.
In the Organizer, Help > System Info reports the wrong amount for “Built-in Memory” on computers with more than 2GB of installed memory.  (The command reports the correct amount in the Editor.)
The setting of View > Show Borders Around Thumbnails isn’t remembered after you restart PSE.
Copying a paragraph from Microsoft Word and pasting it into the Notes field of a keyword tag causes some of the spaces between words to be deleted.
Ctrl-A to select all text doesn’t work in the text fields of the Properties window.
Interestingly, you can use ctrl-A in the text fields of the full-screen mode Properties window.
In the full Editor, if at least one open photo is minimized to the Project Bin, Ctrl-Tab no longer cycles through the open windows.
Dialogs in the Editor sometimes bounce back when you try to move them.
Dates are shown by Display > Import Batch as 2\20\2008 rather than 2/20/2008.
In Create > Slide Show > Slide Show Preferences dialog, you can't use backspace or delete to clear the text in the Static and Transition Duration fields -- you need to select the text and then type over the selection (non-standard Windows behavior).
Escape doesn’t close the full-screen-mode Properties dialog.
You can’t use the Windows Explorer Tile command to tile the PSE Organizer and Editor windows.
The Editor window can’t be resized the standard Windows way by grabbing any edge, just the lower-right corner.
Alt doesn’t underline the shortcut letters of top-level menu items in the Full Editor (but it does in the Organizer).
The width of the Editor's Palette Bin can't be adjusted by dragging the left edge, as you can with all the other similar panes (Project Bin, Organizer Bin, Map View).
Slide Shows
Major Problems
The duration of a video clip included in a Slide Show is set to the default duration, not the length of the video clip, and right-click Edit Duration doesn’t change the clip’s duration.
For video clips, PSE 7 doesn’t enable the command to change the duration as it does for photos. But you can work around this by using Add Media > Photos And Videos From Folder to add the clip to the show.
An audio caption attached to a photo isn’t imported into a slide show even though the option Include Audio Captions as Narration is selected.
Editor
Minor Problems
[N] The Editor crashes if you invoke Quick Fix and use just one Touch Up tool (e.g. Whiten Teeth) and then save the file (but your changes are correctly saved).
The File > Save For Web command doesn’t remember the last settings (e.g. file format and quality) after your restart the Editor.
For a workaround, see http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Allow_Save_For.

Just kidding.    But, are you going to give us a bug comparison between 7 and 8 ?   I will probably sit version 8 out and get 9 next year.  Thanks for the list!
Juergen

Similar Messages

  • Bugs Ive Encountered In PSE 7

    Here are all the reproducible bugs Ive encountered in PSE 7. Problems added since my last posting on 10/5/08 are marked [N]. Because of limitations of the forum, this list is split across several messages.
    Ive reported all of these problems to Adobe. Almost all of them are in the Organizer. Based on all the reports on the forums, it appears that the Editor has far fewer problems than the Organizer. Perhaps thats because the Editor shares the same code with the professional Photoshop, while the Organizer appears to be an orphaned consumer product whose development Adobe has moved offshore.
    For reference, my computer is a midrange Vista laptop with a dual-core 1.8 GHz processor, 3 GB of memory, and a 7200 RPM disk (the same speed as desktop disks).
    File Management and Tagging
    Major Problems
    [N] File > Backup/Restore Catalog doesnt backup and restore audio in slide shows.
    [N] Using Folder Location view to move a folder containing hidden files imported in the catalog will silently fail to move the hidden files and will leave the unhidden files disconnected in the catalog.
    [N] When converting a previous-version catalog whose photos are stored inside the catalog folder, as occurs when youve previously used File > Restore Catalog with New Location, PSE 7 needlessly copies all those photos. If you have a very large catalog, this will waste huge amounts of disk space; and if there isnt enough disk space to do the copy, the conversion will fail instantly with a generic non-explanatory error message.
    [N] After reconnecting a file on a network drive, PSE will let you import the file a second time, failing to recognize it as a duplicate. The catalog is left in an inconsistent state, with two entries in the volume table for the network drive, one upper case and one lower case.
    The Organizer fails very ungracefully when two drives have the same volume serial number, e.g. because of the use of a disk-cloning utility.
    ]Im very disappointed that Adobe didnt add the three lines of code that would have issued a warning when it discovered two drives with the same number. While most people will never encounter this, when it strikes someone, its symptoms are very mysterious.
    The Reconnect command fails to reconnect when: you move your photos to a new drive, assign the drive the letter of the old drive to the new one, and leave both drives connected to your computer.
    If a hard drive containing photos in the catalog gets its drive letter reassigned by Windows, then the left-hand folder pane of Display > Folder Location view shows the old drive letter, not the new one, as containing the photos.
    ]This sounds innocuous, but it led a user on the forums to select the wrong drive when dragging and dropping a folder, permanently deleting some files. This bug and the previous one with Reconnect have the same underlying cause the Organizer doesnt update drive letters in its catalog.
    Folder Location view shows incorrect folder contents when more than one keyword tag is selected in the Keyword Tags pane.
    ]Based on reports on the forums, there appear to be other situations where Folder Location view shows incorrect folder contents, but they havent been easy to reproduce.
    The Restore Catalog command puts the wrong path into the restored catalog for folders whose name starts with the catalog name, and it will mark files in those folders as missing. For example if the catalog is named houses, and a folder containing photos in the catalog is named houses photos, files in the restored catalog will have the path houses\ photos\ instead of houses photos\.

    <i>Part III</i><br /><br /><b>Color Management</b><br /><br /><i>Major Problems</i><br /><br />The Organizer considers photos produced by cameras set to the color space Adobe RGB as untagged with a color profile, showing their colors incorrectly.<br /><br />The Original (left) image in the Save For Web window is displayed without using the photos profile, making it hard to compare the preview with the original.<br /><br /><b>Metadata</b><br /><br /><i>Major Problems</i><br /><br />[N] When setting the Organizers date/time for imported photos containing EXIF:DateTimeOriginal but not XMP:DateTimeOriginal, PSE 7 doesnt properly handle US Daylight Savings Time in years prior to 2007.<br /><br />[N] Edit > Adjust Date and Time doesnt properly handle US Daylight Savings Time when setting date/times many decades ago, e.g. October 5, 1961 12:00 PM.<br /><br />[N] In Thumbnail View, the Organizer incorrectly orders files that have unknown time. For example, it will show a file dated 12/25/1976 8:00 PM PST after a file dated 12/26/1976 (unknown time) on a computer in time zone PST.<br /><br />[N] If you set a file's date/time fields to all unknown with Edit > Adjust Date And Time, the value of EXIF:DateTimeOriginal isn't cleared by File > Write Keyword Tag.<br /><br />[N] The File > Write Keyword Tag command doesnt create or update .XMP sidecars for Nikon D300 or D80 .NEF raw files (but it does for Canon CR2 raw files).<br /><br />New dates set by Edit > Adjust Date and Time sometimes get silently lost. <br /><br />]If you set the date/time for a BMP, PDF, or Quicktime movie, or a file thats marked readonly, invoking the full Editor or Edit > Update Thumbnail will discard the adjusted date/time. <br /><br />Edit > Adjust Date and Time sometimes sets the wrong date/time for the EXIF:CreateDate and DateTimeOriginal, causing other tools to show the wrong date/time.<br /><br />File > Write Keyword Tags and Properties fails to write the map location (GPS coordinates) of TIFFs (tested with TIFFs produced by the PSE Editor and the Nikon Coolscan V, Nikon Coolscan 5000, and Epson 4490 scanners).<br /><br />File > Write Keyword Tags doesnt write the map location (GPS coordinates) into the .xmp sidecar files of Nikon D80 or Canon G9 raw photos.<br /><br /><i>Minor Problems</i><br /><br />[N] The Properties  Metadata window shows the wrong value for Date Time Original when the day is unknown.<br /><br />Edit > Adjust Date and Time applied to a file with time unknown decrements the date by one day.<br /><br />When you save an edited photo as a new file but not in a version set, the edited version picks up the date/time and caption of the original but not the keyword tags, star rating, or notes.<br /><br />With the Import EXIF Caption option turned off, captions pre-existing in a files EXIF:ImageDescription metadata field reappear in the Organizer after invoking the Full Editor.<br /><br /><b>Searching</b><br /><br /><i>Major Problems</i><br /><br />The timeline doesnt correctly display date ranges spanning many years. <br /><br />Using the Keyword Tags pane, you can no longer exclude a parent category from a search, e.g. exclude all photos tagged with any tag in the People category. <br /><br />]The User Guide gives two examples of how to use category exclusion that just dont work in PSE 6 or 7.  Interestingly, you can almost work around this by doing a text search of not <category tag>, e.g. not People.   But this will also exclude photos that happen to have the word people in their filenames, captions, or notes, probably not what you want.<br /><br />Find > By History > Imported On sorts the photo dates alphabetically, rather than by date/time, and it takes a couple of minutes on a large catalog, making the command almost useless; and it shows a scary message Deleting Keyword Tags. <br /><br />Searching for 0 stars only doesnt work for photos in a catalog converted from PSE 5.<br /><br />Searching with date ranges doesnt properly handle time unknown. <br /><br /><i>Minor Problems</i><br /><br />[N] The Show All button sometimes doesnt appear if you quickly type a query into the Search text box and hit Enter.<br /><br />Setting a date range and then excluding two tags from the search clears the date range. <br /><br />Show All doesnt clear a date range set by Find > Set Date Range (can be very confusing). <br /><br />Save Search Criteria As Smart Album isnt available if a date range has been set but no other search criteria have been. <br /><br />When searching, you can exclude a keyword tag and then include an album, but you cant do it in the other order.

  • FW CS4 Major Bugs I've Encountered So Far

    *Had to edit because even the bullet tag doesn't even work.
    C'MON ADOBE!*
    Some of these have been covered already, but I just wanted to
    start a definite list of things that make CS4 unusable and should
    have been fixed in the beta before the final release.
    New Text Engine:
    • Crazy Selection Boxes - The text remains in it's set
    place but the selection box that should be surrounding it is
    located elsewhere on the page. Selecting the text does not move the
    selection box back to the text, but rather the text to the
    selection box, rendering precise formatting useless. Seems to be
    triggered by using the arrow keys to move text, or shift+arrow keys
    for faster 10px movement.
    • Convert Text to Paths - Converting text to paths
    outputs something unrecognizable, especially fonts under 12pt/px.
    • Anti-aliasing - Text looks nothing like in-browser
    text, even when fiddling around with the advanced anti-aliasing
    settings.
    • Auto Kern - Does nothing?
    • Text Editor - Removed... but not?
    New Vector Engine
    • Combining Paths - produces graphic
    anomalies/bleeding. Go "punch" a box into another. A 1px line is
    formed when there shouldn't be anything at all.
    Tabs
    • Selecting Objects - When switching between tabs, a
    double click is required to select an object when going from one
    tab to another, even though said objects appears to be selected
    before switching back.
    • Exporting - When multiple tabs are open and I hit
    Command + Shift + X to export, the document that is going to be
    exported is not the document/tab I have currently selected/open.
    Going into the open document and selecting an object within will
    export it correctly.
    • Tab Management - Not really a bug, but very annoying.
    When the tab bar overflows with tabs, a small button appears at the
    right to scroll through each tab. But you can't scroll, you have to
    select the needed tab from a dropdown.
    • Moving Between/Creating New Tabs - Tabs should act
    more like safari in that objects should be able to be dragged to a
    tab in the tab bar and the tab that is being hovered over should
    open. Also, an object from within or from outside safari should be
    able to be dragged to the tab bar to be opened into a new
    document/tab.
    Fireworks in General
    • Closing - Most of the time, exiting Fireworks using
    Cmd + Q results in a "crash report" window. Not sure why.
    • Resizing Windows - Even without the Application
    Frame, maximizing the window can be a pain. If the "properties"
    toolbar isn't attached to the bottom of the screen, hitting the
    green + button on the main document window will maximize the window
    all the way to the bottom of the screen, behind the properties
    toolbar. It's kinda annoying.
    Text Engine - Convert text to paths sample:
    http://timshundo.com/dpud/uploads/fwcrap.png
    Text Engine - Crazy text boxes sample:
    http://www.timshundo.com/dpud/uploads/ugh.png
    Vector Engine - Combining paths sample:
    http://www.timshundo.com/dpud/uploads/fwcs41.png
    I think that's it for now. Any more I remember/find will be
    posted here. Dearest Adobe, I'm severely disappointed with this
    release and expect a (free) update that fixes it all.

    That works, but it's really just a quick fix. I find myself
    selecting all of the objects on the page before I save and switch
    them over to the cs3 engine. That has to mean something to you
    guys.
    In all, the new engine just isn't very good. Things appear
    bolder than before. All that was wrong with the old engine is that
    you would occasionally get 1 or 2 little rogue pixels when you drew
    paths with tight corners around 1 or 2°.
    quote:
    Originally posted by:
    ArunKaza
    Hi Tim,
    The visibility of 1px lines sometimes on punching 2 vectors
    is because of the differences in the vector rendering engines used
    in FWCS3 and FWCS4.
    While the vector rendering engine in CS4 was improved to be
    more faster and produce smoother antialiased vectors, subtle
    differences do exist between these engines.
    The good news is that you can use the older engine
    selectively on a vector if you wish to, using the command
    Use_FWCS3_Vector_Rendering_For_Selection. This marks the selected
    vector to switch to using the older rendering engine.
    Any vector brought into CS4 which was created in CS3 or
    earlier version of Fireworks, would still continue to use the older
    vector rendering engine to give the exact pixels. These can also be
    forced to use newer vector engine by using the script command
    Use_FWCS4_Vector_Rendering_For_Selection.
    Since these commands act on the selected objects, please be
    sure to select only those that need to be effected.
    For ease, I have attached these 2 command .jsf files that can
    be placed at below mentioned locations and used to switch b/w FWCS3
    and FWCS4 rendering.
    Windows: "[C:]\Program Files\Adobe\Adobe Fireworks
    CS4\Configuration\Commands\"
    Mac: "/Applications/Adobe Fireworks
    CS4/Configuration/Commands/"
    --Arun
    quote:
    Originally posted by:
    Tim Shundo
    New Vector Engine
    • Combining Paths - produces graphic
    anomalies/bleeding. Go "punch" a box into another. A 1px line is
    formed when there shouldn't be anything at all.
    Use_FWCS3_Vector_Rendering_For_Selection
    Use_FWCS4_Vector_Rendering_For_Selection

  • PSE 7 Problems Fixed in PSE 8

    Since PSE 6 was released, I’ve tracked all the reproducible bugs I’ve encountered and reported to Adobe.  I’ve tested these problems in PSE 8 and listed the results below – problems that appear to have been fixed in PSE 8 are marked [F], and problems that remain unfixed are marked [U].
    Overview
    There’s good and bad news. Adobe has fixed a number of serious bugs in the Organizer, but it has left most unfixed, even though they’ve been present since at least version 6.  Even worse, the two major features introduced in the PSE 8 Organizer, face tagging and the keyword-tags text box, have show-stopper problems. And even worse yet, Full Screen view is now painfully slow with large catalogs.
    The most important fixes address serious problems with PSE’s handling of drives that were introduced in version 6. PSE now notices when a drive’s letter has changed, a problem that has bedeviled many users upgrading or rearranging their drives. Also, PSE now ignores the case of UNC pathnames (network drives), no longer creating duplicate volumes for the same network drive.  Unfortunately, one serious bug remains: PSE still gets horribly confused when there are two drives with the same volume serial number, and it still doesn’t even issue a warning.
    But many long-standing problem areas remain: The Map View is an unusable toy.  The handling of metadata is riddled with bugs.  Folder Location view shows the wrong contents of folders. Searching has numerous bugs making it clumsy and confusing.
    Overall, of all the bugs I’ve reported, PSE 8 fixes 8 of 46 major ones and 8 of 28 minor ones:
    Major
    Minor
    Fixed
    Unfixed
    Fixed
    Unfixed
    File Management and Tagging
    4
    6
    2
    Integration with Photoshop.com
    2
    5
    Map View
    6
    Color Management
    1
    Metadata
    10
    2
    3
    Searching
    8
    5
    User Interface
    1
    1
    5
    9
    Slide Shows
    1
    1
    Editor
    1
    1
    Total
    8
    38
    8
    20
    I’ve reported all of these problems to Adobe. Almost all of them are in the Organizer.  Based on all the reports on the forums, it appears that the Editor has far fewer problems than the Organizer.   Perhaps that’s because the Editor shares the same code with the professional Photoshop, while the Organizer appears to be an orphaned consumer product whose development Adobe has moved offshore.
    For reference, my computer is a midrange Vista laptop with a dual-core 1.9 GHz processor, 4 GB of memory, and a 7200 RPM disk (the same speed as desktop disks).
    New Problems in PSE 8
    [U] PSE 8 crashes or gets intolerably slow after using the new Keyword Tags text box a small number of times.
    On my 4 GB Vista 32 system, PSE crashes after tagging 41 photos.
    [U] If you use the new Keyword Tags text box to apply an existing tag name with a comma in it, PSE will silently create two new tags instead.
    Apply the existing tag “San Francisco, CA” will create two new tags, “San Francisco” and “CA”.
    [U] After applying a tag, the Keyword Tags text box loses keyboard focus and you need to mouse-click in the box again to enter another tag.
    Forcing the use of the mouse defeats the purpose of the Keyword Tags text box, which is to make tagging much faster.
    [U] The Find > Find People For Tagging command locks up the Organizer for about 30 seconds after you click Done (even if you haven’t made any changes), when using larger catalogs.
    On a catalog with 10,000 thumbnails showing, the cursor spins for 30 seconds after clicking done.  But you can work around this by doing a tag search or setting a date range to have only a small number of thumbnails showing before you invoke the command.
    [U] In the Find > Find People For Tagging command, when you select Add Missing Person, you usually can’t resize the selection box by grabbing the lower-right or lower-center handles, which are the handles that most right-handed people are likely to use.
    If you move the mouse very quickly so that it is over the photo before the selection box appears, you can usually resize the box with those handles.  But you have to be very quick.
    [U] The Find > Find People For Tagging command doesn’t do auto-complete on pre-existing People tags, making it very hard to use with existing catalogs.
    I have over two hundred People tags in my catalog.  Because the command doesn’t auto-complete on pre-exisiting People tags and will silently create new tags, and because I don’t remember exact spellings (that’s the point of auto-complete!), I found myself creating duplicate tags (e.g. “John Ellis” instead of “John R. Ellis”, “Bob Smith” instead of “Robert Smith”).  It’s painful to clean up such a mess.
    [U] Full Screen view (F11) is much slower than in PSE 7 on larger catalogs.
    With a 14,000-file catalog and all thumbnails visible, PSE 7 takes 6 seconds to invoke F11, while PSE 8 takes 13 seconds.   With just 20 thumbnails visible (e.g. when working on the most recent import batch), PSE 7 takes 1 second, while PSE 8 takes 7 seconds. This makes selecting the good and weeding out the bad significantly slower.
    [U] PSE doesn’t remember the settings if you toggle the Full-Screen Quick Edit Panel and Quick Organize Panel to disappear completely.
    On 4:3 displays, it’s desirable to hide the panels completely in full-screen view, so you see the entire image without the panels overlapping them (that’s the point of full-screen view, no?).  But PSE forgets the toggle settings, even in the same session.
    [U] The keyword tagging in the Quick Organize Panel doesn’t auto-complete tags you type, making it useless with more than a dozen or so tags.
    It’s worse than useless, since it will silently create a new tag if you mistype the name of an existing one.  And the “tag cloud” is a silly toy that doesn’t help with hundreds of tags.
    File Management and Tagging
    Major Problems
    [F] After reconnecting a file on a network drive, PSE will let you import the file a second time, failing to recognize it as a duplicate.  The catalog is left in an inconsistent state, with two entries in the volume table for the network drive, one upper case and one lower case.
    [F] The Reconnect command fails to reconnect when: you move your photos to a new drive, assign the drive the letter of the old drive to the new one, and leave both drives connected to your computer.
    [F] If a hard drive containing photos in the catalog gets its drive letter reassigned by Windows, then the left-hand folder pane of Display > Folder Location view shows the old drive letter, not the new one, as containing the photos.
    This sounds innocuous, but it led a user on the forums to select the wrong drive when dragging and dropping a folder, permanently deleting some files.  This bug and the previous one with Reconnect had the same underlying cause – the Organizer didn’t update drive letters in its catalog.  Fixed in PSE 8.
    [F] The Restore Catalog command puts the wrong path into the restored catalog for folders whose name starts with the catalog name, and it will mark files in those folders as missing. For example if the catalog is named “houses”, and a folder containing photos in the catalog is named “houses photos”, files in the restored catalog will have the path “houses\ photos\” instead of “houses photos\”.
    [U] Folder Location view shows incorrect folder contents when more than one keyword tag is selected in the Keyword Tags pane.
    Based on reports on the forums, there appear to be other situations where Folder Location view shows incorrect folder contents, but they haven’t been easy to reproduce.
    [U] The Organizer fails very ungracefully when two drives have the same volume serial number, e.g. because of the use of a disk-cloning utility.
    I remain mystified that Adobe didn’t add the three lines of code that would have issued a warning when it discovered two drives with the same number.  While most people will never encounter this, when it strikes someone, its symptoms are very mysterious (and a lot of people using cloning utilities).
    [U] The conversion of a catalog from PSE 6 to PSE 8 doesn’t properly handle photos that are stored within the PSE 6 catalog folder (as occurs when PSE 6 was used to restore a catalog from a backup).  As a result, it isn’t possible to save photos in version sets, and PSE 8 will create duplicate thumbnails in the Organizer for an edited file.
    [U] File > Backup/Restore Catalog doesn’t backup and restore audio in slide shows.
    [U] Using Folder Location view to move a folder containing hidden files imported in the catalog will silently fail to move the hidden files and will leave the unhidden files disconnected in the catalog.
    [U] When converting a previous-version catalog whose photos are stored inside the catalog folder, as occurs when you’ve previously used File > Restore Catalog with New Location, PSE 8 needlessly copies all those photos. If you have a very large catalog, this will waste huge amounts of disk space; and if there isn’t enough disk space to do the copy, the conversion will fail instantly with a generic non-explanatory error message.
    Minor Problems
    [U] In File > Export, the Common Basename can no longer be empty, and a hyphen is added automatically, so you can no longer get files named 1.jpg, 2.jpg, etc.
    You can get files named 1.jpg, 2.jpg, etc. but you can’t get files named p1.jpg, p2.jpg, etc. – a hyphen is still added in that case.
    [U] Setting the Apply Metadata > Author or Copyright fields or the option Preserve Current Filename In XMP of the advanced options of the Photo Downloader causes duplicate files to be downloaded and imported.
    Integration with Photoshop.com
    Major problems
    [F] Adding a photo to a second synced album will cause Photoshop.com to lose any changes you’ve made with PSE’s Edit > Adjust Date And Time.
    [F] If you you rename a file that’s synced with Photoshop.com, Photoshop.com doesn’t pick up the new name (important if you’re using Photoshop.com as a backup service).
    [U] Photoshop.com shows an incorrect date/time taken for photos with unknown month, day, or time.
    The date/time shows as the the first month/day/minute/second in that time period in UTC that then gets converted to local time; e.g. “7/2/2005” gets shown as “7/1/2005 5:00 PM” for a user in PDT.
    [U] Photoshop.com doesn’t obey the EXIF Orientation metadata field and can show photos rotated incorrectly, e.g. if they were rotated with the PSE option Edit > Preferences > Files > Rotate JPEGs/TIFFs Using Orientation Metadata.
    [U] Changes to the order of photos in a PSE album aren’t synced to Photoshop.com, and vice versa.
    [U] Only the top photo in a version set is synced with Photoshop.com (so you can’t rely on Photoshop.com to backup version sets).
    [U] When a stack is synced with Photoshop.com, all the photos in the stack are synced, but the fact that they were in a stack is lost (so you can’t rely on Photoshop.com to backup stacks).
    Map View
    Major Problems
    [U] It takes 4 seconds to assign a keyword tag to a photo if there are 2,000 or more photos with map locations.
    It takes 2 seconds with 1,000 photos, 6 seconds with 4000 photos, and 11 seconds with 8,000 photos, and 21 seconds with 12,000 photos.
    [U] Map view is unusably slow with more than 8 - 10,000 mapped photos.
    When I imported 12,000 photos (the size of my catalog) that had GPS locations, the Organizer crashed a number of times when I tried to zoom and pan the Map view.   When I selected Limit Search to Map Area, PSE took over a minute to respond.
    [U] Giving a map location to a tag assigned to hundreds of photos makes both the Keywords pane and the Map view unusably slow.
    Giving a map location to a tag assigned to 1700 photos makes assigning any keyword tag to a photo very slow, 12 seconds.    Searching on keyword tags and Show All each take 13 seconds.
    [U] Removing the map push-pin of a tag assigned to hundreds of photos mistakenly tries to update the metadata of each photo, which can take tens of minutes and fill up your recycle bin.
    The weird thing is that assigning a map location to the tag doesn’t try to write the metadata of files with that tag.
    [U] Moving map locations always fails, silently (too bad if you want to record backcountry locations not namable via a place name).
    [U] If a photo with GPS coordinates is imported, it doesn’t show as a red push-pin on the map.
    Scrolling the map or restarting the Organizer causes the pin to appear.
    Color Management
    Major Problems
    [U] The Organizer considers photos produced by cameras set to the color space Adobe RGB as untagged with a color profile, showing their colors incorrectly.
    Metadata
    Major Problems
    [U] The File > Write Keyword Tag command doesn’t create or update .XMP sidecars for Nikon D300 or D80 .NEF raw files (but it does for Canon CR2 raw files).
    The PSE 8 Write Keyword Tag command now gives a warning when you try to invoke it on a D300 .NEF raw file. Why PSE can write sidecars for Canon but not Nikon raw files is a mystery – it’s no harder to handle one than the other.
    [U] File > Write Keyword Tags and Properties fails to write the map location (GPS coordinates) of TIFFs (tested with TIFFs produced by the PSE Editor and the Nikon Coolscan V, Nikon Coolscan 5000, and Epson 4490 scanners).
    [U] File > Write Keyword Tags doesn’t write the map location (GPS coordinates) into the .xmp sidecar files of Nikon D80 or Canon G9 raw photos.
    [U] The Organizer ignores correctly formatted EXIF GPS locations in some files that many other programs can read without trouble; this may be because the EXIF is encoded in little-endian byte order.
    [U] New dates set by Edit > Adjust Date and Time sometimes get silently lost.
    See http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Date/times_of_files for details and workarounds.
    [U] Edit > Adjust Date and Time > Shift To New Starting Date And Time and > Shift By Set Number Of Hours writes the time in UTC rather than local time, as required by the standard, causing other tools to show the wrong date/time.
    [U] In Thumbnail View, the Organizer incorrectly orders files that have unknown time. For example, it will show a file dated 12/25/1976 8:00 PM PST after a file dated 12/26/1976 (unknown time) on a computer in time zone PST.
    [U] If you set a file's date/time fields to all unknown with Edit > Adjust Date And Time, the value of EXIF:DateTimeOriginal isn't cleared by File > Write Keyword Tag.
    [U] Edit > Adjust Date and Time doesn’t properly handle US Daylight Savings Time when setting date/times many decades ago, e.g. October 5, 1961 12:00 PM.
    [U] When setting the Organizer’s date/time for imported photos containing EXIF:DateTimeOriginal but not XMP:DateTimeOriginal, PSE 7 doesn’t properly handle US Daylight Savings Time in years prior to 2007, e.g. October 31, 2006 12:00 PM.
    Minor Problems
    [F] The Properties – Metadata window shows the wrong value for Date Time Original when the month, day, or time is unknown.
    [F] When you save an edited photo as a new file but not in a version set, the edited version picks up the date/time and caption of the original but not the keyword tags, star rating, or notes.
    Now, the edited version picks up date/time, caption, notes, and keyword tags, but not the star rating, which could be charitably interpreted as a plausible design decision.
    [U] Deselecting the option Use “Last Modified” Date If EXIF Date Is Not Found does not work – the last-modified date is always used for an imported file that doesn’t contain an EXIF date.
    [U] Edit > Adjust Date and Time applied to a file with time “unknown” decrements the date by one day.
    [U] With the Import EXIF Caption option turned off, captions pre-existing in a file’s EXIF:ImageDescription metadata field reappear in the Organizer after invoking the Full Editor.
    Searching
    Major Problems
    [U] The timeline doesn’t correctly display date ranges spanning many years.
    [U] Using the Keyword Tags pane, you can no longer exclude a parent category from a search, e.g. exclude all photos tagged with any tag in the People category.
    The User Guide gives two examples of how to use category exclusion that just don’t work in PSE 6, 7, or 8.  Interestingly, you can almost work around this by doing a text search of “not <category tag>”, e.g. “not People”.   But this will also exclude photos that happen to have the word “people” in their filenames, captions, or notes, probably not what you want.  You can also use the text query “not tag:<category tag>”, .e.g. “not tag:places”, but this will exclude all tags containing “places” as part of their name – there is no way to get an exact match of a tag name.
    [U] Find > By History > Imported On sorts the photo dates alphabetically, rather than by date/time.
    When the results first display, they are now sorted by Imported From then (correctly) by Date/Time. However, if you click on the Date/Time column header to sort by that column, the dates are sorted alphabetically (incorrectly).
    [U] Find > By History > Imported On takes a couple of minutes on a large catalog, making the command almost useless.
    [U] Find > By History > Imported On shows a scary message “Deleting Keyword Tags” that is apparently harmless.
    [U] Searching with the Find Bar for “1 star and lower” doesn’t show photos with 0 stars.
    Find > By Details > Rating Is Lower Than 1 Star does work.
    [U] Searching for “0 stars only” doesn’t work for photos in a catalog converted from PSE 5.
    [U] Searching with date ranges doesn’t properly handle time “unknown”.
    Minor Problems
    [U] The Show All button sometimes doesn’t appear if you quickly type a query into the Search text box and hit Enter.
    [U] Setting a date range and then excluding two tags from the search clears the date range.
    [U] Show All doesn’t clear a date range set by Find > Set Date Range (can be very confusing).
    [U] Save Search Criteria As Smart Album isn’t available if a date range has been set but no other search criteria have been.
    [U] When searching, you can exclude a keyword tag and then include an album, but you can’t do it in the other order.
    User Interface
    Major Problems
    [?] On 1024x768 displays, and sometimes at higher resolutions, the Editor Print window is positioned to perfectly obscure the scroll bar of the drop-down list of printer profiles, leading people to think their printer’s profiles aren’t available.
    I can’t reproduce this in PSE 8.  The Editor’s Print dialog is all rearranged.  But this bug struck some people and not others, so it may be still lurking.
    [U] The menu bars don’t display if you have changed the screen DPI to be larger than 96 (as many people do on today’s ubiquitous high-res displays).
    Adobe should be embarrassed about this, given that more and more computers are shipping preconfigured with higher DPIs.  See http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#The_Organizers_Menu_Bar_ doesnt_show for a workaround.
    Minor Problems
    [F] Copying a paragraph from Microsoft Word and pasting it into the Notes field of a keyword tag causes some of the spaces between words to be deleted.
    [F] In the full Editor, if at least one open photo is minimized to the Project Bin, Ctrl-Tab no longer cycles through the open windows.
    [F] The Editor window can’t be resized the standard Windows way by grabbing any edge, just the lower-right corner.
    Well, almost – you can grab the left, right, and bottom edges but not the top.
    [F] Alt doesn’t underline the shortcut letters of top-level menu items in the Full Editor (but it does in the Organizer).
    Both the Editor and Organizer don’t show the underline until you let up on the Alt key, whereas other Windows program show the underline when you first press the Alt key.
    [F] The width of the Editor's Palette Bin can't be adjusted by dragging the left edge, as you can with all the other similar panes (Project Bin, Organizer Bin, Map View).
    [U] In the Properties window of Full Screen mode, if you click in the Notes field and do Ctrl-A to select all the text, then click in the Caption field and do Ctrl-A to select its text, the notes remain highlighted.
    [U] In the Organizer, Help > System Info reports the wrong amount for “Built-in Memory” on computers with more than 2GB of installed memory.  (The command reports the correct amount in the Editor.)
    [U] The setting of View > Show Borders Around Thumbnails isn’t remembered after you restart PSE.
    [U] Ctrl-A to select all text doesn’t work in the text fields of the Properties window.
    Interestingly, you can use ctrl-A in the text fields of the full-screen mode Properties window.
    [U] Dialogs in the Editor sometimes bounce back when you try to move them.
    [U] Dates are shown by Display > Import Batch as 2\20\2008 rather than 2/20/2008.
    [U] In Create > Slide Show > Slide Show Preferences dialog, you can't use backspace or delete to clear the text in the Static and Transition Duration fields -- you need to select the text and then type over the selection (non-standard Windows behavior).
    [U] Escape doesn’t close the full-screen-mode Properties dialog.
    [U] You can’t use the Windows Explorer Tile command to tile the PSE Organizer and Editor windows.
    The Editor can now be tiled by Windows Explorer and other window managers, but the Organizer still can’t.
    Slide Shows
    Major Problems
    [F] The duration of a video clip included in a Slide Show is set to the default duration, not the length of the video clip, and right-click Edit Duration doesn’t change the clip’s duration.
    PSE now sets the duration to the length of the clip.  You can’t edit the duration, though – you can invoke Edit Duration, but PSE ignores the new value.
    [U] An audio caption attached to a photo isn’t imported into a slide show even though the option Include Audio Captions as Narration is selected.
    For an individual slide, you can give the Use Existing Audio Caption command to import that photo’s existing audio caption.
    Editor
    Minor Problems
    [F] The Editor crashes if you invoke Quick Fix and use just one Touch Up tool (e.g. Whiten Teeth) and then save the file (but your changes are correctly saved).
    [U] The File > Save For Web command doesn’t remember the last settings (e.g. file format and quality) after your restart the Editor.
    For a workaround, see http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Allow_Save_For.

    John,
    Firstly, my apologies for the length of this post – it has been fermenting a while.  For those in a hurry I have split it into two sections – the first contains some general comments on the situation with PSE (v 7 in my case) and Adobe (as I see it) and the second contains a list of issues that I have encountered and some suggestions for improvement.  As with you, my comments are largely directed at the Organiser module within PSE.
    Part 1:
    Before going any further I’d like to say what an excellent job you’ve done in cataloguing, understanding and in many cases providing solutions to a number of bugs.  Adobe should be paying you a hefty sum for doing this work.  It’s a welcome change from a large percentage of what you read in blogs and forums to see things dealt with systematically, objectively and in an informed way.
    I’m less impressed with Adobe’s approach.  In my opinion, if you choose not to provide program updates to your customers (i.e. you get what you bought in the box and that’s it) then you have a moral obligation to make sure that what you sell is as robust and free of bugs as possible.
    I would be very surprised if they were not well aware of the comments you have made (if they aren’t then that would indicate an appalling failure of their ability to process feedback).  The fact that they have not, in subsequent releases, dealt with all of the issues that have been highlighted is not good.  I would go further and suggest that it is actually a breach of fair trading practice and disingenuous to sell the product as “fit for purpose” knowing these bugs are still in place.
    It’s unreasonable to expect software to be absolutely faultless, and this is why the issuing of updates is a much “fairer” system.  The problem, I think, with Adobe’s approach is that to entice new customers to each release they need to provide new features.  A natural consequence of this is that there is a temptation to prioritise development of new features rather than providing solutions to existing issues.  There is no incentive for Adobe to change this state of affairs for as long as customers are purchasing their products.  In this respect one of the problems is that many of the reviewers to whom prospective customers go will rely on first impressions and will not uncover many of the issues.  Adobe may be comfortable with this situation (and on relying on the reflected aura of Photoshop) but their product is not cheap and there is plenty of scope for competitors to provide a more robust, dependable product at cheaper price.  With free applications like Picasa they will need to be very careful they don’t drop the ball.
    Don’t get me wrong I think the concept of PSE organiser is excellent (I actually prefer it to my experience of Lightroom), it is the quality of execution that I have issues with.
    My first experience of PSE was version 3 and this was positive enough for me to purchase PSE 7.  However, my biggest disappointment with PSE 7, because to me it is fundamental, has been the quality of rendering images in full screen mode.  Yours is the first comment I have seen that comments on the appearance of “jaggies” when displaying images in PSE.  My understanding is that this relates to the anti-aliasing which is carried out when converting from image to display resolution and the level to which this smoothes out gradients in hue, saturation and luminance.  I never observed this problem is PSE 3.  Although the degree of anti-aliasing is a subjective preference, I was deeply disappointed and still find it hard to believe that free or bundled software (picture manager, windows picture viewer, etc) can manage this when PSE 7 can’t.
    Anyway, I’m not sure how to illicit a change from Adobe.  One way is to write the sort of rant I have above although I doubt this will make much difference.  In any case keep up the good work and hopefully something will come of it.
    Part 2:
    Some issues I’ve encountered:
    Migration from Windows XP to Windows 7 – change in directory structure means that the “documents and settings” part of the user directory path in XP (i.e. c:\documents and settings\<<username>>\etc.) is now a shortcut which redirects you to the new location for user files which is c:\users\<<username>> \etc.  If you are migrating from an old XP machine to a new Windows 7 one, you’ve kept your username the same and you have tried to retain the same directory structure then PSE 7 will still find files in your catalogue with the old style path.  However, it will not recognise duplicates if you accidentally re-import the same files now they are on your Windows 7 machine.  My workaround for this is to use an external file manager (e.g. windows explorer) to change the name of the directory that contains all of your photos.  This causes PSE 7 to fail to resolve the path locations.  You can then can select the relevant files and reconnect using the reconnect facility (File-Reconnect-Missing Files);
    Watched folders are lost for any drive other than C when PSE 7 is closed and then reopened;
    Duplicate files are not recognised and can be imported if they are not on the C drive (i.e. on an external drive);
    Selecting a category selects all of the keyword tags/subcategories beneath it but excluding it does not exclude all of the keyword tags/subcategories beneath it; however, both selecting and excluding a sub-category selects and excludes the tags/sub categories beneath it;
    Searches bring back the entire version set or stack even if only one of the files within meets the search criteria;
    The instant search facility will sometimes decide that a number typed in is a date and will not find some files you would expect it to e.g. those where the number typed in is part of the filename rather than a date;
    Anti-aliasing is insufficient – jaggies appear on jpegs displayed at certain zoom level.  Interestingly this does not seem to occur if a jpeg has been created from a raw file through PSE 7 rather than an external application (at least for the camera I have).
    Some suggestions:
    Find duplicates facility;
    Sort by filename and other file data;
    Hide directories in the folder directory pane of the folder view if they contain no imported files – in PSE3 this was the only option and was actually quite useful to confirm that there were no imported files in a certain location (e.g. if e:\...etc was not in the list then you knew that you had no imported files located on the e:\ drive).  It would be good to have this a display option.
    Allow filters to be applied only to selected files;
    Allow files to be rotated in the organiser without actually resaving them as a rotated file.

  • Isync Tiger BUG: Contacts created in phone don't sync into Addressbk Group

    This is a bug I've encountered with iSync running on Tiger.
    I use iSync to sync my AddressBook contacts with my Motorola Razor.
    I have many contacts, but I only need a few of them synced with my phone, so I created a Group called "Phone" in AddressBook.app, and have set my sync preferences in iSync to sync only those contacts in the contacts group "Phone".
    When I create a new contact in the phone, and then sync with iSync, the new contact does NOT appear in my designated Group "Phone", but instead in the "All" contacts category. This didn't happen in Leopard.
    What this means is that if I ever need to restore my contacts on my phone, none of the contacts that I created on the phone will be synced b/c they are NOT in the "phone" group, but in the All contacts category.
    If my iSync preferences are set to sync with a particular AddressBook Group, then NEW CONTACTS created in the PHONE should update to that designated GROUP, and not be considered non-categorized in the AddressBook.app.

    You must be mistaken (or very lucky!). This issue was definately around in Tiger too.
    Do a search on these forums for the same issue, and you'll see it comes up time and time again going back many years, relating to all versions of Mac OS X and iSync.
    Here's just a few:
    http://discussions.apple.com/thread.jspa?messageID=5780382
    http://discussions.apple.com/thread.jspa?messageID=4340280
    http://discussions.apple.com/thread.jspa?messageID=4615915
    http://discussions.apple.com/thread.jspa?messageID=4512731
    http://discussions.apple.com/thread.jspa?messageID=4071684
    You can even see in iSync's window that there's an option to "Put events created on phone into:" pop-up, but no equivalent option for Contacts.

  • Ongoing fatal crash and security bug related to connecting external display

    The infrastructures in OS X to resume from sleep, to authenticate, and to change displays is fundamentally not working.
    The security bug I have encountered has to do with connecting a cinema display exclusively to a MacBook Pro. This is a specific situation, but please note that I have experienced the same problem on no fewer than three independent laptop. Plus, the Genius in the Apple Retail Store was convinced of the general instability of this infrastructure. The security problem is that hot corners no longer function if I transition between two states in the same reboot. The first state is where I have the laptop powered on and using its own internal display exclusively (when I'm on the road). The second state is when I have the laptop displaying its output exclusively on an external display (when I'm at home). What happens is that an attempt to use hot corners fails. There is no response. I even added configuration on all four corners (whereas I originally had settings only for the rightmost corners), and even then, the hot corner action (of sleeping the display or entering locked screen saver mode) does not commence. This prevents the user from being able to secure the display on demand using standard methods that are supposed to work.
    The instability level related to connecting the external display exclusively is high. Again, I've experienced this on no fewer than three independent laptops, and the Apple Genius at the Retail Store confirmed that this aspect of OS X did not work consistently. When I want to connect the cinema display to the laptop in such a way that the laptop's own display is not part of the active screen, the process I use succeeds about half the time. Supposing I have been on the road, where I am using the laptop display exclusively. I then put the laptop to sleep. When I return home with the lid open, I connect first the USB (power) from the cinema display to the laptop, and then I connect the Mini DisplayPort. When that step works, what happens is that the login screen shows on the cinema display despite the fact that my laptop lid is closed. This is good, and is what I want. At that point, I open the laptop lid and quickly log in.
    With Apple being a mobile device company, I rely on the laptop for tasks that one traditionally may use a desktop for. This simply points to the versatility of the laptop. But I'd like the bugs resolved, so that I do not have to hesitate to make use of the inherent flexibility possible with the MacBook Pro.
    Here's what happens when the process (of connecting the external display in a way that establishes itself as the only screen in use by OS X) fails. Firstly, when I connect the external display via Mini DisplayPort, the laptop doesn't even respond. Instead, it remains asleep. So to work around it I have to repeatedly disconnect and reconnect the Mini DisplayPort so that the asleep MacBook Pro will see that there is a display connected to it. Also, sometimes that isn't even enough and I have to open the laptop lid, and put it to sleep again so as to trigger whatever actions are necessary to recognise the external display (presumably by having the laptop recently awake). Around half the time, I have to play this game of disconnecting and reconnecting until it actually works. This high level of reproducibility (confirmed by the Apple Genius representative's confidence that this part of the system doesn't actually work) should make it easy for an engineer to look into the problem.
    Fatally, and recently, OS X has completely crashed when I have attempted to connect the external display. The external display has gone completely blue, and after a half a minute, it blanked out and my entire laptop became unresponsive. I called Apple Support and was given a case number. I also took the laptop into the retail store to see if I could recover my current session without rebooting. There was no process suggested to make that happen and I was told to reboot the machine. I've had this happen before on other laptops, and it is frustrating that the kernel reaches such a state that it cannot be used. As I see it, this problem is not too unrelated to the way that I need to play a game in order to get the external display connected exclusively. Here are some workarounds that could be added:
    Firstly, whenever I connect an external display, I'd like the laptop to see that this has happened, and to take action accordingly (such as resuming from sleep). Secondly, If I connect an external keyboard, and press a key on it, I'd like this to wake the laptop too (in the event that the first method fails for some unforeseen reason). I'd also like the connection of the cinema display's USB power not to cause the laptop to enter into a confused state between asleep and awake. Sometimes I need to disconnect and reconnect USB power in order to trigger the laptop into waking, but that's only because it's not doing it on its own properly. On the other hand, I also ensure that the laptop doesn't have the Mini DisplayPort connected without also having the cinema display USB power connected, because that also is an unsupported configuration.
    I've also gotten the laptop to become confused about whether it is asleep or awake. When I open the lid, it seems to enter into sleep mode, but closing it seems to bring it into an active state.
    Also, I've successfully logged on and authenticated with the screen showing exclusively on the external display. But just ten seconds after I start using the system, the laptop falls asleep--with the lid open! Whatever triggers that action doesn't seem to be on track. The laptop is open, there are incoming events such as mouse movements and key presses, and the external display is on and is in use. And then the laptop falls asleep! This has happened numerous times. Not only should this not happen; the instances where it does happen can cause further instability and put my system at risk of fatally crashing.
    Also, the authentication system itself is highly buggy--far more than it should be. At times I have opened the laptop lid and caught a glimpse of a window before I have begun the login process. Also, an external authentication application that asks for Kerberos/AFS login credentials has been able to overlay itself on top of the primary authentication (whereas I should only see a single login dialog when I need to authenticate to the system). Also, I've had several of these authentication screens overlay on top of one another, although it's been months since I've experienced that one (so it may have been fixed). Also, around a third of the time, the window that authenticates me (on the black background) somehow transfers itself into the background (even though there's only one window!). What that means is what I begin to type my password, and now the laptop starts beeping at me and I need to manually click on the password field and begin entering my password again. This really shouldn't happen, and indicates too much complexity in this authentication process (such as, more OS X code is involved than is strictly necessary, which is likely to make the authentication system more difficult to test). Also, at times, I have been using too much CPU, such that the authentication screen takes too long to emerge. That also means that I'm not able to logon until I uncleanly shutdown the laptop. If the laptop has been asleep, and is revived in preparation for login, then that login screen should be given highest priority, even if there are other heavy CPU or I/O intensive tasks running in the background. And maybe the login dialog shouldn't disappear when the user is legitimately attempting to log in. So even if there is a possibility that the system is under heavy resource use (or there is a stall or minor deadlock), it shouldn't prevent the user from logging in altogether.
    At the moment, the very fact that the system shut down uncleanly means that the full disk encryption suite that I used has entered into an undetermined state, suggesting I may lose access to all my data. It's my hope that I can rely on Apple's products to interoperate in a way that won't cause me to be fearful and restrictive in my use, so that I can freely connect an external display at times, and at other times carry the laptop on the road.

    Ive got the same problem with Samsung UE225010 monitor too, its full hd but it looks terrible, could it be Displayport adapter issue, because couple month ago Ive tryed with some IPS display, and it looked same bad.

  • PSE 9 Problem Printing Multiple Photos

    I am unable to properly print multiple photos in V9. For example if I select a single photo and select my paper size as 81/2x11 and try to print 5 copies of the photo in 3 1/2 x 5 size - the preview screen only shows a single photo and it shows it will only use one page. If I print it, the photo is printed one time on 5 pages. I have included a screen shot. The same thing happens if I print multiple copies of multiple photos. I know there is an option under more options to only print one photo per page but it is not selected. Even if it was selected the preview should show that 4 pages would print. I have duplicated this on more then one computer. This is a serious bug and makes printing from PSE useless. This started after I installed a recent upgrade.

    I would like to add my experience with printing.  As per the previous comments I have also used Elements since the first version and have undergone many upgrades, so believe I am qualified to make these observations.  I have always used Elements to manage printing for our art and photographic business and have never had any issue and very little waste, very important when the paper and inks cost so much.
    It would seem that the printing from Editor works much as I would expect.
    Printing from Organiser does not work as it should.  I have always used this for printing greeting cards and other multiple print options and would expect to set for individual prints to a specific size with a number of copies per page.
    Observations of print problems:
    Only one image per image selected appears in the preview window.
    The preview window does not update to indicate multiple pages  will be printed where more than one page worth is chosen.
    Only one image is printed per page.
    Images requested print one to a page, so in my case three pages for one image 'Use each photo' set to three.
    In the 'More Options' is a tick box to select one image per page, this is not selected.
    At this stage popped up a message stating Organiser is unable to print and will skip this page.  The printer then prints 3 blank pages this being the number selected.
    I am pleased to say that returning to PSE7 to check my facts I find it does exactly what I would expect, the preview page fills up with the number of images selected to print.
    I would like to know if Adobe will be pursuing this issue as I have no use for PSE9 if it can't print as per previous versions.

  • IOS 7 iMessage bug

    I have had several problems with sending pictures via iMessage since updating to iOS 7.
    The first problem is when I am on a wifi network, and talking on the phone. iOS has essentially refused to send pictures/images over iMessage in this scenerio. This problem has been partially resolved in the iOS 7.1 update. Now, if I choose the "camera button" next to the text box from within the conversation, all goes as expected over iMessage. If I choose the picture I want to send from "Pictures" and select "send as... message" Then select the recipients name, the picture will be sent as a text message. Once I am no longer talking on the phone, iMessage will resume sending as normal from either location. Again this happens when I am connected to wifi so this is not a LTE/4G/EDGE switching issue.
    The second problem I have is that sometimes pictures will just plain not send when choosing the picture I want to send from "Pictures" and select "send as... message". When this happens it causes my phone to temporarily freeze for a few moments. Then the phone proceeds as if it had sent the message. However upon checking the conversation, it becoems clear that the message never sent or was never "added to" the conversation. This happens at random and usually restarting my phone will resolve the problem temporarily. Sending pictures seems to only consistently work when attaching them from within the conversation itself.
    It should also be noted that the "send as..." feature only breaks down with sending iMessages/text messages. "send as... email" works flawlessly every time.
    Anyway of the many numerious bugs I have encountered in iOS 7 this one is by far the most obnoxious that I have encountered. I was hoping it would be resolved in the iOS 7.1 update but it looks like maybe I set the expectation bar too high for this incrimental update.
    My hardware is an iPhone 5.
    I asked the guys at the Apple store about it and they gave me the usual propaganda induced response that they are required to give. "We never heard of that. iOS is perfect *big toothy grin* "
    I plan to try a clean install of iOS to see if it resolves the problem (not restoring from backup), but that is a time consuming process and I don't have the time for that right now.
    iOS 7 has been somewhat of a disapointemnt. I still can't wrap my head around how simply changing the look and feel of iOS would require Apples developers to break half of the features that worked flawlessly in iOS 6.

    I started having this issue about a month ago. Exactly as you described: especially when a text has an attached photo. Sometimes it is sent as a text message (green), sometimes it will fail completely. FYI, upgrading to 7.1 didn't fix the issue. Another observation is that if it is sent as a text message (without a failure), the recepient receives it but it either takes a while for them to see it, or it doesn't notify them. I had a few friends saying that they didn't even know they got the message until they intentionally went back to our thread and noticed it was sitting there for a while as green but they didn't hear it coming through. So i think on their end it's the same. it attempts to receive and when it finally does, its makes that quite sound like the one when you are actively on the screen, but not the usual tri-tone.
    Both receivers confirmed multiple times that they were home or some other place where they are certain to have at least 4G or LTE. So it has to be the bug in the system, and not my or the recepients settings.

  • SQL Developer 2.1rc1 - some bugs

    Hi!
    I'd like to report some bugs I've encountered with the RC1 version of Oracle SQL Developer (Version 2.1.0.63 build MAIN-63.41).
    - The syntax error highlighting is not very good - I've successfully executed queries almost completely underlined with pink wavy lines
    - something strange happens when I hit <Enter> while the cursor is at the end of a row that reads " union all" - a new line does not get inserted, and the cursor disappears. <Backspace> and <Enter> again, and it works ok.
    - query execution - the command I entered gets modified, stripped of comments, as far as I can tell, and if I get an error report, the line number reported is off by a couple of lines. I remember this working better in 1.5.

    I found a few bugs in the first ten minutes of use:
    - The main one was that my backspace key didn't work, no idea why this was as my keyboard is pretty standard?
    - The search/highlight window changes size when adding a new highlight, and the close button then disappears until it's re-sized
    - Editing xmldata in a window works, if it's not syntax highlighted or able to be pretty printed, but clicking ok does not change the value? Should either work or warn that it doesn't work.
    - In the query result window is 'SQL' in blue, not easy to notice that it's a button'y thing to click and see the SQL that was executed. Also, why does the little bubble with the code just float in the middle and not point to anything in particular? Surely it could point to the 'SQL' button or similar?

  • BUGS in Lightroom 1.0

    Ok, I'm already working a month of 2 with LR. So far, I like the app very much, if it was not for al those bugs!
    I encountered following things: Anybody else with these bugs?
    * sorting order; sorting on edit time instead of capture time
    * exporting photo's, LR keeps exporting the same photo (with other photo's selected) only changes after restart
    * Rejected Flags set with shortcut "x" don't stick (only when you apply them with right-click menu),grrr
    * quick Slideshow" always take the basic ugly theme, not my custom one
    * I'm sure there are plenty more ;-)
    b

    I've just discovered the same as the first point. I'm not sure what the difference is, but I have some photos taken with the same camera but imported at different times, and when it should show in order of capture time, it shows some from Dec 2006 first, then all the rest from May 2006 through to Jan 2007. I've checked the metadata and they are all correct. This is viewing with the folder selected.
    PS. With the photos all being from the same camera and using sequential numbering, if I select to sort by filename they display in the correct order.

  • Volume control sometimes gets stuck controlling the wrong volume - bug report?

    Occasionally the volume control hard buttons on my Pre go wonky and "stick" to controlling an application as opposed to what they are supposed to. For example, I'll use the music player, and it will function fine and show the musical note when adjusting the volume. Then I'll toss away the music player app, but the volume will "stick" with the musical note and not control the system and ringer sound volumes.
    This feels like a bug, but I might be missing something. Thanks!
    Post relates to: Pre p100eww (Sprint)

    Don't think your missing anything. Its a bug, I have encountered a few times. Seems like most the time, it has happened to me if I immediately try to change the volume after tossing a card away such as music player, or video. But have had it happen a few times without any explanation. Restarting it fixes it, and luckily it does not happen that often for me. Just wanted to chime in to say its not just you though.

  • Weird hissing bug in Premiere Pro CS6

    I'm having a very strange problem with audio in Adobe Premiere Pro CS6.
    Whenever I make a cut in an audio clip, a few seconds of broadband hiss is introduced into it after the cut. The hiss is only there in the exported video. It does not appear after every cut but about 10% of them.
    The hiss is equally there when I export into different video/audio formats. It is there when I used different editing codecs. It might only be there for clips I recorded using some not so good microphones on a Canon 5D II, but the hiss only shows up after I make an audio edit and export the video/audio or just the audio. Sometimes though it shows up right away in PP before export. If I clean up the hiss in Audition for a given clip I no longer hear it in PP but again it reappears after export.
    It seems like the problem shows up when editing video shot on a Canon 5D MII with the in camera mic or several shotgun mics, but not with a decent lavalier mic. Changing the edit and export codecs doesn't help the problem.
    (i7 960 3.3 GHz, Win 7 sp1 12GB, Nvidia GeForce GTX 470 1280MB, PP 6.02)

    I have not encountered the "hissing bug"
    But have encountered something similar to what you describe - but with differences.
    When Audio is Cut at a point, that is not a Zero-Crossing, depending on the point on the Waveform, that the Cut was made, there can be a "pop," at that spot. Adobe Audition has the ability to set Cut at Zero-Crossing, but I do not think that PrPro has that capability.
    Now, all of my encounters with a non-Zero-Crossing Cut has been the formation of a Transient, which does sound just like a pop (not a hiss) sound. I have never heard a hiss, and I do not think that what you are hearing, is what I am, with non-Zero-Crossing Cuts - they just happen to appear AT an Audio Cut.
    Still, you might want to look at the Waveform very closely, just to rule out non-Zero-Crossing Cuts, in case that IS causing what you observe, but just producing a different sound, due to the difference in your Audio material.
    Also, have you done a side-by-side comparison in Audition between one of the files with the hiss, and the original sourse file? What differences do you see, where the Cut was made, if so?
    Wish that I had more to offer than a slightly similar problem, with a different sound.
    Good luck,
    Hunt

  • Recreatable Bug in Audition 3

    Hello all, I believe I have found a re-createable bug in AA3 and here is how you can create it.
    Load up a session, and on one of the tracks select all the clips.
    Now, right click a clip and select "clip envelopes > pan > use splines".  So now you have set the clip pan envelopes (NOT the volume envelopes but the PAN envelopes) to use splines.
    Now play back your Multitrack session and within the clips you have set to use splines, keep creating new enveloping points and adjust these envelope points just before the cursor while the cursor is playing and moving toward the envelope points...adjust envelopes just before the cursor gets there and eventually Audition will stop functioning and you will get the message
    "Microsoft Visual C++ Runtime Library
    (X) Runtime Error!
    C:\ProgramFiles\Adobe\AdobeAudition 3.0\Audition.exe
    R6025 Pure Virtual Function Call"
    It also happens (although not nearly as often) when I'm adjusting the "pan splines" whilst Audition is not playing the session, and is completely stopped.
    This is the first real "bug" I have encountered, has anyone else had the same experience or are you able to re-create it?  You have to play with the splines from anywhere from 10 seconds to a minute and eventually with repeated changes in the pan and the addition of more envelope points it will crash.
    Just wondering if anyone else has experienced this, or if you can re-create it in 3.0.1, which I have yet to upgrade to because my friend did and he has now encountered bugs that were not in the original 3.0, can anyone confirm this bug and/or whether it's been fixed in 3.0.1?
    My system has been so stable otherwise I don't want to touch it, even with this re-createable bug, after it crashed if I "control+s" and save the results, it doesn't save the session permanently, but when I choose "continue session" in the post-crash dialog box, it returns my clips with the spline envelopes set just as they were just prior to the crash.

    Mark Branch wrote:
    Could you possibly direct me to a list of what 3.0.1 corrects?
    I can do slightly better than that - I'll post it here:
    Changes in Adobe Audition 3.0.1:
    • Spectral tools no longer crash machines with more than four CPU  cores.
    • The Graphic Phase Shifter effect has been reenabled.
    • Performance while recording MIDI data has been improved.
    • The Sequencer will now record MIDI data even if the panel is  closed.
    • Adobe Audition will now launch on Windows Vista® systems where the  My Documents folder was moved from the default location.
    • The application will now ignore Windows "Locale" settings to  format decimal data in comma-delimited XML settings files.
    • A Healing Brush crash issue has been addressed.
    • Crossfades are no longer incorrectly added to grouped clips when  overlapped with non-grouped clips.
    • Invalid crossfades will no longer be added to the end of a  previously trimmed clip after enabling or disabling looping.
    • Invalid crossfades for clips after enabling non-session  tempo-based looping have been addressed.
    • Dragging crossfaded clips onto the master track no longer creates  two additional tracks and an error in the crossfades. 
    • Inserting MIDI from the Files panel would cause the application to  hang in Edit mode for an audio file whose sample rate didn't match the  session.
    • Several scenarios where crossfade changes could corrupt a session  were addressed.
    • Closing a session without exiting the rewire app no longer causes  Adobe Audition to save a blank session.
    • Undo no longer becomes disabled after undoing the creation of  unique copies of two crossfaded clips.
    • Crossfaded clips no longer disappear after undoing move clips.
    • Canceling VST scan no longer causes Adobe Audition to become  unstable.
    • If a selection existed, a full session mixdown would only process  MIDI data through the end of the selection.
    • The Open MIDI dialog box was not completely modal and could cause a  crash.
    • MIDI Host had problems with some Spectrasonics VSTi instruments,  where it wouldn't show the entire UI.
    • CD burning would sometimes create a corrupted disk but still  report a successful burn.
    • Applying the Clip/Pop Eliminator no longer crashes the  application.
    • Crash recovery is now more reliable when using Auto-Save For  Recovery.
    • When the application detects the possible saving failure that  causes a corrupted session, a warning dialog box now appears so users  can retry the save.
    • Transport controls are no longer disabled if a new session is  opened without closing the existing session.
    • Crossfades will now retain their original shape when clips are  moved and the session is reopened.
    Please note the one I bolded, and the one underneath. I also strongly suspect that this is only the list of tangible things - there have been quite a few changes 'under the hood' to make all this possible, and this has definitely been more stable than the original version - I had healing brush crashes before, and not a single one since. I'm not aware of a single report from anybody that this bugfix release has made anything worse or more unstable at all, and most reports of crashes have more to do with people's unstable OS installs than anything else, and they certainly don't relate to the bugfix, whatever you may have heard.

  • AI CS3 Bug List

    All the problems with Adobe Illustrator CS3 are constantly frustrating me and make my job a lot more difficult. Why is CS2 is a lot better than CS3?
    Maybe some one can help me to fix all these bugs that I have encountered:
    1) Preview does not work.
    I cannot understand why AI CS2 can display Preview before you open a document, but is impossible to do it using CS3. I think is a waste of time using a second program just to view a document file. Using Bridge is just a waste of time because display lot of information that you do not need and the view options are so limited.
    2) Strokes display incorrectly.
    Any stroke under .12 pt is display uneven which makes working with the pen tool frustrating.
    3) Pantone Pallette Window.
    This window still represents a problem even when you select Persistent option, due to the fact that when you select a PMS color, the selection jumps to the bottom of the list. So you have scroll back up to select the next PMS color.
    4) Mesh Tool
    The mesh tool works Ok as long as you do not re-size the artwork. If you re-size the artwork everything is distorted. In other words, your work is useless and you just wasted time. I have to use CS2 to solve the problem. That is right, you have to use the OLD version that works better than the new version.
    5) Outline Stroke.
    If you convert a path into outline, you end up with excessive extra anchor points. Yes, you can reduce the amount of the anchor points by using the Add to Shape Area option on Pathfinder feature. But still is not as good as CS2, and can cost delays on your work.
    6) Tiff files
    CS3 crashes every time you open or place a tiff file. CS2 did not have this problem.
    7) Text Editing
    Every time you have a text with indicator ending on the next line without text, it displays the indicator on the second to the last line. This can cost costly mistakes when you are editing text, spacing, etc.
    8) Selecting text
    If you editing different text sentences, you have to be careful that the programs actually takes the text that you are selecting with the text tool. Some times it takes double click for the program to understand that you are not working with the previous sentence. And sometimes you have to select the Black arrow to click on the text you want to edit and then select the text tool to make the editing. This problem is very annoying.
    The main complaint is that I use these tools every day and with almost every project. So I am constantly reminded that CS2 is way better than the NEW version CS3 and there is not a word from Adobe if they are working on a patch or revised version to fix these very annoying bugs (that I have to deal with them every day). So if someone have a good solution for these bugs please let me know. Feel free to add bugs you have encountered with CS3. May be Adobe can have one good list of everything that is wrong with this very disappointed version. Thank you!

    Kev. Actually the addition of shift in that key combo is what constrains the movement of the duplicated object. So, for example, when I perform the operation I may wish to drag the dupe to the right of the original. The shift keeps it at the exact same "latitude". It is a combo I have used for as long as I have been using AI.
    Aside from that I am happy to report that upon quitting all apps and rebooting, the problem disappeared. This embarrasses me somewhat as what I did is a fairly basic thing to try when troubleshooting. It must have been something in the system or memory which was out of whack and righted itself upon startup. Sorry to have wasted space in this forum.
    On the other hand, it was a glitch which somewhere, somehow manifested. If it happens to somebody else maybe they'll read this and it will halt the panic.
    I am glad I found this little site so I can keep myself better informed as to other possible issues.

  • PSE 8 - Unstable behavior

    Hi!
    I try trial vesion and have some questions:
    1. After start catalogue system crash with message (by my memory):
    "CAHeadless .....  init.cpp -42"
    2. I live in Ukraine, and our storage can't avalable version 7 and 8 where I can buy it from online storage by my visa card?
    PS. PSE 6 is very stable...
    Best regards,
         Ivanoff Alex

    It's very unlikely that Adobe will issue an update that fixes bugs in PSE 8 -- they rarely do that.  Usually we have to wait until the next version comes out (and pay the full price) to get the bug fixes.
    Regarding purchasing PSE 8, you can't buy it directly from Adobe.com?

Maybe you are looking for