Three Bugs in C1 v6
I'm using a Canon EOS 5D (mk 1) tethered to C1 Pro 6.1.1 (build 46651)
Mac Pro 2x 2.4ghz quad-core Xeon, 6gb RAM, OSX 10.6.6.
- Since I first got C1 Pro back in December I've had the issue that I can't switch sessions or start a new session with the camera already tethered. If I finish working on one project, I have to close C1 down, turn the camera off, and restart C1 with the new session before switching the camera back on. If I try to switch sessions when already tethered, I just get the 'attaching camera' window, which never disappears and just makes the software hang, resulting in me having to 'force quit'. Two updates haven't fixed this.
- Since the update previous to this latest one, the Output Naming settings fail to work correctly. I have set it to use the job name and then add a counter number, but instead of taking the job name of the current job/session it takes the job name of the last session that was open. I was hoping it would be fixed in the latest update, but it hasn't been. It means I have to manually type in the job name each time, which defeats the point.
- On a new session this afternoon, I had to take several test shots before trashing them and then restarting the image counter in the Capture Naming settings. When I started the shoot 'proper', the first image appeared not as the shot I'd just taken, but a copy of the previous test shot that I'd just trashed. The rest of the shoot then went fine.
When I browsed back through the images I'd taken, the very first image taken then appeared corrupted (although it had been fine earlier on). Each time I browsed away from it and returned it got progressively worse, with it bizarrely eventually becoming substituted with an image from much later in the series with a bright pink cast over it! The thumbnail image at the bottom was originally fine too, but that then became substituted with a copy of the thumbnail of the second image. This is the first time I've seen anything as bizarre as this.
Mac Pro 2x 2.4ghz quad-core Xeon, 6gb RAM, OSX 10.6.6.
- Since I first got C1 Pro back in December I've had the issue that I can't switch sessions or start a new session with the camera already tethered. If I finish working on one project, I have to close C1 down, turn the camera off, and restart C1 with the new session before switching the camera back on. If I try to switch sessions when already tethered, I just get the 'attaching camera' window, which never disappears and just makes the software hang, resulting in me having to 'force quit'. Two updates haven't fixed this.
- Since the update previous to this latest one, the Output Naming settings fail to work correctly. I have set it to use the job name and then add a counter number, but instead of taking the job name of the current job/session it takes the job name of the last session that was open. I was hoping it would be fixed in the latest update, but it hasn't been. It means I have to manually type in the job name each time, which defeats the point.
- On a new session this afternoon, I had to take several test shots before trashing them and then restarting the image counter in the Capture Naming settings. When I started the shoot 'proper', the first image appeared not as the shot I'd just taken, but a copy of the previous test shot that I'd just trashed. The rest of the shoot then went fine.
When I browsed back through the images I'd taken, the very first image taken then appeared corrupted (although it had been fine earlier on). Each time I browsed away from it and returned it got progressively worse, with it bizarrely eventually becoming substituted with an image from much later in the series with a bright pink cast over it! The thumbnail image at the bottom was originally fine too, but that then became substituted with a copy of the thumbnail of the second image. This is the first time I've seen anything as bizarre as this.
0
-
Do you perhaps have the opportunity to try a more camera recent model. No offense of course but because the Canon 5D is not supported anymore in CO6, you might want to rule that out as a potential cause by testing with a newer model. 0 -
the original 5D is not supported in V6? Is that true? Those files are great much better tonality than the MII (that I own) just smaller. I can't imagine why it would not be supported. So if I go back to an old session with 5D files there will be no profile? 0 -
I'm not a Canon shooter, but I am shocked that a one generation old camera--and a popular one at that--is not supported. Does Phase One expect their clients to be upgrading cameras with every new model that is released?
Rob0 -
[quote="robgo2" wrote:
I'm not a Canon shooter, but I am shocked that a one generation old camera--and a popular one at that--is not supported. Does Phase One expect their clients to be upgrading cameras with every new model that is released?
Rob
well, tethering is not supported or rather not guaranteedTethered camera support... Additionally Capture One 6.1.1 Pro has tethered support for the following cameras:... 1D Mark IV, 1Ds Mark III, 1D Mark III, 5D Mark II, 7D, 60D, 50D, 40D, 550D/Rebel T2i, 500D/Rebel T1i, 450D/Rebel XSi, 1000D/Rebel XS. Some older Canon models may work to some extent but no support is provided for these.
That depends a lot on SDK supplied by Canon, so it might be that P1 is not 100% to blame here, that tethering w/ 5D is no more...0 -
Sorry guys I caused a confusion about the end of 5D support. I meant the tethering support. As explained - thanks deejjjaaaa - it is Canon who dropped support in their SDK. 0 -
How about the second descibed bug?
For me it's a "InputNaming" bug. I want c1pro ton name the impoted files: sessionname-counter.
Worked well in 3.7.
Now it always takes the name of the last import. I always have to rename the files.0 -
Unfortunately I don't have the opportunity to try a newer camera at the moment (my spare camera is an EOS20D). I'm hoping to have a newer model later this year, but it'll depend entirely on how generous my managers are feeling...
Thanks for the replies though - at least that does give me an idea of why I have the tethering issues. Once I get it working, it tends to work fine until I end the session. I also haven't haven't had the third bug occur again (corrupting the image), so hopefully that was a one-off. I have also noticed that occasionally, even when it appears to have tethered successfully and the session is ready to begin, although I can 'capture' from the software the image fails to download. Again, this often fixes itself after restarting C1.0 -
If the tethering issue keeps bothering you, you could consider using CO Pro 5 for that purpose. You can activate it with your CO Pro 6 key. If you do not want to leave CO 6 because of numerous reasons even I can come up with, you could look for an old Intel Mac system or install OS X on an internal disk and install CO 5 on that system.
If you are not too scared from Windows, a Boot Camp setup or virtual machine setup on your Mac could be a solution as well.
Not ideal, but a workaround sometimes can make life easier.0 -
You can enable hot folders in the ession you are currently in and then use Canon Utility to still Tether. Not perfect, but a good workaround! 0
Post ist für Kommentare geschlossen.
Kommentare
9 Kommentare