D810 tethered file naming
Anyone else having problems with tethered file naming with CO8 and a D810?
No matter what I set in Capture One it still adds an extra digit to the end of the file name. This wouldn't be too bad but if I delete an image the new shot is replaced by the one I just deleted!
This continues until you can shoot enough pictures to out run the deleted shots. So if you delete 5 images, you need to shoot 6 new ones until you can see a fresh image! Far from ideal.
If anyone has a work around or fix let me know.
Oliver
No matter what I set in Capture One it still adds an extra digit to the end of the file name. This wouldn't be too bad but if I delete an image the new shot is replaced by the one I just deleted!
This continues until you can shoot enough pictures to out run the deleted shots. So if you delete 5 images, you need to shoot 6 new ones until you can see a fresh image! Far from ideal.
If anyone has a work around or fix let me know.
Oliver
0
-
What naming convention are you using ? 0 -
Yes I'm having the same problem shooting with my D810. When shooting tethered the next capture naming isn't advancing to the next number. It will keep repeating the same name/number followed by a 1 then a 2 etc. i.e. shot_name-14, shot_name-14 1, shot_name-14 2 etc. if I quit CO and restart the first new frame will advance like it should but any more will keep repeating the same name/ number. Tried several different naming formats i.e. Name 2 digit counter, Folder Name 3 digit counter but all do the same thing. In the Next Capture Naming window it will show the correct next name and number but doesn't use it.
My work around is to do a batch rename when completely finished with that shot but sure would be great to not have to do that.0 -
We're using "Name"-"3 digit counter". This is the same preset we used in CO7. We've tried recreating it but it doesn't seem to help. 0 -
I am having the same issue when exporting files in CO8
I set the naming convention as "file name"_"3 digit counter" but it exports as "file name_001 2", "file name_001 3" etc.etc.
I then have to do a batch rename to get the file names into the correct format.
Very frustrating!!!0 -
NN63... do you have the same problem where if you delete a shot the next new one gets overridden by the deleted one? 0 -
Exact Same problem for me on our d810. BTW we are using this camera with the Schneider 90mm tilt-shift... very impressive. 0 -
This appears to be a bug related to the naming tokens when shooting with a D810. I've reported to R&D so we can get to work on a solution. 0 -
I admit I'm a bit off topic, but did any of you have trouble teathering using USB3 while shooting quickly. I was using a D800E w/ Capture 7.23. I posted here because I was wanting to know if CO 8 may have fixed the issue. BTW Plugging to a USB 2 port fixed the disconnection issue. 0 -
[quote="DigiTim2" wrote:
I admit I'm a bit off topic, but did any of you have trouble teathering using USB3 while shooting quickly. I was using a D800E w/ Capture 7.23. I posted here because I was wanting to know if CO 8 may have fixed the issue. BTW Plugging to a USB 2 port fixed the disconnection issue.
Although I can not speak for your setup, more often than not the issue you describe is related to hardware, cable in particular. Short cable of best quality and/or repeater is necessary.
The USB 3 protocol is much more prone to fluctuations in signaling, leading to disconnects when shooting quickly. That explains that you do not have the issue when using USB 2.0 -
Thanks Jon, I look forward to an update.
DigiTim2, we have no problems on model shoots etc when shooting fast with USB3 cables. We use the orange cables from Tether Tools with active repeaters. It's lighting quick on a new iMac with USB3 ports. My older mac needs USB2 cables or it loses connection.0 -
Just in case anyone was hoping the CO8.0.1 update would fix this, it doesn't. Fingers crossed for the next update. 0 -
This seems to be quite a common problem. I'm having the same issues with a d810 and a short, good quality cable 0 -
We are aware of the issue, that only seem to affect the Nikon D810 specifically. We looking into a fix for the issue, but at this early stage, I cannot comment any further.
Thank You for Your patience!0 -
It's only file naming. It's not like it can mess anything up.
First - Very slow D810 RAW file support
Second - No tethered D810 support in C1 Pro 7.2.x ???
Third - D810 file naming issues in C1 Pro 8.0.1
So in other words, D810 users just need to shoot to cards, no big deal... wtf.
Guys, 3 awful D810 blunders on the part of Phase One - following the announce & release of a highly anticipated DSLR. What is going on here? Maybe it's time to hire a few more developers? You think? You said you were working on D810 support months ago, and this is what we have been waiting for?0 -
[quote="Keirnan1" wrote:
It's only file naming. It's not like it can mess anything up.
...
Your post is not accurate by facts. Tethering support became only recently available after Nikon released their new SDK with D810 support. Phase One has chosen to update CO7 with D810 raw file support after they already released CO8, which is a great service to users, not forcing users to upgrade.
Your glass is obviously half-empty. Mine half-full.0 -
I can also report an issue with file naming using a Macbook Pro Retina (2012), running both 8 and 8.01 and the Nikon D810 with tethertools 5m active repeater and short mini cable for camera. It seems to think the first 30-40 shots already exist adding the extra digit at the end, then after a while continuing with normal naming. Hopefully this gets fixed soon! Thanks 0 -
I had the same issue on a shoot yesterday. I spent some time looking the the settings to see if something was set incorrectly. Hopefully Phase One will have a fix for this soon. 0 -
Well the point is, if you own a D810 -you cant use it tethered with any C1 Pro versions as of now. I have been shooting to C1 Pro 8.0.1, then copying the files into C1 Pro 7.2.4, batch renaming and processing. Once Phase releases a version of 8 for D810 users, I will just batch rename all the files all over again. 0 -
Well the point is, if you own a D810 -you cant use it tethered with any C1 Pro versions as of now.
I shot a multi-day job on the D810 and C1 8.0.1. It was very stable, and despite the renaming issue, all else worked great. It was not that big of a deal to batch re-name captures at the end of each shot, within C1 8.
The USB problem is solved by adding a powered USB3 hub in-line. It's not a C1 bug, but rather a problem of implementation of the USB protocol on the D810 and Apple systems...the Nikon uses USB3v1.1, and Apple uses USB3v1, which can cause some instability.0 -
[quote="MikeNYC" wrote:
Well the point is, if you own a D810 -you cant use it tethered with any C1 Pro versions as of now.
I shot a multi-day job on the D810 and C1 8.0.1. It was very stable, and despite the renaming issue, all else worked great. It was not that big of a deal to batch re-name captures at the end of each shot, within C1 8.
Look at your files a little closer... batch rename doesn't work right (or at least not for me). Every time I do a batch rename in 8.0.1 a small number of files within are incorrectly named - which has to be manually fixed. This is why I have just been creating new sessions in 7.2.x, and importing, renaming. Say what you will, but it's a lot of time lost when you don't have any.
I'm curious why you are defending an immature release of C1 Pro 7.2.4 & 8.0.1? Your personal tolerance for dysfunction doesn't make it okay. The D810 was a highly anticipated camera, that a lot of professionals use. I have been using Phase One software since 2006(!), and truth be told, every single major release has been fraught with problems. They have become much more depended upon software since then, and could seemingly benefit from hiring more developers. I'm not sure why they thought pushing D810 users into a brand new, major release was a good idea, rather that giving them the solidity of tethered support in 7.2.x, regardless - they are dealing with the outcome of that now. I just wish they would do it a little faster.0 -
The rename for me works flawlessly. I do a rename twice...the first one with a counter range that's outside of any existing shots in the folder (if I have Image_001 through Image_150, I'll rename first to Image_500 through Image_650) then re-rename to Image_001 etc.
I'm curious why you're expecting perfection out of an initial release. We'd all love all software to be flawless all of the time, but that's simply not the case. If it's not 100% tested by you, don't use it on a critical job. If the D810 + software combo isn't ready for your needs, don't use it. Simple as that.
It's not a "tolerance for dysfunction". I know the limitations of the tools that I'm using, and I adapt accordingly.0 -
Hey guys, try going into the settings under the "next capture naming" tool (upper right ellipsis) and uncheck "Pair RAWs and JPGs"
During tethering, I think the bug might be related to that setting. Let me know if that works for you.0 -
We are looking into the bug, and have found that the D810 does not increment its image-counter in the same way as the all other Nikons do. It is only being incremented when shooting at certain fps (usually 1,25 fps or faster).
We continue to troubleshoot. Thank you for your patience.0 -
Here's a fix that worked for me.
1. In the "Next Capture Naming" tool, uncheck all the preferences and then choose "Reset Capture Counter".
2. Set up a custom name in the "Naming Format" setting. I chose "Name"_"3 Digit Counter" and saved the custom preset with this name; "Name + 3 Digits". This allows me to apply it when needed. I know this is very similar if not exactly the same as the built in preset "Name and 3 Digit Counter". Unfortunately, the built-in preset doesn't work at this time.
3. Anytime you start a new session, you'll have to choose your custom preset or the file naming issues will return.0 -
[quote="Andrew Lawrence" wrote:
Hey guys, try going into the settings under the "next capture naming" tool (upper right ellipsis) and uncheck "Pair RAWs and JPGs"
During tethering, I think the bug might be related to that setting. Let me know if that works for you.
Hey Andrew, this was our solution as well. (tethered raw w/ Nikon D4s, C1 7.2.4, iMac OS10.9.5)0
Post is closed for comments.
Comments
25 comments