Interesting OpenCL experience upgrading 6.1.1 to 6.3.4
Interesting experience upgrading 6.1.1 to 6.3.4
I run the Mac service desk in a large photography studio in NYC and wanted to share our experience upgrading 6.1.1 to 6.3.4. Both myself and my new tech Jason have photography backgrounds as well as Mac support.Â
First of all I should mention we have about 40 installs of C1 DB 6.2.2 doing still life work with little to no issues. However, the fashion studio works at a blinding pace and pushes the limits of C1 and MacPro capture stations. Version 6.1.1 with OpenCL set to NEVER was working fairly well for fashion. They pack as EIP upon capture. Recently we had to upgrade from 6.1.1 to 6.3.3 due to the "assertion failed" USB-related error they experienced when shooting tethered with a Canon 5Dmk2.Â
After doing full resets of C1 on two MacPros, we installed 6.3.3 and set prefs for  OpenCL 'NEVER' and pack as EIP upon capture, just as we did with 6.1.1.
The first shoot using 6.3.3 was a disaster. C1 or ImageCore or Capture Server crashed a total of 18 times in 12 hours. Camera was a Canon 5D mk2 tethered. The digital tech would attempt to change tabs in c1 or make image adjustments while captures were coming in, the spinning pinwheel appeared for a few seconds and then C1 would crash. Other times the previews stopped rezzing up (imagecore crash) requiring a C1 restart.
On the Editing station, scrolling through thumbnails too quickly while c1 was generating previews caused C1 6.3.3 to crash.Â
In the meantime, v.6.3.4 was released.
Jason ran tests with 6.3.4 using the MacPros listed here and a MacBook Pro i5 as well. He tethered a Canon 5D mk2, Canon 1ds mk2, Phase p30 and p40+ and shot hundreds of images.Â
Here is what we found:
6.1.1. OpenCL 'Never' and EIP: stable. 9 months no complaints. Minimal crashing.
6.3.4. OpenCL 'Never' and native RAW CR2 and IIQ: worked fine. minimal crashing during high speed tethered shooting.
6.3.4. OpenCL 'Never' and EIP: unstable. during rapid tethered shooting multitasking within c1 impossible, frequent crashes of c1, ImageCore or capture server.
6.3.4. Open CL 'Auto' and EIP: solid! multitasking within c1 capable, minimal crashing. Occasional ImageCore crash during rapid tethered shooting with P40+ and Canon 5D mk2.
The Editing station, 2.8 ghz 8-core MacPro 2008 running 6.3.4, has some OpenCL issues due to age of the computer. Clicking on a thumbnail may display a completely different image in different session. However, things get worse with OpenCL on 'Never'. C1 gobbles up all the RAM, things get slow and eventually a restart of computer is needed. This really aggravates the Art Director. 32GB RAM installed. We are going to swap out this tower for a newer MacPro (newer OpenCL drivers).
The 6.3.4 capture station has not crashed so far in 1.5 days of shooting, although they had a few ImageCore crashed likely due to rapid shooting with P40+.
With 6.1.1 we had OpenCL set to NEVER to achieve stability. Now the opposite is true with 6.3.4: We must have OpenCL on AUTO on the same computers.
Capture station:
MacPro 5,1
2.4 ghz 8-core
12GB RAM
ATI Radeon 5770
Apple OS 10.6.8
Editing station:
MacPro 3,1 (2008)
2.8 ghz 8-core
32GB RAM
Nvidia GeForce 8800GT
Apple OS 10.6.8
Laptop:
MacBook Pro 6,2
2.4 ghz i5
4 GB RAM
Nvidia GeForce GT 330M
Apple OS 10.6.8
I run the Mac service desk in a large photography studio in NYC and wanted to share our experience upgrading 6.1.1 to 6.3.4. Both myself and my new tech Jason have photography backgrounds as well as Mac support.Â
First of all I should mention we have about 40 installs of C1 DB 6.2.2 doing still life work with little to no issues. However, the fashion studio works at a blinding pace and pushes the limits of C1 and MacPro capture stations. Version 6.1.1 with OpenCL set to NEVER was working fairly well for fashion. They pack as EIP upon capture. Recently we had to upgrade from 6.1.1 to 6.3.3 due to the "assertion failed" USB-related error they experienced when shooting tethered with a Canon 5Dmk2.Â
After doing full resets of C1 on two MacPros, we installed 6.3.3 and set prefs for  OpenCL 'NEVER' and pack as EIP upon capture, just as we did with 6.1.1.
The first shoot using 6.3.3 was a disaster. C1 or ImageCore or Capture Server crashed a total of 18 times in 12 hours. Camera was a Canon 5D mk2 tethered. The digital tech would attempt to change tabs in c1 or make image adjustments while captures were coming in, the spinning pinwheel appeared for a few seconds and then C1 would crash. Other times the previews stopped rezzing up (imagecore crash) requiring a C1 restart.
On the Editing station, scrolling through thumbnails too quickly while c1 was generating previews caused C1 6.3.3 to crash.Â
In the meantime, v.6.3.4 was released.
Jason ran tests with 6.3.4 using the MacPros listed here and a MacBook Pro i5 as well. He tethered a Canon 5D mk2, Canon 1ds mk2, Phase p30 and p40+ and shot hundreds of images.Â
Here is what we found:
6.1.1. OpenCL 'Never' and EIP: stable. 9 months no complaints. Minimal crashing.
6.3.4. OpenCL 'Never' and native RAW CR2 and IIQ: worked fine. minimal crashing during high speed tethered shooting.
6.3.4. OpenCL 'Never' and EIP: unstable. during rapid tethered shooting multitasking within c1 impossible, frequent crashes of c1, ImageCore or capture server.
6.3.4. Open CL 'Auto' and EIP: solid! multitasking within c1 capable, minimal crashing. Occasional ImageCore crash during rapid tethered shooting with P40+ and Canon 5D mk2.
The Editing station, 2.8 ghz 8-core MacPro 2008 running 6.3.4, has some OpenCL issues due to age of the computer. Clicking on a thumbnail may display a completely different image in different session. However, things get worse with OpenCL on 'Never'. C1 gobbles up all the RAM, things get slow and eventually a restart of computer is needed. This really aggravates the Art Director. 32GB RAM installed. We are going to swap out this tower for a newer MacPro (newer OpenCL drivers).
The 6.3.4 capture station has not crashed so far in 1.5 days of shooting, although they had a few ImageCore crashed likely due to rapid shooting with P40+.
With 6.1.1 we had OpenCL set to NEVER to achieve stability. Now the opposite is true with 6.3.4: We must have OpenCL on AUTO on the same computers.
Capture station:
MacPro 5,1
2.4 ghz 8-core
12GB RAM
ATI Radeon 5770
Apple OS 10.6.8
Editing station:
MacPro 3,1 (2008)
2.8 ghz 8-core
32GB RAM
Nvidia GeForce 8800GT
Apple OS 10.6.8
Laptop:
MacBook Pro 6,2
2.4 ghz i5
4 GB RAM
Nvidia GeForce GT 330M
Apple OS 10.6.8
0
-
Did you do a clean install of 6.3.4?
Maybe a .cos file is corrupt?
Look forward to hearing about your solution(s)0 -
Re-formatted hard drive, clean installed 10.6.8, installed fresh download of 6.3.4.
Just thought this was interesting because, while using the exact same MacPro hardware, we had to run 6.1.1 with OpenCL set on 'Never'. Now, with 6.3.4, C1 is very unstable unless we set OpenCL to 'Auto'. It has to do with packing as EIP upon capture for the most part. When we captured using native RAW formats IIQ and CR2, there was not an issue. Unfortunately, Fashion's workflow is built entirely around packing as EIP upon capturing.0 -
I have been having overheating issues running C1 6.1. The fans have been replaced, everything cleaned and tested, thermal paste redone, all to no real advantage. Could OpenCL Auto be contributing to this? The processor runs flat out at 100% for extended periods and the heat builds up until it shuts down. I have good air circulation. I even put a wind machine under it just to see. 0
Post ist für Kommentare geschlossen.
Kommentare
3 Kommentare