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

Ryushin
1st April 2019, 19:12
One other question about x265. I have just recently started to try some x265 encodes but the output did not look that good compared to my x264 encodes.
Most of my x264 encoding is done at CRF18 "Very Slow" with "Film" tune. I realise that you cannot compare x264 settings to x265 but what is the closest equivalent x265 settings?

I switched everything to x265 last fall. I did CRF18 for x264 with similar settings as you. I'm still using CRF18 for x265 and always doing 10 bit regardless of it being a 8 or 10 bit source. I'm not doing any special tuning settings, just using x265 progressive with just adding the --par 1:1. I've not noticed a single case where the x265 looks worse then the x264. It either looks the same or better. File size is usually 25-50% smaller then the x264 source. Supposedly, x265 CRF20 is equivalent to CRG18 x264.

Atak lives and breaths this stuff, so he might have better insight.

Ryushin
2nd April 2019, 02:42
Atak, any idea on a solution to VC-1 sources? Just pulled in Jurassic Park 1-3 to redo them in x265 and it seems they are all VC-1. I'm thinking I might just go back to doing lossless x264 for the time being.

I downloaded ffms2 2.23.1 but it seems that dll was built in December. Maybe it would be best if I just open an issue on github to see if they can duplicate the problem and fix it.

duffbeer
2nd April 2019, 08:57
Atak, any idea on a solution to VC-1 sources? Just pulled in Jurassic Park 1-3 to redo them in x265 and it seems they are all VC-1. I'm thinking I might just go back to doing lossless x264 for the time being.

I downloaded ffms2 2.23.1 but it seems that dll was built in December. Maybe it would be best if I just open an issue on github to see if they can duplicate the problem and fix it.

Is there a problem with VC-1 sources? I hope not as I have encoded quite a few recently. The encoded files looked OK but I haven't watched them all the way through yet.
Never had a problem with VC-1 in the past.

Ryushin
3rd April 2019, 01:13
Is there a problem with VC-1 sources? I hope not as I have encoded quite a few recently. The encoded files looked OK but I haven't watched them all the way through yet.
Never had a problem with VC-1 in the past.

If you are using DE, then you will need to look where the chunks split. For me, a lot seems to be around the 4:00 minute mark. I had decoding issues before with VC-1 before the new update. Decoding issues are gone, but it is not frame accurate for some sources it seems. Blade Runner turned out fine, but four other sources now have not.

Ryushin
5th April 2019, 15:00
Atak, any idea on a solution to VC-1 sources? Just pulled in Jurassic Park 1-3 to redo them in x265 and it seems they are all VC-1. I'm thinking I might just go back to doing lossless x264 for the time being.


Nothing like having a 250GB lossless file to do an encoding. Plus I have to modify the avs file for this. I think I may just try to do any vc-1 sources on a non DE machine and see how that works out.

byteshare
5th April 2019, 16:57
Nothing like having a 250GB lossless file to do an encoding. Plus I have to modify the avs file for this. I think I may just try to do any vc-1 sources on a non DE machine and see how that works out.
Would it be faster/smaller/easier to just encode to 264x CRF1 very fast preset in another application that doesn't have issues with VC-1?

Atak_Snajpera
5th April 2019, 18:01
Nothing like having a 250GB lossless file to do an encoding. Plus I have to modify the avs file for this. I think I may just try to do any vc-1 sources on a non DE machine and see how that works out.

If I were you I would encode to AVC-INTRA with CRF10 instead of lossless.

Reasons:
1) Much smaller filer size
2) Much faster encoding
3) Still visually "lossless"

You really do not need perfect 1:1 copy if you are going to compress later even further with some more aggressive bitrate/CRF.

Ryushin
7th April 2019, 13:30
Well, VC-1 sources using a non DE came out fine. They decoded correctly and I don't see any kind of corruption. I will just have to do this until a ffms2 comes out that decodes correctly along with being frame accurate.

Atak, not sure how you want to deal with this in your code. Maybe have a popup when detecting a VC-1 source that using DE will cause corruption.

byteshare
8th April 2019, 16:42
TLDR: Install official drivers even if the Windows ones work

I have a Nvidia GTX 980.
I couldn't seem to get it listed in the settings as a device for "x264 OpenCL acceleration" or KNLMeansCL"
Guessing it is a drive/OpenCL issue.
I checked out this: https://streamhpc.com/blog/2015-03-16/how-to-install-opencl-on-windows/
But under the link for Nvidia: https://www.nvidia.com/Download/index.aspx#
I don't see an option for OpenCL support.
I found this page: https://developer.nvidia.com/opencl
Which says the OpenCL is included in GPU drivers.
I re-downloaded the drivers for my card and installed them and then I could see my device as an option in RipBot.

Atak_Snajpera
8th April 2019, 19:06
If you are using DE, then you will need to look where the chunks split. For me, a lot seems to be around the 4:00 minute mark. I had decoding issues before with VC-1 before the new update. Decoding issues are gone, but it is not frame accurate for some sources it seems. Blade Runner turned out fine, but four other sources now have not.

If this happens at 4:00 mark then maybe you could cut out first 5 minutes from source video and send it to me?

Ryushin
9th April 2019, 18:12
If this happens at 4:00 mark then maybe you could cut out first 5 minutes from source video and send it to me?

I'm seeing random frame corruption even when not using DE. And it seems to be random. Doing another encode of the trimmed version did not show the same corruption in the same place.
https://i.postimg.cc/bs4vs8qv/VC-1-Decoding-Frame-Corruption.png (https://postimg.cc/bs4vs8qv)

I'll get you a trimmed 5 minute source of the source that I use for testing. Thing is, the new ffms2 fixed the decoding problem but not the DE corruption at the 4 minutes mark.

byteshare
9th April 2019, 19:22
I'm seeing random frame corruption even when not using DE. And it seems to be random. Doing another encode of the trimmed version did not show the same corruption in the same place.
https://i.postimg.cc/bs4vs8qv/VC-1-Decoding-Frame-Corruption.png (https://postimg.cc/bs4vs8qv)

I'll get you a trimmed 5 minute source of the source that I use for testing. Thing is, the new ffms2 fixed the decoding problem but not the DE corruption at the 4 minutes mark.
Is the screenshot from VLC? Is it the same in MPC-HC (Media Player Classic Home Cinema)

Ryushin
9th April 2019, 22:13
Is the screenshot from VLC? Is it the same in MPC-HC (Media Player Classic Home Cinema)

VLC, SMPlayer, MPlayer, MPV Player, and MPC-HC all have the same corruption.

The joy of VC-1.

byteshare
9th April 2019, 22:37
VLC, SMPlayer, MPlayer, MPV Player, and MPC-HC all have the same corruption.

The joy of VC-1.
Just checking because I've seen that sort of visual issue with VLC but then not seen it with the same file in other players such as SMPlayer and MPC-HC.

Viper714
10th April 2019, 23:42
So, I am having an issue with my Encoding server on one machine out of three. Unfortunately it is the latest machine with the more powerful CPU & GPU. I start the encoding server and it it does not show on the taskbar or the system tray. If I go to the task manager it is there. Anybody have this issue?? It worked great about 3-4 weeks ago when I last used it. I recently updated to Windows 1809. could that be the issue? Would appreciate any help on this one!! Thanks

Atak_Snajpera
11th April 2019, 10:31
Use Process Hacker or Process Explorer to check if EncodingServer.exe is not being blocked by other program.
https://forum.doom9.org/showthread.php?p=1862506#post1862506

Ryushin
11th April 2019, 16:34
If this happens at 4:00 mark then maybe you could cut out first 5 minutes from source video and send it to me?

So I've trimmed it to 5, 10, and 15 minutes and the corruption does not show up. But it does every time I do the native source. I'll watch the 15 minutes source all the way through and see if it happens that I can repeat. This inconsistency with VC-1 is getting on my nerves. <grrrrrr>

byteshare
11th April 2019, 20:20
So I've trimmed it to 5, 10, and 15 minutes and the corruption does not show up. But it does every time I do the native source. I'll watch the 15 minutes source all the way through and see if it happens that I can repeat. This inconsistency with VC-1 is getting on my nerves. <grrrrrr>
Have you tried remuxing the whole thing to see if maybe the container is causing some issue?

duffbeer
12th April 2019, 09:06
Have you tried remuxing the whole thing to see if maybe the container is causing some issue?

I've seen no problems with any of my VC-1 encodes and I have done quite a few recently. I don't use DE as I only have 1 PC.
I haven't seen any other reports of this issue so maybe the problem is local to your setup?

Ryushin
13th April 2019, 14:46
I've seen no problems with any of my VC-1 encodes and I have done quite a few recently. I don't use DE as I only have 1 PC.
I haven't seen any other reports of this issue so maybe the problem is local to your setup?

Well, for giggles I'll pull down the latest version and let it do updates and run my tests again.

stryker412
13th April 2019, 18:20
I'm building a new machine. I currently have an aging i7-950 and encodes take a little over an hour per episode for a 45 minute ep on 2-pass. What is Ripbot more dependent on, GPU or CPU/RAM?

Atak_Snajpera
13th April 2019, 18:23
Cpu with many cores...

stryker412
13th April 2019, 18:28
Cpu with many cores...

With an 8 core, what types of speed increases would I see?

https://cpu.userbenchmark.com/Compare/Intel-Core-i7-9700K-vs-Intel-Core-i7-950/4030vs617

Atak_Snajpera
13th April 2019, 18:29
x264 or x265? Ryzen cpu?

stryker412
13th April 2019, 18:30
x264 or x265? Ryzen cpu?

Just edited my previous post with a comparison. I mainly use x264, I haven't gotten into x265 just yet.

Atak_Snajpera
13th April 2019, 18:34
Something around 3x speed up

stryker412
13th April 2019, 18:35
Something around 3x speed up

Ok so like I said, my episodes take a little over an hour and they would decrease to ~20 minutes? Nice! Thanks.

Atak_Snajpera
13th April 2019, 18:44
IPC in 9gen is atleast 1.5x higher than in Nehalem. Furthermore You also get higher all core turbo clock + faster ram so 3x should be a minimum.

Ryushin
18th April 2019, 01:54
If this happens at 4:00 mark then maybe you could cut out first 5 minutes from source video and send it to me?

I have a VC-1 source that is giving me corruption using DE or standalone. I've trimmed the Blu-ray source down and removed everything except trimmed m2ts file under STREAM.

There is also two samples along with a text file that outlines the corruption times. Link expires in two weeks:
https://cloud.chrisdos.com/index.php/s/TkXFnas6yMqtnE4

Please let me know if there is anything else I can provide.

Ryushin
18th April 2019, 17:05
I have a VC-1 source that is giving me corruption using DE or standalone. I've trimmed the Blu-ray source down and removed everything except trimmed m2ts file under STREAM.

There is also two samples along with a text file that outlines the corruption times. Link expires in two weeks:
https://cloud.chrisdos.com/index.php/s/TkXFnas6yMqtnE4

Please let me know if there is anything else I can provide.

BTW, I installed fresh copies of the latest version of Ripbot. Only thing I backed up and restore were my two ini files. I also made a change in the profile to add --sar 1:1.

Viper714
19th April 2019, 23:28
Use Process Hacker or Process Explorer to check if EncodingServer.exe is not being blocked by other program.
https://forum.doom9.org/showthread.php?p=1862506#post1862506

Atak,
I've downloaded both apps and for the life of me can't figure out how to check what is blocking the encoding server.exe. I am positing a screenshot of both the app and taskmanager in order to get some help on this.
Thanks
https://oi1378.photobucket.com/albums/ah89/Viper71463/RipBot_zpss2o6wrdq.png (https://s1378.photobucket.com/user/Viper71463/media/RipBot_zpss2o6wrdq.png.html)

Atak_Snajpera
20th April 2019, 09:54
check if EncodingServer.exe shows up in safe mode.

Viper714
21st April 2019, 20:07
check if EncodingServer.exe shows up in safe mode.

Atak,
So based on your suggestion, The encoding server did indeed run in safe mode. With that said, I decided to turn off all of my "startup" programs in task manager and turn them on a few at a time to find the culprit.
It was not "Everything" as I though it may have been, but a program called "Logitech Gaming Framework." Talk about weird!! No sure how that would interfere. I do have a Logitech Gaming keyboard and Flight sticks. I am going to have to remember to disable this program from starting when I am going to encode movies.

https://oi1378.photobucket.com/albums/ah89/Viper71463/Logitech%20GF_zpscbgbngxk.png (https://s1378.photobucket.com/user/Viper71463/media/Logitech%20GF_zpscbgbngxk.png.html)

Is there anything that I can provide you to possibly prevent this block from happening. I would be more than happy to provide it.
Thanks for pointing me in the right direction.
:thanks:

Atak_Snajpera
21st April 2019, 20:32
Maybe you could contact logitech support and ask them why they inject to other process and thereby block it? This not a normal behaviour in my book... People behind "everything" seem to fix this because it was doing the same thing in the past according to other user.

Viper714
22nd April 2019, 14:03
Maybe you could contact logitech support and ask them why they inject to other process and thereby block it? This not a normal behaviour in my book... People behind "everything" seem to fix this because it was doing the same thing in the past according to other user.

Okay, will do. I have a feeling that it is going to take them a while, but I will definitely contact them. I agree with your view. Thanks!!!

FuzzyNutz
22nd April 2019, 17:09
Ripbot is outputting videos with occasional blocky-digital artifacts when the source is VC-1. I get the same result whether ffdshow's video decoder is set to wmv9 or Intel QuickSync.

Ryushin
23rd April 2019, 17:18
Ripbot is outputting videos with occasional blocky-digital artifacts when the source is VC-1. I get the same result whether ffdshow's video decoder is set to wmv9 or Intel QuickSync.

I've found this problem as well. Please see:
https://forum.doom9.org/showpost.php?p=1866652&postcount=16747
https://forum.doom9.org/showpost.php?p=1863974&postcount=16631

The recent versions of Ripbot264 fixed the decoding issue though, but does not seems frame accurate.

VC-1 sources are just a pain to deal with.

Atak_Snajpera
23rd April 2019, 17:54
I've found this problem as well. Please see:
https://forum.doom9.org/showpost.php?p=1866652&postcount=16747
https://forum.doom9.org/showpost.php?p=1863974&postcount=16631

The recent versions of Ripbot264 fixed the decoding issue though, but does not seems frame accurate.

VC-1 sources are just a pain to deal with.

Works fine for your recently uploaded sample. Chunks are correctly stitched.

Ryushin
23rd April 2019, 19:30
Works fine for your recently uploaded sample. Chunks are correctly stitched.

Then perhaps it has something to do with AviSynth, FFDShow, or Haali Media Splitter that is installed the same way on all four machines. What versions are you recommending?

Atak_Snajpera
24th April 2019, 11:29
Then perhaps it has something to do with AviSynth, FFDShow, or Haali Media Splitter that is installed the same way on all four machines. What versions are you recommending?

How do you know that you have issues with frame accurate seeking? Can you again upload sample showing issues at stitching? I assume you are referring to DE mode...

sneaker_ger
24th April 2019, 11:44
Then perhaps it has something to do with AviSynth, FFDShow, or Haali Media Splitter
I thought you were using ffms2? ffdshow and Haali shouldn't matter, then.

Ryushin
24th April 2019, 12:06
How do you know that you have issues with frame accurate seeking? Can you again upload sample showing issues at stitching? I assume you are referring to DE mode...

Not sure if I'm understanding or not. The link is posted included two encodings along with the times corruption occurred. The DE showed issues at multiple minute marks.

Atak_Snajpera
24th April 2019, 13:12
Not sure if I'm understanding or not. The link is posted included two encodings along with the times corruption occurred. The DE showed issues at multiple minute marks.

well I was under impression that you still have issues even with latest update. Like I said latest version works fine with your uploaded sample.

Ryushin
24th April 2019, 13:41
well I was under impression that you still have issues even with latest update. Like I said latest version works fine with your uploaded sample.

I'll have it check for updates and run it again. Thanks Atak.

duffbeer
24th April 2019, 15:37
All this talk of VC-1 problems has me worried. I've encoded dozens of VC-1 sources recently and I haven't got time to watch all of them.
I've watched a few and so far I've seen no issues but I've got at least 20 more to do and I'm worried that they may encode with errors that I won't see for a little while until I get time to watch them again.

What's the real issue here? Is it just with DE or not?

Atak_Snajpera
24th April 2019, 16:26
All this talk of VC-1 problems has me worried. I've encoded dozens of VC-1 sources recently and I haven't got time to watch all of them.
I've watched a few and so far I've seen no issues but I've got at least 20 more to do and I'm worried that they may encode with errors that I won't see for a little while until I get time to watch them again.

What's the real issue here? Is it just with DE or not?

Mainly in DE mode at stitching points (at 1:00 , 2:00 , 3:00 and so on).
My advise is to encode one movie and then check if you see any corrupted frames at above marks. If everything is ok then you are good to go with rest of your vc1 library.

duffbeer
24th April 2019, 16:41
Mainly in DE mode at stitching points (at 1:00 , 2:00 , 3:00 and so on).
My advise is to encode one movie and then check if you see any corrupted frames at above marks. If everything is ok then you are good to go with rest of your vc1 library.

Thanks Atak. I don't use DE at all so I'm hoping it won't affect me. I've watched a couple recently and didn't see any problems at all and I've never had problems with VC-1 in the past either so I'm not sure where the current issues have come from all of a sudden.

archiel
24th April 2019, 18:20
After adding a Hyper-V VM to my PC I can no longer use Distributed Encloding. Hyper-V adds vEthernet(Default Switch) - used for NAT between the VM and the Network - and assigns a 172.17.x.x/28 address, which changes on each reboot and with only NAT connectivity - Connected to unknown network no traffic. The standard PC IP address in this case 10.55.63.115 is assigned to the vEthernet (External Virtual Switch) Hyper-V Virtual Ethernet Adapter #2.

In the Distributed Encoding tab, the IP address for both Client and Servers are set to 10:55.63.115, but the servers always start-up using the 172.17.x.x address. As a result the servers are seen as Offline. Setting the Client and Server IPs to the 172.17.x.x brings them online, but the NAT only connectivity means that there is still no usable connection.
The servers show ADAPTER0:172.17.x.x and ADAPTER1:10.55.63.115, but only connect to ADAPTER0.

Is there a way to run in Distributed Mode without shutting down the VM?

n.b. I am using DE as it is easier to manage the CPU workload this way rather than manually disabling cores from Task Manager.

Atak_Snajpera
24th April 2019, 18:56
After adding a Hyper-V VM to my PC I can no longer use Distributed Encloding. Hyper-V adds vEthernet(Default Switch) - used for NAT between the VM and the Network - and assigns a 172.17.x.x/28 address, which changes on each reboot and with only NAT connectivity - Connected to unknown network no traffic. The standard PC IP address in this case 10.55.63.115 is assigned to the vEthernet (External Virtual Switch) Hyper-V Virtual Ethernet Adapter #2.

In the Distributed Encoding tab, the IP address for both Client and Servers are set to 10:55.63.115, but the servers always start-up using the 172.17.x.x address. As a result the servers are seen as Offline. Setting the Client and Server IPs to the 172.17.x.x brings them online, but the NAT only connectivity means that there is still no usable connection.
The servers show ADAPTER0:172.17.x.x and ADAPTER1:10.55.63.115, but only connect to ADAPTER0.

Is there a way to run in Distributed Mode without shutting down the VM?

n.b. I am using DE as it is easier to manage the CPU workload this way rather than manually disabling cores from Task Manager.

Could you post some screenshots to help me visualize your issue?

archiel
24th April 2019, 20:22
ipconfig gives

connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
Physical Address. . . . . . . . . : 1C-87-2C-42-1F-38
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a02:c7f:c038:e300:84cc:9e40:3222:143(Preferred)
Temporary IPv6 Address. . . . . . : 2a02:c7f:c038:e300:7957:24f0:84c9:85f7(Preferred)
Link-local IPv6 Address . . . . . : fe80::84cc:9e40:3222:143%8(Preferred)
IPv4 Address. . . . . . . . . . . : 10.55.63.115(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 18 April 2019 11:26:20
Lease Expires . . . . . . . . . . : 19 April 2019 11:26:24
Default Gateway . . . . . . . . . : fe80::ae9e:17ff:fe45:26f8%8
10.55.63.1
DHCP Server . . . . . . . . . . . : 10.55.63.1
DHCPv6 IAID . . . . . . . . . . . : 320636716
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-BF-CB-2C-1C-87-2C-42-1F-38
DNS Servers . . . . . . . . . . . : 2a02:c7f:c038:e300::1
2a02:c7f:c038:e300::1
10.55.63.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter vEthernet (Default Switch):

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
Physical Address. . . . . . . . . : AE-15-4A-FF-42-27
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::358c:6941:5f5e:a048%19(Preferred)
IPv4 Address. . . . . . . . . . . : 172.17.2.225(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 330175818
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-BF-CB-2C-1C-87-2C-42-1F-38
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled