BD Rebuilder Beta - Bug Reports Only

[GaPony]

Wolfe, how about starting a new thread to discuss this further. I have a similar setup to you. We can try to dissect this one point at a time to see where the failure is coming from. According to the change list, there were really only moderate changes from v.0.21.01 to 0.22.01, except for new versions of x264.exe and tsMuxer, and only minor changes between 0.22.01 and 0.22.02. It shouldn't be that difficult to find where things went wrong after reviewing some logs and settings... I can take your settings and see if I come up with the same failure. :)

[Capsbackup]

Were do i add the "MIN_M2TS= ****
Sorry for being a noob!

It's in the changes log that comes with BD-RB. Look under the changes for March 7th, 2009 - v0.20.03.

[colinhunt]

Does "Keep HD audio for BD25 encoding" apply to PCM 7.1 tracks as well, or will BD-RB always try to re-encode PCM 7.1 tracks regardless of settings under Audio Encoding Options?

Forcing PCM 7.1 re-encode does not work since Aften A/52 encoder does not support 7.1 channel audio. Neither does AC-3, for that matter. Eac3to is able to do 7.1 > 5.1 channel downmix so there's one possible solution. Replacing Aften with eac3to altogether might not be a bad idea either.

edit: based on a couple of test runs PCM 7.1 tracks are not re-encoded when target is BD25 and "Keep HD audio for BD25 encoding" is enabled. I also tried setting target size manually to 8142MB (which should be above the DVD9 limit) to see what would happen to PCM 7.1 tracks: BD-RB tried to re-encode PCM 7.1 track and process stopped at Aften error message.

[Mr. Movies]

@Mr. Movies

Hi!Please explain what you mean by "encoding videos manually"...

Please forgive me as it has been some time since I dealt with that so this is to the best of my recollection.

The BD version of Max Payne starts with an opening scene of guns firing and rotating. It is a long sequence and has the gun(s) firing but then has dead silence in between each gun sequence. This is a 6 channel PCM stream but the rest of the movie is AC3 6 channel. I was using ProCoder3 to convert the BD9 rip to DVD9-IFO and the opening PCM sequence was getting way, way, out of sync I believe due to the dead silence as I also ran into issues converting the LOGO screens with dead silence as well. With the studio logo screen lasting lets say 7 seconds and a muted audio track my output from ProCoder would be a flash, less then a second even though in ProCoder the steam reported duration of 7 seconds. To get around this I had to record a muted audio track, duration of 7 seconds, and seam it to the video track in ProCoder and then all was well. With the opening scene of gun sequences I took the PCM 6 channel and converted it to AC3 6 channel and re-encoded the separate audio & video tracks back together. I need to go back and do this all over again as when I stitched the streams together I’m not getting a smooth transition and it is annoying, I just haven’t had the time lately.

Again please excuse me If I’m not totally accurate here and I didn’t take the time to prove my point hands down obviously there could be other stuff going on here. I hope that helps explain what I meant for you setarip_old.

[Mr. Movies]

Audio Sync Problems
Does anyone have any ideas for me to try to get this audio to sync on my first episode of Firefly disc. I’ve now tried to convert the audio to AC3 but that was almost worst then just leaving the audio HD but did the same thing around 8 minutes in just as the movie goes to what should be a commercial break and back to the Firefly opening logo screen the sound track is off. I haven’t timed the separate audio track rip but have listened to it and it most likely is off so maybe to get around this I need to edit the audio track separately and strip out the excess time as the rest of the episode seems to remain around 4 seconds out.

Again any ideas?

[Furiousflea]

Does "Keep HD audio for BD25 encoding" apply to PCM 7.1 tracks as well, or will BD-RB always try to re-encode PCM 7.1 tracks regardless of settings under Audio Encoding Options?

Forcing PCM 7.1 re-encode does not work since Aften A/52 encoder does not support 7.1 channel audio. Neither does AC-3, for that matter. Eac3to is able to do 7.1 > 5.1 channel downmix so there's one possible solution. Replacing Aften with eac3to altogether might not be a bad idea either.

edit: based on a couple of test runs PCM 7.1 tracks are not re-encoded when target is BD25 and "Keep HD audio for BD25 encoding" is enabled. I also tried setting target size manually to 8142MB (which should be above the DVD9 limit) to see what would happen to PCM 7.1 tracks: BD-RB tried to re-encode PCM 7.1 track and process stopped at Aften error message.

Can't replace aften with eac3to cos eac3to is just a frontend in terms of encoding operations. It requires paid software to work optimally. Check the OP of the eac3to thread for details.

[colinhunt]

Can't replace aften with eac3to cos eac3to is just a frontend in terms of encoding operations. It requires paid software to work optimally. Check the OP of the eac3to thread for details.
Ah, so it is. My bad.

[Capsbackup]

Please forgive me as it has been some time since I dealt with that so this is to the best of my recollection.

The BD version of Max Payne starts with an opening scene of guns firing and rotating. It is a long sequence and has the gun(s) firing but then has dead silence in between each gun sequence. This is a 6 channel PCM stream but the rest of the movie is AC3 6 channel. I was using ProCoder3 to convert the BD9 rip to DVD9-IFO and the opening PCM sequence was getting way, way, out of sync I believe due to the dead silence as I also ran into issues converting the LOGO screens with dead silence as well. With the studio logo screen lasting lets say 7 seconds and a muted audio track my output from ProCoder would be a flash, less then a second even though in ProCoder the steam reported duration of 7 seconds. To get around this I had to record a muted audio track, duration of 7 seconds, and seam it to the video track in ProCoder and then all was well. With the opening scene of gun sequences I took the PCM 6 channel and converted it to AC3 6 channel and re-encoded the separate audio & video tracks back together. I need to go back and do this all over again as when I stitched the streams together I’m not getting a smooth transition and it is annoying, I just haven’t had the time lately.

Again please excuse me If I’m not totally accurate here and I didn’t take the time to prove my point hands down obviously there could be other stuff going on here. I hope that helps explain what I meant for you setarip_old.

I backed up the Region 1, NTSC version of Max Payne to movie only BD-5 and it worked perfectly. I have never heard of an audio track having PCM and AC3 together!
BD9 to DVD9-IFO???
This is the BD Rebuilder bug reports thread!!

[jdobbs]

I backed up the Region 1, NTSC version of Max Payne to movie only BD-5 and it worked perfectly. I have never heard of an audio track having PCM and AC3 together!
BD9 to DVD9-IFO???
This is the BD Rebuilder bug reports thread!! It can't. Doing so would violate specs...

[jdobbs]

@jdobbs

Just curious... what's the minimum custom target size that can be used before HD audio isn't kept (with the option to keep HD audio enabled)?

Keep up the amazing work! I assume BD-25 when the setting is greater than 8500.

[Mr. Movies]

I backed up the Region 1, NTSC version of Max Payne to movie only BD-5 and it worked perfectly. I have never heard of an audio track having PCM and AC3 together!
BD9 to DVD9-IFO???
This is the BD Rebuilder bug reports thread!!

You are not reading my post correctly nor have you read prior to it as it is a response to a question asked about what I meant when I had an issue of manually encoding around audio sync issues and and dead silence in a stream.

Yes, I too have ripped Max Payne sucessfully to a BD9 but I ran into an issue when trying to convert it to an IFO/VOB or DVD-IFO format, which isn't really meant for this thread, and NO there were not both PCM and AC3 in the same stream, I NEVER stated that you read into it.

This was not directed at you nor do you need to respond to it. If you wish to try your luck at the real problem I'm having with BD-RB then please read, comprehend, my posts about BD Audio Sync problems with Firefly as I'm open to suggestions on that otherwise this is worthless and doesn't need to be continued.

[colinhunt]

I assume BD-25 when the setting is greater than 8500.
Ah, that's good to know, thanks!

[MILLZY]

drmih just cannot seem to get this right:

[21:02:33] BD Rebuilder v0.22.02 (beta)
- Source: THE_MUMMY_TOMB_OF_THE_DRAGON_EMPEROR
- Input BD size: 45.81 GB
- Approximate total content: [04:26:51.219]
- Target BD size: 22.46 GB
[21:02:36] PHASE ONE, Encoding
- [21:02:36] Extracting audio/subs [VID_00009]
- [21:19:56] Reencoding: VID_00009 (1 of 51)
- [01:55:27] Extracting audio/subs [VID_00010]
- [01:56:36] Reencoding: VID_00010 (2 of 51)
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
[05:36:37] - Failed video encode, aborted

i have placed the MIN_M2TS in the config file,or have i placed it in the wrong place.I still get Encode failed. have attached ini:

[Options]
MIN_M2TS=2100
RESIZE=0
MODE=0
QUICK_EXTRAS=0
MINIMIZE_TO_TRAY=1
TARGET_SIZE=23000
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
TRELLIS=1
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=1
AC3_640=1
KEEP_HD_AUDIO=0
AVCHD=1
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23450
AUTO_BURN=0
PRIORITY_CLASS=1
VERBOSE_STATUS=0
ENCODE_QUALITY=0
[Paths]
WORKING_PATH=L:\BD-REBUILDER WORK FILES\
SOURCE_PATH=L

[Capsbackup]

@MILLZY;
Should be "MIN_M2TS_SIZE=2100".
Check inside the BD-RB zip file for the changes text doc.( March 7th, 2009 - v0.20.03 & May 4th, 2009 - v0.20.08).
It's not going to work unless it is worded correctly. :)

EDIT: Do not use quotes though! ( MIN_M2TS_SIZE=2100 )

[Capsbackup]

I just completed a full movie backup of The Mummy, Region 1, NTSC, to BD-25 with BD-RBV02202, and even though it completed successfully, the main movie will not play. All the extras and menu play back fine, but when I select Play for the main movie, it just plays the intro warnings, and the counter goes to zero and never starts the movie. Play back is on PowerDVD 7. The corresponding .m2ts file plays back fine with MPC.
This is a PIP version Blu-Ray, so could this be the reason it does not work?
I thought the main movie should play but without the PIP option available.

[MILLZY]

@MILLZY;
Should be "MIN_M2TS_SIZE=2100".
Check inside the BD-RB zip file for the changes text doc.( March 7th, 2009 - v0.20.03 & May 4th, 2009 - v0.20.08).
It's not going to work unless it is worded correctly. :)

EDIT: Do not use quotes though! ( MIN_M2TS_SIZE=2100 )

Have changed that m8,Will try again.Let you know when its done!
Thanks very much to you and drmih..........

[user822]

hi guys!

i have the problems with VC1 1080i

i had two working decoders with hight merit in graphstudio but both did NOT work with avisynth/x264

VC1-tweak also does not work for me

Is there any other chance to convert this disc?

greetings
user

[drmih]

Have changed that m8,Will try again.Let you know when its done!
Thanks very much to you and drmih..........

You know if you've got it right as before you start look at the stream window in bd-rb. Without the edit you will see all of the sizeable streams but after you've set it to 2100 there should only be the main movie showing. No need to waste time waiting for it to go wrong.

[PurpleMan]

Hi,

I just finished doing the movie "21" using BD-Rebuilder to BD25.

I thought everything was perfect, until I was lucky enough to catch this (http://g.imagehost.org/view/0924/corrupt) while playing the movie.

This is not a decoding problem, the frame is actually encoded like that in the BD-Rebuilder produced file (has several seconds of corruptions). I also made sure that there's no problem decoding the original m2ts using the .avs BD-Rebuilder used for encoding.

Anybody have a clue what could have caused it?

It got me all worried that my other backed up BD's have the same thing somewhere throughout the movie.

[MILLZY]

You know if you've got it right as before you start look at the stream window in bd-rb. Without the edit you will see all of the sizeable streams but after you've set it to 2100 there should only be the main movie showing. No need to waste time waiting for it to go wrong.


Exactly as you said,Thanks very much........:thanks:

Forgot to mention.Doing it by MIN_M2TS will it be just movie only or will the extras still be intact?

[user822]

finally i fixed the VC1 1080i Problem by using ffdshow :rolleyes:

[drmih]

Exactly as you said,Thanks very much........:thanks:

Forgot to mention.Doing it by MIN_M2TS will it be just movie only or will the extras still be intact?

You make me smile!!

As the problem file is an extra, if you were only doing movie-only it would be included. However, to answer your question it will be a full disc copy but only the movie will be re-encoded - the others will just be copied intact.

[jdobbs]

Hi,

I just finished doing the movie "21" using BD-Rebuilder to BD25.

I thought everything was perfect, until I was lucky enough to catch this (http://g.imagehost.org/view/0924/corrupt) while playing the movie.

This is not a decoding problem, the frame is actually encoded like that in the BD-Rebuilder produced file (has several seconds of corruptions). I also made sure that there's no problem decoding the original m2ts using the .avs BD-Rebuilder used for encoding.

Anybody have a clue what could have caused it?

It got me all worried that my other backed up BD's have the same thing somewhere throughout the movie.Likely a bad rip -- at least it has been on the ones I've seen that issue before -- you saw it a lot in some of the earlier versions of AnyDVD-BD before they perfected their ripping.

What did you use to rip it? Have you checked the source?

[jdobbs]

I'm posting this here directly as opposed to the first post of the thread because I've made a lot of code changes that might cause new issues, and would like to have some testing done by the people who acually read this thead before the "grab it and go" guys have a chance to lambast me. Also, please let me know soonest if there are still any issues with the 50% completion bug. Since I cannot repeat it, it is a compete guessing game for me. Here are a summary of the changes:

June 18th, 2009 - v0.22.03
- Added the --fps parameter to the X264 command line
to circumvent possible inconsistencies in source
frame serving.
- Added code to detect pulldown in VC-1 sources and
perform special handling (e.g. auto removal).
- Changed the method of updating the progress bar
back to that in v0.21.01. It seems the O/S isn't
consistent returning window handles on some systems.
- Corrected an error in which field deinterlacing
could fail when the output of the source codec was
not YUY2 or YV12.
- Corrected an issue related to sources with pulldown
that could result in audio synch errors.
- Changed the default value of the FIX_CLPI hidden INI
setting. The CLPI errors were fixed in TSMUXER and
this is typically no longer needed. If you are using
an older version of TSMUXER rather than the one that
is shipped with BD-RB, however, please add FIX_CLPI=1
to the "Options" area of your config (INI) file.
- Fixed some overall progress reporting errors when
resuming a movie-only encode.
- Added code to identify troublesome (field based)
VC-1 interlaced files. In BD-25 backups they are (if
not the main-feature) automatically copied intact to
prevent CODEC failures during encoding with X264.
NOTE: Setting the RESIZE option will disable this
feature.
- Added two flags to the streams list following the fps
indicator. "*" means the source is PULLDOWN. "**"
(BD5/9 only) means the source is FIELD BASED interlaced
VC-1 and will be BLANKED during reencoding. Audio
will playback correctly, but with a blank screen. This
is required in order to prevent CODEC failures on these
sources. If you see a lot of "**" flags, you may want
to consider movie-only mode.
- Added a hidden option called "DISABLE_VC1_FIX=1" this
will disable the the two changes above (intact copy and
blanking) -- just in case a CODEC is discovered that
properly handles these streams. Flags will still be
displayed.
- Added code to detect when a video source does not
require encoding to meet target size goals, and keep it
intact. Please note that the decision contains more
than meets the eye. For example, if an M2TS is a part
of more than one MPLS and a component portion of the
other cannot be kept intact -- it may not qualify and
requires encoding.
- Other minor corrections and cosmetic fixes.

Please pay attention to the last couple non-cosmetic changes. Don't be surprised when a previous source that would crash the CODEC and cause an X264 failure now becomes a blanked screen.

You can download this version from this link (http://www.jdobbs.net/freeware/BD-RBV02301.ZIP).

[PurpleMan]

Likely a bad rip -- at least it has been on the ones I've seen that issue before -- you saw it a lot in some of the earlier versions of AnyDVD-BD before they perfected their ripping.

What did you use to rip it? Have you checked the source?

Hi jdobbs, thanks for replying.

Like I said, I checked that if I open the .avs file that bd-rb used, the frames there are NOT corrupted (meaning that the source m2ts is fine). It either got corrupted by x264 or by the decoder from some reason while serving it.

I repeated the encode only for that particular m2ts (same avs, same bd-rb commandline for 1st/2nd passes) - and it resulted in a good encode this time.

I am quite bothered at what could have caused it to screw up like that on the first go.


And another bug I noticed, the abovementioned movie ("21") is split to several m2ts's on the original disc with no consistency to the division. meaning, 00133.m2ts is first hour, then 00134.m2ts is another 6 minutes, then another 35 seconds, then another 1 hours, etc. The movie is "glued" together on the disc using a playlist (obviously). After running BD-RB on it, when playing the movie, whenever it crosses a point in which it switches from one m2ts to another, there is an audio gap that makes it noticeable it's switching files. that gap does not exist on the source disc nor the ripped-to-hd version. I think that this could be caused by even the slightest deviation in the number of frames decoded by directshow as opposed to the amount coded on the original m2ts (1 frame difference would result in that gap).

Anyways, I think that's worth looking into. As a side note, any particular reason you chose not to use the DG indexing tools for the frameserving? (DGAVCIndex, DGIndex and DGVC1Index)
Seems like it's kind of a mess using "directshowsource" as each person has a different decoder installed on his system. For instance, I use ffdshow for vc1/mpg2 and coreavc for avc.

Keep up the good work, it is greatly appreciated.
I'll keep reporting and testing, doing whatever I can do to help.

Regards,
-PurpleMan

[Capsbackup]

Thanks jdobbs, you have been busy!! :eek:
I am looking forward to testing this new version.
Have you any input on if a PIP movie can be backed up to a full movie successfully? I just tried The Mummy Returns, and it has the same results as The Mummy, where the menu and extras all play fine, but the main movie will not play.

[drmih]

Thanks jdobbs, you have been busy!! :eek:
I am looking forward to testing this new version.
Have you any input on if a PIP movie can be backed up to a full movie successfully? I just tried The Mummy Returns, and it has the same results as The Mummy, where the menu and extras all play fine, but the main movie will not play.

This is standalone specific (panasonic??), as they are fine on a pc or a sony standalone, although the pip feature is not available everything works fine to bd-25.

[Capsbackup]

This is standalone specific (panasonic??), as they are fine on a pc or a sony standalone, although the pip feature is not available everything works fine to bd-25.

I did not burn to BD-RE, since the main movie would not even play with PowerDVD. My standalone is a Sony BDP-BX1, but if the PowerDVD test did not work, I did not think it would work on BD-RE either.

[Capsbackup]

@jdobbs;
I notice that if I open Terminator 3 with BD-RBV02301, it sees 00001.m2ts as VC-1, 1080P, 23.976fps*, 13,359.84 MB.
If I open it with BD-RBV02202, it sees 00001.m2ts as VC-1, 1080i, 29.97fps, 13,359.84 MB.
If I open 00001.m2ts with BDInfo, it sees VC-1, 1080i, 29.970fps.
Can you explain the difference?
Is this how BD-RB will reencode this file with this new version?

EDIT:
Even though 00002.m2ts is larger than 00001.m2ts, I am unable to use MIN_M2TS_SIZE= to force BD-RB to skip reencoding 00001.m2ts.
If I set MIN_M2TS_SIZE=15000, BD-RB will remove 00002.m2ts from the to rencode list but not 00001.m2ts. Is that the way it is suppose to be?

[jdobbs]

@jdobbs;
I notice that if I open Terminator 3 with BD-RBV02301, it sees 00001.m2ts as VC-1, 1080P, 23.976fps*, 13,359.84 MB.
If I open it with BD-RBV02202, it sees 00001.m2ts as VC-1, 1080i, 29.97fps, 13,359.84 MB.
If I open 00001.m2ts with BDInfo, it sees VC-1, 1080i, 29.970fps.
Can you explain the difference?
Is this how BD-RB will reencode this file with this new version?

EDIT:
Even though 00002.m2ts is larger than 00001.m2ts, I am unable to use MIN_M2TS_SIZE= to force BD-RB to skip reencoding 00001.m2ts.
If I set MIN_M2TS_SIZE=15000, BD-RB will remove 00002.m2ts from the to rencode list but not 00001.m2ts. Is that the way it is suppose to be? That means it is progressive with pulldown -- so BD-RB removes the pulldown and keeps it progressive.

[bassnut]

Yes you have been busy Jdobbs ....... I have 300 running now as soon as it is done I will let you know. Any other movies that might be giving you some issues shout out and I may have it to try. Wow looks like there might be a bit of a speed improvment ...... 166 fps on pass 1 and 85 fps on pass 2

[Capsbackup]

Well, I have burned The Mummy to BD-RE and it does play the movie on my Sony BDP-BX1. Interesting that PowerDVD would not play it but it does play on my standalone.
However, this is the second full movie backup to BD-RE that does not have perfect audio sync. The .m2ts file played back with MPC has audio sync, but the burned version to BD-RE does not. Definitely troublesome!! :confused:

[bassnut]

300 is now at 67% and working fine. With my system it would sometimes stall at 50% sometimes not, take this for what it's worth.

[jdobbs]

@jdobbs;
I notice that if I open Terminator 3 with BD-RBV02301, it sees 00001.m2ts as VC-1, 1080P, 23.976fps*, 13,359.84 MB.
If I open it with BD-RBV02202, it sees 00001.m2ts as VC-1, 1080i, 29.97fps, 13,359.84 MB.
If I open 00001.m2ts with BDInfo, it sees VC-1, 1080i, 29.970fps.
Can you explain the difference?
Is this how BD-RB will reencode this file with this new version?

EDIT:
Even though 00002.m2ts is larger than 00001.m2ts, I am unable to use MIN_M2TS_SIZE= to force BD-RB to skip reencoding 00001.m2ts.
If I set MIN_M2TS_SIZE=15000, BD-RB will remove 00002.m2ts from the to rencode list but not 00001.m2ts. Is that the way it is suppose to be? It all depends. The problem with the MIN_M2TS_SIZE is the structure of the BD. In a BD playback is dictated by the MPLS file. The MPLS might reference several M2TS/CLPI file sets (component parts of the overall playback). But in order for the stream of multiple components to work --they all have to have common audio tracks, subs, video types/framerates etc. There can be lots of MPLS files, and multiple MPLS files might point to a single M2TS. If you reencode an M2TS you also have to reencode all the other components in that MPLS -- or it won't work (one part might use a certain codec and the other won't match). So sometimes you are forced to reencode an M2TS -- even when it falls under MIN_M2TS_SIZE. To make it even more complicated... one of the component M2TS files of an MPLS might also be a part of other MPLS files -- and as a result, when it is encoded -- it forces the components of the other MPLS files to also be encoded.

Bottom line is -- you can set the MIN_M2TS_SIZE, but that doesn't necessarily mean all the files will (or more accurately can) cooperate with your decision.

Hope that isn't too complicated an answer to a simple question. But frankly when you follow the file links involved and try to figure a "why" it starts to look a little like voodoo.

[jdobbs]

Yes you have been busy Jdobbs ....... I have 300 running now as soon as it is done I will let you know. Any other movies that might be giving you some issues shout out and I may have it to try. Wow looks like there might be a bit of a speed improvment ...... 166 fps on pass 1 and 85 fps on pass 2 Your framerates have me green with envy. I want a system like yours when I grow up.

[bassnut]

looks like those frame rates were on the extras @ 720 X 480, should of noticed that earlier ....... dam I need some sleep ........ I am back down to a fairly normal 15 FPS now at 1920 X1280 on pass 2 but at 76% now 3 hours later

[Capsbackup]

@jdobbs;
Thank you for this explanation. I guess I was just hoping to be able to be selective of what I could or could not reencode by using the MIN_M2TS_SIZE.
Also, thanks for your continued efforts and support. :) :thanks:

[drmih]

Well, I have burned The Mummy to BD-RE and it does play the movie on my Sony BDP-BX1. Interesting that PowerDVD would not play it but it does play on my standalone.
However, this is the second full movie backup to BD-RE that does not have perfect audio sync. The .m2ts file played back with MPC has audio sync, but the burned version to BD-RE does not. Definitely troublesome!! :confused:

All I can say is that I have done all three of the mummy films to bd-r and haven't seen a problem, either on my pc with TMT3 or a Sony 550.

[Furiousflea]

Could someone clarify the situation on films with PIP please?

Are they functioning correctly, obviously minus the PIP functionality.

Many thanks, Rob

[tekmobile]

Just running drillbit taylor and noticed that it has demuxed the main movie VC1 stream with the audio/subs but doing the re encode from the m2ts.

Is this intentional or a bug ?

[MikeyBK]

The same test clip that had the stuck at 50% GUI issue in 0.22.01 & 0.22.02, no longer had that issue in v0.23.01... just FYI...

:thanks:

[drmih]

Could someone clarify the situation on films with PIP please?

Are they functioning correctly, obviously minus the PIP functionality.

Many thanks, Rob

On a PC I have found them all to work perfectly whether to bd-9 or bd-25 in full disc mode (but obviously without anything happening if you try and switch on PIP). On my only standalone player (Sony 550) if I copy a bd-9 structure to a dvd-dl disc, although everything 'works', you can't select the audio for the main movie, although the stream can be played on a PS3 with the audio there. If I take the same bd-9 structure and copy it to a bd-re, it works perfectly!! There is therefore something slightly quirky about the Sony's firmware. For full disc copies to bd-r or bd-re all have played fine so far.

[jdobbs]

Just running drillbit taylor and noticed that it has demuxed the main movie VC1 stream with the audio/subs but doing the re encode from the m2ts.

Is this intentional or a bug ? That's something I added. This version looks at the source size to determine whether it needs to reencode or can keep the original stream intact and still fit on the output target. So it obviously has to know the exact size of the original video stream. There are two ways to do that -- either demux the video along with the audio, or rescan the M2TS myself just before reencoding (to get the size). I originally wrote code to scan the M2TS. But it doubled the time of a the first option (demuxing), so I decided just to sacrifice drive space as opposed to adding more time to an already lengthy process. At that time, I planned to remove the demuxed video when the decision is made to reencode it. But then realized there is a possibility that the decision might be reversed when a later component of a shared MPLS is demuxed.... so I left it.

I'll probably play with that a little more. Large components are unlikely to ever have a decision reversed later, so I may remove those demuxed video streams at reencode.

[tekmobile]

That's something I added. This version looks at the source size to determine whether it needs to reencode or can keep the original stream intact and still fit on the output target. There are two ways to do that -- either demux the video along with the audio, or rescan the M2TS myself just before reencoding (to get the size). I originally wrote code to scan the M2TS. But it doubled the time of a the first option (demuxing), so I decided just to sacrifice drive space as opposed to time. At that time, I planned to remove the demuxed video when the decision is made to reencode it. But there is a possibility that the decision might be reversed when a later component of a shared MPLS is demuxed.... so I left it.

I'll probably play with that a little more. Large components are unlikely to ever have a decision reversed later, so I may remove those demuxed video streams at reencode.

Thats OK then I thought you might have started doing the re encoding from the demuxed stream instead of the m2ts but couldnt see any details in the release notes.

So after the ReEncode process has started its safe to manually delete the demuxed video file the only reason im asking is because I have a dedicated partition for the workfiles directory to help save the system drive from fragmentation due to the constant changing of data and its not enough space assigned to store the additianal demuxed video track.

When its done I will increase the partition size to suit.

[bassnut]

@ Furiouseflea ..... I ahe done a cople of the PIP tracked movies ..... Wanted and Taken come to mind right away. All to BD25 the encode works fine and all extras play fine on both my PC, WINDVD9, TMT3 and POWERDVD8 and my Standalone SonyBDPS350. The only issue when you select to play the PIP extras is you get an empty PIP box or screen frame since obviously there is nothing to play. There have been no other issues with these movies or any other movies I have done since ALIEN Vs PREDATOR a little while back (21.02) and that had to do with VC1 Streams which I think has been dealt with.

@Jdobs ....... 300 encoded fine and plays fine on PC. No 50% bug evident. Final encode time was around 5 - 6 hours for complete backup to BD25 all english Audio and all subbs kept so there looks like maybe a bit of a preformance boost even if it just came from encoding the extras, there were allot of 720 X 480 streams in this movie ...... quick encode for extras was not selected. I have Deathrace in now but won't know how that turned out till I get back Sunday ....... Taking off for a litttle holliday. Thanks for your efforts ....... great program.

[PurpleMan]

Hi jdobbs, thanks for replying.

Like I said, I checked that if I open the .avs file that bd-rb used, the frames there are NOT corrupted (meaning that the source m2ts is fine). It either got corrupted by x264 or by the decoder from some reason while serving it.

I repeated the encode only for that particular m2ts (same avs, same bd-rb commandline for 1st/2nd passes) - and it resulted in a good encode this time.

I am quite bothered at what could have caused it to screw up like that on the first go.


And another bug I noticed, the abovementioned movie ("21") is split to several m2ts's on the original disc with no consistency to the division. meaning, 00133.m2ts is first hour, then 00134.m2ts is another 6 minutes, then another 35 seconds, then another 1 hours, etc. The movie is "glued" together on the disc using a playlist (obviously). After running BD-RB on it, when playing the movie, whenever it crosses a point in which it switches from one m2ts to another, there is an audio gap that makes it noticeable it's switching files. that gap does not exist on the source disc nor the ripped-to-hd version. I think that this could be caused by even the slightest deviation in the number of frames decoded by directshow as opposed to the amount coded on the original m2ts (1 frame difference would result in that gap).

Anyways, I think that's worth looking into. As a side note, any particular reason you chose not to use the DG indexing tools for the frameserving? (DGAVCIndex, DGIndex and DGVC1Index)
Seems like it's kind of a mess using "directshowsource" as each person has a different decoder installed on his system. For instance, I use ffdshow for vc1/mpg2 and coreavc for avc.

Keep up the good work, it is greatly appreciated.
I'll keep reporting and testing, doing whatever I can do to help.

Regards,
-PurpleMan

@jdobbs: Sorry, haven't gotten your reply for this.

In addition, I can confirm that in the new version you released yesterday the files are still encoded as 23.975.

[MILLZY]

You make me smile!!

As the problem file is an extra, if you were only doing movie-only it would be included. However, to answer your question it will be a full disc copy but only the movie will be re-encoded - the others will just be copied intact.

Worked like a charm...:thanks:

[user822]

Don't be surprised when a previous source that would crash the CODEC and cause an X264 failure now becomes a blanked screen.

#Created by BD Rebuilder - v0.23.01 (beta)
Blankclip(length=134350, height=1080, width=1920, fps=25)
Subtitle("VIDEO BLANKED...", align=5, size=40)


that was with 1080i VC1

it crashed x264 two times before at about 70%

hope it's working now with the old version and other decoder..

[colinhunt]

In addition, I can confirm that in the new version you released yesterday the files are still encoded as 23.975.
I'm running tests on two PCs right now, and MediaInfo reports the completed VIDs are all 23.976 like they should be. (Note: I'm referring to the MKV files BD-RB uses before the final stage.)

[colinhunt]

June 18th, 2009 - v0.22.03
- Added code to detect when a video source does not
require encoding to meet target size goals, and keep it
intact. Please note that the decision contains more
than meets the eye. For example, if an M2TS is a part
of more than one MPLS and a component portion of the
other cannot be kept intact -- it may not qualify and
requires encoding.
Yay! Silly question though (yes, another one): this wouldn't happen to be intelligent enough to first encode non-movie VIDs (when doing full backup), then making an educated guess whether the movie itself would fit without re-encoding?