Exporting folder question

Piero Annoni

• 2019年11月17日 20:13

Hope I can explain my problem clearly.
Premise: I utilize C1 on the same session most of the time, just switch to a new one once a month (never liked how session works).

In facts: When editing a new project organized in its folder, prior starting the export process I have to, obviously, set a new export folder in the recipe "output position".

My question: When switching (often) to one project to another (hence, folders) in the developing process, I have, every time, to update the "output folder".
Could it be possible for C1 to save in its created folder "CaptureOne" (where all data are stored) also the correct output destination related to the project?? instead of keeping the latest one listed first?

thank you!
Piero

0

• 

  Robert Whetton

  • 2019年11月17日 23:24

  I use the same session all the time too. I just point at the new job folder in Library.
  
  For the Output location. I have Destination pointed at the drive I use for outputs and just put type the name of the sub folder in for each time I need to output.

  0
• 

  SFA

  • 2019年11月17日 23:39

  Piero,
  
  If you are working by Project why not have a new session for each project?
  
  If the Projects are Personal Projects you could then just keep adding to them month after month and let C1 allow you to filter by Month if required rather than start a new Session each month as you described.
  
  There are many options for grouping Output Files (e.g. By using EXIF field based Tokens) into their own folders when using Output Processing.
  
  It sounds like you are not currently able to use the benefits that C1 can offer using sessions or, perhaps, catalogue(s).
  
  
  Grant

  0
• 

  Piero Annoni

  • 2019年11月19日 10:35

  Thank you for your replies.
  Since I started using C1, several years ago, I have always found hard to switch to a new file organization in our hard drives based on the C1 Session method that adds several folders we actually do not need (catalogues even worse).
  I know of many users that behave in the same way, but I am not closed to try different methods if these helps to improve and speed up our workflow.
  For example, I have not understood what you are referring at in relation of this sentence:
  

  grouping Output Files (e.g. By using EXIF field based Tokens) into their own folders when using Output Processing

  
  I think this relates only to the naming of outputted files, but this is not what we are looking for, we just would like, when we go back to develop previous projects, that the output folder info has been kept and linked to the project.
  
  But I think the only way is to create Sessions for each job.
  Piero

  0
• 

  SFA

  • 2019年11月19日 10:44

  Piero,
  
  The Default folders are created simply for convenience.
  
  You do not have to use them at all but for managing a shoot as a session and especially for Archiving purposes putting the file inside a folder structure in the session folder structure (e.g. subfolders in the 'Capture folder' can make management much easier and very effective.
  
  If you are shooting tethered there are things you can so to set up a folder structure in advance of the shoot.
  
  If you are importing you can create sub-folders automatically during the import process. The mechanism is similar to that available for image file naming.
  
  I would offer some links but I have to go out right away. I will check back later to see if you have already discovered the information about them.
  
  Grant

  0
• 

  Piero Annoni

  • 2019年11月19日 19:59

  Thank you Grant for your time.. would be happy to check those links.
  
  Btw, I think I'll give it another try to Sessions, hoping will improve our projects organization.
  
  Piero

  0

投稿コメントは受け付けていません。