'Sounds like there are some real experts out there who are working their H cameras and backs through Flexcolor very hard and in every condition day in and day out without any issues. You guys are amazing and hold a secret the rest of us all want to know. Please tell us exactly how you do it what it is you do so well and who you are.
In the meantime, we at my studio we have had some specific situations in which either Hasselblad's back, the camera or the software do not function to the standard by which Hasselblad has set. Over the past 4 years of shooting these systems and running Flexcolor on the Imacon scanners I have recorded a fairly long and detailed list (including all technical logs of such issues) of technical glitches from battery failure to file corruption to lock-ups to file naming to file exporting and to dng file efficacy. I have worked through the numerous firmware upgrades (including the 4 most recent 4.6.4, 4.6.5, 4.6.7 to 4.7) and I am most certain that version 4.7 will not be the last. But any savvy pro shooter will know that all software/firmware has issues, especially give the pressure placed on software in the many work environments it must perform in.
Therefore, in the process of discussing software stability (not utility - which is another discussion) there ought to be some basic assumptions:
• software/firmware will always need to be updated as other software and hardware changes
• software/firmware upgrades are essentially good, welcome and needed changes
• software/firmware will never perform perfectly in all environments to all users at all times
• time, testing and use will are the steps to reaching the goal of perfect software
• software/firmware will fail
• software/firmware is only as good as those who write the code
• if software does not work, then the quality of life is lowered
Here is the specific issue we have recently found with Flexcolor 4.7 within the specific condition to which Flexcolor has not been stable. Note: the only change in this scenario has been from 4.6.7 to 4.7. Prior to 4.7 the software crashing did not occur
Environment: Mac/Hasselblad
- Mac G4 Powerbook 1.5 GHz, OS X 10.4.9, 1 GB ram
- H2 body
- CF - 39 back
- Tethered with 14' firewire II cable
- Flexcolor 4.7 installed on all 3 devices (laptop, body, back)
Operation: Tethered Shooting on Location
- Enable camera control within Flexcolor
- Firing camera staged from laptop
- Captures load into Flexcolor and on to laptop
- After random # of captures (10-20) Flexcolor crashed with an error message "Flexcolor Unexpectedly Quit"
- Upon re-launching Flexcolor, the recently captured fff files in the designated folder are missing, and after a global search of the drive nowhere else including the trash.
Noteworthy: there are several great tech folk at Hasselblad who are more than willing to address and help investigate and remedy tech issues and software glitches as they arise. I can't give Paul Claesson enough praise regarding his genuine interest and care for the pro shooting community. He is a real asset to Hasselblad and an excellent person when issues need to be addressed.