Hi
We use tandemvids successfully, apart fro the go pro issues, which we are currently testing the workaround.

The issue that we have is with the archiving, when we have an archive set up to go to a network drive, the initialisation of tandemvids takes a super long time. This even happens when the box is unticked, I can only think that it is trying to index the archive over the network every start. the workaround is to unplug the network cables when using tandemvids. has anyone had any experience of this?

Many thanks

Chris

Hi Chris,

Sorry for the delay. I've just got back from a boogie interstate.

I can't think of any reason for this. I don't index any archive locations during start up. As soon as I get a chance, I'll do some testing and step through the initialisation code to see if I can see what may be happening. If Vegas is set to open the previous project and the location doesn't exist, it may be slow to respond.

The GoPro issue still exists although we don't see it on our live system, which is running Vegas 9. I've built a few systems, where I've had to implement the workaround but others have been fine. I really don't know what causes the crashes when rendering to AC3 with GoPro footage.

Mick

No probs, hope you enjoyed your trip.

OK thanks for looking into this, There are no errors received during the startup, but i could film with and without if that helps

Cheers

Chris

I've had a really good look at this and stepped through all the initialisation code. I've also tested it using archive locations on a Network drive and then purposely broken the Network.

It doesn't make sense during initialisation but when shutting down, TandemVids copies the latest database to the archive location. A large database on wireless takes time to copy across. There must be something else causing the issue. TandemVids doesn't check if the archive locations exist during initialisation, it just loads them from the database. If there is an issue, it won't be picked up until the project is actually archived or TandemVids is closed.

Can you please confirm I have the issue correct? If the archive locations on the archive tab are empty, everything is fine, but as soon as you add an archive location on a Network drive, the next time TandemVids starts, it will be slow?

Does this happen even if you haven't actually archived a customer?

I have other customers using archive locations on NAS servers so I'm sure we'll resolve the issue.

One thing playing in the back of my mind is a firewall issue. You haven't blocked Vegas from the Internet or Network by any chance?

Mick

I needed to map a drive to avoid an error when adding a Network archive location. This is due to the line of code that retrieves the volume label for the drive.

Mick.

Hi
4 months later!

The drive was mapped as Z:

It still happens when the archive box is unchecked, the only way to stop it was to just unplug the network cable, this was after the archive so we can't really check with no customers archived any more

Has anyone else had any problems with this?

I haven't seen anyone else with this issue.

Are you referring to the archive folders defined on the Archive tab or the Local projects folder defined under Tools -> Options -> Files?

You don't have the Working folder set to the Network drive do you?

Can you please confirm I have the issue correct? If the archive locations on the archive tab are empty, everything is fine, but as soon as you add an archive location on a Network drive, the next time TandemVids starts, it will be slow?

Mick