4.6 crashes after 100 plus captures/session?
I have a new problem.
I was shooting people last week tethered with my Canon 1Ds Mk III. After about 100 captures the software seized up. The "globe of doom" appeared. We had to restart the computer etc. We continued and it happened a few more times during the day. Then I thought I was loosing files. But not really. They were being numbered incorrectly. I think the software began at "1" again with some of the captures but then seamed to continue where it left off. I've now reopened the session to do my editing and processing. The capture numbers are all over the place. It appears that the software may have been naming captures starting from number 1 after each crash and restart in the session.
In 3.7 I was able to batch rename files and specify what frame number I wanted the renaming to begin at. I can't do that in 4. This is a real shame. How else can I re-arrange the sequence of my captures now.
I checked with my supplier about the crashes and renaming. He said this seems to be an issue with 4, more than about 100 captures in a session and it begins to crash. He's heard about this from several other people. Is this just with 4.6? Should I go back to 4.2 for now?
Anyone else having this issue?
I really felt as if my early issues with C1 4 were about learning the software and there is a lot of cool new stuff to play with. But I'm also running into real issues and I'm running out of time for mucking about. I can't keep apologizing to clients for the delays. Funny thing is that they'll actually say "Is it the new C1 4? Yah, some of the other guys we work with are having issue with that as well." What the heck is going on?
Andreas
I was shooting people last week tethered with my Canon 1Ds Mk III. After about 100 captures the software seized up. The "globe of doom" appeared. We had to restart the computer etc. We continued and it happened a few more times during the day. Then I thought I was loosing files. But not really. They were being numbered incorrectly. I think the software began at "1" again with some of the captures but then seamed to continue where it left off. I've now reopened the session to do my editing and processing. The capture numbers are all over the place. It appears that the software may have been naming captures starting from number 1 after each crash and restart in the session.
In 3.7 I was able to batch rename files and specify what frame number I wanted the renaming to begin at. I can't do that in 4. This is a real shame. How else can I re-arrange the sequence of my captures now.
I checked with my supplier about the crashes and renaming. He said this seems to be an issue with 4, more than about 100 captures in a session and it begins to crash. He's heard about this from several other people. Is this just with 4.6? Should I go back to 4.2 for now?
Anyone else having this issue?
I really felt as if my early issues with C1 4 were about learning the software and there is a lot of cool new stuff to play with. But I'm also running into real issues and I'm running out of time for mucking about. I can't keep apologizing to clients for the delays. Funny thing is that they'll actually say "Is it the new C1 4? Yah, some of the other guys we work with are having issue with that as well." What the heck is going on?
Andreas
0
-
You might check the Luminous Landscape Forums
If you have upgraded to 10.5.6
Evidently although it has sped up the transfer over USB, it has added some new problems. Other people are having the same problem with the Canon software0 -
Thanks David.
I did also just upgrade to OS 10.5.6 as well. I'll check Luminous Landscape.0 -
Currently the problem seems to be related to Image Capture Extension not releasing memory. We are currently looking to the matter to see if it is something we are able create fix for, or whether we will need to wait on updates from Apple or Canon as well. 0
投稿コメントは受け付けていません。
コメント
3件のコメント