Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
|
Thread Tools | Search this Thread | Display Modes |
1st December 2018, 09:36 | #16361 | Link | |||
ByteShare
Join Date: Sep 2014
Location: On the Internet
Posts: 560
|
Quote:
Quote:
Quote:
|
|||
1st December 2018, 16:34 | #16362 | Link | |
ByteShare
Join Date: Sep 2014
Location: On the Internet
Posts: 560
|
Quote:
https://imgur.com/a/K0Pn5pi (cut off columns in the photo. I put this int he description for the photo as well, but: Columns are: Process, CPU, Private Bytes, Working Set, PID, Description, Company Name, Session, CPU Time, CPU History, and Cycles) I'm not sure where you got that User Time in your picture, but I had to use Process Explorer, because in Windows 10 the Task Manager is trash. Incase you wanted User Time Vs. Total time there were also most the same: ffmpeg.exe User Time: 0:02:23.687 / Total Time: 0:02:24.703 x265_x64.exe: User Time: 0:01:15.984 / Total Time: 0:01:17.031 Full details in the image above (2nd Image) Looks like FFMPEG gave up at some point? The other segments were doing ~13-14FPS, or about 107s per segment There are 23 segments and it got stuck on 22, but 23 finished. My command line: Code:
/port 1000 /minimize /priority low /restart-if-no-progress 8 /port 2000 /minimize /priority low /restart-if-no-progress 8 Using Process Explorer I killed the Process Tree for the "EncodingServer.exe" that was stuck and the next server picked up and finished the job, but the whole thing was stuck for many hours. If you needed more info than this let me know and I can gather next time it happens. Last edited by byteshare; 1st December 2018 at 16:45. |
|
1st December 2018, 17:03 | #16363 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,806
|
I suspect that EncodingServer.exe died as well. That would explain why EncodingServer.exe has not restarted child processes. Please confirm my theory!
Basically kill ffmpeg.exe and x265_x64.exe and see If EncodingServer.exe will start encoding again.
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper Last edited by Atak_Snajpera; 1st December 2018 at 17:06. |
1st December 2018, 20:09 | #16364 | Link | |
ByteShare
Join Date: Sep 2014
Location: On the Internet
Posts: 560
|
Quote:
Thank you for your time. |
|
1st December 2018, 20:18 | #16365 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,806
|
I'm 99,9% sure that you will see EncodingServer (not responding) message.
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
1st December 2018, 22:31 | #16368 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,806
|
This is what I meant
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
2nd December 2018, 00:44 | #16369 | Link |
Registered User
Join Date: Jun 2010
Location: NSW, Australia.
Posts: 366
|
Is that suppose to be an example of the error message ???
And that also looks like W7...I think you'll find that the majority of "us" user's are running W10 or Server '16 / '19, and if I recall those OS's throw up messages down in the bottom right hand corner of the screen, or maybe off the Taskbar. I am now only running one W7 machine, as I haven't noticed any advantages or disadvantages using W7 over W10 with Ripbot. You might have to do some test runs on a VM W10.. I'm sure I did some test's for you a couple of weeks back, by suspending most of the components used by the Ripbot process, and those test's revealed that if you suspend either ffmpeg, x264 & x265, that it will indeed restart after the prescribed time in the Encoders commandline instructions...I have mine set @ 2 minutes, byteshare has it @ 8 (for example). Maybe it's a case of monitoring Encoding Server the same way you did it for ffmpeg, etc, and that might make it almost "bullet proof" reliable |
2nd December 2018, 00:49 | #16370 | Link | |
Registered User
Join Date: Jun 2010
Location: NSW, Australia.
Posts: 366
|
Quote:
What CPU(s) are you running ??? you could at least be using NUMA 0 !! |
|
3rd December 2018, 04:26 | #16372 | Link | |
Registered User
Join Date: Jun 2010
Location: NSW, Australia.
Posts: 366
|
Quote:
So I used Ripbot for the 1st time in over a week, today, using the newest EncodingServer 1.12.6.0, and the very first job stalled on Port 2000 !!! But before I say anymore, I still can't understand why it won't start encoding after adding Job's, until you restart Ripbot , this has only started, recently. OK, so back to the stall, I went into Process Hacker, and suspended ffmpeg, but it didn't seem to have any affect. There were no pop up warnings, either, so that might also indicate that it's not ffmpeg, x264 or x265... Back to the Encoder Client window, those ON/OFF buttons for each server control the Encoding Server, correct ?? So, if those button's don't do anything wouldn't that mean that Encoding Server has a major problem ??!!! You can keep pressing the OFF button forever, and it does nothing !!!! Aborting the whole Job seems to be the quickest & best "fix". I can't explain it any other way, I'm not an "IT" person !! OK, a couple of hours later, I have had it happen several more times, but on the Client's, not the main PC (Server, I guess it is)...I cannot diagnose it with Process Hacker, everything appears to me, is still working, but one Encoding Server has definitely "locked up", and there's really only one course of action...re start Ripbot, and hope it doesn't happen again, anytime soon. And as a result of aborting & restarting, the job starts from the beginning , and it show any other jobs that have been completed, as not being done..... Last edited by burt123; 3rd December 2018 at 08:00. Reason: even more info |
|
3rd December 2018, 13:50 | #16373 | Link | |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,806
|
Quote:
http://www.mediafire.com/file/aw8gqz...erver.exe/file
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
|
4th December 2018, 06:35 | #16374 | Link | |
Registered User
Join Date: Jun 2010
Location: NSW, Australia.
Posts: 366
|
Quote:
I only did one encode today, and after a tiny little hiccup right at the start (probably my fault), it run faultlessly....the ONLY different thing that happened (and I wasn't watching when it did), but I returned to notice a "different" looking icon in the Taskbar, so I clicked on it, and there were 4 instances of that "Supervise Process" screen in your previous post, one for each of the servers/ports I had going. Does that mean that there was a stall on all 4, and they were all started automatically ??? |
|
4th December 2018, 12:00 | #16375 | Link | |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,806
|
Quote:
Process Tree Example using different application for testing purposes
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper Last edited by Atak_Snajpera; 4th December 2018 at 12:07. |
|
4th December 2018, 13:01 | #16376 | Link | |
Registered User
Join Date: Jun 2010
Location: NSW, Australia.
Posts: 366
|
Quote:
And this must be what you've incorporated in the Encoding Server you provided, yesterday. |
|
4th December 2018, 13:11 | #16377 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,806
|
It does both now. Monitors ffmpeg.exe/x264/265 and also MAIN application. SuperviseProcess.exe monitors EncodingServer.exe and EncodingServer.exe monitors ffmpeg/x264/x265
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
4th December 2018, 13:14 | #16379 | Link | |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,806
|
Quote:
https://www.virustotal.com/#/file/92...8eb6/detection
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
|
4th December 2018, 13:43 | #16380 | Link |
Registered User
Join Date: Oct 2001
Posts: 454
|
Already did a check on virustotal, seems fine (two heuristic notices, not worth it..), but I canŽt switch virusscan of here (workstation..)
On another note concerning the OPENCL on XEON Issue: I found "GPU" in the avs script in the KNLEANSCL Line - changed it to "auto", works fine now. Not sure how this affects all other machines with real GPUs. |
Tags |
264, 265, appletv, avchd, bluray, gui, iphone, ipod, ps3, psp, ripbot264, x264 2-pass, x264 gui, x264_64, x265, xbox360 |
Thread Tools | Search this Thread |
Display Modes | |
|
|