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

[guest]

Remove "★" and "ü" from file name.

OMG....

I also had to remove the "★" from the folder name, that that file was in...

Unbelievable.. :stupid:

[david.dgc]

Hello,

How works the excel file "workhours.csv" ?

The program will only encode within the time set and pauses according to this file?

How we enter time schedules inside?
Thanks

[Atak_Snajpera]

Go to settings - work hours and generate simple rule. Next open that file in notepad to see how correct syntax should look like.

[guest]

"We" have a long awaited autoupdate......

I was hoping for some significant changes, etc....but you can see for yourselves.

Thanks, Atak.

[FuzzyNutz]

great that we can now add track descriptions. would be more useful if there was predefineable user-editable descriptions, separate for video, audio and subtitles, similar to what MKVToolNix has. thus, eliminating the need to manually type often used descriptions.

twas i that requested this be added to MKVToolNix, btw.

update: i assumed track descriptions = track names. seems i assumed wrong. so, what are track descriptions?

[guest]

great that we can now add track descriptions. would be more useful if there was predefineable user-editable descriptions, separate for video, audio and subtitles, similar to what MKVToolNix has. thus, eliminating the need to manually type often used descriptions.

twas i that requested this be added to MKVToolNix, btw.

This might need to be suggested to the author of MKVToolnix...not here.

[FuzzyNutz]

This might need to be suggested to the author of MKVToolnix...not here.

i referenced an existing ability of MKVToolNix as an example of what i want added to RipBot264.
as an aside, i offered that the author of MKVToolNix added said ability at my request.

[screaming]

Started up RipBot264 and it auto-updated to v1.26.1. Whatever .mkv I feed it, it generates an error after trying to index:
System exception - Access Violation
(c:\temp\job1\getinfo.avs, line 2)

Looking at the getinfo.avs file, line 2 looks something like this:
video=LWLibavVideoSource("c:\Video\Temp\video.mkv",cachefile="c:\temp\RipBot264temp\job1\video.mkv.lwi",prefer_hw=3)

Also spotted at the bottom of the test.log file:
[avisynth @ 0000018da9c30e00] System exception - Access Violation
(c:\temp\RipBot264temp\job1\getinfo.avs, line 2)
c:\temp\RipBot264temp\job1\getinfo.avs: Unknown error occurred

I have tried multiple files, and I'm getting the same error each time now.

[Atak_Snajpera]

Set all decoders to CPU instead of GPU

[screaming]

Set all decoders to CPU instead of GPU

Thank you. I switched just the AVC decoder from GPU to CPU, and that has allowed me to proceed with next steps and to start the encoding.

Is there a reason why decoders need to be set to CPU instead of GPU? Is there an issue a component or plugin that has an issue, or perhaps with a system driver on my computer?

[Atak_Snajpera]

Latest version of lsmash seems to have broken hardware decoders. I haven't noticed that because I always use software decoders.

[slalom]

@Atak

When I add an audio track from the 3-dot button, the program freezes

that's with the latest update, after 2021.05.25

[guest]

Hey guy's,

If anyone is having issues with L Smash, (or just want's to use the older RB decoder, try this :-

overwrite this field in RipBot264.ini if you want to use FFMS2 instead of L-Smash

[DefaultVideoDecoder]
MPEG-2=FFMS2
VC-1=FFMS2
AVC=FFMS2
HEVC=FFMS2
OTHER=FFMS2

[slalom]

@Atak

When I add an audio track from the 3-dot button, the program freezes

that's with the latest update, after 2021.05.25
Probably my bad, they were jobs added with 2021.05.25 update

[Ripmann]

Hey guys, I'm having a dismal month with no free time whatsoever. Just wanted to drop by to thank Pauly Dunne for his advice (although I haven't had a chance to finish the installation yet) and Atak for adding all the title and filter strength options.

A minor note about the strength values: if it's not too much trouble, could you tweak the KNLMeansCL strength input to accept decimal values like 1.5? Back when I ran denoise tests, I saw a notable difference between values like 1.0 and 1.5. So just one decimal point, for better control, would be perfect. Otherwise, great job. Glad to see you back in action.

EDIT: By the way, I didn't notice any issues with audio tracks or GPU encoding after the patch (Nvidia card). In case somebody is wary of the update because of the reports above, back up the installation folder just in case and give it a try.

[guest]

Hey guys, I'm having a dismal month with no free time whatsoever. Just wanted to drop by to thank Pauly Dunne for his advice (although I haven't had a chance to finish the installation yet) and Atak for adding all the title and filter strength options.

A minor note about the strength values: if it's not too much trouble, could you tweak the KNLMeansCL strength input to accept decimal values like 1.5? Back when I ran denoise tests, I saw a notable difference between values like 1.0 and 1.5. So just one decimal point, for better control, would be perfect. Otherwise, great job. Glad to see you back in action.

EDIT: By the way, I didn't notice any issues with audio tracks or GPU encoding after the patch (Nvidia card). In case somebody is wary of the update because of the reports above, back up the installation folder just in case and give it a try.

Hey Ripmann,

Yeah, it's been a little while, and thankyou for your compliment.

Not sure if you would have seen my lengthy explanation of the differences between the original KNLMeansCL filter scripts, and the current one's, before I took that post down.

Anyway, I know it's each to their own, but I still don't understand why you like KNLMeansCL...

OK, so I have just done a very simple edit / test, and it seems like you can use ANY decimal point value you want....you simply choose one from the drop down, and edit the "h" value, eg:-

#After_Prefetch_Denoise
LoadPlugin("D:\RipBot264v1.26.1\Tools\AviSynth plugins\KNLMeansCL\KNLMeansCL.dll")
video=ConvertToYUV444(video).KNLMeansCL(d=0, a=2, s=4, h=1.5, device_type="GPU", device_id=0, channels="YUV").ConvertToYUV420

OR

You could also write up a few custom scripts, and simply choose it from the Custom Script drop down list.

I'm sure you've now seen this :-

https://forum.doom9.org/showthread.php?p=1943629#post1943629

[guest]

So I have just noticed yet another little update...

The mostly obvious addition is a "Demo" mode for the filter's you use, either Sharpen, MDegrain or KNLMeansCL..it split's your clip into a 4 way split screen in MPC-HC, so you can easily compare the difference between the 3 available presets for these filters, but only in their default levels, NOT if you choose a different "Strength" :(

Interesting feature, but as it doesn't adjust to user custom settings, it's just "bling".

Having said all that, I have just tried to start my Job Queue and it has an L-Smash error on the existing jobs, BUT if you load a new job, there isn't a problem.

This would be a MAJOR problem for those who have massive Job Queue's :(

Another observation, when I try and use the "Demo" feature MPC-HC "Cannot render the file", however, "Preview Script" works fine

[slalom]

That split-screen playback is much smoother and it helps a lot to find the right preset filter. It helps a lot!

[guest]

That split-screen playback is much smoother and it helps a lot to find the right preset filter. It helps a lot!

C'mon slalom,

It's ONLY useful if you're using the default filters, with default settings !!

And unless you have a large display, it's hard to really define the fine differences.

But as soon as you alter the filter scripts, it's useless, and you have to go back to the tried & tested (and full screen) original preview script function.

And for those out there that use their own custom filters, you don't even get the "Demo" option.

And as RB still only has 2 degraining / denoising filters, there are probably a LOT of custom filters being used (me for one).

So like I said before,

Interesting feature, but as it doesn't adjust to user custom settings, it's just "bling".

[Wolfe999]

This small app written in Delphi is specially for people looking for something simple without exotic filters and unnecessary settings

@Atak_Snajpera You were true to your word. What a beautifull and "simple" app you've created, so useful for my needs now. A pity it doesn't have the possibility to choose encoding with Nvidia, but for that purpose there's another great program like StaxRip. Besides, with a Ryzen 2700x I can get "enough" speed.
In any case, thank you, I will begin to use it more frequently from now on.

@Pauly Dunne Thank you so much also for your "extra Avisynth degraining / denoising filters". A fantastic addition and, following your advise, used SMDegrain with more than satisfying results.
Hope you continue and expand your useful work.

And thanx to all the good info I could get reading this thread :D

[guest]

@Pauly Dunne Thank you so much also for your "extra Avisynth degraining / denoising filters". A fantastic addition and, following your advise, used SMDegrain with more than satisfying results.
Hope you continue and expand your useful work.

And thanx to all the good info I could get reading this thread :D

Hi Wolfe999,

Thankyou very much for the great feedback, hopefully some other users might be interested.

And I will continue....

Cheers

[Ripmann]

Phew, what a month. I'll be finally getting back to my encoding backlog soon (haven't even had time to update to see the Demo mode yet) but I just remembered something I wanted to ask Atak for a long, looong, looooong time:

• In the New Job window, the Output (file path/name) edit field: is it possible to make it editable (same as the Description field above it), so I can just CTRL-V paste the path and name without opening a Save As dialogue?

I don't know about the rest of us, but I'd certainly find it extremely time-saving, and I'm guessing it's an extremely quick and easy tweak to do, with no apparent downsides. I'm guessing it was disabled to avoid accidentally misspelled path errors, but hey, if you screw up one time, you'll either return to using the Save As dialogue or start being more careful about what you type in there, right? Thanks, Atak.

[coreying]

Is anyone having issues closing RipBot? I've got 2 Windows 10 systems.

On my brand new AMD Ryzen 5900 system after attempting to close RipBot, the queue window closes, but the system tray icon remains. I have to go to task manager and end process on RipBot264.exe. This happens whether I've done anything in RipBot or not (e.g. open RipBot, do nothing else other than click close). The first version installed here was v1.26.0, but it continues to occur after the update.

My old Intel i7-4770k system didn't have this issue, but then the update to v1.26.1 has introduced the problem on this system too.

[guest]

Is anyone having issues closing RipBot? I've got 2 Windows 10 systems.

On my brand new AMD Ryzen 5900 system after attempting to close RipBot, the queue window closes, but the system tray icon remains. I have to go to task manager and end process on RipBot264.exe. This happens whether I've done anything in RipBot or not (e.g. open RipBot, do nothing else other than click close). The first version installed here was v1.26.0, but it continues to occur after the update.

My old Intel i7-4770k system didn't have this issue, but then the update to v1.26.1 has introduced the problem on this system too.

Hi coreying,

This is your first post here, in just over 8 years....

OK, so unfortunately this seems to happen every so often, and it's not necessarily a fault with RipBot, but it IS annoying when one pc does it, and another doesn't.

I have this happen, and have to do what you described, not sure if Atak would be able to track it down.

Off topic a bit here...

However, I have noticed some rather sneaky changes to RipBot with the last couple of updates (not that should affect this, tho), and it's mainly to do with the Avisynth MTmodes & how many "Use multiple threads for encoding" you can set for Prefetch.

It use to be a Limit of 16, NOW you can go all the way up to 64.

Back on topic...

So have you been using RipBot all these years, or just recently...just wondering about the version you had, before the problem started.

I doubt that it would be the AMD platform, as I have a 3950X, and it tends to behave itself pretty well.

Have you got nVidia software / drivers, or any Logitech stuff ??

[Atak_Snajpera]

Is anyone having issues closing RipBot? I've got 2 Windows 10 systems.

On my brand new AMD Ryzen 5900 system after attempting to close RipBot, the queue window closes, but the system tray icon remains. I have to go to task manager and end process on RipBot264.exe. This happens whether I've done anything in RipBot or not (e.g. open RipBot, do nothing else other than click close). The first version installed here was v1.26.0, but it continues to occur after the update.

My old Intel i7-4770k system didn't have this issue, but then the update to v1.26.1 has introduced the problem on this system too.

Check if problem stil occurs in "safe mode". I suspect some app running in background is doing this.

[guest]

If there's something that has been happening, that's a little annoying is, when using DE, just very randomly, it will just "finish" a Job, and start on the next one, when indeed to previous Job has NOT completed.

Fortunately, 95% of the time, when you go back to that stopped Job, it will resume, BUT when it doesn't, it's rather frustrating, and when that happens on a LONG 4K encode, it's a real PITA !!!

[slalom]

And unless you have a large display, it's hard to really define the fine differences
You should try 27" 1440p

[guest]

You should try 27" 1440p

Maybe so, and I do have a 27" 2160p LG monitor.

But the situation doesn't change, it does NOT display custom settings !!!

[guest]

Phew, what a month. I'll be finally getting back to my encoding backlog soon (haven't even had time to update to see the Demo mode yet) but I just remembered something I wanted to ask Atak for a long, looong, looooong time:

• In the New Job window, the Output (file path/name) edit field: is it possible to make it editable (same as the Description field above it), so I can just CTRL-V paste the path and name without opening a Save As dialogue?

I don't know about the rest of us, but I'd certainly find it extremely time-saving, and I'm guessing it's an extremely quick and easy tweak to do, with no apparent downsides. I'm guessing it was disabled to avoid accidentally misspelled path errors, but hey, if you screw up one time, you'll either return to using the Save As dialogue or start being more careful about what you type in there, right? Thanks, Atak.

Interesting, I just noticed that this field in Batch, IS editable...

[PatchWorKs]

Question/idea: is possible to use a remote G-Colab notebook too as encoding server ?

Some (maybe) useful Colabs:
- https://colab.research.google.com/github/shirooo39/MiXLab/blob/master/MiXLab.ipynb
- https://colab.research.google.com/github/AlphaAtlas/VapourSynthColab/blob/master/VapourSynthColab.ipynb
- https://colab.research.google.com/github/sudo-ken/FFmpeg-for-GDrive/blob/master/FFmpeg_for_GDrive.ipynb
- https://colab.research.google.com/github/yunooooo/FFmpeg-for-Google-Drive/blob/master/FFmpeg.ipynb

Hope that inspires !

note: last but not least, why RB264 does not have a git ?

[coreying]

Hi coreying,

This is your first post here, in just over 8 years....
<snip>
So have you been using RipBot all these years, or just recently...just wondering about the version you had, before the problem started.
Yes, using RipBot all these years. It's excellent software.

Have you got nVidia software / drivers, or any Logitech stuff ??
All the above :)

Check if problem stil occurs in "safe mode". I suspect some app running in background is doing this.
I tried Safe Mode, and yep, RipBot closes fine. So I rebooted into Windows, and first started by closing everything in the System Tray. This is when I noticed that each time I started RipBot, the "NVIDIA Settings" tray icon would reappear.

So I tried stopping the Nvidia services one by one and found that the issue is with the "NVIDIA LocalSystem Container" which starts 3 x nvcontainer.exe background tasks. I can perform a reboot, stop only this single service, and RipBot closes normally.

It appears this service must be running for the NVIDIA GeForce Experience software to work. Not specifically sure why it causes RipBot to break or why RipBot starts the Nvidia tray icon etc.

But I have also replicated this on my old Intel computer that I've used RipBot on successfully for the past 8 years. As mentioned in my previous post, it also broke recently. I thought it was the update to 1.26.1 - but around the same time I had also put in a new GPU which updated the drivers so...

Thanks guys :)

[Atak_Snajpera]

I always install clean drivers without spying services like GeForce experience. By the way. I have never had any issues with AMD drivers for example. NVIDIA really likes to know what executables you launch...

[MCFish]

For some time now encodingclient.exe halts at 100% at random encodes. The main window closes, but the task is running and tray icon still showing 100% completion. When killing task, muxing start and encoding is resuming on next item.
Very annoying as it halts the whole ripbot thing until i kill the task again. Tried to initiate a few encodes from another computer, but same random thing happen.
Seems like it cant quit after encoding sometimes

[Atak_Snajpera]

I haven't touched encodinclient's code for long time so maybe some app running in background is causing this issue. See above posts about GeForce experience

[guest]

For some time now encodingclient.exe halts at 100% at random encodes. The main window closes, but the task is running and tray icon still showing 100% completion. When killing task, muxing start and encoding is resuming on next item.
Very annoying as it halts the whole ripbot thing until i kill the task again. Tried to initiate a few encodes from another computer, but same random thing happen.
Seems like it cant quit after encoding sometimes

That's almost the opposite to the random problems I have...

https://forum.doom9.org/showthread.php?p=1945078#post1945078

But yeah, as Atak mentioned, if you're running any nVidia app's (behind the scenes), they play havoc with certain RB functions...someone needs to fix something...

I think you can disable them in ProcessHacker.....

[MCFish]

No nvidia on that computer. Have only seen the encodingserver thing with nvidia, it doesnt bother me. Ugh finding background task ill save for another day....are alot

[frencher]

Hi all,
I search my future CPU for Ribot264 for 4K h265 @60fps.
AMD Ryzen, Intel i7/i9 ?

My actual CPU is Intel i7 3930k 6/12 threads (2011) recode at 3/4 fps.
My dream is 15/20 or better fps.

i7 3930k vs Last intel i9
https://cpu.userbenchmark.com/Compare/Intel-Core-i9-11900K-vs-Intel-Core-i7-3930K/4110vs1487

[guest]

Hi all,
I search my future CPU for Ribot264 for 4K h265 @60fps.
AMD Ryzen, Intel i7/i9 ?

My actual CPU is Intel i7 3930k 6/12 threads (2011) recode at 3/4 fps.
My dream is 15/20 or better fps.

i7 3930k vs Last intel i9
https://cpu.userbenchmark.com/Compare/Intel-Core-i9-11900K-vs-Intel-Core-i7-3930K/4110vs1487

I have an overclocked 3930K, they were pretty good, back in the day, but these day's, pretty slow for this sort of "work".

I also have a slightly overclocked Ryzen 9 3950X, and it's pretty damn good !! :)

I would strongly suggest a Ryzen 9 5900X (or higher).

Of course a Threadripper 32 or 64 core would just smoke this stuff, but at what cost :(

Check this :-

https://www.tomshardware.com/features/intel-core-i9-11900K-vs-amd-ryzen-9-5900x

[guest]

Hey Ripmann,

Today is your lucky day, Atak has released another autoupdate, and amongst a couple of other changes (yet tbd), your request has been granted, and you can now freely edit this :-• In the New Job window, the Output (file path/name) edit field: is it possible to make it editable (same as the Description field above it), so I can just CTRL-V paste the path and name without opening a Save As dialogue?

[frencher]

I have an overclocked 3930K, they were pretty good, back in the day, but these day's, pretty slow for this sort of "work".

I also have a slightly overclocked Ryzen 9 3950X, and it's pretty damn good !! :)

I would strongly suggest a Ryzen 9 5900X (or higher).

Of course a Threadripper 32 or 64 core would just smoke this stuff, but at what cost :(

Check this :-

https://www.tomshardware.com/features/intel-core-i9-11900K-vs-amd-ryzen-9-5900x

Hello,

How many fps in 4K encoding do you encode with your Ryzen?

Has anyone done the test with a Threadripper 32 or 64?

[guest]

Hello,

How many fps in 4K encoding do you encode with your Ryzen?

Has anyone done the test with a Threadripper 32 or 64?

Hi, I have to admit I haven't used the Ryzen on any encoding recently, and no 4K for even longer, and it so depends on the settings & filters you use, that can affect things so much, but it's reasonably impressive.

Some 4K encodes can take day's, and it's a bit of an anxious wait, hoping nothing goes wrong, and it's all been a waste of time.

So just re reading your 1st post, you state that your future CPU needs to process 4K x265 @ 60fps....that's a lot...

It would probably be cheaper to have 2 5900X's, (than a Threadripper) and use Distributed Encoding, you'd have 32 cores crunching thru this..

I think I need to rethink how I process 4K footage, unless it needs some sort of denoising or cleanup, it probably doesn't warrant the time it takes to encode them, if it's not really necessary.

If you need to remove video, remove or convert audio tracks and unneeded subtitles, there are other substantially quicker ways to achieve that.

There might be some older post's from those who are rich enough to be able to afford a 32 or 64 core Threadripper setup.

[frencher]

Hi, I have to admit I haven't used the Ryzen on any encoding recently, and no 4K for even longer, and it so depends on the settings & filters you use, that can affect things so much, but it's reasonably impressive.

Some 4K encodes can take day's, and it's a bit of an anxious wait, hoping nothing goes wrong, and it's all been a waste of time.

So just re reading your 1st post, you state that your future CPU needs to process 4K x265 @ 60fps....that's a lot...

It would probably be cheaper to have 2 5900X's, (than a Threadripper) and use Distributed Encoding, you'd have 32 cores crunching thru this..

I think I need to rethink how I process 4K footage, unless it needs some sort of denoising or cleanup, it probably doesn't warrant the time it takes to encode them, if it's not really necessary.

If you need to remove video, remove or convert audio tracks and unneeded subtitles, there are other substantially quicker ways to achieve that.

There might be some older post's from those who are rich enough to be able to afford a 32 or 64 core Threadripper setup.

4K @ 15/20 fps ;)
Here h265 4K to h265 1080p

https://i.goopics.net/800/w9AgR.jpg (https://goopics.net/i/w9AgR)

With Threadreapper :goodpost:

We now move into the world of video encoding, wherein you are at the whims of the encoder itself. As you can see here, the x.265 encoder demands clock speed almost as much as raw core count, with the 3960X and 3970X outperforming our tweaked 3990X.
https://overclock3d.net/reviews/cpu_mainboard/amd_ryzen_threadripper_3990x_64_core_monster_review/7
https://overclock3d.net/gfx/articles/2020/04/12092218585l.jpg

[chainring]

@ frencher

Do you have a link handy for that x265 benchmark? Searching brings up multiple hits and different tools.

Thanks!

[frencher]

@ frencher

Do you have a link handy for that x265 benchmark? Searching brings up multiple hits and different tools.

Thanks!

The benchmark link is just above the screenshot

Ryzen Threadripper PRO 3995WX à 64 cores / 128 threads @ 5489 dollars :eek:
Look here: https://www.tomshardware.fr/les-ryzen-threadripper-pro-debarquent-sur-le-marche-diy/

[Atak_Snajpera]

That benchmark does not show full potential of 3990X!
In distributed encoding mode 64 core CPU will be always noticeable faster than OC 32 core. Check my x265 FHD Benchmark. Divide FPS by 4 to get estimated speed for 4k resolution.
https://forum.pclab.pl/topic/1184884-x265-fhd-benchmark/

[chainring]

I mean the actual benchmark program itself. I looked at the link you posted and I'm either blind or they make it exceedingly difficult to find the benchmark program.

edit: Just realized that may not be your benchmark run. Duh.

[frencher]

That benchmark does not show full potential of 3990X!
In distributed encoding mode 64 core CPU will be always noticeable faster than OC 32 core. Check my x265 FHD Benchmark. Divide FPS by 4 to get estimated speed for 4k resolution.
https://forum.pclab.pl/topic/1184884-x265-fhd-benchmark/

Atak,
Would you have a screenshot with x265 FHD Benchmark and your processor.
Thank you.

[frencher]

I mean the actual benchmark program itself. I looked at the link you posted and I'm either blind or they make it exceedingly difficult to find the benchmark program.

edit: Just realized that may not be your benchmark run. Duh.

http://www.mediafire.com/file/nm5n7xg2nb22zl7/x265_FHD_Benchmark.7z/file

[Atak_Snajpera]

Atak,
Would you have a screenshot with x265 FHD Benchmark and your processor.
Thank you.

This
http://i.cubeupload.com/CJ6v4n.png

[frencher]

i7 3930k :(

https://i.goopics.net/800/gYy4J.jpg (https://goopics.net/i/gYy4J)

Intel Core i7-3930K @ 3.2GHz ( 6C / 12T )

y4m [info]: 1920x1080 fps 50/1 i420p8 sar 1:1 unknown frame count
raw [info]: output file: NUL
x265 [info]: HEVC encoder version 2.2+15-a18ab7656c30
x265 [info]: build info [Windows][GCC 6.2.0][64 bit] 8bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
x265 [info]: Main Still Picture profile, Level-4.1 (Main tier)
x265 [info]: Thread pool created using 12 threads
x265 [info]: Slices : 1
x265 [info]: frame threads / pool features : 3 / wpp(17 rows)
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : hex / 57 / 2 / 2
x265 [info]: Keyframe min / max / scenecut / bias: 50 / 500 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 3 / on / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 1 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : CRF-28.0 / 0.60
x265 [info]: tools: rd=3 psy-rd=2.00 rskip signhide tmvp strong-intra-smoothing
x265 [info]: tools: lslices=6 deblock sao

encoded 2500 frames in 202.16s (12.37 fps), 7025.74 kbps, Avg QP:37.21

Results please send to: x264.fhd.benchmark@gmail.com