So if you use the fake folder trick on the projects drive and give read
only access to the other drives... Then there shouldn't be any real
problem... And if they get scared by an error message... You tell them
what's up.
On Sunday, June 10, 2012, Roger wrote:
> Also, the fake folder trick does not hide the partition, it simply throws
> an error if a user attempts to create media. Fine if you know about it but
> a bit scary if not.
>
> On 10 Jun 2012, at 22:47, namyrb wrote:
>
> > I believe the official way (at least for unity/Isis) is user groups. I
> > believe any networking solution should let you assign permissions to
> > specific drives for specific users. So if you don't want inexperienced
> > users writing to the media drives you just have them sign into the client
> > with the username that has read-only access to the media drives.
> >
> > On Sunday, June 10, 2012, Axel Jansen wrote:
> >
> > > or maybe save Media Creation Settings in your Site Settings?
> > >
> > > Am 10.06.2012 20:54, schrieb Roger:
> > > > Your 'solution' is what even the Avid engineers use, Steve, but it
> is a
> > > bodge as I'm sure you appreciate. Allowing selected users access to
> some
> > > workspaces/partitions is something that needs to be addressed properly.
> > > >
> > > >
> > > > On 10 Jun 2012, at 19:53, Steve Hullfish wrote:
> > > >
> > > >> 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]
> > > >>
> > > >>
> > > > With best wishes,
> > > > Roger Shufflebottom
> > > > +44 7973 543 660
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > > >
> > > >
> > > > ------------------------------------
> > > >
> > > > Search the official Complete Avid-L archives at:
> > > http://archives.bengrosser.com/avid/
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > >
> > > --
> > >
> > >
> > >
> > > Axel Jansen | Eifflerstr. 6 | 22769 Hamburg | 040 315551 | 0151
> 50007450
> > >
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > Search the official Complete Avid-L archives at:
> > > http://archives.bengrosser.com/avid/
> > > Yahoo! Groups Links
> > >
> > >
> > >
> > >
> >
> > [Non-text portions of this message have been removed]
> >
> >
>
> With best wishes,
> Roger Shufflebottom
> +44 7973 543 660
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------
[Non-text portions of this message have been removed]
No comments:
Post a Comment