Camera counter numbers duplicate after crash . . .

Mark Langridge

• 2009年12月10日 12:56

I have this issue with 5.0.1 Pro that I'm trying to get to the bottom of . . .

I'm shooting tethered with a 1Ds Mk III. I have Capture One set to name the files as they come in with a name + camera counter. This works fine, but then sometimes after a crash the camera counter seemingly jumps back and I end up with duplicate file names that Capture One suffixes with a '1', of course, to differentiate it from the first file with that name. So I'll have, for example, a frame 101209-4567, and also a frame 101209-4567 1. Does anyone know how I can get around this?

Best

Lancton

0

• 

  Paul Steunebrink

  • 2009年12月10日 14:08

  For tethered shooting you can set (and reset) the camera counter manually. This option is staring you in the face but its a bit tiny. At the Camera tool tab, Next Capture Naming tool, click on the small triangle symbol at the right in the tool's title bar...

  0
• 

  Mark Langridge

  • 2009年12月11日 00:04

  Thanks, Paul.
  
  Mmmm . . . I know you can set the counter manually, but surely it's a bug in the program that it thinks certain frames have not been shot previously by the camera, when they actually have, no? In the heat of the moment, in the studio, after a crash, I don't have time to reboot, establish what frames have been transferred onto the computer already, where the camera counter is now at, then go into the program and manually set the capture number back to the relevant value. I want the camera counter to just keep going up, in order, nice and simple. Surely it's not right that Capture One is confusing it into jumping back to previously used counter numbers? Is there a workaround?
  
  Cheers

  0
• 

  Paul Steunebrink

  • 2009年12月11日 08:55

  Lancton,
  When the application closes gracefully, it stores the camera counter value in a file (preference file I think). This does not happen when it crashes (no time or not able to write). I suggest that you should focus on solving the crashing behavior. It is not uncommon during tethering with mkIII cameras (or USB connected cameras in general) due to a OS X issue with USB. This should have been solved in recent OS X updates. So which version are you running? And maybe you should ask Phase One for assistance on this one in a support case.

  0
• 

  Mark Langridge

  • 2009年12月11日 09:44

  That makes sense. As for focusing on the crashing behaviour . . . Erm . . .Me and many others, right?! I'll drop a line to support.
  
  Thanks for your replies.
  
  L

  0

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