BD Rebuilder Beta - Bug Reports Only

[dfsooner]

My settings were:
MENU_BACKGROUND=C:\Program Files Video\BD_Rebuilder\misc\menuback.jpg
IMPORT_THRESHOLD=6
QUICK_PLAY_THRESHOLD=6
MENU_AUTO_BACKGROUND=1
MENU_PLAY_SEQUENTIAL=0
MENU_START_WITH_MENU=1

Where are these MENU_ options documented? I couldn't find them in HIDDENOPTS or CHANGES.

[Sharc]

Switch BD-RB to Full Backup before importing; then....import. :D
D
Ahh......this did the trick. It depends on the workflow. Thanks.

[Sharc]

Where are these MENU_ options documented? I couldn't find them in HIDDENOPTS or CHANGES.
It's a copy from the .ini what is written there depending on your quick menu settings in the GUI.

[dfsooner]

It's a copy from the .ini what is written there depending on your quick menu settings in the GUI.

Then I suppose the .ini has to be edited manually to get an alternative background and change the other settings. However, there is nothing to indicate what alternate settings are permitted or what they mean.

Never mind. I found it under Settings/Import Quick-Play settings.

[kristian65]

Hi sorry for stupid question but i saw before a post how to turn off secondery forced subs so it wont be procesed.
Since im using swedish subs i not need eng forced subs. :)

[gonca]

Hi sorry for stupid question but i saw before a post how to turn off secondery forced subs so it wont be procesed.
Since im using swedish subs i not need eng forced subs. :)

What type of back-up

[AmigaFuture]

Ahh......this did the trick. It depends on the workflow. Thanks.

It was a fun adventure for me to notice also. "Oh, not a funky feature or a rodent in the program...ahhhh!" You're welcome.

[Racer]

Hello jdobbs,

is it actually possible to run the first pass with a CRF (e.g. 20) and only run the second pass if the target size would be exceeded?
This would help to reduce the size and also limit the size to a given value. Thanks!

[Blurayhd]

Hi jdobbs

They lent me a large collection of favorite movies on bluray. I would like to pass them as I always do with bd rebuilder but somehow able to remove the extras and things i do not want but retaining the original menu. I don´t know the option is there any way?

Cheers and have a happy new year, you and everyone on the forum!

[Guest]

They lent me a large collection of favorite movies on bluray. This violates our forum rule 6, putting our forum in jeopardy. You cannot make backups of copyrighted videos that someone has lent to you. Stop this nonsense or strikes will follow.

I also see that you are cross-posting, violating rule 8. You need to read and follow our forum rules or you will run into difficulties here.

[Blurayhd]

This violates our forum rule 6, putting our forum in jeopardy. You cannot make backups of copyrighted videos that someone has lent to you. Stop this nonsense or strikes will follow.

I also see that you are cross-posting, violating rule 8. You need to read and follow our forum rules or you will run into difficulties here.

@neuron2

Thanks for alerting me and tell me about this. I'll read the rules

Honestly, I do not know, there was no bad intention

Thank you again!

[Guest]

Thank you for your understanding and have a prosperous 2014.

[kristian65]

What type of back-up

movie only

[gonca]

From HIDDENOPTS.txt
FORCED_SUB_LANG=s s = 3 letter preferred language codes -- default is "eng", can be multiples (e.g. "ger;deu")

Make sure this is set for the Swedish language in BDREBUILDER.ini

[kristian65]

From HIDDENOPTS.txt
FORCED_SUB_LANG=s s = 3 letter preferred language codes -- default is "eng", can be multiples (e.g. "ger;deu")

Make sure this is set for the Swedish language in BDREBUILDER.ini

Thanks alot :)

[DoctorM]

Tried a BD5 today with a one-pass CRF. The CRF value was 16.33 and the final disc 4.00gb.

When DVD Rebuilder misses the target by that much on a one-pass I'd normally deincrement the Q value, click 'Encode' then 'Rebuild'.
Although a CRF of 16.33 probably can't be improved by much, is a similar method available to tune BD RB? Is a 3 step vs one-click setting coming in the future?

What is the target size set to for a BD5, 4482mb or something less?

@ Racer - If the target size of a one-pass fails, doing a second pass shouldn't improve either quality or encoding speed. A new CRF encoding after adjusting the value is the best answer (if it is possible).

[gonca]

@DoctorM
BD5_SIZE=n n = Change the output size (in one megabyte units) for BD-5 writes -- default = 4469
BD9_SIZE=n n = Change the output size (in one megabyte units) for BD-9 writes -- default = 8032
FIXED_CRF=n n = 10..50 - force CRF encoding to use this CRF value (output size control disappears)
From the HIDDENOPTS.txt file

[DoctorM]

@DoctorM

From the HIDDENOPTS.txt file

Cheers.

I just noticed that the analysis only tested one really low value below the one it selected. Is that normal?
- Analyzing 21.27 15.64 16.74 16.36 [16.33]

[gonca]

It decided that 16.33 was the best value for BD5. As for how many high or low values, it focus in to the value it needs. Next time it could be reversed.

[DoctorM]

@gonca - I know when I've manually encoded using CRF (with MeGUI), tenths of a point rarely made much difference. Later I'm going to try testing clips and comparing 16.33 to 16.00. The bitrate difference should be awfully minor. To extrapolate 16.33 as the best with the next lower tested value is .69 below that seems like a pretty big estimation. Still, I don't know the algorithm used... and DVD RB's method always seemed damn good so I'm willing to assume it's still the best possible system.

@jdobbs - I'm a bit concerned about something though. Doing some further playing around with a BD25 to BD5 one pass CRF, I decided I wanted to compare source vs encode for quality.

source=ffmpegsource2("(Source)\BDMV\STREAM\00000.m2ts").subtitle("Source")
encode=ffmpegsource2("(BDRB Encode)\BDMV\STREAM\00000.m2ts").subtitle("Encode")
interleave(source,encode)

Just a few hundred frames in they go out of sync by a couple frames and then it moves back and forth throughout. No more than a few frames, but I'm at a loss to figure out why. ffms2 should be frame accurate and DVDRB encoding with directshowsource should be perfect since it is being encoded linearly. I'm not sure if I should be worried or not about this, but I've never seen that with encodings before. Any thoughts on this?

[jdobbs]

@DoctorM

Are you playing end-to-end or jumping around and looking at the frames? ffpmegsource2 isn't frame-accurate when an M2TS is a source. From the ffmpegsource2 user manual:
M2TS, TS: Seeking seems to be off a few frames here and there

[mparade]

@gonca - I know when I've manually encoded using CRF (with MeGUI), tenths of a point rarely made much difference. Later I'm going to try testing clips and comparing 16.33 to 16.00. The bitrate difference should be awfully minor. To extrapolate 16.33 as the best with the next lower tested value is .69 below that seems like a pretty big estimation. Still, I don't know the algorithm used... and DVD RB's method always seemed damn good so I'm willing to assume it's still the best possible system.

@jdobbs - I'm a bit concerned about something though. Doing some further playing around with a BD25 to BD5 one pass CRF, I decided I wanted to compare source vs encode for quality.

source=ffmpegsource2("(Source)\BDMV\STREAM\00000.m2ts").subtitle("Source")
encode=ffmpegsource2("(BDRB Encode)\BDMV\STREAM\00000.m2ts").subtitle("Encode")
interleave(source,encode)

Just a few hundred frames in they go out of sync by a couple frames and then it moves back and forth throughout. No more than a few frames, but I'm at a loss to figure out why. ffms2 should be frame accurate and DVDRB encoding with directshowsource should be perfect since it is being encoded linearly. I'm not sure if I should be worried or not about this, but I've never seen that with encodings before. Any thoughts on this?

In what program do you load the avs script? I would like to make some quality check also but with MPEG-4 sources to know which CRF value fits best to my need.

My current script is:

LoadPlugin("E:\Users\X\Downloads\dgavcdec109\DGAVCDecode.dll")
a = DirectShowSource("L:\BD-50\THE DARK KNIGHT RISES\DISC1\DARK_KNIGHT_RISES\BDMV\STREAM\00020.m2ts")
b = DirectShowSource("F:\BDMV\STREAM\00000.m2ts")
Interleave(a,b)

[DoctorM]

@DoctorM

Are you playing end-to-end or jumping around and looking at the frames? ffpmegsource2 isn't frame-accurate when an M2TS is a source. From the ffmpegsource2 user manual:

That's probably it. Will extract the video and try again.

@mparade - directshowsource is definitely not frame accurate. You will need to index the files before you can do this. Demux the video streams and use either ffmpegsource2 or DGAVCIndex.

For viewing, I'm a throwback and still use VirtualDubMod. It still works so I've never felt a reason to change.

[mparade]

That's probably it. Will extract the video and try again.

@mparade - directshowsource is definitely not frame accurate. You will need to index the files before you can do this. Demux the video streams and use either ffmpegsource2 or DGAVCIndex.

For viewing, I'm a throwback and still use VirtualDubMod. It still works so I've never felt a reason to change.

Thank you for the help. Anyway, I have been still using VirtualdubMod as well since the beginning of the release of DVD-RB. :o

[MuttLover]

First off, thank-you for making such a useful product. I donated to and used the original DVD Rebuilder product and I have donated to and use the BD Rebuilder product.
I apologize if this has been reported before. I did a search on this thread and did not see the issue come up.
I have been backing up the holiday DVDs and ran across some strange behavior in The Wolverine, NTSC, Movie-only backup, Keep HD soundtrack, all English subtitles, all English soundtracks, BD. The forced subtitles in the film do not automatically clear off the screen. To get them to clear, I had to fast forward. Otherwise the last subtitle would stay up.

FYI:
I have run inspect.exe and all items check out OK.
- Windows Version: 6.1 [7601]
- AVISYNTH Version: [2.5.8.0], Ok
- HAALI Splitter: [1.9.42.1], 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
- AnyDVD settings check: Ok.
- BD Rebuilder v0.45.0.5, Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- WAVI: Ok
- TSMUXER: Ok

Windows 7.0, 64 Bit Home premium up-to-date

I was working on a series of backups so I did not get a log file.

Thanks for your help, and as I said before, my apologies if you were already aware of this.

Encoder settings, automatic, this is the vanilla version of the BDREBUILDER.ZIP.

Setup changes:
unchecked "Limit to one track for each language" for both audio and subtitles
checked "Keep HD Audio for BD25/Alternate intact"
All other setup is the vanilla setup.
Movie-only mode

[RobertM]

The forced subtitles in the film do not automatically clear off the screen.

Hmm... Interesting. I recently had an instance like this. And it may well have been on "The Wolverine" (can't remember exactly). Could be a bug in the original subtitle stream, I suppose.

[jdobbs]

I just did a movie-only backup of Wolverine two days ago... but I was reencoding the soundtrack to AC3. I run it again keeping the HD audio and see what happens.

[DoctorM]

Demuxed the video tracks with tsMuxerGUI, indexed with DGAVCIndex, modified the script and bing the frames line up perfectly. Whew.
Sorry for stupidly freaking out. Everyone always crow about how great ffmpegsource is, but not it's failures like issues with transport streams.

The final encoding from an animated film, 19gb down to 4gb, BDRB made a pristine copy. I'm hard pressed to find any differences randomly checking frames. Great stuff.

[Guest]

Everyone always crow about how great ffmpegsource is, but not it's failures like issues with transport streams. +1

M2TS, TS: Seeking seems to be off a few frames here and there After all, it is so hard to parse a transport stream. ;)

Call it the dark side of open source software.

[manolito]

Sorry if this has been answered before, but what is your current opinion regarding ffdshow vs. LAV filters?

So far I have been using the recommended versions of ffdshow and Haali from the first post of this thread without any issues. But recently I ran into troubles decoding source files with a non-mod4 width, and switching from ffdshow to LAV filters solved all these problems.

Since ffdshow is not developped any more, and Haali does not support some current formats, is it safe to ditch ffdshow and Haali and use the current (0.59.1) version of LAV filters instead?



Cheers
manolito

[DoctorM]

Sorry if this has been answered before, but what is your current opinion regarding ffdshow vs. LAV filters?

So far I have been using the recommended versions of ffdshow and Haali from the first post of this thread without any issues. But recently I ran into troubles decoding source files with a non-mod4 width, and switching from ffdshow to LAV filters solved all these problems.

Since ffdshow is not developped any more, and Haali does not support some current formats, is it safe to ditch ffdshow and Haali and use the current (0.59.1) version of LAV filters instead?



Cheers
manolito
The last build I see of ffdshow was December 3rd (rev 4527). I don't know what you're following.

[manolito]

The last build I see of ffdshow was December 3rd (rev 4527). I don't know what you're following.

What am I following???

The last official and recommended version of ffdshow on sourceforge is from 2013-01-06 - ffdshow 1.3.4500

The version jdobbs endorses is ffdshow_rev4504_20130312_clsid.exe from March 2013.

And here is a recent quote from qyot27:
ffdshow's development has almost halted, and on top of that, it relies on an internal copy of the libav* libraries, whereas LAV Filters doesn't. So basically, LAV is actively maintained and uses much more up-to-date versions of avcodec, avformat, etc. It's also capable of playing both HEVC and Opus - ffdshow can't (and unless there's been a recent update, Haali can't deal with Opus streams in MKV, despite Opus-in-MKV being finalized back in July).


Plus a few posts by clsid:
http://forum.doom9.org/showthread.php?p=1645211#post1645211
http://forum.doom9.org/showthread.php?p=1656467#post1656467
http://forum.doom9.org/showthread.php?p=1656599#post1656599


So this is what I am following...:mad:


Cheers
manolito

[jdobbs]

Sorry if this has been answered before, but what is your current opinion regarding ffdshow vs. LAV filters?

So far I have been using the recommended versions of ffdshow and Haali from the first post of this thread without any issues. But recently I ran into troubles decoding source files with a non-mod4 width, and switching from ffdshow to LAV filters solved all these problems.

Since ffdshow is not developped any more, and Haali does not support some current formats, is it safe to ditch ffdshow and Haali and use the current (0.59.1) version of LAV filters instead?



Cheers
manolitoIt's been a while, but if I recall correctly the LAV filters have difficulty with VC-1 interlaced content. I'll give it a test later today and let you know if that is still the case.

[DoctorM]

What am I following???

The last official and recommended version of ffdshow on sourceforge is from 2013-01-06 - ffdshow 1.3.4500

The version jdobbs endorses is ffdshow_rev4504_20130312_clsid.exe from March 2013.

And here is a recent quote from qyot27:



Plus a few posts by clsid:
http://forum.doom9.org/showthread.php?p=1645211#post1645211
http://forum.doom9.org/showthread.php?p=1656467#post1656467
http://forum.doom9.org/showthread.php?p=1656599#post1656599


So this is what I am following...:mad:


Cheers
manolito

So your quote regarding ffdshow's development is from a programmer of LAV filters. I'd take that with a grain of salt.

I'm not looking to start a fight, but BD RB already works. Have you found a bug with BD RB and ffdshow that you are reporting or are you just voicing your preference for your favorite filter? Do you have HEVC and Opus BD that need re-encoding?

[Guest]

manolito has already clearly stated his motivation:

"But recently I ran into troubles decoding source files with a non-mod4 width, and switching from ffdshow to LAV filters solved all these problems."

[jdobbs]

Sorry if this has been answered before, but what is your current opinion regarding ffdshow vs. LAV filters?

So far I have been using the recommended versions of ffdshow and Haali from the first post of this thread without any issues. But recently I ran into troubles decoding source files with a non-mod4 width, and switching from ffdshow to LAV filters solved all these problems.

Since ffdshow is not developped any more, and Haali does not support some current formats, is it safe to ditch ffdshow and Haali and use the current (0.59.1) version of LAV filters instead?



Cheers
manolitoIt's been a while, but if I recall correctly the LAV filters have difficulty with VC-1 interlaced content. I'll give it a test later today and let you know if that is still the case.Well at least on the VC-1 interlaced source I tested today it appear X264's LAVF function is now decoding it properly. I'll do some more testing.

Right now, though, if LAVF is selected and BD-RB encounters a VC-1 interlaced source BD-RB reverts to DirectshowSource() for frame serving. The same happens when there is resizing or other AVISYNTH filter requirements based upon settings.

If my continued testing confirms what this one source suggests, I may have to change the process flow. X264 has some internal filtering capabilities (like resizing) so I may be able to make LAVF work in more scenarios than now. Assuming all is well, it may even be worth consideration to make LAVF the default at some point.

[nozuul]

Not sure I know what I am doing with this one. This is the first time I have tried using the forced subs feature. Also the first time I got a fail in quite awhile.

Here is the Log.

[01/04/14] BD Rebuilder v0.45.05 (beta)
[14:34:56] Source: THE_WOLVERINE_00800
- Input BD size: 40.82 GB
- Approximate total content: [02:18:05.277]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: iPad 2+/iPhone 4s+, 720x480/576, 128Kbs AAC
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[14:34:57] PHASE ONE, Encoding
- [14:34:57] Processing: VID_00800 (1 of 1)
- [14:34:57] Extracting A/V streams [VID_00800]
- [14:44:13] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 198,648 frames
- [14:44:14] Reencoding: VID_00800, Pass 1 of 1
- Encode failed. Aborting.
- BD-Rebuilder v0.45.05 (beta)
- Windows Version: 6.1 [7601]
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.11.96.14, Ok
- FFDSHOW: 3882, 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 "ffmpeg-mt": Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- WAVI: Ok
- TSMUXER: Ok
[14:44:15] - Failed video encode, aborted

Any ideas?

Thanks

[nozuul]

Never mind, I had installed the x64 version of SupTitle

Once I installed the x86 files, it seems to be chugging along just fine.

My bad.

Thanks anyway!

[manolito]

If my continued testing confirms what this one source suggests, I may have to change the process flow. X264 has some internal filtering capabilities (like resizing) so I may be able to make LAVF work in more scenarios than now. Assuming all is well, it may even be worth consideration to make LAVF the default at some point.

Thanks a lot jdobbs for looking into it.:thanks:


Cheers
manolito

[laserfan]

I was fiddling with my "Mud" BD today and noticed that the .meta file for my BD-9 Movie-Only mux was set for MUXOPT --avchd. This surprised me as I don't have "Strict AVCHD for BD-5/9 Movie Only" checked and the .INI file has AVCHD=0.

Is this normal or did I find a bug of some sort? I don't think I've ever tried a BD-9 before with BD-RB, and the several BD-25s I've done of course are all muxed as Blu-ray.

[gonca]

@laserfan
Don't quote me on this, I have been known to be wrong -- in fact well known ;), but Movie-Only and BD-9 make it AVCHD. The strict setting applies to audio, AC3 only, bit rates etc -- strict adherence to the spec. If it is not checked BD_RB doesn't enforce the spec as tightly.

[laserfan]

@laserfan
Don't quote me on this, I have been known to be wrong -- in fact well known ;), but Movie-Only and BD-9 make it AVCHD. The strict setting applies to audio, AC3 only, bit rates etc -- strict adherence to the spec. If it is not checked BD_RB doesn't enforce the spec as tightly.
Thanks, I had read in the changelog something about defaulting to AVCHD back in 2011, but then I find that setting which is why I'm confused.

I'm surprised jdobbs if you didn't put a hidden opt or override somewhere for this muxing variation.

[jdobbs]

It's just a way of ensuring a broader range of compatibility. If it is BD-5 or BD-9 it is output using TSMUXER's "--avchd" option. There's really no reason to override it. There are other settings that are specific to BD-5/9 as well. For example, the maximum bitrate has to be lowered because a DVD+-R disc/drive can't read at BD specification rates.

[laserfan]

OK, thanks for that jdobbs. I do wonder what (if any) are the ins-and-outs of --avchd vs --blu-ray i.e. the 200 vs 100 designations & whatnot. I remember there was a lot of discussion about this years ago but I'm not able to resurrect those posts (or brain cells). Maybe it was as simple as "some settop players *need* --avchd for BD-5/9 and/or homemade discs or they won't play" or something, though obviously my players don't care as I have always (manually, not BD-RB) made all my backups using --blu-ray.

The above disc (Mud) I did not burn as --avchd so I won't find-out from that. I had to trim a horribly loud/obnoxious LIONSGATE thing off'n the front of the movie so I changed the meta to --blu-ray.

[jdobbs]

OK, thanks for that jdobbs. I do wonder what (if any) are the ins-and-outs of --avchd vs --blu-ray i.e. the 200 vs 100 designations & whatnot. I remember there was a lot of discussion about this years ago but I'm not able to resurrect those posts (or brain cells). Maybe it was as simple as "some settop players *need* --avchd for BD-5/9 and/or homemade discs or they won't play" or something, though obviously my players don't care as I have always (manually, not BD-RB) made all my backups using --blu-ray.

The above disc (Mud) I did not burn as --avchd so I won't find-out from that. I had to trim a horribly loud/obnoxious LIONSGATE thing off'n the front of the movie so I changed the meta to --blu-ray.Personally I'd leave it at avchd unless you're planning on using the same player forever. But, as always, the choice is yours. The version numbers are different in the different configuration (mpls, clpi, etc.) files (e.g. the header in the index.bdmv file is "INDX0100" rather than "INDX0200" for blu-ray) -- which some players require for BD-5/9 playback.

Honestly, though, now that BD-R discs are almost the same price as DVD+R DL, I do most of my backups to BD-R (I used to do most to DVD+R DL).

[laserfan]

I do most of my backups to BD-R (I used to do most to DVD+R DL).
Yeah me too, which is why I hadn't noticed this AVCHD thing before.

Thanks for your comments. I believe some day that I will get a 3D or 4K or ??? player, but for my current use I have three players, one I use a little and the other two I don't use at all, so I don't worry about AVCHD or Cinavia for example. These are gonna last a very long time...

:)

[ripburnlearn]

I'm trying to compress the new Robocop Blu-Ray (the unrated Director's cut) from 50GB to 25GB. Every time I run the BD-RB app it crashes. I'm using the latest version 0.45.05.

I saw on your website jdobbs a BD-RB System Inspection app. I ran it and here are the results:
- Windows Version: 6.1 [7601]
- AVISYNTH Version: 2.5.8.0, not recommended version
- HAALI Splitter: Isn't recommended version
- FFDSHOW: 4504, not recommended version
- 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 "ffmpeg-mt": Ok
- More info available if run from BD-RB folder

I made sure to download the "recommended" versions of each of these apps in the first post of this thread and I got the above. Why is it coming up as "not recommended" in this app?

[ripburnlearn]

The forum won't let me edit my last post. And just to add to my last post, it crashes my entire computer while it is encoding the film someone around 30%. I think I had this issue before but I can't remember what the exact solution it was. I think I installed in older version of one of the apps. I'm not sure if this Blu ray is the culprit for this app to crash.

EDIT: Ohhhhh, I downloaded the inspection app from the videohelp website. I guess that app is old or something? I went inside of my BDRB folder and I found the same Inspect app and it says:
- Windows Version: 6.1 [7601]
- AVISYNTH Version: [2.5.8.0], Ok
- HAALI Splitter: [1.9.42.1], Ok
- FFDSHOW: [4504], 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 "ffmpeg-mt": Ok
- AnyDVD settings check: Ok.
- BD Rebuilder v0.45.0.5, Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- WAVI: Ok
- TSMUXER: Ok

Everything is OK but my computer. It has crashed and reset itself so many times during my attempts to encode.

[RocKKer]

ripburnlearn,

You seem to have all the supporting software correct.

If your not overclocking, resets while stressed can many times be caused by faulty memory. It could be other things, but I would start by testing memory first.

If it is overclocked, return it to default settings and try BDRB again.

pm sent.

[Guest]

Also check all fans, clean heat sink fins, and general cooling.