View Single Post
Old 22nd February 2018, 18:31   #15550  |  Link
GZZ
Registered User
 
Join Date: Jan 2002
Posts: 581
Quote:
Originally Posted by Viper714 View Post
Ahh!! Okay I do use Distributed Encoding (DE). So I looked at the file "DE_log_pass1.txt and found the following

PHP Code:
Node Address   192.168.1.5:1000
Encoded Chunks 
21 of 125 (17%)
Encoded Frames 30244
Encoding Speed 
9.84 fps
Node Work Time 
00:51:12
-----------------------------------
Node Address   192.168.1.5:2000
Encoded Chunks 
21 of 125 (17%)
Encoded Frames 30243
Encoding Speed 
9.88 fps
Node Work Time 
00:51:02
-----------------------------------
Node Address   192.168.1.6:1000
Encoded Chunks 
26 of 125 (21%)
Encoded Frames 37468
Encoding Speed 
12.98 fps
Node Work Time 
00:48:06
-----------------------------------
Node Address   192.168.1.6:2000
Encoded Chunks 
26 of 125 (21%)
Encoded Frames 37830
Encoding Speed 
13.28 fps
Node Work Time 
00:47:28
-----------------------------------
Node Address   192.168.1.8:1000
Encoded Chunks 
31 of 125 (25%)
Encoded Frames 44623
Encoding Speed 
15.88 fps
Node Work Time 
00:46:50
----------------------------------- 
So if I add the chunks encoded by each machine I get 125. When looking in the "Chunks" folder, it starts from 1 and continues sequentially to 125. All of the chuck numbered files "###.264" range from 19,699 through 180,271.
So I guess this is good as it does not show any missing chunks.
The problem before the FFMpeg fix, was incomplete chuncks. Lets say you have chunck 4 and it crash midway, then it would only have encoded like 40% of the expected frames in the chunck, but before version 1.22.1 it would assume the chunck was completed and when it merge them all together the audio would go out of sync after this incomplete chunck. I normally just check the complete file and see if audio is in sync for the last part of the movie and if so, then everything should be fine.
GZZ is offline   Reply With Quote