Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

moving files/directories between Macs

Comments

8 comments

  • Permanently deleted user

    Honestly, you should probably be using Sessions and not a Catalog. (but that may depend on more details that are unknown so far).

    When you say the "directory contains a .catalog file and RAWs and TIFs" .... are those raws/tiffs INSIDE the catalog "package" or are they in their own set of folders?  (This is determined by how you import them). 

    If they are in their own set of folders, the folders are probably named differently (e.g the volume names are different on the two machines perhaps?... and thus the paths are slightly different).   This video will show you how to "re locate" your raws on the target machine https://www.youtube.com/watch?v=lZ3gL893TaM

    But if you plan on copying image adjustments and raws around, I think a Session makes more sense. 

    0
  • Jill Kuchar

    Thanks.

    I managed to 'connect' with the files, but I could only do this one file at a time. When I clicked on a folder, "Locate" stayed greyed out also the link shows both being done.

    I've always used catalogs not sessions. Not sure why nor what the real differences are.

    Thanks for you assistance.

     

     

    0
  • Permanently deleted user

    A session is sort of an all inclusive directory with everything beneath that one directory. Sessions also "auto recognize" any new images put in the \capture folder which means you never need to import, just put images in there and it will recognize them.

    • Each session has its own folder and its own database . A catalog can be spread across multiple drives and it has one database for all images in the catalog. So typically you might have a catalog of 50,000  to 150,000 images with the database on an SSD drive and the raw files on an external drive or some other drive. A session on the other hand, is often used for a "project" or assignment or whatever you want to call it. But sessions can also be huge if you want them to be.
    • To copy a session between machines, you simply copy the session directory to the other machine and you're done.  When you try to copy a catalog to another machine, then you often run into the "locate" problem you ran into.

    I look at it as there are three basic ways to use C1

    1. SESSIONS ONLY: Some people only use sessions. They will create a new session for each photo shoot or project (say a "headshot session" or "trip to Barcelona".). They put the session folders in a folder structure on their hard disk or RAID array. Maybe they have a \YYYY (year folder) and beneath that they put a \YYYYMM folder and beneath that every Session for that month. But you can do it anyway you want.   The drawback... is that cannot easily search across piles of Sessions, so there is no overarching view of all your images.  Sessions are nice when you travel as you can put the images captured on the trip into a Session on a laptop and edit to your heart's content.  Sessions are also the best way to "tether" where you shoot and the images go right into C1 on a computer.
    2. CATALOG ONLY: This is more like Lightroom. You take images from your SD (or whatever) card and you ingest them, putting them in a folder on a hard drive (your choice as to where that is) and repeat every time you shoot. If you don't "import" then they won't be in your Catalog. (A Session doesn't need to import as it auto-recognizes all images in the \Capture folder). The challenge is, as you get more and more raw images, many people outgrow their internal hard drive and need something bigger (external drive, a RAID array etc) to put their raws.  Also, people want to edit on a big screen  that is color calibrated etc, so they may choose a desktop type computer to host their catalog (which is obviously inconvenient for travel).  This makes catalog harder to use on the road.  Catalogs are difficult to move between computers (as you found out) and not as convenient for travel.  
    3. SESSIONS w/ CATALOG: This is what I do. I shoot professionally at times and also personally. I shoot each paid job with a Session as well as some of my personal stuff if I need mobility. I generally create a Session on my laptop, process the images there.  To put it in my catalog, I simply copy the Session folder off my laptop to my desktop ( in its hard drive's raw image folder structure) ... the same structure where I put all my non-Session images, To get those images into the catalog, I select "import Session" from the menu. At that point, the edits done on the laptop are incorporated into the Catalog  and I do any further edits from there. Thus, all my images are in a catalog whether they started in a Session initially or not... and I can search across years of photos. 

    The main benefit of the catalog is that you can search across images across multiple years. I have a smart album, for example,  which automatically filters for images of one of my sons which have 3 stars. Some people never feel the need to do searches like that; perhaps they are professionals who just have Sessions of all their commercial projects in folders that include the name of the customer, and thus they can find their stuff instantly. They may use the operating system's search to find images as well.  Others may use Sessions only and then process the best images to JPG or TIFF and put them in another place where a different catalog or DAM system is used (IDimager, iMatch, Photomechanic Plus etc. ...)

    Anyway that's sort of where I see it. I just think many people start with catalogs without understanding where Sessions could fit in.  Walter, who posted before,  has his own youtube channel with lots of C1 videos here https://www.youtube.com/channel/UCKBjkW90hIN90n4-U-qFnfg

    Here's another youtube video I found which goes into depth about Sessions and Catalogs 

    https://youtu.be/Qk5jhTcKtXI

    1
  • Jill Kuchar

    I'm going to start by saying that my disappointment with Capture One, the product and the response from so-called 'service', is dropping by the day.

    This post was in response to an earlier one which I can no longer find on the forum to do with v21 files not redisplaying properly after there have been 8 or 9 layers in the file. I suspect it may have been deleted.

    As the problem first manifested with a TIF that I had created in v20, I thought the source of the 'bug' was related to v20 and a TIF as opposed to a RAW and first opened in v21.

    This original assessment was incorrect and it happens to any file: RAW, JPG and TIF where there are many actions and layers.

    At the suggestion of friends on this forum I opened a ticket.

    The treatment I have received since then has been unbelievably bad, especially from a European company where I generally expect a higher level of efficiency ad tested s/w. I was asked to send log files, but not the files themselves. The reason I opened this thread was because I copied a directory with problem files from this machine to another, both macs, but running different versions of the OS. The problem was consistent.

    I believe it took weeks until my bug was finally reported to R&D. I don't know exactly what problem was reported as the more I worked on more photographs, the more I honed into the source of the problem.

    I was told to just keep on using v20 (though I converted many catalogs already to v21 and thus could not go back). I was told that "this" was a known problem in v20 (though I never experienced it with the same files!) I was told the problem could take months to fix. I was to I could use a beta version to help the "company" solve the problem. I was the R&D people ahd a lot of work on their plate with other, more serious bugs -- something which took away all my confidence in the company releasing a 1/2 baked product. Yes, like the Americans, they too now seem to work on an annual release model, ready or not.

    I've really pretty much had enough of the company or at least the 'rep' with whom I'm dealing.

    What are other peoples' experiences with treating bugs?!

    Thanks

     

    0
  • Permanently deleted user

    Anyone having bad experience with the Technical SUpport ?

    Yes. Everyone.

    This forum has become a long martyrologue of bugs reporting - and unsolved issues...

    0
  • Jill Kuchar

    :-(

    The main reason I 'came' to C1 was because I thought European companies knew how to treat their valuable customers, and were not constrained to release bug-ridden programs in order to meet an annual money-making deadline.

    I can see they are no better than what I left behind. I feel I have been treated like an idiot because I found a legitimate bug. But the worst is, they even refuse to want to understand what is the bug! let alone fix it. This has gone on for over 2 months and for me at least, the product is useless.

    Am I the only one that runs with >8 layers and does lots of actions in each one?

     

    0
  • Permanently deleted user

    Nja .. What can we say ?

    No, they are no better than whoever you left.
    Actually for the moment, they probably are worse, as they became an independent company from Phase One.

    The most optimistic here think it is just a transition - we all hope so.
    But one thing is sure: revolt is increasing, and if they don't pay attention to the customers desires, these will quickly start leaving.

    I would say that many layers is not my usual work, but 2 or 3 are very common in jobs aimed to be printed, or Chromalux-printed.

    Keep hope and let's be some more patient before activating the ejection seat.

    0
  • Jill Kuchar

    Oh. I didn't realise they split with Phase One. :-(

     

    0

Post is closed for comments.