Problem with Aperture 3.6 preset exports.

I use an export preset that exports at 225dpi. If I export an image with this preset and subsequently import it into Photoshop, the resolution in PS is only 72dpi. When I open the image using Preview and look under Inspector, I notice that the JFIF data shows X and Y density as 72. This has happened since Ver 3.6.
Images exported with a previous version of Aperture show JFIF X, Y density at 225 (the export preset value) and open in PS with 225 dpi.
I know that I can adjust the resolution in PS but this is an inconvenience I never had until Ver 3.6. Why has this behaviour changed with Ver 3.6? Is this a bug that can / will be fixed before Aperture closes down for good?

Frank,
My export preset limits the dimensions in pixels at a specific dpi, corresponding with an image size in inches. I do this for some images I wish to send to external printing shops to print. I might add text using Photoshop. All worked well before with the set dpi and resulting dimensions in inches. Now, Photoshop resizes the image at 72 dpi giving much larger measurements in inches. As I've said before, this is not a big deal and I can resample under Photoshop back to my dpi of 225. But it is an extra step which I didn't need before 3.6 was released. Also, I do wonder why Aperture allows the dpi to be set to whatever the user wants only to ignore it during the actual export.
I reckon that Photoshop (and perhaps other software as well), picks up the dpi from the JFIF information for jpeg files. So if a user wishes PS to use a specific dpi, it is a bit frustrating that Aperture only "allows" 72 dpi with this latest version.
I have found that this only applies to jpeg exports where Aperture 3.6 mashes up the dpi. An export from Aperture in TIFF formats using a particular dpi sticks. Photoshop will retain that dpi when it opens the file.
I have submitted a report to Aperture. I hope they look at it and consider doing something to rectify the matter. Thanks for your comments.

Similar Messages

  • Some problems with aperture 3

    I have some problems with aperture 3...
    //1
    I updated my library with aperture 3, and export some projects for make another one, everything works fine, I can switch the library very quickly...but when I want change my background in snow leopard, the first library ( current default ) don´t show anything, seems like don´t load well, the "aperture" shows right but without arrow for open the hierarchy, and if I switch the library ( the second one ) the background can load this library without problems, works with all folders, projects...
    I repaired the permissions, database and rebuild database but nothing happens.
    //2
    The second problem I think is the same. In Mail, iWork, iLife...the Media Browser don´t load my main library, only the second one, I have the last update installed, and the second library works fine, why not the first?
    //3
    I imported some projects from the one library to the other, for adjust my pipeline and make much easy my workflow, but if I import, for example, 2 folders with 4 projects, aperture import in my library 4 folders and 8 projects, the imported files are duplicated O_O
    I see the same stuff inside the folders, and when I delete one of them, the aperture delete the 2 "versions", but in the trash I see only one of them xD and if I put back the folder/project, again I see 2 versions xD
    I "fixed" creating new folders/projects and moving the photos manually...( with some crush in the process ) any idea about this problem?
    //4
    This problem is more as a enhancement...what happen if I want to sync different projects from my 2 libraries in my iPhone?? because iTunes only show me the last loaded library
    Regards,
    Jonatan

    many thanks for the answer
    not being very computer literate i will try and answer your question
    1st i tried to download a "fix" from apple support for Aperture3 but after changing the file name to Aperture.app
    as suggested by someone on forum I got the answer
    The version of Aperture installed on this Mac must be updated through the Mac App Store. Check the Mac App Store to see if an update is available.
    by aperture is 3.2.2
    2nd in answer to your question,
    memory 2gb 667  Mhz DDR2 SDRAM
    I have 128.53 gb free out of 319.21 gb
    hope that helps

  • Problem with Aperture 3.6 Can't open Preferences

    I had a problem with Aperture 3.6; opened a new Library from the Vault, now cannot open Aperture Preferences. When I attempt to open preferences I get a very thin vertical line about 1 ½ inches long?? Any fixes for this/  Thanks, Vic

    Try to delete the Aperture preferences as described here at this link:
    Get help with Aperture 3 - Apple Support
    Steps to reset preference settings
    To reset your Aperture user preference settings to their original state, do the following:
    Quit Aperture.
    In the Finder choose "Go to folder" from the Go menu.
    Type ~/Library/Preferences in the "Go to the folder" field. Press the Go button.
    Remove the "com.apple.Aperture.plist" file from the Preferences folder.
    Restart your computer if you're using OS X Mavericks.
    The locations of your Aperture libraries are stored in the preference file listed above. If you have stored your library outside the default location of  ~/Pictures/Aperture Library, make a note of where the library is before deleting the Aperture preferences file. If you have more than one library, you can bring up a dialog to choose which one to load by pressing Option immediately after you open Aperture.

  • I still am having problems with Aperture not loading,  It just refuses to work, and I get the message saying it has encountered a problem, and I may need to re-install which I have done dozens of times. The fix mentioned on an earlier post wont work as it

    I still am having problems with Aperture not loading,  It just refuses to work, and I get the message saying it has encountered a problem, and I may need to re-install which I have done dozens of times. The fix mentioned on an earlier post doesn't work as it is for Ver 10.6.6 and I am running 10.6.7

    Do you have Final Cut installed on your machine?
    If so, you may want to look at this article: http://support.apple.com/kb/TS3528
    Let us know if that helps.

  • Problem with number-fields in csv-Export-Files

    Hello,
    the export with the csv option works fine and our users like this export-function.
    But Unfortunatelly we have some problems with the exported number fields. In my region I defined the field with a format mask.
    On the screen it looks fine but when I change to csv the values are exported as text-values.
    So in excel the columns are shown with left alignment.
    When I try to change the format in excel to number, excel change the column type but not the value inside.
    On this account we cannot use the sum-function and the display of the value is wrong (alignment).
    Which possibilities do I have to resolve that problem?
    Thanks in advance
    Ulrike

    I have the same issue - Anyone any ideas on how to export currency values in a report to excel as numbers?

  • Problems with QCM tables in DB export

    Hi gurus, I have a problem with an export that I'm performing, the problem is that the R3SETUP is trying to export a QCM table "QCMT066" but this table doesn't exits in the database.
    (EXP) ERROR: DbSlExeRead: rc = 107, table "QCMT066"
            (SQL error 942)
    error message returned by DbSl:
    ORA-00942: table or view does not exist
    The R3 system is a 4.6C and runs over HP-UX 11 64 bits and Oracle 8.1.7
    I read and search SAP notes and inside the SAP forums, but I didn't find anything that could help me.
    The transaction SM13 says that --> **** No update records found ****     when I execute without client, user and date parameters.
    The transaction SE11 says that the table in fact doesn't exits in the database, and if I execute a select sentence (SELECT TABLE_NAME FROM DBA_TABLES WHERE TABLE_NAME LIKE 'QCM%') I can see that there is no table with this name.
    In transaction.
    The transaction SE14 > Extras> Invalid temp. table  show the text " ... List is empty "
    So please, Do you know what I could do to solve my problem?.
    Thanks and best regards
    Edited by: Juan Francisco Estrada Garcia on Sep 3, 2010 11:02 AM

    Thank you, that is just what I did.
    I found this [tread|r3load export error ORA-00942 for table QCMBTXBLOK; where the people talk about .TKS files, but the version that I'm trying to migrate is too old, and the R3LOAD doesn't use TKS files, so I edited every file(.EXT, .STR, .TOC)  that contains references to QCM* tables. I deleted every line related with this kind of tables, and finally everything work and the export ended successfully.
    Thanks

  • Problems with certain text appearing once exported as HTML on my third party hosting site

    Hello,
    I am experiencing problems with how certain text is appearing on my website www.pplmedia.com/speakers.
    Most of the text is appearing how I want it to once I have exported it out of Muse, but for a reason I can not rectify, certain text is coming out as plain Arial Black text, in a bigger font and the text boxes move slightly. If you go onto the page  www.pplmedia.com/jock-wishart  you will see what I mean.
    I have taken the text out of Muse, put it into the program 'TextEdit', I changed the text from rich to plain, put the text back into Muse and the problem still remains.
    I have also published the site as a trial in BC and the text is how it should be, so I assume this is an issue with third party hosting I am using?
    If someone can get back to me to offer any help or suggestions that would be greatly appreciated.
    Regards
    Oliver

    You are awesome!!! Thanks so much! I have talked to a ton of people this
    week, and no one could figure this out. I read your email to the technical
    support person at our 3rd Party Host, and she fixed some files that were not
    in the correct spot and changed some of the permissions settings. I am up
    and running. Thanks for making my Friday!
    Re: Adobe Muse Site will not preview properly on Third Party Hosting
    Site...Help!
    created by adobelance <http://forums.adobe.com/people/adobelance>  in Help
    with using Adobe Muse - View the full discussion
    <http://forums.adobe.com/message/5227992#5227992>
    What's the URL for your uploaded site?
    Please note that the Adobe Forums do not accept email attachments. If you
    want to embed a screen image in your message please visit the thread in the
    forum to embed the image at http://forums.adobe.com/message/5227992#5227992
    Replies to this message go to everyone subscribed to this thread, not
    directly to the person who posted the message. To post a reply, either reply
    to this email or visit the message page:
    http://forums.adobe.com/message/5227992#5227992 To unsubscribe from this
    thread, please visit the message page at
    http://forums.adobe.com/message/5227992#5227992. In the Actions box on the
    right, click the Stop Email Notifications link. Start a new discussion in
    Help with using Adobe Muse by email
    <mailto:[email protected].ad
    obe.com>  or at Adobe Community
    <http://forums.adobe.com/choose-container!input.jspa?contentType=1&container
    Type=14&container=4761>  For more information about maintaining your forum
    email notifications please go to
    http://forums.adobe.com/message/2936746#2936746.

  • Pentax K-x RAW color shift problem with Aperture 3

    I have seen a few posts similar to what my problem is but not exactly.I have two Pentax K-200D's and a new Pentax K-x. I shoot RAW with all of them and the K-200D's work great. The RAW files however from the K-x are doing something strange. Sometimes (more and more though) the files are being imported into Aperture and there is a radical color shift after they finish loading. ALL of the preview thumbnails look fine in the camera and the Aperture import window. However, after importing them and processing is complete, some of the shots have a magenta color shift, but most that have this problem shift radically to a green tint. Everybody looks like they are in "The Matrix."
    I do not have any brightness correction on the camera turned on as other posts imply might be the problem. I have also remove the Aperture RAW 3.2 and tried 3.0 and 3.1 with no solution. 3.0 doesn't recognize the files at all and 3.1 does the same thing as 3.2. Here are two examples of UNEDITED RAW files:
    Frame that looks fine in RAW
    http://gallery.me.com/mattcline#100470/IMGP5982&bgcolor=black
    The next frame taken with the same settings on the camera:
    http://gallery.me.com/mattcline#100470/IMGP5983&bgcolor=black
    I do have one possible pattern. I had the camera set on rapid fire capture. It appears to me that the first frame I take when the shutter button is depressed looks and translates fine. All the subsequent frames take in rapid fire under the same shutter release have the green shift when taking shots in relative shade. Things taken in bright sunlight have the magenta shift.
    Any ideas on what is going on or how to fix this?
    Thanks.

    kb8wfh wrote:
    I just downloaded Apple's RAW 3.3 and it still made no difference.
    Going back over the files, I found that going back and forth between the two, see no difference in the RAW processing headings. I did see however that in the meta data that the two pictures I have in the example of those listed above have one difference. There is a setting on the Exposure Bias for the one that was fine was -0.3 ev and the one that has the green contrast blast has an Exposure Bias of 0.3 ev. So the one that looks right is slightly negative. Doesn't seem like that should be a big difference, but apparently it is.
    I did take some pictures with the RAW+JPG setting and I had the same problem with the RAW files. Some were ok, some were green, others were magenta shifted. However, all the JPG files looked just fine.
    Switching from Aperture isn;t really an option for me. I have been using it for a long time and it generally works very well...perfectly with my K-200D's. It's just some bug with the RAW decoder for the K-x.
    It's a known bug and I have been in touch with Apple staff over it, including engineers. It's not just the K-x. Other brands (Canon) and models suffer from the RAW processor gone wrong.
    Right now there is no fix. At the pace Apple works at, there may not be one for quite some time. Use JPEG, use iPhoto, or move to Lightroom.
    Another suggestion is to phone customer service and complain that their "Pro" program is not working as expected. I spent hours with an engineer going over the issue including a screen share session, only to be told to use JPEG.
    This was 4 months ago.

  • Printing problems with Aperture

    I just switched from Windows (long story, many years) to an Intel iMac 20, with Aperture pre-installed. I had a Canon PIXMA iP 6000D printer; all prints had a yellow cast. I bought an HP Photosmart 7160; all prints have a yellow cast. I have done a format and re-install of OS X and all software. I have installed my Aperture software on another iMac 20 at the store; with my printer and the store's printer the prints had a yellow cast. I took my computer to the store and printed on their printer; all prints had a yellow cast. I get the same results printing from Photoshop CS2 for Mac or from Preview. I have tried several USB cables. My monitor is calibrated with a SpyderPro 2. Prints directly from a memory chip in the printer are fine. I've tried all the adustments in the print setup; no help. I'm working on the sliders now, but with seven sliders with 100 possible settings on each I think that's seven to the 100th power possible settings. Both printers work fine with my Windows computers.
    I've exhausted all the available Apple support. Anyone have any ideas?
    Arthur
    iMac 20   Mac OS X (10.4.8)  
    iMac 20   Mac OS X (10.4.8)  

    Well, to reiterate, I am using the HP printer as there is only room for one printer on my desktop. I am using HP paper, the "Advanced" type which is bar coded so that the printer recognizes the paper type and sets the appropriate defaults. I have also tried other HP papers, and selected them from the printer dialog. I have tried setting the paper type manually with the "Advanced" paper. I have tried printing with all the defaults left alone.
    When I said that I had tried every print option in the printer dialog sequence, I meant that in the printer dialog I had tried each of the paper types, each of the color options, each option under HP Colorsmart, several types of HP printer paper with the proper option selected. Under ColorSync, there are only two options here. One is "Standard" and the other is "in Printer" which is greyed out.
    Go down the print dialog. I have tried every option. Under "Paper Type, Quality" I have tried every option for paper type, quality, and color. I have done this systematically, using all available combinations.
    I don't know how else to describe the process Apple and I have tried to use to try to repair my problem. Name an option--I have printed using it.
    I tried the "sliders" as a possible way of altering the output from the computer to the printer, as I had exhausted all other possibilities, and if I could find the magic combination I could set it as the default and all my prints would be
    affected by those settings and print correctly. They appear in the printer dialog from Aperture. My photos print correctly if I copy the file to a Compact Flash chip and place it into the printer slot and print directly.
    Pardon me if I seemed snappish. I bought the iMac specifically for photographic work, have had it for a couple of months, have made several hundred prints, have exhausted support from Apple, and am grasping at straws. I have 8 GB of photos from my last trip which remain unprinted. Shortly before the trip I did two wedding shoots which were quite successful, printed from Photoshop CS2 under Windows. All my current photos print acceptably on this printer from my Windows computer. They are not acceptable printed from Adobe CS2 for Mac.
    Can I be more specific in what I have tried? Do you have a suggestion for something for me to try? Apple and I are grasping at straws, and would appreciate any help you can give.
    Arthur

  • Problem with Materialized Views after an export

    Hi @ everybody,
    At an Oracle 11g R2 (11.2.0.3.0) instance, all actual CPU's/SPU's are installed, on a Red Hat 6 Machine i have a problem with Materialized Views from a schema, which i have exportet from an old database machine on Oracle 10g (10.2.0.1.0) to the new machine.
    I've exportet with the old exp and imported with imp, because i know, that i get some strange errors because of the materialized views when i'm using the new expdp and impdp tools.
    At the old machine the materialized views are so programmed, that they get an update of data at a defined time like this:
    START WITH TRUNC(SYSDATE) + 21/24
          NEXT SYSDATE+1
    ...But after the export this "update function" of the materialized view is not available. So i have deleted that views and recreated them with the START WITH parameters. So now they are running.
    But why do i have this problem?
    Is this "START WITH" somewhere written as a job or so in, for example, DBMS_SCHEDULER or something else? So i had forgotten to export these jobs or where is that defined?
    Is this a bug?
    Thanks for answers and help!
    Best regards,
    David

    I can't remember the error of expdp/impdp. That is some days ago, i have to rebuild this.
    I think in my scenario for the import i don't need the TABLE_EXISTS_ACTION, because by importing at the new server i've just createt the naked tablespace for the data and the users, not more. So he didn't has something to overwrite.
    And i have to tell you: i'm just the dbA. The desining of the tables and materialized views is many years ago by installing the old server. I'm just to young in my company to know about the design of the instance and why it was designed so.
    Anyway: my problem is, that after the import of the schemas to a new server the "START WITH" option in the materialized views is not there anymore and i just want to why so i can think about a solution for that and create it with the database designers of my company.
    EDIT: And here are the SQL Statements for creating the Materialized Views:
    First, at the OLD Server (Oracle 10g 10.2.0.1.0)
      CREATE MATERIALIZED VIEW "DUPONT_CCG2_P"."PR_PRODUCT_ITEMS"
      ORGANIZATION HEAP PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
      STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
      PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
      TABLESPACE "DUPONT_14523"
      BUILD IMMEDIATE
      USING INDEX
      REFRESH COMPLETE ON DEMAND START WITH sysdate+0 NEXT SYSDATE+1
      USING DEFAULT LOCAL ROLLBACK SEGMENT
      DISABLE QUERY REWRITE
      AS (SELECT DISTINCT
          PR_CUSTOMER_MASTER_DATA.CLIENT_ID,
          PR_CUSTOMER_MASTER_DATA.ILN_USER,
          PR_ARTICLE.EAN,
          PR_ARTICLE.CODE,
          PR_USED_ARTICLE_TEXT.ARTICLE_TEXT,
          PR_USED_ARTICLE_TEXT.LANG_CODE,
          PR_ARTICLE.SUP_ITEM_NO,
          PR_ARTICLE.OLD_ITEM_NO,
          PR_COMPANY_ITEM_MATCH.ITEM_BY_NO,
          PR_COMPANY_ITEM_MATCH.UOM_UNIT,
          PR_COMPANY_ITEM_MATCH.PRICE_UOM,
          PR_COMPANY_ITEM_MATCH.PRICE,
          PR_COMPANY_ITEM_MATCH.CURRENCY,
          PR_COMPANY_ITEM_MATCH.PRICE_QTY,
          PR_COMPANY_ITEM_MATCH.SALES_UNIT,
          PR_COMPANY_ITEM_MATCH.START_DATE,
          PR_COMPANY_ITEM_MATCH.END_DATE,
          PR_ARTICLE.UPDATED_AT
            FROM PR_ARTICLE, PR_COMPANY_ITEM_MATCH, PR_USED_ARTICLE_TEXT, PR_CUSTOMER_MASTER_DATA, PR_ADDRESS
            WHERE PR_ADDRESS.ORDER_TYPE='REP'
          AND PR_CUSTOMER_MASTER_DATA.ILN_USER=PR_ADDRESS.ILN_USER
          AND PR_COMPANY_ITEM_MATCH.ILN_USER=PR_ADDRESS.ILN_LINK
          AND PR_CUSTOMER_MASTER_DATA.SALES_ORG=PR_COMPANY_ITEM_MATCH.SALES_ORG
          AND PR_CUSTOMER_MASTER_DATA.CLIENT_ID=PR_COMPANY_ITEM_MATCH.CLIENT_ID
          AND PR_CUSTOMER_MASTER_DATA.CLIENT_ID=PR_ADDRESS.CLIENT_ID
          AND PR_ARTICLE.SUP_ITEM_NO=PR_COMPANY_ITEM_MATCH.SUP_ITEM_NO
          AND PR_COMPANY_ITEM_MATCH.SALES_ORG=PR_USED_ARTICLE_TEXT.SALES_ORG
          AND PR_ARTICLE.SUP_ITEM_NO=PR_USED_ARTICLE_TEXT.SUP_ITEM_NO
          AND PR_CUSTOMER_MASTER_DATA.LANG_CODE=PR_USED_ARTICLE_TEXT.LANG_CODE
          AND ( PR_COMPANY_ITEM_MATCH.END_DATE IS NULL OR to_date(PR_COMPANY_ITEM_MATCH.END_DATE,'YYYYMMDD') - sysdate > 0)
          AND ( PR_COMPANY_ITEM_MATCH.START_DATE IS NULL OR sysdate - to_date(PR_COMPANY_ITEM_MATCH.START_DATE,'YYYYMMDD') > 0)
    )And here the at the NEW Server (Oracle 11g R2 11.2.0.3.0)
      CREATE MATERIALIZED VIEW "DUPONT_CCG2_P"."PR_PRODUCT_ITEMS" ("CLIENT_ID", "ILN_USER", "EAN", "CODE", "ARTICLE_TEXT", "LANG_CODE", "LANR", "OLD_LANR", "ITEM_BY_NO", "UOM_UNIT", "PRICE_UOM", "PRICE", "CURRENCY", "PRICE_QTY", "SALES_UNIT", "START_DATE", "END_DATE", "UPDATED_AT")
      ORGANIZATION HEAP PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
    NOCOMPRESS LOGGING
      STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
      PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
      BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
      TABLESPACE "DUPONT_14523"
      BUILD IMMEDIATE
      USING INDEX
      REFRESH COMPLETE ON DEMAND START WITH sysdate+0 NEXT SYSDATE+1
      USING DEFAULT LOCAL ROLLBACK SEGMENT
      USING ENFORCED CONSTRAINTS DISABLE QUERY REWRITE
      AS (SELECT DISTINCT
          PR_CUSTOMER_MASTER_DATA.CLIENT_ID,
          PR_CUSTOMER_MASTER_DATA.ILN_USER,
          PR_ARTICLE.EAN,
          PR_ARTICLE.CODE,
          PR_USED_ARTICLE_TEXT.ARTICLE_TEXT,
          PR_USED_ARTICLE_TEXT.LANG_CODE,
          PR_ARTICLE.SUP_ITEM_NO,
          PR_ARTICLE.OLD_ITEM_NO,
          PR_COMPANY_ITEM_MATCH.ITEM_BY_NO,
          PR_COMPANY_ITEM_MATCH.UOM_UNIT,
          PR_COMPANY_ITEM_MATCH.PRICE_UOM,
          PR_COMPANY_ITEM_MATCH.PRICE,
          PR_COMPANY_ITEM_MATCH.CURRENCY,
          PR_COMPANY_ITEM_MATCH.PRICE_QTY,
          PR_COMPANY_ITEM_MATCH.SALES_UNIT,
          PR_COMPANY_ITEM_MATCH.START_DATE,
          PR_COMPANY_ITEM_MATCH.END_DATE,
          PR_ARTICLE.UPDATED_AT
            FROM PR_ARTICLE, PR_COMPANY_ITEM_MATCH, PR_USED_ARTICLE_TEXT, PR_CUSTOMER_MASTER_DATA, PR_ADDRESS
            WHERE PR_ADDRESS.ORDER_TYPE='REP'
          AND PR_CUSTOMER_MASTER_DATA.ILN_USER=PR_ADDRESS.ILN_USER
          AND PR_COMPANY_ITEM_MATCH.ILN_USER=PR_ADDRESS.ILN_LINK
          AND PR_CUSTOMER_MASTER_DATA.SALES_ORG=PR_COMPANY_ITEM_MATCH.SALES_ORG
          AND PR_CUSTOMER_MASTER_DATA.CLIENT_ID=PR_COMPANY_ITEM_MATCH.CLIENT_ID
          AND PR_CUSTOMER_MASTER_DATA.CLIENT_ID=PR_ADDRESS.CLIENT_ID
          AND PR_ARTICLE.SUP_ITEM_NO=PR_COMPANY_ITEM_MATCH.SUP_ITEM_NO
          AND PR_COMPANY_ITEM_MATCH.SALES_ORG=PR_USED_ARTICLE_TEXT.SALES_ORG
          AND PR_ARTICLE.SUP_ITEM_NO=PR_USED_ARTICLE_TEXT.SUP_ITEM_NO
          AND PR_CUSTOMER_MASTER_DATA.LANG_CODE=PR_USED_ARTICLE_TEXT.LANG_CODE
          AND ( PR_COMPANY_ITEM_MATCH.END_DATE IS NULL OR to_date(PR_COMPANY_ITEM_MATCH.END_DATE,'YYYYMMDD') - sysdate > 0)
          AND ( PR_COMPANY_ITEM_MATCH.START_DATE IS NULL OR sysdate - to_date(PR_COMPANY_ITEM_MATCH.START_DATE,'YYYYMMDD') > 0)
    )The own differences i can see is at the "header". In the new one is the NOCOMPRESS LOGGING Option and in the first line the code has the columns diretcly defined.
    But, i think, for my problem this line is determining:
      REFRESH COMPLETE ON DEMAND START WITH sysdate+0 NEXT SYSDATE+1And this line is the same at both server.
    Edited by: David_Pasternak on 12.04.2013 00:06

  • Problem with Aperture 2 and Digital Camera Raw Compatability update 3.1

    Has anyone using Aperture 2 experienced problems with the Digital Camera Raw Compatability update 3.1. It may be purely coincidence but, since downloading this on March 3, I get the dreaded red screen and unsupported image format on my previously downloaded and edited RAW photos. I use a Pentax k-7 with which, once set up, I have had no problems until now!
    Please - any help would be very gratefully received

    That probably explains why any checks that your computer did to see if the Camera Raw update was okay to apply didn't stop it. You should probably contact Apple and explain that they broke something that was working fine previously.
    A few people have reported backing off Camera Raw 3.1 and going back to Camera Raw 3.0 for now. This note is one of the ones I've found describing how to do that, if you wish to try that. Or, you could head down the path Apple means to lead you on and upgrade to Aperture 3.
    Message was edited by: Ailish Eklof

  • Is anyone else having problems with Apertures Date fields?

    After experiencing a sysems failure I began restoring my images from backups.  I have had no end of problems with Image dates.  I have come to the determination that Aperture is NOT using either the "Create Date" or "DateTimeOriginal" as the image "Date" or "Date Created" data if other fields have other dates.
    Here is a clip from my image metadata using exiftool:
    File Modification Date/Time     : 2012:09:23 19:53:15-04:00
    File Access Date/Time           : 2013:01:16 11:34:38-05:00
    File Inode Change Date/Time     : 2013:01:16 11:31:32-05:00
    Create Date                          : 2006:02:20 11:51:12.10
    Date/Time Original              : 2006:02:20 16:51:12.10
    Modify Date                          : 2006:02:20 11:51:12.10
    And here is what Aperture utilized on import
    Date:                               9/23/12 7:53:15 PM EDT
    Date Created                         9/23/2012 7:53:15 PM
    So Aperture utlized the File Modification Date/Time as the Create Date despite that the fact that the Create Date field is present and is properly formatted in the original image.
    According to the Aperture mapping table, this shouldn't be happening.
    Now, before someone recommends that I use Aperture's Date Adjust utility - I'm talking about  slightly over 30,000 images.  Editing images one at a time, or in blocks when you don't know what field Aperture is using as the Create Date would require individual inspection of each image followed by manual adjustment of each image.  That approach isn't acceptable.

    Hmm ok, let me restate the issue then, I thought I was clear.  I could have pointed out in my original post however, that only the EXIF and IPTC date fields were displayed from the metadata dump.
    The data set presented in my first post is the EXIF dataset from the file which clearly shows the image was captured by digital camera at
    Create Date                          : 2006:02:20 11:51:12.10
    Date/Time Original              : 2006:02:20 16:51:12.10
    (The delta of 5 hours is the result of Zulu versus local time offset)
    But, when I ingested it into Aperture, the import routine utilized the IPTC field
    File Modification Date/Time     : 2012:09:23 19:53:15-04:00
    which is updated by the OS whenever you move the file around outside of Aperture. (a number of image data fields are updated by the OS - filename for example is another.).  This resulted in the image date fields being stamped in Aperture as:
    Date:                               9/23/12 7:53:15 PM EDT
    Date Created                         9/23/2012 7:53:15 PM
    Which obviously came form the File Modification Date/Time field and not (either) the Create Date or Date/Time Original fields.

  • 10.5.3 problem with Aperture 2.1

    I recently spent the $200 to buy Aperture and have been enjoying it.
    Until, last night I updated Leopard to 10.5.3
    Last night I read about problems other people were having with RAW photos appearing black upon editing after upgrading, and NOW the same thing is happening to me.
    Not only that, but upon adjustments, my photos are also appearing as a 'scrambled' graphic.
    I can't seem to find the post, but I notice that touchy topics are quite often deleted from this forum very fast.
    Does anybody know if Apple has addressed this and plan to release a fix?
    I am a wedding photographer who has a tight deadline to deliver, hence the reason I just picked up a new imac 24" and Aperture 2.1
    Now I am on hold and can not deliver my product. I hope there is some info out there.
    Thanks in advance!
    Message was edited by: colorsound

    I'm posted an image of Aperture corruption, fresh this morning:
    http://lemon.soju.co.uk/2008/06/05/would-you-trust-your-photos-to-an-application -that-does-this/
    - New iMac 3.06GHz Dual Core, 4GB Memory, NVidia 512MB (received Sunday 1st June 2008)
    - 10.5.2 upgraded to 10.5.3, then Aperture 2.1 trial installed
    - First import of 40GB of photos, left to run overnight
    - When trying to use this morning, Aperture screens were corrupt and it refused to shut down. I had to power off then boot back into Mac OS X. When I restarted Aperture it worked, but it still seemed to have problems taking over the machine - eg, I wasn't able to send mail from Gmail within VMWare Fusion until I closed down Aperture. I never have problems with VMWare Fusion.

  • Problem with audio sample rate when exporting

    I am having an issue with my audio sample rate. For some reason it is set at 8 khz by defualt when I am exporting. This was not an issue until the latest update (2 weeks ago). I'll try and give all the info I can up front. Also I tried customer support...that was a nightmare.
    Ok the issue I am addressing is that the audio sample rate when exporting is at 8khz by default. Which to my knowledge has NO relevant use what so ever. Even when I set the file format to h.264 it insists on resetting to 8khz. Even if I manually set everything look at the render queue and click on output module again it changes the sample rate back to 8 khz automatically which I must adjust again. Why can it not just be set at 48000 like every other adobe product is and like it used to be two weeks ago. Does anybody have an answer?

    This problem is addressed by the After Effects CC (12.2.1) bug-fix update, which is now available:
    http://adobe.ly/AE_CC_1221
    Note the part at the end of that page about a crucial update for the Creative Cloud desktop application, which addresses some severe problems with AME, Premiere Pro, and After Effects.

  • Problem with QT PRO image sequence export

    I have quicktime pro. When I export a .avi file into a .bmp sequence, it will name the files like this: whatever0001.bmp, whatever0002.bmp, and so on until whatever8000.bmp, depending on how long the video is. The problem with this is, I need to use the image sequence combined with a WAV file in order to get a certain file format (please, don't ask me what it is). However, the encoder needs to files to be: whatever1.bmp, whatever2.bmp, whatever3.bmp, etc.
    How can I get quicktime pro to export the image sequence .bmp pictures like that? And if it's not possible, can you please point me to some freeware that can (OS X prefered, but I can use windows ones).
    Thanks.

    http://www.publicspace.net/ABetterFinderRename/
    One of dozens of Mac apps that help rename file names.
    Why are you using the .bmp format?
    http://www.iceteks.com/articles.php/imageformats/1

Maybe you are looking for