BD Rebuilder Beta - Bug Reports Only

[jdobbs]

Not a "dodgy USB interface" - internal SATA with standard SMB shares. And it doesn't matter whether it's a NAS or another Win7 computer on the wired gigabit LAN. I have four Windows 7 desktops and two NAS servers on my LAN and the problem manifests itself on any SMB share (even on the local machine). Not saying there may not be an OS issue, but I haven't seen this problem with other programs. Ok. I think I have it working using UNC paths. I'm doing a test run of an encode now. The problem was an oddity (that, by the way, I couldn't find documented in the Microsoft docs) in the O/S's "CreateFile()" function as BD-RB is collecting filesizes when working with UNC filenames. Luckily a google search found someone who discussed it.

[discoballs]

@discoballs; RE: the option to select audio is not there in tree view but I know it should be.

You failed to mention what disk you are processing and also what kind of audio files that were originally on the disk. I have seen the problem you are refering to on a few disk before, but can't remember which ones, maybe the Last Emperor, Max & Me, or one of the Girl with Dragon Tattoo's. The audio was there but BD_RB was not able to recognize it. I ended up pre-processing (used either ClownBD or TsmuxeR GUI) it to remove the audio and rebuild it to a BD output that had 640k 5.1 audio that BD_RB was happy to use. I seen to remember it was some LPCM weird bitrate that was not being recognised. Hope this helps


Thanks for replying but the fault comes up on all of the bluray discs I have (even the one's I have already done). There must be something I installed recently affecting it but the only way I know to fix it is format and reinstall everything. Was hoping there was a way to fix it but don't know it. Will have to check after each thing I install so I can bin it. :confused::confused:

[Capsbackup]

The META should be there. It's called "AUD_00044.META".

This is the contents of AUD_00044.META:
MUXOPT --no-pcr-on-video-pid --new-audio-pes --demux --vbr --vbv-len=500
V_MPEG4/ISO/AVC, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts", fps=23.976, track=4113
A_DTS, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts", track=4352, lang=eng
S_HDMV/PGS, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts",fps=23.976, track=4608,lang=eng
S_HDMV/PGS, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts",fps=23.976, track=4609,lang=fra
S_HDMV/PGS, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts",fps=23.976, track=4610,lang=spa
S_HDMV/PGS, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts",fps=23.976, track=4611,lang=por
S_HDMV/PGS, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts",fps=23.976, track=4612,lang=nld

Interesting -- so you're saying the file demuxed directly by TSMUXER directly is also 1K long?

No, the file demuxed directly with tsMuxeR is the same file size as the one demuxed with BD-RB. These .dts files range in size from about 5MB to 8MB. They both will play correctly. BD-RB demuxed them correctly. BD-RB just did not reencode them to .ac3 correctly.
It is the BD-RB created .ac3 that is only 1kb with no audio!

I can manually convert these BD-RB .dts files to 448kbps ac3 with Aften, rename them to AUD_00044_4352, etc... insert them in the Workfiles folder in place of the 1kb files, and do a rebuild and now the audio is there and works for these m2ts files that previously had no audio.

[jdobbs]

This is the contents of AUD_00044.META:
MUXOPT --no-pcr-on-video-pid --new-audio-pes --demux --vbr --vbv-len=500
V_MPEG4/ISO/AVC, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts", fps=23.976, track=4113
A_DTS, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts", track=4352, lang=eng
S_HDMV/PGS, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts",fps=23.976, track=4608,lang=eng
S_HDMV/PGS, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts",fps=23.976, track=4609,lang=fra
S_HDMV/PGS, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts",fps=23.976, track=4610,lang=spa
S_HDMV/PGS, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts",fps=23.976, track=4611,lang=por
S_HDMV/PGS, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts",fps=23.976, track=4612,lang=nld



No, the file demuxed directly with tsMuxeR is the same file size as the one demuxed with BD-RB. These .dts files range in size from about 5MB to 8MB. They both will play correctly. BD-RB demuxed them correctly. BD-RB just did not reencode them to .ac3 correctly.
It is the BD-RB created .ac3 that is only 1kb with no audio!

I can manually convert these BD-RB .dts files to 448kbps ac3 with Aften, rename them to AUD_00044_4352, etc... insert them in the Workfiles folder in place of the 1kb files, and do a rebuild and now the audio is there and works for these m2ts files that previously had no audio. I can see the problem. The AUD_00044.META file should have had "down-to-DTS" as a part of this line:

A_DTS, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts", track=4352, lang=eng

Without it NICAUDIO.DLL cannot decode it (because it is HD) and the AC3 encode fails. The question is: Why did it not insert it?

I'm not sure I got the gist correctly... you did say these were DTS-HD, right?

[jdobbs]

Thanks for replying but the fault comes up on all of the bluray discs I have (even the one's I have already done). There must be something I installed recently affecting it but the only way I know to fix it is format and reinstall everything. Was hoping there was a way to fix it but don't know it. Will have to check after each thing I install so I can bin it. :confused::confused: You have to select the desired audio you want in the "Setup". ex.: go to Settings, Setup and set your desired audio and subtitle tracks. You can also click on the audio track while in the regular tree view of BD-RB and select/deselect your desired audio/subtitles for each video file listed. :)
Capsbackup has given you the correct advice. Go to SETUP and select the languages you want to keep by default -- and then save.

[Capsbackup]

I can see the problem. The AUD_00044.META file should have had "down-to-DTS" as a part of this line:

A_DTS, "G:\BD RIPS\TRUE_BLOOD_S3_D2\BDMV\STREAM\00044.m2ts", track=4352, lang=eng

Without it NICAUDIO.DLL cannot decode it (because it is HD) and the AC3 encode fails. The question is: Why did it not insert it?

I'm not sure I got the gist correctly... you did say these were DTS-HD, right?

No only the main movie's audio track is DTS-HD. These other files are just dts. The main DTS-HD tracks were reencoded properly and play back perfectly.

[Capsbackup]

Just completed True Blood season 3 disc 3, and a whopping 36 .dts audio tracks were not converted to ac3 :eek:

[jdobbs]

Just completed True Blood season 3 disc 3, and a whopping 36 .dts audio tracks were not converted to ac3 :eek: I'll do some testing with that disc and see what's up.

[discoballs]

Capsbackup has given you the correct advice. Go to SETUP and select the languages you want to keep by default -- and then save.

Have tried that.
http://img831.imageshack.us/img831/3614/picture20110617054046.th.jpg (http://imageshack.us/photo/my-images/831/picture20110617054046.jpg/) Uploaded with ImageShack.us (http://imageshack.us)

:confused::confused:

[setarip_old]

@discoballs

Hi!

Does your system have the ability to play TrueHD audio, the audio that you've selected as the ONLY audiostream?

[Carter]

I wonder, is the entire re-encoding process with x264 is any way limited by copying speed of harddisks ?

HDD1 re-encode to HDD2 = faster if HDD's are 200mb/s read/write or doesnt it matter if they are 100mb/s read/write only ? or basically, completely CPU dependend only ?:thanks:

[PurpleMan]

Sorry but that's just outright incorrect. Standalone players are the standard to shoot for. Software players are almost always much more forgiving. I can create a BD that wildly violates the standard and they will play back just fine on a software player, mainly because it has virtually no buffer or processor limits. Their biggest problem is just poorly written code that does goofy things randomly.

Even if I agree with you and accept that software players are forgiving, it only enhances my point that if a backup does not play on a software player - chances are something is very wrong.

As mentioned, in my experience whenever PowerDVD fails to play something correctly, I will usually find something wrong in the MPLS or CLPI (which, as mentioned, led to bug reports which were confirmed and fixed later on).

My only point is that if a backup doesn't work on PowerDVD we shouldn't dismiss it because "it's a software player" but rather investigate why the original plays fine and the backup does not.


P.S.
TMT (both 3 and 5) are more forgiving than PDVD11, which I find is very strict.

[jdobbs]

Have tried that.
http://img831.imageshack.us/img831/3614/picture20110617054046.th.jpg (http://imageshack.us/photo/my-images/831/picture20110617054046.jpg/) Uploaded with ImageShack.us (http://imageshack.us)

:confused::confused: I don't even see how that is possible, I just followed the code and there isn't even a path that would create the audio tree without an image (either selected or not selected).

My best guess is that some other program has replaced the registered version of MSCOMCTL.OCX (included with Windows) with a corrupted or old one. Some less-then-careful developers will do that without telling you. You may be able to fix it by registering the one in the BD Rebuilder folder. You can do that by putting yourself in that folder under CMD and then typing:

regsvr32 MSCOMCTL.OCX

[jdobbs]

Even if I agree with you and accept that software players are forgiving, it only enhances my point that if a backup does not play on a software player - chances are something is very wrong.

As mentioned, in my experience whenever PowerDVD fails to play something correctly, I will usually find something wrong in the MPLS or CLPI (which, as mentioned, led to bug reports which were confirmed and fixed later on).

My only point is that if a backup doesn't work on PowerDVD we shouldn't dismiss it because "it's a software player" but rather investigate why the original plays fine and the backup does not.


P.S.
TMT (both 3 and 5) are more forgiving than PDVD11, which I find is very strict. I have said at least 20 times in this very thread that I will not accept bug reports from software players. It's because they are buggy and unreliable. If you go back through the thread you will also find numerous reports that turned out to be the software player. I don't have the time or inclination to chase down bugs for the developers of software players and will not do so. I also do not intend to spend my time debating the point.

Sorry, but that's just the way it is.

By the way, I don't "dismiss it" when it is reported -- I simply ask that it be confirmed on a real player (a standalone).

[jdobbs]

I wonder, is the entire re-encoding process with x264 is any way limited by copying speed of harddisks ?

HDD1 re-encode to HDD2 = faster if HDD's are 200mb/s read/write or doesnt it matter if they are 100mb/s read/write only ? or basically, completely CPU dependend only ?:thanks: Hard drive speed makes a difference, especially on large writes like BD-25, but CPU speed has much more impact by far.

[PurpleMan]

I have said at least 20 times in this very thread that I will not accept bug reports from software players. It's because they are buggy and unreliable. If you go back through the thread you will also find numerous reports that turned out to be the software player. I don't have the time or inclination to chase down bugs for the developers of software players and will not do so. I also do not intend to spend my time debating the point.

Sorry, but that's just the way it is.

By the way, I don't "dismiss it" when it is reported -- I simply ask that it be confirmed on a real player (a standalone).

I think you got me wrong. I know you don't usually dismiss it and we obviously have similar goals in regards to bugs and this thread. I was only stressing that it's indeed important to act like you do and not dismiss a report solely on it being a software player tested issue.

And by the way, I know how you feel about software players, and that's why whenever something doesn't play right I try to find the underline cause by examining the appropriate MPLS/CLPI/M2TS and only then report a bug :)

[RJNelson]

I seem to be having trouble with every BLU-RAY I try to encode after the update on this computer. I haven't really seen anything like the problem I'm having since it's not related to a specific movie. Anyway, here's some info i got from BD-Rebuilder:

[08:51:27] PHASE ONE, Encoding
- [08:51:27] Extracting A/V streams [VID_00400]
- [08:51:29] Reencoding: VID_00400 (1 of 20)
- [08:51:29] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 568 frames
- [08:51:29] Reencoding: VID_00400, Pass 1 of 1
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
- BD-Rebuilder v0.38.03 (beta)
- Windows Version: 6.1 [7600]
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: Ok
- FFDSHOW: 3326, Ok
- WIN7 preferred AVC CODEC: Ok
- WIN7 preferred VC-1 CODEC: Ok
- WIN7 preferred MPEG2 CODEC: Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
[08:51:30] - Failed video encode, aborted

I hope this helps, please let me know what the problem could be if possible.

[jdobbs]

A good bet would be that something else has changed your configuration and is intercepting the AVC CODEC. I'd suggest you uninstall FFDSHOW and reinstall it.

[Ch3vr0n]

I just had a rather serious issue with a rebuild of the disc "How Do You Know" (with reese witherspoon) The rebuild itself was successful, however BDRB cut the last chapter short the original movie is just a fraction over 2hrs long (2hrs 45seconds). Verified this with the original disc, and the iso rip from anydvd hd. Both say the same. However with the rebuild the last 5 minutes are missing and the movie is cut short to 1hr 55min 22 seconds where the ending is arround 1:57h and the rest are credits with the last chapter mark being set at 1:52:11 (same on original and rebuilt disc). Something is off, thats for sure

The rebuilt disc had 154 m2ts files and so did the original, i'm at a loss here. I enjoyed the 1h55m long in front of my TV and then had to swap to my htpc for the ending, kind of a mood killer if you ask me

Another thing that i noticed is that the original had the common PS3 folders, on the rebuilt they were not present however a file called PS3_DISC.FSB was (wich was also on the original disc)

[A.Fenderson]

My past system instability issues have been resolved: oddly, Avast was causing frequent BSODs, so it's been replaced with MS Security Essentials, and I'm back to normal on that machine.

I had one really odd rebuild problem: Boogie Nights. There's a point in the movie when it cuts to a black screen with just "80s" in white letters for a few seconds, then the film resumes--but not on my rebuild. From that point to the very end of the massive, full-movie m2ts file, I get the "80s" only for video, but audio is normal. I don't have access to the log atm, but I did read through it and no errors were reported.

[DMagic1]

I'm not sure which recent version of BD Rebuilder it started with but recently I started getting a video glitch once on every project I do. It varies on when during the movie but always happens once.

See here.

http://img823.imageshack.us/img823/6056/ci107049385630158389.jpg (http://imageshack.us/photo/my-images/823/ci107049385630158389.jpg/)

[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)

[PurpleMan]

I'm not sure which recent version of BD Rebuilder it started with but recently I started getting a video glitch once on every project I do. It varies on when during the movie but always happens once.

See here.

http://img823.imageshack.us/img823/6056/ci107049385630158389.jpg (http://imageshack.us/photo/my-images/823/ci107049385630158389.jpg/)

Assuming there's nothing wrong with your decoder and that you use all the recommended versions in the first post, that is likely to happen if your system is overclocked.

No matter how stable you think your system is, video encoding is an extremely demanding process, and even the slightest mistake in calculation during encodes could cause this.

[DMagic1]

Assuming there's nothing wrong with your decoder and that you use all the recommended versions in the first post, that is likely to happen if your system is overclocked.

No matter how stable you think your system is, video encoding is an extremely demanding process, and even the slightest mistake in calculation during encodes could cause this.

Thanks, Ill look into the overclock.

[DMagic1]

If that is the problem, which I am really not thinking so, I am checking it. I have had the system setup this way for the longest, before Avatar came out and never had this issue untill recently. I'm running the same project as earlier a third time now without overclocking and I see what happens. The second time I ran it still overclocked it gave the glitch at the same place again.

[jdobbs]

If that is the problem, which I am really not thinking so, I am checking it. I have had the system setup this way for the longest, before Avatar came out and never had this issue untill recently. I'm running the same project as earlier a third time now without overclocking and I see what happens. The second time I ran it still overclocked it gave the glitch at the same place again. Unfortunately, though, no one else is reporting anything like your post shows. That points back to something systemic on your computer. The only other similar report I've ever seen turned out to be a flaky hard drive. That kind of macroblocking seems to only come when the encoding is corrupted somehow.

[Capsbackup]

@jdobbs;
A happy father's day to you! :)

I ran a full backup to BD9 of True Blood season 3 disc 5, which has only one episode and the rest bonus features. There are 355 titles with .dts audio tracks that do not get reencoded to ac3. :eek:
Interesting that the first dts track, the second track, which is a dts-hd track and the next three dts tracks are converted to ac3 properly. ( the first five audio tracks are fine ) The following 355 dts tracks are not converted or are converted to only 1 kb. :(

[LowDead]

I'm not sure which recent version of BD Rebuilder it started with but recently I started getting a video glitch once on every project I do. It varies on when during the movie but always happens once.

See here.

http://img823.imageshack.us/img823/6056/ci107049385630158389.jpg (http://imageshack.us/photo/my-images/823/ci107049385630158389.jpg/)

To me it sounds like there's something going on with your hdd.. do a chkdsk on it..

[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.

[PurpleMan]

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.

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.

[jdobbs]

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]

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]

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]

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]

@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.

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]

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]

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]

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]

....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]

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]

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]

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! :confused:

[jdobbs]

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! :confused: 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]

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? :)