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

Rich86
5th March 2019, 03:13
I just had to jump through hoops again to make a DVD from my "A Star Is Born" (2018 release) blu-ray, as BDRB is unable to create a DVD directly from this (and many other) BDs.

It failed towards the end of "Starting to MPLEX":
[21:32:59]PHASE TWO - Rebuild Started
- [21:32:59] Building ALTERNATE OUTPUT Structure
- [21:32:59] Converting 1 subtitles to DVD format.
- [21:33:46] Starting MPLEX.
- ERROR in attempt to mux (MPLEX)
[21:35:37] - Failed to REBUILD

I got it to work by:
The BD was ripped to hard disc using DVDFab64.
I then created a movie only BD50 folder/files using BDRB and forcing BDRB to convert the audio to lossy Dolby Digital by unchecking everything under "Audio Encoding Options" in Setup.
Then I used BDRB to create a DVD from those BD folder/files successfully.
It appears the process to create a DVD from a BD in BDRB doesn't like the lossless audio tracks in many titles?

AmigaFuture
5th March 2019, 06:08
Rich86:

Your Log is incomplete. [Snips] are good when redundancy is not required. Movie-Only Alt. output (DVD) will create AC-3 (Lossy). BD-RB isn't about "like" or "not like".. It's about function; logic.

Low HD space? Stuff missing. DVD's also uses Dolby Digital (AC-3) which is Lossy.

jdobbs
5th March 2019, 14:16
I just had to jump through hoops again to make a DVD from my "A Star Is Born" (2018 release) blu-ray, as BDRB is unable to create a DVD directly from this (and many other) BDs.

It failed towards the end of "Starting to MPLEX":
[21:32:59]PHASE TWO - Rebuild Started
- [21:32:59] Building ALTERNATE OUTPUT Structure
- [21:32:59] Converting 1 subtitles to DVD format.
- [21:33:46] Starting MPLEX.
- ERROR in attempt to mux (MPLEX)
[21:35:37] - Failed to REBUILD

I got it to work by:
The BD was ripped to hard disc using DVDFab64.
I then created a movie only BD50 folder/files using BDRB and forcing BDRB to convert the audio to lossy Dolby Digital by unchecking everything under "Audio Encoding Options" in Setup.
Then I used BDRB to create a DVD from those BD folder/files successfully.
It appears the process to create a DVD from a BD in BDRB doesn't like the lossless audio tracks in many titles?I'll pick up that release (using a recent generous donation from mparade) and give it a try. I've never experienced any problems in DVD conversion, so I'll be interested to see how it works.

jdobbs
5th March 2019, 17:28
No problem with "A Star Is Born":[03/05/19] BD Rebuilder v0.60.06
[08:05:05] Source: A_STAR_IS_BORN_2018_00002
- Input BD size: 33.97 GB
- Approximate total content: [02:15:45.136]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: DVD-5, 720x480/576, AC3 Audio
- Quality: High Quality (Default)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[08:05:06] PHASE ONE, Encoding
- [08:05:06] Processing: VID_00018 (1 of 1)
- [08:05:06] Extracting A/V streams [VID_00018]
- [08:12:30] Reencoding video [VID_00018]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 195,288 frames
- Bitrate: 3,956 Kbs
- [08:12:30] Reencoding: VID_00018
- [09:00:51] Video Encode complete
- [09:00:52] Processing audio tracks
- Track 4353 (eng): Reencoding audio to AC3...
[09:05:40]PHASE ONE complete
[09:05:40]PHASE TWO - Rebuild Started
- [09:05:40] Building ALTERNATE OUTPUT Structure
- [09:05:40] Converting 1 subtitles to DVD format.
- [09:08:14] Starting MPLEX.
- [09:09:49] Multiplexing 1 subtitles into stream.
- [09:12:49] Building DVD File Structure.
[09:15:01] - Encode and Rebuild complete
[09:15:01] JOB: A_STAR_IS_BORN_2018 finished.I'll try it with a different audio track... but I think the result will be the same.

jdobbs
6th March 2019, 00:28
I just had to jump through hoops again to make a DVD from my "A Star Is Born" (2018 release) blu-ray, as BDRB is unable to create a DVD directly from this (and many other) BDs.

It failed towards the end of "Starting to MPLEX":
[21:32:59]PHASE TWO - Rebuild Started
- [21:32:59] Building ALTERNATE OUTPUT Structure
- [21:32:59] Converting 1 subtitles to DVD format.
- [21:33:46] Starting MPLEX.
- ERROR in attempt to mux (MPLEX)
[21:35:37] - Failed to REBUILD

I got it to work by:
The BD was ripped to hard disc using DVDFab64.
I then created a movie only BD50 folder/files using BDRB and forcing BDRB to convert the audio to lossy Dolby Digital by unchecking everything under "Audio Encoding Options" in Setup.
Then I used BDRB to create a DVD from those BD folder/files successfully.
It appears the process to create a DVD from a BD in BDRB doesn't like the lossless audio tracks in many titles?Well, I found the issue... but it isn't BD-RB. The DD TRUE_HD track has an issue. BD-RB extracts the core audio -- and, strangely enough, it is 448Kbs (instead of 640Kbs as you normally see). That isn't really an issue since 448Kbs is what is used on DVD. But... it makes BD-RB try to use it intact. The problem is that the core audio track is corrupt. So when MPLEX tries to mux it, it gets this error:

**ERROR: [mplex.exe] Can't find next AC3 frame: @ 456128512 we have e027 - broken bit-stream?

The other english track is DTS-HD XLL. That one is used by default on my system. It works fine because BD-RB correctly realizes it must be encoded.

I'll try to put a fix in by adding an option in which the audio is forced to be reencoded.

AmigaFuture
6th March 2019, 07:06
It works fine with the 2nd Eng (DTS) for me to DVD-5/9. The 1st failed for me, as it did for JD...

Rich86
6th March 2019, 15:56
Yes - I had chosen the 1st audio track and it (mplex) failed trying to go to DVD-5 output. As I described, when I ran BDRB to create a movie only BD50 and forced the conversion of the True_HD track to lossy AC3 - then it ran fine. Then I ran BDRB again using the created movie only BD to make the DVD-5 and that ran fine.
I didn't think to try using the DTS track as the source when trying to go directly from the original BD to DVD5.
Thanks for looking at this.

gamete
7th March 2019, 10:09
Hi

For bdrebuilder is better win7 or win10?

Thanks

Ch3vr0n
7th March 2019, 16:02
Works the same. That said you should update to a newer is anyway. Win7 is in its last year of extended support. Jan '20 it's definitively game-over. Not even security updates anymore.

Verstuurd vanaf mijn Nexus 6P met Tapatalk

gamete
7th March 2019, 16:03
I know
Thanks 😊

AmigaFuture
7th March 2019, 21:05
Works the same. That said you should update to a newer is anyway. Win7 is in its last year of extended support. Jan '20 it's definitively game-over. Not even security updates anymore.

Verstuurd vanaf mijn Nexus 6P met Tapatalk

It has been a while since I've looked at Stardock WindowBlinds, and they've finally got it looking much better.. Hmm.. Stock Windows 10 is just...horrible to look at. I'll check it. Otherwise I'm my own security for 7 and XP. JD hasn't complained about 10 and BD-RB so...is functional.

Ch3vr0n
7th March 2019, 22:05
It's really not that bad. Despite being a bit big, once you remove all the tiles, it looks a lot like a classic start menu just more modern.

There's no need for third party stuff.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

AmigaFuture
8th March 2019, 01:47
I have attempted many times to enjoy the "modern" look. Flat, bland colors are good for an older OS before pizzazz was possible. I like the correct "Window" logo vs ?colored windows? logo (WHO puts "Wallpaper" over a Window anyway? A lot of hidden activity in the background also; lots of snooping.) No one from the State, of Federal where I live enjoys it. Most people I know deal with it because they aren't "tech enough to remove it". Now our Phones look like it. Anyway, I dig changes - not Loseer10. My son works at Intel and has told me a lot also. I would obliterate the tiles/Browser incorporation..not remove them. At least Windows 7 control panel is still there last time I checked. Auto-Updates are also...lame-as-the-figment.

Making Windows 10 mandatory...also excludes a large part of the population that doesn't dig, like, or even want to use it. Windows 10 was not introduced as a transition, it was forced. Bad, MS...*spanking*.

Anyway, when JD returns, I'm excited for new videos being supported. Taking some videos with my S9, I noticed some challenges as others have. Found work-around but... I'm laughing because now I'm also interested in the UHD support (camera).

Lathe
10th March 2019, 20:26
I have attempted many times to enjoy the "modern" look. Flat, bland colors are good for an older OS before pizzazz was possible. I like the correct "Window" logo vs ?colored windows? logo (WHO puts "Wallpaper" over a Window anyway? A lot of hidden activity in the background also; lots of snooping.) No one from the State, of Federal where I live enjoys it. Most people I know deal with it because they aren't "tech enough to remove it". Now our Phones look like it. Anyway, I dig changes - not Loseer10. My son works at Intel and has told me a lot also. I would obliterate the tiles/Browser incorporation..not remove them. At least Windows 7 control panel is still there last time I checked. Auto-Updates are also...lame-as-the-figment.

Making Windows 10 mandatory...also excludes a large part of the population that doesn't dig, like, or even want to use it. Windows 10 was not introduced as a transition, it was forced. Bad, MS...*spanking*.

Anyway, when JD returns, I'm excited for new videos being supported. Taking some videos with my S9, I noticed some challenges as others have. Found work-around but... I'm laughing because now I'm also interested in the UHD support (camera).

I've been quite happy with W8 which I've had since it came out. I know it's kind of a bastardized version since Windows I believe now only recognizes 8.1 Everything has always run simply and smoothly. I DO use Classic Start Menu for the Retro look and it gives you a crapload of options for how Explorer looks and works. And, of COURSE the very first thing I had the guy do who was building my computer at the time and going from W7 to W8 was IMMEDIATELY eliminate all the tiles! But, to be fair, I've never tried W10, and for all I know it could run better or faster. Just REALLY don't like changing my OS.

AmigaFuture
10th March 2019, 23:20
I've been messing with Start10 and WindowBlinds with XP and Seven skins. Ahhh, finally...doesn't look so horrible-eye-sore. Tiles are replaced, Yeess!!! Now I'm checking speeds...as well as how it functions with BD-RB. So far I haven't noticed the browse button click-no-response, click-again-and-get-the-prompt "bug" isn't there. Hmmm. 10 is supposed to be a lot better with RAM+CPU, so..for now, on a test partition only. Once in a great while it required 2 to 3 clicks before the source browse button actions of BD-RB would show a prompt.

Lathe
10th March 2019, 23:42
I've been messing with Start10 and WindowBlinds with XP and Seven skins. Ahhh, finally...doesn't look so horrible-eye-sore. Tiles are replaced, Yeess!!! Now I'm checking speeds...as well as how it functions with BD-RB. So far I haven't noticed the browse button click-no-response, click-again-and-get-the-prompt "bug" isn't there. Hmmm. 10 is supposed to be a lot better with RAM+CPU, so..for now, on a test partition only. Once in a great while it required 2 to 3 clicks before the source browse button actions of BD-RB would show a prompt.

Hmmm, well, I certainly could use 'a lot better' with RAM & CPU, that's for sure! :) I just FINALLY realized today that I had my CPU set to 'Turbo', which under normal circumstances is fine. BUT... I've been having x264 fail on encodes, so I checked the CPU temperature and I know that's it because I've been having some very long-standing trouble with it. Just today I had an encode fail part way through. So, just on a whim, mainly to see if I could boost the CPU fan speed or something, I noticed the Turbo setting. So, I THINK I put it back to normal. After rebooting up the system, I re-checked the CPU temperature, and sure enough, even during the same encode again, it was a HELL of a lot cooler, at least in CPU terms. So, maybe that will get me by until I am bloody forced to build another system.

wambaz
11th March 2019, 14:13
Hello everybody,

I'm trying to use the function "movie only" to fit one film UHD o a BDR-DL.
the main movie is a file.M2TS of 53GB, so removing additional languages it is within 50GB.
if I look at the log both audio and video are processed without re-encoding.

I use a player to see original M2TS file and it is ok
I use a player to see HEVC file inside WORKFILES directory, and it is ok
But when I open final M2TS file after rebuilding, the video is jerky, audio plays ok but it goes more and more out of synchro (because video is jerky).
practically the video is becoming longer because every 4-5 secs it hangs for 1 second.

any idea?
thanks a lot :thanks:

Sharc
11th March 2019, 14:46
^^^
BD-UHD is still experimental. See previous posts on this subject. You have to wait for a new release.

musiclover
12th March 2019, 10:28
You might want to try TSM2UHD. See http://forum.doom9.org/showthread.php?t=175120

SeeMoreDigital
12th March 2019, 10:44
You might want to try TSM2UHD. See http://forum.doom9.org/showthread.php?t=175120With regard to generating UHD (HEVC) muxes, unfortunately any muxing application that relies on TSmuxer is going to have problems!

The development of TSmuxer ceased years ago, way before the creation of HEVC...

wambaz
12th March 2019, 13:06
You might want to try TSM2UHD. See http://forum.doom9.org/showthread.php?t=175120

My problem is not the uhd bd structure, I'm not burning a disc but I'm just trying mux files on hard disk.
It seems bitrate has an influence, if I reencode with lower bitrate like 35000 the Effect is less, but still present.

jdobbs
12th March 2019, 14:12
My problem is not the uhd bd structure, I'm not burning a disc but I'm just trying mux files on hard disk.
It seems bitrate has an influence, if I reencode with lower bitrate like 35000 the Effect is less, but still present.TSMuxer has issues with UHD. It misses recognizing the start of some frames and then buries the frame within the PES packet of another. As a result the timestamps get way off, sync is lost, and you get jerky playback. After TSMuxer creates the structure, the video stream has to be remuxed completely to correct it. I'm working on that for BD-RB, but just haven't had a lot of free time lately.

omegaman7
15th March 2019, 04:09
I've been dealing with DTS XLL/HD-MA tracks, and I'm starting to keep the tracks. Or rather, instructing BD rebuilder to do so on MKV outputs(Keep original audio). I've been noticing that the outputs lose more than half their bitrate/file size(3700K becomes 1500K). Since I don't see BD Rebuilder "Encoding Audio Track", I'm assuming there's another explanation?
I've dismissed it for a few encodes, since i'm sure the difference is negligible. But now I'm curious lol

MrVideo
15th March 2019, 04:18
Since I don't see BD Rebuilder "Encoding Audio Track", I'm assuming there's another explanation?
Keeping the core of an HD/MA audio stream does not require recoding. After the MKV file is created, run it through Media Info to see if the HD/MA audio is still there, or not.

omegaman7
15th March 2019, 04:32
The output file says compression mode: lossy. Nothing of HD-MA.
So, the original HD-MA has redundant audio information? In that when removed, it's unnoticed? Apologies, my current audio system is bordering on analog, and my understanding not much better lol

MrVideo
16th March 2019, 02:18
Each of the high-def (actually a misnomer) audio formats have in their core the base codec, i.e.Dolby Digital 5.1 @ 640k and DTS 5.1 @ 1509k. That is to allow for players, amps, etc. that do not know about the non-lossy formats to be able to play them. That also allows for programs to also extract the core. No idea why BDRB is extracting the core instead of keeping the whole stream.

AmigaFuture
16th March 2019, 19:21
The output file says compression mode: lossy. Nothing of HD-MA.
So, the original HD-MA has redundant audio information? In that when removed, it's unnoticed? Apologies, my current audio system is bordering on analog, and my understanding not much better lol

You have disabled "Keep HD Audio for BD25/Alternate Intact". Which reduces core. It doesn't rerender the Audio.

omegaman7
16th March 2019, 21:31
You have disabled "Keep HD Audio for BD25/Alternate Intact". Which reduces core. It doesn't rerender the Audio.

Since I'm outputting MKV, I didn't think that setting would apply.

jdobbs
16th March 2019, 22:02
Since I'm outputting MKV, I didn't think that setting would apply.Make sure you have "Keep HD Audio for BD25/Alternate Intact" checked on the SETUP dialog. You also have to select (or create) an ALTERNATE profile that has aType set to 2 (intact audio). If those two conditions are met, then both the core and the HD audio will be kept.

Just a warning, though. In creating an MKV the HD and core audio are muxed separately (as two independent audio streams). An MKV doesn't support two audio types muxed as one stream like Blu-Ray does. That fact makes it even more complicated when you go the other way (from MKV to Blu-Ray), since the Blu-Ray standard doesn't support the HD stream without the core.

Output to MKV is Alternate output (non BD)... so the setting "Keep HD Audio for BD25/Alternate Intact" applies.

omegaman7
16th March 2019, 22:41
Well, that's embarrassing lol Guess I disregarded the second part.
Thanks for your help, everyone. MUCH appreciated.

AmigaFuture
16th March 2019, 23:00
Well, that's embarrassing lol Guess I disregarded the second part.
Thanks for your help, everyone. MUCH appreciated.

Why embarrassing? Ya lurned sumtin', right? :D

Make sure you have "Keep HD Audio for BD25/Alternate Intact" checked on the SETUP dialog. You also have to select (or create) an ALTERNATE profile that has aType set to 2 (intact audio). If those two conditions are met, then both the core and the HD audio will be kept.

Just a warning, though. In creating an MKV the HD and core audio are muxed separately (as two independent audio streams). An MKV doesn't support two audio types muxed as one stream like Blu-Ray does. That fact makes it even more complicated when you go the other way (from MKV to Blu-Ray), since the Blu-Ray standard doesn't support the HD stream without the core.

Output to MKV is Alternate output (non BD)... so the setting "Keep HD Audio for BD25/Alternate Intact" applies.

All right, all right, just because I didn't go into details... Show-off! :D

jdobbs
17th March 2019, 13:32
Well, that's embarrassing lol Guess I disregarded the second part.
Thanks for your help, everyone. MUCH appreciated.Don't be embarrassed. I actually looked at the code to be sure myself.All right, all right, just because I didn't go into details... Show-off! :DIt's an old trick. A quote from W.C. Fields: "If you can't dazzle them with brilliance, baffle them with bullshit."

AmigaFuture
17th March 2019, 23:25
Yeah, he wasn't a very consistently happy guy. I also forget about the quote. Are you sure, Penn of Penn and Teller didn't say that? Haa!

The 3 Stooges: "It's my vein...the biggest vein you ever saw." - "I'll show you, it's right there. Ain't it a wopper"?

DrinkLyeAndDie
20th March 2019, 00:42
Has anyone else updated to DGDecNV 2053 dated 2019-03-10 and run into any issues using it with BD-RB? Initially I was getting errors related to extracting subs and then after playing around with settings, a clean BD-RB install, etc, the problem moved to errors when doing CRF prediction. I spent a number of hours trying to figure out why I was running into issues seemingly out of nowhere until I remembered that I had recently updated from the previous DGDecNV version. I reverted back to the older version, 2053 dated 2019-02-23, and things appear to be working again. So far.

Original error message:

03-19-19 [17:47:12] ExtractAudioSubs() 00053 1604

Don't happen to have error from the CRF prediction stage. I deleted the log before saving it.

jdobbs
20th March 2019, 01:20
Has anyone else updated to DGDecNV 2053 dated 2019-03-10 and run into any issues using it with BD-RB? Initially I was getting errors related to extracting subs and then after playing around with settings, a clean BD-RB install, etc, the problem moved to errors when doing CRF prediction. I spent a number of hours trying to figure out why I was running into issues seemingly out of nowhere until I remembered that I had recently updated from the previous DGDecNV version. I reverted back to the older version, 2053 dated 2019-02-23, and things appear to be working again. So far.

Original error message:



Don't happen to have error from the CRF prediction stage. I deleted the log before saving it.I've been using v2053 for some time now. But it is dated 5/21/2017 (last modified date). It doesn't sound right that there would be a difference in the same version? A bad download, maybe?

DrinkLyeAndDie
20th March 2019, 01:31
I've been using v2053 for some time now. But it is dated 5/21/2017. It doesn't sound right that there would be a difference in the same version???? A bad download, maybe?

I definitely agree that it is odd. DG does "slipstream" in changes and there have been a number since February 23rd. You can find the changes here: http://rationalqm.us/board/viewtopic.php?f=5&t=463&start=150. Slipstream 170-172 are the new changes; the last 3 posts.

With the above said, all backups were failing with the latest version, slipstream 172. All. I was beginning to get extremely concerned. I dropped back to the older release, sleepstream 169, and I have one successful backup completed and a second 75% completed. Once the current backup finishes I am going to move to the new version again with the download I previously used to see if the failures return. I'll then test with a new download of the same version.

I'll report back my results.

DrinkLyeAndDie
20th March 2019, 01:49
Ugh. DG moved the binaries. :mad: He changed the location of the x86 binaries to a sub directory so BD-RB was pointing to the wrong location. If I correct the path to the DGDecNV files I bet the problem will miraculously go away.

EDIT: I corrected the path in BDREBUILDER.INI to point to the files in the new sub directory that DG moved the dgdecnv EXE and DLL to. The failure still occurred. So, I moved them to the base directory like they used to be and then set the paths again in BDREBUILDER.INI. Now things are working. Problem solved.

AmigaFuture
23rd March 2019, 05:38
Ugh. DG moved the binaries. :mad: He changed the location of the x86 binaries to a sub directory so BD-RB was pointing to the wrong location. If I correct the path to the DGDecNV files I bet the problem will miraculously go away.

EDIT: I corrected the path in BDREBUILDER.INI to point to the files in the new sub directory that DG moved the dgdecnv EXE and DLL to. The failure still occurred. So, I moved them to the base directory like they used to be and then set the paths again in BDREBUILDER.INI. Now things are working. Problem solved.

What do you mean DG moved the files? You're the one that copies them into place, as I did, and you're the one that picks the BD-RB location from Settings/Edits the prefs. Do you mean Donald Graft performed a magic(miracle) act on your Windows install you don't understand? :p

gonca
23rd March 2019, 13:07
What do you mean DG moved the files? You're the one that copies them into place, as I did, and you're the one that picks the BD-RB location from Settings/Edits the prefs. Do you mean Donald Graft preformed a magic(miracle) act on your Windows install you don't understand? :p

Do you mean performed by any chance?

MrVideo
24th March 2019, 10:28
BDRB failed to find 6 videos on a DVD.

Here is an image showing what BDRB saw and what VRD saw (http://vidiot.com/images/90210-S2-D6-compare.jpg).

No idea why BDRB is not seeing them.

UPDATE: BDRB missed displaying a file for selection on S1-D5. It displayed the first one in the title, but failed to display the 2nd.

AmigaFuture
24th March 2019, 23:47
Do you mean performed by any chance?

Nice notice, by opportunity! :) Appreciate it.

Blurayhd
27th March 2019, 04:17
Hi guys I have to convert UHD to FULL HD a movie and I have no idea what number put just right there where arrow is? I mean, for get the best quality possible what number I have to set in CRF?


https://i.ibb.co/CKS6b48/Captura.png

Thank you in advance!!

MrVideo
27th March 2019, 06:31
OK, on another DVD, of the same 90210 S1, I told BDRB to import two of the special feature files. It did, in that the Stream directory has the two files. But, when I import the current project into the Batch queue, it only converted the 2nd M2TS file into a MKV. The first file was ignored, not even mentioned in the log.

When I re-did it, only selecting the first file that it wouldn't do, it did it.

sneaker_ger
27th March 2019, 11:27
Hi guys I have to convert UHD to FULL HD a movie and I have no idea what number put just right there where arrow is? I mean, for get the best quality possible what number I have to set in CRF?
18 is high quality.
Basically,
low crf = high quality, big file size
high crf = low quality, small file size

If you go too low the file becomes bigger than the source file so you have to find a compromise. No one can tell you what you would like because it's subjective. You have to experiment a bit.

jdobbs
27th March 2019, 12:49
Hi guys I have to convert UHD to FULL HD a movie and I have no idea what number put just right there where arrow is? I mean, for get the best quality possible what number I have to set in CRF?

Thank you in advance!!A CRF of 23 is X264's default and is a good compromise between size and quality. A value of 16 is pretty close to a lossless encode, but creates a huge file size. Anything below that is massive overkill. I'd recommend keeping it at 23, but if you are really worried about quality, try something a bit lower.

Blurayhd
27th March 2019, 17:19
A CRF of 23 is X264's default and is a good compromise between size and quality. A value of 16 is pretty close to a lossless encode, but creates a huge file size. Anything below that is massive overkill. I'd recommend keeping it at 23, but if you are really worried about quality, try something a bit lower.

Hi Jdobbs and yes I´m talking about quality I mean, the idea is to get approximately the same quality that you got with you have the full bluray BD50, if I have the UHD from some movie so far I understand it I can convert to Full hd but keeping the quality of BD50 ?

What is exactly, dear Jjdobbs of CRF number to obtain, I dont know, 48gb is the normal size of a BD50?

i really hope you can understand it because English is not my first language

Thank you in advance!!

Blurayhd
27th March 2019, 17:24
18 is high quality.
Basically,
low crf = high quality, big file size
high crf = low quality, small file size

If you go too low the file becomes bigger than the source file so you have to find a compromise. No one can tell you what you would like because it's subjective. You have to experiment a bit.

Yes I tried it with a very low crf and I get a120gb larger file

Like I said to Jdobbs the idea is to encode UHD to Full hd but the result file keep the BD50 quality and fit on a 48gb file

ps: as an example, think just like this, we have an UHD file that we need to encode to Fullhd but keeping the quality and the file size have to br 46/48gb (a BD50 disc)

You know what I mean?

Excuse me my English I try to do my best

sneaker_ger
27th March 2019, 17:25
If you want to hit a certain target size .. select "Two Pass Target Size (MB)" and enter the size you want. Not CRF.

Blurayhd
27th March 2019, 17:41
If you want to hit a certain target size .. select "Two Pass Target Size (MB)" and enter the size you want. Not CRF.

Thank you for that speaking about CRF I forget about that option but, as I always use BD rebuilder with CRF option and I love the quality I preffer to keep using this crf option dear Sneaker because maybe I get a lite bigger file size but that file I´ll can convert again with BD rebuilder this time to fit an BD25 is that correct?

I mean, maybe no matters if the file size is 48 or 80gb, Bd rebuilder can convert this file to a BD25 keeping the amazing quality is that correct?

ps: if you all have to convert UHD to Full hd using CRF what number you put there?

sneaker_ger
27th March 2019, 18:13
You are confusing me. What is your goal? Why are you doing this? Are you targeting HDD, BD25 or BD50?