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

byteshare
13th September 2017, 20:33
Because all plugins are still 32bit.
I thought the plugins that came with the 64bit AVISynth+ would be 64bit. My mistake, didn't think about it being more dependent on the plugins in RipBot.
I know MVTools and a few others should support 64bit.

You will have to reduce prefech limit significantly because it looks like you are using some very demanding filters.
My filters:
LoadPlugin("C:\RipBot264v1.20.0\Tools\AviSynth plugins\hqdn3d\hqdn3d.dll")
LoadPlugin("C:\RipBot264v1.20.0\Tools\AviSynth plugins\flash3kyuu_deband\flash3kyuu_deband.dll")
LoadPlugin("C:\RipBot264v1.20.0\Tools\AviSynth plugins\masktools\masktools2.dll")
Loadplugin("C:\RipBot264v1.20.0\Tools\AviSynth plugins\mvtools\mvtools2.dll")
LoadPlugin("C:\RipBot264v1.20.0\Tools\AviSynth plugins\Custom\Deen.dll")
Import("C:\RipBot264v1.20.0\Tools\AviSynth plugins\Custom\HQdering.avs")
super = video.MSuper(pel=2)
bv1 = MAnalyse(super, isb = true, delta = 1, overlap=4)
fv1 = MAnalyse(super, isb = false, delta = 1, overlap=4)
bv2 = MAnalyse(super, isb = true, delta = 2, overlap=4)
fv2 = MAnalyse(super, isb = false, delta = 2, overlap=4)
bv3 = MAnalyse(super, isb = true, delta = 3, overlap=4)
fv3 = MAnalyse(super, isb = false, delta = 3, overlap=4)
video=video.MDegrain3(super,bv1,fv1,bv2,fv2,bv3,fv3,thSAD=1000).HQDering(strength=255).f3kdb
I'm using prefetch 2 right now, I can try 1 but most likely will have to stick with non-MT mode which puts my memory usage around 1.3-1.5GB (avs2yuv.ext) per server.

skylinekiller
13th September 2017, 20:34
Currently it only works if subtitle has the same name as video file. so if I do the exact same thing I did, but change my test file to the exact same as the movie title, it will hard code when it burns?

Atak_Snajpera
13th September 2017, 20:53
@byteshare
Are you working with 4k footage that you can't go above 2?

slalom
14th September 2017, 17:09
Hello. Not used ripbot in a while, quite a while in fact and have ran into a problem.

I have all the necessary additional tools installed, haali, avsynth, etc. When I load a file into ripbot, it takes ages to demux, even though I have 3 HDs. Once the file is finally demuxed, ripbot just sits there with the, "please wait, gathering information" message, and nothing happens at all. I have to abort the process.

I am running:
Ryzen 8 core 1700@3.70ghz, no overclocking.
16gig DDR4 3600mhz.
Windows Pro 64bit.

Regards....
Same problem here, did you find a solution?

MaistroX
14th September 2017, 20:25
Hey!

My RipBot just stopped working after it updated to 1.20.1! :(

Every prepared Movie in que just fails direct after I push START, all with the same fault in Error Message:

"
C:\>"C:\5.8 RipBot264 v1.19.2\tools\avs2yuv\avs2yuv.exe" "C:\Temp\RipBot264temp\job1\job1.avs" -o - | "C:\5.8 RipBot264 v1.19.2\tools\x264\x264_x64.exe" --pass 1 --bitrate 10000 --stats "C:\Temp\RipBot264temp\job1\job1.stats" --fps 24000/1001 --force-cfr --min-keyint 24 --keyint 240 --frames 185749 --sar 1:1 --threads 8 --pass 2 --level 4.1 --preset slower --vbv-bufsize 62500 --vbv-maxrate 62500 --filter 0,0 --ref 7 --no-mixed-refs --bframes 10 --b-adapt 2 --b-pyramid none --subme 7 --aq-mode 1 --trellis 2 --partitions all --me tesa --stdin y4m --output NUL -
y4m [info]: 1920x800p 1:1 @ 10000000/417083 fps (cfr)
x264 [info]: using SAR=1/1
x264 [warning]: DPB size (7 frames, 42000 mbs) > level limit (5 frames, 32768 mbs)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX XOP FMA3 BMI1
x264 [error]: ratecontrol_init: can't open stats file
x264 [error]: x264_encoder_open failed

C:\Temp\RipBot264temp\job1\job1.avs: 1920x800, 10000000/417083 fps, 185749 frames
error: wrote only 2285802 of 2304000 bytes

C:\>"C:\5.8 RipBot264 v1.19.2\tools\avs2yuv\avs2yuv.exe" "C:\Temp\RipBot264temp\job1\job1.avs" -o - | "C:\5.8 RipBot264 v1.19.2\tools\x264\x264_x64.exe" --pass 2 --bitrate 10000 --stats "C:\Temp\RipBot264temp\job1\job1.stats" --fps 24000/1001 --force-cfr --min-keyint 24 --keyint 240 --frames 185749 --sar 1:1 --threads 8 --pass 2 --level 4.1 --preset slower --vbv-bufsize 62500 --vbv-maxrate 62500 --filter 0,0 --ref 7 --no-mixed-refs --bframes 10 --b-adapt 2 --b-pyramid none --subme 7 --aq-mode 1 --trellis 2 --partitions all --me tesa --stdin y4m --output "C:\Temp\RipBot264temp\video.264" -
y4m [info]: 1920x800p 1:1 @ 10000000/417083 fps (cfr)
x264 [info]: using SAR=1/1
x264 [warning]: DPB size (7 frames, 42000 mbs) > level limit (5 frames, 32768 mbs)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX XOP FMA3 BMI1
x264 [error]: ratecontrol_init: can't open stats file
x264 [error]: x264_encoder_open failed

C:\Temp\RipBot264temp\job1\job1.avs: 1920x800, 10000000/417083 fps, 185749 frames
error: wrote only 2285802 of 2304000 bytes

C:\>"C:\5.8 RipBot264 v1.19.2\tools\mkvtoolnix\mkvmerge.exe" -o "C:\TEMP\Movie_2017.mkv" --compression 0:none --title "Movie_2017" --default-duration 0:24000/1001fps "C:\Temp\RipBot264temp\video.264"
mkvmerge v14.0.0 ('Flow') 32bit
Error: The type of file 'C:\Temp\RipBot264temp\video.264' could not be recognized.
-------------------------

Elapsed Time: 00h:00m:02s"

What has happened here, can anyone please explain?

P.S I havent changed a thing in setting nor in my Profiles/Avc/[HIGH 4.1] 1080p BÄSTA SLOWER . DEFAULT.txt , that I have used for years now.

sneaker_ger
14th September 2017, 20:35
First pass has both "--pass 1" and "--pass 2", first one gets ignored and it fails because naturally there is no pass file yet. But I don't know why RipBot did that. Or did you manually set "--pass 2" by accident somehow?

MaistroX
15th September 2017, 17:20
yes I did, will remove it, but it was the same Before with out both of them, RipBot would´nt start as it did Before 1.20.1 update! :(


First pass has both "--pass 1" and "--pass 2", first one gets ignored and it fails because naturally there is no pass file yet. But I don't know why RipBot did that. Or did you manually set "--pass 2" by accident somehow?

Atak_Snajpera
15th September 2017, 17:53
yes I did, will remove it, but it was the same Before with out both of them, RipBot would´nt start as it did Before 1.20.1 update! :(

So show us new log then.

klopsknoedel
16th September 2017, 02:55
@Big Gern
@slalom

Have you tried this: http://forum.doom9.org/showthread.php?p=1524496#post1524496

slalom
16th September 2017, 08:34
I've gone back to 1.20.0 with no updates and it works fine

byteshare
18th September 2017, 20:41
@byteshare
Are you working with 4k footage that you can't go above 2?
Correct, I am indeed working with 4K footage.

guest
20th September 2017, 08:09
Well, I have just discovered a major problem with the latest auto update.
I had a batch queue encoding using the previous update (11/09/17), and it was working well, so I then updated to (13/09/17), and the DE went berserk, only a couple of the 10 servers I had enabled, connected, and I could not re connect them.

So now I'll have to "re install" the "vanilla" 1.20.0, and update up to the second last update....unless there's a fix, beforehand :)

EDIT:- Well, it's all working nicely today.....the only thing that I have changed was, I disabled x264 OpenCL acceleration for my GTX 580 card.....

byteshare
20th September 2017, 16:58
Well, I have just discovered a major problem with the latest auto update.
I had a batch queue encoding using the previous update (11/09/17), and it was working well, so I then updated to (13/09/17), and the DE went berserk, only a couple of the 10 servers I had enabled, connected, and I could not re connect them.

So now I'll have to "re install" the "vanilla" 1.20.0, and update up to the second last update....unless there's a fix, beforehand :)

I didn't have this issue.

guest
21st September 2017, 03:53
I didn't have this issue.

It's working alright, today (see my previous post)

guest
21st September 2017, 13:33
So I'm having a bit of a problem with the auto shutdown option.

I generally have a "main" pc doing the Ripbot "thing", and one server helping.

Twice now (which is as many times as I've used it), when I have selected "Shutdown Servers" option, it shutdowns both pc's...I haven't tried the "Shutdown Client" option.....

I have all 16 servers enabled, 10 on the main pc, and 6 on the "helper"....maybe that shutdown option can't tell the difference between the 2....

Also, auto update hasn't worked for the last couple of days :(

Atak_Snajpera
21st September 2017, 14:26
Shutdown Servers option basically tells Encoding client to send shutdown command to ALL specified IP's. So It will shutdown your main PC as well if you also have running encodingserver.exe in background.

Also, auto update hasn't worked for the last couple of days
It was intentionally disabled by me because newer version 1.21.0 will only work with AViSynth+ MT x64. Also due to this change old jobs created by 1.20.x won't work in newer x64 environment!
I decided to abandon x86 mainly due to annoying 2 GiB limit which can be easily reached when working with multiple processing threads.

byteshare
21st September 2017, 17:00
It was intentionally disabled by me because newer version 1.21.0 will only work with AViSynth+ MT x64. Also due to this change old jobs created by 1.20.x won't work in newer x64 environment!
I decided to abandon x86 mainly due to annoying 2 GiB limit which can be easily reached when working with multiple processing threads.

This is awesome. Looking forward to my batch of encodes finishing so I can test this out.

Atak_Snajpera
21st September 2017, 17:12
v1.21.0
Added: Support for AviSynth+ MT x64 (installer located in \Tools\AviSynth folder)
Finally no need to automatically limit processing threads due to 32bit memory limitation.
Warning! Jobs created by older version won't work with this version! You must start with freshly created job!
Fixed: Various tweaks and changes under the hood.
Updated: MKVToolnix v15.0.0, EncodingServer v1.8.1

byteshare
21st September 2017, 19:14
Playing with the new version now, love what you did with AVISynth installer.
For x265
I'm only seeing 1 file in the folder now: x265_x64.exe
Before there were 4 files x265_x64.exe, x265_x64_10bit.exe, x265_x86.exe, and x265_x86_10bit.exe
I wanted to update becase the x265 is on 2.5+4 and stable is 2.5+5
My question before is figuring out which files to take from: http://msystem.waw.pl/x265/ wasn't too hard before.

The x265 files (for updating) come as:
libx265_main.dll
libx265_main10.dll
libx265_main12.dll
x265.exe
x265_32.exe
x265-8b.exe
x265-8b_32.exe
x265-10b.exe
x265-10b_32.exe
x265-12b.exe
x265-12b_32.exe

My guess was to use the x265.exe but it is significantly larger than the x265_x64.exe that comes with 1.21.0
Suggestion?

Atak_Snajpera
21st September 2017, 19:27
Yes use the largest binary (all in one).

soneca
21st September 2017, 19:45
In this new release RipBot264 can not be started because MSVCP140.dll is missing.

byteshare
21st September 2017, 20:04
In this new release RipBot264 can not be started because MSVCP140.dll is missing.

Try reinstalling Visual C++ Redistributable for Visual Studio 2015
32bit and 64bit
https://www.microsoft.com/en-US/download/details.aspx?id=48145

Atak_Snajpera
21st September 2017, 20:12
Whole collection
http://www.mediafire.com/file/v8cwedgd1y7ys0g/vc_redist.7z

soneca
21st September 2017, 21:10
But I already have Visual Studio 2015, 13,12,10,8 and 5 installed.
So this version requires Visual Studio 2017 as well.

soneca
21st September 2017, 22:11
Resolved with the installation of the x64 version of Visual Studio 2015.
Only the x86 version was installed so far.

byteshare
21st September 2017, 23:29
Was using HQDering, had to switch to HQDering Mod for 64bit support with 1.21 of RipBot
http://avisynth.nl/index.php/HQDering_mod
Incase anyone else needs this info. I find HQDering with MDegrain a really good pairing for denoise.

guest
22nd September 2017, 02:29
Shutdown Servers option basically tells Encoding client to send shutdown command to ALL specified IP's. So It will shutdown your main PC as well if you also have running encodingserver.exe in background.

OK, thanks for the explanation, I'm pretty sure I now know how to "fix" this :)

Also, a HUGE thanks for yet another major Ripbot update, can't wait to give it a test drive.

Cheers

guest
22nd September 2017, 04:33
Well, I can't get Java to be recognised with 1.21.0 on my PC....works OK on this laptop (that I'm using now).
I have installed & re installed many times, both x32 & x64 versions of jre u8 144...... :(

Running Windows Server 2016 on the "problem" PC....also running Server on laptop.

EDIT:- have now tried on 2 other PC's, one with a day old fresh setup of Windows, and none of them will "find" Java, so I can't "test drive" the new version, yet :(

Atak_Snajpera
22nd September 2017, 13:46
Well, I can't get Java to be recognised with 1.21.0 on my PC....works OK on this laptop (that I'm using now).
I have installed & re installed many times, both x32 & x64 versions of jre u8 144...... :(

Running Windows Server 2016 on the "problem" PC....also running Server on laptop.

EDIT:- have now tried on 2 other PC's, one with a day old fresh setup of Windows, and none of them will "find" Java, so I can't "test drive" the new version, yet :(

Check if you have this entry in registry
HKEY_CURRENT_USER\Software\JavaSoft\Java Runtime Environment

guest
22nd September 2017, 15:18
Check if you have this entry in registry
HKEY_CURRENT_USER\Software\JavaSoft\Java Runtime Environment

OK, thanks again for your support...

On the laptop (which Ripbot works), I DO have that entry, but on the 1st PC I tried yesterday, which didn't work, that entry is NOT there !!!

What can I do about it ???

Thanks

EDIT:- OK, here's what I have just done, I exported that registry entry, saved as a .reg file, copied to usb, ran it on the "faulty" PC, and now it works.....

But I would still like your opinion, please.

Is there a specific version of Java you suggest ??? I've notice that v8 has been discontinued, so v9 is now the go, but I haven't been able to find x86 version, so that might be a future problem.

byteshare
22nd September 2017, 16:19
I would say 64bit AVISythn is awesome. I now can have 1 encode going that uses 100% CPU but much less RAM.
If looking for 64bit alternatives to your 32bit ones: http://avisynth.nl/index.php/AviSynth%2B#AviSynth.2B_x64_plugins
If anyone wants an example of HQDering Mod, Deband, and MDegrain3 (default is 2):
LoadPlugin("C:\RipBot264v1.21.0\Tools\AviSynth plugins\flash3kyuu_deband\flash3kyuu_deband.dll")
Loadplugin("C:\RipBot264v1.21.0\Tools\AviSynth plugins\mvtools\mvtools2.dll")
Loadplugin("C:\RipBot264v1.21.0\Tools\AviSynth plugins\Custom\dither.dll")
Loadplugin("C:\RipBot264v1.21.0\Tools\AviSynth plugins\masktools\masktools2.dll")
Loadplugin("C:\RipBot264v1.21.0\Tools\AviSynth plugins\Custom\medianblur2.dll")
Loadplugin("C:\RipBot264v1.21.0\Tools\AviSynth plugins\RgTools\RgTools.dll")
Loadplugin("C:\RipBot264v1.21.0\Tools\AviSynth plugins\Custom\smoothadjust.dll")
Import("C:\RipBot264v1.21.0\Tools\AviSynth plugins\Custom\dither.avsi")
Import("C:\RipBot264v1.21.0\Tools\AviSynth plugins\Custom\HQDeringmod_v1.8.avsi")
super = video.MSuper(pel=2)
bv1 = MAnalyse(super, isb = true, delta = 1, overlap=4)
fv1 = MAnalyse(super, isb = false, delta = 1, overlap=4)
bv2 = MAnalyse(super, isb = true, delta = 2, overlap=4)
fv2 = MAnalyse(super, isb = false, delta = 2, overlap=4)
bv3 = MAnalyse(super, isb = true, delta = 3, overlap=4)
fv3 = MAnalyse(super, isb = false, delta = 3, overlap=4)
video=video.MDegrain3(super,bv1,fv1,bv2,fv2,bv3,fv3,thSAD=400).HQDeringmod(nrmode=2,Y=3,U=3,V=3,lsb=False,thr=255.0,darkthr=255.0).f3kdb
If you need the files I used in my "custom" folder, which automatically gets moved/copied for DE mode, then just steal them from StaxRip like I did :D

soneca
22nd September 2017, 20:48
I would say 64bit AVISythn is awesome. I now can have 1 encode going that uses 100% CPU but much less RAM.

Really! Huge difference in achievement, a bottleneck less! :cool:

stasi
22nd September 2017, 22:14
With the new 1.21.0 I got this error everytime I add a job:

http://forum.doom9.org/attachment.php?attachmentid=16067&stc=1&d=1506114747

I tested a few random MKVs. When I just change the ripbot.exe from 1.20.0 it works fine.

Edit: It seems like it happens only on MKVs with DTS

Atak_Snajpera
23rd September 2017, 11:59
Pro tip: Never use attachments.

soneca
23rd September 2017, 14:40
Atak, no options for sources with DTS-MA, only core extraction.

byteshare
23rd September 2017, 17:15
I can send you a test file but I've only been seeing this issue thus far on x264 10bit as a source but have only tested with x264 8bit and 10bit thus far and not other input codecs.
The issue:
https://imgur.com/a/2tbUF
https://imgur.com/a/2tbUF

LoadPlugin("C:\RipBot264v1.21.0\Tools\AviSynth plugins\hqdn3d\hqdn3d.dll")
LoadPlugin("C:\RipBot264v1.21.0\Tools\AviSynth plugins\flash3kyuu_deband\flash3kyuu_deband.dll")
video=hqdn3d(video,2,0,0,0).f3kdb
I get the issue after removing the f3kdb as well.
I don't get the issue while using MDegrain, which is why I think it has something to do with both HQDN3D and F3KDB.

I don't see this issue with MDegrain, but I do if I use MDegrain and F3KDB

I tried updating to the flash3kyuu_deband.dll 2.0 but that was a whole different set of problems and couldn't get the test video to start.

I'm using both r2506MT 64bit and r2508MT 64bit (separate computers).
Both computers are on RipBot 1.21.0, and both Win7

Atak_Snajpera
23rd September 2017, 18:02
Yes send it.

jandor
23rd September 2017, 18:32
Hi, Atak_Snajpera

When running the AviSynth+ MT (r2508 x86/x64) installer: Tools\AviSynth...... install.cmd
On Windows 10 64 bits ... When I run install.cmd as Administrator, then you get:

C:\Windows\System32 === AviSynth.dll === x64 === 1.882 KB
C:\Windows\SysWOW64 === AviSynth.dll === x86 === 1.492 KB

----
xcopy "AviSynth+" %InstallPath%\ /E /Y
xcopy "Libraries\x64\AviSynth.dll" "%SYSTEMROOT%\System32" /Y
xcopy "Libraries\x86\AviSynth.dll" "%SYSTEMROOT%\SysWOW64" /Y
xcopy "Libraries\x64\DevIL.dll" "%SYSTEMROOT%\System32" /Y
xcopy "Libraries\x86\DevIL.dll" "%SYSTEMROOT%\SysWOW64" /Y

Is this right?
DLL x64 would not go to SysWOW64 and DLL x86 for System32?


Thanks!

Atak_Snajpera
23rd September 2017, 18:39
DLL x64 would not go to SysWOW64 and DLL x86 for System32?
Nope.

jandor
23rd September 2017, 18:54
Nope.

So the correct is just as you schematized?


Many Thanks!

byteshare
23rd September 2017, 20:53
Yes send it.
Okay, I PM'd you with a link.

activoice
24th September 2017, 09:54
Not sure if this has been asked for before and declined...

Can an option be added in the settings to Retain all Subtitle tracks, so that they will all be extracted and automatically muxed when the output is created.

guest
24th September 2017, 12:36
Not sure if this has been asked for before and declined...

Can an option be added in the settings to Retain all Subtitle tracks, so that they will all be extracted and automatically muxed when the output is created.

@ activoice

1st post here...

As far as I know, ALL subtitles are saved into the relevant job folder, but you have to manually add them, if you want them muxed in..there are a couple of different options to do this.

soneca
24th September 2017, 14:57
Atak, I still have no options on audio tracks with DTS-HD MA sources.

https://s20.postimg.org/fegtv3zv1/ripbot.jpg

byteshare
24th September 2017, 16:39
There is an option to Remux Subs in Batch mode. The only problem with this is that if those subs had names (MKV Titles) in the previous file that information is lost.
I manually remux subs after an encode with a batch file for the reason above.

stasi
24th September 2017, 20:22
Pro tip: Never use attachments.

Here is the result of the test.log btw. Ripbot just made an update, thought it was fixed.

ffprobe version N-87294-gec1573f Copyright (c) 2007-2017 the FFmpeg developers
built with gcc 7.1.0 (GCC)
configuration: --enable-gpl --enable-version3 --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-zlib
libavutil 55. 75.100 / 55. 75.100
libavcodec 57.106.101 / 57.106.101
libavformat 57. 82.100 / 57. 82.100
libavdevice 57. 8.101 / 57. 8.101
libavfilter 6.105.100 / 6.105.100
libswscale 4. 7.103 / 4. 7.103
libswresample 2. 8.100 / 2. 8.100
libpostproc 54. 6.100 / 54. 6.100
[avisynth @ 0000000000d63660] FFAudioSource: Audio format change detected. This is currently unsupported. Channels: 6 -> 6; Sample rate: 48000 -> 48000; Sample format: Unknown -> Unknown
(E:\$Temp\RipBot264temp\job1\getinfo.avs, line 4)
E:\$Temp\RipBot264temp\job1\getinfo.avs: Unknown error occurred

Any other format works, except DTS HD MA.

Atak_Snajpera
24th September 2017, 20:28
Can you send me some sample to see what is so special about this particular DTS-MA audio. I have many test samples with DTS-MA and FFAudioSource decodes those streams without any problem.

soneca
24th September 2017, 20:51
I tested it with five blu-ray(DTS-MA) and it does not recognize any.
With version 1.19.5 I have no problems.

stasi
24th September 2017, 20:55
Mhm. Original file aborts with that error. A chunk created with DGSplit works fine.

Atak_Snajpera
24th September 2017, 21:01
Mhm. Original file aborts with that error. A chunk created with DGSplit works fine.

What is an original file? .m2ts or .mkv?