Scenarist 3.1 and networking

[Corion]

Hello,

When authoring with Scenarist (we use version 3.1) we have always kept the assets on a local drive. I'd been told that working from assets on a network drive lead to "problems with subtitles" (the guy that first looked into it has long since moved on).

I'm sure I've heard of authoring houses working with assets on network drives so I tried compiling a project I'm working on from the network.

The project is meant to have 2 subtitle streams (Stream 1 is German, Stream 2 is French) but on compiling it indeed has 2 streams but the second stream is simply a duplicate of the first (ie both are German).

I suppose my question is, does anybody work with Scenarist 3.1 using assets on a shared network drive and if so have you ever encountered this problem?

Thanks


PS. If you're wandering what the problem is with working locally, the network drives are backed up on a daily basis, and besides we work off the network for menu design, audio, etc.

[dgoodbourn]

Working from network drives should in theory be fine so long as your network is up to the constant data traffic. It will be a lot slower than a local SCSI array (or 2 to be fastest!!), but it will work.

You're right, there are authoring companies in London that work from network drives.

If the speed isn't an issue then I'd say do it, as the backups are a great idea.

Good luck.

D.

[Corion]

Aha just needed to reimport the offending second stream. The network's 1gbit so it's not too bad. Parsing and muxing is a fair bit slower but I now have an extra drive on which to compile the video_ts so it probably just about evens out.