John Richard wrote:Another example of why announcing in advance what is in the next firmware is the missing audio levels issue. Many of us are just down rigging out the cameras we are receiving. We now know that the next firmware probably won't address in camera recording of audio and being able to see levels. So we know we have to find another solution such as the Juiced Link Riggy Assist and how to calibrate the meters on it. If we did not have this advance idea roughly of what was coming in the next firmware, we would be in the dark on what to for current usage. I also know we won't have to make a purchase to replace the non-working 35mm/1.4 Canon lens.
But you don't. You're assuming based on preliminary testing. It's beta. It can change. Also, some features might be included, like audio levels, but they ask the testers not to speak about them because they're not sure they'll be done in time. Buyers beware. You shouldn't be making any sort of purchasing or logistical planning based on "beta" info. Look how many people on this forum say they have a big project that they can't do since their BMCC didn't ship in time. Wonder what their customers think of them?!
It's product development. To the un-initiated, it's confusing and sets unrealistic expectations. I love feedback and open communication, but going public is very different that selectively engaging your users. This is why we have beta programs to begin with.