Dilemma! - HD Slidehow Output from Aperture 3

I have recently upgraded to Aperture 3 and have created a photo only slideshow with music.  I export this using the 1080p HD export setting and Aperture creates a .MOV file.  I play this on my TV via a 1st generation Western Digital Media Player.  Unfortunately this version of the WD player does not support the audio that aperture creates within the MOV file, however the photo images/slideshow is perfect.  The latest version of WD's media player (£150.00) does support this file as I have tried it on a friends.  So for £150.00 (if I want to spend that) I can easily solve the problem.  Of course another way would be to convert the MOV file to say an MP4 or something similar (I'm no expert on file extensions/formats) but although I have tried a few things whihc work and then play fine, I cannot find anything to convert the MOV without any noticeable loss of quality.  Sometimes the loss is only slight but I notice it and I'm a fuss pot.
Is there any way of converting the MOV file Aperture 3 creates to a file forat without any loss of video (and preferably) audio quality?
Thanks.

Compressor within the Final Cut Studio suite.
Handbrake, (free), http://handbrake.fr/
are two options for encoding, as for the quality hits, that will come down to playing with the encode settings.
Tony

Similar Messages

  • Cannot print from Aperture v.2.1.2 to an Epson Artisan 800 printer

    I recently purchased an Epson Artisan 800 printer and I would like to be able to print from Aperture. Unfortunately, I have been unable to do so, in spite of multiple conversations with the Epson support group. I am able to print from other applications, such as TextEdit, Safari, and iPhoto. However, when I try to print from Aperture, I never get any output from the printer. Depending on the image that I try to print from Aperture, I will see an error message flash on the printer's display screen.
    I captured the following error message from the "system.log" file:
    Jan 20 20:11:24 new-host Aperture[12196]: An instance 0xce644a0 of class RKPrintPreviewView is being deallocated while key value observers are still registered with it. Observation info is being leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:\n<NSKeyValueObservationInfo 0xf86da40> (\n<NSKeyValueObservance 0x1c6597e0: Observer: 0xb8c7d10, Key path: selection.isModified, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0x1c641630>\n<NSKeyValueObservance 0xce9b170: Observer: 0xb8c7d10, Key path: selection.gamma, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0xce7e7d0>\n<NSKeyValueObservance 0x1c659830: Observer: 0xb8c7d10, Key path: selection.blackPointCompensation, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0x1c640340>\n<NSKeyValueObservance 0x1c65ef80: Observer: 0xb8c7d10, Key path: selection.colorSyncProfile, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0x1c65d8e0>\n<NSKeyValueObservance 0x1c65d890: Observer: 0xb8c7d10, Key path: selection.dpi, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0x1c6715c0>\n<NSKeyValueObservance 0x1c65eba0: Observer: 0xb8c7d10, Key path: selection.sharpenAmount, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0x1c645070>\n<NSKeyValueObservance 0x1c65ebe0: Observer: 0xb8c7d10, Key path: selection.sharpenRadius, Options: <New: YES, Old: NO, Prior: NO> Context: 0x0, Property: 0x1c645630>\n)
    ----------END of ERROR MESSAGE------------
    I am having this problem on both my iMac G5 and my wife's MacBook. Both are running the latest versions of Mac OS X (10.5.6) and the latest version of Aperture.
    If anyone has been able to print from Aperture to an Epson Artisan 800 printer, please let me know how you did it. Thanks.
    Bruce

    I run 10.4.11 and am unfamiliar with that specific Epson. However step one with Epson troubleshooting is to do any OS updates then download and install the latest Epson driver, even if what you are using is current. The new install will simply install over the old installation. Repair Permissions via Disk Utility immediately before and again immediately after both the OS updates and the printer driver installation.
    Once good Epson paper and a new driver installation are done the final step is to carefully follow Gary Ballard's excellent color management tutorials:
    <http://www.gballard.net/psd.html>
    Good luck!
    -Allen Wicks
    P.S. Epson tech support for consumer printers has always been worse than useless. Specialized support for the pro printers is pretty good.

  • Massive colour variation from Aperture to Photoshop

    Hi there
    I have experienced a startling colour variation when exporting an image form Aperture to Photoshop 3 (for a bit of tweaking).
    Please see this screen grab which shows the variation - particularly the desaturated reds in p/shop:
    http://www.white-adams.co.uk/white-adams.co.uk/ScreenGrab.tif
    (although the screen grab is less dramatic varied than the reality on screen here).
    Some background:
    File is a raw file with some basic adjustments made in Aperture
    I then right-clicked on the version made in Aperture and selected "edit with" Photoshop CS3
    Can anyone help me explain the variation?
    If I want to get this image printed and I export it from Aperture will it retain the lovely saturated reds - or look more like the photoshop version?!
    Help!
    Kind regards
    Robert

    have checked soft-proofing is off in Photoshop
    Configuring Photoshop for compatible assumptions is complex. The first ICC-enabled version was 6 and it introduced dialogues including Colour Settings, Proof Setup, Proof Colours, Print with Preview > Colour Management on top of the old PostScript colour management model and the even older PostScript level 1 model where transfer curves and frequency algorithms get programmed into Encapsulated PostScript and change the calibration of the raster image processor at runtime.
    The controls are here and there technically non-sensical. A couple of critical controls are Simulate > Paper White and Simulate > Ink Black. The English is non-sense, so the localisations are non-sense. If EU localisations are inverted back into English, they read Simulate > White Paper and Simulate > Black Ink - including the German localisation that one would suppose the good people at Heidelberg, FOGRA and Bundesverband Druck und Medien would have had their beady eyes on.
    Why is the English technical non-sense? Because in a colour test chart there is a null colourant patch where the spectrophotometer measures the colour of the paper itself (its L* lightness and its ab hue and chroma); a patch where the colourant combination is C100 M100 Y100 K100 which is where the spectrophometer measures maximum process black; and a patch where the colourant is K100 where the spectrophotometer measures black solid and solo.
    Process black in C100 M100 Y100 K100 is what Photoshop uses in Simulate > Ink Black and the colour of paper measured in the null colourant patch is used in Simulate > Paper White. There were discussions with Adobe in 2004 and again in the following, but I stopped trying to get them to change either their localisations or their source English - let alone the multiple modal dialogues for controlling rendering intent configurations.
    With regard to Aperture, the idea of allowing the enduser to apply a gamma correction on top of the colour management input-output is not a good idea. It helps the one person who doesn't have proper studio lighting for a display-print match, but it does not help the colour management process with other people in a workgroup.
    /hh

  • Few questions related to moving from aperture to iphoto

    i have decided that i want to move from aperture to iphoto,
    a. provided iphoto can meet some basic needs that i have in mind. assuming it can,
    b. the next question will be on how to make the move easiest and effective.
    why, you might ask:
    aperture is great but is more difficult to edit in. further aperture does not have some fun and easy edits - apply styles for instance. not to mention faces and places (although one can expect these features to find their way in aperture over time).
    anyhow i am realizing that if my photo software was as simple as iphoto, i would share more and enjoy more . therefore moving. but moving is tough - need to think through. help appreciated!
    Couple of questions:
    0. i have looked and looked. did not find any solution that is thorough. these two links are the most relevant. http://bit.ly/1WSexN (this one is more of a sync solution, i need to research if it accomplishes what i need done - which is to abandon Aperture. at some point be able to delete Aperture library and the photos that Aperture refers to because the set will quickly get outdated) and http://bit.ly/zc7mC (this one does not answer the questions i have below, although it does seem to suggest that one can do export of projects such that nested folders are created)
    1. i would like to move my projects (comprising of images in aperture) into folders on the hard disk, such that the IPTC tags are stored in the images on the HDD. I assume that masters will already have the tags and versions - no idea? anybody know about this. i will try test it too.
    2. i have rated images extensively in aperture. anybody know how to transfer those ratings to iphoto? one kludgy way i can think of is to save an IPTC tag for every rating level and that hopefully will get transferred over to iPhoto.
    3. importing folders into iPhoto - i am assuming that folders can be imported (by reference, without copying the image file into iphoto library) into iPhoto as events. how will i get the albums from aperture - not sure. kludgy way will be to enter album name as IPTC tag and then create smart albums. too kludgy and painfully slow in my opinion... anybody have ideas?
    3.a. if i import nested folders of images into iPhoto, how would iPhoto treat that? again i can test, but if somebody knows, will not mind the commentary.
    4. simple question - when i edit tags in iphoto, does it edit IPTC tags or does it have non-IPTC tagging approach?
    5. simple question - when i make an edit in iphoto, where does it same the edited file? or is it a virtual version of the master image as in Aperture.
    and that is all

    0. What do you want to move? Use the Show Aperture Library in iPhoto will access your Aperture Previews not your actual files.
    You need to export from Aperture to folders on the desktop and thereafter import to iPhoto. You need to decide if you want to export Originals - which means you'll have to start editing from scratch all over again - Versions, (which will be the edited photos, but you won't have your Originals) - or both. But if you import both to iPhoto you will have a large amount of duplication.
    . i would like to move my projects (comprising of images in aperture) into folders on the hard disk, such that the IPTC tags are stored in the images on the HDD. I assume that masters will already have the tags and versions - no idea? anybody know about this. i will try test it too.
    When you export from Aperture you will need to explicitly choose to write the tags to the output file. This is a setting in the Aperture export dialogue.
    3. importing folders into iPhoto - i am assuming that folders can be imported (by reference, without copying the image file into iphoto library)
    I strongly urge you not to run iPhoto in Referenced Mode. IPhoto works best in the default mode. Should the path to the files change at any point in the future - especially if you move the files to a new disk - then you may find yourself resolving the location of each individual photo in your Library.
    Is there a particular reason you want to run a Referenced Library?
    how will i get the albums from aperture - not sure. kludgy way will be to enter album name as IPTC tag and then create smart albums. too kludgy and painfully slow in my opinion... anybody have ideas?
    That's the best way.
    3.a. if i import nested folders of images into iPhoto, how would iPhoto treat that? again i can test, but if somebody knows, will not mind the commentary
    In the iPhoto Preferences -> Events Uncheck the box at 'Imported Items from the Finder'. Now each folder will be created as an Event. There are no nested events.
    If you don't uncheck the box, then each folder will be broken by date and time into Events.
    4. simple question - when i edit tags in iphoto, does it edit IPTC tags or does it have non-IPTC tagging approach?
    IPhoto works exactly the same way as Aperture. It does not edit the tags on the pic, but stores them in the database. The tags are written to the IPTC on export.
    5. simple question - when i make an edit in iphoto, where does it same the edited file? or is it a virtual version of the master image as in Aperture
    When you edit a pic with or via iPhoto it creates a new version of the photo. This is stored inside the Library package.
    A Note about the iPhoto Library Package:
    In this folder there are various files, which are the Library itself and some ancillary files. Then you have three core folders
    Originals are the photos as they were downloaded from your camera or scanner.
    (ii) Modified contains edited pics, shots that you have cropped, rotated or changed in any way.
    (iii) Data holds the thumbnails the the app needs to show you the photos in the iPhoto Window.
    Remember: iPhoto depends on the structure as well as the contents of this folder. Moving things, renaming things or otherwise making changes will prevent iPhoto from working and could even cause you to damage or lose your photos.
    Regards
    TD

  • Going back/away from aperture

    i have this problem with importing DNGs with all my settings (see my other post).
    that made me think, what if in a year or two i decide to migrate away from aperture to another software (lightroom, captureone, unknown)?
    is it possible to export your files/adjustment/settings and import them in another application?
    i don't seem to be able to do it, as of now.
    also, how do you make IVMP to read aperture adjustments? not keywords, image adjustments.
    thanks,
    @lberto

    I'm not sure how helpful this will be Alberto, as your needs for metadata probably overshadow mine. Plus I have a RAW supported camera: key issue!!!
    Prior to Aperture, I used PS CS2/ACR/Bridge combo. I set date/time in camera and diligently changed for time zones.
    Import from CF card to "Unprocessed" folder under project/event under location under year folder structure
    Rename in Finder using "Renamer4Mac" utility
    Save to DVD
    Select in Bridge, open a select into ACR and save as PSD to "Part Processed" folder
    Continue (hand notes for images processed I've done ... ugh) [BTW, comments/notes in Aperture has been requested by some folks and its a great idea in my mind]
    Open each image in CS2 and adjust/crop/save ... as different versions for different print or crops. Save to "Processed" folder
    Burn folder to DVD
    Post-process in Pages, InDesign ...
    With Aperture .... BTW: I do not generate Previews until I've completed the project
    Copy CF card to disk
    Burn DVD
    Import from disk to new Project: name files using import naming options (I tend to use custom). Add Copyright and keywords (I tend to add a superset and then remove ad hoc later). Set auto-stack time to make as much sense as possible (adjust discrepancies manually later). Then import.
    First pass:
    Scan images sequentially and reject, or mark as 1*, 3*, 5*. Note that Aperture caches the next/last images so this speeds up image "Loading" times considerably.
    Adjust any stack membership
    Second pass:
    Adjust RAW settings ad hoc (for shadowy or very bright or shiny surface images I use different RAW presets)
    Adjust for any exposure, levels, shadow/highlight, WB etc.
    Adjust straighten then dust
    Create different crop versions
    Amend * ratings up/down and esp. for crop preferences
    Alter keywords (delete or add additional if necessary)
    Output to external editor (around 2% images) for filters or blemishes above/beyond spot/patch
    Set stack pick
    Once this pass is complete, I generate full res. JPG's
    Back up to Vault
    From that point I'm into post-process, and I'm doing the majority of that from Aperture direct into Pages and iWeb or from Aperture itself.
    Except for panoramas, where I export TIF's to Calico, and re-import the new image, then manually stack with the original images, I hardly move out of Aperture. My use of CS2 has dropped from 100% to a couple of %, and those tend to be for soft filter actions applied to unmask, liquify filter or occasionally I'll use Nik plug-in's or clone stamp and healing brushes with pen sensitivity.
    As I said up front, I'm not sure how useful this will be. I didn't feel a need for PhotoMechanic or iView, and my level of pain with Bridge/ACR/CS2 was easy for me to leave .... even Aperture 1.0 with less than ideal hardware was a significant productivity gain.
    Working between Aperture and other apps. is likely to be tiresome. Working within Aperture becomes really smoooooth.
    So, unless you absolutely must have can't live without the world will end some function of these, consider how you could make do with Aperture's nearest equivalent. Give a negative score to Aperture though. If a function is required, then can you export to/import from at a point in an Aperture centric workflow? If so, score as a negative to Aperture. (If you cannot see how to interface to Aperture, ask. If the answers still no, then you know.) Then, score the things that Aperture gives you as a benefit. If your tally is net positive (and I trust that it will), or a net negative, you've answered your question.
    G.

  • Export to SmugMug from Aperture - all metadata is lost

    I've had flawless results in metadata remaining intact using SmugExporter or ApertureToSmugMug until recently. Now all of my exports strip the captions, keywords and even the basics of 'date taken' from my photos when they post to SmugMug.
    What is going wrong? I'm using my MacPro, Aperture version 1.5.6 and Tiger 10.4.11.
    I read a post while researching this problem about checking a box saying I want to export metadata. I don't know where it's located. I never checked it and I certainly never un-checked it.
    Any suggestions are welcome.

    Thanks for the response, Vittra. I'm guessing that's a simpler way to fix settings, but I can't check it out right now since exporting does not work in the background on Aperture. This is the method I was told to use and it worked too:
    I searched and posted in several forums before calling Apple Support today. I've discovered the problem with that tech person's guidance. If anyone else faces this dilemma, check your settings here:
    Aperture > File > Export Versions
    Then you get a pop up box with some drop down menus. The top drop down box has 'Edit' at the bottom of its list. Go into there. You'll have several preferences to choose from (file type, dimensions, quality, etc) and there's a tiny box that accidently got unchecked which says something like: Include Metadata.
    I can't check it for exact wording because I'm merrily re-exporting right now - Metadata intact!

  • Export from Aperture builds file structure like projects/albums

    Hi!
    I use Aperture but also want to use iPhoto (for iLife-Integration - and for the superb presentation facitilities like slideshos with Ken Burns effect etc.).
    I´d like to know whether there is a possibility to export from Aperture - perhaps via Automator-script - that the structure of projects, folders, albums, etc. is beeing transferred into the same structure but made of folders. The picture-files themselves should be jpgs.
    Can something like that be realized in Automator? Or is there another possibility to get such a result?
    regards,
    Sandro

    When you export versions via the export versions window you have the opportunity to specify the output folder structure for the images.
    So for example you can select a subfolder structure using the images year/month/day or the project name or the image year/month etc.
    You'll need to look through the options and see what settings will work for you.

  • Terrible red color cast when printing from aperture

    I have printed the same image from Iphoto as well as a windows machine and got very nice prints on my Epson R2880. However, every time i print from Aperture it comes out with a terrible red cast. I have tried the system managed colorsync profile as well as the generic one. (FWIW, B&W prints from Aperture on the R2880 come out very nice)
    Any other ideas?

    You may find it helpful.
    Thanks, but if you look in the archives of the Apple ColorSync Users List, you'll find thousands of posts from his Mac dating back to the beginning of the List.
    The principle is that you configure your device colour spaces to the largest gamut of which they are capable, calibrate them to a stable condition, characterise that condition in a measured test chart, and build ICC device profiles for those characterisations in your ICC profiling package of choice.
    You then capture and correct colour with correct colour previews, resulting in normalised exposures in an ideal CIE colour space. With you normalised exposures, you convert into output condition 1, output condition 2, output condition n which is what repurposing is about.
    But you do no apply a gamma change on top of the colour managed rendering. That is incorrect by definition. You apply your gamma change as part of the colour correction in order to get your normalised exposure.
    If you imagine this in a prepress process, then you can forget the concept of determinate rendering which is the bedrock of the ICC architecture. If you as photographer do a gamma correction on top of your presentation print or proof print, then you can claim that you have a presentation print, but you cannot contractually claim that you have a proof print as your proof print is a colour correction on top of the colour management system. If Apple Aperture allows the user access to colour correction on top of colour management, then that is a bug in the application. Sorry ...
    /hh

  • Unlogged Missing Photos After Import From Aperture

    Hi!
    I have just made the switch from Aperture to Lightroom, and have use the 1.1 version of the Aperture import plugin.
    In my Aperture Library I have, according to the Library -> Photos: 11105 Photos, however after importing to Lightroom, I have only 10967 photos. I have checked the import log, and there were 4 items which failed to import - 3 were .mpo files (panoramas from an xPeria) and 1 was a .gif file. This leaves a deficit of 133 photos that I can't account for.
    Is there any way to compare the aperture library to the lightroom library to see what is missing?

    *WARNING* Once agin, this is a VERY long post! And this contains not only SQL, but heaps of command line fun!
    TLDR Summary: Aperture is storing duplicates on disk (and referencing them in the DB) but hiding them in the GUI. Exactly how it does this, I'm not sure yet. And how to clean it up, I'm not sure either. But if you would like to know how I proved it, read on!
    An update on handling metadata exported from Aperture. Once you have a file, if you try to view it in the terminal, perhaps like this:
    $ less ApertureMetadataExtendedExport.txt
    "ApertureMetadataExtendedExport.txt" may be a binary file.  See it anyway?
    you will get that error. Turns out I was wrong, it's not (only?) due to the size of the file / line length; it's actually the file type Aperture creates:
    $ file ApertureMetadataExtendedExport.txt
    ApertureMetadataExtendedExport.txt: Little-endian UTF-16 Unicode text, with very long lines
    The key bit being "Little-endian UTF-16", that is what is causing the shell to think it's binary. The little endian is not surprising, after all it's an X86_64 platform. The UTF-16 though is not able to be handled by the shell. So it has to be converted. There are command line utils, but Text Wrangler does the job nicely.
    After conversion (to Unicode UTF-8):
    $ file ApertureMetadataExtendedExport.txt
    ApertureMetadataExtendedExport.txt: ASCII text, with very long lines
    and
    $ less ApertureMetadataExtendedExport.txt
    Version Name    Title   Urgency Categories      Suppl. Categories       Keywords        Instructions    Date Created    Contact Creator Contact Job Title       City    State/Province  Country Job Identifier  Headline        Provider        Source  Copyright Notice        Caption Caption Writer  Rating  IPTC Subject Code       Usage Terms     Intellectual Genre      IPTC Scene      Location        ISO Country Code        Contact Address Contact City    Contact State/Providence        Contact Postal Code     Contact Country Contact Phone   Contact Email   Contact Website Label   Latitude        Longitude       Altitude        AltitudeRef
    So, there you have it! That's what you have access to when exporting the metadata. Helpful? Well, at first glance I didn't think so - as the "Version Name" field is just "IMG_2104", no extension, no path etc. So if we have multiple images called "IMG_2104" we can't tell them apart (unless you have a few other fields to look at - and even then just comparing to the File System entries wouldn't be possible). But! In my last post, I mentioned that the Aperture SQLite DB (Library.apdb, the RKMasters table in particular) contained 11130 entries, and if you looked at the Schema, you would have noticed that there was a column called "originalVersionName" which should match! So, in theory, I can now create a small script to compare metadata with database and find my missing 25 files!
    First of all, I need to add that, when exporting metadata in Aperture, you need to select all the photos! ... and it will take some time! In my case TextWrangler managed to handle the 11108 line file without any problems. And even better, after converting, I was able to view the file with less. This is a BIG step on my last attempt.
    At this point it is worth pointing out that the file is tab-delimited (csv would be easier, of course) but we should be able to work with it anyway.
    To extract the version name (first column) we can use awk:
    $ cat ApertureMetadataExtendedExport.txt | awk -F'\t' '{print $1}' > ApertureMetadataVersionNames.txt
    and we can compare the line counts of both input and output to ensure we got everything:
    $ wc -l ApertureMetadataExtendedExport.txt
       11106 ApertureMetadataExtendedExport.txt
    $ wc -l ApertureMetadataVersionNames.txt
       11106 ApertureMetadataVersionNames.txt
    So far, so good! You might have noticed that the line count is 11106, not 11105, the input file has the header as I printed earlier. So we need to remove the first line. I just use vi for that.
    Lastly, the file needs to be sorted, so we can ensure we are looking in the same order when comparing the metadata version names with the DB version names.
    $ cat ApertureMetadataVersionNames.txt | sort > ApertureMetadataVersionNamesSorted.txt
    To get the Version Names from the DB, fire up sqlite3:
    $ sqlite3 Library.apdb
    sqlite> .output ApertureDBMasterVersionNames.txt
    sqlite> select originalVersionName from RKMaster;
    sqlite> .exit
    Checking the line count in the DB Output:
    $ wc -l ApertureDBMasterVersionNames.txt
       11130 ApertureDBMasterVersionNames.txt
    Brilliant! 11130 lines as expected. Then sort as we did before:
    $ cat ApertureDBMasterVersionNames.txt | sort > ApertureDBMasterVersionNamesSorted.txt
    So, now, in theory, running a diff on both files, should reveal the 25 missing files.... I must admit, I'm rather excited at this point!
    $ diff ApertureDBMasterVersionNamesSorted.txt ApertureMetadataVersionNamesSorted.txt
    IT WORKED! The output is a list of changes you need to make to the second input file to make it look the same as the first. Essentially, this will (in my case) show the Version Names that are missing in Aperture that are present on the File System.
    So, a line like this:
    1280,1281d1279
    < IMG_0144
    < IMG_0144
    basically just means, that there are IMG_0144 appears twice more in the DB than in the Metadata. Note: this is specific for the way I ordered the input files to diff; although you will get the same basic output if you reversed the input files to diff, the interpretation is obviously reversed) as shown here: (note in the first output, we have 'd' for deleted, and in the second output it's 'a' for added)
    1279a1280,1281
    > IMG_0144
    > IMG_0144
    In anycase, looking through my output and counting, I indeed have 25 images to investigate. The problem here is we just have a version name, fortunately in my output, most are unique with just a couple of duplicates. This leads me to believe that my "missing" files are actually Aperture handling duplicates (though why it's hiding them I'm not sure). I could, in my DB dump look at the path etc as well and that might help, but as it's just 25 cases, I will instead get a FS dump, and grep for the version name. This will give me all the files on the FS that match. I can then look at each and see what's happening.
    Dumping a list of master files from the FS: (execute from within the Masters directory of your Aperture library)
    $ find . -type f > ApertureFSMasters.txt
    This will be a list including path (relative to Master) which is exactly what we want. Then grep for each version name. For example:
    $ grep IMG_0144 ApertureFSMasters.txt
    ./2014/04/11/20140411-222634/IMG_0144.JPG
    ./2014/04/23/20140423-070845/IMG_0144 (1).jpg
    ./2014/04/23/20140423-070845/IMG_0144.jpg
    ./2014/06/28/20140628-215220/IMG_0144.JPG
    Here is a solid bit of information! On the FS i have 4 files called IMG_0144, yet if I look in the GUI (or metadata dump) I only have 2.
    $ grep IMG_0144 ApertureMetadataVersionNamesSorted.txt
    IMG_0144
    IMG_0144
    So, there is two files already!
    The path preceding the image in the FS dump, is the date of import. So I can see that two were imported at the same time, and two separately. The two that show up in the GUI have import sessions of 2014-06-28 @ 09:52:20 PM and 2014-04-11 @ 10:26:34 PM. That means that the first and last are the two files that show in the GUI, the middle two do not.... Why are they not in the GUI (yet are in the DB) and why do they have the exact same import date/time? I have no answer to that yet!
    I used open <filename> from the terminal prompt to view each file, and 3 out of my 4 are identical, and the fourth different.
    So, lastly, with a little command line fu, we can make a useful script to tell us what we want to know:
    #! /bin/bash
    grep $1 ApertureFSMasters.txt | sed 's|\.|Masters|' | awk '{print "<full path to Aperture Library folder>"$0}' | \
    while read line; do
      openssl sha1 "$line"
    done
    replace the <full path to Aperture Library folder> with the full path to you Aperture Library Folder, perhaps /volumes/some_disk_name/some_username/Pictures/.... etc. Then chmod 755 the script, and execute ./<scriptname> <version name> so something like
    $ ./calculateSHA.sh IMG_0144
    What we're doing here is taking in the version name we want to find (for example IMG_0144), and we are looking for it in the FS dump list. Remember that file contains image files relative to the Aperture Library Master path, which look something like "./YYYY/MM/DD/YYYYMMDD-HHMMSS/<FILENAME>" - we use sed to replace the "./" part with "Masters". Then we pipe it to awk, and insert the full path to aperture before the file name, the end result is a line which contains the absolute path to an image. There are several other ways to solve this, such as generating the FS dump from the root dir. You could also combine the awk into the sed (or the sed into the awk).. but this works. Each line is then passed, one at a time, to the openssl program to calculate the sha-1 checksum for that image. If a SHA-1 matches, then those files are identical (yes, there is a small chance of a collision in SHA-1, but it's unlikely!).
    So, at the end of all this, you can see exactly whats going on. And in my case, Aperture is storing duplicates on disk, and not showing them in the GUI. To be honest, I don't actually know how to clean this up now! So if anyone has any ideas. Please let me know I can't just delete the files on disk, as they are referenced in the DB. I guess it doesn't make too much difference, but my personality requires me to clean this up (at the very least to provide closure on this thread).
    The final point to make here is that, since Lightroom also has 11126 images (11130 less 4 non-compatible files). Then it has taken all the duplicates in the import.
    Well, that was a fun journey, and I learned a lot about Aperture in the process. And yes, I know this is a Lightroom forum and maybe this info would be better on the Aperture forum, I will probably update it there too. But there is some tie back to the Lightroom importer to let people know whats happening internally. (I guess I should update my earlier post, where I assumed the Lightroom Aperture import plugin was using the FS only, it *could* be using the DB as well (and probably is, so it can get more metadata))
    UPDATE: I jumped the gun a bit here, and based my conclusion on limited data. I have finished calculating the SHA-1 for all my missing versions. As well as comparing the counts in the GUI, to the counts in the FS. For the most part, where the GUI count is lower than the FS count, there is a clear duplicate (two files with the same SHA-1). However I have a few cases, where the FS count is higher, and all the images on disk have different SHA-1's! Picking one at random from my list; I have 3 images in the GUI called IMG_0843. On disk I have 4 files all with different SHA-1's. Viewing the actual images, 2 look the same, and the other 2 are different. So that matches 3 "unique" images.
    Using Preview to inspect the exif data for the images which look the same:
    image 1:
    Pixel X Dimension: 1 536
    Pixel Y Dimension: 2 048
    image 2:
    Pixel X Dimension: 3 264
    Pixel Y Dimension: 2 448
    (image 2 also has an extra Regions dictionary in the exit)
    So! These two images are not identical (we knew that from the SHA-1), but they are similar (content is the same - resolution is the same) yet Aperture is treating these as duplicates it seems.. that's not good! does this mean that if I resize an image for the web, and keep both, that Aperture won't show me both? (at least it keeps both on disk though, I guess...)
    The resolution of image 1, is suspiciously like the resolutions that were uploaded to (the original version of) iCloud Photos on the iPhone (one of the reasons I never used it). And indeed, the photo I chose at random here, is one that I have in an iCloud stored album (I have created a screensaver synced to iCloud, to use on my various Mac's and AppleTVs). Examining the data for the cloud version of the image, shows the resolution to be 1536x2048. The screensaver contains 22 images - I theorised earlier that these might be the missing images, perhaps I was right after all? Yet another avenue to explore.
    Ok. I dumped the screensaver metadata, converted it to UTF-8, grabbed the version names, and sorted them (just like before). Then compared them to the output of the diff command. Yep! the 22 screensaver images match to 22 / 25 missing images. The other 3, appear to be exact duplicates (same SHA-1) of images already in the library. That almost solves it! So then, can I conclude that Lightroom has imported my iCloud Screensaver as normal photos of lower res? In which case, it would likely do it for any shared photo source in Aperture, and perhaps it would be wise to turn that feature off before importing to Lightroom?

  • Discoverer report - Output from Discoverer plus is not the same as Discoverer desktop

    As a part of Upgrade project we are migrating the discoverer reports from 11i (11.5.10.2) to R12 (12.1.3) .After migrating to R12, for a custom discoverer report the output given by discoverer desktop is correct (24 rows for a scenario). But the report output from Discoverer plus does not show the credit transactions (2 rows). The output from Discoverer plus shows only 22 rows (24 - 2), which is incorrect. The query is the same in Discoverer desktop and Discoverer plus.
    Please let me know why these transactions that are appearing when the report is run from discoverer desktop are not appearing in discoverer plus. Is there any setup in discoverer plus for this?
    Regards,
    Brajesh

    Pretty hard to answer a question like this.  Best bet would be to copy the existing discoverer plus book and start removing conditions, fields, etc until those two rows from desktop show up and see if you can work it out. 

  • Unable to output from FCP to Canon XL1.

    I have an eMac with Final Cut Pro 4.5 HD. I also have a Canon XL1 3 CCD camcorder.
    I have no problem capturing footage from my camcorder to my eMac on FCP. I can also connect my Canon to my VCR and record off my camcorder to my TV, as well as play the tape on my camcorder to watch it on TV.
    However, I cannot output from FCP to my camcorder. The 4 to 6 FireWire is attached to both the camera and the eMac and I checked the Log and Capture feature and FCP does recognize a camera or deck is attached. I've been trying to output it using manual record in which I press record on my camcorder and play the playhead on FCP. As I record, there is no picture on my viewfinder, nor any audio being recorded and when I play it back, I just get this blank blue screen, but the timecode is recorded.
    Am I missing something here?

    ensure the following are set
    View>Video Playback>Firewire Apple 720x480 (NTSC or PAL - whatever is appropriate)
    View>Audio Playback>Audio follows video
    View>External Video>All Frames
    If this isn't what you are set to do, you won't be sending video out to your recorder.
    x

  • How to sync both from hard drive folders and from Aperture?

    I have the following problem. So far I was syncing photos directly from my hard drive folders and everything was fine. Recently I decided to add some photos from Aperture albums. When I did this all previous photos synced from HD were deleted. When I switched back to syncing from folders, the photos from Aperture were deleted. It looks that it is impossible to sync from both sources. Anyone had this problem and found the solution?

    I couldn't figure this out on my device, so I just consolidated them into one sync folder by copying photos.
    Good thing I have extra disc space.....

  • Copying pictures from Aperture 3

    My wife wants to upload some of our picutres to the Costco web site for printing. She's been copying the individual images from Aperture to a folder on our desktop. In doing so she's noticed that the individual file sizes are quite small and that they're nowhere near the full size of the individual image files. How should she be copying the pictures so she gets a larger file size?

    How should she be copying the pictures so she gets a larger file size?
    How did she copy the files to the desktop? By dragging them from Aperture's Browser window? Then she will only have exported the previews, not the full size images.
    To export full size images,
    select the image you want to export in the Browser.
    Then use the command "File > Export > Version(s)" from the main menu bar
    In the panel that will pop up, select a suitable "Export preset", for example "Jpeg - Original size".
    If the exported image is still to small, set the "Export Preset" to "Edit" and check the export preset, if it has been modified.
    Regards
    Léonie

  • How to Generate CSV Output from JD Edwards BI Publisher

    Hi All,
    I have a report "Critical Date Report" - R15611 in JD Edwards 8.11. This report has to be generated as CSV output from BI Publisher which is embedded to JDE.
    The purpose we want use BI Publisher is to move some of the data displaying to different place in the page(ex: Move the company address from top left corner to Bottom right corner).
    In order to achieve this
    1.We created blank rtf template and upload to XML repository using P95600 application
    2.Create report definition using P95620 application
    3.Here I see the available output types as PDF,RTF,HTML,EXCEL,POWERPOINT and XML,ETEXT(GRAYED OUT)
    Which output type we can use for CSV ?
    4.Execute the report definition of the critical date report from P95620 to get the XML source
    5.This XML source will be loaded into the blank rtf template
    6.From this point no idea how to design the rtf template in order to get the CSV output.
    7.We did design and output type as excel - but the result data is not in good formatting and alignment*(Headers and footers are repeating).*
    If any one has worked on similar type of requirement,let us know how to do or send a sample XML source,rtf template and how the CSV output will be. Or any document link present in Oracle site will be helpful. Please let me know if you need more details.
    Thanks in Advance.
    Vijay

    Hi Vijay,
    For CSV output, you need an E-text template (not RTF) that's why its grayed out! You can use Excel as output type and have (No headers and footers) , then you can open the file in Excel and store it as CSV. Does not always display correctly though.
    Why are you compelled to use BI publisher? you can use the JDE standard csv output report, (as is used by most EDI systems) of course this may involve a bit of customization if you wants the fields arranged differently.
    -Domnic

  • Error message by periodic weekly: No output from the 1 file processed

    Hi there,
    since four weeks, I got a problem with the maintenance script periodic weekly. Up to December 22nd, the script did, what it should do: rebuilding the database of locate and whatis, rotating log-files. Since one week later, I got the error message: No output from the 1 file processed.
    Normally, I use Anacron to do the job. When I noticed the problem, I tried to start the script with Tinker Tool System getting the same result. Another try using the Terminal (sudo periodic weekly) also failed. The commands locate and whatis are working, locate.updatedb and makewhatis also. I'm running 10.4.8; in the past, I did not have such problems. Anyone with an idea or solution?
    Thanks
    Klaus
    MacBook Pro   Mac OS X (10.4.8)  

    Hi Gary,
    here is the output you were asking for:
    Last login: Thu Jan 25 20:03:55 on console
    Welcome to Darwin!
    DeepThought:~ dirk$ sudo /private/etc/periodic/weekly/500.weekly; echo $?
    Password:
    Sorry, try again.
    Password:
    Rebuilding locate database:
    Rebuilding whatis database:
    find: /usr/local/man: No such file or directory
    makewhatis: /usr/share/man/man1/fetchmailconf.1.gz: No such file or directory
    Rotating log files: ftp.log lpr.log mail.log netinfo.log ipfw.log ppp.log secure.log
    access_log error_log
    Running weekly.local:
    Rotating psync log files:/etc/weekly.local: line 17: syntax error near unexpected token `)'
    /etc/weekly.local: line 17: `if [ -f /var/run/syslog.pid ]; then kill -HUP 0 80 79 81 0cat /var/run/syslog.pid | head -1); fi'
    2
    DeepThought:~ dirk$ ls -loe /private/etc/periodic/weekly/500.weekly
    -r-xr-xr-x 1 root wheel - 2532 Jan 13 2006 /private/etc/periodic/weekly/500.weekly
    DeepThought:~ dirk$
    It seems, Rogers idea, PsynX respectively the deficient uninstalling by me is responsible for my problems, is correct. Should I remove the whole file weekly.local or should I only remove the content? I prefer removing the whole file, because it was created while installing PsyncX. The date of creation is the same as the date of installing the app (December 25).
    Klaus
    By the way: it seems to me, the solution of my problem is in sight. So I want to thank you all for the amazing aid I got from you!

Maybe you are looking for