Support for new cameras in c1 3.7
Hello
Have played around with c1 pro 4.5.2, some nice features, but the fact that we can't work with sessions generated by 3.x is a major problem. Almost five years worth of projects will become basically inaccessible, and from what I understand will remain so. We will probably continue to work with 3.7 for this reason, for as long as we can, but I was wondering if anyone from Phase would care to enlighten us as to whether 3.7 will continue to be updated, particularly with support for new cameras like the 5D mk2, 1ds mk4, or p65+, all of which we are likely to be working with in the near future. Sadly I suspect not, which means that we will eventually have to move reluctantly from working with Phase software to some other platform that will maintain backwards compatibility as new cameras and software versions are released, rather than forcing us to abandon established workflows and methods. I think Phase One should be embarrassed and ashamed. You trumpet your association with professionals in your marketing materials and all over your website, but how can you really claim to have the interests of professionals in mind when you so casually overlook something as basic as backwards compatibility? Perhaps it will eventually be sorted out, in which case I apologise for the frustrated tone of this post, but if it doesn't happen soon I think you might run the risk, at least from a software perspective, of marginalizing yourselves.
Have played around with c1 pro 4.5.2, some nice features, but the fact that we can't work with sessions generated by 3.x is a major problem. Almost five years worth of projects will become basically inaccessible, and from what I understand will remain so. We will probably continue to work with 3.7 for this reason, for as long as we can, but I was wondering if anyone from Phase would care to enlighten us as to whether 3.7 will continue to be updated, particularly with support for new cameras like the 5D mk2, 1ds mk4, or p65+, all of which we are likely to be working with in the near future. Sadly I suspect not, which means that we will eventually have to move reluctantly from working with Phase software to some other platform that will maintain backwards compatibility as new cameras and software versions are released, rather than forcing us to abandon established workflows and methods. I think Phase One should be embarrassed and ashamed. You trumpet your association with professionals in your marketing materials and all over your website, but how can you really claim to have the interests of professionals in mind when you so casually overlook something as basic as backwards compatibility? Perhaps it will eventually be sorted out, in which case I apologise for the frustrated tone of this post, but if it doesn't happen soon I think you might run the risk, at least from a software perspective, of marginalizing yourselves.
0
-
Find your answer here:
viewtopic.php?p=26219#p26219
and please don't shoot the messenger (=me) 😉0 -
Yes, that is what I was afraid of.
As you can imagine it opens up multiple cans of worms. In order to run 4.5.2 we will now have to globally upgrade to osx 10.5.5 across all our in studio workstations as well as all our field capture systems, which means incurring a great deal of expense as well as of course introducing a host of incompatibilities with many of our software packages, not the least of which are the mysterious, devastating crashes we are experiencing when using 3.7.9 (which we will have to continue using for the sake of our older jobs) under 10.5.5.
The upgrade to 4.5 will at least generate a lot of overtime pay for assistants! Any chance of eventually making c1 pro 4 backwards compatible with 3.7.x sessions? It would make things a little less frustrating.0
Post is closed for comments.
Comments
2 comments