BD Rebuilder Beta - Bug Reports Only

[jdobbs]

Answer to

"Can anyone with a Panasonic standalone player please confirm whether the output from the latest version of BD-RB works correctly on your player (without FIX_CLPI=0 set)? It works a little differently than FixCLPI, and I have no way of testing it.)

I have tested a couple with 20.01 on a Panasonic DMP-BD55 and no problems. I am not sure about FIX_CLPI=0 I just used the default settings and it worked fine.Great. The default is "1", which is what I wanted to hear.

[jdobbs]

I've posted a link to an updated version of BD Rebuilder (v0.20.02). The changes are:
- Made additional change to the CLPI "fix" code
to provide greater compatibility across more
players.
- Regressed the version of TSMUXER included to
the same one released with v0.19.6. Apparently
the new one introduces issues.
- Other minor corrections and cosmetic fixes.

[[SLiM]D12]

Furiousflea,

No luck, came out as DVD-5 again..........weird huh?

[turbojet]

I have not experienced the playback issues with MPC-HC build 1000 with evr custom + coreavc/ffdshow/built in avc decoder.
I also haven't experienced issues with PowerDVD 8 on about 15 encodes I've done so far with v0.20.01.
I'm not saying you guys are wrong I just think it goes a lot deeper then it being tsmuxer to blame, could the people having issues post MPC-HC build, output method and decoder?

jdobbs I see from changelog it doesn't look like it but I want to make sure. Is there any reason to check sizing in v0.20.02 over v0.20.01?

[Binnugsai]

I've posted a link to an updated version of BD Rebuilder (v0.20.02). The changes are:
- Made additional change to the CLPI "fix" code
to provide greater compatibility across more
players.
- Regressed the version of TSMUXER included to
the same one released with v0.19.6. Apparently
the new one introduces issues.
- Other minor corrections and cosmetic fixes.

Hi jdobbs,

Did you think we can use this last version and have good audio or perhaps without changing anything and keep the original audio. Sometimes we have some Bluray with only DTS Master audio.

Thanks very much

[Furiousflea]

Hi jdobbs,

Did you think we can use this last version and have good audio or perhaps without changing anything and keep the original audio. Sometimes we have some Bluray with only DTS Master audio.

Thanks very much

.....whistles....la la....;)

[bobrap]

tried doing full backup of Death Race to dvd-9 and got a encoder abort error. What files should I attach if you want to see what may have caused the problem? First full backup I've tried.:(

[ds9delta]

Hi jdobbs,

Did you think we can use this last version and have good audio or perhaps without changing anything and keep the original audio. Sometimes we have some Bluray with only DTS Master audio.

Thanks very much

I Have To Agree I Realise You Wanted To Wait To Tackle The Audio Till The Last Moment But Here In Australia (ALMOST) Every Blu-Ray Being Released Now The ONLY English Track Is DTS-HD Master 7.1 And At Present Only The Foreign Tracks Are Standard Surround... It May Not Exactly Be A Bug But I Would Like To Ask If We Could Just Mux The Original Audio Stream To The Newly Encoded Video Stream Would That Really Create Many Problems?? At The Least I Would Ask That Another Method Of Encoding Be Looked At So We Aussies Can Do Some New Movies With English Sound... And Always :thanks: For The Great Program!

[Chefkoch_ico]

I did some testing with tsmuxer:
Tested with BD-RB 0.20.01 and PowerDVD 7.3 and 8.0
1.8.4 -> OK
1.8.18 -> NOK
1.8.19 -> NOK

Results are Black Screen on most files and bad chapter skipping on the files, that are not black screen.

Bye

[turbojet]

bobrap: check which m2ts it's failing on and let us know what it says for codec (AVC/VC-1/MPEG2 in the stream window for that m2ts.

chefkoch_ico: what program are you mounting with? what powerdvd 8 version?

[bobrap]

bobrap: check which m2ts it's failing on and let us know what it says for codec (AVC/VC-1/MPEG2 in the stream window for that m2ts.

I've read all your posts and I got to tell ya, I'm clueless to this. I don't know how to check, but if you tell me, I'll know.:D:thanks:

Wait...with a little common sense, I might have this fingered out.

00287.m2ts...mediainfo says AVC.

[turbojet]

OK can you open the m2ts with graphstudio (http://blog.monogram.sk/janos/download/dl-graphstudio.php) and let us know what decoder loads (ffdshow/coreavc/cyberlink/ etc.)

[bobrap]

That m2ts file will not render in graphstudio. The previous one will. Tried to play the file in TMT and it's a green screen. I guess bad rip.

[smnckl]

I have not experienced the playback issues with MPC-HC build 1000 with evr custom + coreavc/ffdshow/built in avc decoder.
...
I'm not saying you guys are wrong I just think it goes a lot deeper then it being tsmuxer to blame, could the people having issues post MPC-HC build, output method and decoder?


From the MPC-HC ChangeLog - v1.2.908.0 - 30.Nobember 2008

Am going to uninstall and do a new install to check.
Codecs and splitters installed work are pretty common to all apps used and work across the board, but then, who knows what might have gotten corrupted.

[jdobbs]

I have not experienced the playback issues with MPC-HC build 1000 with evr custom + coreavc/ffdshow/built in avc decoder.
I also haven't experienced issues with PowerDVD 8 on about 15 encodes I've done so far with v0.20.01.
I'm not saying you guys are wrong I just think it goes a lot deeper then it being tsmuxer to blame, could the people having issues post MPC-HC build, output method and decoder?

jdobbs I see from changelog it doesn't look like it but I want to make sure. Is there any reason to check sizing in v0.20.02 over v0.20.01? No. This update was mainly because of a correction I put in the fixclpi portion and to back TSMUXER to the older version (because of the reports I've receive here and from other sources, it is obvious I didn't do enough testing before that change). I also made some other minor changes, but nothing that would affect sizing.

I have, though, done quite a bit of testing with muxing/sizing in the past few days -- and I have to tell you that whoever has given you the impression that there is consistency in this process is misinformed. Yes, X264 is pretty accurate in its sizing. But, I have some sources that use as little as 4.5% overhead when muxed, and others (usually smaller) that hit as high as 12.5%. I'm sure there's a magic formula out there somewhere, but it's not something I've been able to put my arms around.

[jdobbs]

@All

Please stop asking about keeping original audio. How many posts does it take? I've heard you, I've answered you, I get the point, I'll get it done. End of story. It's not as simple as you all would imply, and some of it requres a TSMUXER version that has other issues. It also makes it harder for me to debug the basic portions of BD-RB, which where I am concentrating right now. All for keeping audio streams that in many cases aren't even supported by the most popular players.

Bottom line: Be patient. Continually pinging me about it isn't going to raise its priority, it's just getting me annoyed.

[turbojet]

bobrap: could you cut 5-10 seconds or so of the m2ts and upload to a place like sendspace (http://www.sendspace.com/)

jdobbs: Panasonic BD30 played BD-RB v0.20.01 movie only without fix_clpi=0 just fine.

Ya I see the same inconsistency sizing, atak posted RipBot264's formula (http://forum.doom9.org/showthread.php?p=1220277&highlight=229376#post1220277) which I've never had a problem with on sizing since dts was fixed back in may.

[turbojet]

With the subtitle issue on the shifted subs (http://img6.imageshack.us/my.php?image=shifted.png) it also shows in suprip with a lot of black in the screen.

Here is a screenshot from the retail (http://img99.imageshack.us/my.php?image=retail.png)

The aligned subs (http://img19.imageshack.us/my.php?image=aligned.png) show up in suprip covering the whole pic (very little black).

Also BDSup2Sub (http://forum.doom9.org/showthread.php?t=145277) shifts things the same.

original sup (http://www.sendspace.com/file/iyrnxf)

[setarip_old]

@jdobbs

What does the following error message indicate?
- [14:55:07] PredictAndEncode() 00006 3

[jdobbs]

@jdobbs

What does the following error message indicate?
It means I've gotten an overflow error on a variable in section 3 of the encoding routine. It's the section where I calculate the amount of space required by the audio so I can determine the bitrate for the video. What disc are you seeing this on? Also, what are your settings for audio (keeping the original, default, 640Kbs AC3)?

[setarip_old]

What disc are you seeing this on?It was a snippet (for test purposes) of "The Santa Clause 3" (Another problematic, for me) VC-1.

Also, what are your settings for audio (keeping the original, default, 640Kbs AC3)?Retained original.

[isoss]

Answer to

"Can anyone with a Panasonic standalone player please confirm whether the output from the latest version of BD-RB works correctly on your player (without FIX_CLPI=0 set)? It works a little differently than FixCLPI, and I have no way of testing it.)

I have tested a couple with 20.01 on a Panasonic DMP-BD55 and no problems. I am not sure about FIX_CLPI=0 I just used the default settings and it worked fine.


i have a panasonic standalone the dmp-bd30 and it play's all menu and movie a like

[turbojet]

on BD25 lsoss?

[Philippe62]

During conversion of pirates of carribeans 3, an error occurs (either on 02002 version) :

[06:45:49] BD Rebuilder v0.19.06 (beta)
* - Source:* PIRATES DES CARAÏBES 3
* - Input BD size: 39,97 GB
* - Approximate total content: [02:48:31.101]
* - Target BD size: 22,90 GB
* - MOVIE-ONLY mode enabled
[06:45:49] PHASE ONE, Encoding
*- Extracting audio/subs [VID_00001]
*- [06:59:36] Reencoding: VID_00001 (1 of 2)
*- Extracting audio/subs [VID_00002]
*- [20:14:32] Reencoding: VID_00002 (2 of 2)
*- [20:14:35] DoEncoding() 00009* 8

The BDREBUILDER.INI :
[Options]
MODE=1
QUICK_EXTRAS=0
PRIORITY_CLASS=1
RESIZE=0
TARGET_SIZE=23450
AUDIO_TO_KEEP=eng;fra;fre;
SUBS_TO_KEEP=eng;fra;fre;
TRELLIS=1
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=0
AVCHD=1
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
VERBOSE_STATUS=0
AUTO_BURN=1
[Paths]
SOURCE_PATH=J:\BLURAY\PIRATES DES CARAÏBES 3\
WORKING_PATH=V:\BLU-RAY\BD-RE\PDC3\

And the BDREBUILDER.INF :
[Status]
LABEL=PIRATES DES CARAÏBES 3
VERSION=v0.19.06 (beta)
SOURCE_SIZE=42912356352
SOURCE_VIDEO_SIZE=42912356352
TARGET_SIZE=24589107200
REDUCTION=.573007620422922
RESIZE_1080=0
AUDIO_TO_KEEP=eng;fra;fre;
SUBS_TO_KEEP=eng;fra;fre;
BACKUP_MODE=1
QUICK=0
PASS=0
COMPLETED=1
[00001]
M2TS_TARGET=24589086077
RATE=15558
AUDIO=001100
NSIZE=20590123008
FLINK=0
MLINK=0
[00002]
M2TS_TARGET=21123
RATE=135

An the program can't be aborted (only with process control)

The VID_00002 MPEG-4 has no audio track and no subtitle and I can't remove it from the stream

Running on VISTA 64* Q6600* 4Go RAM

[Chefkoch_ico]

bobrap: check which m2ts it's failing on and let us know what it says for codec (AVC/VC-1/MPEG2 in the stream window for that m2ts.

chefkoch_ico: what program are you mounting with? what powerdvd 8 version?

I use Virtual Clone Drive (Beta Version from Slysoft) and PowerDVD 8 Ultra Build 2521 (newest Build).

Bye

[brogan]

Hello,

I'm having a little issue when trying to use the latest version of BD Rebuilder...attempting to convert a 28.4 GB Blu-ray (full movie) to a DVD-9...I get an error: Target is too small to continue
And the application says that the BD is 84.48 GB! No idea what the problem is, I've converted several movies w/out any issues at all...I tried the previous version of Rebuilder & I get the same issue...has anyone seen this or am I doing something wrong?? Thanks

[VistaVick]

Hello,

I'm having a little issue when trying to use the latest version of BD Rebuilder...attempting to convert a 28.4 GB Blu-ray (full movie) to a DVD-9...I get an error: Target is too small to continue
And the application says that the BD is 84.48 GB! No idea what the problem is, I've converted several movies w/out any issues at all...I tried the previous version of Rebuilder & I get the same issue...has anyone seen this or am I doing something wrong?? Thanks

I've had that happen before. What I did was change the location of the source file folder, or rename it and then it usually reads the correct file size.

[jdobbs]

I've had that happen before. What I did was change the location of the source file folder, or rename it and then it usually reads the correct file size. That's weird. BD-RB scans the source directory to get the size.

Any way someone could give me an example of a path that causes the sizing issue? Also, please make sure there aren't any other files in the path. BD-RB assumes everything under the source path is a part of the BD, not just the BDMV and CERTIFICATE folders. I use NTFS in my sources on HD, I assume others are keeping with NTFS (except, of course, direct reads from the disc). I'm trying to decide whether limiting myself to those two folders would result in any other issues. When I copy to HD that's all I transfer.

[Elesias]

Ok.

I always use "x264 encoder" (FFMPEG is greyed out), "Highest Quality", and "Target BD25".
I choose "Movie only backup" with no alternate or subtitles options.

In "Setup", I check "Stricter AVCHD Compliance for movie only" & Trellis Algorithm.

I burn either with Nero or ImgBurn, UDF 2.50, the BDMV & CERTIFICATE folders.
The movie seems to start fine, but I get only sound : no picture at all with my BD-35 (euro firmware 1.3)

When I try to read the M2TS with Windows Media Player, everything works perfectly, sound and picture alike. Did I miss something ?

[jdobbs]

What version are you using. Make sure it is v0.20.2, because there was apparently some issue introduced in v0.20.1 with the new TSMUXER. I've backed into the older TSMUXER with the latest one.

[drmih]

For information I have had issues where a rip has either reported that each segment was 4 GB and was therefore too big to be done, or the file structure looked okay but rebuilder still said it was too big. I have re-ripped the discs to images and mounted rather than from a file structure on the HDD and they are now fine. This isn't a correction in bd-rebuilder as that still gives the message with the files with the new version but hopefully assists others who have seen this problem.

For those of you who have 'lost' the original disc, you can use imgburn to create an image of the files which also works.

Just a reiteration from an earlier post I made regarding the issue of the size being wrongly reported.

[jdobbs]

If you can repeat the values being shown wrong, add this to the "[Options]" area of the INI (config) file:

SPECIAL_DEBUG_FILE=d:\debugfile.txt

Replace the file name with whatever you think works for you. This will record all the files/sizes it finds in the source path and save them into that file. Just run BD-RB and point to the source. Then exit. Don't forget to remove the option when you're done.

Then please send the file to me (dvd-rb@dvd-rb.com) so I can see why it is getting such goofy values.

[Elesias]

What version are you using. Make sure it is v0.20.2, because there was apparently some issue introduced in v0.20.1 with the new TSMUXER. I've backed into the older TSMUXER with the latest one.

Ah yes ok, gonna try the lastest version. :)

[drmih]

If you can repeat the values being shown wrong, add this to the "[Options]" area of the INI (config) file:

SPECIAL_DEBUG_FILE=d:\debugfile.txt

Replace the file name with whatever you think works for you. This will record all the files/sizes it finds in the source path and save them into that file. Just run BD-RB and point to the source. Then exit. Don't forget to remove the option when you're done.

Then please send the file to me (dvd-rb@dvd-rb.com) so I can see why it is getting such goofy values.

I'm away from home at the moment but have still got the good and bad structures on my pc so will do as you say on Friday.

[xxvvuu]

When I tried to do a full backup the program returned a size of 146GB and the error message: Target is too small to continue. I checked my directory where the files where stored and noticed the length of the directory path was greater that 48 characters long. I renamed the directory to less than 12 characters and then tried again. This time I got the correct computed disk size and could then proceed.

[jdobbs]

Ahh... thanks for the input. That may be the clue I'm looking for. I think my current "open" calls have a maximum path length of 128 characters. But I thought I'd get an error rather than bad data. I'll do some checking.

Maybe my memory is going... it seems like we discussed this once before.

[Furiousflea]

Ahh... thanks for the input. That may be the clue I'm looking for. I think my current "open" calls have a maximum path length of 128 characters. But I thought I'd get an error rather than bad data. I'll do some checking.

Maybe my memory is going... it seems like we discussed this once before.

long path names have caused a problem for me before, as have loading bluray structure from folders with esoteric characters. Moving BDRB folder closer to root sorted it out\rename bluray folder etc. EDIT (Although I didn't post about it, so it won't be me your remembering ;))

Kids these days eh, they don't know the slightest thing about problem solving! ^

Too much spoon feeding the little blighters, I honestly wouldn't be surprised if they weren't yet wiping their own backsides!...i kid...sortof :)

[BobZhome]

Ahh... thanks for the input. That may be the clue I'm looking for. I think my current "open" calls have a maximum path length of 128 characters. But I thought I'd get an error rather than bad data. I'll do some checking.

Maybe my memory is going... it seems like we discussed this once before.

You did discuss it and figured out the problem back here:http://forum.doom9.org/showthread.php?p=1231739#post1231739

[jdobbs]

I thought so. I never fixed it. Bad Dobbs! Sit!

[jdobbs]

Ok. I need one of you folks who have reported problems with NIGHTS_IN_RODANTHE to tell me what you're doing special... I just bought it and ran it in full-backup mode and it when through without any issues whatsoever. I need to see your settings.

[datman]

I have been getting these lately. Some will go ahead and finish the encode others are are aborted.

some movies work great others just won't do it. The first did not complete the last one did

[jdobbs]

I have been getting these lately. Some will go ahead and finish the encode others are are aborted.

some movies work great others just won't do it. The first did not complete the last one didHow long did you let it run? The percent "0%" doesn't seem to work in my observation -- but I've never seen it hang... sometimes these encodes can take a while.

[Capsbackup]

@jdobbs,
Regarding Nights in Rodanthe, I have tried a few different times, with v20.1 and 20.2, full 1080P and the last time was resize to 720P, but all fail with the same message.
-----------------------
[20:06:46] BD Rebuilder v0.20.01 (beta)
- Source: NIGHTS_IN_RODANTHE
- Input BD size: 20.55 GB
- Approximate total content: [02:45:40.688]
- Target BD size: 4.27 GB
- RESIZE 1080p to 720p enabled
[20:06:46] PHASE ONE, Encoding
- [20:06:46] Extracting audio/subs [VID_00003]
- [20:06:52] Collecting video information [00003]
- [20:06:52] Reencoding: VID_00003 (1 of 17)
- [20:07:04] Video Encode complete
- [20:07:04] Reencoding audio tracks
- [20:07:04] Multiplexing M2TS
- [20:07:05] Extracting audio/subs [VID_00022]
- [20:07:05] Collecting video information [00022]
- [20:07:05] Reencoding: VID_00022 (2 of 17)
- [20:07:20] Video Encode complete
- [20:07:20] Reencoding audio tracks
- [20:07:20] Multiplexing M2TS
- [20:07:21] Extracting audio/subs [VID_00018]
- [20:07:22] Collecting video information [00018]
- [20:07:22] Reencoding: VID_00018 (3 of 17)
- [20:07:32] Video Encode complete
- [20:07:32] Reencoding audio tracks
- [20:07:33] Multiplexing M2TS
- [20:07:33] Extracting audio/subs [VID_00001]
- [20:07:35] Collecting video information [00001]
- [20:07:35] Reencoding: VID_00001 (4 of 17)
- [20:07:59] Video Encode complete
- [20:07:59] Reencoding audio tracks
- [20:08:00] Multiplexing M2TS
- [20:08:01] Extracting audio/subs [VID_00011]
- [20:08:02] Collecting video information [00011]
- [20:08:02] Reencoding: VID_00011 (5 of 17)
- [20:08:13] Video Encode complete
- [20:08:13] Reencoding audio tracks
- [20:08:13] Multiplexing M2TS
- [20:08:14] Extracting audio/subs [VID_00008]
- [20:08:14] Collecting video information [00008]
- [20:08:14] Reencoding: VID_00008 (6 of 17)
- [20:08:33] Video Encode complete
- [20:08:33] Reencoding audio tracks
- [20:08:33] Multiplexing M2TS
- [20:08:33] Extracting audio/subs [VID_00021]
- [20:08:34] Collecting video information [00021]
- [20:08:34] Reencoding: VID_00021 (7 of 17)
- [20:09:27] Video Encode complete
- [20:09:27] Reencoding audio tracks
- [20:09:27] Multiplexing M2TS
- [20:09:28] Extracting audio/subs [VID_00020]
- [20:09:30] Collecting video information [00020]
- [20:09:30] Reencoding: VID_00020 (8 of 17)
- [20:10:30] Video Encode complete
- [20:10:30] Reencoding audio tracks
- [20:10:31] Multiplexing M2TS
- [20:10:32] Extracting audio/subs [VID_00019]
- [20:10:36] Collecting video information [00019]
- [20:10:36] Reencoding: VID_00019 (9 of 17)
- [20:12:20] Video Encode complete
- [20:12:20] Reencoding audio tracks
- [20:12:22] Multiplexing M2TS
- [20:12:22] Extracting audio/subs [VID_00023]
- [20:12:26] Collecting video information [00023]
- [20:12:26] Reencoding: VID_00023 (10 of 17)
- [20:14:18] Video Encode complete
- [20:14:18] Reencoding audio tracks
- [20:14:19] Multiplexing M2TS
- [20:14:20] Extracting audio/subs [VID_00010]
- [20:14:23] Collecting video information [00010]
- [20:14:23] Reencoding: VID_00010 (11 of 17)
- [20:20:37] Video Encode complete
- [20:20:37] Reencoding audio tracks
- [20:20:38] Multiplexing M2TS
- [20:20:40] Extracting audio/subs [VID_00025]
- [20:20:44] Collecting video information [00025]
- [20:20:44] Reencoding: VID_00025 (12 of 17)
- [20:23:45] Video Encode complete
- [20:23:45] Reencoding audio tracks
- [20:23:48] Multiplexing M2TS
- [20:23:48] Extracting audio/subs [VID_00013]
- [20:23:54] Collecting video information [00013]
- [20:23:54] Reencoding: VID_00013 (13 of 17)
- [20:27:09] Video Encode complete
- [20:27:09] Reencoding audio tracks
- [20:27:11] Multiplexing M2TS
- [20:27:11] Extracting audio/subs [VID_00015]
- [20:27:28] Collecting video information [00015]
- [20:27:28] Reencoding: VID_00015 (14 of 17)
- [20:40:19] Video Encode complete
- [20:40:19] Reencoding audio tracks
- [20:40:29] Multiplexing M2TS
- [20:40:32] Extracting audio/subs [VID_00017]
- [20:41:01] Collecting video information [00017]
- [20:41:01] Reencoding: VID_00017 (15 of 17)
- [20:54:45] Video Encode complete
- [20:54:45] Reencoding audio tracks
- [20:54:55] Multiplexing M2TS
- [20:54:57] Extracting audio/subs [VID_00012]
- [20:55:34] Collecting video information [00012]
- [20:55:34] Reencoding: VID_00012 (16 of 17)
- [21:19:16] Video Encode complete
- [21:19:16] Reencoding audio tracks
- [21:19:34] Multiplexing M2TS
- [21:19:38] Extracting audio/subs [VID_00004]
- [21:23:20] Collecting video information [00004]
- Video: 1920x1080, 23.976fps
- Bitrate: 4,256 Kbs
- [21:23:20] Reencoding: VID_00004, Pass 1 of 2
- [22:41:10] Reencoding: VID_00004, Pass 2 of 2
- [00:21:11] Video Encode complete
- [00:21:11] Reencoding audio tracks
- [00:22:33] Multiplexing M2TS
[00:23:57]PHASE ONE complete
[00:23:57]PHASE TWO - Rebuild Started
- [00:23:57] Rebuilding BD file Structure
- [00:24:04] CorrectMPLS() 00009 5
[01:15:00] - Aborted at user request

[Status]
LABEL=NIGHTS_IN_RODANTHE
VERSION=v0.20.01 (beta)
SOURCE_SIZE=22064934883
SOURCE_VIDEO_SIZE=22000011264
TARGET_SIZE=4581228544
REDUCTION=.205286482393321
RESIZE_1080=-1
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=all
BACKUP_MODE=0
QUICK=1
ENCODE_STEP=0
COMPLETED=17
REBUILD_COMPLETE=0
[00003]
M2TS_TARGET=2208502
AUDIO=1
NSIZE=1763328
FLINK=0
MLINK=0
[00022]
M2TS_TARGET=3150678
AUDIO=
NSIZE=3065856
FLINK=0
MLINK=0
[00018]
M2TS_TARGET=3173381
AUDIO=1000
NSIZE=1818624
FLINK=0
MLINK=0
[00001]
M2TS_TARGET=3517710
AUDIO=1000
NSIZE=10334208
FLINK=0
MLINK=0
[00011]
M2TS_TARGET=3901139
AUDIO=1
NSIZE=3348480
FLINK=0
MLINK=0
[00008]
M2TS_TARGET=4094115
AUDIO=
NSIZE=1978368
FLINK=0
MLINK=0
[00021]
M2TS_TARGET=10707007
AUDIO=1000
NSIZE=6776832
FLINK=0
MLINK=0
[00020]
M2TS_TARGET=20431477
AUDIO=1000
NSIZE=9621504
FLINK=0
MLINK=0
[00019]
M2TS_TARGET=34426642
AUDIO=1000
NSIZE=20219904
FLINK=0
MLINK=0
[00023]
M2TS_TARGET=36985779
AUDIO=1000
NSIZE=23347200
FLINK=0
MLINK=0
[00010]
M2TS_TARGET=47551523
AUDIO=1
NSIZE=76609536
FLINK=0
MLINK=0
[00025]
M2TS_TARGET=59412601
AUDIO=1000
NSIZE=28784640
FLINK=0
MLINK=0
[00013]
M2TS_TARGET=85648490
AUDIO=1000
NSIZE=37699584
FLINK=0
MLINK=0
[00015]
M2TS_TARGET=257037543
AUDIO=1000
NSIZE=142000128
FLINK=0
MLINK=0
[00017]
M2TS_TARGET=277268476
AUDIO=1000
NSIZE=135376896
FLINK=0
MLINK=0
[00012]
M2TS_TARGET=485505829
AUDIO=1000
NSIZE=231192576
FLINK=0
MLINK=0
[00004]
M2TS_TARGET=3782367261
RATE=4256
AUDIO=1000
NSIZE=3699572736
FLINK=0
MLINK=0

[jdobbs]

Ok. I'm trying it again with your settings.

[datman]

How long did you let it run? The percent "0%" doesn't seem to work in my observation -- but I've never seen it hang... sometimes these encodes can take a while.

The ones I'm referring to ran all the way to the end of the 2nd pass. As I said a few would continue after the error screen was closed. The ones that wouldn't continue would restart a previous project and the error would cycle over again.

The image might be from one of the restarted projects with what looked to me the same error but the numbers said 0% that's just a guess

[datman]

I was trying “Personal Effects” and twice it got to the end of phase 1 and tsmuxer failed. I tried to run the movie directly in tsmuxer and there were a bunch of errors. Tsremux 0212 seemed to work with no errors. I am running that file right now in 20.02

[jdobbs]

The ones I'm referring to ran all the way to the end of the 2nd pass. As I said a few would continue after the error screen was closed. The ones that wouldn't continue would restart a previous project and the error would cycle over again.

The image might be from one of the restarted projects with what looked to me the same error but the numbers said 0% that's just a guess
What error screen?

[Edit] Let me know what happens with the latest version.

[rainfellow]

I've been using BD Rebuilder for a month or so now and it works beautifully, and a heck of a lot quicker than the last program I was using.

The only problem is with one disc. I've been told it's one of the ones that is not yet able to be shrunk down using any known methods. So I just put it aside and try each new version of BD Rebuilder to see if it'll work yet. With this build, V0.20.02, I think there has been some progress as I have gotten a bit farther than I have before with it.

The disc in particular is Wrestlemania 24 (either disc of the 2 disc set).

According to BD Rebuilder it is VC-1, 1080i, 29.97fps with AC3 Multichannel sound.

Here is the bd-rebuilder.log file;
-----------------------
[21:09:44] BD Rebuilder v0.20.02 (beta)
- Source: WRESTLEMANIA_24_DISC_1
- Input BD size: 39.19 GB
- Approximate total content: [03:53:29.862]
- Target BD size: 7.72 GB
- MOVIE-ONLY mode enabled
[21:09:44] PHASE ONE, Encoding
- [21:09:44] Extracting audio/subs [VID_00064]
- [21:29:48] Collecting video information [00064]
- Video: 1920x1080, 29.970fps
- Bitrate: 3,921 Kbs
- [21:29:48] Reencoding: VID_00064, Pass 1 of 2
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
[21:30:02] - Failed video encode, aborted



This is the lastcmd.txt file;
"C:\BD_Rebuilder\tools\x264.exe" "C:\WORKING\WORKFILES\VID_00064.AVS" --bitrate 3921 --level 4.1 --sar 1:1 --aud --vbv-bufsize 14500 --keyint 24 --min-keyint 1 --vbv-maxrate 17500 --filter 0,0 --subme 2 --me dia --bframes 3 --direct auto --weightb --partitions none --trellis 0 --analyse none --threads auto --thread-input --progress --no-psnr --no-ssim --stats "C:\WORKING\WORKFILES\VID_00064.AVS.264.stats" --pass 1 --output NUL

When run from the command prompt I get the following;

avis [info]: 1920x1080 @ 29.97 fps (149451 frames)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2 SSE3 cached64
x264 [info]: profile Main, level 4.1
[0.0%] (counts from 0 - 40)/149451 frames, 7.62 fps, 10040.68 kb/s, eta (changes)

Then it drops back to a C:\ prompt.

I have ffdshow v.2639 installed, I have tried it with VC-1 on all 3 settings (disabled/libavcodec/wmv9) all give the same error.

At least this time it actually tried to run.

Just hoping this will help some. :thanks:

[datman]

I was trying “Personal Effects” and twice it got to the end of phase 1 and tsmuxer failed. I tried to run the movie directly in tsmuxer and there were a bunch of errors. Tsremux 0212 seemed to work with no errors. I am running that file right now in 20.02


this looks like I have a bad disc. or anydvd needs an update

[setarip_old]

@datman

Hi!

The following two statements appear to be contradictory:Tsremux 0212 seemed to work with no errors.and
this looks like I have a bad disc. or anydvd needs an update