BD Rebuilder Beta - Bug Reports Only

[mmace]

P.S. For the people with i7 processors, the process time of 5 hours is using High Quality or Highest Quality option for encoder. Is there any advantage of using Highest Quality?I'm doing my 2nd full disc back up to 25Gb at the moment, my 1st one took 12 days and the current one's been going since Sunday and this morning it got on to the main feature (that's with fast encodes for extras too!!)

Wish I could afford a new PC!! (currently Dual core 3.4 Ghz Pentium D)

[rafrag]

Its not a problem with BD-Rebuilder, its a limitation of the PS3. Don't waste your time with full movies to BD9 or BD5 for PS3 playback...it will fail. If you want the full movie for the PS3, you have to use BD25 media.

If you want to use BD5 or BD9 discs in the PS3, you have to make a Movie Only copy... with the option for "Stricter AVCHD compliance for Movie Only" enabled (checked). I've done 50 of these discs for the PS3... trust me. ;)
i've done about 30 myself (mo) i'm curious about quality of video when you put 4-5 hours of content on dvd9. thanks for the answer.

[YolkiePolkie]

Great work Mr Dobbs, I've been using v0.17.13 for a few weeks now with no problems. As I have a PS3 and you seem to have the skipping issue sorted I am about to use v0.18.08. Just a few questions about the new version:
By ticking stricter AVCHD compliance for movie only, do I no longer have to patch the index file for use on the PS3?
Is there a big difference in encoding times between default high setting and highest, and is there a noticeable increase in picture quality?

I know these aren't bugs but I wasn't sure how/where else to ask.

Thanks again

YP

[MR.WaynesWorld]

I just tried to do Hancock with the 18.8 release and it failed with X264.exe has stopped working. With the 18.7 release it worked. Failed early on when it started to encode the first file.

[jdobbs]

tried backing up pearl harbor with bd rebuilder 18.4 and 18.8. both versions result in the same error

[10:24:09] PHASE ONE, Encoding
- [11:07:02] Collecting video information [00000]
- Video: 1920x1080, 23.976fps
- Bitrate: 13,601 Kbs
- [11:07:05] Reencoding: VID_00000, Pass 1 of 2
- [12:46:38] Reencoding: VID_00000, Pass 2 of 2
- [19:10:53] Video Encode complete
- [19:10:53] Extracting/reencoding audio tracks
- [19:12:27] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00000.meta
[19:25:21] - Failed to build structure, aborted


target size is bd-25. the file that breaks is mpeg-2 with ac3 audio. 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.

[jdobbs]

I just tried to do Hancock with the 18.8 release and it failed with X264.exe has stopped working. With the 18.7 release it worked. Failed early on when it started to encode the first file. I asked earlier for someone to do an encode from the command line (the command can be found in LASTCMD.TXT). That way I can get some idea as to what the real error is. I don't think I've seen a post of the results yet. One person mentioned changing from a networked drive to a local... but I'm not sure how that would help unless the command line was too long.

I also asked for someone to try replacing X264.EXE with a previous version -- but I haven't seen any results from that request either.

[MR.WaynesWorld]

I asked earlier for someone to do an encode from the command line (the command can be found in LASTCMD.TXT). That way I can get some idea as to what the real error is. I don't think I've seen a post of the results yet. One person mentioned changing from a networked drive to a local... but I'm not sure how that would help unless the command line was too long.

I also asked for someone to try replacing X264.EXE with a previous version -- but I haven't seen any results from that request either.

I just moved over the x264.exe from 18.7 to 18.8 and re-running the encode. I should be able to let you know before I leave for work.

Thanks,
Wayne

[jdobbs]

Thanks. At least then we can see if the issue is in BD-RB or the new version of X264.

[m1482]

I asked earlier for someone to do an encode from the command line (the command can be found in LASTCMD.TXT). That way I can get some idea as to what the real error is. I don't think I've seen a post of the results yet. One person mentioned changing from a networked drive to a local... but I'm not sure how that would help unless the command line was too long.

I also asked for someone to try replacing X264.EXE with a previous version -- but I haven't seen any results from that request either.

I beleived that the problem is the latest versions of FFDSHOW and X264. With new BD Rebuilder release, X264 also crash in my computer. So I substitute new X264 version with version 1102 and problem was solved. Then I decided to unistalled FFDSHOW and Haali Mux and installed K-lited Coded Pack 453 that has a previous version of FFDSHOW and now the latest version of X264 doesn't crash...

[MR.WaynesWorld]

I just moved over the x264.exe from 18.7 to 18.8 and re-running the encode. I should be able to let you know before I leave for work.

Thanks,
Wayne

OK with the x264 executable from 18.7 it's trucking along... Did it's extract of Audio and went into the encode process.

Thanks,

Wayne

[Dark Shikari]

I beleived that the problem is the latest versions of FFDSHOW and X264. With new BD Rebuilder release, X264 also crash in my computer. So I substitute new X264 version with version 1102 and problem was solved. Then I decided to unistalled FFDSHOW and Haali Mux and installed K-lited Coded Pack 453 that has a previous version of FFDSHOW and now the latest version of X264 doesn't crash...If the latest revision of x264 crashes, report the bug, don't complain about it while giving no useful information... we aren't psychic and can't fix bugs if people don't tell us about them!

(and "it crashes" is about as much of a bug report as "my computer won't work". If there's a crash, try to find what settings cause it, or at least provide a backtrace from a debug build.)

[drmih]

Its not a problem with BD-Rebuilder, its a limitation of the PS3. Don't waste your time with full movies to BD9 or BD5 for PS3 playback...it will fail. If you want the full movie for the PS3, you have to use BD25 media.

If you want to use BD5 or BD9 discs in the PS3, you have to make a Movie Only copy... with the option for "Stricter AVCHD compliance for Movie Only" enabled (checked). I've done 50 of these discs for the PS3... trust me. ;)

I would slightly disagree with this only from the perspective of long term compatibilty. I have found that full disc copies to bd-9 are good quality (and you get the full structure), and although the ps3 shows them as data discs, you can still play the streams. Therefore although it won't play straight away like an avchd it's only a couple of clicks to play it and you can work your way through the extras as well. The benefit being that if there is ever an update for the PS3 to make it compatible (and all Sony standalones are) or you buy a compatible standalone when they are cheaper, you have full disc bd-9s

[m1482]

If the latest revision of x264 crashes, report the bug, don't complain about it while giving no useful information... we aren't psychic and can't fix bugs if people don't tell us about them!

(and "it crashes" is about as much of a bug report as "my computer won't work". If there's a crash, try to find what settings cause it, or at least provide a backtrace from a debug build.)

I am not complaining!!!
I just explain how I deal with the problem. I think that there is a compatibility problem between both latest versions. I solved the problem going back to a previous version of FFDSHOW.
So not offence, I think that X264 is one of the best encoders available!!!

[jdobbs]

I beleived that the problem is the latest versions of FFDSHOW and X264. With new BD Rebuilder release, X264 also crash in my computer. So I substitute new X264 version with version 1102 and problem was solved. Then I decided to unistalled FFDSHOW and Haali Mux and installed K-lited Coded Pack 453 that has a previous version of FFDSHOW and now the latest version of X264 doesn't crash... Thanks, now if you could go back to the new version and run it from the command line (in LASTCMD.TXT) we could see what error message we are receiving.

[Dark Shikari]

I am not complaining!!!
I just explain how I deal with the problem.But saying "it crashed, so I used another revision" is the worst possible thing us developers can hear. It tells us:

a) There is a serious problem.
b) People aren't giving us any useful information about the serious problem.
therefore
c) We can't do anything about the serious problem, so the serious problem will continue to exist.

Furthermore, it doesn't even tell us which revision introduced the problem.

[jdobbs]

If the latest revision of x264 crashes, report the bug, don't complain about it while giving no useful information... we aren't psychic and can't fix bugs if people don't tell us about them!

(and "it crashes" is about as much of a bug report as "my computer won't work". If there's a crash, try to find what settings cause it, or at least provide a backtrace from a debug build.) C'mon, man. No sense yelling at people, they're only trying to help.

We don't even know if it is X264 causing the problem (I already know the BD-RB side is buggy) -- so there's no bug to report yet.

[MR.WaynesWorld]

Guys, like I said in post #1210, the encoding of Hancock was moving along with the x264 executable from the 18.7 beta release when I left this morning. But using the executable included with the 18.8 release it failed. Also when I selected to close the program when the error came up it continued to run not completely abort...

Let me know if you need anything else on this. I can get the x264 executable of 18.8 back in there and get some more information for you when I get home tonight after work. Just let me know.

[YolkiePolkie]

I have a bug to report using v0.18.08:

[11:52:43] BD Rebuilder v0.18.8 (beta)
- Source: GALAPAGOS_UK
- Input BD size: 21.67 GB
- Approximate total content: [02:26:52.937]
- Target BD size: 7.72 GB
- MOVIE-ONLY mode enabled
[11:52:43] PHASE ONE, Encoding
- Reached retry limit. Aborting.
[12:01:00] - Failed video encode, aborted

I did have FFDSHOW installed and also made sure I had AVC decoding enabled.

The blu-ray disc has 8.m2ts files in the streams folder, seen as 3 vc-1 streams by BD Rebuilder.

any ideas?

v0.17.13 only saw the first vc-1 stream.

[jdobbs]

...The blu-ray disc has 8.m2ts files in the streams folder, seen as 3 vc-1 streams by BD Rebuilder... I don't know what this means. You've selected MOVIE-ONLY, and if the movie is contained in only those three streams, that should be what is displayed.

Can you post the contents of LASTCMD.TXT (located in the BD-RB folder)?

Also, can you click on SETTINGS/VERBOSE STATUS REPORTING and run it again? I'd like to see a little more detail.

I did have FFDSHOW installed and also made sure I had AVC decoding enabled. You also need to have VC-1 decoding enabled.

v0.17.13 only saw the first vc-1 stream. I'd guess that was a bug in v0.17.13.

Thanks.

[BenieUK]

Hi all, I will start off by saying i have been a DVD-RB user from the beginning, also a doom9 user for years but this is my first post here.. My problem is i have tried to make a backup of my UK THE SIMPSONS MOVIE, i tell BD-RB to keep all audio and not convert and select size BD25 (all others default), after 4hrs the job is complete and the BD works fine BUT its only around 13GB not 25GB? (but looks great)

Using brand new built i7 PC with fresh install Vista Ultimate 32bit & BD-RB v01807.. will be trying same movie again tonight with new version BD-RB v0.18.08 (beta) to see if that helps,

I have just run Alien Vs. Predator 2 through BD-RB v0.18.08 (beta) all other needed software upto date also, full disc mode with same setting as above and its completed in 7 hrs ish and looks great and size is 21.3GB (close to the 25GB i asked)

Also like to say thanks to jdobbs & all others involved .. cant wait until this software is at a final release :) donation on its way !!

Donation sent from m0neygrabber :)

[YolkiePolkie]

I don't know what this means. You've selected MOVIE-ONLY, and if the movie is contained in only those three streams, that should be what is displayed.

Can you post the contents of LASTCMD.TXT (located in the BD-RB folder)?

Also, can you click on SETTINGS/VERBOSE STATUS REPORTING and run it again? I'd like to see a little more detail.

You also need to have VC-1 decoding enabled.

I'd guess that was a bug in v0.17.13.

Thanks.

Hi,

VC-1 decoding is enabled in FFDSHOW.

Here is the verbose report:

-----------------------
[15:01:53] BD Rebuilder v0.18.8 (beta)
- Source: GALAPAGOS_UK
- Input BD size: 21.67 GB
- Approximate total content: [02:26:52.937]
- Target BD size: 7.72 GB
- MOVIE-ONLY mode enabled
[15:01:53] PHASE ONE, Encoding
- [16:15:14] Collecting video information [00001]
- Error [01:-1] returned from encoder. Retrying.
- Error [02:-1] returned from encoder. Retrying.
- Error [03:-1] returned from encoder. Retrying.
- Reached retry limit. Aborting.
[16:18:25] - Failed video encode, aborted


Here is the contents of lastcmd.txt

"C:\Documents and Settings\XXXXXXXX\Desktop\BD-RBV01808\BD_Rebuilder\tools\x264.exe" "C:\BD9S\GALAPAGOS H264 BD9\WORKFILES\INFO.AVS" --crf 16 --output NUL



I've also attached some screenshots of the contents of the galapagos blu-ray disc stream folder and what is displayed by BD rebuilder when it reads the ripped disc folder to clarify the situation.

thanks

[GaPony]

I would slightly disagree with this only from the perspective of long term compatibilty. I have found that full disc copies to bd-9 are good quality (and you get the full structure), and although the ps3 shows them as data discs, you can still play the streams. Therefore although it won't play straight away like an avchd it's only a couple of clicks to play it and you can work your way through the extras as well. The benefit being that if there is ever an update for the PS3 to make it compatible (and all Sony standalones are) or you buy a compatible standalone when they are cheaper, you have full disc bd-9s

You can play individual streams on the PS3, but I haven't had any success in anything remotely resembling a normal playback for a full movie copy on the PS3, using DVD media. If you have a movie with a single m2ts for the main movie, it will play through, but there will be no chapter selection or any other options. The AVCHD (movie only) copy on the other hand, will play on most, if not all current players. I'm not certain the problem with full movie on BD9 or BD5 isn't somehow related to the fact that the PS3 is a gaming console first and a Blu-Ray player second.

Long term compatibility may be a tricky issue for all of us, but for those with only a PS3 it will likely be a bit more complicated. When considering a new standalone, PS3 owners may want to stay in the Sony family, or at least they make sure they buy a player that fully supports AVCHD.

[BenieUK]

Just tried The Mummy 3 UK version... failed with a crash from x264.exe about 5 and a half hours into it.. full disc mode, movie had been done was the next stream (extras) that it failed on.

[jdobbs]

I'm thinking it may be saturation, but Dark Shikari would be a better source for that information (he's probably the most prolific developer for X264). I know I ran a test encode last night with the intent of putting a single LOST episode on a BD-9, and found the output to be only 5GB. I ran it again with a BD-5 target and it sized very exactly. I made the assumption that it was encoder saturation -- but didn't follow up by looking at any of the logs.

[jdobbs]

Just tried The Mummy 3 UK version... failed with a crash from x264.exe about 5 and a half hours into it.. full disc mode, movie had been done was the next stream (extras) that it failed on.
I'm still waiting for someone to run the failed encode from the command line using LASTCMD.TXT so I can see what we're getting... just the word "crash" alone doesn't give a person a lot to work with. I've already gotten at least 10 of those reports on the new release.

[DIVX2009]

JDOBBS, support for lpcm 7.1 audio ???

[jdobbs]

Not yet. Maybe some day, after I get past all the major bug fixes.

[BenieUK]

I have tried what you said (I'm still waiting for someone to run the failed encode from the command line using LASTCMD.TXT so I can see what we're getting) but get no info when the error happens.. do i need to rerun with VERBOSE STATUS REPORTING on before seeing the error report?

Also i dont have vc-1 decoding on in FFDShow as at the min i get around 16fps but if i put it on i get arounf 0.35fps... do i need it on ?

[jdobbs]

Hi,

VC-1 decoding is enabled in FFDSHOW.

Here is the verbose report:

-----------------------
[15:01:53] BD Rebuilder v0.18.8 (beta)
- Source: GALAPAGOS_UK
- Input BD size: 21.67 GB
- Approximate total content: [02:26:52.937]
- Target BD size: 7.72 GB
- MOVIE-ONLY mode enabled
[15:01:53] PHASE ONE, Encoding
- [16:15:14] Collecting video information [00001]
- Error [01:-1] returned from encoder. Retrying.
- Error [02:-1] returned from encoder. Retrying.
- Error [03:-1] returned from encoder. Retrying.
- Reached retry limit. Aborting.
[16:18:25] - Failed video encode, aborted


Here is the contents of lastcmd.txt

"C:\Documents and Settings\XXXXXXXX\Desktop\BD-RBV01808\BD_Rebuilder\tools\x264.exe" "C:\BD9S\GALAPAGOS H264 BD9\WORKFILES\INFO.AVS" --crf 16 --output NUL



I've also attached some screenshots of the contents of the galapagos blu-ray disc stream folder and what is displayed by BD rebuilder when it reads the ripped disc folder to clarify the situation.

thanks Hmmm... this seems to indicate that it didn't even get to the point of attempting to encode -- INFO.AVS just writes information about the stream to an intermediate file.

What I don't understand is why it is happening to you but not to me? Can you also post the contents of INFO.AVS?

[MikeyBK]

Well I also had the x264 crash but only on one title.... It did a fine job a couple nights ago on The Secret Life of Bees, but had the same crashing as Yolkie when I attempted Pride & Glory last night.... I then overwrote that x264.exe with the exe from 0.18.07 and it appeared to encode fine, but when I awoke this morning BD-RB had completely shut down and exited, with only about half of the encoding done???

Anyways I reloaded the current x264.exe back into 0.18.8 and attempted a different movie, SpaceBuddies, and the current x264 no longer crashed.

Just FYI, Pride & Glory is VC-1 encoded..... but GaPony stated that he was successful on this title a couple nights ago already?? Not sure what to think at this point.

[YolkiePolkie]

Hmmm... this seems to indicate that it didn't even get to the point of attempting to encode -- INFO.AVS just writes information about the stream to an intermediate file.

What I don't understand is why it is happening to you but not to me? Can you also post the contents of INFO.AVS?

Here you go:

#Created by BD Rebuilder - v0.18.8 (beta)
DirectshowSource("C:\BLU-RAY RIPS\GALAPAGOS BLURAY RIP\GALAPAGOS_UK\BDMV\STREAM\00001.m2ts", fps=29.97, framecount=88260, audio=false)
LoadPlugin("C:\Documents and Settings\XXXXXXX\Desktop\Copy of BD-RBV01808\BD_Rebuilder\tools\decomb521.dll")
FieldDeinterlace(blend=false)
Tweak(0.0,1.1,0.0,1.0)
WriteFile("C:\BD9S\GALAPAGOS H264 BD9\WORKFILES\INFO.INI",""" "[Options]" """)
WriteFile("C:\BD9S\GALAPAGOS H264 BD9\WORKFILES\INFO.INI",""" "framecount=" ""","framecount")
WriteFile("C:\BD9S\GALAPAGOS H264 BD9\WORKFILES\INFO.INI",""" "framerate=" ""","framerate")
WriteFile("C:\BD9S\GALAPAGOS H264 BD9\WORKFILES\INFO.INI",""" "width=" ""","width")
WriteFile("C:\BD9S\GALAPAGOS H264 BD9\WORKFILES\INFO.INI",""" "height=" ""","height")
ConvertToYV12()
trim(0,-1)


Regards,

YP

[Furiousflea]

jdobbs, just an apology for not posting that lastcommand.txt thingy, i've got nasty flu and bright lights are killing me eyes. if still needed will post in couple of days. Sorry :(

[mmace]

Also i dont have vc-1 decoding on in FFDShow as at the min i get around 16fps but if i put it on i get arounf 0.35fps... do i need it on ?x264 kept saying it was crashing for me with a VC-1 disc so I had to turn it on in FFDShow and it dropped to about the same speed, for a full disc back up it took 12 days, it was either that or it got no where because of crashing

[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. ;)

[jdobbs]

Here you go:

#Created by BD Rebuilder - v0.18.8 (beta)
DirectshowSource("C:\BLU-RAY RIPS\GALAPAGOS BLURAY RIP\GALAPAGOS_UK\BDMV\STREAM\00001.m2ts", fps=29.97, framecount=88260, audio=false)
LoadPlugin("C:\Documents and Settings\XXXXXXX\Desktop\Copy of BD-RBV01808\BD_Rebuilder\tools\decomb521.dll")
FieldDeinterlace(blend=false)
Tweak(0.0,1.1,0.0,1.0)
WriteFile("C:\BD9S\GALAPAGOS H264 BD9\WORKFILES\INFO.INI",""" "[Options]" """)
WriteFile("C:\BD9S\GALAPAGOS H264 BD9\WORKFILES\INFO.INI",""" "framecount=" ""","framecount")
WriteFile("C:\BD9S\GALAPAGOS H264 BD9\WORKFILES\INFO.INI",""" "framerate=" ""","framerate")
WriteFile("C:\BD9S\GALAPAGOS H264 BD9\WORKFILES\INFO.INI",""" "width=" ""","width")
WriteFile("C:\BD9S\GALAPAGOS H264 BD9\WORKFILES\INFO.INI",""" "height=" ""","height")
ConvertToYV12()
trim(0,-1)


Regards,

YP I sure don't see anything wrong with this. I'm making a modification to BD-RB that makes the INFO file a backup method rather than the primary for getting this info.

[jdobbs]

I have tried what you said (I'm still waiting for someone to run the failed encode from the command line using LASTCMD.TXT so I can see what we're getting) but get no info when the error happens.. do i need to rerun with VERBOSE STATUS REPORTING on before seeing the error report?

Also i dont have vc-1 decoding on in FFDShow as at the min i get around 16fps but if i put it on i get arounf 0.35fps... do i need it on ? The best solution is to install Windows Media Player 11. It will install a WMV11 codec that works well. I'll be releasing v0.18.9 tomorrow -- hopefully it will help. The VERBOSE STATUS REPORTING just gives a little more detail in the logs...

[datman]

One of the 2 disc I have not been able to encode “Patton” was successful last night with 18.8.:thanks: I also rip to image with anydvd. I tried working off the disc last week and it failed. Anydvd would not rip the movie either. So I tried ripping to image, perhaps that was the fix.

Tonight I’m attempting to encode my hardest film “The Longest Day” I tried it 4 or 5 times. 1st I’m working from folder if that fails I will try from image. I will post my results

Yes it was sucessful:thanks: in 6.5 hours holy smokes was that fast

[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).

[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....

[DaMacFunkin]

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. ;)

To Be Fair I think Galapagos is about 10 hours long LOL, well maybe not that long but it is after all a documentry on all the wierd and wonderful creatures of Darwin land, so it does run for a bit.

[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 (http://forum.doom9.org/showpost.php?p=1247875&postcount=1130)).
Later I saw this post (http://forum.doom9.org/showthread.php?p=1248749#post1248749) 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?p=1248749&postcount=1

[Capsbackup]

Another successful backup, :thanks:
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. :rolleyes:

[dmancornell]

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 :D 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]

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]

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