BD Rebuilder Beta - Bug Reports Only

[canadian guy]

i did that but it keeps coming up this is not a BD file or somthing like that,,not BD image,,but in the stream folder the files do not appear,,should you see them,,then chose a file to load,,NO BD FILE FOUND,,thats what it says,,

[leChameleon]

I just wanted to confirm the PIP extra's in Weeds: Season 4 Disc 1 is not working with BD-RB 0.22.01 beta.
Full Backup, All Audio, All everything 47GB -> 25GB.
If you need anything from me please let me know.

[GaPony]

i did that but it keeps coming up this is not a BD file or somthing like that,,not BD image,,but in the stream folder the files do not appear,,should you see them,,then chose a file to load,,NO BD FILE FOUND,,thats what it says,,

When you rip the movie to your hard drive, it will be placed in a folder that has the same name as the volume lable of the original movie disc... such as C:\BD_Movies\Eastern_Promises. That's where you want to point the source...not to the sub-folders of that original folder.

[Furiousflea]

I just wanted to confirm the PIP extra's in Weeds: Season 4 Disc 1 is not working with BD-RB 0.22.01 beta.
Full Backup, All Audio, All everything 47GB -> 25GB.
If you need anything from me please let me know.

Not supposed to work yet, 2 video tracks in 1 m2ts hasn't been implemented yet.

[canadian guy]

When you rip the movie to your hard drive, it will be placed in a folder that has the same name as the volume lable of the original movie disc... such as C:\BD_Movies\Eastern_Promises. That's where you want to point the source...not to the sub-folders of that original folder.

thank you,,,i thought you had to to open up a file in the sub folder,,,like the stream folder,,thank you again,,cheers

[jdobbs]

Just posted a new version of BD-RB in the first post of this thread (v0.22.02). The changes for this version are:

- Corrected an error in which the CERTIFICATE folder
was not being properly removed (when it exists) from
movie-only encodes.
- Added code to use alternate means to obtain window
handle (for status bar update) when PID cannot be
obtained. This should prevent the confusing "50%
completed" display that incorrectly gives the
impression of an encoding freeze.
- Added a hidden option that will force movie-only
encodes into BLU-RAY format. This is enabled by
adding "FORCE_BLURAY=1" to the OPTIONS area of the
config file (BDREBUILDER.INI).
- Change the default for PRIORITY to IDLE rather than
NORMAL. This is typically the better setting.
- Other minor corrections and cosmetic fixes.

[Chefkoch_ico]

@jdobbs
At first, your last version works great. I am doing only full backups to bd25. I dont run into problems anymore, but one.

For playing the discs I am using a HTPC with PowerDVD8 and a LG 370 SAP.

Mostly all discs work on both players great. But full backups of european Universal titles have problems on PowerDVD and, so I heard here, on some Panasonic models.

When pressing on the main menu "Play movie" the screen gets black and the display time stays at 00:00. No way to play the disc, even after waiting 30 minutes the disc does not start.

Examples of movies are the Bourne triology.

Are you interested/have time to analyse this problem? Can I help you somehow with analysing?

Thx for your efforts.

[MikeyBK]

v0.22.02 still has the stuck at 50% issue. It still continues on and finishes both passes and the rebuild, but the progress bar just shows stuck at 50% after the first pass.

I haven't tested that playability on PS3s with Stricter AVCHD checked on movie-only.

[drmih]

@jdobbs
At first, your last version works great. I am doing only full backups to bd25. I dont run into problems anymore, but one.

For playing the discs I am using a HTPC with PowerDVD8 and a LG 370 SAP.

Mostly all discs work on both players great. But full backups of european Universal titles have problems on PowerDVD and, so I heard here, on some Panasonic models.

When pressing on the main menu "Play movie" the screen gets black and the display time stays at 00:00. No way to play the disc, even after waiting 30 minutes the disc does not start.

Examples of movies are the Bourne triology.

Are you interested/have time to analyse this problem? Can I help you somehow with analysing?

Thx for your efforts.

The european Universal titles work fine on bd-25 (I have done the Bourne series myself although using a much earlier version). On bd-9 there is an issue with the audio track on sony standalones. However, everything plays fine with TMT3.

[colinhunt]

Did my second "Full Backup to DVD9" encode last night with 0.22.01. Everything went fine until the Rebuilding phase.

[02:05:42] BD Rebuilder v0.22.01 (beta)
- Source: BDROM
- Input BD size: 20,47 GB
- Approximate total content: [01:48:49.723]
- Target BD size: 7,72 GB
[02:05:43] PHASE ONE, Encoding
- [02:05:43] Extracting audio/subs [VID_00000]
- [02:05:48] Collecting video information [00000]
- Video: 1920x1080, 23,976fps
- Bitrate: 8*374 Kbs
- [02:05:48] Reencoding: VID_00000, Pass 1 of 2
- [02:06:27] Reencoding: VID_00000, Pass 2 of 2
- [02:08:38] Video Encode complete
- [02:08:38] Reencoding audio tracks
- [02:08:39] Multiplexing M2TS
- [02:08:40] Extracting audio/subs [VID_00001]
- [02:08:42] Collecting video information [00001]
- Video: 1920x1080, 29,970fps
- Bitrate: 6*967 Kbs
- [02:08:42] Reencoding: VID_00001, Pass 1 of 2
- [02:08:51] Reencoding: VID_00001, Pass 2 of 2
- [02:08:59] Video Encode complete
- [02:08:59] Reencoding audio tracks
- [02:08:59] Multiplexing M2TS
- [02:09:00] Extracting audio/subs [VID_00003]
- [02:09:20] Collecting video information [00003]
- Video: 1920x1080, 23,976fps
- Bitrate: 7*973 Kbs
- [02:09:20] Reencoding: VID_00003, Pass 1 of 2
- [02:12:58] Reencoding: VID_00003, Pass 2 of 2
- [02:25:53] Video Encode complete
- [02:25:53] Reencoding audio tracks
- [02:25:53] Multiplexing M2TS
- [02:25:58] Extracting audio/subs [VID_00004]
- [02:26:05] Collecting video information [00004]
- Video: 1920x1080, 23,976fps
- Bitrate: 7*660 Kbs
- [02:26:05] Reencoding: VID_00004, Pass 1 of 2
- [02:27:10] Reencoding: VID_00004, Pass 2 of 2
- [02:30:27] Video Encode complete
- [02:30:27] Reencoding audio tracks
- [02:30:27] Multiplexing M2TS
- [02:30:28] Extracting audio/subs [VID_00005]
- [02:37:54] Collecting video information [00005]
- Video: 1920x1080, 23,976fps
- Bitrate: 9*019 Kbs
- [02:37:54] Reencoding: VID_00005, Pass 1 of 2
- [03:49:18] Reencoding: VID_00005, Pass 2 of 2
- [06:53:39] Video Encode complete
- [06:53:39] Reencoding audio tracks
- [06:53:39] Multiplexing M2TS
[06:55:55]PHASE ONE complete
[06:55:55]PHASE TWO - Rebuild Started
- [06:55:55] Rebuilding BD file Structure

I have a dialog box with a title of "Error Condition" on screen, with the text "BD Rebuilder experienced an error 2202 [06:55:55] RebuildBDFiles() 00052 2202" on it. I clicked OK and the line " - [06:55:55] RebuildBDFiles() 00052 2202" was added to the log, followed by "Aborted at user request".

I've done one successful "Full backup to DVD9" run earlier with 0.22.01, but used another PC for it. Both PCs are running WinXP Pro SP3. I've done several "Full Backup to BD25" encodes on this PC but using the previous version of BD Rebuilder; this was the first encoding with 0.22.01 on this PC.

Update: Well, I learned a lesson. Always keep the source data on the same PC you're doing the encoding with. I had ripped the original as an .ISO file, placed it on a NAS box and mounted it over LAN with Daemon Tools. At some point during the night the PC had decided to disconnect from the NAS share (I'd appreciate suggestions on how to stop that from happening!) and ruined the encode.

I re-mounted the ISO with Daemon Tools, clicked Backup on BD-RB and told it to continue previous job: it finished the rebuilding stage without problems. But since the connection to NAS had been disrupted, the output was only 5GB and half of the movie was missing, replaced by a gray screen, while audio played fine to the end.

[Chefkoch_ico]

The european Universal titles work fine on bd-25 (I have done the Bourne series myself although using a much earlier version). On bd-9 there is an issue with the audio track on sony standalones. However, everything plays fine with TMT3.
They dont work fine. They work fine IF using TMT3. But not on PowerDVD and not on some Panasonic SAP and who knows on what others players this problem exists.

[drmih]

They dont work fine. They work fine IF using TMT3. But not on PowerDVD and not on some Panasonic SAP and who knows on what others players this problem exists.

So given the fact that they work on the recommended Sony SAP (which he owns) and also on a pc with one type of media player, is there a bug in bd-rb and if so how would you identify it? I would assume that if a SAP isn't able to play full backups on bd-5/9 then the implementation could be a bit flaky on some discs done to bd-25.

[turbojet]

A little process of elimination on the PIP issue.

Does a universal BD25 with PIP burned on to a BDR play in the problematic player? If not it's a player issue.
Does the M2TS play ok in PowerDVD? If not the m2ts is part of the issue, more than likely mux problem. If yes, it's an issue with clpi, mpls, index.bdmv and/or movieobject.bdmv
Stripping any sub/audio streams? If yes, it's known that the mpls isn't updated correctly thus stripped streams are accessible by some players, try without stripping.

Beyond that I have no idea.

[jdobbs]

v0.22.02 still has the stuck at 50% issue. It still continues on and finishes both passes and the rebuild, but the progress bar just shows stuck at 50% after the first pass.

I haven't tested that playability on PS3s with Stricter AVCHD checked on movie-only. That's a disappointment. I changed the only thing that I could imagine as the cause, and the only thing that has changed related to it -- and after running numerous attempts on my system I still can't repeat it. I don't have a clue where to go from here.

1. What O/S are you using?
2. What version of X264 are you using?
3. Does it happen all the time, or just occasionally?
4. Could you post your BDREBUILDER.INI so I can try with the same settings?

Something has to be different that makes it happen on your system but not mine.

As an experiment, could you add the parameter "SHOW_ENCODER=1" to your BDREBUILDER.INI file? Then the X264 window will show when it is executing. See if, while the 2nd pass is executing, the window caption is being updated with the status, also -- capture the screen if you could so I can see what it looks like with the encode and BD-RB both running (and there is no update being made to the BD-RB GUI).

Your help would be greatly appreciated.

[MikeyBK]

That's a disappointment. I changed the only thing that I could imagine as the cause, and the only thing that has changed related to it -- and after running numerous attempts on my system I still can't repeat it. I don't have a clue where to go from here.

1. What O/S are you using?
2. What version of X264 are you using?
3. Does it happen all the time, or just occasionally?
4. Could you post your BDREBUILDER.INI so I can try with the same settings?

Something has to be different that makes it happen on your system but not mine.

As an experiment, could you add the parameter "SHOW_ENCODER=1" to your BDREBUILDER.INI file? Then the X264 window will show when it is executing. See if, while the 2nd pass is executing, the window caption is being updated with the status, also -- capture the screen if you could so I can see what it looks like with the encode and BD-RB both running (and there is no update being made to the BD-RB GUI).

Your help would be greatly appreciated.

You're right JD, it's not happening on the Bluray that I'm doing currently. The Express, which is VC-1, movie-only to BD-9, set to fast encoding setting, using the version of x264 that you've placed in the Tools folder at Normal priority.

I'll post the INI file of this current encoding, if you still need.
I had tested v0.22.02 on a few short test clips, which also showed the same 'stuck at 50%' charecteristic when it was happening with all the other movie encodings in v0.22.01.
I'll run another encoding later tonite and see if it also shows the progress bar correctly.

BTW, my OS is XP MCE SP3.

[Dingo27]

Powerdvd normally plays it fine when the disc is mounted from an iso. But in the last versions of BD_Rebuilder the screen in powerdvd was black while playing. So i demuxed the mounted movie with tsmuxer and became the info that the stream hasn`t an correct framerate, it was in that case 23,975fps.
Tried to fix the stream with h264info and muxed it again with tsmuxer, builded an iso again and powerdvd played it well.

I think BD_Rebuilder didn`t make any changes to the framerate, could it be that ffdshow did not set it correct?

sorry for my english, regards

dingo

[Furiousflea]

Could someone please explain why all output from BD-Rebuilder gets it's frame rate changed, this has been noted since the first release.

When you view the bluray details with eac3to frontend the frame rate for 23.976 video is changed to 23.975, same goes fo9r 60fps interlaced material, it gets changed to 59...something or other.

I asked this a long time ago at least twice with no response, hope the chief notices it this time :)


Thanx, :)

[GaPony]

Maybe... sometimes its better to not do so much investigating. I've never noticed any frame rate issues and am not sure how a 1/1000th fps would make any difference. Is it possible that its simply a mathematical difference in the computation used by the two programs?

[Dingo27]

Maybe... sometimes its better to not do so much investigating. I've never noticed any frame rate issues and am not sure how a 1/1000th fps would make any difference. Is it possible that its simply a mathematical difference in the computation used by the two programs?

i`m sure that i would make a difference dippending to what kind of player i`m using. My Pana BD-30 had always a black screen with movies that came from BD_Rebuilder, same disc played fine in my Pioneer 51FP. The Player`s from Panasonic keep the spezifications strictly and a framerate 23,975 fps isn`t correct. Maybe the same on Powerdvd ...

[MikeyBK]

BDInfo shows every on of my BDs output from BD-RB as 23.976.
Is there a reason it would show differently in BDInfo as opposed to eAC3to?

[Capsbackup]

BDInfo displays 23.976fps on all of my BD-RB backups too. Maybe it's a region code? My discs are all region A.
I have never had a BD-RB movie only backup to BD-5 or BD-9 not play on my Sony BDP-BX1. And before BD-RB, I used MeGui and TsMuxer, and everyone of those movie only backups played back too. I would suggest a quick visit to the local Best Buy or Fry's with the disc in hand that does not play on the Panasonic players, and test them out on other players, Sony in particular, and then maybe it could be related to BD-RB if it does not play correctly.

[GaPony]

i`m sure that i would make a difference dippending to what kind of player i`m using. My Pana BD-30 had always a black screen with movies that came from BD_Rebuilder, same disc played fine in my Pioneer 51FP. The Player`s from Panasonic keep the spezifications strictly and a framerate 23,975 fps isn`t correct. Maybe the same on Powerdvd ...

Given all that I have read on this forum, I would look first at the Panasonic being out of spec long before placing blame on BD Rebuilder. Its success rate for other brands (less Denon) seems to be too good.

I still think the frame rate difference of 23.975 vs. 23.976 is likely in the algorithm used by the various scanning/checking programs.

The Panasonic players have been the subject of several posts where 24p playback must be disabled for BD Rebuilder copies, which would point to a flaw in the player, not the software.

[turbojet]

The framerate issue is either eac3to not reading the x264 fps header correctly or x264 not outputting the correct fps header, eac3to detects fps of DivX H.264 and retail BD correctly.

With the Panasonic 24p issue I found another difference between RipBot264 and BD-RB. The full list of differences I've found that could make a difference are:
- x264 --nal-hrd in RipBot264
- x264 --aud in RipBot264 (no difference in mkv files)
- x264 --fps <fps> in RipBot264 (no difference in mkv files)
- RipBot264 outputs to .264 files
- x264 --keyint 250 --min-keyint 25 in RipBot264 (BD-RB uses --keyint 24 min-keyint 1)

[Dingo27]

it`s not only eac3to, tsmuxer shows also the framerate 23,975 fps from the stream rebuilded with BD_Rebuilder, and when the original stream is loaded in tsmuxer the correct framerate 23,976 fps.

[MikeyBK]

it`s not only eac3to, tsmuxer shows also the framerate 23,975 fps from the stream rebuilded with BD_Rebuilder, and when the original stream is loaded in tsmuxer the correct framerate 23,976 fps.

TSMuxer shows the BD-RB outputs as 23.976 for me.... as BDInfo does.

http://img5.imageshack.us/img5/3721/fps23976.th.png (http://img5.imageshack.us/my.php?image=fps23976.png)

[Capsbackup]

TSMuxer shows the BD-RB outputs as 23.976 for me.... as BDInfo does.

http://img5.imageshack.us/img5/3721/fps23976.th.png (http://img5.imageshack.us/my.php?image=fps23976.png)

I second that. All my backups have always shown 23.976fps.

[mouw]

v 22.02
using Alternate Movie to get 2-part BROKEN TRAIL --> 2 BD9s
x264 Encoder - Normal Priority - Highest Quality - Custom Size = 8250 - AC3 640kps audio
Overall Progress STUCK= 50% -- Encode Finishes OK

VISTA 32/Ultimate - Intel Q6600 cpu (NOT OverClocked)
Playback PowerDVD 7.3 / Sony BDP-S350 == OK
same problem w/ v22.01 == NO problems w/ v20.09
i do MOVIE only Encodes== this always happens since v22.01


[Options]
RESIZE=0
MODE=1
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
TRELLIS=1
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=1
AC3_REENCODE=1
AC3_640=1
KEEP_HD_AUDIO=0
AVCHD=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=8250
FORCE_BLURAY=1
PRIORITY_CLASS=0
ENCODE_QUALITY=3
TARGET_SIZE=8250
[Paths]
WORKING_PATH=C:\TEMP\REBUILDER\
SOURCE_PATH=C:\MOVIES\BROKEN_TRAIL_BD\

[Sharc]

The framerate issue is either eac3to not reading the x264 fps header correctly or x264 not outputting the correct fps header, eac3to detects fps of DivX H.264 and retail BD correctly.

With the Panasonic 24p issue I found another difference between RipBot264 and BD-RB. The full list of differences I've found that could make a difference are:
- x264 --nal-hrd in RipBot264
- x264 --aud in RipBot264 (no difference in mkv files)
- x264 --fps <fps> in RipBot264 (no difference in mkv files)
- RipBot264 outputs to .264 files
- x264 --keyint 250 --min-keyint 25 in RipBot264 (BD-RB uses --keyint 24 min-keyint 1)

Don't know if this is relevant: I have seen MPC (or MPC-HC) indicating weird (random?) framerates (check: properties ....) for x264 encoded DVD (720x576) PAL material (raw encoded video stream *.264). This resulted in an odd movie length indication in MPC and in difficulties with random seeking.
Converting the *.264 to *.mkv with mkvtools and enforcing 25fps solved the problem.

--nal-hrd requires a patched version of x264 IIRC. However, I understand that tsMuxeR adds this as well, so it may no longer be required for x264. I still do wonder why meGui still uses --nal-hrd for blu-ray encodes....

--keyint 24 instead of --keyint 250 is required for compliant blu-ray format. GOPs must not be longer than 1 second as I understand.

[GaPony]

v 22.02
using Alternate Movie to get 2-part BROKEN TRAIL --> 2 BD9s
x264 Encoder - Normal Priority - Highest Quality - Custom Size = 8250 - AC3 640kps audio
Overall Progress STUCK= 50% -- Encode Finishes OK

VISTA 32/Ultimate - Intel Q6600 cpu (NOT OverClocked)
Playback PowerDVD 7.3 / Sony BDP-S350 == OK
same problem w/ v22.01 == NO problems w/ v20.09
i do MOVIE only Encodes== this always happens since v22.01



This is obviously not effecting everyone equally. I haven't experienced the stuck progress bar with v.22.02 and only did a couple of movies with v.22.01, and didn't pay any attention.

[Tongariro]

That's a disappointment. I changed the only thing that I could imagine as the cause, and the only thing that has changed related to it -- and after running numerous attempts on my system I still can't repeat it. I don't have a clue where to go from here.

1. What O/S are you using?
2. What version of X264 are you using?
3. Does it happen all the time, or just occasionally?
4. Could you post your BDREBUILDER.INI so I can try with the same settings?

Something has to be different that makes it happen on your system but not mine.

As an experiment, could you add the parameter "SHOW_ENCODER=1" to your BDREBUILDER.INI file? Then the X264 window will show when it is executing. See if, while the 2nd pass is executing, the window caption is being updated with the status, also -- capture the screen if you could so I can see what it looks like with the encode and BD-RB both running (and there is no update being made to the BD-RB GUI).

Your help would be greatly appreciated.

Jdobbs
I can confirm that the progress bar is stuck on 22.02.
I did 2 movies already with it (Yes man and Starship troopers).
It is stuck for pass1 and for pass2 on muxing and demuxing its moving O.K.
I am using xp (not 64bit) and x264 is 1163 (latest).
It happens must of the time . I did observed that one of the MT2S i did saw pass1 moving but its one out of dozens.

:thanks:

[MikeyBK]

Here is a test clip that shows stuck on the progress bar @ 0% during both first and second passes.
Attached is a screenshot of the 'SHOW_ENCODER=1' parameter inserted into the INI which you requested.

http://img3.imageshack.us/img3/9072/showencodernoprogressup.th.png (http://img3.imageshack.us/my.php?image=showencodernoprogressup.png)

[GaPony]

Just out of curiosity, I changed the Target Size (copying Movie Only to BD9) from the default of 7910 to 8250 (based on mouo's settings) and got the progress bar to stick. I don't know why that single change would cause this issue. I did the exact same movie under the default settings and it worked fine.

[MikeyBK]

Just out of curiosity, I changed the Target Size (copying Movie Only to BD9) from the default of 7910 to 8250 (based on mouo's settings) and got the progress bar to stick. I don't know why that single change would cause this issue. I did the exact same movie under the default settings and it worked fine.

I think that you're on to something, I too set it to custom size, 8350 MBs. May help give some feedback to JD.

[ibanez]

Just out of curiosity, I changed the Target Size (copying Movie Only to BD9) from the default of 7910 to 8250 (based on mouo's settings) and got the progress bar to stick. I don't know why that single change would cause this issue. I did the exact same movie under the default settings and it worked fine.

My progress bar is sticking too. I was doing a movie only backup and had set the custom size also, at 8240.

[PurpleMan]

Hi. I got a couple of questions:

1. How does BD-RB decide what bitrate to use on extras? I tried doing "the dark knight" in full backup mode, and I found that it used a 5000kbit/sec bitrate on a VC1 extra that was originally 10000kbit/sec, so that's 50% less. Is this normal? configurable?

2. Off-topic, does anyone know the exact size in bytes that can be written to a BD-R25?

Thanks everyone, and jdobbs - keep up the good work!

-purpleman2k

[Furiousflea]

I second that. All my backups have always shown 23.976fps.

All well and good....

But the issue remains, and it is a very real one. The original bluray in eac3to is shown correctly. The backup isn't, therefore something is wrong with the backup. eac3to likely does a much deeper (proper) analysis than tsmuxer. I haven't used bdinfo before to check although I am aware that tsmuxer reports no problem.

Pretty weird.

[GaPony]

My progress bar is sticking too. I was doing a movie only backup and had set the custom size also, at 8240.

Try setting it back to the default of 7910 and rerun it to see if it still sticks. :)

I know it takes alot of time, but its in the name of science. ;)

[jdobbs]

Could someone please explain why all output from BD-Rebuilder gets it's frame rate changed, this has been noted since the first release.

When you view the bluray details with eac3to frontend the frame rate for 23.976 video is changed to 23.975, same goes fo9r 60fps interlaced material, it gets changed to 59...something or other.

I asked this a long time ago at least twice with no response, hope the chief notices it this time :)


Thanx, :) My guess: eac3to is wrong. It looks like a rounding error in the reporting. BD Rebuilder doesn't have the capability to set it to anything other than one of the BD standards. But of course I'll look at it.

One possibility: X264 will determine the playback rate from the frame server used. If your codec is reporting it incorrectly it may get passed through... I've never see it happen though, and I'm not even sure that it is possible. I can always force the framerate with --fps easy enough and will, but I have no confidence that it will have an effect.

[jdobbs]

The framerate issue is either eac3to not reading the x264 fps header correctly or x264 not outputting the correct fps header, eac3to detects fps of DivX H.264 and retail BD correctly.

With the Panasonic 24p issue I found another difference between RipBot264 and BD-RB. The full list of differences I've found that could make a difference are:
- x264 --nal-hrd in RipBot264
- x264 --aud in RipBot264 (no difference in mkv files)
- x264 --fps <fps> in RipBot264 (no difference in mkv files)
- RipBot264 outputs to .264 files
- x264 --keyint 250 --min-keyint 25 in RipBot264 (BD-RB uses --keyint 24 min-keyint 1) --nal-hrd has been proven not to make a difference.

--aud is included in the BD-RB command line

--fps shouldn't make a difference, but I can easily add it

--keyint 250 is a violation of the BD and AVCHD standards.

I'd say the Panasonic is the issue...

[jdobbs]

Just out of curiosity, I changed the Target Size (copying Movie Only to BD9) from the default of 7910 to 8250 (based on mouo's settings) and got the progress bar to stick. I don't know why that single change would cause this issue. I did the exact same movie under the default settings and it worked fine. Hmmm... can't imagine the connection -- but stranger things have happened. I'll do some testing.

[GaPony]

Hmmm... can't imagine the connection -- but stranger things have happened. I'll do some testing.

Looking a bit closer... When I edited the config file setting of TARGET_SIZE=7910 to read 8250, saved the file and restarted, and clicked "Backup", it stuck at 50%. After completion, I re-checked the settings and TARGET_SIZE setting was set to the same size as the CUSTOM_TARGET_SIZE setting.

Then I went into settings and changed the CUSTOM_TARGET_SIZE box to 8250, re-ran the Backup and it didn't stick.

So basically, if I changed to TARGET_SIZE manually in the config file, it sticks. If I change the CUSTOM_TARGET_SIZE in the settings window (GUI) it works as it should. If I don't make any changes to the default settings for a movie only copy to BD9, it works normally.

I don't know what this means, but I hope it helps.

[jdobbs]

Here is a test clip that shows stuck on the progress bar @ 0% during both first and second passes.
Attached is a screenshot of the 'SHOW_ENCODER=1' parameter inserted into the INI which you requested.

http://img3.imageshack.us/img3/9072/showencodernoprogressup.th.png (http://img3.imageshack.us/my.php?image=showencodernoprogressup.png)Is it still running? It looks like it should be errored out because of the illegal (higher than max) bitrate?

[PurpleMan]

My guess: eac3to is wrong. It looks like a rounding error in the reporting. BD Rebuilder doesn't have the capability to set it to anything other than one of the BD standards. But of course I'll look at it.

One possibility: X264 will determine the playback rate from the frame server used. If your codec is reporting it incorrectly it may get passed through... I've never see it happen though, and I'm not even sure that it is possible. I can always force the framerate with --fps easy enough and will, but I have no confidence that it will have an effect.

DGAVCIndex also reports the encoded BD-RB stream as 23.975986 fps. Opening the original m2ts with DGVC1Index shows 23.976024 fps.

[mouw]

if I changed to TARGET_SIZE manually in the config file, it sticks. If I change the CUSTOM_TARGET_SIZE in the settings window (GUI) it works as it should. If I don't make any changes to the default settings for a movie only copy to BD9, it works normally.

i always change Custom Target in Settings win (GUI)

edited Config File-- SHOW_ENCODER=1
now encoding the International == Movie Only
set Custom Target = 24300 (for BD25)
Keep HD Audio

Encoding process just went to PASS 2/2
both GUI Overall Progress & x264 DOS window show progress 50+% and counting

so NOW it's working ??

[ibanez]

Try setting it back to the default of 7910 and rerun it to see if it still sticks. :)

I know it takes alot of time, but its in the name of science. ;)

Ok, tried it again with the Target Size set to BD-9(DVD-9) (TARGET_SIZE=7910), and it worked. Used the same source as before (Blood Diamond), did a movie only backup as before, with the same settings "Do not convert DTS to AC3" and "Do not reencode AC3". Source video was VC-1 1080p 23.976fps and audio was 640 Kbps AC-3.

This time the progress bar kept updating after pass 2 commenced (current progress = 13.20% and overall progress = 56.60%). Previous the progress bar would stick at the end of pass 1 on 100% and 50% respectively.

I'll try again with the original custom setting (TARGET_SIZE=8240) and see if the problem occurs again.

[MikeyBK]

No it doesn't error out, it keeps running and finishes. It may be the test clip I'm using which causes what you're seeing.

I'll do a movie-only of a actual Bluray with SHOW-ENCODER=1 set and see if it gets stuck @ 50%.
I was thinking it might be what GaPony might be suspecting about the custom target size, however with that same setting the last encoding did not have the progress bar stuck.

Anyways, I'll post the screenshot of the show encoder again when I do the Bluray.

[turbojet]

--nal-hrd has been proven not to make a difference.

--aud is included in the BD-RB command line

--fps shouldn't make a difference, but I can easily add it

--keyint 250 is a violation of the BD and AVCHD standards.

I'd say the Panasonic is the issue...

I posted it mainly for those that are testing to find out what makes a difference with RipBot264 with 24p on some Panasonic players. I don't see a reason to change anything without knowing what it is.

[jdobbs]

No it doesn't error out, it keeps running and finishes. It may be the test clip I'm using which causes what you're seeing.

I'll do a movie-only of a actual Bluray with SHOW-ENCODER=1 set and see if it gets stuck @ 50%.
I was thinking it might be what GaPony might be suspecting about the custom target size, however with that same setting the last encoding did not have the progress bar stuck.

Anyways, I'll post the screenshot of the show encoder again when I do the Bluray. I used to do a search of the active windows to find X264, and then pull the stats from the caption. In v0.22.1 I changed it so I used the process ID from the shell execution to find the window in order to prevent it from ever grabbing the wrong window. I think it's randomly failing to find the window for some odd reason only on pass 2 and only on certain computers. Weird. Even more weird is that it has never once happened to me. Ever. And I've been trying like hell to make it happen.

I'm just going to go back to the original way I grabbed the window.

[turbojet]

DGAVCIndex also reports the encoded BD-RB stream as 23.975986 fps. Opening the original m2ts with DGVC1Index shows 23.976024 fps.

Good find. Someone should really post these issues in the H.264 forum as it's an x264 issue.

EDIT: I posted it in the H.264 forum.

I'm just going to go back to the original way I grabbed the window.

I can see a fix and really some needed cleanup from the last few posts, removing one or the other TARGET_SIZE parameters in the ini, wouldn't fixing it be better then re-introducing an old bug?

Did you get around to removing --stats and --pass from crf encodes as well?

[leChameleon]

Removed. I'll post side by side comparisons.