Adding to the volumes of discussion and questions on network rendering...
I have a simple setup with two computers on my LAN. There are no firewalls to worry about. I have my remote machine added as a renderer in the network rendering service of my host machine. Since I find all the mapping stuff quite confusing and rather annoying, I simply map a drive on my remote machine that points to the root of a drive on the host machine with the same drive letter. (Yes, I've read all the postings about the bug that drops the initial letter in the file name, black frames, blah blah blah. That doesn't happen to me because I don't save my projects in the root. I just map the drive to the root.) Anyway, the net affect is that on both the host and the remote machines, all the file paths are exactly the same, right down to the drive letter.
So, I initiate a distributed render, and it seems to connect and "get rolling" just fine. The remote machine receives the job and shows its status as rendering, as does the host machine, which is also a renderer and the stitch host. The problem is that the remote machine never finishes the first segment. The progress window appears, and the bar climbs to 30%, then it "flashes" for a moment, for lack of a better word, and then goes back to 0 to 3% and starts climbing again. This happens ad infinitum, until I kill the process on the remote machine. 0 to 30 and back again, over, and over, and over.
In the meantime, the host machine happily renders the entire project, which defeats the purpose of having network rendering.
Anyone have any clues?
I have a simple setup with two computers on my LAN. There are no firewalls to worry about. I have my remote machine added as a renderer in the network rendering service of my host machine. Since I find all the mapping stuff quite confusing and rather annoying, I simply map a drive on my remote machine that points to the root of a drive on the host machine with the same drive letter. (Yes, I've read all the postings about the bug that drops the initial letter in the file name, black frames, blah blah blah. That doesn't happen to me because I don't save my projects in the root. I just map the drive to the root.) Anyway, the net affect is that on both the host and the remote machines, all the file paths are exactly the same, right down to the drive letter.
So, I initiate a distributed render, and it seems to connect and "get rolling" just fine. The remote machine receives the job and shows its status as rendering, as does the host machine, which is also a renderer and the stitch host. The problem is that the remote machine never finishes the first segment. The progress window appears, and the bar climbs to 30%, then it "flashes" for a moment, for lack of a better word, and then goes back to 0 to 3% and starts climbing again. This happens ad infinitum, until I kill the process on the remote machine. 0 to 30 and back again, over, and over, and over.
In the meantime, the host machine happily renders the entire project, which defeats the purpose of having network rendering.
Anyone have any clues?