Vegas 5.0a hangs with incorrect file mappings specified in Network Render Service?

jelsberry wrote on 5/31/2004, 7:01 AM

I'm having trouble getting the network rederer to work correctly. I have a client machine and its status is ready. What puzzles me is that I can't seem to get the file mappings right. I'm not using the root directory of my share, so I can rule that out from the get go.

All of my media dependencies are located in subdirectories of a share named vegas. When I specify only the root of the share, Vegas hangs. When I specify the output directory only (where my rendered avi file will go), the render job is sent to the remote client, but fails because it can't find the media dependencies. When I add another mapping to the media directory, Vegas hangs. Very strange. So far, the product seems inordinately buggy.

Here's where my data is located and the share info:

share: d:\vegas (vegas)
output directory: d:\vegas\output (\\nora\vegas\output)
media directory: d:\vegas\input\dv (\\nora\vegas\input\dv)

Here's a synopsis of what happens with different file mappings:

1) hangs
d:\vegas --> \\nora\vegas

2) remote client fails to load media
d:\vegas\output --> \\nora\vegas\output (can't find media assetts)

3) hangs
d:\vegas\output --> \\nora\vegas\output
d:\vegas\input\dv --> \\nora\vegas\input\dv

Comments

johnmeyer wrote on 5/31/2004, 10:27 AM

I assume from what you said that you already read my posts that contain recommendations on how to get around some of the problems. I have come to the conclusion that this feature isn't worth the hassle. The render time improvements that most people have reported are minimal; the setup time is, as you are finding, inordinate -- and it must be done almost every time you do a new render (unless your media assets and output files are always in the identical directories). The remote render machine sometimes doesn't come back on line on subsequent re-renders. Also, many people are looking for help reducing the MPEG encoding time, and because of both license and technical shortcomings there is no solution for this. The network render feature only helps with renders.

My bottom line: if you are doing a lot of compositing, bezier masks, blurs, and other things that require HUGE amounts of rendering, and you have at least two really fast remote computers, then it is probably still worth it to spend the time to set up this feature. Otherwise, save yourself considerable time and aggrevation and wait until Sony smooths out the problems.