dougpeterson
Workshop Member
We now expect the public release of this firmware fix to occur tomorrow (Thursday July 25).We’ve been testing a beta of the fix.
Should be more news next week.
Brevity of post due to caring for baby.
Great to see you here. Join our insightful photographic forum today and start tapping into a huge wealth of photographic knowledge. Completing our simple registration process will allow you to gain access to exclusive content, add your own topics and posts, share your work and connect with other members through your own private inbox! And don’t forget to say hi!
We now expect the public release of this firmware fix to occur tomorrow (Thursday July 25).We’ve been testing a beta of the fix.
Should be more news next week.
Brevity of post due to caring for baby.
Hoping this FW update/fix comes with 4 more feature updates :clap:We now expect the public release of this firmware fix to occur tomorrow (Thursday July 25).
It will not have any new features. Given the rather serious nature of the bug they focused exclusively on fixing that bug and testing to make sure they didn't create any new ones.Hoping this FW update/fix comes with 4 more feature updates :clap:
Dear Doug,It will not have any new features. Given the rather serious nature of the bug they focused exclusively on fixing that bug and testing to make sure they didn't create any new ones.
But hopefully new Feature Updates will come more quickly in the future.
Indeed; dealers received a beta of this fix, but you can imagine most of us were a bit gun shy to widely distribute. While the bug in the previous firmware was unacceptable and serious, it was also a known-issue that had a known-workaround. "The devil you know"Dear Doug,
I have used the beta FW 5.01 since Friday, courtesy of my dealer, Studio Import, in Norway
I have been shooting in a remote location in Lakho national park in Norway, so fortunately my dealer
Studio Import in Norway managed to get a copy of the beta FW sent tome in the field, so I could avoid
the file format bug.
Yes, it's a very focused/narrow update.Note, update seems to be basically a bit switch, as it only takes about 2 minutes to complete unlike all previous IQ/XF updates that take up to 5 to 8 minutes and require the long period of LCD black out on the IQ4, (only see the blue light at bottom).
The information is incorrect. None of them tested again (I can not believe it)..........
• When using Automated Frame Averaging in conjunction with the IIQ 16 Extended file format, the total number of frames changes as the sequence is started. However, feature works as intended.
........
IQ4150 not when selecting IIQ14 + in conjunction with the FA function. IQ4150 always writes a normal 14 bit L file. IQ4 Achromatic behaves as described above and will never finish. Both IQ4 and both XF of me have absolutely the same firmware. There is much more in the bad ............
• Automated Frame Averaging doesn’t work correctly when the IIQ 14 Sensor+ file format is used as the sequence never completes. Please use another file format.
........
Gerd is correct.
See attached screen shots:
Image 778 through 781 are were all captured in with back set to 16bit EX, all show low 14 bit resolution capture, and is also shown from screen print of file sizes.
With latest firmware, Frame Averaged images are only 114MB, this is the size of 14Bit low rez.
You can record at 16 EX with no problem, files are 179 to 190MB, once you switch to Frame averaging, back records the smaller file sizes, even with 16bit EX selected.
When you go back to normal mode in 16bit EX, files go back to full size.
But they did fix the issue of everything going to 14 bit, i.e. when you start up, with camera set to 16bit EX, count is correct and image appear to be recorded correctly
No comment, but will say amazed.
Paul C
Errr... what?It has been our understanding that for now Frame Averaging will remain at 14 bit L quality, with 16 bit availability in the future. The read me notes may have jumped the gun a bit on this change, as our communication with Phase One indicated that frame Averaging was initially intended to be in 14bit L mode, and an update in the future would offer 16 bit options. As such, we (Capture Integration) see this then as not a bug, but as an intended limited release. And Phase One infomred of this even before the initial bug was detected, so this is not something new with this release or something that they did not "fix". It was intentional (for now).
I ordered two cheseburgers years ago at the "hot witch" (german fastfoot chain). When the food came I opened the burgers and asked where the cheese is? The waiters answer which cheese? I answer I have ordered Cheseburger. The waitress answered - they are only named that way.It has been our understanding that for now Frame Averaging will remain at 14 bit L quality, with 16 bit availability in the future. The read me notes may have jumped the gun a bit on this change, as our communication with Phase One indicated that frame Averaging was initially intended to be in 14bit L mode, and an update in the future would offer 16 bit options. As such, we (Capture Integration) see this then as not a bug, but as an intended limited release. And Phase One infomred of this even before the initial bug was detected, so this is not something new with this release or something that they did not "fix". It was intentional (for now).
Steve Hendrix/CI
Errr... what?
That does not match my understanding. If there's been a purposeful change to only allow 14-bit capture for frame averaging it was not communicated to me, is not noted in the release notes, and represents a reduction in capability from the previous firmware.
I'm really left scratching my head here and don't expect to have any answers earlier than tomorrow.
I call it a disappointment and a step in the wrong direction.You can call it a bug, you can call it a here you go for now. Irregardless, it works and does even now provide some advantages. Why Phase One could not wait until they had a 16 bit mode ready I have no idea.
I intend to harass my messenger quite a bit; just as soon as mine shows up. It sounds like Phase One told you/CI to expect this which only deepens my confusion as DT was not told despite being in continuous contact with P1, and again, it's not stated in the beta release notes, public/final release notes, or the dealer notification email. And in fact the only mention of 14 bit vs 16 bit is a note in the release notes that implies the exact opposite: "When using Automated Frame Averaging in conjunction with the IIQ 16 Extended file format [...]".Don't shoot the Messenger.
I call it a disappointment and a step in the wrong direction.
As do we. Your statement that "Phase One told you/CI to expect this" is 100% incorrect, nor do I appreciate you even suggesting it because it implies that we knew the files were only 14 bit before our clients did and this is 100% not the case. When the bug was first reported by Dave Chew - that is when we went back to Phase One and had a long discussion about the 14 bit single frame bug, but also discussed the now realized only 14 bit L mode for frame averaging. This was when they told us of their original intent to provide 14 bit until they had the 16 bit mode ready. I would appreciate it if you would address your statement regarding when we knew of this.I intend to harass my messenger quite a bit; just as soon as mine shows up. It sounds like Phase One told you/CI to expect this which only deepens my confusion as DT was not told, and again, it's not in the beta release notes, public/final release notes, or the dealer notification email. And in fact the only mention of bit depth or file-format is a note in the release notes that implies the exact opposite: "When using Automated Frame Averaging in conjunction with the IIQ 16 Extended file format [...]".
If Phase One intended Frame Averaging (temporarily or permanently) to be limited to 14-bit capture they sure as heck dropped the ball on communicating that well.