IIRC, a new installation of Media Composer should be run for the first time under an Admin account. This creates the MCState file for the first time, owned by Admin and R/W by all other users. But ... I've just experienced a glitch. If a non-admin user (my students, or one of my standard test accounts) deletes MCState (a regular troubleshooting

I believe that deactivation and reactivation is not needed any more. I think this was flagged in some release notes but I know from experience that if I run MC on my iMac, then quit and launch it on my MacBook, it will run correctly. Quit and return to the iMac? Runs fine. Not sure when this happened but I have not had to deactivate for some time. Only

Spoke too soon. Some SD media from my G-Raid now throws the error again. Someone at Avid must know what this error means?

Is it that it's not there at all or it's not populated with the effect parameters? And don't forget that clicking the TC track will make it vanish. Don't do that unless you plan to play more of the sequence in the monitor than just the effect clip.

No - saving locally is good as gold. My workaround, to avoid students freaking out, is to create a project on the Desktop and then copying it to a student's network space when done. Next time copy it back to the Desktop and so on. Cliunky. We had the same issue with Editshare but not consistently. I tried to retire from my university but they are

Mercer wrote: "Can you import them rather than linking? There should be no change if you import, with no change, to DV25, for example." It's a thought, but I don't want to get 80 students importing the files and filling up our media spaces with a load of duplicated gigabytes! I did try your suggestion - I get a 'Can't import

Your solution is not good for me. These files have been used for a number of years and are used for teaching. They are well suited to this purpose and have accompanying scripts and logs. I will have to convert them. BTW, this is not an issue in MC 2018.12.15 which I have on another ssystem for testing such anomalies. Clearly, something has changed in

It's possible, but in that case, why are the bins updated and saved? It's a university network so I don't live in hope of getting anything changed!

Here's an old but (not) goodie. Launch MC in our University and make a project on a student's network drive. All seems good until we save (or Autosave kicks in) and we get a frightening message: 'Project setting is not saved' Aaarggh! Actually, all bins ARE saved but the Project setting file is not. It is created correctly in the first

Let's face it, Jef is right. I spend too much time saving and resaving workspaces to get them to look the way I want. There is lots of good stuff in the recent releases but the whole UI thing has been messed up for ... who knows why? If I return to a 2018 release, I can breathe out 'Ah ..' all is good in Avid's little world. I know it's