Log in

View Full Version : RipBot264 v1.18.3 - Simple and easy to use GUI -> IPOD . PSP . CONSOLES . BLURAY


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 [360] 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429

tkwou
6th December 2019, 19:18
Hi Atak, I recently updated to v1.25.0. I just tried encoding the movie Life in DE mode and it failed with about 8 minutes left in the movie. When I look at the Chunks folder there are no *.264 files for the last 8 chunks. When I try to run each .cmd file manually I get these errors.

y4m[error]: bad sequence header magic
x2464[error]: could not open input file `_'

If I rerun the .cmd files for any of the completed chunks I get the normal .264 output. I don't understand what's going on. Should I just try recoding again from scratch?

stax76
6th December 2019, 19:29
This might be corrupted source file, bug in source filter or broken hardware or driver.

byteshare
6th December 2019, 19:46
When I say frame accurate, I mean that If I request frame 100 (with Trim function in script), I get frame 100. With ffms2 ,on other hand, you may get frame 99 or 101 or even totally corrupted frame.
GPU decoding is done via LSmash so results will be the same.
Okay, thank you for clarifying. The only time you use FFMS2 is HEVC, right? I recall thinking it was MPEG2 but you saying it is best with LSmash.

Atak_Snajpera
6th December 2019, 19:46
Hi Atak, I recently updated to v1.25.0. I just tried encoding the movie Life in DE mode and it failed with about 8 minutes left in the movie. When I look at the Chunks folder there are no *.264 files for the last 8 chunks. When I try to run each .cmd file manually I get these errors.

y4m[error]: bad sequence header magic
x2464[error]: could not open input file `_'

If I rerun the .cmd files for any of the completed chunks I get the normal .264 output. I don't understand what's going on. Should I just try recoding again from scratch?

open [chunk_number].avs in mpc-hc and see if there is some error message.

Atak_Snajpera
6th December 2019, 19:49
Okay, thank you for clarifying. The only time you use FFMS2 is HEVC, right? I recall thinking it was MPEG2 but you saying it is best with LSmash.

With latest version of lsmash I recommend to use it for ALL formats! Just forget about ffms. Lsmash is superior in almost every aspect.

slalom
6th December 2019, 19:54
Add MDegrain2 to custom section and you have all 3 in the same spot.
That's a good idea, just did!

tkwou
6th December 2019, 23:00
Thanks Atak, I just tried restarting from Ripbot264 and DE just finished the remaining 8 minutes.

jlpsvk
7th December 2019, 00:07
With latest version of lsmash I recommend to use it for ALL formats! Just forget about ffms. Lsmash is superior in almost every aspect.

can you be more concrete? :) still using ffms. :)

guest
7th December 2019, 00:42
You have to add the name of the command to the "Limit to following filters only", such as MDegrain1, MDegrain3, etc... It is the name (command) you use in the AVS script to call the function (filter). Not the name of the custom script or the name of the DLL/AVSI/AVS

Thanks heaps for this, byteshare :)

guest
7th December 2019, 07:42
So I would imagine that most of you have a reasonable collection of both unprocessed and processed movies & series, etc, which can add up to a LOT of Terabytes.

I would be interested to know what some of you (who are happy to oblige) have & use for storage, of said data ???

I have several reasonable capacity Supermicro storage servers, and a couple of Unraid "box's", but unfortunately, every so often there is a problem, and as a result, I get data corruption.

I don't really have too much backed up, so sometimes it's a complete loss :(, which can be very frustrating, especially if it was irreplaceable.

Anyway, I'm just curious...

GZZ
7th December 2019, 16:44
So I would imagine that most of you have a reasonable collection of both unprocessed and processed movies & series, etc, which can add up to a LOT of Terabytes.

I would be interested to know what some of you (who are happy to oblige) have & use for storage, of said data ???

I have several reasonable capacity Supermicro storage servers, and a couple of Unraid "box's", but unfortunately, every so often there is a problem, and as a result, I get data corruption.

I don't really have too much backed up, so sometimes it's a complete loss :(, which can be very frustrating, especially if it was irreplaceable.

Anyway, I'm just curious...


Should be in another thread or properly another group, try search forum as its out off topic for this thread.

tkwou
7th December 2019, 17:34
Hi Atak, I recently updated to v1.25.0. I just tried encoding the movie Life in DE mode and it failed with about 8 minutes left in the movie. When I look at the Chunks folder there are no *.264 files for the last 8 chunks. When I try to run each .cmd file manually I get these errors.

y4m[error]: bad sequence header magic
x2464[error]: could not open input file `_'

If I rerun the .cmd files for any of the completed chunks I get the normal .264 output. I don't understand what's going on. Should I just try recoding again from scratch?

Hi Atak, strange this just happened again. Processing stopped with just 2 chunks to go. With the missing chunks, the CombineChunk.cmd fails and video.264 is missing for the mux. I restarted the encode and again it finished the final 2 chunks and everything completed fine.

Atak_Snajpera
7th December 2019, 18:31
Hi Atak, strange this just happened again. Processing stopped with just 2 chunks to go. With the missing chunks, the CombineChunk.cmd fails and video.264 is missing for the mux. I restarted the encode and again it finished the final 2 chunks and everything completed fine.

You have some network issues or some instability in RAM/CPU...

Ryushin
7th December 2019, 18:57
With latest version of lsmash I recommend to use it for ALL formats! Just forget about ffms. Lsmash is superior in almost every aspect.

So the random frames happening around the end of the DE chunks should be fixed? Works for VC-1 too?

Atak_Snajpera
7th December 2019, 20:17
So the random frames happening around the end of the DE chunks should be fixed? Works for VC-1 too?

yes...

guest
8th December 2019, 01:43
Should be in another thread or properly another group, try search forum as its out off topic for this thread.

OMG, GZZ !!!

I knew that I was off topic for this thread, but I thought I'd just ask the question of the member's on THIS thread, as they MUST have some form of reliable storage.

So why you reply to state the bleeding obvious is a waste of your time, when for the same effort you could have said something like ....I have a Synology or Unraid backup....

guest
8th December 2019, 07:05
Is there a way to confirm that these "Custom" MDegrain filters are / or have been used ??
Other than creating some short test encodes and comparing the fps, kbps (whilst processing), or time taken to encode & final file size ??

Anyway, I did that, and here's some interesting results:-

a test tv episode, mp4, 17 minutes long.

MDegrain1 took 8:34m

MDegrain2 took 11:43m

MDegrain3 took 15:18m

they are ALL with MT enabled.

Then I ran MDegrain1 test again changing the MT settings.

with no MT, it took a "massive" 28:25m.

with MT enable, but using 16 threads took the original 8:34m

with 8 threads it took 8:17m

with 0 (which must be unlimited) it took 8:08m (on my 24 thread pc)

so going on that all the above times would be a touch faster if I had of had it set on 0 threads.

As for file size change:-

original file is 255,856kb @ 1,923kb/s

MD1 encoded is 303,196kb @ 2,192kb/s

MD2 encoded is 289,490kb @ 2,126kb/s

MD3 encoded is 281,275kb @ 2,126kb/s

No other filters or changes where made, using CRF 20, and ONLY the custom MDegrain filters.

Atak_Snajpera
8th December 2019, 13:26
Zero means number of physical cores If I remember correctly. So If your CPU is 12c/24t then value will be 12.
Regarding file size. You should try with noisy source. Difference will be much higher. MD2 should give you up to 1.8x bitrate reduction.

guest
8th December 2019, 13:57
Zero means number of physical cores If I remember correctly. So If your CPU is 12c/24t then value will be 12.
Regarding file size. You should try with noisy source. Difference will be much higher. MD2 should give you up to 1.8x bitrate reduction.

So does "0" automatically determine how many cores/threads are available ??

As "0" is the fastest of the settings I tried.

Also, I DID do a test on much noisier source (The Fifth Element), and there was a bigger file size/bitrate difference between the three.

guest
9th December 2019, 04:26
Me again,

I thought I'd run a few job thru RB today, on a pc that I was using successfully just last week, and I just keep getting errors, several time during the same job.

Cannot find file F:\Temp\RipBot264temp\job10\video.264
Error importing F:\Temp\RipBot264temp\job10\video.264:name=The Report 2019: Requested URL is not valid or cannot be found

It got thru approx 12 chunks before the 1st error, then after restarting the job, it got thru to chunk 24, then the next time I think it got thru quite a bit further, and errored again.

After several more attempts with different jobs, restarting the pc, I gave up, and went and did some cooking.

Atak_Snajpera
9th December 2019, 15:19
Auto-update 2019.12.09
Added: EncodingClient combines chunks with output file on fly as soon as they are encoded in correct order
Added: Audio profiles in Profile\Audio.txt
Changed: Jobless servers will be suspended only if ETA>60s (reason: reduce unnecessary suspend -> resume cycles)
Fixed: Excessive flickering of encoding status in EncodingClient
Fixed: EncodingClient didn't resume suspended jobless servers before starting second pass.
Fixed: EncodingServer didn't go to suspend mode again after previous resume

ReinerSchweinlin
9th December 2019, 16:03
Thanks for the update log. This is very helpful, please continue posting when updates are done :)

byteshare
9th December 2019, 16:54
So I would imagine that most of you have a reasonable collection of both unprocessed and processed movies & series, etc, which can add up to a LOT of Terabytes.

I would be interested to know what some of you (who are happy to oblige) have & use for storage, of said data ???
https://www.reddit.com/r/DataHoarder/
I use 1 to 1 backups

Is there a way to confirm that these "Custom" MDegrain filters are / or have been used ??
Other than creating some short test encodes and comparing the fps, kbps (whilst processing), or time taken to encode & final file size ??
Won't give you the benefits of a test encode (seeing the actual file results) but you can check:
(on a job) edit > AviSynth > Show Video Script > Look under the custom section that you see your script, then...
> Preview (first to make sure there are no errors in your script.
If no errors and your script is being loaded > AVS Meter to see the speed and such it runs at.
If you're still skeptical that your script isn't being used because of a mistake in your code that you're not seeing try removing it and then running the AVS Meter again, if there is no difference in speed (FPS) then something could be wrong with your script and then you'd want to run a test encode to see if there are any filesize differences, if none then it is likely your script or you're using a filter that is not having an impact either by design or by an error in your script.
(tip, on your script be sure "video" is somewhere after the "=" otherwise it isn't being using in the final video sent to the HEVC encoder, otherwise it is fine if you're using it for a mask, prefilter, etc...

original file is 255,856kb @ 1,923kb/s
MD1 encoded is 303,196kb @ 2,192kb/s
MD2 encoded is 289,490kb @ 2,126kb/s
MD3 encoded is 281,275kb @ 2,126kb/s
Besides MD1-3 (there are higher ones as well) you can try adjusting the strength as well (thSAD, higher values mean more removal of grain/noise but too high removes noticeable details). Can also try after MD a filter like FineDehalo/HQDeringmod (there are a lot of choices in this area) to remove some created/leftover temporal noise (mosquitoes) depending on your source and filter results.

guest
10th December 2019, 03:45
Auto-update 2019.12.09
Added: EncodingClient combines chunks with output file on fly as soon as they are encoded in correct order
Added: Audio profiles in Profile\Audio.txt
Changed: Jobless servers will be suspended only if ETA>60s (reason: reduce unnecessary suspend -> resume cycles)
Fixed: Excessive flickering of encoding status in EncodingClient
Fixed: EncodingClient didn't resume suspended jobless servers before starting second pass.
Fixed: EncodingServer didn't go to suspend mode again after previous resume

Thanks very much for that, will be a lot easier on the eyes :)

And how do you use the "audio.txt" ?

Just need to add that I updated a client & 1 server with the latest, and it was running well, it had done 2 3/4 jobs, and Encoding Client just stopped all processing, both Client & Server...had to force RB shutdown with Processhacker, started again, and away it went.

edit addition:-since that error, I have had no more problems, maybe it just needed to "warm up"

I do have a question about the function of the Encoding Client "button" on the very right of the 4 buttons...

Not sure what you've named it, but I did a little fiddling, and noticed that if that button is enabled, as soon as the processing chunk is complete, that server/port goes idle....and if thats the only chunk on a particular server, it would then shut that server down....so my question is why, if there are more chunks for that server to process.

All that comes to my old mind is that if you had a very long queue and you wanted to stop it part way thru, you'd enable that button. Then eventually all the servers would turn themselves off, and you'd only be left with the client.

I actually thought that that button would do similar to the suspend option, BUT turn them off !!

I really like the suspend option, that's great, and seems to work well for me. :)

guest
10th December 2019, 03:51
https://www.reddit.com/r/DataHoarder/
I use 1 to 1 backups


Won't give you the benefits of a test encode (seeing the actual file results) but you can check:
(on a job) edit > AviSynth > Show Video Script > Look under the custom section that you see your script, then...
> Preview (first to make sure there are no errors in your script.
If no errors and your script is being loaded > AVS Meter to see the speed and such it runs at.
If you're still skeptical that your script isn't being used because of a mistake in your code that you're not seeing try removing it and then running the AVS Meter again, if there is no difference in speed (FPS) then something could be wrong with your script and then you'd want to run a test encode to see if there are any filesize differences, if none then it is likely your script or you're using a filter that is not having an impact either by design or by an error in your script.
(tip, on your script be sure "video" is somewhere after the "=" otherwise it isn't being using in the final video sent to the HEVC encoder, otherwise it is fine if you're using it for a mask, prefilter, etc...


Besides MD1-3 (there are higher ones as well) you can try adjusting the strength as well (thSAD, higher values mean more removal of grain/noise but too high removes noticeable details). Can also try after MD a filter like FineDehalo/HQDeringmod (there are a lot of choices in this area) to remove some created/leftover temporal noise (mosquitoes) depending on your source and filter results.

Thanks for the great reply :)

I did do a run on the first few minutes of The Fifth Element (which is VERY noisey), and I was pretty happy the MD3 results (thSAD=800).

I do have slightly different thSAD numbers for MD1 & MD2.

I might go back to a much older version of RB, and see what the HQDN3D settings were, and maybe create a custom filter for non 10bit encodes.

Ryushin
10th December 2019, 12:03
Besides MD1-3 (there are higher ones as well) you can try adjusting the strength as well (thSAD, higher values mean more removal of grain/noise but too high removes noticeable details). Can also try after MD a filter like FineDehalo/HQDeringmod (there are a lot of choices in this area) to remove some created/leftover temporal noise (mosquitoes) depending on your source and filter results.

Do you have a copy of those custom scripts for FineDehalo/HQDeringmod. Originally that is what I was using mdegrain2+hqdn3d. If it does a good job I'm hoping Atak will add those as additional features.

Ryushin
10th December 2019, 14:57
Just updated and I noticed something, which I'm not sure is related to the last update or not. If I open RipBot264, change the order of the encodes, close RipBot264 and open it again, the order goes back to what it was before I changed the order.

Atak_Snajpera
10th December 2019, 15:15
Thanks very much for that, will be a lot easier on the eyes :)

And how do you use the "audio.txt" ?

Just need to add that I updated a client & 1 server with the latest, and it was running well, it had done 2 3/4 jobs, and Encoding Client just stopped all processing, both Client & Server...had to force RB shutdown with Processhacker, started again, and away it went.

edit addition:-since that error, I have had no more problems, maybe it just needed to "warm up"

I do have a question about the function of the Encoding Client "button" on the very right of the 4 buttons...

Not sure what you've named it, but I did a little fiddling, and noticed that if that button is enabled, as soon as the processing chunk is complete, that server/port goes idle....and if thats the only chunk on a particular server, it would then shut that server down....so my question is why, if there are more chunks for that server to process.

All that comes to my old mind is that if you had a very long queue and you wanted to stop it part way thru, you'd enable that button. Then eventually all the servers would turn themselves off, and you'd only be left with the client.

I actually thought that that button would do similar to the suspend option, BUT turn them off !!

I really like the suspend option, that's great, and seems to work well for me. :)

https://i.postimg.cc/dtqFRTNP/Untitled-1.png = SUSPEND JOBLESS SERVER (All chunks have been already assigned to other servers)

https://i.postimg.cc/nc0J3cNs/Untitled-2.png = SHUTDOWN SERVER AT IDLE STATE (Finish encoding current chunk and then shutdown)

byteshare
10th December 2019, 18:26
Do you have a copy of those custom scripts for FineDehalo/HQDeringmod. Originally that is what I was using mdegrain2+hqdn3d. If it does a good job I'm hoping Atak will add those as additional features.
I usually use SMDegrain rather than straight MDegrain. I don't like HQDN3D on its own. I'd rather use KNLMeansCL with GPU, which is actually the prefilter I use with SMDegrain.
For FineDehalo I either use the default: FineDehalo() or something like:
"FineDehalo(rx=2.0,ry=2.0,thmi=80,thma=128,thlimi=50,thlima=100,darkstr=1.0,brightstr=1.0,showmask=0,contra=0.0,excl=true)"
There are some safer settings if you're using anime/cartoons.

For HQDeringmod I also use the defaults "HQDeringmod()" or something like: "HQDeringmod(nrmode=2,Y=3,U=3,V=3,lsb=False,thr=255.0,darkthr=255.0)"

For those filters and others it depends on the source and what you want.

I'd stay away from thSAD values of 800 and higher for MDegrain, as it can soften the image under closer inspection. SMDegrain values of thSAD are a little different because it combines more filters.

guest
11th December 2019, 01:01
https://i.postimg.cc/dtqFRTNP/Untitled-1.png = SUSPEND JOBLESS SERVER (All chunks have been already assigned to other servers)

https://i.postimg.cc/nc0J3cNs/Untitled-2.png = SHUTDOWN SERVER AT IDLE STATE (Finish encoding current chunk and then shutdown)

Thankyou for that, I thought that https://i.postimg.cc/dtqFRTNP/Untitled-1.png put that particular server to "sleep" after the encoding was completed, then once the next job queue was starting, they would wake up, and start encoding :o

However, I really can't see that https://i.postimg.cc/nc0J3cNs/Untitled-2.png is all that necessary until towards the very end of the chunk queue, and you want individual servers to turn off.

The only reason I can see for it's use is if you have a LONG queue, and you want to stop it part way thru (for what ever reason).

I think one nice function would be to have a similar option for the client, but when the chunk that was processing completed, it didn't start the next one.

Used in conjunction with https://i.postimg.cc/nc0J3cNs/Untitled-2.png you could completely (automatically) pause or stop an encode, without doing it manually.

Anyway, enough of that, it's all a little bit over my head, but I know what works for me.

Could you please explain the use of the new "audio.txt" ?

guest
11th December 2019, 01:21
I usually use SMDegrain rather than straight MDegrain. I don't like HQDN3D on its own. I'd rather use KNLMeansCL with GPU, which is actually the prefilter I use with SMDegrain.
For FineDehalo I either use the default: FineDehalo() or something like:
"FineDehalo(rx=2.0,ry=2.0,thmi=80,thma=128,thlimi=50,thlima=100,darkstr=1.0,brightstr=1.0,showmask=0,contra=0.0,excl=true)"
There are some safer settings if you're using anime/cartoons.

For HQDeringmod I also use the defaults "HQDeringmod()" or something like: "HQDeringmod(nrmode=2,Y=3,U=3,V=3,lsb=False,thr=255.0,darkthr=255.0)"

For those filters and others it depends on the source and what you want.

I'd stay away from thSAD values of 800 and higher for MDegrain, as it can soften the image under closer inspection. SMDegrain values of thSAD are a little different because it combines more filters.

So how would you set these up a a Custom filter ??

guest
11th December 2019, 05:55
I have had a pretty frustrating couple of days with the problem that is shown in the screen shots (attached).

https://www.mediafire.com/file/dxbozrqmj3algb9/Client_encoding_problems.rar/file

I have a job encoding as it should, using a couple of servers, and it gets to a random point, and everything just stops (as far as the Encoding Client is concerned), if you check cpu usage, and TCP traffic, etc, it's still encoding in the background, but no progress is shown, it's completes the chunk that it was on, (when it locked up), then it stops, will not start another chunk.

The abort function does not work, you have to "kill" it with processhacker or similar, then once RB is finally shutdown...if you start that same job again, nothing starts :(

I know a video capture would have been preferable, but I had nothing set up on the pc to do that.

So the pic's (in order) shows that the Client is stalled, but the Server is still processing, in the 2nd pic it shows that Client is still the same, but the Server has now finished.
Then 3rd pic is restarting the job...and that's where it stays.

This has happened on 2 different pc's, and different jobs, all freshly loaded using the very latest RB version.

Atak_Snajpera
11th December 2019, 11:47
Can you move encoding client window or IT is locked with not responding message in title?

guest
11th December 2019, 12:40
Can you move encoding client window or IT is locked with not responding message in title?

Not 100% what you mean, but I don't think I tried to move it, but I'm pretty sure you couldn't minimize it, close it, so maybe if I had of tried to move it, it wouldn't have....I don't recall any message displayed.

duffbeer
11th December 2019, 15:24
I have a feature request.
The file currently encoding has an eta which is really useful. I would also like to know the estimated file size.
I realise that it may not be 100% accurate and that the predicted size will change during the encode but it would be useful none the less.

Ryushin
11th December 2019, 15:24
Can you move encoding client window or IT is locked with not responding message in title?

I'll try that today. I noticed this happening after the last update. Also getting jobs that are failing with ERROR in queue list. The job never finishes and I assume it's crashing or hanging and it's dumping a log in the output directory with:
Error: The file 'D:\Temp\RipBot264temp\job2\video.265' could not be opened for reading: open file error.

Probably related to the new code that is combing chunks during the encoding job.

forkicks
11th December 2019, 15:39
I have had a pretty frustrating couple of days with the problem that is shown in the screen shots (attached).

https://www.mediafire.com/file/dxbozrqmj3algb9/Client_encoding_problems.rar/file

I have a job encoding as it should, using a couple of servers, and it gets to a random point, and everything just stops (as far as the Encoding Client is concerned), if you check cpu usage, and TCP traffic, etc, it's still encoding in the background, but no progress is shown, it's completes the chunk that it was on, (when it locked up), then it stops, will not start another chunk.

The abort function does not work, you have to "kill" it with processhacker or similar, then once RB is finally shutdown...if you start that same job again, nothing starts :(

I know a video capture would have been preferable, but I had nothing set up on the pc to do that.

So the pic's (in order) shows that the Client is stalled, but the Server is still processing, in the 2nd pic it shows that Client is still the same, but the Server has now finished.
Then 3rd pic is restarting the job...and that's where it stays.

This has happened on 2 different pc's, and different jobs, all freshly loaded using the very latest RB version.

I can confirm this behaviour with latest updates (updated today). Main RB window completely stops responding, encoder window controls react but do nothing (ie, buttons are depressed, but no action occurs).

fK

jfisher1740
11th December 2019, 15:45
I have had a pretty frustrating couple of days with the problem that is shown in the screen shots (attached).

https://www.mediafire.com/file/dxbozrqmj3algb9/Client_encoding_problems.rar/file

I have a job encoding as it should, using a couple of servers, and it gets to a random point, and everything just stops (as far as the Encoding Client is concerned), if you check cpu usage, and TCP traffic, etc, it's still encoding in the background, but no progress is shown, it's completes the chunk that it was on, (when it locked up), then it stops, will not start another chunk.

The abort function does not work, you have to "kill" it with processhacker or similar, then once RB is finally shutdown...if you start that same job again, nothing starts :(

I know a video capture would have been preferable, but I had nothing set up on the pc to do that.

So the pic's (in order) shows that the Client is stalled, but the Server is still processing, in the 2nd pic it shows that Client is still the same, but the Server has now finished.
Then 3rd pic is restarting the job...and that's where it stays.

This has happened on 2 different pc's, and different jobs, all freshly loaded using the very latest RB version.

+1 to this same issue and behavior for DE. It seems like this started after the most recent auto update.

Atak_Snajpera
11th December 2019, 15:50
I will prepare debug version for you guys. I will need approximately 1 hour.

Ryushin
11th December 2019, 15:51
I'll try that today. I noticed this happening after the last update. Also getting jobs that are failing with ERROR in queue list. The job never finishes and I assume it's crashing or hanging and it's dumping a log in the output directory with:
Error: The file 'D:\Temp\RipBot264temp\job2\video.265' could not be opened for reading: open file error.

Probably related to the new code that is combing chunks during the encoding job.

I could move both windows. But if I click abort, then the Encoding Client window locks up with Aborting in it's title and I cannot move it. Only by killing it in the Task Manager does it make it die.

Atak_Snajpera
11th December 2019, 17:00
Use this debug version -> https://www.mediafire.com/file/e4w9w4a4dy3ye0d/EncodingClient.exe/file
and then post content of Debug.txt when encodingclient.exe hangs.

Ryushin
12th December 2019, 00:15
Use this debug version ->
and then post content of Debug.txt when encodingclient.exe hangs.

It hung, I clicked abort and waited 15 minutes and it did not abort. Log:
http://ix.io/24aS

Atak_Snajpera
12th December 2019, 00:22
It hung, I clicked abort and waited 15 minutes and it did not abort. Log:
http://ix.io/24aS

From log i see that you are experiencing different bug than Paul and others because all chunks have been combined with video.part file.

guest
12th December 2019, 06:12
From log i see that you are experiencing different bug than Paul and others because all chunks have been combined with video.part file.

Sorry I haven't responded earlier, but I'm in a very different time zone to most of you....(unless I've woken up in the middle of the night, and checked in)

Anyways...

I got around to doing a test with the same movie I had problems with yesterday, and it's funny you're sitting there waiting for it to f*** up, and it did :(, and it didn't get as far, this time.

Please check out the attached screenshots & debug.txt's.

https://www.mediafire.com/file/8g4yarseb9tdiax/Debug.rar/file

Firstly (attempt 1) I just tried to see what yesterdays stalled job would do the the debug client (not a lot)

Then I reloaded the job, (attempt 2) and it all started OK (a bit slow on the uptake due to using MD2 custom filter)

Anyway, to my untrained eye, there doesn't appear to be any errors, (as per Ryushin's post), it just simply stopped, however the server I had helping, completed the 4 chunks it had left to do, then it stopped, without issue.

But once an Abort was initiated, the window was locked in position (if that means anything), it didn't Abort, so back to ProcessHacker to do the job.

Atak_Snajpera
12th December 2019, 12:12
At least i know that code resonsible for combining chunks works as intended. I will prepare debug2 with more loging in other parts of the code.

guest
12th December 2019, 12:37
At least i know that code resonsible for combining chunks works as intended. I will prepare debug2 with more loging in other parts of the code.

Well, that's a good thing, 'cause that's a good time saver :)

So, will keep an eye out for debug2, and give it a run.

Are the screen shots helpful ??

Is there any other info you might need ??

Ryushin
12th December 2019, 12:58
From log i see that you are experiencing different bug than Paul and others because all chunks have been combined with video.part file.

Here is the debug from the hang that has occurred most of the time:
http://ix.io/24cD

guest
12th December 2019, 13:03
Here is the debug from the hang that has occurred most of the time:
http://ix.io/24cD

Did it hang before the encode completed ??

Did it work with the Abort function ??

Ryushin
12th December 2019, 13:14
Did it hang before the encode completed ??

Did it work with the Abort function ??

It hung before the encode completed. Abort results in a hard hang for the Encoding Client and must be killed using the Task Manager.

guest
12th December 2019, 13:19
It hung before the encode completed. Abort results in a hard hang for the Encoding Client and must be killed using the Task Manager.

Yep, sounds about right.

Well, another interesting challenge for Atak.