Open Vegas project file has to be locked for editing

mircea-r wrote on 6/26/2018, 3:57 AM

I have 2 Synology DiskStation NAS's (OS DSM 6.2, 'nix-ish) with various shared folders configured on them.
One of the NAS's serves as Active Directory controller.
The file sharing on the NAS's is done via SMB, min. ver. 2, max. ver. 3.
SMB Opportunistick Locks are enabled, although afaik they relate to local file caching and not directly to file locking.
I have added in the smb.conf files on both DSs' the kernel oplocks=yes

The network comprises of a few Windows 7 Pro and 10 Pro workstations.
On these workstations the NAS shares are mapped and authenticated with the above mentioned Active Directory users.

What I am trying to get done is this:

Once a Sony Vegas (v9) project file stored on these shares is opened by a user, no other user should be able to open that file, until it is closed.

I have spoken with tech guys oriented towards network storage and Samba/SMB. Their input was that Samba flags the open files correctly., as that is visible to me on the console output of the NAS's.

Microsoft support input was that this is not a Windows issue, as it receives those flags/attributes and forwards them to the opening application.

The files are Sony Vegas project files and the associated media files.

How could I go about achieving this file locking with Vegas? I have been browsing through all the options and preferences, but haven't found anything yet.

Thank you

Comments

john_dennis wrote on 6/26/2018, 10:11 AM

Since I'm retired after spending 39 years in the computer business, I find the whole question tedious, but my knee-jerk answer would be that you can't cause Vegas to lock the files on the NAS. Vegas doesn't lock the files even on local disks. I sometimes work on the the same project in two different sessions of Vegas on the same machine. Then, it's on me to maintain version control.

Now that I've moved your question back to the top of the queue, maybe you'll get an answer from someone who knows what they're talking about.

mircea-r wrote on 6/27/2018, 2:46 AM

Thanks for the answer.

My issue is not about Vegas locking or flagging the project file as open or read only, that is not Vegas's role, as you point out.
The file sharing service, i.e. Samba/SMB does that already. The Windows platform afaik forwards - or might forward - that file flag/lock/state to the application, ant the application does or does not take it into account.
The problem arises when two users try and succeed to open that same project file.
On the same NAS there are also some MS Office files that do deny opening if one is already open by a user. That is a feature of MS Office, to account for the file locks/flags. Ironically, 99% of the complaints over the internet are 'well, I do want to open an already open file'. My - let's say complaint is that I do NOT want to have the same project file opened by two users/machines at the same time.

I do agree that the sentence "How could I go about achieving this file locking with Vegas?" might have caused a bit of a confusion, as it should have been better phrased, like "How can I make Vegas take into account the file locking states/flags and deny file opening for an already open project file?"

fifonik wrote on 6/27/2018, 5:52 AM

> Once a Sony Vegas (v9) project file stored on these shares is opened by a user, no other user should be able to open that file, until it is closed.

Why do you think so? It's up to application to set or not to set locks. Have you read in Vegas manual that project file is locked while opened?

Anyway, I do NOT want Vegas lock project file that is opened.

Quite often Vegas users opening one project file more than once (open project + nesting the same project into another project so it would be opened again).

Developers might decide to implement such feature in the future (it must be optional if implemented in my opinion). Until then you cannot do what you want.

mircea-r wrote on 6/27/2018, 6:05 AM

I do not 'think' so.

That is what I would like to achieve.

'My' Vegas users have been asking for such a feature to be - if possible - enabled or functional for quite a while, using both civilized and heavy language, after they realized that one of them at some point in time can render useless some other user's work. Because such a project file locking feature does not work at this time.