Your view doesn't take into account the real world I live in. I have to collaborate with a broad base of Avid installs and if Avid stops maintaining a reasonable backwards compatibility there will be trouble in my River City. I get a sequence offlined on 5.5.x and online in 6.5.X and end up making changes that effect the AAF sent to protools. Now if Avid stops patching 5.5.X to be compatible with bins from newer systems I'm in a bit of a bind. How do I get a sequence back to the AE at the production company that he can open and conform to my newly revised timeline? Perhaps we are agreeing on the main point of backwards compatibility but as they add new features they will still need to apply resources to the older software to keep everybody collaborating. I don't expect the newer ama plugins and new features to be added to earlier versions but core maintenance issues have to go back to 5.5.x in my world. In fact I just did a job on V.4 and the AE had to use his 7.0.x home system to aaf the Red Clips back into my Avid. It was a bit of a cluster flop but he banged through it so at least I had media I could color correct. I posted some of the issues on that job.
A week ago I was bouncing bins from Ver 7.0.3 to 6.0.3 and I had problems. I realize they needed to upgrade to the latest ver of 6.0.x to have better bin compatibility. Does Avid do any patches to anything before v5.5.x now?
I don't think there's a way to add features and maintain backwards compatibility without having to patch the older systems. I'm not a programmer but it seems like that would be a difficult task.
---In Avid-L2@yahoogroups.com, <switthaus@...> wrote :
Posted by: bigfish@pacbell.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (27) |
No comments:
Post a Comment