RipBot264 v1.18.3 - Simple and easy to use GUI -> IPOD . PSP . CONSOLES . BLURAY [Archive] - Page 378

Pulp Catalyst

14th January 2021, 01:28

Hey,

i'm really sorry to go on about this, but i'm still not understanding.

i turned off autocrop and i turned of resize.

and i get this on the output

Duration : 29 min 14 s
Bit rate : 609 kb/s
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 5:4
Frame rate mode : Constant
Frame rate : 50.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.029
Stream size : 127 MiB (86%)
Writing library : x265 3.4+22-ga988fbbac:[Windows][GCC 10.2.0][64 bit] 10bit

the aspect ratio is now coming out at 5:4, why? if i turned off all cropping and resizing, why is the aspect ratio signal changing?

i'm don't understand the technical things on this stuff... but none of this feels right if you get my meaning as i don't see this kind of behaviour in other similar kind of programs.

EDIT

so i done some more searching, and it could be a container issue, so i loaded the mkv in toolnix

i see a possible clue?

for the output from ripbot

i see in the video properties of mkvtoolnix

Display width/height 720 x 576 (all are the same from ripbot)

however the same file but from staxrip has a higher first number

Display width/height 759 x 576

another episode from a different series

Display width/height 768 x 576

could this be the reason for the ratio calculation going wrong?

mrlenny

14th January 2021, 14:30

Hi Atak! I've noticed when a filename contains a single quote like person's name, ripbot doesn't parse the audio file into the temp folder (resulting in NO AUDIO in the audio drop down). It looks like the json file that's being build with the list of extracted files to copy into the temp folder is escaped out by that single quote. If I rename the file removing the single quote, all works as expected.

dv8r

14th January 2021, 21:01

Anyone have any tips to get DE working on a single machine with Win10. I had it working a couple months ago and now no bueno. I've turned every setting I can find OFF in Windows Defender. AV and Firewall off. Still won't open the Encoding Server no matter what I do. Everything works fine in regular mode. Thanks

Atak_Snajpera

15th January 2021, 04:47

Run win10 in safe mode

Ryushin

15th January 2021, 13:43

Atak_Snajpera

15th January 2021, 18:01

guest

16th January 2021, 01:26

There is a small bug with custom scripts. I've previous selected a custom script, ran the job, after it completed I went back into the job and selected "OFF" for the custom script but it did not remove the code from the Video Script. I had to edit the Video Script manually to remove it.

When I read your post, I knew that someone else had a very similar issue a couple of months back...

https://forum.doom9.org/showthread.php?p=1927793#post1927793 (post #18735, also #18725))

See if that helps (it did for me).

guest

16th January 2021, 10:05

Atak,

For the first time in quite a while I wanted to use RipBot, and I updated everything (had some issues there, as well)...

So I set up one job (as a test), a TV series recorded episode, edited all the ad's, etc out with VideoRedo, saved as an .mkv.

Had RB setup to do DE, pressed start, and watched, as soon as it processed & displayed the "chunk's" I knew there was something wrong (see attached).

https://www.mediafire.com/file/t972h9euuswp1d6/chunk+problem.jpg/file

Needless to say, it didn't do anything more than just re start try to encode whatever that chunk was.

So, I eventually switched back to "single" mode, and had no problems.

Hopefully you have some clue to why it might have done this ???

Atak_Snajpera

16th January 2021, 10:09

What happens if use untouched recording in de mode? Try also remuxing in mkvtoolnix your edited MKV file.

Ryushin

16th January 2021, 15:34

Show me your custom script

Variations of MDegrain with a different thSAD failue. Here is one:

#Denoise MDegrain2 Modified
Loadplugin("C:\Program Files\RipBot264\Tools\AviSynth plugins\mvtools\mvtools2.dll")
super=MSuper(video,pel=2)
bv1=MAnalyse(super,blksize=8,isb=true,delta=1,overlap=4)
bv2=MAnalyse(super,blksize=8,isb=true,delta=2,overlap=4)
fv1=MAnalyse(super,blksize=8,isb=false,delta=1,overlap=4)
fv2=MAnalyse(super,blksize=8,isb=false,delta=2,overlap=4)
video=MDegrain2(video,super,bv1,fv1,bv2,fv2,thSAD=200)

Atak_Snajpera

16th January 2021, 15:36

#Denoise MDegrain2 Modified
change to
#Denoise

Do not put extra text in marker's line

Ryushin

16th January 2021, 15:47

When I read your post, I knew that someone else had a very similar issue a couple of months back...

https://forum.doom9.org/showthread.php?p=1927793#post1927793 (post #18735, also #18725))

See if that helps (it did for me).

That looks like my problem. I'll modify all my scripts to make sure there is a #Custom marker.

Thanks Pauly and Atak.

guest

17th January 2021, 02:29

That looks like my problem. I'll modify all my scripts to make sure there is a #Custom marker.

Thanks Pauly and Atak.

Excellent ;)

guest

17th January 2021, 02:34

What happens if use untouched recording in de mode? Try also remuxing in mkvtoolnix your edited MKV file.

OK, untouched is worse (see attached) https://www.mediafire.com/file/j4zcqqxfae1vfnz/untouched+m2ts+file.jpg/file

Also a screenshot of another file from the same "set" (see attached) https://www.mediafire.com/file/r0ygkjv56x4vj1b/different+chunks-different+file-same+series.jpg/file

That first screenshot I sent (other post) WAS thru mkvtoolnix :(

However, if I run them thru Handbrake, they are fine, in DE..:confused:

Atak_Snajpera

17th January 2021, 10:43

Will you be ale to send original file? Trimmed 200MiB should be enough.

guest

17th January 2021, 10:46

Will you be ale to send original file? Trimmed 200MiB should be enough.

I was wondering if you were going to ask for that...

The original is just over 600mb (rar'ed up), not sure what to trim it with, that might affect it's problem...

Let me know what you'd prefer...

Atak_Snajpera

17th January 2021, 12:04

If you have fast upload speed then send whole 600MiB to Mediafire.

guest

17th January 2021, 12:43

If you have fast upload speed then send whole 600MiB to Mediafire.

I don't, but I will post the whole thing..

Will send you a link, when it's ready.

slalom

17th January 2021, 13:03

What about this error, when I set the KNLMeansC1

https://i.ibb.co/87bT5YY/137521778-838786856691689-7961683675896361424-n.jpg (https://ibb.co/sVCkwWW)

the path is correct

guest

17th January 2021, 13:21

What about this error, when I set the KNLMeansC1

https://i.ibb.co/87bT5YY/137521778-838786856691689-7961683675896361424-n.jpg (https://ibb.co/sVCkwWW)

the path is correct

Hi, so the fresh setup didn't help !!!

I mentioned to you in FB Messenger that I loaded a job, and enabled those filters, and it worked ok.

Hopefully Atak will have an answer...

guest

17th January 2021, 13:24

If you have fast upload speed then send whole 600MiB to Mediafire.

OK, here ya go...didn't take too long to upload :)

https://www.mediafire.com/file/xy2t8o90344zkzf/Ep_4.rar/file

I just hope that it has the same errors for you, as it did for me...

Atak_Snajpera

17th January 2021, 14:15

What about this error, when I set the KNLMeansC1

https://i.ibb.co/87bT5YY/137521778-838786856691689-7961683675896361424-n.jpg (https://ibb.co/sVCkwWW)

the path is correct

Incorrect AviSynth+ version? EncodingServer.exe shows what AviSynth version you have installed at the bottom field.

Atak_Snajpera

17th January 2021, 14:40

OK, here ya go...didn't take too long to upload :)

https://www.mediafire.com/file/xy2t8o90344zkzf/Ep_4.rar/file

I just hope that it has the same errors for you, as it did for me...

That file is ultra weird because decoder sees ONLY one key-frame for whole file!

example from video.mkv.lwi
<LSMASHWorksIndexVersion=0.0.2.0>
<LibavReaderIndexFile=16>
<InputFilePath>C:\Temp\RipBot264temp\job2\video.mkv</InputFilePath>
<FileSize=625585425>
<FileHash=0x65d6f4a4>
<LibavReaderIndex=0x00000000,0,matroska,webm>
<ActiveVideoStreamIndex>+0000000000</ActiveVideoStreamIndex>
<ActiveAudioStreamIndex>-0000000002</ActiveAudioStreamIndex>
<StreamInfo=0,0>
Codec=27,TimeBase=1/1000,Width=720,Height=576,Format=yuv420p,ColorSpace=2
</StreamInfo>
Index=0,POS=362,PTS=0,DTS=-9223372036854775808,EDI=0
Key=1,Pic=1,POC=0,Repeat=1,Field=1
Index=0,POS=9479,PTS=120,DTS=0,EDI=0
Key=0,Pic=2,POC=6,Repeat=1,Field=1
Index=0,POS=10636,PTS=40,DTS=40,EDI=0
Key=0,Pic=3,POC=2,Repeat=1,Field=1
Index=0,POS=10781,PTS=80,DTS=80,EDI=0
Key=0,Pic=3,POC=4,Repeat=1,Field=1
Index=0,POS=10924,PTS=240,DTS=120,EDI=0
Key=0,Pic=2,POC=12,Repeat=1,Field=1
Index=0,POS=12324,PTS=160,DTS=160,EDI=0
Key=0,Pic=3,POC=8,Repeat=1,Field=1
Index=0,POS=12478,PTS=200,DTS=200,EDI=0
Key=0,Pic=3,POC=10,Repeat=1,Field=1
Index=0,POS=12657,PTS=360,DTS=240,EDI=0
Key=0,Pic=2,POC=18,Repeat=1,Field=1
Index=0,POS=13920,PTS=280,DTS=280,EDI=0
Key=0,Pic=3,POC=14,Repeat=1,Field=1
Index=0,POS=14070,PTS=320,DTS=320,EDI=0
Key=0,Pic=3,POC=16,Repeat=1,Field=1
Index=0,POS=14263,PTS=480,DTS=360,EDI=0
Key=0,Pic=2,POC=24,Repeat=1,Field=1
Index=0,POS=15419,PTS=400,DTS=400,EDI=0
Key=0,Pic=3,POC=20,Repeat=1,Field=1
Index=0,POS=15562,PTS=440,DTS=440,EDI=0
Key=0,Pic=3,POC=22,Repeat=1,Field=1
Index=0,POS=15735,PTS=600,DTS=480,EDI=0
Key=0,Pic=1,POC=30,Repeat=1,Field=1
Index=0,POS=24816,PTS=520,DTS=520,EDI=0
Key=0,Pic=3,POC=26,Repeat=1,Field=1
Index=0,POS=24976,PTS=560,DTS=560,EDI=0
Key=0,Pic=3,POC=28,Repeat=1,Field=1
Index=0,POS=25164,PTS=720,DTS=600,EDI=0
Key=0,Pic=2,POC=36,Repeat=1,Field=1
Index=0,POS=26479,PTS=640,DTS=640,EDI=0
Key=0,Pic=3,POC=32,Repeat=1,Field=1
Index=0,POS=26656,PTS=680,DTS=680,EDI=0
Key=0,Pic=3,POC=34,Repeat=1,Field=1
Index=0,POS=26843,PTS=840,DTS=720,EDI=0
Key=0,Pic=2,POC=42,Repeat=1,Field=1
Index=0,POS=28110,PTS=760,DTS=760,EDI=0
Key=0,Pic=3,POC=38,Repeat=1,Field=1
Index=0,POS=28274,PTS=800,DTS=800,EDI=0

guest

18th January 2021, 02:02

That file is ultra weird because decoder sees ONLY one key-frame for whole file!

OK, so all that doesn't really mean a lot to me...

So let me try and get my head around this....the "decoder", which is Lsmash, correct ??, isn't "seeing everything" ??.

So before you implemented Lsmash into RB, was it FFMPEG that was used ??

Can that still be used ??

It seems strange that RB's decoder has this problem with this type of file (and unfortunately I have a LOT of them), BUT Handbrake doesn't (not knowing what decoder HB uses).

It would be nice NOT having to use HB, it just adds another step to the process, although there are a couple of advantages.

Anyway, do you have any suggestions ?? or do I just carry on with the current workflow ??

Cheers & thanks again.

guest

18th January 2021, 02:06

What about this error, when I set the KNLMeansC1

https://i.ibb.co/87bT5YY/137521778-838786856691689-7961683675896361424-n.jpg (https://ibb.co/sVCkwWW)

the path is correct

Hi, again,

Just found the latest version of Avisynth...go and grab it :)

https://github.com/AviSynth/AviSynthPlus/releases

If you're unsure of which to download, pick AviSynthPlus_3.7.0_20210111_vcredist.exe

guest

18th January 2021, 02:30

Atak,

I've found a few "important" updates :-

Avisynth 3.7.0 as in above post #18877

FFMPEG 20210106 https://ottverse.com/ffmpeg-builds/

L-Smash 12.12.2020 https://cloud.owncube.com/s/MXk3zBcZfNkrGF9

L-Smash 16.12.2020 https://cloud.owncube.com/s/C8SBjF53JTL7s73

https://forum.doom9.org/showthread.php?p=1930562#post1930562

also x265, 3.4+36 http://msystem.waw.pl/x265/

and x264, r3033 https://artifacts.videolan.org/x264/release-win64/

LigH

18th January 2021, 08:50

KNLMeansCL also had an update for compatibility with recent AviSynth+ versions by pinterf: https://github.com/pinterf/KNLMeansCL/releases

Ryushin

18th January 2021, 13:43

I wanted to give an example of what light MDegrain2 (thSAD value) can do for some files.

This is with Hickok (2017) 4K (Original source size of video is 50GB). Settings used CQ18 x265:

No MDegrain: 12.80GB
thSAD=100: 8.98GB
thSAD=150: 5.45GB
thSAD=200: 4.51GB

This is all relative to the video. I suspect the film is recorded with a digital camera and there is very light grain structure. Then MDegrain can remove just this light grain and then it cleans up beautifully. Hard to believe the file with thSAD=200 is less than 1/10 it's original size

I think it would be good to add an adjustable thSAD value to the UI.

I had not mentioned this in the past, but for those that use MDegrain3, you should be aware of something I've noticed over the last couple of years. The temporal function of MDegrain3 uses three frames and this can lead to some odd looking results. For example, what I've found, depending on the movie, if the camera is still and someone turns their face, the skin texture will smooth out during the turn and then the texture returns when they stop moving. Just something to be aware of. I don't use MDegrain3 very often and I'm more reluctant to do so now since I've been noticing this. The size difference from MD2 compared to MD3 is not that great. For example, 22GB vs 25GB. For super grainy sources, MD3 still the way to go.

slalom

19th January 2021, 18:25

Incorrect AviSynth+ version? EncodingServer.exe shows what AviSynth version you have installed at the bottom field.
No, that was 3.6.1, your update fixed my problem :thanks:

will install 3.7 too

@Pauly :thanks:

guest

27th January 2021, 01:10

So I was hoping to post this last night, but the forum seemed to be "down"...

Yesterday, for the 1st time in month's & month's, I thought I'd process a 4K movie (Hobbit-The Unexpected Journey, extended version), it's just over 3 hours, 182 chunks, so I expected it to take quite some time to process, even though I'm ONLY doing the video.

I only got 40% done, will continue when able to...

So once I had the main PC working on it (Ryzen 9 3950X), it was grinding along fairly well, I also had the DE help of another PC.

I thought I'd used some of my "farm servers" to help, so I turned them on, 1 at a time, as I hadn't used them for age's either, and the 1st one connected without issue (dual E5-2690 Xeon's), so then I turned on another (dual X5690 Xeon's, Windows Server 2019), and it just would NOT start processing a chunk, if I went back to the main PC and watched, the chunk would start it's process, but as soon as it switched to the actual processing, it would them go idle, then start again, repeat, repeat, repeat...

So I tried another server, (same spec's), same problem...

So I tried another server, (dual X5680 Xeon's, Server 2019), same problem...

There were no pop up error messages !!!.

So then I tried yet another PC, (again, dual X5680 Xeon's, Tyan MB, Server 2019), same problem !!!

And finally yet another PC, (again dual Xeon's, Windows 10 Enterprise), same problem, but this one threw up an ffmeg not working error).

Got the latest build of that, didn't make any difference.

Meanwhile the first PC's were still processing along pretty well.

I took a short video of this DE behaviour, and will post a link...

https://drive.google.com/file/d/1JCAYWElXyDTX6a4vEAR2UuA0mU81Ihee/view?usp=sharing

I can't help but think someone has had a similar issue recently, but not too sure when.

Later on, on the Ryzen, DE was starting to play up, and I have a screen shot of that...but then it got to a point, that I stopped RB, and hoping that it will re start where it left off, I re started, and sure enough, it carried on :)

(screenshot link) :- https://www.mediafire.com/file/4c7bg5rwgswjv1j/double+ip+address.jpg/file

So to sum up, it's pretty frustrating when you have several reasonable PC's that you want to use to "help" with DE, and none of them connect :(

I think I might need to "start from scratch", and put fresh setup's on all of them....

Atak_Snajpera

27th January 2021, 01:57

You should record what encoding server is showing. I suspect some problem with shared folder or/and avisynth instalation.

guest

27th January 2021, 06:54

You should record what encoding server is showing. I suspect some problem with shared folder or/and avisynth instalation.

Damn, I knew there was something else I needed to check as well :(

It's just strange that some PC's are good, and others aren't, they're all set up pretty much exactly the same.

So what could go wrong with the Avisynth install ???, that link I posted (#18877 & 78), should be good...

Question:- If avisynth is installed into it's own default folder location, do the contents also need to be copied to the RB tool's folder as well ???

Would you be able to do an auto update with the latest avisynth included ??, and maybe a few more updates as well ??

blacksapprow

29th January 2021, 21:58

Question: With Ripbot version 1.26.0 there came settings inside AviSynth:

Sharpen: Off, %25, %55, %75, %100 --> This is understandable.

CPU Denoise: Off, MDegrain1, MDegrain2, MDegrain3 --> Is that: MDegrain1 low, MDegrain2 middle, MDegrain3 high setting? What actually it is for? White Gaussian noise? https://en.wikipedia.org/wiki/White_noise

GPU Denoise: Off, KNLMeansCL1, KNLMeansCL3, KNLMeansCL5 --> Is that: KNLMeansCL1 low, KNLMeansCL3 middle, KNLMeansCL5 high setting? What actually it does? Can anyone tell about this more? What is it's difference with MDegrain? Only use of CPU and/or GPU? Near same results?

If we use only MDegrain, only KNLMeans and MDegrain + KNLMeans together, what they differs? Can anyone tell briefly?

Atak_Snajpera

29th January 2021, 23:07

Last digit indicates how many previous and next frames are taken for analysis. More means stronger denoising and more stable output.
MDegrain aims for fine detail retention while knlmeanscl is much more aggressive. My recommendation is as follows. Use MDegrain first and then knlmeanscl if you still need to remove any grain leftovers.

guest

30th January 2021, 01:53

Atak,

I asked a legit question about the installation of Avisynth, mainly due to "you" suggesting that maybe something is wrong.

If you download the latest version of AV, it is installed (by default) into it's own folder, but AviSynth.dll & DevlL.dll are installed in the SYSWOW64 root.

In RB's "Tool's" folder under Avisynth/Libraries/x64 is where you'll find these files, and it's version 3.4.0.0, dated 04-11-2019.

So to be more specific, do these 2 .dll files need to be copied into RB's Libraries/x64 folder ???

Or is that Folder's contents redundant ??

Atak_Snajpera

30th January 2021, 09:47

I sugested to check encoding server window in first place.

guest

30th January 2021, 13:34

I sugested to check encoding server window in first place.

Yes you did, but I haven't had a chance to get back to encoding, since then.

However, you haven't commented on the Avisynth question..

Atak_Snajpera

30th January 2021, 14:48

Yes you did, but I haven't had a chance to get back to encoding, since then.

However, you haven't commented on the Avisynth question..

Because it is irrelevant as long as you do not check what is happening on server side.

Dhry

30th January 2021, 17:15

Hey. Wanted to drop this off here just in case someone has ever experienced the same issue I did in recent months.

The problem was simply that starting a Ripbot encode did NOT trigger the startup of any EncodingServers. The client window appears, and four (which is what I use) EncodingServer.exe instances appear as tasks, but their WINDOWS do not appear and work does not commence. It was the absolute most frustrating thing for me and I tried dozens of things to try and fix it. I have a few other machines here and on each of those, the EncodingServer app would start fine. But it simply wouldn't on my main desktop. I read about something like this in previous posts on this thread and have tried reinstalling the VC redistributables, it did not help at all. Tried clean boots via msconfig and all of a sudden EncodingServer started working again and that's when I knew it was something I was running that was preventing proper operation.

By a process of elimination I have discovered that two Nvidia services kill the ability for EncodingServer.exe to bring up a window and/or commence work.

NVIDIA Display Container LS (this is the prime culprit)
NVIDIA LocalSystem Container

I have a Ryzen 9 3950X (but had an I7 4-core before, same issue) and a GTX1080. The services above appear to be related to the nVIDIA GeForce experience app that is installed by default with the GeForce drivers. I messed around in there with settings but absolutely could not fix this without completely stopping and disabling those services. Soon as I did, boom, up came all four windows for EncodingServer.

FWIW I also think that I had problems with my browser (Brave) at one point, but I changed a lot of flags in there and now there are no issues with EncodingServer, even with Brave running. I can only imagine that there is something related to the GPU perhaps, that when in operation somehow jams up EncodingServer's functionality.

Running the NVIDIA Display Container LS, over time, also seemed to spin up some sort of weird background process, making my mouse pointer sluggish to animate and move over time. Stopping that process instantly gave me back pointer responsiveness, however it also kills off the GeForce experience app from my systray. I'm fine with that.

Regards
Dhry

slalom

30th January 2021, 18:15

Later on, on the Ryzen, DE was starting to play up, and I have a screen shot of that...but then it got to a point, that I stopped RB, and hoping that it will re start where it left off, I re started, and sure enough, it carried on :)

(screenshot link) :- https://www.mediafire.com/file/4c7bg5rwgswjv1j/double+ip+address.jpg/file

So to sum up, it's pretty frustrating when you have several reasonable PC's that you want to use to "help" with DE, and none of them connect :(

I think I might need to "start from scratch", and put fresh setup's on all of them....
I get that screenshot too, sometimes. I abort and restart and it goes away

About the other stuff in your post, restart all your PCs and make sure they have all the ripbot updates, as I understand you don't use them frequently
(I can't see the video you posted, maybe you removed it)
Question:- If avisynth is installed into it's own default folder location, do the contents also need to be copied to the RB tool's folder as well ???
It works as it is

guest

1st February 2021, 00:54

Going back to :- https://forum.doom9.org/showthread.php?p=1933709#post1933709

I asked what decoder RipBot now uses...

There was a time when "we" had a choice, but I think it's now just L-Smash by default, and GPU options.

Is there still a way to use FFMPEG ??

guest

1st February 2021, 04:45

Because it is irrelevant as long as you do not check what is happening on server side.

OK, got to record what's going on (poor quality)..

https://drive.google.com/file/d/1Mfc7_zxqZJvevqOqtFPIjExsKfPp5tih/view?usp=sharing

the pop error is :- "ffmpeg has stopped working"

and the error in the encoder window, is :-

x265 [error]: unable to open input file <->

Atak_Snajpera

1st February 2021, 19:50

Ripmann

1st February 2021, 21:41

Ripmann

1st February 2021, 22:14

Also, a possible bug/oversight:

When clicking Preview Script, only one MPC window pops up regardless of the MPC settings ("Player->Open a new player for each media file played").

The reason it's even an issue is because I usually enabled multiple players before and clicking Preview Script several times opened several of them. That allowed me to quickly compare the quality of the frames with different denoise or color adjustment settings, so I used it all the time when I needed to manually tweak something. If that's something that can be easily addressed (I can only assume that RipBot checks if there's a "job1_preview.avs" named window and ignores another preview request), I'd really appreciate it.

guest

2nd February 2021, 01:32

Hey guys. Can somebody please clarify how GPU-based encoding works? I have two GPUs in my system, a dedicated Nvidia card and the integrated graphics one that comes with most Intel chips. My question is, does the integrated GPU has any relevance on encoding at all? AMD finally came out with a non-crappy line of CPUs last year that don't have integrated graphics in them. If, for example, I switch to a roughly equivalent AMD CPU, will I lose any performance from not having an integrated graphics chip anymore? Or is it completely unused and the video card alone does all the encoding? This question bugs me from time to time and I never found an answer given by somebody who really knows what they're doing.

A related question, also. Is it possible to dedicate one particular GPU to encoding? RipBot's options don't seem to allow it, but it should be completely doable to choose which GPU you want to be used, right? If so, can this GPU selection option be added in the setting then? Seems like a useful feature with people with multiple cards. Thanks.

Well, GPU encoding uses the available GPU's in your system, generally slower, but it allows for the use of different filters.

And of course CPU encoding uses the CPU, generally a lot faster, and use other filters.

You can specify which does what by using appropriate switches...

check this link for a bit of info (hidden switches) :-

https://forum.doom9.org/showthread.php?p=1894410#post1894410

/port 1000 /minimize /priority low /node 0 /knlmeanscl-opencl-device-type CPU
/port 2000 /minimize /priority low /node 0 /knlmeanscl-opencl-device-type CPU
/port 3000 /minimize /priority low /node 1 /knlmeanscl-opencl-device-type CPU
/port 4000 /minimize /priority low /node 1 /knlmeanscl-opencl-device-type CPU

Multiple GPU's

/port 1000 /minimize /priority low /knlmeanscl-opencl-device-id 0
/port 2000 /minimize /priority low /knlmeanscl-opencl-device-id 1

and/or

If you are using x264+KNLMeansCL and you also have iGPU (device 0) and dGPU (device 1) then

/port 1000 /minimize /priority low /x264-opencl-device-id 0 /knlmeanscl-opencl-device-id 1

To see what devices you have you need to look in the OpenCL tab (in Settings) of RipBot, it will list your GPU's

Hope this helps a little.

guest

2nd February 2021, 12:46

Run EncodingServer.exe WITHOUT any extra switches. When window pops-up with message "FFMpeg.exe has stopped working" check details. You should see what exact DLL module crashed within ffmpeg.exe executable.

So I was hoping to do this today, but I had an unexpected, but not surprising major set back with my current encoding job.

Anyway, I started up the PC that had my current 4K encode, and I only had about 60 or so chunks to do, but yesterday, RipBot did not want to shut down...even tho I stopped the processing once a chunk was complete, it just froze, (not responding) when I went to close it down.

So, not unexpectedly, when I re-started the job, it started from chunk #1, so 2 days (approx 10 hours of encoding down the f*ckin' drain).

Anyway, that's another whole major problem that needs to be addressed, that is & has been a problem, that has been around for a long time.

So I continued "testing" the problem on another PC, and I think it might have something to do with x265.

I just happened across this....I batch loaded a few files in, and once they were in the job list, I thought I'd change 1 job to HEVC, and as soon as Encoder started to process & start the job, it re started (as in that video I sent thru), so repeat, repeat...I stopped it, changed it back to x264, and started with no problem.

I got no error pop up's or anything, so have no idea what was causing it.

Atak_Snajpera

2nd February 2021, 19:50

So, not unexpectedly, when I re-started the job, it started from chunk #1, so 2 days (approx 10 hours of encoding down the f*ckin' drain).

Anyway, that's another whole major problem that needs to be addressed, that is & has been a problem, that has been around for a long time.

When file EncodingProgress.Pass1 or EncodingProgress.Pass2 in Chunks folder is missing then you lose whole progress. That file is being updated every time chunk gets encoded. For your unstable PC I guess I would have to implement some backup system...

Regarding crashing ffmpeg.exe. I've just checked the code in EncodingServer.exe and crash window will always be automatically closed regardless of switches used. It would be much easier if you just manually executed /Chunks/1.cmd from shared folder and then expand details. Look for FAULTY MODULE: line