Network Render - Multiple Issues

[Mark Tone]

Hey,

We're using After Effects CC on OSX and Adobe Media Encoder CC on Windows. The windows machine is the server with a shared folder set up on the desktop, which the OS X machine can access.

The OSX machine collects the files, selects the shared network folder as the destination.

AME fails to detect the new project unless we move the file back out of the directory (which contains footage and the AE file, which the collect process made. it stores the files in a sub directory to the folder that you actually select with the name of the project as the folder name).

Not only that, but when it renders certain assets are missing and need to be re-linked. Mainly certain solids and assets Sometimes if we open it after collecting on the Windows machine through After Effects before Media Encoder, it will magically find the assets and render correctly. Otherwise if entered straight in to AME it will lose the assets.

Any ideas? Other than that it seems like a good process, but just a few quirks that need ironing out but the resource on the internet for network rendering is vague or just not there.

Thanks in advance...

[ToolfarmJP · Accepted solution]

Hello,

The instability may come from the number of the concurrent access with the shared PCs. If you use a Mac server OS as a shared directory, it is usually unlimited. But if you use a client OS, the limitation is set. I guess 10 for Mac and 20 for Win.

You also have an option to use a rendering dispatcher tool like this below to make your system more stable.

brave rabbit » Pipeline Overview

DEADLINE®

[Mark Tone]

Thanks for that, will do a bit more reading on the subject!