Aperture file issue

Dear Kirby, reading some of your threads, I am very impressed by your knowledge about special issues concerning "Aperture", and would be most obliged to you, if you could possibly help me with a suggestion with regard to the below issue:
I just returned from a trip to Vietnam bringing along home 2000 photos, approx. 50 GB, and having started my editing them, I discover an unacceptably, and so far not observed, slow rendering, f.inst. when dodging and burning. Therefore I would appreciate any hint given to me about what to do to change this unbearable situation - thus, it may take up to 5 seconds to render f. inst a burning process.
Operating System: Mac OS X 10.7.2 Lion
My hardware:
Macbook Pro Intel, 8GB, HD: 500GB, Free: 142GB, 28%, 142GB pictures contained on the hard drive - and a great deal of relocated masterfiles to external disks.
5 Nik software plugins installed, but they are NOT in use all of them at the same time.
Have tried to shift from 32 to 64 bit, but without a remarkable effect.
Very best regards
Per
[COMPLAIN]
[IGNORE USER] [BOOKMARK] [REPLY THIS MESSAGE] [QUOTE]
< Title Edited By Host >

Our Host was nice enough to start a new thread with this post, which had been mistakenly posted as a reply in another thread. The OP, however, has already started his/her own thread. Please reply there.
Replies to this are better put in this other thread.
Thanks.

Similar Messages

Aperture Library Issues on NAS - Advice Needed

List-
Need some practical advice here. I've got a 90GB Aperture library that resides on a NAS (QNAP 419P II) that is experiencing major issues. Understood that having the library live on a non-HFS+, non-local drive is not advised by Apple, but it's been there for two years with no issues to speak of.
I had a power failure occur that seems to have done some damage to the library in some way. Upon opening the library, I got an error that said that there were inconsistencies with the file and that it needed to be repaired. I repaired it, and noticed something strange. In almost all files, the picture resolution was poor and both the camera and lens information was gone--in addition to the fact that the Adjustments capability was disabled.
I ran the Aperture first aid and ran all three processes--concluding with the full library rebuild. It looked to be successful and resolution, previews, and picture info returned--but halfway through the preview reprocessing the process just stopped and the beach ball of death ensued. I let it run overnight and it never recovered. I had to force quit and now if I reopen the file it say that there are inconsistencies and that the library needs to be repaired, which won't help.
I also tried to move the library off of the NAS an onto the local drive, but encountered an Error - 50 message--something that apparently is well known in the NAS world where Mac permissions get screwy when dealing with non HFS+ drives.
I have a backup of the original library, but it is sitting in a cloud repository (CrashPlan) that will take time and money to restore.
All of the masters are intact in the Aperture directory, and I have very few major adjustments made to any photos. Aperture is really just a repository for me.
So any practical advice would be appreciated as to how I can create a new local Aperture library and get all of the existing photo files there. I am pretty much giving up on the idea of getting the existing NAS-based library to work properly, so this is more of a real-world question on how to create a new library and eliminate whatever issues there are with the other Aperture files. It looks like everything in the Aperture package is in place, but the library itself is just malfunctioning.
I am also considering moving everything into iPhoto as well, as Aperture may simply be more than I need for my usage. If is is faster and a but simpler to manage, that could be the right answer as well.
Thanks in advance for any ideas or guidance.

The problem is most likely with the library itself being located on the NAS.
But you can have a hybrid solution where the library is located on your internal drive while the actual image files are located externally, eg on your NAS. Image files stored within the Apeture library are called "managed" while image files stored externally are called "referenced". Whichever approach you take, the process is the same:
If you try to make a new Library from your masters, you will lose your project structure. The resulting mess will be in accordance to how you created your projects. Basically, if you look at your Masters folder, that's what you'll end up with when you import your masters. If that isn't a problem, the process is simple
Step 1: Prep.
Move or copy your masters out of the library bundle to a folder (to make them more accesible in finder).
Step 2: Create new library.
Within Aperture, from the File menu "Switch to Library -> Other/New..." to create a new Library on your internal drive.
Set the preferences to indicate previews/faces etc. I'd turn these off for now as they will slow you down.
Step 3: Import your images.
Within your new library, File -> Import - Folders as Projects. This gives you a dialog where you specifiy what and where to import.
If you choose "Import folders as: Folders and Projects" you will get a folder structure that matches the Masters folder, with projects at the end of the chain with names like 20120213-200100.
If you choose "Import folders as: Projects and Albums" you will get a single Project called "Masters" with a folder and Album structure that matches the Masters folder.
Neither of these will look particularly great. If you want to avoid this mess, here's what I'd try.
Fix your library again like you did before. After the rebuild, go to the Aperture activity window (SHIFT + CMD + 0) and cancel the preview generation process before it has chance to hang. This should give you a sem-functional library, hopefully functional enough for the next step:
Select all images and use File -> Relocate Original to move your original files out of the library. During this process you can specify that the originals are stored in sub-folders that match the project name, within a parent folder if required.
This gives you a much neater structure for importing into your new library where the projects will get the folder names (which will be your existing project names). It may not be perfect, for example if you have the same project name in different folders and don't/can't segregate them, but it's a lot cleaner than just importing your masters folder.
Andy

How do you share Aperture file across multiple users on same Mac?

How do you share Aperture file across multiple users on same Mac? Seems this should be a preferences choice.

When you share your library between users, you may run into permission and ownership problems, if both users are editing the Aperture library and not only reading it. To avoid that, it helps to put the Aperture library onto a separate disk or a separate partion of your hard drive. For s separate partition or disk you can enable the "ignore ownership on this volume" flag. Then all users can access the library as owners of this library.
You might try to put the aperture library into a shared folder on your mac, but that has caused problems recently, i.e. when the library also contains video files.
Regards
Léonie

How can I transfer all my photos from mb aperture file to a external hdd?

The problem is it is taking too much of my internal memory therefore I want to transfer all my photos from mb to external. can somebody help me???

More complete explanation:
First make a Vault to an external drive as backup.
Then from within Aperture:
File Menu--> Relocate Masters.
Next back up the drive that the Masters were relocated to, because now you have a Referenced Masters Library so Masters are backed up (once) separately from the Library Vault backups.
In the future back up originals (once) on external drives prior to import into Aperture or any other images app. I cannot overstate how important that is, and various manuals, texts, etc. present workflows that skip that critical step. Also back up the Aperture Library using Aperture's Vaults, which are designed for that purpose.
A complete Referenced-Masters workflow follows. Note that for image security reasons Aperture is not involved until the end of the process:
• Create a folder ("abc") for the incoming images. Easiest is to create the folder on the external hard drive where the Masters will permanently live, but Referenced Masters can be temporarily on the laptop's internal drive, then moved later as described above. I initially put Masters referenced on my MBP internal drive, then after backup and editing I use File Menu--> Relocate Masters to move the Masters to a permanent external drive location.
• Connect a card reader with the camera card in it. The camera card should show on the desktop. If it does not show, restart the Mac with the reader and card still plugged in. You can of course use the camera directly in this step, but I do not recommend it. Obviously cameras like the iPad2 do require direct camera-to-computer uploading.
• Drag the contents of the card's image folder(s) to the abc folder that you previously created on the hard drive.
• Review the abc folder contents to be sure they all copied properly.
• Software-eject the camera card.
• Physically disconnect the camera card reader from the Mac. This step is important to help avoid all-too-common human error.
• Again review the abc folder contents to be sure they are indeed all there (because stuff happens sometimes...).
• Back up the abc folder contents on to another drive.
• Review the files on the backup to be sure they all copied properly.
• At any time after but not before the previous step you can reformat the camera card in-camera. Do not delete images on the card using the computer.
• Start Aperture.
• Import the images from folder abc into Aperture, selecting "Store Files: In their current location" on the right-hand side of the import window (important!).
HTH
-Allen Wicks

Is there a way to transfer Aperture files to Photoshop CS5 for editing?

Is there a way to transfer Aperture files to Photoshop CS5 for editing? I recently had a crash of CS5 Bridge. It seems to have caused a problem with Aperture. So, I reinstalled both CS5 and Aperture. Before installing CS5 I uploaded NEF (Nikon RAW) files to Aperture. Now I have reinstalled CS5 I want to use it to edit the same photos from Aperture, as I know more about editing in CS5 than Aperture. I tried to export to CS5 but, Aperture would not give me that option. At least I could not find it.

You can set an external editor in the "Aperture Preferences -> Export " settings.
Just set this to CS5.
The resullt of your external edit will create a new version of your image.

Ocrfile is not being written to. open file issues. Help please.

I've been troubleshooting an open file issue on our Test environment for quite a while now. Oracle has had me update to latest CRS bundle for 10.2.0.3, then upgrade to 10.2.0.4, then two more patches via OPatch to bring 10.2.0.4 RAC to it's most recent patch. None of these patches resolved our problem. We have ~8700 datafiles in the database and once the database is started, we're at ~11k on Production but on Test we're at ~37K or higher. It takes 1-2 days to hit the 65536 limit before it crashes. I have to 'bounce' the database to keep it from crashing. Yes, I could raise the ulimit but that isn't solving the problem.
Over the weekend I noticed that on Production and DEV, the ocrfile is being written to constantly and has a current timestamp but on Test, the ocrfile has not been written to since the last OPatch install. I've checked the crs status via 'cluvfy stage -post crsinst -n all -verbose' and everything comes back as 'passed'. The database is up and running, but the ocrfile is still timestamped at April 14th and open files jump to 37k upon opening the database and continue to grow to the ulimit. Before hitting the limit, I'll have over 5,000 open files for 'hc_<instance>.dat, which is where I've been led down the path of patching Oracle CRS and RDBMS to resolve the 'hc_<instance>.dat bug which was supposed to be resolved in all of the patches I've applied.
From imon_<instance>.log:
Health check failed to connect to instance.
GIM-00090: OS-dependent operation:mmap failed with status: 22
GIM-00091: OS failure message: Invalid argument
GIM-00092: OS failure occurred at: sskgmsmr_13
That info started the patching process but it seems like there's more to it and this is just a result of some other issue. The fact that my ocrfile on Test is not being written to when it updates frequently on Prod and Dev, seems odd.
We're using OCFS2 as our CFS, updated to most recent version for our kernel (RHEL AS 4 u7 -- 2.6.9-67.0.15.ELsmp for x86_64)
Any help greatly appreciated.

Check Bug... on metalink
if Bug 6931689
Solve:
To fix this issue please apply following patch:
Patch 7298531 CRS MLR#2 ON TOP OF 10.2.0.4 FOR BUGS 6931689 7174111 6912026 7116314
or
Patch 7493592 CRS 10.2.0.4 Bundle Patch #2
Be aware that the fix has to be applied to the 10.2.0.4 database home to fix the problem
Good Luck

Easy Photo Print does not see Aperture files

I have a Canon MP640 printer, which gives me really poor results when used with Aperture (3.1.3) so I have been using the print software that came with my printer (Easy photo print EX). The problem with Easy PhotoPrint, is that this software does not see my Aperture files, even though I have turned on the “View in finder” feature in Aperture. Can anyone tell me how to configure my system, so that Easy PrintPhoto will see my files, without having to export every time I want to print

Ahh ok, that function File->Show In Finder shows the current selection in the finder if it is a referenced image. That's all it does, it doesn't cause any permanent changes to any settings in Aperture or the Finder. Why you couldn't see your referenced files in the finder before clicking this and now you can is a mystery and a coincidence and will do nothing to enable other programs from accessing the images in the library.
As for turning off color management when you print from Aperture, in the print dialog under the Rendering section
when you open the Color Profile you can select Printer Managed.
Once you set it to Printer Managed you'll see the warning change from Turn off in Printer to Turn on in Printer
Might be worth a shot if you haven't try it yet.

Sudden MTS File Issues

I have been editing MTS files (AVCHD) from a Panasonic GH2 (Some hacked some stock firmware) for over 2 years with little to no issues. I am using the CS5.5 Master Collection, Premiere Pro in this case, on a 3 year old Sager laptop (64-bit, i-7 720qm, 8GB RAM, 2 internal HDDs, nVidia GeForce GTX 285M). I am not sure if I am having hardware issues or a corrupt file but something is not right.
I am now in the middle of a project and all of the sudden my computer is VERY sluggish and it takes minutes before things update (such as scrolling in my timeline to a different frame) and sometimes it just freezes up all together. There is also an issue (could be related) with the second set of spanned clips (detailed below) from this project.
The timeline is DV 24P widescreen since it is going to DVD and also uses footage shot from a DVX100b for cutaways. The GH2 footage was all shot with stock firmware 1.1 at 24H, all shot on one day and the first recording time was just shy of an hour, then about 20 minutes and then another for about an hour. This produced 3 mts files for the first section, 1 solo file for the short section and 4 files for the last long section. I copied the whole card to my D drive without altering any of the folder structure like a good boy. I brought in the clips to the project window and had no issues with editing the first hour section. I will say that I did not use the media browser as I have learned recently is the preferred way to import these clips. For the last 2 years I have dragged and dropped using the windows explorer window and have not had any issues until now. I have dealt with spanned clips, a music video hat required over ten video tracks and much higher bit rates so I am not sure what the trigger is for these issues. What is odd about the second longer clip is that when the first clip is dragged in to the timeline( 00004), it only brings that clip, not the others that should be attached. The first section worked but not this one. And all of the files that follow this clip are numbered differently but look identical to (00004) when dragged to the timeline. They all appear normal in explorer (smaller clips that should be spanned together) so the footage is in tact, just not in PP.
I experimented a little and copied clip 0005 into it's own folder, dragged it in and it then displayed properly (not a copy of 00004). The sluggish issue is still there so I am not ready to just grin and bear it with this workaround. I also experimented by creating a brand new project, copying the original footage from my archive drive (never imported into a timeline so no xmp files) into a new folder and used media browser to bring in the footage. It didn't show clips 00005 and up since the media browser is only supposed to show the first of the spanned clips but it was still only 24 minutes long and obviously not including the rest of the clips. MEdia browser recognizes these clips are supposed to be together, but PP is seeing them all as copies of 00005.
I will greatly appreciate any opinions but bear in mind that I have used this same workflow on this same system for over 2 years. The only variable is that these spanned clips may be slightly longer than I have used in the past but not by much. I really don't know if there is a peice of hardware malfunctioning, if the clip is somehow corrupt or if I am missing something obvious.
What coulod cause this sudden change in performance? Would editing with a proxy help? Should I convert this trouble clip to a different format? Am I asking too much of my system? Are there ways to check if my computer is functioning properly?
Thanks in advance for any insight and for reading this rather lengthy explaination.
Cole

I wanted to give a quick update on this MTS file issue. I was able to get my system back to normal by isolating the trouble files in their own folders outside of the "Private" folder(the actual source files, not in the premiere project). I copied the first clip of the group into a folder by itself and the last 3 clips into another folder. I deleted the originals from premiere and imported (dragging and dropping from windows, not using media browser) the isolated files and they worked fine. Obviously they were now 4 independent files that I had to place side by side in the timeline but they lined up and there is no more lag in the system and there are no more duplicate files.
Far from conventional but it has me editing again and I didn't have to buy a new computer to be back in business. I can only guess that something glitched when it was conforming and it wouldn't recognize the spanned clips.
A special thanks to Eric at ADK for offering some suggestions that I fortunately didn't have to try.

Setting up old Aperture File with my new Macbook Pro?

Hello:
I installed Aperture and have my old Aperture File on an external drive. I can't seem to figure out how to get this file over to my Aperture now on my laptop.
I also tried restoring from the Vault and for some reason not all the images in the display tab under the main window appear.
Any suggestions?
Thanks

or did you want to move the library from the external to the internal ???
if the latter, just copy it over to where you want and then double click from there to open and make default library ...

Oracle 11g - External Table/Remote File Issue?

Oracle 11g - External Table/Remote File Issue?
=============================
I hope this is the right forum for this issue, if not let me, where to go.
We are using Oracle 11g (11.2.0.1.0) on (Platform : solaris[tm] oe (64-bit)), Sql Developer 3.0.04
We are not allowed to put files on the CSV file system (Server A), where DB instance is running. We are able place CSV files on another server(Server B), where DB instance is not running.
We are trying to use oracle external table to load text files in .CSV format.
How do we create a Directory (Create Directory) on Server A DB to point to File system of Server B?
Is it feasible?
Any idea?
Thanks in helping.

The Solaris DBA should be able to mount the filesystem for you. Either that or you have to get creative transferring the file like this;
http://www.linkedin.com/groups/Getting-creative-external-table-preprocessor-140609.S.50474382?qid=ba673ce4-c4bb-40c5-8367-52bd2a2dfc80&trk=group_search_item_list-0-b-ttl&goback=%2Egmp_140609
Cheers
David

Lock Box File issue

I in the process of trying to test the lockbox upload and I was hoping someone could help me on this file issue.
the bank is providing the file as below for the "6" and the "4" record
620000100000480351220002470375406600000000014936CONCISYS INCORPORATE20111026
42000016019                     901293890        0000048035
my issue is I cannot get SAP to match the invoice number becuase of the spaces.     If I remove the spaces from the fil SAP will l match the invoice and clear the invoice. The bank is giving me the file in a Fixed Length format.
I have also tried the file this way
620300100000455000759116030755701208000000279048SIGNICAST           20120117
4203001601900000018000606470000045500
sap does not like the extra "0" in the fields.
I am indicating the file is a BAI2.
Any insight would help.

Hi,
If your file is in BAI2, this is the format, For Record type 6 :
Here for example the Check total amount is 15670.89
Data Type     Length     Description
NUMC     1     Record Type for Lockbox     6
NUMC     3     Batch Number for Lockbox (Bundle Number)     001
NUMC     3     Batch Item Number for Lockbox     001
NUMC     10     Remittance Amount (Check total Amount) for Lockbox     0001567089
CHAR     9     Remitter Identifier 1: Transit Routing Number for Lockbox (Customer' bank transit routing number)     111000614
CHAR     10     Remitter Identifier 2: Account Number for Lockbox (customer bank account number)      0000000000
NUMC     9     Check Number     000014801
CHAR     35     Data Element Type CHAR Length 35     ENERFLEXENERGYSYSTEMINC
For above example the record type 6 should be:
600100100015670891110006140000000000000014801ENERFLEXENERGYSYSTEMINC
And for Record type 4:
For below mentioned example:
Invoice number is - 1800000001 (But total character space is 16, as this field is CHARACTER in nature so we will add 0's at the end)
Invoice amount - 15670.89
Deduction amount - 0
Data Type     Length     Description
NUMC     1     Record Type for Lockbox     4
NUMC     3     Batch Number for Lockbox (Bundle Number)     001
NUMC     3     Batch Item Number for Lockbox     001
NUMC     1     Type of Overflow(Recd Type 4 Still Belongs to a Recd Type 6)     6
NUMC     2     Sequence Number - Serial Number of Record Type 4     01
NUMC     1     End Indicator ('9' the Last Record of a Type 4 Series)     9
CHAR     16     Invoice number     1800000001000000
NUMC     10     Payment Amount     0001567089
NUMC     10     Deduction amount     0000000000
CHAR     3     External Reason Code for Payment Differences     000
CHAR     30     30 Characters
The record 4 should be:
40010016019180000000100000000015670890000000000000
Assuming that its a first and last record in 4, that means 1 invoice and 1 check only.
Sometimes instead of using zeros bank uses space, the choice can be yours. You can tell the bank that you want zeros instead of space. I am also working on Lockbox and already did several testing by creating mock files. Create your own mock files and see how your system is responding. Then ask bank to follow the same.
For rest of the records like RT 1, 2, 5, 7, 8, 9, you will get the standard BAI2 format from SE12 - Database - FLB01, FLB02, FLB05, FLB26, FLB24, FLB07, FLB08, FLB09. Create some FI invoices in B70 and create your mock files using the standard BAI2 format. upload the file using FLB2 and test it. Test with different scenarios like within tolerance, w/o tolerance, with reason code etc
Thanks
Meha

Aperture file tripled in size after importing iPhoto

My iPhoto folder is 43GB and contains 20K images. When I imported into Aperture my aperture file grew to 120 GB. I deleted the albums in aperture which contained duplicate files, but my aperture file is still 120GB. Why is this and how can I get it down to 43GB. BTW, my aperture library shows 20K images so I don't understand why my file size is so large. Thanks.

what type of files ???
do you have previews turned on ???
what size and res of previews ???
it is possible but a 300% increase is not likely ...
what is telling you 120GB ???
Message was edited by: tidysteve
btw ... if you use a managed library it will never be the same size as all your photos ... always bigger ... thumbnails, sidecar files, previews, etc all take up space ...

Cant install PSE 11 shared files issue?

Hi - I cant seem to install PSE 11 as I keep getting shared file issues. Ive managed to work my way into the manual error log and its saying this - Any ideas please? Please go slow I am so not technical at all!
Thanks
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
Visit http://www.adobe.com/go/loganalyzer/ for more information
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
START - Installer Session
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
RIBS version: 3.5.8.0
Win OS version: 6.1.1.0 64 bit Type: 1
::START TIMER:: [Total Timer]
CHECK: Single instance running
CHECK : Credentials
Load Deployment File
Create Required Folders
Assuming install mode
Looking up install source path
Sync Media DB ...
::START TIMER:: [Sync Media DB]
Pre check media db sync
End of Pre check media db sync. Exit code: 0
:: END TIMER :: [Sync Media DB] took 247.39 miliseconds (0.24739 seconds) DTR = 371.882 KBPS (0.363166 MBPS)
Ready to initialize session to start with ...
::START TIMER:: [CreatePayloadSession]
-------------------- BEGIN - Updating Media Sources - BEGIN --------------------
Updated source path: C:\Users\Nina\Adobe Photoshop Elements 11\PSE 11\ElementsSTIInstaller
Updating media info for: {0449467E-102A-4514-9F4D-91BCEE129390}
Ignoring original data since install source is local
Type: 0, Volume Order: 1, Media Name: Adobe Photoshop Elements 11
Path: C:\Users\Nina\Adobe Photoshop Elements 11\PSE 11\ElementsSTIInstaller\payloads\ElementsCameraRawProfile7.0All-160512123011\Install.db
Updating media info for: {2EBE92C3-F9D8-48B5-A32B-04FA5D1709FA}
Ignoring original data since install source is local
Type: 0, Volume Order: 1, Media Name: Adobe Photoshop Elements 11
Path: C:\Users\Nina\Adobe Photoshop Elements 11\PSE 11\ElementsSTIInstaller\payloads\AdobeXMPPanelsAll\Install.db
Updating media info for: {3A8D4A3A-5E08-4E33-8831-50CB4DC101E6}
Ignoring original data since install source is local
Type: 0, Volume Order: 1, Media Name: Adobe Photoshop Elements 11
Path: C:\Users\Nina\Adobe Photoshop Elements 11\PSE 11\ElementsSTIInstaller\payloads\ElementsCameraRaw7.1All-x64\Install.db
Updating media info for: {5A73BC84-244A-48B4-ADDB-99CE9E2DBBE7}
Ignoring original data since install source is local
Type: 0, Volume Order: 1, Media Name: Adobe Photoshop Elements 11
Path: C:\Users\Nina\Adobe Photoshop Elements 11\PSE 11\ElementsSTIInstaller\payloads\ElementsCameraRaw7.1All\Install.db
Updating media info for: {98CE8819-87AA-4814-8167-ADDDD513485F}
Ignoring original data since install source is local
Type: 0, Volume Order: 1, Media Name: Adobe Photoshop Elements 11
Path: C:\Users\Nina\Adobe Photoshop Elements 11\PSE 11\ElementsSTIInstaller\payloads\PSE11STIInstaller\Install.db
Updating media info for: {D1B83970-7269-48BE-8B0E-5120D9327E52}
Ignoring original data since install source is local
Type: 0, Volume Order: 1, Media Name: Adobe Photoshop Elements 11
Path: C:\Users\Nina\Adobe Photoshop Elements 11\PSE 11\ElementsSTIInstaller\payloads\AdobeAPE3.101-mul\Install.db
Updating media info for: {F6F5021E-0548-43C1-82CC-C5C7A6906585}
Ignoring original data since install source is local
Type: 0, Volume Order: 1, Media Name: Adobe Photoshop Elements 11
Path: C:\Users\Nina\Adobe Photoshop Elements 11\PSE 11\ElementsSTIInstaller\payloads\ElementsCameraRawProfile7.0All\Install.db
-------------------- END - Updating Media Sources - END --------------------
Supported RIBS version range: [0.0.66.0,3.5.8.0]
[    3392] Tue Jul 02 20:12:47 2013 ERROR
Payload {98CE8819-87AA-4814-8167-ADDDD513485F} of version: 4.0.19.0 is not supported by this version: 3.5.8.0 of RIBS
Payload {D1B83970-7269-48BE-8B0E-5120D9327E52} of version: 4.0.19.0 is not supported by this version: 3.5.8.0 of RIBS
Unsupported payload versions included
[    3392] Tue Jul 02 20:12:47 2013 INFO
:: END TIMER :: [Total Timer] took 326.856 miliseconds (0.326856 seconds) DTR = 293.707 KBPS (0.286824 MBPS)
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 3 error(s), 0 warning(s)
ERROR: Payload {98CE8819-87AA-4814-8167-ADDDD513485F} of version: 4.0.19.0 is not supported by this version: 3.5.8.0 of RIBS
ERROR: Payload {D1B83970-7269-48BE-8B0E-5120D9327E52} of version: 4.0.19.0 is not supported by this version: 3.5.8.0 of RIBS
ERROR: Unsupported payload versions included
Search the same string above to find when the error occured.
Exit Code: 21 - payloads version is not supported by installed version of RIBS
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
END - Installer Session
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*

I have come across this on another forum but I dont have any idea how to do this? Can someone help please?
So resolve this TIME consuming problem, i had another look at that support page and this is what i did to fix it Thank you for your help 99jon for the link.
Copied the elements folder to the root of the HD, then renamed the folder with the installer files contained within to c:\PSElements9Installer then ran the setup.exe as administrator and hey presto, it worked and fully completed the install grrrrr.
Cheers people of the Digital World, ive now relieved my stress
Was this helpful?Yes NoSubmit
Reply
|
Mark as:
1 posts
11-Apr-2013
Currently Being Moderated
3. TangAdmin,
11-Apr-2013 17:04   in reply to Digital Controller
Report
    Had the same problem with PSE10 Copying it to kthe root of c and renaming it to PSElements10Installer Worked perfectly.
thanks to all involved
Was this helpful?Yes No

Managing Large Aperture file backup and export

I have a 250GB Aperture library file with 30,000 photos on my Mac Book Pro with a 500GB Solid State driive. I bought a 1TB GoFlex external drive with FireWire 800. I copied the entire 250gb Aperture file to the drive. After 24 hours the file size changed to 180GB? I exported the Masters (full size) from Aperture to the external drive in a separate file that is 60GB as a second backup. I tried to "RELOCATE MASTERS" to the external drive, but it did not reduce the Aperture Libray size by anything. I also exported all of the Versions (full sze) from Aperture to the external drive as a third backup. I am terrified of losing my work which is now all backed up in three forms on a single hard drive. What do I do now?
I must decide whether to use the full Aperture.library on the external drive.. which is HUGE and will only get more bloated.
or import the versions with metadata into a new library but manage previews better.
or what?
Thanks

First, make and confirm two back-ups of your Library and of any Referenced Masters. Your originals and each of your back-up sets should be on separate spindles. Move one of the back-up sets off-site. End of terror: it is now virtually impossible to lose any work you've done up to the point you made the back-ups.
A good set-up to end up with is this:
- Library on SSD
- Masters older than 60 days on external FW800 drive (these will be Referenced Masters; let's call this drive your Referenced Masters Drive).
- - - These constitute a complete Aperture "set".
- Back-up Library _and_ Referenced Masters to _another_ external drive (1st Back-up Set)
- Back-up Library _and_ Referenced Masters to a third external drive (2nd Back-up Set)
- Keep one Back-up Set off-site. Never have all three Sets in the same location.
- Import new files into Library as Managed Masters. Set Previews to be the size of your laptop screen.
- Every 60 days, using a Smart Folder to identify Images with Managed Masters older than 60 days, relocate those Managed Masters to your Referenced Masters external drive
- Back-up regularly
The above is just a template: adjust to suit. (Added:) How you get there will depend on where you are. I didn't untangle your post.
When Images' Masters are off-line (you laptop is not connected to your Referenced Masters drive), you will be able to do all metadata administration, including moving Images, etc. You will not be able to make Adjustments, Export, or Print. (But you can drag the Preview out of Aperture and use it.)
Message was edited by: Kirby Krieger

HOW DO YOU CONVERT IPHOTO 8.1 TO APERTURE FILE FORMATT

how do you convert iphoto 8.1.2 photos to aperture file formatt?

I believe this is still possible if the iPhoto library has not been up graded.
No joy, Frank. This is what I get, when I try to import an older iPhoto Library into Aperture 3.4.3 using "File > Import > Library":
Aperture 3.4.x insists on the library being converted to 9.4.x. To be able to import earlier iPhoto Libraries you would have to fall back on Aperture 3.2.x; temporarily install a second, older Aperture version, create a new Aperture library with this version, import the iPhoto Libraries, then open this Aperture library in Aperture 3.4.3 to convert it to a current version.
bertpa, how many iphoto photos are we talking abourt? If you are having several iPhoto libraries with thousands of edited photos, it really would be worth it to upgrade to iPhoto 9.4 to convert your libraries. iPhoto 9.4 will convert your library to a format with Master-version pairs like aperture uses. If you import this to Aperture, you will be able to import each edited image as a single image with two versions (original and edited)- importing from previous iPhoto versions you would be importing each edited image as two separate images - an edited image and the original. This would be wasteful, if you have many photos in Aperture, and it would cause a lot of additional work to get these duplicates sorted out. But if you only have a handful of iPhoto images, launch iPhoto and use the "File > Export" command to export your photos from iPhoto to a folder. You will have to do it twice - once to export the originals and once to export the edited versions. Then import your exported iPhoto photos into Aperture.
Regards
Léonie

Aperture file issue

Similar Messages

Maybe you are looking for