portability PC move

[Nigel Packer]

Hi all

New to all this so be gentle with me. I have IT experience but slowly getting up to speed with this AV stuff.

The people I do work for did have a AV show running 5 projectors with your software on it. The PC/media server has developed a fault on the PCI3 slot so I need to move content and software to a new machine.

New one is Windows 10 Pro old is Windows 7 home edition. I notice a USB device with a ring on it, is this the licence??

My question is what would be involved transferring Watchout to this new machine and would I be able to keep all configuration. Is it just a case of installing the correct version on the new PC and copying files over ??

Nigel

 

[jfk]

2 hours ago, Nigel Packer said:

Hi all

New to all this so be gentle with me. I have IT experience but slowly getting up to speed with this AV stuff.

The people I do work for did have a AV show running 5 projectors with your software on it. The PC/media server has developed a fault on the PCI3 slot so I need to move content and software to a new machine.

New one is Windows 10 Pro old is Windows 7 home edition. I notice a USB device with a ring on it, is this the licence??

Most likely. This might help: https://forum.dataton.com/topic/3633-everything-i-think-i-know-about-dataton-v5-and-v6-license-keys/

Quote

My question is what would be involved transferring Watchout to this new machine and would I be able to keep all configuration. Is it just a case of installing the correct version on the new PC and copying files over ??

Nigel

 

Yes, install the correct version, no do not copy the files. (While it may be possible to just copy the files over, success is fully dependent on the organization of the original programmer). 

Watchout includes a function, "Consolidate To ...", specifically for moving shows. This function automatically adjusts file references to ensure portability. The User Guide gives a good description on use of the consolidate function.

[Nigel Packer]

That's great

Thank you for the reply

1st it looks like a micro-key, yes that helps.

2nd I will do that, give me few days as i'm on other things at the moment and I will let you know how I get on.

Nigel

[Steve Farris]

Hi JIm

On 7/3/2019 at 9:37 AM, jfk said:

Most likely. This might help: https://forum.dataton.com/topic/3633-everything-i-think-i-know-about-dataton-v5-and-v6-license-keys/

Yes, install the correct version, no do not copy the files. (While it may be possible to just copy the files over, success is fully dependent on the organization of the original programmer). 

Watchout includes a function, "Consolidate To ...", specifically for moving shows. This function automatically adjusts file references to ensure portability. The User Guide gives a good description on use of the consolidate function.

What is the method to do this in Version 7?  I don't see the "consolidate to" function in the menu.

Steve

[jfk]

Thanks for reviving a five year old thread. i do not know the answer to your question for v7.

Seems quite a popular question. Recently, there are 2 or 3 current forum posts asking essentially this question. 

Here’s hoping someone better versed in v7 intricacies assists.

[RBeddig]

My work-around is so far:

Create a project folder for each project and save your show file here.

.../myProject

Create a sub folder "/.wo" and change the working directory in the producer to this path when starting to program it. The leading dot is important!

.../myProject/.wo

This folder should now hold all assets of your project.

Then take this project folder to the new computer. You may have to tell the producer again where the working directory sits if you've changed the path.

Since the asset manager will always copy every asset into this folder you won't get into the situation that some files from external drives haven't made it into your show folder.

Hope this helps.

 

[Steve Farris]

20 minutes ago, RBeddig said:

Create a project folder for each project and save your show file here.

.../myProject

Create a sub folder "/.wo" and change the working directory in the producer to this path when starting to program it. The leading dot is important!

.../myProject/.wo

This folder should now hold all assets of your project.

I was thinking of something like that.  Since the .wo directory lives in the WATCHOUT7 folder by default, I was thinking to copy that folder to the new machine.  Your method seems a bit more elegant as everything is now in the /myproject folder.  I'll give that a try.

Do you know what would happen if I copy the .wo folder to my project folder and then change the working directory once I am in the middle of a project?  I guess I'll find out since I will try that...  Thanks for the idea.

Steve

[Steve Farris]

 

12 hours ago, RBeddig said:

My work-around is so far:

Create a project folder for each project and save your show file here.

.../myProject

I can report success using your method.  I have a couple details to add that I figured out with a couple missteps.

Since I am in the middle of a project, I did the following (everything was backed up before starting the process).

- On the Producer I have been using to edit, I copied the .wo directory from the WATCHOUT7 folder to ~/myproject folder

- I deleted everything from the .wo folder in WATCHOUT7 (not sure if this was necessary, just trying to be thorough)

- I started a new show (with manager running) and changed the working directory to the new .wo folder in ~/myproject

- Opened the current show file

- Checked that the working directory was pointing to ~/myproject/.wo (it was)

- First I assigned the asset manager to the current machine (it's critical to do this first!)

- Changed the Director to the current machine.

Now all my cues have valid files associated with them.  I had to reassign my runners and I was good to go.

Hopefully Dataton will create a more elegant solution, this was not intuitive or easy!

Steve

[Josef Swanberg]

The correct way to do it in WATCHOUT 7 is to use the Export Assets feature. You can read about it here:
https://docs.dataton.com/watchout-7/am/asset_manager.html

[RBeddig]

7 minutes ago, Josef Swanberg said:

The correct way to do it in WATCHOUT 7 is to use the Export Assets feature. You can read about it here:
https://docs.dataton.com/watchout-7/am/asset_manager.html

In real life, we're often working on a number of projects at the same time and we MUST NOT mix assets of those projects.

Exporting assets is fine as long as you only work on one project and this is finally done. If it isn't done, we need to keep the asset selections apart from each other and the only usable way I figured out so far is to use a separate location for each /.wo folder.

[Steve Farris]

On 9/24/2024 at 5:22 AM, Josef Swanberg said:

The correct way to do it in WATCHOUT 7 is to use the Export Assets feature. You can read about it here:
https://docs.dataton.com/watchout-7/am/asset_manager.html

There is not much information in the manual page you reference on how to use this feature, aside from saying it exists.  I initially tried to use the import/export feature when I was testing how to run a backup server, but it doesn't seem to be designed for my use case.  The import/export feature seems to work best if I need to take a completed show to a different machine / system.  However, trying to keep a backup system updated and in sync with a primary system doesn't seem to be how it is designed.  Perhaps I need more understanding of how to do this as intended.

In any case, running a backup director and a primary director on the same network leads to all kinds of issues.

[jfk]

Agreed, you can not run WATCHOUT 7 primary and backup on the same  network.

Consider, once your show is completed, the show will continue to run correctly if the asset manager fails or is removed. So does the asset manager need to be redundant? If not, run only one asset manager for both primary and backup. place the asset manager on its own server with either two or three NICs - one for primary, one for backup, and if needed one for internet or other network where assets may be accessed. Unlike other components in WATCHOUT 7, the asset manager has NIC settings. As long as the Windows aspects are setup properly, the asset manager will not cross connect the two or three networks while maintaining access to all. I believe one active asset manager will keep independent shows on independent networks up to date when changes are made. Create a windows shared folder on the asset manager computer to move .watch files between networks. Does that get you any closer to your goals?

[artboy]

5 hours ago, jfk said:

Agreed, you can not run WATCHOUT 7 primary and backup on the same  network.

Consider, once your show is completed, the show will continue to run correctly if the asset manager fails or is removed. So does the asset manager need to be redundant? If not, run only one asset manager for both primary and backup. place the asset manager on its own server with either two or three NICs - one for primary, one for backup, and if needed one for internet or other network where assets may be accessed. Unlike other components in WATCHOUT 7, the asset manager has NIC settings. As long as the Windows aspects are setup properly, the asset manager will not cross connect the two or three networks while maintaining access to all. I believe one active asset manager will keep independent shows on independent networks up to date when changes are made. Create a windows shared folder on the asset manager computer to move .watch files between networks. Does that get you any closer to your goals?

Can you explain what this means in more detail?

"...once your show is completed"

In WO6, this is the moment to do 'online', but in wo7, it goes on without doing this.

So when the " your show is com[leted"... I don't understand what it's like.

 

and you say also "asset manager has NIC settings"

What is the nic setting for assets manager?

Is choosing assets magager device in Produce?

[Steve Farris]

17 hours ago, artboy said:

Can you explain what this means in more detail?

"...once your show is completed"

 

I have to laugh, that was my exact thought when reading Jim's post.  My shows tend to run out of time, finished means the event is over.  Up until that point, I am always making modifications.

That said, Jim's suggestion makes sense.  I need to look at how that scenario will work.  I was already using a separate computer with 2 NICs in order to transfer files between primary and backup, if that machine could become the asset manager as well and create a solid fail over system it is worth considering.  One drawback is needing another license for the asset manager computer.

Is there a separate "asset manager" program, or would it run in producer without a director or any cues / displays?

[Josef Swanberg]

On 9/28/2024 at 7:18 PM, Steve Farris said:

Is there a separate "asset manager" program, or would it run in producer without a director or any cues / displays?

Just run "WATCHOUT Manager" on the computer you want to use as asset manager, locate the node in the network Devices window in your Producer, right click and select "Use Asset Manager", and the asset manager will run on that machine.

[Josef Swanberg]

On 9/27/2024 at 5:03 PM, Steve Farris said:

There is not much information in the manual page you reference on how to use this feature, aside from saying it exists.  I initially tried to use the import/export feature when I was testing how to run a backup server, but it doesn't seem to be designed for my use case.  The import/export feature seems to work best if I need to take a completed show to a different machine / system.

Whoever wrote that part of the manual probably thought it was quite self explanatory, but perhaps it could be elaborated a bit. The export functionality exports the selected assets, or all assets depending on the command you choose. They will be exported to a folder of your choice, on the same computer as the asset manager is running on, which may not be the same computer that is running the producer. Copy that folder, together with your show file to another computer. Then you can import those assets to an asset manager on that computer, and then you can open your show on that computer, and the imported assets will be used by that show.

You are right that this export/import functionality is not made for the backup server use case.

[Josef Swanberg]

On 9/24/2024 at 2:33 PM, RBeddig said:

In real life, we're often working on a number of projects at the same time and we MUST NOT mix assets of those projects.

Exporting assets is fine as long as you only work on one project and this is finally done. If it isn't done, we need to keep the asset selections apart from each other and the only usable way I figured out so far is to use a separate location for each /.wo folder.

How about arranging the assets in different folders in the asset window?

[RBeddig]

4 minutes ago, Josef Swanberg said:

How about arranging the assets in different folders in the asset window?

Hi Josef,

There are a few points which don't work that good in one Asset manager.

a) When I drag content into the asset manager, the content often doesn't land in the folder I have selected. If you already need sub-folders for different parts of the show or show dates etc., things can get very messy in short time and usually you have to do this with the client waiting behind you which adds to the stress level.

b) we sometimes work for competing clients. They don't want to see the assets of the competition on your screen.

c) In larger shows, the amount of data can get really big. If you have more than one project t in the same asset manager .wo folder, it can lead to the message "not enough space".

d) moving the assets later on to a storage server for archiving or just to another computer to take that one on-site can get complicated if you have to export a selection of folders instead of just the complete .wo folder. It would need time consuming checks that you really copied all necessary files. The old consolidation concept was way more usable for those cases.

/Rainer

[mindopera]

On 9/24/2024 at 5:33 AM, RBeddig said:

In real life, we're often working on a number of projects at the same time and we MUST NOT mix assets of those projects.

Exporting assets is fine as long as you only work on one project and this is finally done. If it isn't done, we need to keep the asset selections apart from each other and the only usable way I figured out so far is to use a separate location for each /.wo folder.

I am using the same method.  Creating a project folder with the WO file and within that folder I create a folder for native assets if I chose to keep the original assets and a folder .wo.  When I'm finished with the project I move the project folder to my storage server.    It would be nice if no matter what computer you opened the file from it would find file associated assets.