Network rendering will not work - 5b

LittleJeff wrote on 8/13/2004, 1:47 AM
I've seen many threads like this. Someone says "I can't get network rendering to work no matter what I try." And then about 10 posts later, they say they got it to work, as if by magic. Unfrotunately, I don't have time for magic, and nothing I try is working anyway.

I have installed 5.0b on three machines. I can answer "yes, I'm sure" to all the standard questions. Did you define the domain suffix? Are your folders where the media resides shared? Did you do the file mappings on the editing machine? Do you have the server running on the rendering machines?

When I start a network render, whether it's distributed or non, the editing machine IS able to communicate with the renderers, because the second Vegas 5.0 window pops up on the rendering machine, and it looks like it's going to do something. After the progress bar hits 20% on the rendering machine, it quits and says "failed". The log file says that it cannot open the project in the shared folder, which is a bunch of you-know-what, because I can open the stupid folder from the rendering machine using the universal path and create, open, and edit files to my heart's content.

I have a very large project. Network rendering would save my life. I don't understand why the renderer says it can't open the project.

Comments

johnmeyer wrote on 8/13/2004, 8:53 AM
5.0b makes the setup easier, but it is still pretty convoluted. Here are links to some old threads, where I shared what I knew at the time. Some of the stuff about file mapping no longer applies, since 5.0b can do this automatically.

Network render bugs, suggestions, & solutions

Also:

Network Render Directions

Please note that if you updated to 5.0b, you must have 5.0b running on ALL computers involved in the network render. If you have only one copy of Vegas, you can have this installed on two other computers (three total), and that you must use the same serial number and user information on each computer.
LittleJeff wrote on 8/13/2004, 12:32 PM
Thank you, John. I have read both of the threads you referenced in detail on numerous occasions. Unfortunately, I must have some issue that isn't resolvable by normal means. I have tried using two different computers on my LAN as remote renders, and they both exhibit the same behavior. I am running 5.0b with the same serial number on both machines. What is happening is that the remote renderer is complaining that it cannot open the temporary VEG project that the network rendering process creates (or tries to) in the destination directory. Yes, the directory is shared. Yes, it's mapped. Yes I can see it, write to it, and read from it on the remote machine. I have no idea what the problem is.
johnmeyer wrote on 8/13/2004, 6:17 PM
Maybe someone from Sony can suggest something. They have been pretty good about helping people through some of these tougher situations.