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

mmick
18th July 2014, 20:19
I am very pleased with AMD's CPUs. You get a lot of performance for a lot less money than Intel. If money or price/performance ratio isn't important, then Intel is ok. Also, can you imagine what Intel would be charging for their CPUs if AMD didn't exist as a competitor?

You´re right about competition, but AMD only plays cards on sub i5 chips unfortunately. In most european countries you can find Intel chips (not Haswell based) for a very good price, that already include a decent (for integrated gpus...) Intel HD 4000 with Quick sync. Before I just bought AMD, but now I was forced to go Intel on my Ultrabook, and it works too well to go AMD on a near future.

Nevertheless I have a question:
Are the latest Quick sync faster or slower (at a comparable quality) than the sibilings OpenCL on a Intel 4000/4400 comparable AMD/NVIDIA GPU?

I tested DVDFAB for example with Quick sync on my Haswell i5 (4200u with Intel 4400) and it was miles faster than using CUDA/OpenCL on my (much much faster on 3D) Geforce 730U (my ultrabook has 2 GPUs, intel and nvidia)

jdobbs
18th July 2014, 22:20
You´re right about competition, but AMD only plays cards on sub i5 chips unfortunately. In most european countries you can find Intel chips (not Haswell based) for a very good price, that already include a decent (for integrated gpus...) Intel HD 4000 with Quick sync. Before I just bought AMD, but now I was forced to go Intel on my Ultrabook, and it works too well to go AMD on a near future.

Nevertheless I have a question:
Are the latest Quick sync faster or slower (at a comparable quality) than the sibilings OpenCL on a Intel 4000/4400 comparable AMD/NVIDIA GPU?

I tested DVDFAB for example with Quick sync on my Haswell i5 (4200u with Intel 4400) and it was miles faster than using CUDA/OpenCL on my (much much faster on 3D) Geforce 730U (my ultrabook has 2 GPUs, intel and nvidia)Not sure what you mean by "sub i5" -- I'd consider my 8350 eight-core AMD processor superior to an i5.

Can't comment on Quick-Sync speeds compared to OpenCL -- I'll leave that for someone who's done some testing. Generally, though, I think the speeds I've seen reported from a compatible Quick-Sync card hard to beat for 3D.

jdobbs
18th July 2014, 23:40
I have updated the first post of this thread with a link to the most recent version of BD-RB (v0.47.07). Changes for this release:- Corrected an error that could prevent keeping
the original video in sources with multipart
playlists in a movie-only backup, even though
it will fit without reencoding.
- Added code to prefer 3D playlists over non-3D
playlists when selecting the default playlist
for movie-only encoding. Note: The selected
playlist can still be overridden using the
"Other Movie-Only Playlist" menu option.
- Made changes so that "ENCODER_MENU=1" actually
displays the encoder menu.
- Corrected a "PredictAndEncode() 00053 2806"
error when FRIMEncode is used while "Use x264
internal LAVF..." is selected.
- Added code to tell BD-RB to use the SSIF file
as the source for 3D encoding when the two
component M2TS files are not complete.
- Other minor corrections and cosmetic fixes.

HWK
19th July 2014, 00:05
Just trying with problematic source. (LEGO)

http://i59.tinypic.com/s1nsi8.jpg

Not an error, but shouldn't it say 00042.ssif instead of m2ts.

soneca
19th July 2014, 00:17
Many thanks jdobbs! :)
You got to check this (http://forum.doom9.org/showthread.php?p=1678732#post1678732) claim?

jdobbs
19th July 2014, 01:32
Many thanks jdobbs! :)
You got to check this (http://forum.doom9.org/showthread.php?p=1678732#post1678732) claim?Ughh... no.

jdobbs
19th July 2014, 01:32
Just trying with problematic source. (LEGO)

http://i59.tinypic.com/s1nsi8.jpg

Not an error, but shouldn't it say 00042.ssif instead of m2ts.Yeah, that's a cosmetic change I didn't consider. I'll get it in the next release.

Sharc
19th July 2014, 10:56
Is there any chance you may have exited and restarted? The problem with the edited changes and an ISO (or a direct read from a BD disc) is that the titles.inf file can't be saved to the source. So the changes are only good for as long as BD-RB is active. If you exit and reenter (or possibly if you run it as a BATCH job, I'll have to check that) the changes are lost.

I'll have to look and see if there is a way I can save it somewhere else for those kinds of sources. The problem is that there are few paths that are guaranteed to remain consistent between runs.
Thank you for the new release 0.47.07, jdobbs.
Did you have a chance to look into this? I still can't edit the Quick Menu's for .iso sources. Is there possibly a workaround?

mparade
19th July 2014, 16:44
I have updated the first post of this thread with a link to the most recent version of BD-RB (v0.47.07). Changes for this release:- Corrected an error that could prevent keeping
the original video in sources with multipart
playlists in a movie-only backup, even though
it will fit without reencoding.
- Added code to prefer 3D playlists over non-3D
playlists when selecting the default playlist
for movie-only encoding. Note: The selected
playlist can still be overridden using the
"Other Movie-Only Playlist" menu option.
- Made changes so that "ENCODER_MENU=1" actually
displays the encoder menu.
- Corrected a "PredictAndEncode() 00053 2806"
error when FRIMEncode is used while "Use x264
internal LAVF..." is selected.
- Added code to tell BD-RB to use the SSIF file
as the source for 3D encoding when the two
component M2TS files are not complete.
- Other minor corrections and cosmetic fixes.

Nice job, thank you very much!

mmick
19th July 2014, 16:49
I have updated the first post of this thread with a link to the most recent version of BD-RB (v0.47.07).

Thank you very much! You´ll be the king of Game of Thrones :-D

Not sure what you mean by "sub i5" -- I'd consider my 8350 eight-core AMD processor superior to an i5

Your CPU is an AMD´s beast, 8 cores and very high frequency, naturally on very well multithreaded code it has a big advantage.

Of course your AMD (162 Euros) holds well vs. i5 3570k (210 euros), but the i5 takes frequently the lead, it really depends what you use more:
http://www.tomshardware.com/reviews/far-cry-3-performance-benchmark,3379-7.html

http://www.anandtech.com/bench/Product/697?vs=701

Despite of that, I´m just saying AMD just can´t fight newer i5 - i7 (250€ or more chips), and they need to come up with a new CPU design that consumes a lot less, lower frequencies, and better performance.

Other than that, we have a choice, things have turned up REALLY well (and fast) on the transcoding community: transcoding using Quicksync/OpenCL allows over 110 fps on general "CPUs" (using the GPU).

When I encode SW mode: 8-12 fps, CPU 100%, FAN on
When I encode HW mode: 110-120 fps, CPU 10% and FAN...off. :eek:

Many thanks jdobbs! :)
You got to check this (http://forum.doom9.org/showthread.php?p=1678732#post1678732) claim?

I hope you find a solution for the omnipresent FRIM "HW" issue... I tested another movie, and the same compression issues. I suspect soneca´s issue is the same I have, or at least FRIM has issues with Intel HD 4x00 series´ Quick sync.

omegaman7
19th July 2014, 16:54
Careful about the intel vs Amd arguments ;) There are fans from each side of CPU pool in this forum.

Jdobbs, I have a lucrative job coming up, and will likely be able to make a good donation soon :) Really appreciate your efforts.

mmick
19th July 2014, 17:15
Careful about the intel vs Amd arguments ;) There are fans from each side of CPU pool in this forum.

:D no problem, I am an objective guy: I look at performance/money, and of course what suits me best. I don´t care if it´s called AMD or Intel. I already had (a looooong time ago) even a Cyrix CPU :eek:

jdobbs
19th July 2014, 21:30
Of course your AMD (162 Euros) holds well vs. i5 3570k (210 euros), You can get an AMD FX-8350 for around 130 euros almost everywhere (Amazon, Newegg). It also beats the i5 in almost every meaningful category (http://versus.com/en/amd-fx-8350-black-edition-vs-intel-core-i5-4670k) for significantly less money (I bought mine 1 1/2 years ago for $179, when the i5 was even higher than now) -- and because of the 8 true cores it widens the gap even further when you use the BD-RB multiprocessing setting. In fact, most of the i5's strong points are due to the integrated video. In benchmarking CPUs (http://www.cpubenchmark.net/cpu_lookup.php?cpu=AMD+FX-8350+Eight-Core) you have to go quite a way down the list below an FX-8350 before you hit your first i5. You'll also note that in pass 2 of an X264 encode, where BD-RB spends most of its time, your referenced link (http://www.anandtech.com/bench/Product/697?vs=701) shows the AMD over 43% faster than the i5 -- and video processing is what I use it for. That seems to be a slam dunk to me.

For 3D I would guess that the intel's quick-sync video capability would put it clearly out in front. And, of course, if you really want fast, an i7 is by far the best choice -- as long as you don't mind the sticker shock.

HWK
19th July 2014, 22:24
... if you really want fast, an i7 is by far the best choice -- as long as you don't mind the sticker shock.

I agree, when I bought cpu chip it was close to $600 and no it didn't include fan. After monitor it was most expensive thing I brought.

jdobbs
20th July 2014, 00:29
Thank you for the new release 0.47.07, jdobbs.
Did you have a chance to look into this? I still can't edit the Quick Menu's for .iso sources. Is there possibly a workaround?Not at all, or just when you exit and reenter?

jdobbs
20th July 2014, 01:24
Thank you for the new release 0.47.07, jdobbs.
Did you have a chance to look into this? I still can't edit the Quick Menu's for .iso sources. Is there possibly a workaround?I found what was causing it and it has been fixed for the next release. It was losing it every time whether you exited or not. Now it will remain current until you exit BD-RB or take an action that forces a disc scan.

Sharc
20th July 2014, 08:28
I found what was causing it and it has been fixed for the next release. It was losing it every time whether you exited or not. Now it will remain current until you exit BD-RB or take an action that forces a disc scan.
Great, thank you. :)

worknstiff
20th July 2014, 19:31
@ jdobbs RE:I have updated the first post of this thread with a link to the most recent version of BD-RB (v0.47.07).

Hey thanks man, I just finished making a backup of Lego 3D that had stopped me cold and it now works perfectly. I am amazed how you can find and fix the problems we toss at you. You never fail to figure it out and then quickly put up a new version that fixes it. Many BIG THANKS for how much BD Rebuilder has grown over the past few years. I wish I could have this great experience with all the other software I use, lol.

jdobbs
20th July 2014, 19:49
@ jdobbs RE:I have updated the first post of this thread with a link to the most recent version of BD-RB (v0.47.07).

Hey thanks man, I just finished making a backup of Lego 3D that had stopped me cold and it now works perfectly. I am amazed how you can find and fix the problems we toss at you. You never fail to figure it out and then quickly put up a new version that fixes it. Many BIG THANKS for how much BD Rebuilder has grown over the past few years. I wish I could have this great experience with all the other software I use, lol.Your comments are deeply appreciated.

Sharc
20th July 2014, 21:00
When I import a 1440x1080i file from my videocam it seems that BD-RB always adds padding pillows to make it 1920x1080. This seems unnecessary as 1440x1080 with --sar 4:3 is blu-ray compliant.
The workaround which I found is to edit the Pinfo.inf in the Pseudo folder to skip adding these boders.
Or do I miss something in the settings?

Added:
Could .mts be added to the video file import list? (Now I have always to rename the .mts to .m2ts)

DarWun
21st July 2014, 02:36
What has changed since February 2014 and now with respect to 3D Movie Only processing? I have a number of 3D Movie Only disks that I processed back in February. They play fine on my PS3. I did three 3D Movie only conversions over the past weekend, and none of them played. I then processed a couple of disks that I had previously had success with as Movie Only 3D backups, and they did not play on the PS3 either. I ripped one of the Movie Only 3D disks that had previously worked and burned it to a new BD-R. It played on the PS3. I did full disk conversions of the same 3D Bluray. It played on the PS3 as well. I only seem to be having a problem with the Movie Only conversions using recent versions of BD-Rebuilder.

This is my Inspect log using the most recent version of BD-Rebuilder:

[07-20-14] Checking System Settings
- BD-Rebuilder v0.47.07 (beta)
- Windows Version: 6.2 [9200]
- Working Path Free Space: 1,635.37GB
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4504, Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[07-20-14] Systems Settings Check complete

jdobbs
21st July 2014, 02:49
When I import a 1440x1080i file from my videocam it seems that BD-RB always adds padding pillows to make it 1920x1080. This seems unnecessary as 1440x1080 with --sar 4:3 is blu-ray compliant.
The workaround which I found is to edit the Pinfo.inf in the Pseudo folder to skip adding these boders.
Or do I miss something in the settings?

Added:
Could .mts be added to the video file import list? (Now I have always to rename the .mts to .m2ts)It isn't blu-ray compliant. 1440x1080 is allowed but it is interpolated to 1920x1080 -- and can only be 16:9.

Your player may play it if you force it into a BD structure... but that doesn't mean it is compliant, it just means you got lucky.

jdobbs
21st July 2014, 02:55
What has changed since February 2014 and now with respect to 3D Movie Only processing? I have a number of 3D Movie Only disks that I processed back in February. They play fine on my PS3. I did three 3D Movie only conversions over the past weekend, and none of them played. I then processed a couple of disks that I had previously had success with as Movie Only 3D backups, and they did not play on the PS3 either. I ripped one of the Movie Only 3D disks that had previously worked and burned it to a new BD-R. It played on the PS3. I did full disk conversions of the same 3D Bluray. It played on the PS3 as well. I only seem to be having a problem with the Movie Only conversions using recent versions of BD-Rebuilder.

This is my Inspect log using the most recent version of BD-Rebuilder:

[07-20-14] Checking System Settings
- BD-Rebuilder v0.47.07 (beta)
- Windows Version: 6.2 [9200]
- Working Path Free Space: 1,635.37GB
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4504, Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[07-20-14] Systems Settings Check completeThere's no difference in the way BD-RB structures the 3D in a movie-only and full backup. BD-RB's output is 100% BD-3D compliant, which would lead me to believe the issue is either in your settings or (more likely) in the PS3.

Just as a test you might try this for movie-only:

OUTPUT_3D_ISO=1

Then burn your ISO output to a disc. That way you can get a structure with the SSIF folder for movie-only encodes (only) which might make it easier to recognize on players that aren't "really" BD players (like the PS3).

Sharc
21st July 2014, 08:15
It isn't blu-ray compliant. 1480x1080 is allowed but it is interpolated to 1920x1080 -- and can only be 16:9.

Your player may play it if you force it into a BD structure... but that doesn't mean it is compliant, it just means you got lucky.
Hmmm.... how comes that it is "allowed but non-compliant"? I thought that 1440x1080 encoded with --sar 4:3 gets always displayed as 16:9 (stretched) as per the blu-ray 2D standard and hence it will be played back correctly by all blu-ray-logo players. It is the "anamorph version of 2D blu-ray" so to speak. I might be wrong though.
Does this also mean the the setting "Resize 1920x1080 to 1440x1080" produces non-compliant backups? In the few cases I have tested on various blu-ray standalones I never had problems with this format, which accepts interlaced for 25 and 29.97fps as a salient feature. (My SONY videocam produces 1440x1080i 25fps btw.).

With the current addition of left and right borders by BD-RB for padding to 1920 the standalone adds top and botton borders for playback in order to display the clip undistorted. This means that I get a small active picture with large borders on all sides on the TV screen which cannot be zoomed to full screen.
1440x1080 encoded with --sar 4:3 would however get correctly stretched to 16:9 full screen without any borders.

Don't get me wrong, I don't want to argue, I am just wondering how to do it right (or wrong) with the formats. My present simple workaround is to edit (remove) the addition of borders in the Pinfo.ini.

DarWun
21st July 2014, 14:17
Just as a test you might try this for movie-only:

OUTPUT_3D_ISO=1

Then burn your ISO output to a disc. That way you can get a structure with the SSIF folder for movie-only encodes (only) which might make it easier to recognize on players that aren't "really" BD players (like the PS3).

Thanks jdobbs. That should fix the problem. I went back through the forums, and found that the changelog for BD-RB ver 47.02 mentions the OUTPUT_3D_ISO hidden option. The log also mentions that the SSIF folder was no longer required -- the method is 100% compliant with the BD standard. I suspect that the PS3 views things differently (as usual).

Anyway, I added that hidden option to the configuration file and ran a Movie Only 3D rebuild to BD25 overnight. I suspect that the disk will work in the PS3 once I burn it. I'll post back after work tonight to confirm.

jdobbs
21st July 2014, 15:22
Hmmm.... how comes that it is "allowed but non-compliant"? I thought that 1440x1080 encoded with --sar 4:3 gets always displayed as 16:9 (stretched) as per the blu-ray 2D standard and hence it will be played back correctly by all blu-ray-logo players. It is the "anamorph version of 2D blu-ray" so to speak. I might be wrong though.
Does this also mean the the setting "Resize 1920x1080 to 1440x1080" produces non-compliant backups? In the few cases I have tested on various blu-ray standalones I never had problems with this format, which accepts interlaced for 25 and 29.97fps as a salient feature. (My SONY videocam produces 1440x1080i 25fps btw.).

With the current addition of left and right borders by BD-RB for padding to 1920 the standalone adds top and botton borders for playback in order to display the clip undistorted. This means that I get a small active picture with large borders on all sides on the TV screen which cannot be zoomed to full screen.
1440x1080 encoded with --sar 4:3 would however get correctly stretched to 16:9 full screen without any borders.

Don't get me wrong, I don't want to argue, I am just wondering how to do it right (or wrong) with the formats. My present simple workaround is to edit (remove) the addition of borders in the Pinfo.ini.I may have misunderstood.

If your source is 1440x1080 -- but it is meant to be displayed at 16:9 then it doesn't need the borders. If it is meant to be displayed as 4:3, then it is does. 1440x1080 sources, by the standard, are run through a 4/3 interpolation filter (making it 16:9 @ 1920x1080 when presented to the video plane). The standard never mentions any action related to the source's SAR (at least not that I can find), it only deals with display aspect ratios.

The problem is that people like to strip off the black borders when they create a standalone video file (MKV, MP4, etc). So movies like "The Wizard of Oz", or any other classic that was filmed in 4:3 that is converted to BD, is still 1:1 at 1440x1080 -- while a 1440x1080 anamorphic source is pretty rare. So I made the import function assume it needs the black borders.

From what you just said, I assume that your camera records the source at 1440x1080 anamorphic. I guess I wasn't aware that was commonly available. I'll have to modify the code to correct for that. I'll also have to adjust for the 1080i, which needs the two fields resized separately.

jdobbs
21st July 2014, 15:59
Thanks jdobbs. That should fix the problem. I went back through the forums, and found that the changelog for BD-RB ver 47.02 mentions the OUTPUT_3D_ISO hidden option. The log also mentions that the SSIF folder was no longer required -- the method is 100% compliant with the BD standard. I suspect that the PS3 views things differently (as usual).

Anyway, I added that hidden option to the configuration file and ran a Movie Only 3D rebuild to BD25 overnight. I suspect that the disk will work in the PS3 once I burn it. I'll post back after work tonight to confirm.I had to select the in-mux format as the default when I added support for full-backups, because TSMUXER can only create an ISO for a movie-only format. Without the ISO output you'd have to half the encoding rate to account for the redundancy of the SSIF file. The in-mux format used to eliminate the need for a SSIF is 100% BD compatible, but the PS3 apparently doesn't know how to handle it. That's interesting, since commercial discs use it as well (e.g. AVATAR).

Sharc
21st July 2014, 18:38
I may have misunderstood.

If your source is 1440x1080 -- but it is meant to be displayed at 16:9 then it doesn't need the borders. If it is meant to be displayed as 4:3, then it is does. 1440x1080 sources, by the standard, are run through a 4/3 interpolation filter (making it 16:9 @ 1920x1080 when presented to the video plane). The standard never mentions any action related to the source's SAR (at least not that I can find), it only deals with display aspect ratios.

The problem is that people like to strip off the black borders when they create a standalone video file (MKV, MP4, etc). So movies like "The Wizard of Oz", or any other classic that was filmed in 4:3 that is converted to BD, is still 1:1 at 1440x1080 -- while a 1440x1080 anamorphic source is pretty rare. So I made the import function assume it needs the black borders.

From what you just said, I assume that your camera records the source at 1440x1080 anamorphic. I guess I wasn't aware that was commonly available. I'll have to modify the code to correct for that. I'll also have to adjust for the 1080i, which needs the two fields resized separately.
Yes, this is exactly my case. I was indeed surprised myself to find the camera shooting at 1440x1080i25 anamorph. Well, it is a compact photo camera with a video option.
From MediaInfo:
Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.0
Format settings, CABAC : Yes
Format settings, ReFrames : 2 frames
Format settings, GOP : M=2, N=13
Codec ID : 27
Duration : 7s 720ms
Bit rate mode : variable
Bit rate : 10,4 Mbps
Maximum bit rate : 16,0 Mbps
Width : 1 440 Pixel
Height : 1 080 Pixel
Display aspect ratio : 16:9
Frame rate : 25,000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : top field first
Bits/(Pixel*Frame) : 0.268
Stream size : 9,59 MiB (93%)

Off the records: I made good experience with bob-deinterlacing (double rate) and resizing these videos to 1280x720p50. The benefit of keeping the temporal resolution of the hand-held (shaky) video clearly outweights the bob shimmer -- which is hardly noticeable.

Anyway, I recall that the original idea and application for DB-RB was backing up blu-ray disks .... :D
I certainly don't mind if you would skip above modifications for such rare cases.

Added:
... The standard never mentions any action related to the source's SAR (at least not that I can find), it only deals with display aspect ratios.
Yes you are right, for blu-ray authored material the SAR of the .m2ts seems to have no effect. However I noticed when the .m2ts files are directly played via my standalone the SAR overrides the DAR. This also means when the --sar for encoding does not match the pixel aspect ratio of the original, the picture will be distorted. Fortunately its 1:1 in most cases.

DarWun
22nd July 2014, 00:02
I had to select the in-mux format as the default when I added support for full-backups, because TSMUXER can only create an ISO for a movie-only format. Without the ISO output you'd have to half the encoding rate to account for the redundancy of the SSIF file. The in-mux format used to eliminate the need for a SSIF is 100% BD compatible, but the PS3 apparently doesn't know how to handle it. That's interesting, since commercial discs use it as well (e.g. AVATAR).

I can confirm that with OUTPUT_3D_ISO set to 1, the resultant 3D Movie Only BD25 disk works on the PS3. So problem solved. Thanks for your help.

I wanted to check one more thing based on your response to my previous post. The PS3 plays a BD25 Full 3D Disk Backup created using the most recent version of BD-RB without issue. Doesn't this indicate that the PS3 can handle the in-mux format? If it can handle it for a full disk backup, why wouldn't it be able to handle it for a movie only backup?

jdobbs
22nd July 2014, 05:00
I can confirm that with OUTPUT_3D_ISO set to 1, the resultant 3D Movie Only BD25 disk works on the PS3. So problem solved. Thanks for your help.

I wanted to check one more thing based on your response to my previous post. The PS3 plays a BD25 Full 3D Disk Backup created using the most recent version of BD-RB without issue. Doesn't this indicate that the PS3 can handle the in-mux format? If it can handle it for a full disk backup, why wouldn't it be able to handle it for a movie only backup?Yes, a full backup would use in-mux. I've no idea why it wouldn't be able to handle it in a movie-only backup. I would suspect it may be something odd in your settings.

andref4
22nd July 2014, 18:53
Downloaded bd-rb 0.47.07 and will try to make a full backup of Cloudy with a Chance of Meatballs 2 3D (ger BD). Hope that the movie will not crash after 7:30 mins. playing as before. I will post here tomorrow. 3D Encoding takes a while with Frimcode and no Intel GPU.

Lathe
22nd July 2014, 22:42
[Edit] Hmm... the confirmation message from Amazon says "Prime Two-day shipping" -- and then estimates Friday, July 11th for delivery. Is it me, or does 11-7=2 now? It's been a while since I was in school. I have to admit I haven't been keeping up with "new math".

Heh, I'm kind of behind in reading these posts (I wasn't notified for some odd reason - so, I thought I would throw in a comment here about Amazon Prime shipping, and also HOPEFULLY re-subscribe to the thread and subsequently get notified of new posts)

I've had an Amazon Prime membership for a few years. On occasion, if a 3rd party is providing an item, although it is offered as a Prime item, the other company may take longer to process the order. But, then after whatever time it takes them, THEN the actual shipping only takes 2 days :)

andref4
23rd July 2014, 13:20
I give it up with Cloudy 2 3D.

Same error as before and muxing stops. See log. Only thing that works ist a movie only backup or a full 3D SBS backup but not a normal full 3D backup. If I mount the Cloudy 2 3D iso I bacame the error you see in the log. If I copy the complete movie to a Folder (over 60GB because ssif) encoding finishes but the movie crashes on playing at 7:20, 7:30 minutes watching.

----------------------
[07.22.14] BD Rebuilder v0.47.07 (beta)
[19:57:36] Source: CLOUDY_2
- Input BD size: 31,57 GB
- Approximate total content: [02:05:56.170]
- Target BD size: 22,95 GB
- Windows Version: 6.1 [7601]
- Quality: Good (Very Fast), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[19:57:36] PHASE ONE, Encoding
- [19:57:36] Processing: VID_00102 (1 of 5)
- [19:57:36] Extracting A/V streams [VID_00102]
- [19:57:48] Reencoding video [VID_00102]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 6.887 frames
- Bitrate: 5.999 Kbs
- [19:57:49] Reencoding: VID_00102, Pass 1 of 1
- [19:59:35] Video Encode complete
- [19:59:35] Processing audio tracks
- [19:59:35] Multiplexing M2TS
- [19:59:43] Processing: VID_00341 (2 of 5)
- [19:59:43] Extracting A/V streams [VID_00341]
- [19:59:53] Reencoding video [VID_00341]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 2.051 frames
- Bitrate: 17.094 Kbs
- Using FRIMEncoder for MVC encoding
- [19:59:53] Reencoding: VID_00341, Pass 1 of 1
- [20:07:24] Video Encode complete
- [20:07:24] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [20:07:24] Multiplexing M2TS
- [20:07:30] Scanning for 3D CLPI info...
- [20:07:33] Processing: VID_00344 (3 of 5)
- [20:07:33] Extracting A/V streams [VID_00344]
- [20:08:33] Reencoding video [VID_00344]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 10.903 frames
- Bitrate: 25.167 Kbs
- Using FRIMEncoder for MVC encoding
- [20:08:33] Reencoding: VID_00344, Pass 1 of 1
- [20:48:17] Video Encode complete
- [20:48:17] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (deu): Keeping original audio
- Track 4355 (eng): Keeping original audio
- [20:48:18] Multiplexing M2TS
- [20:49:10] Scanning for 3D CLPI info...
- [20:49:41] Processing: VID_00345 (4 of 5)
- [20:49:41] Extracting A/V streams [VID_00345]
- [20:49:47] Reencoding video [VID_00345]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 425 frames
- Bitrate: 22.232 Kbs
- Using FRIMEncoder for MVC encoding
- [20:49:47] Reencoding: VID_00345, Pass 1 of 1
- [20:51:22] Video Encode complete
- [20:51:22] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (deu): Keeping original audio
- Track 4355 (eng): Keeping original audio
- [20:51:22] Multiplexing M2TS
- [20:51:28] Scanning for 3D CLPI info...
- [20:51:29] Processing: VID_00346 (5 of 5)
- [20:51:29] Extracting A/V streams [VID_00346]
- [21:02:16] Reencoding video [VID_00346]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 125.112 frames
- Bitrate: 24.366 Kbs
- Using FRIMEncoder for MVC encoding
- [21:02:16] Reencoding: VID_00346, Pass 1 of 1
- [04:36:32] Video Encode complete
- [04:36:33] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (deu): Keeping original audio
- Track 4355 (eng): Keeping original audio
- [04:36:33] Multiplexing M2TS
- [04:54:27] Scanning for 3D CLPI info...
[05:06:58]PHASE ONE complete
[05:06:58]PHASE TWO - Rebuild Started
- [05:06:58] Converting SSIF file references
- ERROR: 3D remuxing failed. Aborted.
- Failed to rebuild BD file(s). Aborted.

jdobbs
23rd July 2014, 14:17
@andref4

I'll do some research and, short of buying the disc, I'll see what I can do. My donations are at an all-time low -- and I just can't afford to buy discs for testing anymore. In fact, if things don't change I may be forced to abandon the project in the near future.

I'm guessing it might have something to do with the fact that it is both multipart and has undersized M2TS files.

mmick
23rd July 2014, 18:56
My donations are at an all-time low

I´ve just made a Donation, you deserve it :p

I hope we´ll get a new Intel Quick sync "home made" encoder :-)

jdobbs
23rd July 2014, 19:18
@andref4

I'll do some research and, short of buying the disc, I'll see what I can do. My donations are at an all-time low -- and I just can't afford to buy discs for testing anymore. In fact, if things don't change I may be forced to abandon the project in the near future.

I'm guessing it might have something to do with the fact that it is both multipart and has undersized M2TS files.Well, that wasn't it. I just forced BD-RB to use the SSIF on another multipart title -- and it worked fine.

jdobbs
23rd July 2014, 19:23
I´ve just made a Donation, you deserve it :p

I hope we´ll get a new Intel Quick sync "home made" encoder :-)I appreciated it, thanks.

I don't want to give the impression to the people here on DOOM9 that I'm putting the squeeze on them. Pretty much everyone here has already contributed either through supporting the forum's questions and bug-reports -- or through PayPal. The problem is the many, many thousands of others who use it regularly, and don't contribute at all.

meadrocks
23rd July 2014, 19:24
@andref4

My donations are at an all-time low -- .


Donation completed.

omegaman7
23rd July 2014, 19:26
I appreciated it, thanks.

I don't want to give the impression to the people here on DOOM9 that I'm putting the squeeze on them. Pretty much everyone here has already contributed either through supporting the forum's questions and bug-reports -- or through PayPal. The problem is the many, many thousands of others who use it regularly, and don't contribute at all.

What's sad is, most of us can afford 1 - $5. If all of us were to give you at least that, you'd be very well off ;) I feel very guilty giving such a small amount. But If others were to, I'd be onboard. In any case, this week I should be able to make a substantial donation. At the very least, you could buy a couple movies for testing.

jdobbs
23rd July 2014, 20:07
@andref4

Ok. I can't find anything that could be the issue, and some folks have been kind enough to donate after my post, so I've ordered "Cloudy With A Chance of Meatballs 2 3D" for testing.

omegaman7
23rd July 2014, 22:09
I'm afraid I can't comment on Cloudy 2. I did a 1 : 1 backup, though I replaced the audio track with the one from the DVD ;) Gotta love those multi-packs!

HWK
23rd July 2014, 22:58
@andref4

Ok. I can't find anything that could be the issue, and some folks have been kind enough to donate after my post, so I've ordered "Cloudy With A Chance of Meatballs 2 3D" for testing.

I'm afraid I can't comment on Cloudy 2. I did a 1 : 1 backup, though I replaced the audio track with the one from the DVD ;) Gotta love those multi-packs!

I also performed compression while back, and it worked.

@ Jdobbs, I can rerun if necessary for testing.

jdobbs
23rd July 2014, 23:40
@andref4

Could you post your settings (the contents of BDREBUILDER.INI) at the time the job fails? That way I (and HWK) can try to reproduce the problem you reported.

dfemia01
24th July 2014, 01:51
I'm looking for some help using the IMPORT_PAL_TO_FILM switch. BluRay is Disc 1 (UK, Region B) of Mrs Brown's Boys, Series 1. I've ripped all of the discs but to play them I need to re-encode from 25fps to 23.976 for North America/Canada. I can downsize without issues but it's not doing the frame rate conversion. Here's the INI file ...

[Options]
VERSION=0.47.0.7
MODE=0
MULTIPROCESS=1
FORCE_ENCODE=1
ENCODE_QUALITY=0
ONEPASS_ENCODING=2
AUTO_QUALITY=1
TARGET_SIZE=23500
PRIORITY_CLASS=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
IMPORT_PAL_TO_FILM=1
DEINTERLACE=1
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=0
AVCHD=1
REMOVE_WORKFILES=1
MOVIE_ONLY_LOOP=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
UNMASK_CHAPTER=1
COMPLETION_BEEP=0
DGDECNV=0
OUTPUT_3D=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23500
AUTO_BURN=2
MOVIEONLY_TYPE=0
ALTCRF=20
ALT_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
QUICK_EXTRAS=1
ENCODER=0
SHUTDOWN_SLEEP=1
[Paths]
SOURCE_PATH=E:\BLURAY\MRS BROWN'S BOYS\S1D1\U5_8285950\
WORKING_PATH=E:\BLURAY\MRS BROWN'S BOYS\S1D1\

I'm probably just missing something stupid with this but so far I haven't found anything in other posts. I'd appreciate any suggestions etc.

Dave

Lathe
24th July 2014, 03:35
What's sad is, most of us can afford 1 - $5. If all of us were to give you at least that, you'd be very well off ;) I feel very guilty giving such a small amount. But If others were to, I'd be onboard. In any case, this week I should be able to make a substantial donation. At the very least, you could buy a couple movies for testing.

Yeah, you do make a good point mate; I was just getting ready about a month ago to send a moderately decent donation, but then I was given an 'enforced holiday' from Doom9 for about a month (I'm still not quite clear as to why exactly, but I'll certainly try not to repeat the experiment :) )

Anyway, I really was not in the contributing mood for a while, but you are right Omegaman, we should ALL really be sending at least a little something more often.

I just sent a small donation, and I'm hoping that more will follow soon. Thanks kindly Mr. JDobbs for your consistent hard work and for an unquestionably excellent program!

andref4
25th July 2014, 01:25
@andref4

Could you post your settings (the contents of BDREBUILDER.INI) at the time the job fails? That way I (and HWK) can try to reproduce the problem you reported.

tomorrow... I must reencode Cloudy 2 3D and that does takes some time.
The german Cloudy 2 3D BD has Multi Angel and Cinavia protection. I dont know if the US BD has Multi Angel and Cinavia too.

Ch3vr0n
25th July 2014, 02:07
cinavia is irrelevant. BDRB doesnt remove it.

andref4
25th July 2014, 11:09
jea, cinavia is a "watermark" on audio track thats right. So here is the bdrebuilder.ini and new log:

ini:
[Options]
VERSION=0.47.0.7
ENCODER=0
MODE=0
ENCODE_QUALITY=0
ONEPASS_ENCODING=2
AUTO_QUALITY=1
TARGET_SIZE=23500
AUTO_BURN=2
AUDIO_TO_KEEP=deu;eng;ger;
SUBS_TO_KEEP=all
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=1
REMOVE_WORKFILES=0
DGDECIM=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
DGDECNV=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23500
[Paths]
WORKING_PATH=C:\BD_REBUILDER\MOVIE\
SOURCE_PATH=H:\


log:
----------------------
[07.25.14] BD Rebuilder v0.47.07 (beta)
[02:47:54] Source: CLOUDY_2
- Input BD size: 31,57 GB
- Approximate total content: [02:05:56.170]
- Target BD size: 22,95 GB
- Windows Version: 6.1 [7601]
- Quality: Good (Very Fast), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[02:47:54] PHASE ONE, Encoding
- [02:47:54] Processing: VID_00102 (1 of 5)
- [02:47:54] Extracting A/V streams [VID_00102]
- [02:48:08] Reencoding video [VID_00102]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 6.887 frames
- Bitrate: 5.999 Kbs
- [02:48:08] Reencoding: VID_00102, Pass 1 of 1
- [02:49:51] Video Encode complete
- [02:49:51] Processing audio tracks
- [02:49:51] Multiplexing M2TS
- [02:49:59] Processing: VID_00341 (2 of 5)
- [02:50:00] Extracting A/V streams [VID_00341]
- [02:50:14] Reencoding video [VID_00341]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 2.051 frames
- Bitrate: 17.094 Kbs
- Using FRIMEncoder for MVC encoding
- [02:50:14] Reencoding: VID_00341, Pass 1 of 1
- [02:57:43] Video Encode complete
- [02:57:43] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [02:57:43] Multiplexing M2TS
- [02:57:57] Scanning for 3D CLPI info...
- [02:58:01] Processing: VID_00344 (3 of 5)
- [02:58:01] Extracting A/V streams [VID_00344]
- [02:59:02] Reencoding video [VID_00344]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 10.903 frames
- Bitrate: 25.167 Kbs
- Using FRIMEncoder for MVC encoding
- [02:59:02] Reencoding: VID_00344, Pass 1 of 1
- [03:38:24] Video Encode complete
- [03:38:24] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (deu): Keeping original audio
- Track 4355 (eng): Keeping original audio
- [03:38:24] Multiplexing M2TS
- [03:39:44] Scanning for 3D CLPI info...
- [03:40:21] Processing: VID_00345 (4 of 5)
- [03:40:21] Extracting A/V streams [VID_00345]
- [03:40:27] Reencoding video [VID_00345]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 425 frames
- Bitrate: 22.232 Kbs
- Using FRIMEncoder for MVC encoding
- [03:40:27] Reencoding: VID_00345, Pass 1 of 1
- [03:42:03] Video Encode complete
- [03:42:03] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (deu): Keeping original audio
- Track 4355 (eng): Keeping original audio
- [03:42:03] Multiplexing M2TS
- [03:42:09] Scanning for 3D CLPI info...
- [03:42:10] Processing: VID_00346 (5 of 5)
- [03:42:10] Extracting A/V streams [VID_00346]
- [03:52:59] Reencoding video [VID_00346]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 125.112 frames
- Bitrate: 24.366 Kbs
- Using FRIMEncoder for MVC encoding
- [03:52:59] Reencoding: VID_00346, Pass 1 of 1
- [11:22:54] Video Encode complete
- [11:22:54] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (deu): Keeping original audio
- Track 4355 (eng): Keeping original audio
- [11:22:54] Multiplexing M2TS
- [11:39:02] Scanning for 3D CLPI info...
[11:45:33]PHASE ONE complete
[11:45:33]PHASE TWO - Rebuild Started
- [11:45:33] Converting SSIF file references
- ERROR: 3D remuxing failed. Aborted.
- Failed to rebuild BD file(s). Aborted.

jdobbs
25th July 2014, 22:50
Downloaded bd-rb 0.47.07 and will try to make a full backup of Cloudy with a Chance of Meatballs 2 3D (ger BD). Hope that the movie will not crash after 7:30 mins. playing as before. I will post here tomorrow. 3D Encoding takes a while with Frimcode and no Intel GPU.Just to be clear... are you saying it stops at 7:30 mins because of Cinavia?

If so, there's nothing I can do about that. Removal of protection mechanisms is something BD-RB won't do.

Patrick
25th July 2014, 23:46
Hi jdobbs,

using your grand software on a regular basis (even though I could use the DVDfab internal tools), I believe it would be a shame if the project was to die for lack of appreciation...so hopefully donations will pick up again. My share is on its way.
Anyway, have you ever considered making updates available only to those who have actually donated? I mean, like with DVD Rebuilder Pro? That might keep the "leeches" at bay and the project alive for those who have learned to appreciate it? Just a thought...:thanks: