BD Rebuilder Beta - Bug Reports Only

[jdobbs]

Originally Posted by DMagic1

I did the project again with no overclock and the glitch is in the same exact spot.

If it was something with my system it would seem that the glitch would be in different locations in the video not at the same exact spot right?

This makes 4 times running it and its always at the same location.

I'll check into the chkdsk.

Or it's possible it could be fed a bad frame at that location...

[jdobbs]

I have updated the first post of this thread with a link to the latest release of BD-RB (v0.38.04). Changes for this version:

- Corrected an issue in which end-times might be
  incorrectly updated in an MPLS file for cases
  where partial CLPI/M2TS playback is referenced.
- Added code to handle non-standard 1080p/25 and
  1080p/29.97 sources and use "--fake-interlaced"
  in the command line to make them compliant.
- Added a hidden option "CHECK_FFDSHOW".  If set
  to "0" BD-RB will continue running even if no
  version of FFDSHOW is found.  Anyone using this
  option must ensure appropriate alternate CODECs
  are installed, and bug reports will not be
  accepted when FFDSHOW has not been installed.
- Changed routines so that UNC pathnames can be
  used as a source (should make use with NAS and
  other network units more compatible).
- Added an additional quality setting for hidden
  AUTO_BIAS.  Setting AUTO_BIAS=3, gives bias for
  even higher quality settings (lower speed) when
  "Automatic Quality Settings" is selected.  See
  HIDDENOPTS.TXT for more details on AUTO_BIAS.
- Changed the default values so that DTS and AC3
  are kept in their original format rather than
  being reencoding.  That choice can be changed
  via the SETUP dialog.
- Completed testing on FFDSHOW rev 3882 and HAALI
  Mediasplitter version 1.11.96.14.  These are now
  the recommended versions of these helper apps
  and can be downloaded from jdobbs.net.  They are
  also now linked in the first post of the DOOM9 
  bug reporting thread.
- Made improvements that should improve accuracy
  of sizing.
- Updated the included version of X264.EXE to the
  latest release (r2008).
- Updated the included version of X264-64.EXE to 
  the latest release (r2008).
- Other minor corrections and cosmetic fixes.

[berndy2001]

- Updated the included version of X264-64.EXE to the latest release (r2008).

I have a Question: I´m using win7 64bit. How can I use the 64bit edition of x264? Just rename it to X264.EXE? Or is there a switch i haven´t found yet?

[jdobbs]

Originally Posted by berndy2001

I have a Question: I´m using win7 64bit. How can I use the 64bit edition of x264? Just rename it to X264.EXE? Or is there a switch i haven´t found yet?

No. Doing so will cause BD-RB to fail.

There are only certain circumstances in which the 64 bit version can be used. If you set "Use X264's internal LAVF for decoding" in the SETUP dialog the 64 bit version will be used whenever it is possible.

This tells BD-RB to use the internal decoders in X264 (LAVF), making use of the X264 64 bit version possible. You don't have to rename anything, BD-RB knows if you are on a 64 bit system. Note, however, that lots of things will make BD-RB revert to 32 bit automatically (like resizing, using filters, etc.). When USE_LAVF is asserted and is in effect, FFDSHOW, AVISYNTH, and HAALI are not used for decoding.

Do some testing... sometimes the 32 bit version along with the helper apps can be faster, even on a 64 bit system.

[Capsbackup]

Will this change be used for AVCHD, full backups to BD5/9?
- Changed the default values so that DTS and AC3
are kept in their original format rather than
being reencoding. That choice can be changed
via the SETUP dialog.

[laserfan]

Originally Posted by PurpleMan

I would suggest opening the corresponding AVS in the WORKFILES folder (VID_XXXX.avs) in VirtualDub or another editing program, then scroll to the location where the glitch occurs and look if you see it there as well.

If you do, it means that the glitch is being frameserved to the encoder, in which case it's not BD-RB's fault but rather the decoder your system is using. If it's indeed the correct version of ffdshow, try switching between ffmpeg and libavcodec for h264 decoding and see if that makes a difference.

Couldn't have said it better myself!

I used to have odd, infrequent glitching exactly as you're describing DMagic1, and found that it went away once I started using DGIndexNV to decode-and-feed to x264. My issues were never as frequent as your own (you said it now happens on every project) but they were exactly as you've described.

I dunno if this issue still exists for me as I very rarely use BD-RB (when I have, it's worked) and more typically roll-my-own BDs using DG's nvidia tools now. Anyway my money's on a decoding problem in your PC. Good luck finding it!

[jdobbs]

Originally Posted by Capsbackup

Will this change be used for AVCHD, full backups to BD5/9?
- Changed the default values so that DTS and AC3
are kept in their original format rather than
being reencoding. That choice can be changed
via the SETUP dialog.

It still works the way it always did. The only difference is the default setting. DTS cannot be used in AVCHD, as it is not a part of the standard.

[A.Fenderson]

Originally Posted by setarip_old

@A.Fenderson

Hi!

Did you play your rip of "Boogie Nights" to make certain that it doesn't exhibit the same behavior? (I presume you've ascertained that the commercial Blu-ray plays properly)

Yeah, the rip plays normally. It might have been a one-off: I'm going to update to the newest BD-RB and run it again.

Originally Posted by DMagic1

I did the project again with no overclock and the glitch is in the same exact spot.

If it was something with my system it would seem that the glitch would be in different locations in the video not at the same exact spot right?

This makes 4 times running it and its always at the same location.

I'll check into the chkdsk.

Possibly a bad rip: I've had similar happen with one. Sometimes you can see a problem (even if it's very, very minor) in the original rip if you play back and step frame-by-frame through it, looking carefully for artifacts, at the spot where the reencode shows the issue.

[DMagic1]

Originally Posted by PurpleMan

I would suggest opening the corresponding AVS in the WORKFILES folder (VID_XXXX.avs) in VirtualDub or another editing program, then scroll to the location where the glitch occurs and look if you see it there as well.

If you do, it means that the glitch is being frameserved to the encoder, in which case it's not BD-RB's fault but rather the decoder your system is using. If it's indeed the correct version of ffdshow, try switching between ffmpeg and libavcodec for h264 decoding and see if that makes a difference.

Checked the AVS and no glitches.

I'm running the project again with the new version of BD with the lastest x264.
Also did a frame by frame of the source and saw no glitch or pixel errors.

[Stormcrow]

Regarding the new recommended versions of FFDSHOW and HAALI:

Do the new versions install cleanly on top of the old ones?
Or is it better to un-install and re-install?

And will their settings be preserved?

--
SC

[Balthazar2k4]

Let me start by saying that DVD Rebuilder Pro is a great program and jdobbs, I hope you were well compensated for your work. Next, let me apologize for asking a question that has probably been answered, but I have searched and this thread is far too long to just sit down and read. I have played around with BD-Rebuilder just a tad and I am unable to find a one-pass CRF mode. I see places in this thread where it is mentioned so that leads me to believe it exists. Am I missing something? Ultimately, I don't really care so much about the file size, so I would rather set a target quality and call it a day.

EDIT: Nevermind. I am an idiot. Nothing to see here folks.... move along....

EDIT #2: Is it possible to keep HD audio when using CRF and MKV container?

[JJB]

Originally Posted by Balthazar2k4

Let me start by saying that DVD Rebuilder Pro is a great program and jdobbs, I hope you were well compensated for your work. Next, let me apologize for asking a question that has probably been answered, but I have searched and this thread is far too long to just sit down and read. I have played around with BD-Rebuilder just a tad and I am unable to find a one-pass CRF mode. I see places in this thread where it is mentioned so that leads me to believe it exists. Am I missing something? Ultimately, I don't really care so much about the file size, so I would rather set a target quality and call it a day.

Just uncheck Automatic Quality Settings and then choose what you want.

[jdobbs]

Originally Posted by Stormcrow

Regarding the new recommended versions of FFDSHOW and HAALI:

Do the new versions install cleanly on top of the old ones?
Or is it better to un-install and re-install?

And will their settings be preserved?

--
SC

I installed both on top of the old ones.

[Sharc]

Originally Posted by laserfan

....I used to have odd, infrequent glitching exactly as you're describing DMagic1, and found that it went away once I started using DGIndexNV to decode-and-feed to x264. .....

I noticed similar glitches in the temporary sample file which is produced for CRF prediction. Fortunately it has so far never materialized for the real encode.

[jdobbs]

Originally Posted by Balthazar2k4

EDIT #2: Is it possible to keep HD audio when using CRF and MKV container?

Currently you keep the core of HD audio when "intact" is selected. I do plan to allow keeping HD audio as well -- but I forgot to make that change in this release, it'll probably be in the next release. I'm not a big believer in HD audio (I think its a useless marketing gimmick) so it probably just slipped my mind.

[Balthazar2k4]

Originally Posted by jdobbs

Currently you keep the core of HD audio when "intact" is selected. I do plan to allow keeping HD audio as well -- but I forgot to make that change in this release, it'll probably be in the next release. I'm not a big believer in HD audio (I think its a useless marketing gimmick) so it probably just slipped my mind.

Thanks jdobbs. I have several thousand dollars in audio gear alone invested in my home theater, so even if it is a placebo effect, I feel better about my investment with HD audio

I'll keep an eye out for the next release.

[Balthazar2k4]

Originally Posted by JJB

Just uncheck Automatic Quality Settings and then choose what you want.

Thanks jjb. I found it just before your post. Just needed to tinker with it some more before posting...

[Capsbackup]

I just downloaded the new release, BD-RBV03804 and the new ffdshow and haali. Installed ffdshow and haali and now I get the " - HAALI Splitter: Isn't recommended version" when I run Inspect!

[jdobbs]

Originally Posted by Capsbackup

I just downloaded the new release, BD-RBV03804 and the new ffdshow and haali. Installed ffdshow and haali and now I get the " - HAALI Splitter: Isn't recommended version" when I run Inspect!

Hmm... it says "Ok" on both my 32 and 64 bit systems. Can you look at the HAALI/Mediasplitter folder and tell me what it says for the total size?

[Edit] Whoops. I just tested it again and realized that I didn't save after I updated the size on the 32 bit check. I'll fix it for the next release. If the folder is 2,434,588 bytes, you're good to go.

[jdobbs]

Originally Posted by Balthazar2k4

Thanks jdobbs. I have several thousand dollars in audio gear alone invested in my home theater, so even if it is a placebo effect, I feel better about my investment with HD audio

I'll keep an eye out for the next release.

Wow. You must be rich. Have you donated?