BD Rebuilder Beta - Bug Reports Only

[MR.WaynesWorld]

Ok I copied the last command into a command prompt to execute it and came up with this..

C:\Users\Wayne Cierkowski\Desktop\Blu-Ray Tools\BD_Rebuilder\Tools>x264.exe "E:\
BLU-RAY WORKING\WORKFILES\VID_00123.AVS" --bitrate 4651 --level 4.1 --sar 1:1 --
aud --vbv-bufsize 14500 --keyint 24 --min-keyint 1 --vbv-maxrate 17500 --filter
0,0 --subme 2 --me hex --bframes 3 --8x8dct --direct auto --weightb --trellis 0
--analyse none --threads auto --thread-input --progress --no-psnr --no-ssim --st
ats "E:\BLU-RAY WORKING\WORKFILES\VID_00123.AVS.264.stats" --pass 1 --output NUL

avis [info]: 1920x1080 @ 23.98 fps (8409 frames)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64
x264 [info]: profile High, level 4.1
[0.1%] 8/8409 frames, 28.17 fps, 0.00 kb/s, eta 0:04:58
C:\Users\Wayne Cierkowski\Desktop\Blu-Ray Tools\BD_Rebuilder\Tools>

Hope that helps.....

[SvT]

Succes !

I earlier posted an error report on "Day after tomorrow". I got an error while backing up (find post).
Later I saw this post from setarip_old about rebooting and from Atak_Snajpera about using WMV11. I realized I didn't boot after I installed everything neededfor your program. So I finally did.

I can tell you now I also succesfully made a back up of my disk !!!

Thanks for this great program and succes making it even better !

LOL See next post ! It worked for me !

[20:41:46] BD Rebuilder v0.18.8 (beta)
- Source: DAT_F2
- Input BD size: 29,76 GB
- Approximate total content: [02:03:40.412]
- Target BD size: 4,27 GB
- MOVIE-ONLY mode enabled
[20:41:48] PHASE ONE, Encoding
- [20:58:47] Collecting video information [00001]
- Video: 1920x1080, 23,976fps
- Bitrate: 3.473 Kbs
- [20:58:48] Reencoding: VID_00001, Pass 1 of 2
- [20:58:48] Reencoding: VID_00001, Pass 2 of 2
- [23:38:56] Video Encode complete
- [23:38:56] Extracting/reencoding audio tracks
- [23:44:46] Multiplexing M2TS
[23:49:40]PHASE ONE complete
[23:49:40]PHASE TWO - Rebuild Started
- [23:49:40] Rebuilding BD file Structure
[23:57:07] - Encode and Rebuild complete
[23:57:07]JOB: DAT_F2 completed.

Thanks.

[setarip_old]

@jdobbs, @BenieUK, @SvT

Regarding the problems encountered by "BenieUK", please see my post at:

http://forum.doom9.org/showpost.php?...49&postcount=1

[Capsbackup]

Another successful backup,
No issues on playback for Zack and Miri on my BX1. Used BD-RB v0.18.8 with included .x264, movie only, kept 640kbps AC3, BD-5 size. It could be considered slightly undersized at 4.13GB, but my guess is noone could tell the difference visually. Completed in 5 hours and 3 minutes on i7 920 at 2.67GHz.
Thanks again jdobbs!!
P.S. I do hope "shut down after completion" can be implemented soon since I no longer have to wait over night ( or over the next few days ) for my backup to finish, and that humming to shut down sound will greatly improve my sleep pattern.

[dmancornell]

Originally Posted by jdobbs

Try running the mux from the command line:

"c:\path\to\bd-rb\tools\tsmuxer.exe" "c:\working\path\mux_00000.meta" "c:\working\path\TMP"

See what error is occurring.

Thanks for looking at this. Here's the meta file

MUXOPT --no-pcr-on-video-pid --new-audio-pes --blu-ray --vbr --auto-chapters=5 --vbv-len=500
V_MPEG4/ISO/AVC, "D:\BDRIP\WORKFILES\VID_00000.AVS.264", fps=23.976, insertSEI, contSPS
A_AC3, "D:\BDRIP\WORKFILES\AUD_00000_4352.AC3", lang=eng
A_AC3, "D:\BDRIP\WORKFILES\AUD_00000_4354.AC3", lang=eng
S_HDMV/PGS, "D:\BDRIP\WORKFILES\00000.track_4608.sup", fps=23.976, lang=eng
S_HDMV/PGS, "D:\BDRIP\WORKFILES\00000.track_4609.sup", fps=23.976, lang=fra
S_HDMV/PGS, "D:\BDRIP\WORKFILES\00000.track_4610.sup", fps=23.976, lang=spa
S_HDMV/PGS, "D:\BDRIP\WORKFILES\00000.track_4611.sup", fps=23.976, lang=fra

And here's the terminal output

SmartLabs tsMuxeR. Version 1.8.4(b) http://www.smlabs.net
Decoding H264 stream (track 1): Profile: High@4.1 Resolution: 1920:1080p Frame rate: 23.976
0.0% complete
H264 bitstream changed: insert pict timing and buffering period SEI units
Decoding AC3 stream (track 2): Bitrate: 448Kbps Sample Rate: 48KHz Channels: 6
Decoding AC3 stream (track 3): Bitrate: 448Kbps Sample Rate: 48KHz Channels: 6
Decoding PGS stream (track 4): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 5): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 6): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 7): Resolution: 1920:1080 Frame rate: 23.976
H264 bitstream changed: insert SPS/PPS units
99.9% complete
Processed 263474 video frames
100.0% complete
Creation of Blu-ray playlist
Creation of Blu-ray stream info and seek index
Bitstream exception. It does not have to be! Plase contact the application support team for more information.

update: I have the disc image on HD and it stuttered terribly. The original disc might have been scratched. I'll get another original and see what happens, because that error above looks like it has nothing to do with BD-RB.

update 2: stuttering problem was caused by powerdvd, ignore previous update.

[rafrag]

i don't think of it as a bug more like a early software limitation but here it is: blackhawk down r1 main movie consists of 2 files 1 14gigs and 1 22gigs i can only select one or the other, deja vu r1 comes out so f***ed up don't even know where to start it starts as a movie then some sort of a interactive menu kicks in then it goes back to main movie then menu and so on

[datman]

I don't know if this is a bug, but as far as I can tell any ISO files from 18.7 and 18.8 will not play in pdvd8. Anything before works fine

[jdobbs]

Originally Posted by MR.WaynesWorld

OK jdobbs, I put back the X264 executable and started the encode of Hancock again. When the x264 error poped up I left it hang. Went into lastcmd to get you the last command.

"C:\Users\Wayne Cierkowski\Desktop\Blu-Ray Tools\BD_Rebuilder\tools\x264.exe" "E:\BLU-RAY WORKING\WORKFILES\VID_00123.AVS" --bitrate 4651 --level 4.1 --sar 1:1 --aud --vbv-bufsize 14500 --keyint 24 --min-keyint 1 --vbv-maxrate 17500 --filter 0,0 --subme 2 --me hex --bframes 3 --8x8dct --direct auto --weightb --trellis 0 --analyse none --threads auto --thread-input --progress --no-psnr --no-ssim --stats "E:\BLU-RAY WORKING\WORKFILES\VID_00123.AVS.264.stats" --pass 1 --output NUL


What should I do now....

Run CMD.EXE and cut/paste that command line into it. When it runs, see what error is reported.

[MR.WaynesWorld]

@jdobbs, check post 1241 for results...

[datman]

Originally Posted by jdobbs

Yeah -- but it was probably done with the INI setting at ENCODE_QUALITY=5 (that I left set by mistake), which won't look good in most cases (except possibly BD-25).

what should it be, I checked and it is set =3

[datman]

Originally Posted by datman

I don't know if this is a bug, but as far as I can tell any ISO files from 18.7 and 18.8 will not play in pdvd8. Anything before works fine

for what it's worth I converted a BDRB file dated 1-20-09 to ISO tonight and it will mount and play.

I have had the "Stricter AVCHD compliance for movie-only" checked since about this time

[jdobbs]

Originally Posted by datman

what should it be, I checked and it is set =3

That's correct for the "High Quality" setting. That variable is set by the selection on the ENCODER SETTINGS menu. But I added a couple of "hidden" settings for testing (mainly to speed things up). I accidentally left one set in the INI I sent out in the v0.18.8 ZIP file.

[dmancornell]

2nd update on my above post. the stuttering was a problem with powerdvd, so the image is fine.

trying again now with tsmuxer 1.8.8 beta

[hlonipha]

I have Nero 9 or Img burn. could someone post a step by step on how to burn to a dvd5 please ?


Thanks

Hlonipha

[klas]

Originally Posted by datman

I don't know if this is a bug, but as far as I can tell any ISO files from 18.7 and 18.8 will not play in pdvd8. Anything before works fine

May be necessary to update the PowerDVD 8. I've done tests with Amadeus and the target=8150 and every
thing ok.

[mmace]

Originally Posted by jdobbs

I gotta' tell you. If I had to wait 12 days for an encode, I'd probably just buy an extra copy of every movie... more likely though, I'd buy a new computer. You must get tired just from shoveling coal into the rear of that one.

Ha ha, I know what you mean, I will have a nice new i7 by the end of the month. I didn't even need the shrink I was doing, I was just testing the software and was determined for it to work!

[DIVX2009]

JDOBBS...I HAVE THIS ERROR:

[07:36:49] BD Rebuilder v0.18.8 (beta)
- Source: HI-DEFINITION REFERENCE DISC 2008 BLU-RAY 1080I AVC LPCM7.1
- Input BD size: 16.56 GB
- Approximate total content: [00:57:38.955]
- Target BD size: 4.27 GB
[07:36:50] PHASE ONE, Encoding
- [07:36:53] Reencoding: VID_00000 (1 of 64)
- [07:39:36] Reencoding: VID_00001 (2 of 64)
- [07:40:13] Reencoding: VID_00002 (3 of 64)
- [07:44:28] Reencoding: VID_00003 (4 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [07:44:41] Reencoding: VID_00004 (5 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [07:44:52] Reencoding: VID_00005 (6 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [07:45:10] Reencoding: VID_00006 (7 of 64)
- [07:46:52] Reencoding: VID_00007 (8 of 64)
- [07:50:38] Reencoding: VID_00008 (9 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [07:52:15] Reencoding: VID_00009 (10 of 64)
- [07:56:29] Reencoding: VID_00010 (11 of 64)
- [07:59:54] Reencoding: VID_00011 (12 of 64)
- [08:05:57] Reencoding: VID_00012 (13 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [08:06:41] Reencoding: VID_00013 (14 of 64)
- [08:11:04] Reencoding: VID_00014 (15 of 64)
- [08:15:05] Reencoding: VID_00015 (16 of 64)
- [08:19:33] Reencoding: VID_00016 (17 of 64)
- [08:25:43] Reencoding: VID_00017 (18 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [08:26:02] Reencoding: VID_00018 (19 of 64)
- [08:27:17] Reencoding: VID_00019 (20 of 64)
- [08:38:06] Reencoding: VID_00020 (21 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [08:38:49] Reencoding: VID_00021 (22 of 64)
- [08:47:10] Reencoding: VID_00022 (23 of 64)
- [08:53:10] Reencoding: VID_00023 (24 of 64)
- [08:57:26] Reencoding: VID_00024 (25 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [10:28:38] Reencoding: VID_00025 (26 of 64)
- [10:29:52] Reencoding: VID_00026 (27 of 64)
- [10:37:26] Reencoding: VID_00027 (28 of 64)
- [10:43:22] Reencoding: VID_00028 (29 of 64)
- [10:50:24] Reencoding: VID_00029 (30 of 64)
- [10:55:23] Reencoding: VID_00030 (31 of 64)
- [11:03:09] Reencoding: VID_00031 (32 of 64)
- [11:05:01] Reencoding: VID_00032 (33 of 64)
- [11:06:13] Reencoding: VID_00033 (34 of 64)
- [11:11:41] Reencoding: VID_00034 (35 of 64)
- [11:17:48] Reencoding: VID_00035 (36 of 64)
- [11:21:48] Reencoding: VID_00036 (37 of 64)
- [11:29:45] Reencoding: VID_00037 (38 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [11:30:26] Reencoding: VID_00038 (39 of 64)
- [11:34:26] Reencoding: VID_00039 (40 of 64)
- [11:41:23] Reencoding: VID_00040 (41 of 64)
- [11:43:23] Reencoding: VID_00041 (42 of 64)
- [11:48:09] Reencoding: VID_00042 (43 of 64)
- [11:50:41] Reencoding: VID_00043 (44 of 64)
- [11:54:29] Reencoding: VID_00044 (45 of 64)
- [12:01:26] Reencoding: VID_00045 (46 of 64)
- [12:05:30] Reencoding: VID_00046 (47 of 64)
- [12:12:38] Reencoding: VID_00047 (48 of 64)
- [12:15:43] Reencoding: VID_00048 (49 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [12:16:37] Reencoding: VID_00049 (50 of 64)
- [12:22:27] Reencoding: VID_00050 (51 of 64)
- [12:24:34] Reencoding: VID_00051 (52 of 64)
- [12:32:42] Reencoding: VID_00052 (53 of 64)
- [12:40:51] Reencoding: VID_00053 (54 of 64)
- Reached retry limit. Aborting.
- [12:41:50] Reencoding: VID_00054 (55 of 64)
- [12:43:22] Reencoding: VID_00055 (56 of 64)
- [12:45:36] Reencoding: VID_00056 (57 of 64)
- [12:49:03] Reencoding: VID_00057 (58 of 64)
- [12:53:35] Reencoding: VID_00058 (59 of 64)
- Reached retry limit. Aborting.
- [12:57:43] Reencoding: VID_00059 (60 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
- [13:07:27] Reencoding: VID_00060 (61 of 64)
- [13:10:27] Reencoding: VID_00061 (62 of 64)
- Reached retry limit. Aborting.
- [13:12:46] Reencoding: VID_00062 (63 of 64)
- [13:13:39] Reencoding: VID_00063 (64 of 64)
- Reached retry limit. Aborting.
- Reached retry limit. Aborting.
[13:14:02]PHASE ONE complete
[13:14:02]PHASE TWO - Rebuild Started
- [13:14:02] Rebuilding BD file Structure
- [13:14:09] CorrectMPLS() 00009 5
[13:14:11] - Aborted at user request

???

[jdobbs]

The 21 times that you got "Reached retry limit. Aborting" is not a good sign... that means that each of those sections of the disc did not finish encoding. That would logically create a problem in the rebuild.

Something is causing X264 to fail in encoding those segments. I would suggest you step back to the previous version of X264.

[jdobbs]

Originally Posted by MR.WaynesWorld

Ok I copied the last command into a command prompt to execute it and came up with this..

C:\Users\Wayne Cierkowski\Desktop\Blu-Ray Tools\BD_Rebuilder\Tools>x264.exe "E:\
BLU-RAY WORKING\WORKFILES\VID_00123.AVS" --bitrate 4651 --level 4.1 --sar 1:1 --
aud --vbv-bufsize 14500 --keyint 24 --min-keyint 1 --vbv-maxrate 17500 --filter
0,0 --subme 2 --me hex --bframes 3 --8x8dct --direct auto --weightb --trellis 0
--analyse none --threads auto --thread-input --progress --no-psnr --no-ssim --st
ats "E:\BLU-RAY WORKING\WORKFILES\VID_00123.AVS.264.stats" --pass 1 --output NUL

avis [info]: 1920x1080 @ 23.98 fps (8409 frames)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64
x264 [info]: profile High, level 4.1
[0.1%] 8/8409 frames, 28.17 fps, 0.00 kb/s, eta 0:04:58
C:\Users\Wayne Cierkowski\Desktop\Blu-Ray Tools\BD_Rebuilder\Tools>

Hope that helps.....

When it crashes, can you select the "more info" (or whatever it says) button on the popup and see where it says it happened? That way we can see if it was in the encoder or possibly the CODEC.

Interestingly I have done a number of encodes with this version of X264 and haven't had a crash yet. Is there anything unique about your setup, codecs, configuration?

What worries me is that the issue seems to go away by stepping back to X264 r1082... but all I have are reports, no personal experiences -- I guess I'll just change back in the next release, but I was hoping more info would come in that we could pass over to the X264 developers. I hate to lose all those speed improvements that have been implemented.

[jdobbs]

Just as a test, could one of the folks who is experiencing "crashes" with X264, please download this version (r1112) and see if (by some chance) the issue has resolved itself?

A quick response would be appreciated. I'd like to put out a new BD-RB release. Thanks.