Forum Replies Created

  • This bug was indeed logged with Apple back in June of 2009. I have to say it was given what seems to me to be a half-hearted effort. They made no attempt to re-create the problem but requested a logged report from me which required forcing an unrelated failure, consequently engineering was unable to identify the issue. Given the FCP-Avid rivalry, Apple does not seem concerned.
    Avid is also aware of the problem. The use of Mac-authenticated accounts is apparently not widespread, so not much interest has been generated. I manage an educational lab with 70 computers and a variety of software that requires flexible usage of space, hence my needs. It seems post houses and broadcasters just don’t usually get quite so sophisticated or give up trying.
    Both Apple and Avid need to hear from more customers. I had to cancel my planned upgrades for this fall.

  • A followup and FYI, this bug is now reported to Apple. I’ll try to keep updates posted. (Hard to believe this isn’t affecting more facilities).

  • I have been wrestling with this issue since last fall when 3.1.x came out.

    The problem is NOT 10.5.7. The problem has to do with how the Mac account profiles are being handled. I can successfully launch Media Composer on the same Macs using the Windows OS, authenticating against the same server with Windows roaming profiles. I can also successfully launch Media Composer under the Mac OS if a local account is used rather than a networked account.

    Looks like this is an Apple issue. A similar condition exists for Adobe Acrobat ver.9. The resolution for Adobe is a convoluted system of symbolic links.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy