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

Ch3vr0n
6th September 2014, 00:12
been using 2048 for a while now

AmigaFuture
6th September 2014, 00:34
Updated the Dirty Dancing post. I hope you're able to repeat it with that BD or another. I'm able to repeat it with Toy Story 3..

soneca
6th September 2014, 00:40
Thanks guys. I think everything should be all right with the latest version.
jdobbs, why not do some tests the latest versions of ffdshow and Haali Media Splitter?
I've been testing the latest versions and seem to be 100%.
Unlikely to be updated again, and it also helps prevent certain problems.

HWK
6th September 2014, 02:25
Hmm.. guess I need to get up-to-date. I'm using 2046.

Donald has changed license system in 2047 and beyond. Just wanted to give you heads up.

Here is link to generate license
http://rationalqm.us/licensing.html

andref4
6th September 2014, 11:43
Huge thanks :)
Can Multiprocess be used with Threads is (in my case) at 8?

A little bit OT: can we expect H265 any soon on your program?

in new dvdfab you can use H265. You can try it free for 30 days.

andref4
6th September 2014, 11:51
I don't now how "isn't recommended version" is ok...

BD-RB doesn't care about FFDSHOW folders or where it is installed. It looks at the registry key (32 bit and 64 bit):

HKLM\Software\GNU\ffdshow
HKLM\Software\Wow6432Node\GNU\ffdshow

If it exists... then FFDSHOW is installed correctly. If not, then it isn't.

I just installed the July 2014 (ffdshow_rev4532_20140717_clsid.exe) version of FFDSHOW and it is working fine (although it hasn't been tested and therefore isn't recommended). So the version has no impact (they all set the registry entry). That tells me something else is the issue (not the version) on your system.

I dont know. Now I use your old 0.48.03 for 2d and a few 3d bds and dvdfab for mkvs and 3d copy. I cant format my machine only whily new bd-reb wont work. On my brothers machine is the same thing. 0.48.05 wont work with ffdshow. And all other Frame Servers are to slow and dont work with cropping black borders. You can remove this option if other Frame Servers are selected. It doesnt work.

jdobbs
6th September 2014, 13:59
Thanks guys. I think everything should be all right with the latest version.
jdobbs, why not do some tests the latest versions of ffdshow and Haali Media Splitter?
I've been testing the latest versions and seem to be 100%.
Unlikely to be updated again, and it also helps prevent certain problems.The problem with those is that, in the past, I've found that it sometimes takes a month or two of running it before you pick up on something that is a deal-breaker. So it's not just a matter of "Ok I ran it on a few jobs, let's ok it for general use."

jdobbs
6th September 2014, 14:00
in new dvdfab you can use H265. You can try it free for 30 days.The point is to be able to do it forever, not 30 days.

jdobbs
6th September 2014, 14:02
I dont know. Now I use your old 0.48.03 for 2d and a few 3d bds and dvdfab for mkvs and 3d copy. I cant format my machine only whily new bd-reb wont work. On my brothers machine is the same thing. 0.48.05 wont work with ffdshow. And all other Frame Servers are to slow and dont work with cropping black borders. You can remove this option if other Frame Servers are selected. It doesnt work.You're distorting the facts. It works on everybody's machine but yours... because you refuse to follow the installation instructions. How many other posts do you see in this thread that supports your contention? I'll give you the answer: none.

Also... this is a BD Rebuilder thread. Throwing other software into your comments because you are unhappy is inappropriate and off topic.

laserfan
6th September 2014, 14:31
Hmm.. guess I need to get up-to-date. I'm using 2046.

Be wary of 2048, I think it might no longer be compatible with older video cards such as my 9600GT.

But I haven't tested it.

Ch3vr0n
6th September 2014, 14:56
doubt it, ya could ask him on his forum

soneca
6th September 2014, 15:07
It seems that these cards (https://developer.nvidia.com/cuda-gpus) below do not work with version 2048.

GeForce 8800 Ultra
GeForce 8800 GTX
GeForce GT 340
GeForce GT 330
GeForce GT 320
GeForce 315
GeForce 310
GeForce 9800 GT
GeForce 9600 GT
GeForce 9400GT

jdobbs
6th September 2014, 15:16
I'm testing with an almost stock INI. I stopped the reencode process, and entered FORCE_NOENCODE=1 via the Edit Config. After the refresh I select Preview and the screen grab is what was displayed.

Then I exited BD-RB, then reran...and had it preview again. The file is displayed correctly. It has done it a couple times now with the Red Text. I'm attempting note how to get it to show the text again every time..I'll add to this when I get it.Updated the Dirty Dancing post. I hope you're able to repeat it with that BD or another. I'm able to repeat it with Toy Story 3..I don't know what "...the screen grab is what was displayed" means?

I just opened "Toy Story 3" and previewed one of the parts. I then edited the config/ini and set FORCE_NOENCODE=1. I then previewed again. No issue.

I tried it again by starting a job, stopping it, and then setting FORCE_NOENCODE=1 -- still no issue.

Video Dude
6th September 2014, 15:41
It seems that these cards (https://developer.nvidia.com/cuda-gpus) below do not work with version 2048.

GeForce 8800 Ultra
GeForce 8800 GTX
GeForce GT 340
GeForce GT 330
GeForce GT 320
GeForce 315
GeForce 310
GeForce 9800 GT
GeForce 9600 GT
GeForce 9400GT

Don wanted to still support those cards, but because NVIDIA changed/updated the CUDA library he can't. The new CUDA drops support of the older cards.

jdobbs
6th September 2014, 16:05
So what's the advantage of the newer library? Faster?

jdobbs
6th September 2014, 16:30
You're distorting the facts. It works on everybody's machine but yours... because you refuse to follow the installation instructions. How many other posts do you see in this thread that supports your contention? I'll give you the answer: none.

Also... this is a BD Rebuilder thread. Throwing other software into your comments because you are unhappy is inappropriate and off topic.By the way. If you want to get it to work, even with your bad install, just use the registry editor and add the two keys I told you about.

Video Dude
6th September 2014, 16:47
So what's the advantage of the newer library? Faster?

The advantage is for NVIDIA, people will have to buy new cards. It should be mentioned that NVIDIA will soon be dropping driver support for the cards listed above, its not just CUDA support. That means those cards will no longer work with the upcoming driver release.

Anyone interested can read Don's inquiry on the Nvidia forum:

http://devtalk.nvidia.com/default/topic/761171/cuda-setup-and-installation/cuda-backward-compatibility-questions-inspired-by-version-6-5/

daberti
6th September 2014, 18:29
in new dvdfab you can use H265. You can try it free for 30 days.

Thanks, nighly builds of Handbrake offer it.
I gave it a try, but at current moment it is NOT yet ripe enough (H265) IMHO

daberti
6th September 2014, 18:30
The point is to be able to do it forever, not 30 days.

Agreed !

Ch3vr0n
6th September 2014, 18:44
@jdobbs: looks like you will have "no choice" but to implement x265 support at some point in the future ;)

http://www.myce.com/news/4k-blu-ray-format-confirmed-72606/

The 4K format will also offer an expanded color gamut, higher frame rates (up to 60fps), high dynamic range (HDR), and will use the H265 video codec for the most efficient compression on the discs.

but ofcourse in the end it's your software, you decide if you'll implement support or not :)

jdobbs
6th September 2014, 18:53
@jdobbs: looks like you will have "no choice" but to implement x265 support at some point in the future ;)

http://www.myce.com/news/4k-blu-ray-format-confirmed-72606/



but ofcourse in the end it's your software, you decide if you'll implement support or not :)I wonder just how far they can go. I mean most people really can't distinguish 720p from 1080p -- I just wonder if 4K is just beyond reasonable? I'm sure you could see the difference if you are 6 inches from your screen... but I don't know anyone who watches that close.

Now that I think about it, never mind. People pay $1.50 for a 16oz bottle of water that came filtered from a tap (just like the one in their kitchen). So they'll surely be willing to pay for 4K.

Ch3vr0n
6th September 2014, 18:54
jup, i'm pleny ok with the normal lvl of detail, in my eyes 4k is just a gimmick to pull cash out of ppl's pockets for differences they can't actually see :).

Sharc
6th September 2014, 18:56
Pixelmania .....
A big step I would see is 3D (home) cinema without goggles.

HWK
6th September 2014, 22:54
I wonder just how far they can go. I mean most people really can't distinguish 720p from 1080p -- I just wonder if 4K is just beyond reasonable? I'm sure you could see the difference if you are 6 inches from your screen... but I don't know anyone who watches that close.


jup, i'm pleny ok with the normal lvl of detail, in my eyes 4k is just a gimmick to pull cash out of ppl's pockets for differences they can't actually see :).

Let not forget about new layer of DRM nonsense coming your way :D I have full hope Slysoft will tackle it without any issues.

Lathe
6th September 2014, 23:08
You generally don't want to set it to the number of threads. Pick a lower number (probably 3 or so) that will get the processor usage close to 100% in Pass 1. That will get the maximum out of the setting. Setting it too high can actually slow things down (especially in Pass 2).

At some point I will support H265 output to MKV. I still need to test it with a newer version of MKVMERGE (that supports it). I need to find a directshow H265 decoder for my system -- any recommendations?

I may add MULTIPROCESS capability for LAVF in the future. But, at least on my system, there isn't a lot of processor headroom left when using LAVF; so I'm not sure the benefit would be that great.

Yes, with my system too (I just about always use LAVF) my CPU is pretty much always almost fully utilized. At first, when the Multiprocess option came out I was pretty excited to try it, but I found out that in my case anyway, my CPU was almost always topped out (AMD A8-5600 APU w/Radeon 7560 - 8 Gigs RAM - Samsung Evo SSD primary drive)

Lathe
6th September 2014, 23:36
I wonder just how far they can go. I mean most people really can't distinguish 720p from 1080p -- I just wonder if 4K is just beyond reasonable? I'm sure you could see the difference if you are 6 inches from your screen... but I don't know anyone who watches that close.

Now that I think about it, never mind. People pay $1.50 for a 16oz bottle of water that came filtered from a tap (just like the one in their kitchen). So they'll surely be willing to pay for 4K.

Fully agree...

I mean, I like my High Quality - 2 pass and all..., but there comes a point where it gets pretty silly...

BTW, the 'Bottled water' example is most incisive - one of THE most outstanding examples of mass brainwashing I've ever seen...

IVaN_000
7th September 2014, 01:17
@jdobbs: looks like you will have "no choice" but to implement x265 support at some point in the future ;)

http://www.myce.com/news/4k-blu-ray-format-confirmed-72606/



but ofcourse in the end it's your software, you decide if you'll implement support or not :)

I welcome the 60 fps, but 4K... meh.

With the new codec it's impossible to make those new discs backwards compatible.

jdobbs
7th September 2014, 04:51
Let not forget about new layer of DRM nonsense coming your way :D I have full hope Slysoft will tackle it without any issues.I worry that at some point in the future they will make a system that uses the now-common internet capable player to "phone-home" for a key to play. The only thing that makes all current DRM vulnerable is the fact that the player has to have a localized capability to decrypt/play it. I'd hate to own a disc that won't play unless the distributor's servers are up.

Of course if they do that, they may make themselves obsolete -- since HD via internet (e.g. Netflix, Hulu, Amazon) would be a better alternative with the same type of requirements. I'm betting we see H265 in use in those players pretty soon too, as it cuts down the bandwidth requirement considerably.

Hmm... I guess we're really getting off-topic for this thread.

Lathe
7th September 2014, 05:46
Hmm... I guess we're really getting off-topic for this thread.

Yeah, but that's okay because you're the boss... :cool:

mparade
7th September 2014, 12:02
FORCED_SUB_LANG hiddenopt is valid only for movie-only backups? I read about it everything in the changes.txt and in this thread but I still don't know when it is applied.

Any help would be really appreciated.

daberti
7th September 2014, 14:15
I wonder just how far they can go. I mean most people really can't distinguish 720p from 1080p -- I just wonder if 4K is just beyond reasonable? I'm sure you could see the difference if you are 6 inches from your screen... but I don't know anyone who watches that close.

Now that I think about it, never mind. People pay $1.50 for a 16oz bottle of water that came filtered from a tap (just like the one in their kitchen). So they'll surely be willing to pay for 4K.

Yes, I do agree. But H265 could have good advantages even on 1080p.
Back to my issues, I still cannot get 100% usage on my CPU :(

jdobbs
7th September 2014, 14:42
FORCED_SUB_LANG hiddenopt is valid only for movie-only backups? I read about it everything in the changes.txt and in this thread but I still don't know when it is applied.

Any help would be really appreciated.It only applies to movie-only backups. When doing a full backup the backup has to follow the same rules as the original.

jdobbs
7th September 2014, 16:23
Yeah, but that's okay because you're the boss... :cool:DOOM9 makes the rules... :)

AmigaFuture
7th September 2014, 21:35
I just opened "Toy Story 3" and previewed one of the parts. I then edited the config/ini and set FORCE_NOENCODE=1. I then previewed again. No issue.

I tried it again by starting a job, stopping it, and then setting FORCE_NOENCODE=1 -- still no issue.

Select Dirty Dancing BD. Or Toy Story 3.
VID is for 0056 or 00076; respectively.
Exit BD-RB if it's running.
Then load/run BD-RB.
Disable "Quicker" Encode for Extras
Remove FORCE_NOENCODE=1 if it's in the config. (This shouldn't be needed...but...I'm testing..)
Preview VID.
If it shows as should, now enable "Quicker" Encode..
Click Backup.
Let first Encode happen...then abort.
Go back and preview same VID.
Now you should see RED text with MKV also in it.
Uncheck "Quicker".
Preview VID again, and still same RED.
Exit BD-RB.
Run/Load BD-RB.
Preview VID... Now should display correctly.
Check mark "Quicker" again.
Preview VID.. Displays as should.
Click Backup, I use don't resume..
Then abort.
Preview VID..should show Red text.
Uncheck "Quckier" again..
Preview gain, and displays correct (DD or red for ST3).
Click Backup.
Once rerender starts, for a couple seconds...abort.
Preview that VID again... Now Red Text shows.

The point being, after aborting a backup...I'm noticing Red text with some VIDs. What are your results? I'm using Movie & Menus with DGDecNV and DirectshowSource.

I Uninstalled FFDShow, then Installed it again, reconfigured it..in case of corruption. My machine isn't using any Codec Packs...I stopped that long ago.

Update: With FIRMSource serving, this doesn't happen. Of course.

daberti
8th September 2014, 14:42
@JDobbs

I've just sent a donation to encourage your work ;)

Some questions:
1)Is it possible that, outputting to MKV, from a BD source, with the only setting changed being the resolution (Others being Alternate Movie Only, AAC Auto, CRF=20, Better (Faster) ) , if I keep 1080p I get roughly 1/3rd the size of the downsized version at 720p, i.e. 1.2GB vs 3.3GB ?

2)I never had CPU at full employment

3)Even when using LAVF without resizing H264 32bit had been used

All of this with Alternate Movie Only output and mkv container.

Last question: maybe it has been treated already, is there a way to "trim" the input video just to test a part of it without waiting for hours for the complete video encoding?

Thanks in advance

jdobbs
8th September 2014, 15:41
@JDobbs

I've just sent a donation to encourage your work ;)

Some questions:
1)Is it possible that, outputting to MKV, from a BD source, with the only setting changed being the resolution (Others being Alternate Movie Only, AAC Auto, CRF=20, Better (Faster) ) , if I keep 1080p I get roughly 1/3rd the size of the downsized version at 720p, i.e. 1.2GB vs 3.3GB ?

2)I never had CPU at full employment

3)Even when using LAVF without resizing H264 32bit had been used

All of this with Alternate Movie Only output and mkv container.

Last question: maybe it has been treated already, is there a way to "trim" the input video just to test a part of it without waiting for hours for the complete video encoding?

Thanks in advance1. That doesn't sound right. When outputting with the same settings 720p should be significantly smaller than 1080p.

2. Have you tried using MULTIPROCESS?

3. Currently LAVF is never used for ALTERNATE output. I did that because generally ALTERNATE requires resizing, and X264's resizing is pretty slow. But since I'm trying to get to a point where BD-RB is less dependent on Directshow, I may have to readdress that.

*Thanks for contributing!

daberti
8th September 2014, 16:43
1. That doesn't sound right. When outputting with the same settings 720p should be significantly smaller than 1080p.

2. Have you tried using MULTIPROCESS?

3. Currently LAVF is never used for ALTERNATE output. I did that because generally ALTERNATE requires resizing, and X264's resizing is pretty slow. But since I'm trying to get to a point where BD-RB is less dependent on Directshow, I may have to readdress that.

*Thanks for contributing!

Should be smaller indeed.
I'm retrying. Let you know later.
FYI the source is VC1 encoded.

I used multiprocess=1 but it did not improve things.

LAVF. Actually when I did no resizing, i,e, keeping 1080P, LAVF value is set at -1 (from the INF file) if it can help you.
Mmmh: could I recommend you to leave LAVF enabled when the Alternate Output resolution is kept just as the source resolution?

Trimming to limit encoding length? How? Just to do a 10min encoding to test different quality settings.

Edit
Job started:
17:53:43] Source: L_UOMO_CHE_FISSA_LE_CAPRE_00000
- Input BD size: 20,18 GB
- Approximate total content: [01:34:03.971]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1280x720, Auto-AAC
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[17:53:43] PHASE ONE, Encoding
- [17:53:43] Processing: VID_00000 (1 of 1)
- [17:53:43] Extracting A/V streams [VID_00000]

it is defintely using LAVF!

jdobbs
8th September 2014, 17:11
Should be smaller indeed.
I'm retrying. Let you know later.
FYI the source is VC1 encoded.

I used multiprocess=1 but it did not improve things.

LAVF. Actually when I did no resizing, i,e, keeping 1080P, LAVF value is set at -1 (from the INF file) if it can help you.
Mmmh: could I recommend you to leave LAVF enabled when the Alternate Output resolution is kept just as the source resolution?

Trimming to limit encoding length? How? Just to do a 10min encoding to test different quality settings.

Edit
Job started:
17:53:43] Source: L_UOMO_CHE_FISSA_LE_CAPRE_00000
- Input BD size: 20,18 GB
- Approximate total content: [01:34:03.971]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1280x720, Auto-AAC
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[17:53:43] PHASE ONE, Encoding
- [17:53:43] Processing: VID_00000 (1 of 1)
- [17:53:43] Extracting A/V streams [VID_00000]

it is defintely using LAVF!No. It isn't. What is shown is your setting... but, as I said, ALTERNATE never actually uses it. Look at LASTCMD.TXT and you'll see that an AVS is used in the command line.

I can only tell you the facts... whether you want to accept them is another matter.

daberti
8th September 2014, 17:41
No. It isn't. What is shown is your setting... but, as I said, ALTERNATE never actually uses it. Look at LASTCMD.TXT and you'll see that an AVS is used in the command line.

I can only tell you the facts... whether you want to accept them is another matter.

I'm accepting them :)
http://www.danieleberti.com/dan/clipboard.jpg
Also this is a fact: CPU is by no means even at 40%.

So, to sum up:
1)LAVF is never used with ALTERNATE and so never will be x264-64.
2)No trimming currently implemented.

Not to be critical, just for sake of knowing :)

Just the time to allow the encoding to finish to cross-check the size.

EDIT2
This time it produced a 600MB file.

Now trying again multiprocess=1 on 1080p, CRF20, High Quality. Will tell later or Tomorrow.

jdobbs
8th September 2014, 20:23
So, to sum up:
1)LAVF is never used with ALTERNATE and so never will be x264-64.
2)No trimming currently implemented.1. That's correct. Although it may be used in next release, depending upon whether I get to it.
2. If you trim to less than 5000 frames, MULTIPROCESS will also not be used.

daberti
8th September 2014, 21:10
1. That's correct. Although it may be used in next release, depending upon whether I get to it.
2. If you trim to less than 5000 frames, MULTIPROCESS will also not be used.

Great thanks :)
Great thanks also for your precious software.

Edit
The promised results: ALTERNATE, CRF20, 1080p, High Quality.
First with MULTIPROCESS=1
Last without.
In both cases High Quality brought about 100% CPU usage on all of 4 Cores.
----------------------
[09/08/14] BD Rebuilder v0.48.05 (beta)
[19:56:41] Source: L_UOMO_CHE_FISSA_LE_CAPRE_00000
- Input BD size: 20,18 GB
- Approximate total content: [01:34:03.971]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1920x1080, Auto-AAC
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[19:56:45] PHASE ONE, Encoding
- [19:56:45] Processing: VID_00000 (1 of 1)
- [19:56:45] Extracting A/V streams [VID_00000]
- [20:07:03] Reencoding video [VID_00000]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23,976fps, 135.320 frames
- [20:07:03] Reencoding: VID_00000, Pass 1 of 1
- [23:22:36] Video Encode complete
- [23:22:36] Processing audio tracks
- Track 4352 (ita): Reencoding audio to AAC...
[23:35:00]PHASE ONE complete
[23:35:00]PHASE TWO - Rebuild Started
- [23:35:00] Building ALTERNATE OUTPUT Structure
[23:36:47] - Encode and Rebuild complete
[23:36:47] JOB: L_UOMO_CHE_FISSA_LE_CAPRE finished.
----------------------
[09/09/14] BD Rebuilder v0.48.05 (beta)
[09:27:06] Source: L_UOMO_CHE_FISSA_LE_CAPRE_00000
- Input BD size: 20,18 GB
- Approximate total content: [01:34:03.971]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1920x1080, Auto-AAC
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[09:27:06] PHASE ONE, Encoding
- [09:27:06] Processing: VID_00000 (1 of 1)
- [09:27:06] Extracting A/V streams [VID_00000]
- [09:39:02] Reencoding video [VID_00000]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23,976fps, 135.320 frames
- [09:39:02] Reencoding: VID_00000, Pass 1 of 1
- [10:49:51] Video Encode complete
- [10:49:51] Processing audio tracks
- Track 4352 (ita): Reencoding audio to AAC...
[11:02:34]PHASE ONE complete
[11:02:34]PHASE TWO - Rebuild Started
- [11:02:34] Building ALTERNATE OUTPUT Structure
[11:02:48] - Encode and Rebuild complete
[11:02:48] JOB: L_UOMO_CHE_FISSA_LE_CAPRE finished.

Sharc
9th September 2014, 20:56
There seems to be no direct relation between the Auto Quality terminology and the x264 --preset.
For example (with AUTO_BIAS=3):
- Auto Quality: Good (Very Fast), Two pass
- lastcmd.txt: --preset superfast
(the reduction source/target is 36/23 GB)
Is this possibly a bug, or does BD-RB just use its own terminology?

jdobbs
9th September 2014, 22:15
There seems to be no direct relation between the Auto Quality terminology and the x264 --preset.
For example (with AUTO_BIAS=3):
- Auto Quality: Good (Very Fast), Two pass
- lastcmd.txt: --preset superfast
(the reduction source/target is 36/23 GB)
Is this possibly a bug, or does BD-RB just use its own terminology?BD-RB uses its own terminology, mainly to avoid confusion. I don't believe the settings in X264 are clear, in terms of actual quality, to most people. For example, you get a very high level of quality that is appropriate for almost all encodes with the "medium" preset -- but the term "medium" doesn't reflect that. The X264 presets represent speed more than quality (fast, veryfast, slow, slower, etc.).

Sharc
9th September 2014, 22:24
BD-RB uses its own terminology, mainly to avoid confusion. I don't believe the settings in X264 are clear, in terms of actual quality, to most people. For example, you get a very high level of quality that is appropriate for almost all encodes with the "medium" preset -- but the term "medium" doesn't reflect that. The X264 presets represent speed more than quality (fast, veryfast, slow, slower, etc.).
o.k., thanks. Nice to see how fast it goes; I changed from BD5/9 to BD25 only recently.

Lathe
10th September 2014, 19:08
Since we are SORT of talking about speed, I'm curious about something. I had upgraded to the newest version and for some odd reason I guess I must have forgotten to set the 'Use internal LAVF' like I always do (I never really do any resizing or anything other than occasionally throw in some x264 tweaks) So, I'm running this encode overnight and normally say I have it set for High Quality 2 Pass and a few x264 tweaks; usually a Blu-ray of about 28 Gigs or so would take about an hour or a bit more for the first pass and then about maybe 6-8 hours or so for the second pass.

Well, when I went to bed I noticed on the screen that the frame server being used was Directshow, which I normally never use; I am guessing that it is the default setting. Anyway, when I got up this morning and looked at it, it had already run about 9 hours and it has about another 8 to go! :) Also, I did notice before going to bed that the frame rate for the first pass seemed slower than usual.

I am just curious since I happened inadvertently to use Directshow this time, with all other things being equal, why would it take so much longer and be so much slower (fps @ about 2.5 instead of with LAVF about 6-7)? My CPU is normally topped out; now, it is pretty close to that, maybe running at about 90-95%.

And this time, I was looking forward to it maybe being a little faster because I am using my new SSD drive. Appreciate any insight...

omegaman7
10th September 2014, 19:15
Had a dvd encode recently take 6hrs using X264 frameserving. I usually use DGDecNV, but since I was watching some videos at the same time, I switched it. My CPU usage was averaging 22 - 30%. Not sure what could have caused this. Been pretty busy, so I haven't been able to post. I'll have to see if I can repeat this. Because my recent reorganizing has lost the information :p

JD, the HC encoder is used for DVD, eh? Is it 6 core capable?

I noticed the progress now shows pass 2 for DVD's. Is it possible that this change has caused the slowness?

Sharc
10th September 2014, 19:28
....normally say I have it set for High Quality 2 Pass and a few x264 tweaks; ....
....I am just curious since I happened inadvertently to use Directshow this time, with all other things being equal, why would it take so much longer .....

Did you parhaps make any changes to your "few x264 tweaks"; or setting QUALITY_ULTRA=..... ?

Capsbackup
10th September 2014, 22:04
I noticed this too a week or so back. ;)
This was the explanation.


I noticed the progress now shows pass 2 for DVD's. Is it possible that this change has caused the slowness?

It always did a 2 pass encode, I just changed the way it is presented to better reflect it. In previous versions the 2nd pass started at 50%...

omegaman7
10th September 2014, 23:01
I'm simply wondering if the code somehow had an adverse reaction ;) I suppose it would be quite a stretch. And I know damn near nothing about coding.

Lathe
10th September 2014, 23:09
Did you parhaps make any changes to your "few x264 tweaks"; or setting QUALITY_ULTRA=..... ?

Oh no, nothing like that; just what I always use when I want to fine tune an encode. Everything is the same that I usually do except that I unintentionally must have left the frame server as the default which I guess is Directshow.

I have about 4 more hours to go (I just got back from work) AND, I've had an unrelated issue for quite a while where my computer freezes for no apparent reason. So, I'm holding my breath and hoping that it gets through this unusual marathon encode for the next 4 hours :)