Jeff. . .
Stefan Rhys
Hi Stefan,
Hopefully by now you are out of uninstall hell.One thing to keep in mind with the Avid software (you mentioned you were relatively new to Avid from FCP) is that Media Composer is VERY finicky about system requirements. It's not just OS versions, it's hardware too!For a while it was also very finicky about Quicktime updates - and I had quite a few users who wanted to be able to upgrade their iTunes so they could plug in their iPhones - but it required quicktime updates... some did the updates and could no longer export from the Avid.Long story short, no one updates the machines but me - and I treat our Media Composer stations as if that is the ONLY software that runs on them.If Adobe requires an OS update that Media Composer can't handle - then the Adobe update goes on the back burner.One of the benefits of FCP was that since Apple ran it - they tended not to do OS updates that broke it (at least in my memory - I've been in and out of support for FCP through the years). As a fellow apple user I know it can be very frustrating to not do all the updates that they are pushing out to you (and in this case with the SSL bug... I hear you), however, if you can treat that CPU as your Media Composer CPU only, that will make things like this easier.I understand that it is a lot to ask - having one CPU dedicated to only one software package. But, believe me, if you can to do this, your life will be easier.Keep an eye on the 'Version Matrix' on Avid's site.And look carefully through the 'Read Me's' that come out for each version - they are good at specifying what you can and can't run with that version.Another recommendation I will give you is that once you have a working OS and Media Composer setup - make a disk image of it, and set aside so that if you end up against a wall, it is relatively painless to erase a hard drive and install a known working version.Good luck,Jeff------------------
Jeff HedbergDirector of Operations
Union Editorial
575 Broadway,6th floor
New York, NY 10012On Mar 2, 2014, at 2:21 PM, Stefan Rhys <srhys@coffeecartproductions.com> wrote:No, Michael. My problems started when I was on 10.9.1. They continued after I had to move to 10.9.2 for my machine's security. Thanks for paying attention.
Stefan RhysContact: 626.679.0813Filmmaker/ConsultantCoffee Cart ProductionsE-mail: srhys@coffeecartproductions.comBiography: www.neweraartist.net**The information contained in this electronic mail is privileged and confidential information intended only for the use of the individual or entity named in the above address. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.**On Mar 1, 2014, at 5:18 PM, Michael Brockington <brocking@sfu.ca> wrote:I wouldn't argue that point with you David; I'm sure it's true. But I'm equally sure such issues are less common with supported OS versions.
In this case, as Stefan confirmed towards the end of this thread, his problems started when he upgraded from 10.9.1, which is supported, to 10.9.2 which is not.
Cheers,
--MichaelOn 14-03-01 4:41 PM, David Dodson wrote:Michael, I'm gonna have to chime in here and say that your comment isn't quite fair in that these uninstall issues are not isolated to efforts to install on unsupported and/or unqualified OS's. Because that's just not true. I've had uninstall frustrations on boxes that were supposedly 100% qualified for the versions being installed. So let's be fair about this, and not assume that there's no problem based on the false assertion that these problems do not exist on supported versions and OS's. Because that just ain't so.DDOn Mar 1, 2014, at 4:31 PM, Michael Brockington <brocking@sfu.ca> wrote:Stefan:
You created your own problem by running the software on an unsupported operating system version. Not too surprising, then, that some members of this forum are unsympathetic to your ensuing rant about how crappy Avid software is. Not so classy, that. I'm impressed by how many folks offered help nonetheless.
If you still need to discharge some anger, maybe Apple would be a more appropriate target. You know -- the company that left the gaping security hole in 10.9.1 which prompted your unfortunate OS upgrade.
--Michael BrockingtonOn 14-03-01 3:10 PM, Stefan Rhys wrote:Wow.Classy, Evan Wright! Thanks.When I initially started my migration, I HAD an approved operating system. And actually, you're wrong Evan, Mavericks 10.9.1 was finally approved for use with MC 6.5 (or else I never would have made the jump in the first place).But then with the recent SSL issue and I HAD to update, guess what? I'm not on an approved system. And despite following all the recommended protocols previously I was given, still the issue.Fortunately both David and Marianna are both ACTUALLY classy individuals and have reached out to me.I will wait until the latest approved update comes out and hope for the best.Keep it classy,--S.
Sent from my iPadSeems like all of this uninstall fiasco could have been avoided in the first place by installing the Avid software on a QUALIFIED operating system. It makes complete sense that the uninstall is also having issues, as it too is running on an unqualified OS. Seems the easiest way to fix everything would be to simply-- and properly (meaning use backups) reformat your drive back to Mountain Lion, then reinstall Media Composer. Once that is done, that should give you time to fix your own coffeecartproductions website that is also broken, which offers iPad visitors a black void instead of a home page. Seems like you are IT challenged, and not Avid.
David Dodson
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (50) |
No comments:
Post a Comment