Log in

View Full Version : BD Rebuilder Beta - Bug Reports Only


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 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 [480] 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648

mparade
4th April 2016, 18:09
Hello,

Does BD-RB automatically use MULTIPROCESS=0 when AVS editor is being used (no any rescaling is used in either the script, or in the setup dialogue, only MVDegrain3 and LimitedSharpenFaster as the last filter in the chain)? I did not find anything regarding this in the description of "BD Rebuilder Multi-process Encoding". The filter-chain used seems not to be working in MT mode so my only chance to speed up the process is to divide the encoding task into smaller chunks and then running multiple instances of X264 concurrently".

Any help would be appreciated.

jdobbs
4th April 2016, 18:55
Hello,

Does BD-RB automatically use MULTIPROCESS=0 when AVS editor is being used (no any rescaling is used in either the script, or in the setup dialogue, only MVDegrain3 and LimitedSharpenFaster as the last filter in the chain)? I did not find anything regarding this in the description of "BD Rebuilder Multi-process Encoding". The filter-chain used seems not to be working in MT mode so my only chance to speed up the process is to divide the encoding task into smaller chunks and then running multiple instances of X264 concurrently".

Any help would be appreciated.No, it will still break it up assuming nothing else stops it.

jdobbs
4th April 2016, 18:58
I had tried bumping the output size a gigabyte, but it almost seems like once videos start getting encoded they all get encoded.

Would Rebuilder actually distinguish that it doesn't need to touch the movie once the extras have been encoded?The determination to re-encode is made for each segment based on the calculated space required v.s. the output space allocated.

Lathe
4th April 2016, 19:21
@Lathe

Download the following and see if it plays on your Oppo: http://vidiot.com/StarWars-DeletedScene.mkv

If it does, use MediaInfo to see what encoder settings that I used. I have a script that I use to do H.264 encodings (x264, cygwin and Z-shell).

Thanks kindly, I'll give it a go!

Lathe
4th April 2016, 19:42
@Lathe

Download the following and see if it plays on your Oppo: http://vidiot.com/StarWars-DeletedScene.mkv

If it does, use MediaInfo to see what encoder settings that I used. I have a script that I use to do H.264 encodings (x264, cygwin and Z-shell).

It did PRECISELY the same thing that always happens. As an MKV file, it looked exactly like the other ones. However, when I used TSMuxer and placed the file in a BDMV folder, it played perfectly.

Weird, huh...?

I appreciate any suggestions. But, this is has been a very long standing weirdness with my player. It could just be some odd idiosyncracy with my player when rendering MKV files that have been encoded for BDMV. I don't know... I looked at the x264 settings in the file, and again, other than the bluray_compat=1 setting and whatever other BDMV settings there (buffer, etc...???) it doesn't look like anything else is out of place.

Please don't bother yourselves too much with this, since even OPPO didn't have an answer for me. And, quite honestly, this ONLY happens in this case. I should try re-encoding files like this and just simply remove whatever Blu-ray compatible settings are there. That might work, I don't know...

But, this only happens in these rare cases or when I use BDMV for alternate output, which now I almost never do. The workaround, which really isn't that bad, is just to place the file in a BDMV folder and play it that way, that's all.

Thanks though!

I KNOW... it has been quite a mystery! :)

Here is the encoding settings for that file FWIW:

cabac=1 / ref=4 / deblock=1:1:-1 / analyse=0x3:0x113 / me=umh / subme=10 / psy=1 / psy_rd=1.00:0.15 / mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-3 / threads=12 / lookahead_threads=1 / sliced_threads=0 / slices=4 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=1 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=1 / weightp=0 / keyint=24 / keyint_min=1 / scenecut=40 / intra_refresh=0 / rc_lookahead=60 / rc=2pass / mbtree=1 / bitrate=4000[?] / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=5000 / vbv_bufsize=14745 / [?]nal_hrd=vbr [?]/ filler=0 / ip_ratio=1.40 / aq=1:1.00

mparade
4th April 2016, 21:18
No, it will still break it up assuming nothing else stops it.

BD-RB ignored MULTIPROCESS>0 in my Quick-play menu encode including 159 very short cartoon episodes. I would suspect that the reason is the very short length of the episodes (~9-10.000 frames/episode). Anyway, all the episodes are 576i 25fps (progressive content, DGDecNV used for frameserving, --fake interlaced command is used in the command line to be BD compliant). Without using multiprocess my processor utilization is at 40% averagely. :scared:

gonca
4th April 2016, 23:08
@Lathe
Your oppo might be FAT32 limited for files
What size are the MKVs that work and those that don't

PS
It seems that the oppo prefers extension .mkv and might not like .MKV

DoctorM
5th April 2016, 00:17
The determination to re-encode is made for each segment based on the calculated space required v.s. the output space allocated.

Unfortunately, that is not what I'm seeing happen. I've bumped the BD25 target all the way up to 36gb and BDRB still starts to re-encode the film and the extras, even though 24gb would be enough to keep everything untouched.

With a target above the total size of the disc (45gb) nothing gets re-encoded.

I'm sure I'm doing something wrong or someone would have seen this before.

Honestly, it seems like if you use Edit Mode/Manual Blanking, the items selected for blanking aren't being deducted from the calculations:

LABEL=HOLIDAY_INN
VERSION=v0.50.11
SOURCE_SIZE=48822190130
SOURCE_VIDEO_SIZE=48655048704
TARGET_SIZE=38341181440
REDUCTION=.784585382829175

(Source size or video size should be more like 24gb, not 48gb).

Thanks for the suggestions.
I'll just let it re-encode everything and then swap out the .m2ts and small files for the movie. :confused:

MrVideo
5th April 2016, 00:51
It did PRECISELY the same thing that always happens. As an MKV file, it looked exactly like the other ones. However, when I used TSMuxer and placed the file in a BDMV folder, it played perfectly.

Weird, huh...?
Weird, yes indeed.
I appreciate any suggestions. But, this is has been a very long standing weirdness with my player. It could just be some odd idiosyncracy with my player when rendering MKV files that have been encoded for BDMV. I don't know... I looked at the x264 settings in the file, and again, other than the bluray_compat=1 setting and whatever other BDMV settings there (buffer, etc...???) it doesn't look like anything else is out of place.
I suppose I could try it without the bluray_compat=1 setting. But, something tells me that not even that will make a difference.
Please don't bother yourselves too much with this, since even OPPO didn't have an answer for me. And, quite honestly, this ONLY happens in this case. I should try re-encoding files like this and just simply remove whatever Blu-ray compatible settings are there. That might work, I don't know...
It has been quite a while since I set up the script. I'd have to go digging thru the net again to see what setting were important for Blu-ray and what ones were needed for H.264 to play correctly, no matter the playback device. Other than your Oppo. :D
But, this only happens in these rare cases or when I use BDMV for alternate output, which now I almost never do. The workaround, which really isn't that bad, is just to place the file in a BDMV folder and play it that way, that's all.
That just seems to be a strange thing to do.
Here is the encoding settings for that file FWIW:

cabac=1 / ref=4 / deblock=1:1:-1 / analyse=0x3:0x113 / me=umh / subme=10 / psy=1 / psy_rd=1.00:0.15 / mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-3 / threads=12 / lookahead_threads=1 / sliced_threads=0 / slices=4 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=1 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=1 / weightp=0 / keyint=24 / keyint_min=1 / scenecut=40 / intra_refresh=0 / rc_lookahead=60 / rc=2pass / mbtree=1 / bitrate=4000[?] / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=5000 / vbv_bufsize=14745 / [?]nal_hrd=vbr [?]/ filler=0 / ip_ratio=1.40 / aq=1:1.00

What is strange with a 4 Mbps bitrate? For playback of stuff that I just watch, that bitrate is perfect. The x264 encoder, when used in 2-pass, is hard to beat. Try to find macroblocks at that bitrate is extremely difficult. Other stuff that I do is done at higher bit rates, especially if I plan on authoring a Blu-ray.

SquallMX
5th April 2016, 01:11
What is strange with a 4 Mbps bitrate? For playback of stuff that I just watch, that bitrate is perfect. The x264 encoder, when used in 2-pass, is hard to beat. Try to find macroblocks at that bitrate is extremely difficult. Other stuff that I do is done at higher bit rates, especially if I plan on authoring a Blu-ray.

Per Bluray specs vbv_maxrate need to be higher than vbv_bufsize, additionally a maxrate of only 5000 kbps will severely impact the quality of complex scenes, something like vbv_maxrate=15000 / vbv_bufsize=14745 is probably better.

Lathe
5th April 2016, 01:43
@Lathe
Your oppo might be FAT32 limited for files
What size are the MKVs that work and those that don't

PS
It seems that the oppo prefers extension .mkv and might not like .MKV

Yes, that is true when using the USB for playing. But whenever I want to watch a Blu-ray or something that large file-wise on the USB, I just make sure that the m2ts files are under 4 Gigs within the BDMV folder.

Heh, interesting catch with the capitalizing; hadn't noticed that. I don't THINK that is it because the only time I've noticed this behaviour is specifically when an MKV file is encoded for Blu-ray compatibility (or if some mysterious parameters are off and it just simply chokes my player, but that happens very rarely)

Lathe
5th April 2016, 01:48
Unfortunately, that is not what I'm seeing happen. I've bumped the BD25 target all the way up to 36gb and BDRB still starts to re-encode the film and the extras, even though 24gb would be enough to keep everything untouched.

With a target above the total size of the disc (45gb) nothing gets re-encoded.

I'm sure I'm doing something wrong or someone would have seen this before.

Honestly, it seems like if you use Edit Mode/Manual Blanking, the items selected for blanking aren't being deducted from the calculations:



(Source size or video size should be more like 24gb, not 48gb).

Thanks for the suggestions.
I'll just let it re-encode everything and then swap out the .m2ts and small files for the movie. :confused:

Well, if you are going to go to that trouble to allow it to re-encode, then what I would suggest, and sometimes I do this myself, is simply allow BDRB to create an m2ts file for the MOVIE ONLY and set it aside. Then go back and browse to the same Blu-ray and blank the main movie and ONLY encode the xtras. See how much space you need for the xtras to fit along with the movie in a BDMV folder, and set custom output for slightly smaller than that.

That way, you at least ONLY have to wait until the xtras re-encode, which you could choose 'Very Fast' 1 pass ABR if you want and it wouldn't take long. The take the resulting m2ts files for the xtras and the movie only m2ts and use TSMuxer to mux them together into one Blu-ray folder (BDMV) and you should be set.

This way at least, you don't have to wait to re-encode the actual whole movie (which you don't want anyway)

I hope that helps!

Lathe
5th April 2016, 02:07
Weird, yes indeed.

I suppose I could try it without the bluray_compat=1 setting. But, something tells me that not even that will make a difference.

It has been quite a while since I set up the script. I'd have to go digging thru the net again to see what setting were important for Blu-ray and what ones were needed for H.264 to play correctly, no matter the playback device. Other than your Oppo. :D

That just seems to be a strange thing to do.


What is strange with a 4 Mbps bitrate? For playback of stuff that I just watch, that bitrate is perfect. The x264 encoder, when used in 2-pass, is hard to beat. Try to find macroblocks at that bitrate is extremely difficult. Other stuff that I do is done at higher bit rates, especially if I plan on authoring a Blu-ray.

Appreciate the comments! Believe me, I have read EXTENSIVELY about what x264 parameters are needed just for Blu-ray compatibility. A pretty basic CMD line is SUPPOSEDLY all you need. For example, her are some I've tried for just a simple re-encode:

x264-64.exe "C:\x\test.mkv" --profile high --level 4.1 --vbv-maxrate 62500 --vbv-bufsize 78125 --preset veryfast --crf 24 --tune film --output "C:\x\Encode.mkv"

or this one was recommended by Selur, the designer of HYBRID:

--profile high --level 4.1 --vbv-maxrate 62500 --vbv-bufsize 78125

It doesn't get much simpler than that. But, no go... The damn things won't play AT ALL. They always choke my player. So, I am COMPLETELY mystified by what the heck is doing it, especially when I am trying such bloody SIMPLE CMD line codes! One thing that I WAS able to determine is that the presets like 'Slow' or maybe it was 'Very Slow' have parameters that my player won't play (like to high ref frames or B frames, for example) But, GEEZ, you think using 'Very Fast' should work, but NO!

That is why I frigg'n LOVE BDRB, because, overall whatever IT does, even though I can only play the BDMV folder stuff, at least it still always re-encodes and bloody WORKS!

I just don't know frigg'n WHY...! :cool:

Anyway, I found some research and comparisons from some movie snippets and encodes that I had tried before and the results (Sorry JD for taking up so much bloody room 'talking' about my stuff, but this should be it :o )


(THOMAS CROWN AFFAIR - BDRB) * DOESN'T PLAY *

cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=6 / lookahead_threads=1 / sliced_threads=0 / slices=4 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=1 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=1 / keyint=24 / keyint_min=1 / scenecut=40 / intra_refresh=0 / rc_lookahead=24 / rc=crf / mbtree=1 / crf=16.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=35000 / vbv_bufsize=30000 / crf_max=0.0 / nal_hrd=vbr / filler=0 / ip_ratio=1.10 / aq=1:1.00


(PELICAN BRIEF - BDRB) * PIXELIZES *

cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=6 / lookahead_threads=1 / sliced_threads=0 / slices=4 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=1 / constrained_intra=0 / bframes=3 / b_pyramid=0 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=1 / keyint=24 / keyint_min=1 / scenecut=40 / intra_refresh=0 / rc_lookahead=24 / rc=crf / mbtree=1 / crf=16.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=35000 / vbv_bufsize=30000 / crf_max=0.0 / nal_hrd=vbr / filler=0 / ip_ratio=1.10 / aq=1:1.00


(PELICAN BRIEF -REDO BDRB) * PIXELIZES *

cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=6 / lookahead_threads=1 / sliced_threads=0 / slices=4 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=1 / constrained_intra=0 / bframes=3 / b_pyramid=0 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=1 / keyint=24 / keyint_min=1 / scenecut=40 / intra_refresh=0 / rc_lookahead=24 / rc=crf / mbtree=1 / crf=16.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=35000 / vbv_bufsize=30000 / crf_max=0.0 / nal_hrd=vbr / filler=0 / ip_ratio=1.10 / aq=1:1.00


(SHAME THE DEVIL) L4.1 *** THIS DOES PLAY ***

cabac=1 / ref=5 / deblock=1:-1:-1 / analyse=0x3:0x133 / me=umh / subme=7 / psy=1 / psy_rd=1.00:0.15 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-3 / threads=12 / lookahead_threads=2 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=240 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=crf / mbtree=1 / crf=20.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00

MrVideo
5th April 2016, 02:16
Per Bluray specs vbv_maxrate need to be higher than vbv_bufsize, additionally a maxrate of only 5000 kbps will severely impact the quality of complex scenes, something like vbv_maxrate=15000 / vbv_bufsize=14745 is probably better.

I've 2-pass encoded many a file, with complex scenes, and you will be hard pressed to find macroblocking/pixelization issues.

MrVideo
5th April 2016, 02:19
Appreciate the comments! Believe me, I have read EXTENSIVELY about what x264 parameters are needed just for Blu-ray compatibility. A pretty basic CMD line is SUPPOSEDLY all you need.
I didn't know that you have really dug into this problem. I hate to say this, but your only fix may be to get a newer OPPO player.

Lathe
5th April 2016, 02:27
I didn't know that you have really dug into this problem. I hate to say this, but your only fix may be to get a newer OPPO player.

Heh, that's funny :) Nah, everything else is fine, and like I say, this ONLY really happens once in a while with random MKV files (it hasn't happened in a while) And just the re-encode thing, and I can work around that. Otherwise it honestly is a kick@ss player :D

As to what you said about about your encodes. I didn't mean that there was anything wrong with yours. I just meant that whatever was in these encodes that I happened to try just caused my OPPO to pixelize, and I don't mean just some macroblocking because of low bitrate, I'm talking about kind of like the picture I posted. Obviously not being played back properly at all.

Thanks Bro!

MrVideo
5th April 2016, 03:28
As to what you said about about your encodes. I didn't mean that there was anything wrong with yours. I just meant that whatever was in these encodes that I happened to try just caused my OPPO to pixelize, and I don't mean just some macroblocking because of low bitrate, I'm talking about kind of like the picture I posted. Obviously not being played back properly at all.

I didn't take your posting as being negative in any way, shape, or form. I understand that the pixelization issues you are having are a result of the player. I was just curious as to why you flagged the 4 Mbps bitrate.

Seriously, a new OPPO might be in order. It will be even more kick-ass. :D

Lathe
5th April 2016, 03:42
I didn't take your posting as being negative in any way, shape, or form. I understand that the pixelization issues you are having are a result of the player. I was just curious as to why you flagged the 4 Mbps bitrate.

Seriously, a new OPPO might be in order. It will be even more kick-ass. :D

Oh yeah, I see what you mean now... Well, one thing I really DON'T understand is the parameter within the encode that actually specifies a particular bit rate. I didn't mean that anything is wrong with it, but in my ignorance, I just selected it as one of the parameters that I don't understand and I don't know how it directly affects the playback since I DON'T always see a bit rate specified in MKV encodes. Or, at least if it is there, I have missed it...

For example, in the above configuration for the film 'SHAME THE DEVIL' (that actually DID play properly) you notice that there is no bit rate specified in the encode. So, I was pointing out that in the 3 other encodes that either didn't play or played pixelated, VBV max & buffer rates ARE specified (as for Blu-rays) So, I was selecting that parameter as a POSSIBLE snag in affecting my playback. Not the bit rate specifically, but perhaps just the fact that any is included or specified in the encode itself. I really don't know...

DoctorM
5th April 2016, 04:18
Well, if you are going to go to that trouble to allow it to re-encode, then what I would suggest, and sometimes I do this myself, is simply allow BDRB to create an m2ts file for the MOVIE ONLY and set it aside. Then go back and browse to the same Blu-ray and blank the main movie and ONLY encode the xtras. See how much space you need for the xtras to fit along with the movie in a BDMV folder, and set custom output for slightly smaller than that.

That way, you at least ONLY have to wait until the xtras re-encode, which you could choose 'Very Fast' 1 pass ABR if you want and it wouldn't take long. The take the resulting m2ts files for the xtras and the movie only m2ts and use TSMuxer to mux them together into one Blu-ray folder (BDMV) and you should be set.

This way at least, you don't have to wait to re-encode the actual whole movie (which you don't want anyway)

I hope that helps!
I've done similar, and probably what I'll do this time. (http://forum.doom9.org/showthread.php?p=1678011#post1678011)

In this case, it probably doesn't matter since the extras are all 480i, but in general there is the problem that if you do it that way, the max bitrate is restricted to AVCHD spec and the audio can only be up to DD 640kbps.

Again, in this case, it won't matter.

Lathe
5th April 2016, 04:42
I've done similar, and probably what I'll do this time. (http://forum.doom9.org/showthread.php?p=1678011#post1678011)

In this case, it probably doesn't matter since the extras are all 480i, but in general there is the problem that if you do it that way, the max bitrate is restricted to AVCHD spec and the audio can only be up to DD 640kbps.

Again, in this case, it won't matter.

But, if he is doing a full 25 Gig Blu-ray backup, he shouldn't have to worry about that, right...?

MrVideo
5th April 2016, 06:39
Well, one thing I really DON'T understand is the parameter within the encode that actually specifies a particular bit rate. I didn't mean that anything is wrong with it, but in my ignorance, I just selected it as one of the parameters that I don't understand and I don't know how it directly affects the playback since I DON'T always see a bit rate specified in MKV encodes.

It seems that most people prefer to use the crf parameter. I'm the oddball that likes choosing the bitrate. :D

MrVideo
5th April 2016, 06:44
For example, in the above configuration for the film 'SHAME THE DEVIL' (that actually DID play properly) you notice that there is no bit rate specified in the encode. So, I was pointing out that in the 3 other encodes that either didn't play or played pixelated, VBV max & buffer rates ARE specified (as for Blu-rays) So, I was selecting that parameter as a POSSIBLE snag in affecting my playback. Not the bit rate specifically, but perhaps just the fact that any is included or specified in the encode itself. I really don't know...

Looking at your examples again, I did notice that bluray_compat=1 for all the ones that didn't work and bluray_compat=0 for the one that did work.

If you are curious, I can try encoding the same video again, but with bluray_compat=0.

Lathe
5th April 2016, 06:53
Looking at your examples again, I did notice that bluray_compat=1 for all the ones that didn't work and bluray_compat=0 for the one that did work.

If you are curious, I can try encoding the same video again, but with bluray_compat=0.

Yeah, that is what I'm thinkin...

Sharc
5th April 2016, 07:31
Here is the encoding settings for that file FWIW:

cabac=1 / ref=4 / deblock=1:1:-1 / analyse=0x3:0x113 / me=umh / subme=10 / psy=1 / psy_rd=1.00:0.15 / mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-3 / threads=12 / lookahead_threads=1 / sliced_threads=0 / slices=4 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=1 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=1 / weightp=0 / keyint=24 / keyint_min=1 / scenecut=40 / intra_refresh=0 / rc_lookahead=60 / rc=2pass / mbtree=1 / bitrate=4000[?] / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=5000 / vbv_bufsize=14745 / [?]nal_hrd=vbr [?]/ filler=0 / ip_ratio=1.40 / aq=1:1.00
vbv_bufsize should always be less or equal to vbv_maxrate (for max. 1 second buffer delay for Blu-ray compliance).

Sharc
5th April 2016, 07:39
[QUOTE=Lathe;1763361
(THOMAS CROWN AFFAIR - BDRB) * DOESN'T PLAY *
....... / bluray_compat=1 / ....... / crf=16.0 / ........./ vbv_maxrate=35000 / vbv_bufsize=30000 / ............

(PELICAN BRIEF - BDRB) * PIXELIZES *
......./ bluray_compat=1 / ...... / crf=16.0 / ......../ vbv_maxrate=35000 / vbv_bufsize=30000 / ..........

(PELICAN BRIEF -REDO BDRB) * PIXELIZES *
.........../ bluray_compat=1 / ......... / crf=16.0 / ....... / vbv_maxrate=35000 / vbv_bufsize=30000 / .............

(SHAME THE DEVIL) L4.1 *** THIS DOES PLAY ***
......... / bluray_compat=0 /...... / crf=20.0 / ..........[/QUOTE]


You might have a buffer problem with the OPPO for your crf=16 + buffer settings combination.
You could try to increase the crf (crf=20 for lowering the bitrate), or play with the buffers, or simply drop the buffer specification for .mkv output. You may also drop --bluray-compat.

MrVideo
5th April 2016, 10:57
vbv_bufsize should always be less or equal to vbv_maxrate (for max. 1 second buffer delay for Blu-ray compliance).

I'll have to fix that in my script. Thanks.

emilio99
5th April 2016, 19:05
I have still a error which I reported a long time ago:
setting the default language to another language than english (in my case to german) doesn't work. In the mkv english is still the DEFAULT language.

I provided relevant logs and also added some step by step photos. I'm using alternative output with:
MKV 1920x1080, Intact Audio

BD-REBUILDER.LOG
[04.04.16] BD Rebuilder v0.50.14
[21:19:01] Source: TRANSFORMERS_2_D1_EU_00003
- Input BD size: 44,44 GB
- Approximate total content: [02:29:53.025]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1920x1080, Intact Audio
- Quality: High Quality (Default)
- Automatic cropping of borders enabled
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=1 HD=1 Kbs=448
- Audio [5] set to default.
[21:19:05] PHASE ONE, Encoding
- [21:19:05] Processing: VID_00003 (1 of 1)
- [21:19:05] Extracting A/V streams [VID_00003]
- [23:26:24] Reencoding video [VID_00003]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 215.617 frames
- [23:26:25] Reencoding: VID_00003, Pass 1 of 1
- [02:19:04] Video Encode complete
- [02:19:04] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4356 (deu): Keeping original audio
[02:19:04]PHASE ONE complete
[02:19:04]PHASE TWO - Rebuild Started
- [02:19:04] Building ALTERNATE OUTPUT Structure
[02:57:04] - Encode and Rebuild complete
[02:57:04] JOB: TRANSFORMERS_2_D1_EU finished.


TRANSFORMERS_2_D1_EU.INF
[Status]
LABEL=TRANSFORMERS_2_D1_EU
VERSION=v0.50.14
SOURCE_SIZE=47718555648
SOURCE_VIDEO_SIZE=47718555648
TARGET_SIZE=4686086144
REDUCTION=9.82025981374481E-02
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;ger;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=deu;eng;
BACKUP_MODE=1
MOVIEONLY_TYPE=11
USE_LAVF=0
INSTANCES=1
DGDECNV=-1
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=1
[00003]
AUDIO=1000100
PGS=01100000001110001000
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=4686086144
SPLITS=1
NSIZE=0
FLINK=0
MLINK=0

jdobbs
5th April 2016, 19:52
@emilio99

Currently the default audio selection from the streams list only applies to a movie-only BD backup. But I will add code to make it apply to MKV and MP4 for the next release.

emilio99
5th April 2016, 20:49
@emilio99

Currently the default audio selection from the streams list only applies to a movie-only BD backup. But I will add code to make it apply to MKV and MP4 for the next release.

Thanks, that would be awesome :D

laserfan
5th April 2016, 22:15
Believe me, I have read EXTENSIVELY about what x264 parameters are needed just for Blu-ray compatibility. A pretty basic CMD line is SUPPOSEDLY all you need. For example, her are some I've tried for just a simple re-encode:

x264-64.exe "C:\x\test.mkv" --profile high --level 4.1 --vbv-maxrate 62500 --vbv-bufsize 78125 --preset veryfast --crf 24 --tune film --output "C:\x\Encode.mkv"

or this one was recommended by Selur, the designer of HYBRID:

--profile high --level 4.1 --vbv-maxrate 62500 --vbv-bufsize 78125

Late to this party, and I don't know nuttin' bout playing mkv on an Oppo player, but you mention Blu-ray compatibility and then set yours off-the-charts-high? Those need to be 40000 and 30000 respectively, with bitrate no higher than 15000.

AmigaFuture
5th April 2016, 23:20
Hello,

There's something broken with MULTIPROCESS=X and 2-pass. As well as IVTC with 59.940fps files(?), this one happens to be H.264. When I set MULTIPROCESS=0 then the job completes but with jerky video. It's from a TiVo file I processed with VideoReDo TVSuite. With 2-pass, it fails as soon as 2nd is started.


[12:27:33] Importing M2TS: TEST
- Preparing M2TS for processing...
- Collecting audio/video streams from source...
- Building pseudo-BD source structure...
[12:28:54] Video import completed successfully.
----------------------
[04/05/16] BD Rebuilder v0.50.12
[12:30:00] Source: TEST
- Input BD size: 1.29 GB
- Approximate total content: [01:00:59.021]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- Quality: Good (Very Fast), Two Pass
- Decoding/Frame serving: DGDecNV [4-way]
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[12:30:01] PHASE ONE, Encoding
- [12:30:01] Processing: VID_00000 (1 of 1)
- [12:30:01] Extracting A/V streams [VID_00000]
- [12:30:20] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1280x720
- Rate/Length: 59.940fps, 219,322 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 35,000 Kbs
- [12:30:20] Reencoding: VID_00000, Pass 1 of 2
- [12:52:15] Reencoding: VID_00000, Pass 2 of 2
- Encode failed. Aborting.
- BD-Rebuilder v0.50.12
- Windows Version: 6.1 [7601]
- Working Path Free Space: 80.53GB
- AVISYNTH Version: 2.5.8.0, Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[12:52:16] - Failed video encode, aborted

Sharc
5th April 2016, 23:41
........Believe me, I have read EXTENSIVELY about what x264 parameters are needed just for Blu-ray compatibility.......

Seeing your partially odd buffer settings, I have my doubts..... :rolleyes:
Did you get these from BD-RB??

DoctorM
5th April 2016, 23:45
But, if he is doing a full 25 Gig Blu-ray backup, he shouldn't have to worry about that, right...?

No. We are talking about removing the movie and re-encoding only the extras and adding the untouched movie back later.

I'm not sure where the cut-off is but somewhere under 25gb (possible 9gb), BD-RB assumes a disc that size is AVCHD and will use AVCHD specs instead of BD.

Edit: Okay so I pre-stripped what I wanted removed using BD-RB and reloaded the stripped version and set the movie to be blanked.
And now this:
LABEL=HOLIDAY_INN_STRIPPED
VERSION=v0.50.11
SOURCE_SIZE=2784044796
SOURCE_VIDEO_SIZE=2763804672
TARGET_SIZE=2086666240
REDUCTION=.747674442023666
So reduction is 0.75
VID_00300 is originally 5139Kbps according to MediaInfo.
This is happening with Rebuilder...
http://114.imagebam.com/download/FZKehMiESPU9DmgfIweGPw/47614/476138466/BDRB.jpg

Any suggestions?

Edit 2: Ah, never mind. I'll just duplicate the first strip and remove the movie with the same target size. Should do the job.
Weird though.

Lathe
5th April 2016, 23:53
You might have a buffer problem with the OPPO for your crf=16 + buffer settings combination.
You could try to increase the crf (crf=20 for lowering the bitrate), or play with the buffers, or simply drop the buffer specification for .mkv output. You may also drop --bluray-compat.

Hmmm, yes, this seems to be moving towards what the deal is with my OPPO player. The way the picture looks (when it plays) in this situation, is almost like the OPPO is trying to 'catch up' with the picture. It renders it okay for a couple of seconds and then the screen looks like the picture I attached earlier here. ALMOST the same thing happens when the ref frames are too high; the picture will look okay for a couple of seconds and then pixelate, although in that specific case it doesn't form the same pattern as the picture I posted here, but is more random pixelation.

This is what I was wondering, as you say, because it is almost ALWAYS in encodes where the buffer rates and sizes ARE specified is where it seems that this happens. It still leaves unexplained as to why when I use the most basic CMD line codes to re-encode an MKV file, it never bloody plays...

But hey, one step at a time :)

Thanks for your input. I think this is likely getting close to what my OPPO is doing with some of these files.

Lathe
6th April 2016, 00:01
from Laserfan:

Late to this party, and I don't know nuttin' bout playing mkv on an Oppo player, but you mention Blu-ray compatibility and then set yours off-the-charts-high? Those need to be 40000 and 30000 respectively, with bitrate no higher than 15000.


Seeing your partially odd buffer settings, I have my doubts..... :rolleyes:
Did you get these from BD-RB??

Yes, I believe both of you are right. I was just parroting what some 'Official' page said about Blu-ray compatibility settings. I don't claim to UNDERSTAND them fully... :)

I'm still thinking though that you are right about the rate and buffer settings; I have a feeling that for MKV files those should just be jettisoned as far as my player is concerned. Like I mentioned, with about 95%+ of the MKV files that I 'come across', most do NOT have any of these settings and play just fine.

Thanks guys!

worknstiff
6th April 2016, 01:38
@ DoctorM RE: No. We are talking about removing the movie and re-encoding only the extras and adding the untouched movie back later.
Wow, on the few times that I came across some extra I couldn't live without like some Mad Men or Game of Thrones extras, I did it the hard way. I encoded the movie down to a 15gb size and then put all the extras back into a 50gb BDRB rebuild. Then I re-encoded that back down to a BD25 Rebuild. I had some extras that started out maybe 3gb and were now less than 600mb and the main episodes were almost un-touched. It never occurred to me to just strip them out first and then get them down, lol.

DoctorM
6th April 2016, 02:24
The more I experiment, the more it looks like using manual blanking on any streams results in a wrong reduction percentage calculation.
I can't seem to get around that.

Has anyone else found this? Take any disc, select to remove something big and the reduction calculated is based on the pre-blanking size instead of the post-blanking size?

Right now I'm using the original BD, stripping both copies of the movie and re-encoding just the extras to 1990gb. Should be fine, except:
SOURCE_SIZE=48822190130
SOURCE_VIDEO_SIZE=48791666688
TARGET_SIZE=2086666240
REDUCTION=.042141269966203

I could work around that since I'm using 'faster encoding' for the extras, but there is one menu video that's getting 2-pass and compressed to 4%.

mparade
6th April 2016, 21:55
Hello,

Is SBS or O/U 3D output possible in Full backup mode of BD3D sources?

Thanks.

AmigaFuture
6th April 2016, 22:16
Update: 59.940fps MPEG-2 files are IVTC'd correctly. I checked an older MPEG-2 to be sure that is still ok. It's only MPEG-4 59.940fps that's failing.

jdobbs
6th April 2016, 23:36
Hello,

Is SBS or O/U 3D output possible in Full backup mode of BD3D sources?

Thanks.It's been a while since I worked on that -- but as I recall, yes to half-SBS. Just select it from the SETUP dialog.

MrVideo
7th April 2016, 04:12
Update: 59.940fps MPEG-2 files are IVTC'd correctly. I checked an older MPEG-2 to be sure that is still ok. It's only MPEG-4 59.940fps that's failing.

FYI: 59.94 fps video doesn't exist. 29.97 fps video does. FPS = frames per second, not fields per second.

DoctorM
7th April 2016, 04:20
For 720p (and 4k) it does... but then you wouldn't need to IVTC it.

mparade
7th April 2016, 08:30
It's been a while since I worked on that -- but as I recall, yes to half-SBS. Just select it from the SETUP dialog.

It would be great! I will test it today. Anyway, half O/U would be better for me because I have a not so big passive 3D TV (will change the TYPE_OF_3D hiddenopt and see the results).

Thanks!

varekai
7th April 2016, 10:03
...off topic... :o

MrVideo
7th April 2016, 11:41
For 720p (and 4k) it does... but then you wouldn't need to IVTC it.

True. But I think HD in terms of 1080. I've never really considered 720 as true HD, just a poor man's high res. :D

But it isn't true that 720p doesn't need IVTC. For example, dramas on the ABC and Fox networks are produced at 23.976p and 2:3 pulldown converted for 720p. In order to get back to the original 23.976p frame rate, IVTC is required.

But, as I said, I prefer 1080 over 720.

raul124
7th April 2016, 12:55
:confused:Hello good people, 1 request what's a good tool to pick the correct play list from the BVM mackingjay2. i back it up and it's out of sequence..and where do i get this tool from or the link? thank's..

Sharc
7th April 2016, 14:13
I would like to experiment with encoding scripts like this.
Never done it before so if anyone could explain how to add/implement it into BDRB I would be grateful.
Using Blu-ray discs as input.
Would like to make smaller mkv's with audio ac3 640 2 channel, video bitrate around 10 mbps.

Thanks...
Settings like those in that script are not produced by BD-RB normal usage. That's probably the reason why it caused problems for the OP of that script.

However, if you want to experiment with settings at your own risk, you can do so by customizing the x264 command line via the TWEAK_..... option in the .ini, see HIDDENOPTS.TXT and search for the explanations in Changes.txt. But don't complain if your tweaks produce problems and non-playable files!

For .mkv output you have to select in the BD-RB Mode-menu "Alternate Movie-Only Output" and then select one of the proposed .mkv formats. (You could also add some customization in the file "alternate.txt" which is in the MISC folder. See the comments at the beginning of that file.)

If you want full flexibility with any (wild) settings you may better switch to another GUI, or do everything "by hand".
Good luck :p

jdobbs
7th April 2016, 14:27
:confused:Hello good people, 1 request what's a good tool to pick the correct play list from the BVM mackingjay2. i back it up and it's out of sequence..and where do i get this tool from or the link? thank's..This method (https://www.youtube.com/watch?v=AlhBmIbReao) works well if you have PowerDVD available on your system.

varekai
7th April 2016, 15:08
...off topic... :o

kufo
7th April 2016, 16:42
:confused:Hello good people, 1 request what's a good tool to pick the correct play list from the BVM mackingjay2. i back it up and it's out of sequence..and where do i get this tool from or the link? thank's..


This seems to be solved in the redfox forum. To get a working copy youŽll ned the original disc or an untouched mountable image.
Look here for details: https://forum.redfox.bz/threads/mockingjay-2.68608/