BD Rebuilder Beta - Bug Reports Only

[Dark Shikari]

No, that shouldn't be the case. It will give you the quality associated with the CRF. You'd just use a little more bitrate than a higher quality setting.Different presets at the same CRF are not guaranteed to give the same quality. This is particularly true on the following three boundaries:

1. No AQ -> AQ (ultrafast -> superfast)
2. No MBtree -> MBtree (veryfast -> faster)
3. No psy -> psy (faster -> fast)

[tandi]

What program (and what version) are you using to play the disc?
What was used to burn the disc?
Is the disc an DVD5, DVD9, BDR?
Was it burned as an AVCHD?
Using clipinf.edit (from clownbd site) open the clip file. Does it say it's AVCHD or Blu ray?


Z

i use powerdvd BD Edition ver 7.3
i use Imgburn and nero as UDF 2.5
the disc : verbatim dvd+DL
ClipINF Header : Blu-ray

[Sharc]

Mmmh, ok for the rc to CRF, but shouldn't the quality preset be a bit better than ultrafast? That gives sometimes ugly result compared to default or slow preset. Fortunately most of the time secondaries are reduced on playback.
Wouldn't QUICK_USE_QUALITY=1 in the [Options] of the .ini help in your case?
It would force the CRF encodes to use the same settings as for the main feature.

[SoniG]

Different presets at the same CRF are not guaranteed to give the same quality. This is particularly true on the following three boundaries:

1. No AQ -> AQ (ultrafast -> superfast)
2. No MBtree -> MBtree (veryfast -> faster)
3. No psy -> psy (faster -> fast)

That's what I would say. CRF could be variables but with better preset and other x264 setting quality. With the same CRF, the quality is not the same with ultrafast preset and slow preset. The only difference is encoding time. I already take time to make a full backup in the highest quality possible, bonuses included, I have time to give the same for the PiP. The main movie took 14 hours to encode, the secondary : 10 minutes (that is in 480p I know). Why not just let the secondary with the same quality than all the rest with 1pass, crf you want? To not say normally you should only need to touch the crf in 'one pass encoding' and the bitrate in 2 pass for your final BD size calculation. All the other parameters are for quality/encode speed already set to the beginning by the user.

[Zot]

i use powerdvd BD Edition ver 7.3
i use Imgburn and nero as UDF 2.5
the disc : verbatim dvd+DL
ClipINF Header : Blu-ray

Hi,

PowerDVD 7 has AVCHD support so that should not be the problem.

I have never used Nero, so I don't know if that will work for you or not, but imgburn has always produced good output for me.

Using clipinf.exe to set header to 100 (AVCHD) and AVCHD patcher will ensure that the index.bdmv are set to AVCHD. This could be the problem - I can't see anything else with your setup that could be the problem.

I have a Verbatim DVD-9 set to AVCHD as above burned with imgburn 2.5.1.0. I just tested with PowerDVD 7.3 Ultra and it recognized it fine. Try opening the .m2ts file with VLC Media player and see if that plays. If so, you know the .m2ts file is good and it's disc structure/layout that's the issue. You can even drag and drop the AVCHD drive right onto VLC and see if it plays.

I"m afraid that's as far as I can help. :-(

[Sharc]

Why not just let the secondary with the same quality than all the rest with 1pass, crf and bitrate you want? To not say normally you should only need to touch the bitrate for your final BD size calculation. All the other parameters are for quality/encode speed already set to the beginning by the user.
QUICK_USE_QUALITY=1 in the [Options] of the .ini does exactly what you want (The default is 0, I always set it to 1 for that reason).

[SoniG]

QUICK_USE_QUALITY=1 in the [Options] of the .ini does exactly what you want (The default is 0, I always set it to 1 for that reason).
I never used this option because I always encode in 2-pass (abr is used in first pass) and QUICK_EXTRAS=0. So this option should have no effect (that I confirm). And I've just tested it on the highest quality, one pass crf setting, and I have well the slow preset for the main movie and the same preset quality on secondary : ultrafast. So it changes nothing.

[jdobbs]

I never used this option because I always encode in 2-pass (abr is used in first pass) and QUICK_EXTRAS=0. So this option should have no effect (that I confirm). And I've just tested it on the highest quality, one pass crf setting, and I have well the slow preset for the main movie and the same preset quality on secondary : ultrafast. So it changes nothing.

I'll put a hidden option in that will allow secondaries to use the same quality selection as the primary video (but still CRF). But, IMHO changing the encoding parameters for secondaries really isn't that important -- and while I stand corrected by Dark Shikari that all CRF settings aren't equal, I've looked at both outputs and we're debating over something that just isn't that significant. If the output isn't looking good enough for you it's probably more related to my selection of "25" for the CRF value on secondaries (I was mixing this one up with how I do the extras in my previous post). I guess I should rethink that too. I was just trying to breeze through the secondaries quickly so they didn't add an inordinate amount of time to the overall job.

[Edit] I've added two new hidden options to the next release. SECONDARY_USE_QUALITY=1 will use the selected quality level for encoding secondaries and SECONDARY_CRF=n will use a specified CRF value for that encode. I warn, though, that any additional bitrate that is used for secondaries is stolen directly from the primary video...

[SoniG]

jdobbs : Yeah I understand you about speed optimization, but when you have a 1080p main movie with about 6-7 1080/480p bonuses, like this BD of Dumbo I am doing (who is laughing?...), the secondary is finally just another 480p one. When my main setting is low preset with --me umh --subme 9 etc... believe me it's not the same as ultrafast preset, --me dia --subme 0 etc... Maybe you should eventually consider this secondary as another bonus footage in the backup process, it would be clearer, with same setting for all. But I suppose you are constrained by some technical limitations and sizeable code work.

Edit : Yeah, to go to your meaning, the secondary is so often reduced to top of the main movie (at about 25%), so in theory the encode quality loss is 4 time less felt than the main movie or any full screen bonus. About crf to 25, it makes a 7500 bitrate for the movie, and 450 for the secondary. A 7000/1000 ratio should maybe be more fair.

[drmih]

i use powerdvd BD Edition ver 7.3
i use Imgburn and nero as UDF 2.5
the disc : verbatim dvd+DL
ClipINF Header : Blu-ray

I am guessing that the old version of Powerdvd (it's now on V10) isnt able to handle newer discs. Doesn't it give you some indication apart from 'unsupported' - or is that the message from the LG.

As you are using BD-Rebuilder and have said that you haven't done 'movie-only' copies, then you are doing proper blu ray copies rather than avchd, so I'm note sure the previous advice regarding avchd is valid. On the bright side, I think that the discs that you have done will turn out to be fine when you get the correct equipment / software.

[DK]

Tried 33.05's DECOMB option today for the first time as i still have severe issues with one interlaced title which came out stuttering for the last 5 or so bd-rb versions i tried it with and it failed completely:


[15:09:55] BD Rebuilder v0.33.05 (beta)
- Source: BLOOD_AND_FLOWERS
- Input BD size: 19,84 GB
- Approximate total content: [02:12:20.198]
- Target BD size: 4,27 GB
- Windows Version: 5.1 [2600]
- MOVIE-ONLY mode enabled
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[15:09:55] PHASE ONE, Encoding
- [15:09:55] Extracting A/V streams [VID_00003]
- [15:39:52] Reencoding: VID_00003 (1 of 1)
- [15:39:53] Collecting video information
- Source Video: VC-1, 1920x1080
- Rate/Length: 29,970fps, 237.968 frames
- [15:39:54] Performing CRF Prediction...
- Analyzing 28,80 19,40 27,57 26,85 26,46 26,23 [26,12]
- [15:51:46] Encoding using constant rate factor.
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
- BD-Rebuilder v0.33.05 (beta)
- Windows Version: 5.1 [2600]
- AVISYNTH Version: 2.5.8.0, not recommended version
- HAALI Splitter: Ok
- FFDSHOW: 3326, 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
[15:51:56] - Failed video encode, aborted




"C:\Programme\BD_Rebuilder\tools\x264.exe" "F:\DVD\BLOOD\WORKFILES\VID_00003.AVS" --preset veryfast --b-pyramid strict --weightp 0 --slow-firstpass --qpmin=0 --crf 26.12 --level 4.0 --sar 1:1 --aud --nal-hrd vbr --pic-struct --vbv-bufsize 14500 --keyint 24 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 17500 --tff --threads auto --thread-input --stats "F:\DVD\BLOOD\WORKFILES\VID_00003.AVS.264.stats" --pass 1 --output "F:\DVD\BLOOD\WORKFILES\VID_00003.AVS.264"




[Options]

RESIZE=0
MODE=1
AUDIO_TO_KEEP=deu;eng;ger;
SUBS_TO_KEEP=deu;eng;ger;
SD_CONVERT=0
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=0
KEEP_HD_AUDIO=1
AVCHD=1
REMOVE_WORKFILES=1
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23450
TARGET_SIZE=4369
ONEPASS_ENCODING=1
ENCODE_QUALITY=0
QUICK_EXTRAS=0
STATUS_LOG=1
PRIORITY_CLASS=0
FULL_AVCHD=0
AUTO_QUALITY=0
DEINTERLACE=1
AC3_192=0
[Paths]
SOURCE_PATH=E:\BD\BLOOD_AND_FLOWERS\
WORKING_PATH=F:\DVD\BLOOD\


btw: i have this avisynth version in use for quite some time with bd-rb and no issues so far

the same bd version and title worked fine in a testrun before WITHOUT decomb

[jdobbs]

@DK

Since DECOMB is an AVISYNTH function. Please try it with the recommended version of AVISYNTH and report back.

[SoniG]

DK : follow jdobbs advice and if the problem remain you should open VID_00003.AVS with a directshow compatible media player to see what you get.

tandi : First when you insert the disc to your pc, you should see if you can access the BD files, bdmv, certificate, m2ts files etc.. After, I'd really recommended you to install and use Arcsoft Total Media Platinum 3. It take on isos and bdmv folders (it is the only one to support this), I have also Powerdvd and Windvd and by my own experience it is just the best one. Best BD compatibility, best reliability, best non-crap protections.

[DK]

OK, installed 257 now and rerun the test

will report back

+++

pls dont worry about my chosen output size:
of course i do not expect any decent quality at all with fastest setting and 4gb size.
the only purpose was to be able to burn it to a DVD-RW media for testing purposes on the bd player as i have tried this title with different bd versions and settings over the time (all of which were not successful and resulted in a stuttering playback) so i was not willing to output to the usual 9gb for this test

btw: i did NOT maintain HD audio. at least i have picked AC3 encoding in the setup for movie only

[jdobbs]

DK : Yeah but as avisynth is used for decomb process, who knows? You should stay with recommended versions, especially for a specific avisynth version and his plugin code compatibilty. Now I don't know if to shrink a BD from 20 to 4GB in maintaining HD audio is the best thing to do. And first you should launch VID_00003.AVS with a directshow compatible media player to see what you get.

tandi : First when you insert the disc to your pc, you should see if you can access the BD files, bdmv, certificate, m2ts files etc.. After, I'd really recommended you to install and use Arcsoft Total Media Platinum 3. It take on isos and bdmv folders (it is the only one to support this), I have also Powerdvd and Windvd and by my own experience it is just the best one. Best BD compatibility, best reliability, best non-crap protections. I do movie-only encodes to BD-5 all the time. They look great.

[jdobbs]

OK, installed 257 now and rerun the test

will report backJust a note... in all previous versions BD-RB was using DECOMB by default, so it isn't really anything new.

I just tested the DECOMB selection on an interlaced 29.97 source and didn't have any issues.

Let me know if you continue to have problems, though.

If it works with 2.57 -- you may want to try reinstalling 2.58 and see if it fails again. It could have just been something that got corrupted in AVISYNTH too.

[DK]

I know you said in the change log, that decomb was not new but because of the field order change i had hopes that maybe this time it would make a change to this "problem movie" of mine

Last night i ran the title with standard settings and NO decomb and because the result was not ok I thought to give the decomb option another try.

What yould be the correct setting (inside the config) btw to maintain interlacing?
Something like: keep_interlacing=1 and deinterlace=0 ?

One more thing concerning the field order in question:
I am NOT able to load my original m2ts into DGAVCIndex - it fails preview but i can check the converted m2ts.
Is there another way to determine which field order may be in the original m2ts?

+++++

The encoding process started this time after installing 257.
Will let you know what comes out of this test and will also try 258 afterwards as well again.

[jdobbs]

I know you said in the change log, that decomb was not new but because of the field order change i had hopes that maybe this time it would make a change to this "problem movie" of mine

Last night i ran the title with standard settings and NO decomb and because the result was not ok I thought to give the decomb option another try.

What yould be the correct setting (inside the config) btw to maintain interlacing?
Something like: keep_interlacing=1 and deinterlace=0 ?

One more thing concerning the field order in question:
I am NOT able to load my original m2ts into DGAVCIndex - it fails preview but i can check the converted m2ts.
Is there another way to determine which field order may be in the original m2ts?

+++++

The encoding process started this time after installing 257.
Will let you know what comes out of this test and will also try 258 afterwards as well again. When you open BD-RB, is there a "**" or a "*" next to the frame rate in the streams list? "**" means it is a field-based source. "*" means it is using pulldown.

BD Rebuilder does a sample scan of the M2TS and looks at the TFF/RFF flags. I've tested it on a lot of sources and I'm confident it is right.

[SoniG]

I do movie-only encodes to BD-5 all the time. They look great.
Sorry, I didn't noticed it was a movie-only mode.

To encode in interlace mode you have to use : DEINTERLACE=0, it should be ok in this mode.

About image stuttering jdobbs, I saw the logs, I think I know where it come from and I already gave you my point of view about this.

[DK]

When you open BD-RB, is there a "**" or a "*" next to the frame rate in the streams list? "**" means it is a field-based source. "*" means it is using pulldown.

BD Rebuilder does a sample scan of the M2TS and looks at the TFF/RFF flags. I've tested it on a lot of sources and I'm confident it is right.

It says this:

VC-1, 1080i, 29.97fps**

[WiseWeasel]

Hi. I've been using BD Rebuilder with great success for several months, but recently hit a snag with v3304 and now v3305. BD Rebuilder has apparently stopped working since build v3304; when it gets to and AVC-encoded titles, it just fails to encode the video and stops. I've been able to reproduce this behavior on all the movies I've tried, including with the same BluRay rips that previously worked with v3208. Here's the end of the log from trying to process Law Abiding Citizen:
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 29.970fps, 27,180 frames
- [15:28:32] Reencoding: VID_00046, Pass 1 of 1
- [15:56:52] Video Encode complete
- [15:56:52] Reencoding audio tracks (if req'd)
- [15:56:52] Multiplexing M2TS
- [15:57:17] Extracting A/V streams [VID_00001]
- [16:09:54] Reencoding: VID_00001 (14 of 14)
- [16:09:54] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 169,896 frames
- Bitrate: 16,231 Kbs
- [16:09:54] Reencoding: VID_00001, Pass 1 of 1
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
- BD-Rebuilder v0.33.04 (beta)
- Windows Version: 6.0 [6002]
- AVISYNTH Version: 2.5.7.0, Ok
- HAALI Splitter: Ok
- FFDSHOW: 3326, Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libmpeg2": Ok
- FFDSHOW AVC set to "ffmpeg-mt": Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
[16:11:19] - Failed video encode, aborted
I tried ripping discs several different times, and was careful to clean the discs of any smudges before ripping, with the same results. I tried using BD Rebuilder in Full Backup and Movie Only modes. I even tried installing the latest releases of ffdshow and Haali Media Splitter, and even the 64-bit beta of Haali, all to no avail. I tried all the different ffdshow decoder options for the AVC/h.264 codec, including libavcodec and ffmpeg-mt. I'm running Windows Vista 64bit SP2 on an AMD Athlon64 X2 machine I built. This may be the same issue as Nerz was having here (http://forum.doom9.org/showthread.php?p=1387272&highlight=abiding#post1387272), along with some other problems people were having, though I wasn't able to find a working solution in this thread.

While I've been waiting for the 5-day forum account activation to take effect and allow me to post this, I've tried installing every version of all the different apps, and even grabbing a copy of the x264.exe codec from BD Rebuilder v3208, which had been working previously, all to no avail. I don't seem to be able to run version 3208 anymore to test side by side, as it reports it has expired. I'd be happy to test anything out for you to help get this resolved. Thanks for your time, and for this great software!

[sa2k9]

JDobbs,

Is there any way I can use 3 dedicated drives for

1.Source folder
2.Working folder
3.Destination folder ??


TIA.

[Ch3vr0n]

The Working folder is currently the destination folder, all finished recodes end up there. However i wouldnt mind a feature like that, could be handy yes. Although lately i'm having BDRB remove the workfiles & output folder after a successful burn. Easy way to free up the space again.

[SoniG]

WiseWeasel : First you should set back ffdshow h.264 decoding to libavcodec. Last version 0.33.05 works properly with any source format. You are in 64bit but you don't have to bother about any 64bit codecs. All codecs used by BDRebuilder will be 32bit ones. If the log say ok, your 32bit codecs installation should be ok. Install 32bit version of Media Player Classic HC (http://mpc-hc.sourceforge.net/download-media-player-classic-hc.html). From your source BD, open the file BDMV\STREAM\00001.m2ts with mpc-hc. Does it play well? If it doesn't, you should uninstall/reinstall Haali and ffdshow codecs to reset their priority use. If it's ok, double click ffdshow icon on the taskbar while playing, verify the version is well 3326...x86 in about section. Verify all ffdshow effects are unchecked. If it's ok, you should go to the WORKFILES folder where you outputted your BDR and open the VID_00001.AVS file generated by BDRebuilder with mpc-hc and see what you get. You should see the movie or an error message. If it's an error, you should uninstall/reinstall avisynth 2.5.7. If you see the movie, try to reencode the BD again. Let us informed.

[sa2k9]

The Working folder is currently the destination folder, all finished recodes end up there. However i wouldnt mind a feature like that, could be handy yes. Although lately i'm having BDRB remove the workfiles & output folder after a successful burn. Easy way to free up the space again.

This way, for a BD25, the multiplexing is taking about 20 to 25 minutes on a 7200RPM SATAii drive. If the destination folder is on a different drive, it'd be much less.

Jdobbs, is there any way we can add a line to config file to accomplish this? or could you please add this feature in the next build. TIA

[WiseWeasel]

1) ffdshow set to libavcodec.
2) Media Player Classic HC plays all the m2ts files I've tried just fine.
3) There does not seem to be a ffdshow icon appearing in my taskbar while either MPC-HC or BD RB is running. The only one I see while BD RB is running is Haali before it errors out.
4) No ffdshow effects appear to be enabled in the ffdshow video decoder configuration. I'm not sure if I'm looking in the right place, however.
5) The only VID_xxx.AVS file I see is VID_00423.AVS, and opening it in MPC-HC, it simply says "Cannot render the file". Note that manually telling MPC-HC to open and play the 00423.m2ts file does play it normally (it's a copyright notice).
6) Uninstalling and re-installing AVISynth did nothing.

Additional note: While troubleshooting, I ran into advice from jdobbs to check the registry for certain entries that should reference ffdshow's ID. I checked, and my registry seemed to be missing the directory with those keys entirely. I can't find the post now, but it may indicate that ffdshow is somehow not completely installed correctly or something. I've tried reinstalling everything multiple times though. It really seemed like version 0.33.04 broke something that was working before on this setup, and I was suspecting the new version of x264 not liking my 64-bit AMD CPU for some reason.

Oh, I will also note that mpeg2-encoded titles seem to still encode just fine in the latest builds of BD RB; it's just the AVC titles that fail.

[jdobbs]

Sorry, I didn't noticed it was a movie-only mode.

To encode in interlace mode you have to use : DEINTERLACE=0, it should be ok in this mode.

About image stuttering jdobbs, I saw the logs, I think I know where it come from and I already gave you my point of view about this. You can use DEINTERLACE=0 or you can just delete it. If it isn't there it defaults to "0" now.

[jdobbs]

Sorry, I didn't noticed it was a movie-only mode.

To encode in interlace mode you have to use : DEINTERLACE=0, it should be ok in this mode.

About image stuttering jdobbs, I saw the logs, I think I know where it come from and I already gave you my point of view about this. You can use DEINTERLACE=0 or you can just delete it. If it isn't there it defaults to "0" now. If you set DEINTERLACE=1, the output will still be interlaced -- but the difference between the two fields will be smoothed. This is especially useful when your player is attempting to play it as frames (like on a PC).

[jdobbs]

JDobbs,

Is there any way I can use 3 dedicated drives for

1.Source folder
2.Working folder
3.Destination folder ??


TIA. Not right now.

[jdobbs]

Hi. I've been using BD Rebuilder with great success for several months, but recently hit a snag with v3304 and now v3305. BD Rebuilder has apparently stopped working since build v3304; when it gets to and AVC-encoded titles, it just fails to encode the video and stops. I've been able to reproduce this behavior on all the movies I've tried, including with the same BluRay rips that previously worked with v3208. Here's the end of the log from trying to process Law Abiding Citizen:
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 29.970fps, 27,180 frames
- [15:28:32] Reencoding: VID_00046, Pass 1 of 1
- [15:56:52] Video Encode complete
- [15:56:52] Reencoding audio tracks (if req'd)
- [15:56:52] Multiplexing M2TS
- [15:57:17] Extracting A/V streams [VID_00001]
- [16:09:54] Reencoding: VID_00001 (14 of 14)
- [16:09:54] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 169,896 frames
- Bitrate: 16,231 Kbs
- [16:09:54] Reencoding: VID_00001, Pass 1 of 1
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
- BD-Rebuilder v0.33.04 (beta)
- Windows Version: 6.0 [6002]
- AVISYNTH Version: 2.5.7.0, Ok
- HAALI Splitter: Ok
- FFDSHOW: 3326, Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libmpeg2": Ok
- FFDSHOW AVC set to "ffmpeg-mt": Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
[16:11:19] - Failed video encode, aborted
I tried ripping discs several different times, and was careful to clean the discs of any smudges before ripping, with the same results. I tried using BD Rebuilder in Full Backup and Movie Only modes. I even tried installing the latest releases of ffdshow and Haali Media Splitter, and even the 64-bit beta of Haali, all to no avail. I tried all the different ffdshow decoder options for the AVC/h.264 codec, including libavcodec and ffmpeg-mt. I'm running Windows Vista 64bit SP2 on an AMD Athlon64 X2 machine I built. This may be the same issue as Nerz was having here (http://forum.doom9.org/showthread.php?p=1387272&highlight=abiding#post1387272), along with some other problems people were having, though I wasn't able to find a working solution in this thread.

While I've been waiting for the 5-day forum account activation to take effect and allow me to post this, I've tried installing every version of all the different apps, and even grabbing a copy of the x264.exe codec from BD Rebuilder v3208, which had been working previously, all to no avail. I don't seem to be able to run version 3208 anymore to test side by side, as it reports it has expired. I'd be happy to test anything out for you to help get this resolved. Thanks for your time, and for this great software! Make sure you haven't installed 64 bit versions of any of the packages. They just don't work correctly.

[jdobbs]

1) ffdshow set to libavcodec.
2) Media Player Classic HC plays all the m2ts files I've tried just fine.
3) There does not seem to be a ffdshow icon appearing in my taskbar while either MPC-HC or BD RB is running. The only one I see while BD RB is running is Haali before it errors out.
4) No ffdshow effects appear to be enabled in the ffdshow video decoder configuration. I'm not sure if I'm looking in the right place, however.
5) The only VID_xxx.AVS file I see is VID_00423.AVS, and opening it in MPC-HC, it simply says "Cannot render the file". Note that manually telling MPC-HC to open and play the 00423.m2ts file does play it normally (it's a copyright notice).
6) Uninstalling and re-installing AVISynth did nothing.

Additional note: While troubleshooting, I ran into advice from jdobbs to check the registry for certain entries that should reference ffdshow's ID. I checked, and my registry seemed to be missing the directory with those keys entirely. I can't find the post now, but it may indicate that ffdshow is somehow not completely installed correctly or something. I've tried reinstalling everything multiple times though. It really seemed like version 0.33.04 broke something that was working before on this setup, and I was suspecting the new version of x264 not liking my 64-bit AMD CPU for some reason.

Oh, I will also note that mpeg2-encoded titles seem to still encode just fine in the latest builds of BD RB; it's just the AVC titles that fail. Have you installed any "Codec Packs" or other AVC decoders? That would cause exactly the problem you're describing. If so, remove all codec packs. FFDSHOW has everything you need, and these packs are notorious for screwing up the process.

[SoniG]

You can use DEINTERLACE=0 or you can just delete it. If it isn't there it defaults to "0" now. If you set DEINTERLACE=1, the output will still be interlaced -- but the difference between the two fields will be smoothed. This is especially useful when your player is attempting to play it as frames (like on a PC).

Problem jdobbs is that decomb without the dthreshold to 0 will forget some fields line that should be deinterlaced, and so I'm agree, a part will be smoothed, I would much say 'field blended', but another part will be artefacts irrelevant to any logical, and reinterlacing after is even worse and not done for that. You decomb, it's progressive. You interlace progressive, you take more artefacts because there is no fields anymore. And a deinterlacer is made to transform your footage to progressive and be played by your pc as frames as you say, you don't need to interlace anything after. Or we keep fields interlaced and we let the player play with the fields. Fields will be deinterlaced by the player by frame blend (as decomb do), or Bob (double framerate that also exist as a avisynth plugin). But trust me there is nothing else valuable. Any other processes are artefacts, or jerky results in motion as somes will complain because x264 with --tff... will recreate irrelevant fields from deinterlaced, smoothed or whatever frames.
As the full example I sent you. Really look at motions on any bonuses, you will see strange lines that comes from nowhere. It's not fields, it's not frames, it's artefacts, generated by decomb and x264. Now I let you think about it and will not talk about this anymore. If you want to discuss more about it, we could maybe chat or you can PM me.

WiseWeasel : I think your ffdshow install/priority set is the issue. Don't think installing BDRebuilder messed something. First there is no installer and the only mess that could occured would be from ffdshow/Haali/Avisynth or other codec packs installations. BDRebuilder do nothing apart from using these elements. So you say you can play m2ts files but you don't see any ffdshow icon on the taskbar. That's not a good thing, and maybe you play the file with another codec than ffdshow, and this would be the problem. You should try to analyse which codec is actually playing your AVC/H.264 files. Open one of them with mpc-hc, right click on the movie and see what you have on the 'Filters' section. Find the codec which is playing the video and you will have to find the way to lower his priority or disable it from your system (MMCompView), until ffdshow take the control of your AVC videos. Be sure before to well set on the ffdshow video decoder config, AVC to libavc and VC1 to wm9. You can set the merit/priority there too. Good luck, I think you have definitely a codec conflict and you will have to get rid of it. Try to find tools : Codec Tweak Tool, GraphStudio, and MMCompView to enable/disable any codecs to test your installation. As jdobbs asked you, remove any other codecs and codecs pack, even 3rd parts from Adobe Premiere/After Effects installs, Mainconcept or whatever.

[jdobbs]

@SoniG

The reason it has to stay flagged as interlaced even when deinterlacing (at least on 720x480 sources) is because the blu-ray standard doesn't support progressive streams at 29.97fps on primary video.

I think in most circumstances now that X264 inherently supports, it is better just to leave it as-is and not deinterlace. That's why I changed the default. But some folks like the look better with the source is deinterlaced -- so the option remains.

[SoniG]

Damn are you sure? Because that's what I did with Batman 1989 bonuses. I reencoded as 29.97 480p and of course on TMT3 it worked well. Finally I'm surprised, and I'm not. I would say to you the only solution would be to let these footages as interlaced, or is there a way to pulldown them (I sux on pulldowns), or transform them as 720p or something compatible? But I think if nothing is compatible, the best way is to keep those footages as is. And believe me deinterlace+interlace, it doesn't exist. But if it would only doesn't exist I would even don't bother you with that, but the problem is it doesn't exist, and in encoding deinterlaced footages as interlaced, it creates artefacts, and it's not logical. And for what can be deinterlaced, to say, no many things anymore, decomb gives artefacts too. You just had to remove his 'motion detection' or 'luma detection' something or whatever, in using what I told you. Do the test with any high motion footages, play them as progressive on your PC and you will notice the same thing than me, there is no reason. I really tell you that to guarantee you free artifacts footages. If you stay with these settings, you can send me any processed footages, I will show you where it's wrong.

[WiseWeasel]

OK, great news guys! Thanks for all your help, SoniG and jdobbs! So, after not being able to figure out what codec was actually being used in MPC-HC, I decided to simply go use the 'Uninstall Programs' function in the control panel to remove all the tools one more time (I had previously used the individual uninstallers), in addition to some Cannon camera software I think one of my roommates installed which happened to be running an h.264 decoder according to Installed Codecs and DSFMgr, and Real Software, which I had installed at some point. After uninstalling everything, I installed the correct versions of ffdshow, haali and AVISynth once more, and now BD RB works perfectly again. Unfortunately, since I uninstalled everything all at once, I didn't really get to see what exactly was causing the problem, but it's working now, so I'll go sacrifice a chicken to the version dependency gods and pray that BD RB and RipBot can play nicely together. Now that I think about it, I was messing around with RipBot around the time v3304 came out, so maybe that's when I managed to screw something up in one of the libs.

[SoniG]

WiseWeasel : Yeah don't bother what caused the issue, it was an obscure and scary one. Happy you got rid of it. If you use Ripbot, I advise you to always keep ffdshow/haali/Avisynth versions recommended by jdobbs. Don't touch anything and you will be able to encode with BDRB, Ripbot, play movies and whatever. You can even create 'auto presets' on ffdshow following your needs. Ripbot will always work with BDRB recommendations, and soon, you will even not need Ripbot anymore, and you will be able to thank jdobbs for that too ! :) Good encodes!

[jdobbs]

Damn are you sure? Because that's what I did with Batman 1989 bonuses. I reencoded as 29.97 480p and of course on TMT3 it worked well. Positive. Some players will play 480p@29.97... but it is very definitely not compliant. The only place where 480p@29.97 is accepted is for secondary video that is being played with a 720p source @ 59.94fps.

No progressive stream at all is allowed for 720x480 or 720x576 when it is primary video -- not even 23.976 or 24fps. If you do have a 23.976 stream @720x480, it has to include pulldown flags making it 29.97i.

[SoniG]

Ok, you make me things clearer now, all these footages tagged 480i here and 480p pulldown there. I hope more and more new productions will be provided all in hd progressive, and at worst, just interlaced. I will take a look at all these BD compliancy rules.

[8ternity]

Hi jdobbs;

I've god an issue about version 33.05;

1rst: 1920x1080 m2ts : video mouvements is saccaged; jerky movements,.. i dont know if i explain you correctly, but when the peoples moves, camera moves, mouvements are not fluid.

2nd: Compression ratio is too high, poor quality for any videos likes bonus features, previews, etc. Main movie is look to be okay. Poor quality for 720x480 29.97 FPS

Here two samples about the issue point #1 and #2.

#1 sample:
http://rapidshare.com/files/379045164/sample.split.89.m2ts.html

#2 sample:
http://rapidshare.com/files/379049887/00013.m2ts.html

Thank You.

EDIT:

Settings ini:

[Options]
MODE=0
ENCODE_QUALITY=0
AUTO_QUALITY=1
TARGET_SIZE=23200
AUDIO_TO_KEEP=all
SUBS_TO_KEEP=all
SD_CONVERT=0
COLOR_BOOST=0
RESIZE_1080=0
DEINTERLACE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=0
REMOVE_WORKFILES=1
FULL_AVCHD=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23450
ONEPASS_ENCODING=2
[Paths]
SOURCE_PATH=E:\BDR\BAD_LIEUTENANT\FULLDISC\
WORKING_PATH=E:\BDR\BAD_LIEUTENANT_REBUILDED_3305\


Log:

-----------------------
[08:21:36] BD Rebuilder v0.33.05 (beta)
- Source: FULLDISC
- Input BD size: 23,28 GB
- Approximate total content: [03:12:07.048]
- Target BD size: 22,66 GB
- Windows Version: 6.1 [7600]
- One Pass ABR Mode enabled
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[08:21:36] PHASE ONE, Encoding
- [08:21:36] Extracting A/V streams [VID_00006]
- [08:21:37] Reencoding: VID_00006 (1 of 7)
- [08:21:37] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 214 frames
- Bitrate: 14*585 Kbs
- [08:21:37] Reencoding: VID_00006, Pass 1 of 1
- [08:21:47] Video Encode complete
- [08:21:47] Reencoding audio tracks (if req'd)
- [08:21:47] Multiplexing M2TS
- [08:21:48] Extracting A/V streams [VID_00013]
- [08:21:52] Reencoding: VID_00013 (2 of 7)
- [08:21:52] Collecting video information
- Source Video: MPEG-4 (AVC), 720x480
- Rate/Length: 29,970fps, 3*837 frames
- [08:21:52] Reencoding: VID_00013, Pass 1 of 1
- [08:22:11] Video Encode complete
- [08:22:11] Reencoding audio tracks (if req'd)
- [08:22:11] Multiplexing M2TS
- [08:22:12] Extracting A/V streams [VID_00011]
- [08:22:22] Reencoding: VID_00011 (3 of 7)
- [08:22:22] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 3*649 frames
- [08:22:22] Reencoding: VID_00011, Pass 1 of 1
- [08:23:40] Video Encode complete
- [08:23:40] Reencoding audio tracks (if req'd)
- [08:23:40] Multiplexing M2TS
- [08:23:43] Extracting A/V streams [VID_00008]
- [08:24:24] Reencoding: VID_00008 (4 of 7)
- [08:24:24] Collecting video information
- Source Video: MPEG-4 (AVC), 720x480
- Rate/Length: 29,970fps, 24*727 frames
- [08:24:24] Reencoding: VID_00008, Pass 1 of 1
- [08:26:50] Video Encode complete
- [08:26:50] Reencoding audio tracks (if req'd)
- [08:26:50] Multiplexing M2TS
- [08:26:56] Extracting A/V streams [VID_00012]
- [08:27:40] Reencoding: VID_00012 (5 of 7)
- [08:27:40] Collecting video information
- Source Video: MPEG-4 (AVC), 720x480
- Rate/Length: 29,970fps, 37*048 frames
- [08:27:40] Reencoding: VID_00012, Pass 1 of 1
- [08:30:23] Video Encode complete
- [08:30:23] Reencoding audio tracks (if req'd)
- [08:30:23] Multiplexing M2TS
- [08:30:28] Extracting A/V streams [VID_00009]
- [08:31:54] Reencoding: VID_00009 (6 of 7)
- [08:31:54] Collecting video information
- Source Video: MPEG-4 (AVC), 720x480
- Rate/Length: 29,970fps, 56*084 frames
- [08:31:54] Reencoding: VID_00009, Pass 1 of 1
- [08:36:42] Video Encode complete
- [08:36:42] Reencoding audio tracks (if req'd)
- [08:36:42] Multiplexing M2TS
- [08:37:02] Extracting A/V streams [VID_00000]
- [08:45:24] Reencoding: VID_00000 (7 of 7)
- [08:45:24] Collecting video information
- [08:45:24] Keeping original video (no reencode)
- [08:45:24] Reencoding audio tracks (if req'd)
- [08:45:24] Multiplexing M2TS
[08:55:02]PHASE ONE complete
[08:55:02]PHASE TWO - Rebuild Started
- [08:55:02] Rebuilding BD file Structure
[08:55:06] - Encode and Rebuild complete
- WORKFILES folder removed.
[08:55:08]JOB: FULLDISC finished.


Fulldisc:

[Status]
LABEL=FULLDISC
VERSION=v0.33.05 (beta)
SOURCE_SIZE=24999965565
SOURCE_VIDEO_SIZE=24807383040
TARGET_SIZE=24326963200
REDUCTION=.972870884288164
RESIZE_1080=0
AUDIO_TO_KEEP=all
SUBS_TO_KEEP=all
BACKUP_MODE=0
MOVIEONLY_TYPE=0
QUICK=1
ENCODE_STEP=0
COMPLETED=7
REBUILD_COMPLETE=1
[00006]
AUDIO=1111
PGS=
M2TS_TARGET=19761016
RATE=14585
NSIZE=19814400
FLINK=0
MLINK=0
USE_ORIGINAL=1
[00013]
AUDIO=1
PGS=
M2TS_TARGET=138392860
NSIZE=45287424
FLINK=0
MLINK=0
[00011]
AUDIO=1
PGS=
M2TS_TARGET=352841124
NSIZE=141459456
FLINK=0
MLINK=0
[00008]
AUDIO=1
PGS=
M2TS_TARGET=1453283431
NSIZE=333066240
FLINK=0
MLINK=0
[00012]
AUDIO=1
PGS=
M2TS_TARGET=1613045205
NSIZE=318019584
FLINK=0
MLINK=0
[00009]
AUDIO=1
PGS=
M2TS_TARGET=3028043910
NSIZE=1013925888
FLINK=0
MLINK=0
[00000]
AUDIO=1111
PGS=1
M2TS_TARGET=22262807683
USE_ORIGINAL=1
NSIZE=18000046080
FLINK=0
MLINK=0

[DK]

It took me quite a while to get back to you and I had a lot of re-tries/re-installations since then:

When I said the conversion started I was right only for a couple of minutes because then again it failed and after some retries BD RB said: I cant - Failure.
Since I had installed Avisynth 257 by then and all else was OK according to Inspect I had no clue what was going on and tried again and again... to no avail.

I went back to the setting WITHOUT decomb - same problem!
Uninstalled FFDSHOW and reinstalled it - same problem!
Used 3304 instead of 3305 with and without decomb - same problem!

I could not believe that the title did not work or go beyond the stage of the CRF prediction because hours before it completed fine in a 2 pass mode!

So after hours of trying I decided to NOT use 1 pass CRF for this quick test but set 2 pass and guess what: the conversion works fine again.

I have absolutely no idea what is going on here but I can NOT use CRF mode with this title.
Any infos I can provide?

[kanerulz69]

is there a difference in speed between idle priority and normal priority? cause when i use bd rebuilder, i dont run anything else, and exit out of anything im not using in the system tray?

[SoniG]

8ternity : You should tell which settings you used. Sample 2 seems to be an original.

DK : Your issue is strange, it seems to be a crf issue, as normally in 2pass mode, abr is used. So if you want to encode this in 1 pass, try one pass ABR encoding.

kanerulz69 : idle priority will just lower the process priority of x264. It just useful if you want to encode in keeping using your computer. Your other tasks will have priority. Of course more you use your computer, longer the encode will be. If you do nothing and don't have greedy tasks, it would have no effect and you can even set it to normal. Number of threads is also an important value. By default, threads is set to auto, it will create 1,5 x you number of cores. For a 4 cores machine it will encode with 6 threads. So it will maximise your encode speed. If your machine respond too bad, you can lower this number in the BDRebuilder config file.

[jdobbs]

@8ternity

Something is fishy in your post. I look at it and it is telling me that you completed that entire disc (23.8GB) in about 34 minutes. That's just not feasible.... it's also saying the biggest thing on the disc is only 57,084 frames (about 31 minutes).

I have to believe you're preprocessing the disc in some way -- either that or you're editing what is being posted. I don't accept bug reports on preprocessed sources. My experience is that 99% of the time the problem is caused in the preprocessing.

I also noticed that the bitrate is being shown on one of the encodes, but not on the others. Are you editing the log before you're posting it? How does the verbose reporting change midstream?

What gives?

[Manuel Marques]

First of all, thank you very much for your EXCELENT program!
I use a VAIO AW11Z PC with VISTA Home, WMediaPlayer11, and BD-RB v0.33.05(beta) with Haali Media Spliter 1.10.120.15 and Avysinth 2.6.0.1. latest versions (instead of Haali MS 1.9.42.1 and Avysinth 257).
With H.264 video streams BD-RB functions PERFECTLY!
But it doesn't encode VC-1 video streams (I've selected the "wmv9" codec).
There's anything I can do?
Thanks again.

[Manuel Marques]

When I said H.264 video files I mean MPEG-4 (AVC) video files. The problem is ONLY with the VC-1 video files.

[jdobbs]

First of all, thank you very much for your EXCELENT program!
I use a VAIO AW11Z PC with VISTA Home, WMediaPlayer11, and BD-RB v0.33.05(beta) with Haali Media Spliter 1.10.120.15 and Avysinth 2.6.0.1. latest versions (instead of Haali MS 1.9.42.1 and Avysinth 257).
With H.264 video streams BD-RB functions PERFECTLY!
But it doesn't encode VC-1 video streams (I've selected the "wmv9" codec).
There's anything I can do?
Thanks again. Check and make sure you don't have any "Codec Packs" or programs that may have another VC-1 codec installed. These can override FFDSHOW. While FFDSHOW's "wmv9" will decode all types of VC-1 while others have issues.

If you've installed a codec pack -- uninstall it. FFDSHOW has all the CODECs anyone ever needs.

Also, while I'm sure you know what you're doing -- you have to use the software listed in the first post of this thread. The odds are good that the version of HAALI you have installed isn't splitting VC-1 correctly. I've seen it before. Additionally you are using a version of AVISYNTH that is obviously not what is supported and isn't even considered stable yet. I don't mean to be rude, but it's just not appropriate to post a bug report here when you are already aware that you aren't using the right software and haven't even tried to correct it.

Last but not least... if you did a search of the postings in this thread you'll see that this subject has been discussed about a gazzillion times already. Again, I don't like being difficult, but people seem to think that their time (doing a search) is much more valuable than mine (answering the same question over-and-over) -- and I think that's inconsiderate.

No hard feelings... but every now and then I have to reemphasize the rules (look up DOOM9 forum rule 1a).

[Manuel Marques]

You are absolutely right, I'm very sorry but I've read the guide by milOtis (pag.4) where he says:"The versions below are considered the minimum versions, while any builds that came after the ones listed are also compatible."
My behaviour doesn't mean any inconsideration for you. I have THE MAXIMUM consideration for you because I think that your program is a PUBLIC SERVICE.

The VC1 video files are noe beeing PERFECTLY encoded.

Thank you very much again for your pacience for newbies like me.

[setarip_old]

@ManuelMarques

Hi!I'm very sorry but I've read the guide by milOtisThat's outdated...

[drmih]

I have come across a similar bug to one I mentioned earlier. 'The Last Emperor', when encoded to bd-9 lost the audio. Although the original, and HDD rip played fine, the encoded one with Dolby Digital 64kbs wouldn't play and tsmuxer reported it as an unsupported file type. I got around it by encoding to bd-25 and keeping the audio. However, I have just had exactly the same with Clash of the Titans (the original one). That had an audio track of DTS-HD which became DD64kbps. Once again it won't play and tsmuxer says it's not supported.

[Shuttle99]

jdobbs, I have backed up a couple movies only with 1pass 33.04 and it would take about 2 hours and now 33.05 1pass takes about 4.5 hours so I redid it with 33.04 and it took 2 hours and 20 min. Not sure what changed between versions but it was not good time wise.