Welcome, Guest
Username Password: Remember me
  • Page:
  • 1

TOPIC: Import exported archive into different project space?

Import exported archive into different project space? 3 months, 2 weeks ago #168389

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 14275
  • 3 months, 2 weeks ago
On Win7, same user, same machine number, same machine, when exporting a project from Local Files and restoring in shared project space it's always locked.

Does anybody know how to unlock it?
It's better to travel well than to arrive...

Re: Import exported archive into different project space? 3 months, 2 weeks ago #168445

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 14275
  • 3 months, 2 weeks ago
Let me add a second question.

Assuming I'd work on a project in shared project space and I wish to import an archived sequence created on a single computer with only Local Files present.

How would I do that in order to avoid locked sequences?
It's better to travel well than to arrive...

Re: Import exported archive into different project space? 3 months, 2 weeks ago #168513

  • lghtwrks
  • OFFLINE
  • Platinum Boarder
  • Posts: 3641
  • 3 months, 2 weeks ago
there is/was a setting:

Administrator 1

to overcome left machines and locked edits.
(config.dat)
I did not test that with later versions.
It has to be set on only 1 machine afaik.

unlocking all edits on restore would make sense ...

ref www.lwks.com/index.php?option=com_kunena&func=view&catid=6&id=101956&Itemid=81#101967

s
Last Edit: 3 months, 2 weeks ago by lghtwrks.

Re: Import exported archive into different project space? 3 months, 2 weeks ago #168523

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 14275
  • 3 months, 2 weeks ago
lghtwrks, thanks fro answering.

Administrator 1 in config.dat doesn't seem to work anymore, at least I don't see any change in behaviour.

lghtwrks wrote:
unlocking all edits on restore would make sense ...


Absolutely!
It's better to travel well than to arrive...
Last Edit: 3 months, 2 weeks ago by hugly.

Re: Import exported archive into different project space? 3 months, 2 weeks ago #168603

  • lghtwrks
  • OFFLINE
  • Platinum Boarder
  • Posts: 3641
  • 3 months, 2 weeks ago
setting "administrator 1" wrkflw. could be ...
RMB-click any edit/bin(all edits): "unlock" all edits in the bin or select the target user(machine).

reminds me on "reread" all metadata for RED clips in 1 go. probably the implementation is more or less the same or not so far away.

s

Re: Import exported archive into different project space? 3 months, 2 weeks ago #168645

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 14275
  • 3 months, 2 weeks ago
setting "administrator 1" wrkflw. could be ...

I can't see anything changing with lower case "a" in config.dat, unfortunately.

RMB-click any edit/bin(all edits): "unlock" all edits in the bin or select the target user(machine).

Is this a feature request or an operational procedure?
It's better to travel well than to arrive...
Last Edit: 3 months, 2 weeks ago by hugly.

Re: Import exported archive into different project space? 3 months, 2 weeks ago #168650

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 14275
  • 3 months, 2 weeks ago
Let me add a third one.

I'm drowning in test projects created in my private workspace "Local Files". I would like to keep them directly accessible, but away from main project space.

Even with the Pro version I can't add private workspaces, only shared and that's where
"bells and whistles" for shared access appear.

What I can do is switching default Lightworks directory on OS level, but that can be done with the Free version as well and it isn't convenient.

Is it possible to add private project spaces, to avoid the problem with locked projects? Is there an easy method to move selected projects between project spaces? That would help much when organizing projects.
It's better to travel well than to arrive...
Last Edit: 3 months, 2 weeks ago by hugly.

Re: Import exported archive into different project space? 3 months, 2 weeks ago #168652

  • hugly
  • OFFLINE
  • Platinum Boarder
  • Posts: 14275
  • 3 months, 2 weeks ago
After all, I found an easy method from within Lightworks which allows to take over any shared project space locally accessible on OS level. It bypasses limited access of shared projects established by Lightworks entirely. That doesn't solve all problems listed above, but some and that's good for me for now. It doesn't need "administrator = 1".

Nevertheless, this might cause unintended behaviour on shared project spaces used by real work groups under certain circumstances, I think.
It's better to travel well than to arrive...
  • Page:
  • 1
Time to create page: 0.52 seconds
Scroll To Top