environment (NC 9.04 and Isis 7000 though).
It's driving me nuts!
Bye,
Christian
--
Sent from my phone. It's got a rotary dial.
On Jan 26, 2012 8:36 PM, "Roger" <rogershuff@yahoo.co.uk> wrote:
> **
>
>
> OK - if I get you right - editors may work on any machine, may wish to
> change settings on the machine they are working on, then have MC save the
> updated settings on the server to be able to use the modified settings on
> another workstation? This should work as you describe - in the situations
> I've been in we've used Group settings so that users can't mess up the
> settings we wanted them to use. The settings are read from the server and
> however they mess them up, they are not saved and come back as new every
> time. I'll be in a room with several machines on a network tomorrow so I'll
> see if I can test Personal settings.
>
> On 26 Jan 2012, at 15:19, Christian Foerster wrote:
>
> > Sorry if I was unclear. I do want the editors to change their
> > settings, so Personal is the way to go (each editor would have their
> > individual setting, for testing I created one).
> >
> > All workstations should be looking at the same setting, right? That
> > way if you change something, it will propagate the other workstations
> > automatically?
> >
> >
> > Bye,
> > Christian
> >
> > On Thu, Jan 26, 2012 at 14:19, Roger Shufflebottom
> > <rogershuff@yahoo.co.uk> wrote:
> >>
> >>
> >>
> >> It's been a while since I did this but I've used this process in
> >> Newsrooms. I'm not clear from your mail whether you want individual
> >> users to be able to change their settings or not. If not, make a Group
> >> setting and do what you've done. If you DO allow editors to change, get
> >> them to re-export to a different folder on the server and see if that
> >> works. Otherwise all the workstations are looking at the same setting.
> >> If I have time, I'll test this.
> >>
> >>
> >>
> >> On 26/01/2012 11:18, Christian Foerster wrote:
> >>>
> >>> Hi all,
> >>>
> >>> we have just built an ISIS 5000 installation with 5 MC 6 (Win7 64)
> >>> clients. We want the user settings to be saved on the server and
> >>> propagate to the serveral workstations.
> >>>
> >>> I have created a User Setting on one workstation, exported to the
> >>> server (Personal -- auto-save and auto-load), imported it on another
> >>> workstation.
> >>>
> >>> Changed user settings will not be stored on the server, this means a)
> >>> they don't propagate and b) they are not even available on the
> >>> workstation they were created on when reloading the user.
> >>>
> >>> All workstation will always use the user settings in the state thy
> >>> were first exported at (because no change is saved to the server).
> >>>
> >>> Any clues as to what I'm doing wrong?
> >>>
> >>> Thanks,
> >>> Christian
> >>>
> >>> --
> >>> http://www.filmeschneider.de
> >>> http://www.avidscreencast.com
> >>>
> >>>
> >>
> >> --
> >> With Best Wishes,
> >> Roger Shufflebottom
> >> +44 7973 543660
> >>
> >> [Non-text portions of this message have been removed]
> >>
> >>
> >
> >
> >
> >
> > --
> > http://www.filmeschneider.de
> > http://www.avidscreencast.com
> >
> >
> > ------------------------------------
> >
> > Search the official Complete Avid-L archives at:
> http://archives.bengrosser.com/avid/
> > Yahoo! Groups Links
> >
> >
> >
>
> With best wishes,
> Roger Shufflebottom
> rogershuff@yahoo.co.uk
> +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
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/Avid-L2/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/Avid-L2/join
(Yahoo! ID required)
<*> To change settings via email:
Avid-L2-digest@yahoogroups.com
Avid-L2-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
Avid-L2-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
No comments:
Post a Comment