Aperture Import Folder Structure

Discussions, questions, comments and suggestions regarding Capture One PRO, Capture One PRO(For Sony), Capture One DB and Capture One Express(For Sony) 8.x.

Aperture Import Folder Structure

Postby rjackb » Sat Apr 18, 2015 11:41 pm

I have successfully imported about 11,000 referenced images from my Aperture library into Capture One 8.2.1. After the import, my Aperture projects show up as Capture One collections and my folders show up in a folder tree. The problem is that when I import a brand new set of images into a new folder, the folder shows up in a separate tree that looks identical except for a few icons. I really don't want to have to separate folder tree but rather add on to my existing tree. I'll try indicate what I am seeing below? Thank you.

Code: Select all
v <icon> Macintosh HD
   v <icon> Users
      v <icon> Jack
         v <icon>Desktop
            v <icon> Images
               v <icon>Nikon D300
                  <icon>2015-04-18     <- new folder added but want in tree below
v <icon> Macintosh HD
   v <icon> Users
      v <icon> Jack
         v <icon>Desktop
            v <icon> Images
               v <icon>Nikon D300
                  <icon>2005-01-01     <- folder that I imported
                  <icon>2005-01-02     <- folder that I imported
                  ... many more folders imported from Aperture ...
rjackb
 
Posts: 5
Joined: Sun Feb 22, 2015 8:40 pm

Re: Aperture Import Folder Structure

Postby Paul_Steunebrink » Sun Apr 19, 2015 8:39 am

I am afraid I do not get the point yet. Maybe you can post a screenshot? First thought was that you can import to any folder you like.
Best regards,
Paul E. Steunebrink, Image Alchemist (website All about Capture One), Capture One trainer
User avatar
Paul_Steunebrink
Certified Professional
Certified Professional
 
Posts: 9456
Joined: Tue Feb 06, 2007 8:49 pm
Location: The Netherlands

Re: Aperture Import Folder Structure

Postby rjackb » Sun Apr 19, 2015 6:29 pm

How do I post a screenshot? I was going to but couldn't figure out how so I opted to try to reproduce the look. Looking at the Capture One catalog with a hex editor, it appears that file paths that are imported from Aperture are stored a bit differently than from an import which might account for the display of separate trees.
rjackb
 
Posts: 5
Joined: Sun Feb 22, 2015 8:40 pm

Re: Aperture Import Folder Structure

Postby RedRobin » Sun Apr 19, 2015 7:04 pm

Join a free online image host such as Photobucket and upload your image/screenshot there and then copy and paste the code in your post here.

The code should start [ img ] and end [ /img ].
Robin Procter - Amateur Wildlife Photographer - https://www.flickr.com/photos/114775606@N07/
CaptureOne 12 on Mac OS 10.13.6
RedRobin
 
Posts: 125
Joined: Mon Apr 13, 2015 11:54 am

Re: Aperture Import Folder Structure

Postby SFA » Sun Apr 19, 2015 8:16 pm

NN635602308421234413UL wrote:How do I post a screenshot? I was going to but couldn't figure out how so I opted to try to reproduce the look. Looking at the Capture One catalog with a hex editor, it appears that file paths that are imported from Aperture are stored a bit differently than from an import which might account for the display of separate trees.


I would think that the easiest course of action here would be to ask the question in a Support Case.

It is possible that the Aperture Catalog Ingestion is thought of as a unique "copy" (for whatever reason) and so is intended to be kept separate within the catalogue. I don't know, I'm just speculating on how one might approach such a Transfer of data from one system to another.

Asking those who should certainly know seems to be the best and fastest way to get an answer and perhaps a way to work with how you want things to be in the future.

HTH.



Grant
Last edited by SFA on Sun Apr 19, 2015 9:07 pm, edited 1 time in total.
SFA
 
Posts: 5993
Joined: Tue Dec 20, 2011 9:32 pm

Re: Aperture Import Folder Structure

Postby rjackb » Sun Apr 19, 2015 8:46 pm

Following is a screenshot. The first folder tree contains a new folder that I imported directly into Capture One. The second folder tree is the one created by the Aperture import. Notice that the icons are plain in the second tree but look like standard Mac icons in the first tree.

Image

If the image doesn't make it, this is the URL:

https://www.flickr.com/photos/22959801@N05/17202487531/
rjackb
 
Posts: 5
Joined: Sun Feb 22, 2015 8:40 pm

Re: Aperture Import Folder Structure

Postby rjackb » Sun Apr 19, 2015 11:54 pm

I did find a workaround for the duplicate folder trees although it involves quite a bit of work. If I go to the first folder tree, right click, "Add Folder...", and choose one of the imported folders then Capture One will add the folder to the first tree. I can then select the same folder in the second tree, select all of the images in that folder, drag them to the same folder in the first tree, and delete the folder from the second tree. All adjustments, etc. picked up from Aperture by Capture One are retained with the images.

I realize that the Aperture Import functionality is labeled beta but would like to ask that it be modified to store file paths the same whether from an Aperture Import or from a new import (or however else the problem can be corrected) so as not to create multiple folder trees for what is actually a single physical folder structure. Thank you.
rjackb
 
Posts: 5
Joined: Sun Feb 22, 2015 8:40 pm

Re: Aperture Import Folder Structure

Postby RedRobin » Tue Apr 21, 2015 9:21 am

Does this tutorial video about importing an Aperture library help?....

https://www.youtube.com/watch?v=IylO2Hxegkg&feature=youtu.be

I haven't imported mine yet.
Robin Procter - Amateur Wildlife Photographer - https://www.flickr.com/photos/114775606@N07/
CaptureOne 12 on Mac OS 10.13.6
RedRobin
 
Posts: 125
Joined: Mon Apr 13, 2015 11:54 am

Re: Aperture Import Folder Structure

Postby rjackb » Thu Apr 23, 2015 11:42 pm

I resolved this issue by modifying the Capture One catalog to store the file path root and path names of paths imported from Aperture similar to how they are stored when new images are imported from a card reader. The catalog is a sqlite3 database so it was simple for me to do (I'm a former software developer). Now I have only a single tree of folders.
rjackb
 
Posts: 5
Joined: Sun Feb 22, 2015 8:40 pm

Re: Aperture Import Folder Structure

Postby PaaS » Fri Apr 24, 2015 10:43 am

rjackb wrote:I resolved this issue by modifying the Capture One catalog to store the file path root and path names of paths imported from Aperture similar to how they are stored when new images are imported from a card reader. The catalog is a sqlite3 database so it was simple for me to do (I'm a former software developer). Now I have only a single tree of folders.


Worth report a bug to PO? Everyone was/is/would-like-to-be a developer!! No one wants to be Tester - because 'we' are bad ppl - we show developers, that they're wrong ;)
:twisted:
PaaS
 
Posts: 12
Joined: Sun Apr 12, 2015 5:39 pm

Re: Aperture Import Folder Structure

Postby SFA » Fri Apr 24, 2015 12:36 pm

PaaS wrote:
rjackb wrote:I resolved this issue by modifying the Capture One catalog to store the file path root and path names of paths imported from Aperture similar to how they are stored when new images are imported from a card reader. The catalog is a sqlite3 database so it was simple for me to do (I'm a former software developer). Now I have only a single tree of folders.


Worth report a bug to PO? Everyone was/is/would-like-to-be a developer!! No one wants to be Tester - because 'we' are bad ppl - we show developers, that they're wrong ;)
:twisted:


Except that in this case as I read it the observed dislike relates to a dedicated free utility put together to help people who wanted to try out Capture One when Apple, in their wisdom, announced that they would stop supporting Aperture.

So any change is, surely, a Feature Enhancement Request and can be proposed as such through the Support Case system.

That woould apply to both the conversion utility an the C1 application.

Hacking database structures is all very well for those with the skill sets to do so but more suited to Open Source activity. It should also, assuming it is not disallowed by the terms of the use licence, be declared whenever techical support is requested for the avoidance of any confusion.

In my opinion.


Grant
SFA
 
Posts: 5993
Joined: Tue Dec 20, 2011 9:32 pm

Re: Aperture Import Folder Structure

Postby PaaS » Fri Apr 24, 2015 5:36 pm

SFA wrote:...
Except that in this case as I read it the observed dislike relates to a dedicated free utility put together to help people who wanted to try out Capture One when Apple, in their wisdom, announced that they would stop supporting Aperture.


Sorry, not sure what are you talking about. Based on what is that assumption? If the PO - borrowed (politely said) some mechanism for importing Aperture library - and I as customer paid for C1P - thus the PO support is the right place where to demand...
I honor OpenSource very much and I strongly disagree, that one (maybe import module) community should do the work and the others (PO) should collect $$.

As far as I understand, the problem is NOT SQLite, but the form of data (wrong path) which are stored there - the responsible for them is application (C1P, thus developer from PO).

Feel free to correct me if I am mistaken.
PaaS
 
Posts: 12
Joined: Sun Apr 12, 2015 5:39 pm

Re: Aperture Import Folder Structure

Postby SFA » Fri Apr 24, 2015 5:57 pm

It's a free utility with a specific purpose (and probably a short life) to help Aperture users migrate from a product Apply decided not to support - leaving their valued customers to look for alternatives it seems.

We have all paid for it, one way or another, but I am not a Mac or Aperture user so should I get a refund of some sort? The code is of no use to me at all and, presumably, took resources away from work from which I (and all other non-Aperture users) might have benefited.

Sure, placing a request for an enhancement through Support is fine and it would then be up to Phase to decide if the effort was useful enough to enough people to make sense as a development project. Feeling that you can make a demand related to a free add-on utility is a different matter. Had you paid for it you might have a more reasonable case ... perhaps Apple could offer you some financial help as compensation for the wasted years of effort you have had with Aperture? They could surely afford it.

I think you have a rather odd view of what Phase One have set out to offer people and what follow-on responsibility they may or may not have being driven by a group of users with very specific interests not necessarily required by other customers.


Grant
SFA
 
Posts: 5993
Joined: Tue Dec 20, 2011 9:32 pm

Re: Aperture Import Folder Structure

Postby PaaS » Fri Apr 24, 2015 7:26 pm

SFA wrote:It's a free utility with a specific purpose (and probably a short life) to help Aperture users migrate from a product Apply decided not to support - leaving their valued customers to look for alternatives it seems.
...
Grant

Grant - still don't understand your point. What is free utility? C1P and File/Import Catalog/Aperture Library/ ??
if you think so, you're then wrong. In case customer paid for C1P, thus paid for background color, help, everything inside. I didn't pay YET - but you can be sure, once I finish my choice and realize, that I'll pay - I won't be satisfied with buggy SW. In case I use that built-in function - then I expect no mismatch of my data. No matter who is developer behind - is community or PO builder machine. I bought from PO, thus expect support from them - unless stated in terms otherwise.
So still don't understand the point why I should claim anything from Apple. They did they work, decided not to continue - their choice. They offered me support for certain time.
Why this should be wrong to claim support from PO when I bought SW? (imaginary - I still didn't yet).
PaaS
 
Posts: 12
Joined: Sun Apr 12, 2015 5:39 pm

Re: Aperture Import Folder Structure

Postby SFA » Fri Apr 24, 2015 11:37 pm

PaaS wrote:
SFA wrote:So still don't understand the point why I should claim anything from Apple. They did they work, decided not to continue - their choice. They offered me support for certain time.


So they took your money for some years, got you committed to the Aperture way as the only way and then dropped you when they decided to take a different route that you do not like. No compensation from them for all of the time you spent adopting to their concepts only to have them abandon you.

Now you look for Aperture from a different vendor but don't find an exact match.

So you expect any potential new vendor to change what they do to be more like Aperture just because you want it to be that way. And if their design is currently different you call that a bug and suggest that they must change what they do or you will claim that the software is "buggy".

So, the new vendor may or may not choose to adopt the Aperture design that you want them to adopt - "their choice" as you said about Apple and the Aperture decision. So why not just accept it for what it is, as you seem to have done in the case of Apple, and simply ask if a change to be implemented rather than make remarks about "bugs"?



Grant
SFA
 
Posts: 5993
Joined: Tue Dec 20, 2011 9:32 pm

Next

Return to Capture One 8.x Software



Who is online

Users browsing this forum: No registered users and 8 guests