You are correct. So there are two problems here really. The way to solve the issue of having a Unity workspace reserved exclusively for Avid Projects instead of Avid MEDIA is to FAKE the Avid MediaFiles folder. Create a dummy of it using a texteditor so that the Avid THINKS that there is a MediaFiles folder, because you don't want it to create a NEW one, but to have to be something that CAN'T be written to.
THAT solves the problem of accidentally writing media to a drive where you want NO media, but sometimes the real problem is to allow SOME people to read and write media to a specific drive or workspace, but not EVERYONE. I don't have a solution for THAT one, but it's clearly something that would be good. In Unity, I think you can assign permissions. Not so much with shared drives or specific drives on a system other than Unity.
Steve Hullfish
contributor: www.provideocoalition.com
author: "The Art and Technique of Digital Color Correction"
On Jun 10, 2012, at 5:25 AM, Roger wrote:
> My specific concern was inexperienced users chucking media on to drives or partitions that they are not supposed to be using. For instance, in a newsroom, there is often a Unity workspace designated for shared projects, not media. Your idea would not work as the Avid system would simply create a new MediaFiles folder.
>
> On 10 Jun 2012, at 03:03, Steve Apter wrote:
>
> > I always just add the project name to the end of the Avid Media Files folder when I want to keep it separate. This disables the folder from further writing.
[Non-text portions of this message have been removed]
No comments:
Post a Comment