Your experience with teamrender

[lollolo]

I just rendered a scene two times. I only chanced the settings in the Team Render tab of the render settings.
First:
Client update interval: 10s
Maximum size: 25MB
Time: 26:20

Second:
Automatic
Time: 53:04

The different is just HUGE!
Something is completely strange with the Automatic mode turned on.

[HFPatzi]

Yeah, I usually bump up the settings to 20s and 150MB. But i don't get the system behind corona's teamrenderer anyways. If you look at the console output it all looks mixed up :D

But I noticed another thing, which might be a reason why sometimes my renderclients just quit (not the whole computer, only C4D-Teamrenderclient) without any errormessage.
This only happens when i render image in final resolution, which is 9000 x 6000 pixel for me. Other (smaller) resolution are rendering without any problems. I also noticed, that there are some communication errors in the console output:

Code: [Select]

2018/12/13 08:23:53  [Corona4D] [TR] Sending chunk 2/5 to the server
2018/12/13 08:23:59  [Corona4D] [TR] Finished chunks: 1/5
2018/12/13 08:24:00  [Corona4D] [TR] Sending chunk 3/5 to the server
2018/12/13 08:24:16  [Corona4D] [TR] Frame synchronization failed: Communication Error
2018/12/13 08:24:18  [Corona4D] [TR] Sending chunk 3/5 to the server
2018/12/13 08:24:18  [Corona4D] [TR] Frame synchronization failed: Communication Error
2018/12/13 08:24:20  [Corona4D] [TR] Sending chunk 3/5 to the server
2018/12/13 08:24:20  [Corona4D] [TR] Frame synchronization failed: Communication Error
2018/12/13 08:24:21  [Corona4D] [TR] Sending chunk 3/5 to the server
2018/12/13 08:24:22  [Corona4D] [TR] Frame synchronization failed: Communication Error
2018/12/13 08:24:23  [Corona4D] [TR] Sending chunk 3/5 to the server
2018/12/13 08:24:24  [Corona4D] [TR] Frame synchronization failed: Communication Error
2018/12/13 08:24:25  [Corona4D] [TR] Sending chunk 3/5 to the server
2018/12/13 08:24:26  [Corona4D] [TR] Frame synchronization failed: Communication Error
2018/12/13 08:24:27  [Corona4D] [TR] Sending chunk 3/5 to the server
2018/12/13 08:24:27  [Corona4D] [TR] Frame synchronization failed: Communication Error
2018/12/13 08:24:29  Peer-to-Peer-Statistik:
    > CAD660023 Downloadgeschwindigkeit 4.83 MiB\s (1x)
    > CAD660027 Downloadgeschwindigkeit 5.75 MiB\s (2x)
    > CAD660022 Downloadgeschwindigkeit 7.45 MiB\s (7x)
    > mac_5s Mac Pro Downloadgeschwindigkeit 10.21 MiB\s (3x)
    > CAD660025 Downloadgeschwindigkeit 10.26 MiB\s (1x)
    > PC01 Downloadgeschwindigkeit 21.11 MiB\s (5x)
    > repronorms Mac Pro Downloadgeschwindigkeit 52.88 MiB\s (4x)
    > CAD660029 Downloadgeschwindigkeit 56.27 MiB\s (2x)
    > CAD660024 Downloadgeschwindigkeit 65.67 MiB\s (6x)
Peer-to-Peer-Statistik Ende
Polycount or Number of Objects do not seem to be a problem here, since my renderclients also quit on a fairly simple scene (1 cube and some deformed and extruded text).
Maybe some of you can proof my thesis.

Greetings,
Moritz

[CBAS VISUAL]

I've the same probleme "[Corona4D]

Frame synchronization failed: Communication Error" when i render image in high def. The clients quit the render without reason.

[gigabright4d]

I've the same probleme "[Corona4D]

Frame synchronization failed: Communication Error" when i render image in high def. The clients quit the render without reason.

I had the same problem too when render the final image (3325 x 4200 px)
the setting was 20s and the maximum size: 150 MB

but when I changed the maximum size to 50 MB, I had no error at all.
So I assume the maximum size is too large that cause the problem.

[HFPatzi]

So I assume the maximum size is too large that cause the problem.

That's my second guess. Problem with smaller chunks however is the increase in render time.  Need against misery i'd say ;-)

One question though: Has anybody tried the latest corona build?

[lollolo]

So I assume the maximum size is too large that cause the problem.

That's my second guess. Problem with smaller chunks however is the increase in render time.  Need against misery i'd say ;-)

One question though: Has anybody tried the latest corona build?

I guess too. I had the same problem, thats why I changed the maximum size to 25MB.
I'm using the Final Beta. (I think this is the latest build)

[gigabright4d]

So I assume the maximum size is too large that cause the problem.

That's my second guess. Problem with smaller chunks however is the increase in render time.  Need against misery i'd say ;-)

One question though: Has anybody tried the latest corona build?

I agree with you about the render time, larger maximum size renders faster than smaller size.
Ps. I use the latest dally build (corona-3-c4d-daily-2018-12-06)

[Beanzvision]

So I assume the maximum size is too large that cause the problem.

That's my second guess. Problem with smaller chunks however is the increase in render time.  Need against misery i'd say ;-)

One question though: Has anybody tried the latest corona build?

I guess too. I had the same problem, thats why I changed the maximum size to 25MB.
I'm using the Final Beta. (I think this is the latest build)

The latest build can be found here guys:
https://drive.google.com/drive/folders/17msYVIuJPs___3w192dpuyeF2MjW1B__

[HFPatzi]

I just tested teamrtendering (9000 x 6000 px) with a max size of 50MB and a refresh-time of 20s and it renders without any problem. So for a start, i'll teamrender with 50MB max size. But i have to say, the whole corona/teamrendering topic is a little bit confusing ;)
A easier to use solution in the final version would be much appreciated :)

Have a nice weekend all together!


________
Edit:

While finishing the teamrender (waiting for chunks) i noticed that some of the clients finished way earlier than others (same hardware). As i checked the console-outputs of them, it seems that some network communication errors happend. Don't know if this is something i should be afraid of but anyhow attached 2 example logs. One from a client with and one from a client without network errors. I just censored some of the asset names ;)

[jojorender]

Did you guys notice that these client disconnects happen right around the same time the "low memory" warning pops up?

I tried all settings 20s/150MB - 10s/50MB on a image 4500x3000 using only 1 client machine to rule out a network bottleneck.
Every setting i tried had disconnects. Not easy to test, since it always takes a while till it happens.