BD Rebuilder Beta - Bug Reports Only

[jdobbs]

@bcovington

Uninstall BD-RB and all utilities. Then reinstall using only those from the first post of this thread. There are numerous reasons those specific versions are used.

Run INSPECT.EXE (in the BD Rebuilder installation folder) and it should tell you inconsistencies.

[had-z]

Hi again, i do the backup of The Dark Knight again with LAVF decoder and is showing the same issue...

I shall try changing the decoder of VC-1 to WM11 (disabled) on Windows 7?

[bcovington]

@bcovington

Uninstall BD-RB and all utilities. Then reinstall using only those from the first post of this thread. There are numerous reasons those specific versions are used.

Run INSPECT.EXE (in the BD Rebuilder installation folder) and it should tell you inconsistencies.

ffdshow was the only one "out of compliance" - I uninstalled the bad and installed the good. Ran inspect.exe and it all checked out OK. I am at 92% on my second attempt on the movie. I'll let you know if it does not work.
Thanks.

[jdobbs]

ffdshow was the only one "out of compliance" - I uninstalled the bad and installed the good. Ran inspect.exe and it all checked out OK. I am at 92% on my second attempt on the movie. I'll let you know if it does not work.
Thanks. If you still have an issue -- please reinstall all as I suggested. There are some things that INSPECT can't catch, especially when other software intercepts things. A reinstall can sometimes correct that.

[jdobbs]

Hi again, i do the backup of The Dark Knight again with LAVF decoder and is showing the same issue...

I shall try changing the decoder of VC-1 to WM11 (disabled) on Windows 7? I have to believe it is the source then - or a system issue. There's no way that two different frame-servers could result in that same problem happening in the same place.

I have "Dark Knight" and I'll do a test run and see if I can find that same scene.

[bcovington]

If you still have an issue -- please reinstall all as I suggested. There are some things that INSPECT can't catch, especially when other software intercepts things. A reinstall can sometimes correct that.

Attempt 2 failed, but not as badly as attempt 1. This time, I got 1hr 44 minutes of the movie in excellent quality. Video ends but audio continues. Workfiles folder is 7.5gb. The output folder (bdmv stream) is only 3.7gb. The 0000.m2ts video in workfiles is 2.93gb and contains the 1:44 of video.

I will uninstall all and try #3. Thanks.

[jdobbs]

Attempt 2 failed, but not as badly as attempt 1. This time, I got 1hr 44 minutes of the movie in excellent quality. Video ends but audio continues. Workfiles folder is 7.5gb. The output folder (bdmv stream) is only 3.7gb. The 0000.m2ts video in workfiles is 2.93gb and contains the 1:44 of video.

I will uninstall all and try #3. Thanks. If you are overclocked... slow your system down a bit. If it didn't finish the encode it means that X264 must have failed somehow. When that happens it is almost always an indicator of system problems (often overclocking).

[matiypau]

Hi I have a big problem with bdrebuilder
When i can resume the job, says THE WORKING PATH IS NOT EMPTY, DELETE ALL OLD FILES
Can you help me PLEASE !!

[jdobbs]

Hi I have a big problem with bdrebuilder
When i can resume the job, says THE WORKING PATH IS NOT EMPTY, DELETE ALL OLD FILES
Can you help me PLEASE !!That means that you have changed one or more settings between the time you stopped and restarted. BD Rebuilder would need to start over to support the new setting(s).

[bcovington]

If you are overclocked... slow your system down a bit. If it didn't finish the encode it means that X264 must have failed somehow. When that happens it is almost always an indicator of system problems (often overclocking).

Not overclocked. No tweaks to my system whatsoever.
Attemp #3 failed. Output was only 1.9gb.... 44 minutes of video. I don't know what data I could post to assist you. Here is what I see.

-----------------------
[00:40:40] BD Rebuilder v0.37.07 (beta)
- Source: STARTREK11D1AC
- Input BD size: 36.85 GB
- Approximate total content: [02:06:50.269]
- Target BD size: 4.36 GB
- Windows Version: 6.0 [6001]
- MOVIE-ONLY mode enabled
- Auto Quality: High Quality (Default), Two Pass
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[00:40:40] PHASE ONE, Encoding
- [00:40:40] Extracting A/V streams [VID_00000]
- [01:17:15] Reencoding: VID_00000 (1 of 1)
- [01:17:15] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 182,464 frames
- Bitrate: 3,721 Kbs
- [01:17:16] Reencoding: VID_00000, Pass 1 of 2
- [04:19:26] Reencoding: VID_00000, Pass 2 of 2
- [12:51:54] Video Encode complete
- [12:51:58] Reencoding audio tracks (if req'd)
- [12:58:03] Multiplexing M2TS
[13:01:23]PHASE ONE complete
[13:01:23]PHASE TWO - Rebuild Started
- [13:01:23] Rebuilding AVCHD file Structure
[13:05:09] - Encode and Rebuild complete
[13:05:09]JOB: STARTREK11D1AC finished.

and...

[Status]
LABEL=STARTREK11D1AC
VERSION=v0.37.07 (beta)
SOURCE_SIZE=39570505728
SOURCE_VIDEO_SIZE=39570505728
TARGET_SIZE=4686086144
REDUCTION=.118423711241177
RESIZE_1080=0
AUDIO_TO_KEEP=eng
KEEP_HD_AUDIO=0
SUBS_TO_KEEP=all
BACKUP_MODE=1
MOVIEONLY_TYPE=0
USE_LAVF=0
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=1
[00000]
AUDIO=1000
PGS=1011100
M2TS_TARGET=4686086144
RATE=3721
NSTART=27000000
NEND=369462240
NSIZE=1257682944
FLINK=0
MLINK=0

Thanks.

[Capsbackup]

Not overclocked. No tweaks to my system whatsoever.
Attemp #3 failed. Output was only 1.9gb.... 44 minutes of video. I don't know what data I could post to assist you. Here is what I see.


Perhaps you could try opening VID_00000.avs, which is found in the Workfiles folder, with MPC or VirtualDub. See if it will display the full time code and if it will advance thru the entire movie.
You could also try opening VID_00000.m2ts with MPC or WMP and see what it reports for total time and if it plays throughout.
What did you use to rip the disc with?

[jdobbs]

@bcovington

Unfortunately though, this problem isn't happening to anyone else -- and your system is the only thing unique to the issue. I really don't think it is a bug in BD-RB.

Here is the output size used for the encode:

SOURCE_VIDEO_SIZE=39570505728

Here's the bitrate:

RATE=3721

It appears to be failing before the encode is complete -- that is almost assuredly the result of system problems.

[Ch3vr0n]

When i try to backup Harry Potter 5, i keep getting this error

"Target size too small to continue", i've tried it with versions dating back to 37.04. Each and everyone gives that error. When i try to backup HP6, v37.07 has no problems. The weird thing is, BDRB is set to do a full disc backup to BD25. So it should work.

Bug ?

http://img858.imageshack.us/f/bdrbtargettoosmall.png/

BD-REBUILDER.LOG

[22:39:35] BD Rebuilder v0.37.07 (beta)
- Source: HP5_PHOENIX
- Input BD size: 44,42 GB
- Approximate total content: [05:03:47.266]
- Target BD size: 22,95 GB
- Windows Version: 6.0 [6002]
- Auto Quality: Good (Very Fast), Two Pass
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Target too small. Encode stopped.

BD-REBUILDER.INI

[Options]
MODE=0
ENCODE_QUALITY=0
ONEPASS_ENCODING=0
AUTO_QUALITY=1
AUDIO_TO_KEEP=dut;eng;nld;und;
SUBS_TO_KEEP=dut;eng;nld;und;
SD_CONVERT=0
COLOR_BOOST=0
RESIZE_1080=0
DEINTERLACE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=0
REMOVE_WORKFILES=1
FULL_AVCHD=0
REMOVE_OUTPUT=1
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23450
PRIORITY_CLASS=1
TARGET_SIZE=23500
AUTO_BURN=2
IMGBURN_TARGET_DEVICE=e:
QUICK_EXTRAS=1
MINIMIZE_TO_TRAY=1
OPEN_GOP=0
MOVIE_ONLY_LOOP=0
USE_FILTERS=0
USE_LAVF=1
VERBOSE_STATUS=1
BDMV_CERT_ONLY=1
IVTC_PULLDOWN=1
ASSUME_DVD_PAL=1
VERSION=0.37.0.7
SD_TO_1080=0
CONVERT_WIDE=0
[Paths]
WORKING_PATH=C:\TEMP\
SOURCE_PATH=Y:\BLU-RAY\HP5_PHOENIX\


HP 7 pt 1. for example wich is 39GB works fine

[bcovington]

Perhaps you could try opening VID_00000.avs, which is found in the Workfiles folder, with MPC or VirtualDub. See if it will display the full time code and if it will advance thru the entire movie.
You could also try opening VID_00000.m2ts with MPC or WMP and see what it reports for total time and if it plays throughout.
What did you use to rip the disc with?

Thanks. The vid_00000.avs is a tiny file. The vid_00000.avs.264 is 3.3gb - but it won't play in mpc or vdub or vmc, etc. There is no vid_0000.m2ts, but there is a 0000.m2ts and it is the truncated size of 1.17gb, 44 mins of video.

Thanks for trying to help. It appears to be some kind of system problem. Since, everything works correctly but it just can't finish the file completely.

[bcovington]

@bcovington

Unfortunately though, this problem isn't happening to anyone else -- and your system is the only thing unique to the issue. I really don't think it is a bug in BD-RB.

Here is the output size used for the encode:

SOURCE_VIDEO_SIZE=39570505728

Here's the bitrate:

RATE=3721

It appears to be failing before the encode is complete -- that is almost assuredly the result of system problems.

Thanks for trying. I don't doubt your answer. But that leaves me little that I can do. My system is Vista Ultimate, 32bit, Intel Core 2 Duo, E8400@3GHz, 2Gig of Ram.

Strangely, the movie output from attempt #2 that resulted in 1:44 mins of the movie took less time to process (9hrs) than the 2 attempts that resulted in much smaller file sizes (12+hrs).

I am running BD RD in high priority mode and leaving the computer mostly undisturbed during the process.

My source file is the original bluray movie ripped to iso using anydvd hd. So, I mount the iso and select that virtual drive as the source.

Can you point me to an earlier BD RB set up? I will gladly try to make it work with a previous configuration.
Thanks.

[Capsbackup]

Thanks. The vid_00000.avs is a tiny file. The vid_00000.avs.264 is 3.3gb - but it won't play in mpc or vdub or vmc, etc. There is no vid_0000.m2ts, but there is a 0000.m2ts and it is the truncated size of 1.17gb, 44 mins of video.

Thanks for trying to help. It appears to be some kind of system problem. Since, everything works correctly but it just can't finish the file completely.

Sorry, I meant 00000.m2ts. :) If it is only 44 minutes, then there must be other .m2ts files within the playlist (mpls) for the movie.
When you select the playlist thru mode, other movie-only playlist, what does it say the playlist / playlength options are?
When you select the one you want, and before you select Backup, what other VID_xxxx numbers are listed to be encoded?

EDIT:
Though I don't think it is related, you might try using AnyDVD to "Rip Video DVD to Harddisk" option. This always works for me!

If you right click on the VID_00000.avs and select "open with" and direct it to mpc.exe, it will play. The reason I mention this is it is this VID_00000.avs that is being frame served to x264, so it should have the entire correct video length there, and that is what will be reencoded.

[bcovington]

Sorry, I meant 00000.m2ts. :) If it is only 44 minutes, then there must be other .m2ts files within the playlist (mpls) for the movie.
When you select the playlist thru mode, other movie-only playlist, what does it say the playlist / playlength options are?
When you select the one you want, and before you select Backup, what other VID_xxxx numbers are listed to be encoded?

EDIT:
Though I don't think it is related, you might try using AnyDVD to "Rip Video DVD to Harddisk" option. This always works for me!

If you right click on the VID_00000.avs and select "open with" and direct it to mpc.exe, it will play. The reason I mention this is it is this VID_00000.avs that is being frame served to x264, so it should have the entire correct video length there, and that is what will be reencoded.

Well, the playlist only contains Playlist 00000- playlength 2:06:50 [16 capters]. No other files. I am using an anydvd "ripped to disk" iso as my source. The VID_0000.avs file is only 174bytes but it does play (black screen, no video, no sound) in MPC indicating the correct length of 02:06:50. It seems that BDRB does everything correctly, but somehow gets an instruction that the video is finished too soon. I've done it 3 times and gotten 3 different file lengths/sizes, 20 minutes, 1:45 and 44 minutes. So there is no discernable trigger. The audio is complete.

[Capsbackup]

Well, the playlist only contains Playlist 00000- playlength 2:06:50 [16 capters]. No other files. I am using an anydvd "ripped to disk" iso as my source. The VID_0000.avs file is only 174bytes but it does play (black screen, no video, no sound) in MPC indicating the correct length of 02:06:50. It seems that BDRB does everything correctly, but somehow gets an instruction that the video is finished too soon. I've done it 3 times and gotten 3 different file lengths/sizes, 20 minutes, 1:45 and 44 minutes. So there is no discernable trigger. The audio is complete.

Rip to harddisk is different than to ISO. You will not need to mount the files, so perhaps Vista will be more "forgiving" to process it this way. :rolleyes:
If you try to play the original 00000.m2ts with MPC, does it play?
The VID_00000.avs will not have sound when played with MPC, but should have the original video. If it does not and has only a black screen, you have another issue.
Since it will not hurt, I would uninstall haali, delete the program folder for haali, uninstall ffdshow and avisynth. Reboot. Then install the ones available from page one of this thread. ( even if you did this before, do it again and make sure you delete the program folder for haali!)

[bcovington]

Rip to harddisk is different than to ISO. You will not need to mount the files, so perhaps Vista will be more "forgiving" to process it this way. :rolleyes:
If you try to play the original 00000.m2ts with MPC, does it play?
The VID_00000.avs will not have sound when played with MPC, but should have the original video. If it does not and has only a black screen, you have another issue.
Since it will not hurt, I would uninstall haali, delete the program folder for haali, uninstall ffdshow and avisynth. Reboot. Then install the ones available from page one of this thread. ( even if you did this before, do it again and make sure you delete the program folder for haali!)

OK, I'll get the files out of the iso. I'll uninstall/reinstall per your instructions. The .m2ts file plays fine, audio and video - it is just too short. The .avs is just black screen in MPC.
I opened it in notepad and it is pointing to the correct file in the bdmv/stream folder on my virtual drive.
I'll try it all again with the bd files on the hard drive. Who knows, maybe the 4th try will work.
Thanks.

[bcovington]

The VID_00000.avs will not have sound when played with MPC, but should have the original video. If it does not and has only a black screen, you have another issue.

By the way, what is the other "issue" related to the black screen? Is there something I can do about that in ffdshow settings, AviSynth, yv12, etc?
Thanks.

[Capsbackup]

By the way, what is the other "issue" related to the black screen? Is there something I can do about that in ffdshow settings, AviSynth, yv12, etc?
Thanks.

I am not sure why, but you should be able to see video when playing this .avs file with MPC. If not, then I believe a DirectshowSource problem exists.
Since this does not appear to be a BD-RB bug, it should be moved or you can start a new thread for further discussion. :)

[jz1276]

My backups are taking 23 hrs to complete. XP serv pack3 AMD 64 processsor 4000+ / 1.43 GB RAM. Is this normal?

[omegaman7]

My backups are taking 23 hrs to complete. XP serv pack3 AMD 64 processsor 4000+ / 1.43 GB RAM. Is this normal?

Sounds about right. You might be able to shave some time, Depending on the scenario though.

Settings, Encoder settings, Good (very fast). You can't be under automatic settings of course ;) And of course your 4000+ is limited. 3 Cores or more is preferred.

[bcovington]

Rip to harddisk is different than to ISO. You will not need to mount the files, so perhaps Vista will be more "forgiving" to process it this way. :rolleyes:
If you try to play the original 00000.m2ts with MPC, does it play?
The VID_00000.avs will not have sound when played with MPC, but should have the original video. If it does not and has only a black screen, you have another issue.
Since it will not hurt, I would uninstall haali, delete the program folder for haali, uninstall ffdshow and avisynth. Reboot. Then install the ones available from page one of this thread. ( even if you did this before, do it again and make sure you delete the program folder for haali!)

Attempt #4 failed with an error. I had not gotten errors on previous attempts. This time, I had the bdmv files on the hard drive instead of inside and iso in a virtual drive. If you see an obvious error, let me know. Otherwise I guess I am just going to give up. Thanks.

-----------------------
[21:19:28] BD Rebuilder v0.37.07 (beta)
- Source: STAR_TREK
- Input BD size: 36.85 GB
- Approximate total content: [02:06:50.269]
- Target BD size: 4.36 GB
- Windows Version: 6.0 [6001]
- MOVIE-ONLY mode enabled
- Auto Quality: High Quality (Default), Two Pass
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[21:19:28] PHASE ONE, Encoding
- [21:19:28] Extracting A/V streams [VID_00000]
- [21:40:52] Reencoding: VID_00000 (1 of 1)
- [21:40:52] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 182,464 frames
- Bitrate: 3,721 Kbs
- [21:40:52] Reencoding: VID_00000, Pass 1 of 2
- [00:41:13] Reencoding: VID_00000, Pass 2 of 2
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
- BD-Rebuilder v0.37.07 (beta)
- Windows Version: 6.0 [6001]
- AVISYNTH Version: 2.5.7.0, Ok
- HAALI Splitter: Ok
- FFDSHOW: 3326, Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
[05:10:06] - Failed video encode, aborted

[jdobbs]

@bcovington

You really don't need to post everytime you try to encode and clutter up the thread -- logic tells us that it is going to keep on failing until you find the cause. As I said before, the problem happens only on your system. I'm personally convinced it is an issue with either your source or (more likely) your system. You may want to think about reseating your memory and/or checking the temperature of your processor.

Since right now I don't think it is an issue with BD Rebuilder itself, I'd suggest you move this discussion to a new thread.

[jdobbs]

@Ch3vr0n

I'll pick up "Order of the Phoenix" and run it. I thought I'd run that one before but I can't seem to find it now. That message means that after adding up all the content (audio/video) that must remain intact, there isn't any room left.

[Ch3vr0n]

I think i've found the problem. All streams are identified as english. See image 1. however on the box cover the audio streams are PCM: English 5.1, Dolby digital: English, Netherlands, Flemish, french, german, spanish, italian, danish swedish and japanese 5.1. See image 2. Image 2 also shows "audio 13" wich is the flemish stream, but PDVD can't identify it properly. Thats probably a PDVD issue and not BDRB. But bdrb thinks they're all english. Which is probably why it thinks theirs no room left. If i manually deselect the unwanted streams (being all of them except the 2 english streams and audio 13). BDRB still can't run. The disc is R2 belgian: with barcode 7321906156947

http://img222.imageshack.us/img222/9489/bdrballenglishaudio.png
http://img163.imageshack.us/img163/7939/sam0567.jpg

2nd image is link only due to being too big in screen size

[bcovington]

@bcovington

You really don't need to post everytime you try to encode and clutter up the thread -- logic tells us that it is going to keep on failing until you find the cause. As I said before, the problem happens only on your system. I'm personally convinced it is an issue with either your source or (more likely) your system. You may want to think about reseating your memory and/or checking the temperature of your processor.

Since right now I don't think it is an issue with BD Rebuilder itself, I'd suggest you move this discussion to a new thread.

I am cluttering up your 587 page long thread? I am posting results after attempting the changes that have been suggested by other forum members.
It may very well be my system. But my system accurately completes everything else I ask it to do.
And, I found this particular thread because I saw a post from someone who had the exact same problem. He got no solution either.
I am not going away mad. I am just going away. The software does not work for me and it's not worth the trouble anyway.
Thanks for your help, and especially the suggestions I received from others.

[omegaman7]

Bcovington:

I think what Jdobbs means by "Cluttering up" is anything that is NOT a probable bug. Since he believes you have a system issue, E.g. Ram errors, Cpu overclock errors, etc. He requests you take it to a new thread for resolving. It's not personal, just logical ;)

[had-z]

... Seems like my problem is related to the codecs VC-1 and MPEG-2 and always was here...
Because the first 2 movies that i backuped was x264 sources (Main movie and extras) Iron Man 2 and Transformers 2 resulting in perfect quality, Today i do the backup of X-men 1 Disc 1, The main movie was encoded perfectly (x264) but when i test some extras discover a new bug/issue.

http://i53.tinypic.com/156bjh3.jpg

How i can delete the register of the required programs FFdshow and Avisynth? or test the frameserving?

[jdobbs]

I am cluttering up your 587 page long thread? I am posting results after attempting the changes that have been suggested by other forum members.
It may very well be my system. But my system accurately completes everything else I ask it to do.
And, I found this particular thread because I saw a post from someone who had the exact same problem. He got no solution either.
I am not going away mad. I am just going away. The software does not work for me and it's not worth the trouble anyway.
Thanks for your help, and especially the suggestions I received from others. Sigh... I guess the other several thousand people who are using it and don't have your problem must be missing something. I'm simply telling you the facts, whether you accept it is up to you.

But my system accurately completes everything else I ask it to do. As anyone here at DOOM9 can tell you, video encoding (especially X264) is very demanding and it will find issues on your system that would be hidden to other apps... it's the ultimate stability tester.

Good luck.

[Discoboy]

Hi jdobbs,

Is this a bug, a setting I have not correctly set or code that is not implemented yet for this situation?

Background:
Machete – region B, Movie only, 1080p to 720p downsize, target size BD-5

This movie has a lot of forced subs especially in the first 5 mins of the movie for the Mexican spoken. In the above project the forced subs are not displayed until I manually press the subs button on the players remote. But when the forced subs have finished the subs still stay displayed i.e. now over the English that is spoken until I turn the subs off again via the players remote.

If I run again the project but do NOT downsize:
Machete – region B, Movie only, 1080p, target size BD-9

With this project the forced subs are correctly auto displayed and cleared when finish i.e. no user intervention is needed via the player remote.

To complete this project at 720p / BD-5 with forced subs auto enabled I used Ripbot264 as this has an option to select the forced subs as well as the standard subs for a downsized 720p movie.

Many thanks in advance for your help

[jdobbs]

Hi jdobbs,

Is this a bug, a setting I have not correctly set or code that is not implemented yet for this situation?

Background:
Machete – region B, Movie only, 1080p to 720p downsize, target size BD-5

This movie has a lot of forced subs especially in the first 5 mins of the movie for the Mexican spoken. In the above project the forced subs are not displayed until I manually press the subs button on the players remote. But when the forced subs have finished the subs still stay displayed i.e. now over the English that is spoken until I turn the subs off again via the players remote.

If I run again the project but do NOT downsize:
Machete – region B, Movie only, 1080p, target size BD-9

With this project the forced subs are correctly auto displayed and cleared when finish i.e. no user intervention is needed via the player remote.

To complete this project at 720p / BD-5 with forced subs auto enabled I used Ripbot264 as this has an option to select the forced subs as well as the standard subs for a downsized 720p movie.

Many thanks in advance for your help The SUP file has a flag within it (I'm not sure which flag it is) that "forces" it. When TSMUXER resizes the sub to 720, somehow that flag isn't transferred.

I wish knew where that flag was stored -- and I'd set it. Documentation on BD SUP files is scarce. I have a couple things I've dug up (showing how the object/segment formats) but I don't see the flag forces the subs on. I know its there, though -- because it continues to work if you don't resize.

You can turn subs ON by default in BD Rebuilder by right clicking on the subtitle and clicking "Default On", but as you noted, that doesn't help in your situation. In other movies, however, the "forced" subs are in a separate stream and can be left on.

I'll do some research today and see what I can find.

[jdobbs]

The SUP file has a flag within it (I'm not sure which flag it is) that "forces" it. When TSMUXER resizes the sub to 720, somehow that flag isn't transferred.

I wish knew where that flag was stored -- and I'd set it. Documentation on BD SUP files is scarce. I have a couple things I've dug up (showing how the object/segment formats) but I don't see the flag forces the subs on. I know its there, though -- because it continues to work if you don't resize.

You can turn subs ON by default in BD Rebuilder by right clicking on the subtitle and clicking "Default On", but as you noted, that doesn't help in your situation. In other movies, however, the "forced" subs are in a separate stream and can be left on.

I'll do some research today and see what I can find.
[Edit] Hmmm... well that didn't take long. I found it in the docs I have. I'll try to have it fixed for the next release. I'll probably have to resize the subs myself, though -- as TSMUXER's output for 720p would have it missing already.

[jdobbs]

... Seems like my problem is related to the codecs VC-1 and MPEG-2 and always was here...
Because the first 2 movies that i backuped was x264 sources (Main movie and extras) Iron Man 2 and Transformers 2 resulting in perfect quality, Today i do the backup of X-men 1 Disc 1, The main movie was encoded perfectly (x264) but when i test some extras discover a new bug/issue.

How i can delete the register of the required programs FFdshow and Avisynth? or test the frameserving? Uninstall everything and reinstall using only the versions linked in the first post of this thread. Also, look through your system and see if you can find other programs that are interfering with the CODEC settings.

You can see if the CODECs are working by installing "Media Player Classic" (MPC). Then open the AVS with MPC. If it plays back correctly, the odds are very high that it will also be frame-served correctly.

[had-z]

Uninstall everything and reinstall using only the versions linked in the first post of this thread. Also, look through your system and see if you can find other programs that are interfering with the CODEC settings.

You can see if the CODECs are working by installing "Media Player Classic" (MPC). Then open the AVS with MPC. If it plays back correctly, the odds are very high that it will also be frame-served correctly.

Thanks!! seems like the problem with the dark knight is solved, in this moment a backup of Xmen is cooking :) to view if the problem with MPEG-2 still exist...

The only bug remaining is the related to black hawk down...
(The main movie don't appear in the stream list)

[1Bullet]

wierd bug in CURRENT VERSION 0.37.07 (March 29th, 2011)

I just tried to do movie only on 2 separate films both films are over 40 gb+ after ripping. After using BD Rebuilder, I end up with a film that is 8gb(should be 25gb) with full audio. The entire audio is there for length of film. the log shows everything completed.
The film plays fine for 27 minutes the uses the same frame (like a still) for the balance of the film using the entire audio. The entire film is 3 hours long(176 minutes).
This now the second time this has happened, with this version. First time I thought it was just a glich.
It is not consistantly doing it it appears it is only happening on large films over 2.5 hours. The last one was Waterworld directors cut.

[jdobbs]

wierd bug in CURRENT VERSION 0.37.07 (March 29th, 2011)

I just tried to do movie only on 2 separate films both films are over 40 gb+ after ripping. After using BD Rebuilder, I end up with a film that is 8gb(should be 25gb) with full audio. The entire audio is there for length of film. the log shows everything completed.
The film plays fine for 27 minutes the uses the same frame (like a still) for the balance of the film using the entire audio. The entire film is 3 hours long(176 minutes).
This now the second time this has happened, with this version. First time I thought it was just a glich.
It is not consistantly doing it it appears it is only happening on large films over 2.5 hours. The last one was Waterworld directors cut. I hate to say it again... but are you overclocked? It sounds like X264 is crashing mid-encode.

You may want to try stepping back a version of X264 (look in one of the previous zip files for BD-RB) and see if that has an impact. But if you are overclocked, I'd suggest you back the cpu clock down a bit as that's more likely the issue. The time factor makes CPU heat a likely problem...

As I said a few posts back, X264 is the ultimate test for system stability.

[Capsbackup]

wierd bug in CURRENT VERSION 0.37.07 (March 29th, 2011)

I just tried to do movie only on 2 separate films both films are over 40 gb+ after ripping. After using BD Rebuilder, I end up with a film that is 8gb(should be 25gb) with full audio. The entire audio is there for length of film. the log shows everything completed.
The film plays fine for 27 minutes the uses the same frame (like a still) for the balance of the film using the entire audio. The entire film is 3 hours long(176 minutes).
This now the second time this has happened, with this version. First time I thought it was just a glich.
It is not consistantly doing it it appears it is only happening on large films over 2.5 hours. The last one was Waterworld directors cut.

Sounds like your PC has become unstable! Have you cleaned out the dust on the cpu fan, power supply, etc... to make sure it's not over heating? Or faulty power supply, memory, cpu, fan, etc.. among other potential issues could be present. :(

edit: looks like jdobbs is on top of this one too! :p

[jdobbs]

Just a note for those folks who do a lot of resizing to 720p.

I've been looking through the SUP file format and doing some work in resizing (to support subtitle conversion when outputting to DVD and fix the "forced flag" issue). In doing so I've just happened to have stumbled across the cause of the TSMUXER error that causes occasional failures when resizing to 720p.

The Object_Definition_Segment that includes all the information for actually drawing the subtitle image (stored as run-length encoded data) normally consists of only a single sequence (the graphic image of the text). Good enough, as the graphics for text is fairly small in most circumstances. But the Object_Definition_Segment has a mechanism for handling multiple sequences of graphic data (so large bitmaps can be divided into multiple parts each less than 64K long). It appears TSMUXER doesn't have the capability to handle those multiple sequences and dies when it encounters them (with the error "Unexpected byte").

The good news is that since these sequences are generally used in graphic overlays that aren't related to subtitles -- I can make BD Rebuilder ignore them completely when doing a movie-only encode. For full backups, however, the graphics are needed (usually to handle some type of special feature like pop-up selections etc.) I'm going to have to come up with some other way of resizing them.

Just thought it was interesting and wanted to let you know...

[1Bullet]

I hate to say it again... but are you overclocked? It sounds like X264 is crashing mid-encode.


No I am not overclocked
I will try stepping back a version of X264.

I have a power supply tester will check it out. I have been stable up till now.

[jdobbs]

No I am not overclocked
I will try stepping back a version of X264.

I have a power supply tester will check it out. I have been stable up till now. Find and run a utility that checks CPU temperature and look at it a couple of hours into the encode. Overclocking is the most common cause of overheating, but not the only one. You might look at your CPU's heatsink for dust buildup.

System issues are much more likely to be the problem than X264. Lots of other people are running the latest versions of BD-RB and X264 without issues.

I start hearing these kinds of reports every year when spring/summer comes around (most from overclocked systems). You'll see another one a little way back in this thread (but he refused to consider that his system might be at fault). Normally when X264 encounters an error, BD-RB will catch it by examining the O/S's returned error code. But when it is related to system instability it is unlikely that an error code will be returned. When that happens, all you end up with is a partial video encode that gets multiplexed into the output stream.

[Sharc]

Just a note for those folks who do a lot of resizing to 720p.

I've been looking through the SUP file format and doing some work in resizing (to support subtitle conversion when outputting to DVD and fix the "forced flag" issue). In doing so I've just happened to have stumbled across the cause of the TSMUXER error that causes occasional failures when resizing to 720p. ............

........... I'm going to have to come up with some other way of resizing them.

Just thought it was interesting and wanted to let you know...
That's really exciting news. Would be great to have a solution for the (seldom, but annoying) 720p sups failure of TSMUXER, plus sub support for DVD output :)

[jdobbs]

That's really exciting news. Would be great to have a solution for the (seldom, but annoying) 720p sups failure of TSMUXER, plus sub support for DVD output :)Hey, I just sent you a PM about that one... :) Not too long ago I was convinced it was a ripping issue.

[jdobbs]

That's really exciting news. Would be great to have a solution for the (seldom, but annoying) 720p sups failure of TSMUXER, plus sub support for DVD output :) I have the DVD resizing working and it will be in the next release. There are some limits, though, when converting from a format that allows 256 colors to one that uses 4. But based on my testing it is still pretty good.

[Discoboy]

Just a note for those folks who do a lot of resizing to 720p.

I've been looking through the SUP file format and doing some work in resizing (to support subtitle conversion when outputting to DVD and fix the "forced flag" issue). In doing so I've just happened to have stumbled across the cause of the TSMUXER error that causes occasional failures when resizing to 720p.

The Object_Definition_Segment that includes all the information for actually drawing the subtitle image (stored as run-length encoded data) normally consists of only a single sequence (the graphic image of the text). Good enough, as the graphics for text is fairly small in most circumstances. But the Object_Definition_Segment has a mechanism for handling multiple sequences of graphic data (so large bitmaps can be divided into multiple parts each less than 64K long). It appears TSMUXER doesn't have the capability to handle those multiple sequences and dies when it encounters them (with the error "Unexpected byte").

The good news is that since these sequences are generally used in graphic overlays that aren't related to subtitles -- I can make BD Rebuilder ignore them completely when doing a movie-only encode. For full backups, however, the graphics are needed (usually to handle some type of special feature like pop-up selections etc.) I'm going to have to come up with some other way of resizing them.

Just thought it was interesting and wanted to let you know...

Thanks for the update jdobbs :thanks:

[had-z]

All my problems was solved with clearing the register of the ffdshow!! now i can backup without the fear of bad frames or macroblocks...

If i can help to solve the problem with black hawk down uploading a file (clpi or mpls) i will be even more happy! I'm very curious to see how will look a MPEG2-source encoded with the superior x264. (BHD is the only BD i have with the main movie encoded in MPEG-2)

Thanks Again Jdobbs.

[setarip_old]

@jdobbsI've just happened to have stumbled across the cause of the TSMUXER error that causes occasional failures when resizing to 720p. Be careful - The last time you did that you fell off your roof ;>}

[wolverine3n8]

Just a note for those folks who do a lot of resizing to 720p.

The good news is that since these sequences are generally used in graphic overlays that aren't related to subtitles -- I can make BD Rebuilder ignore them completely when doing a movie-only encode.

That's good news. I do resizing quite often and have noticed the "english subs for non-english parts" didn't show up in the rebuilt version. This will be a great improvement to an already excellent program. Thanks.

[jdobbs]

@jdobbs Be careful - The last time you did that you fell off your roof ;>} Hah! Good point. I haven't had the best luck with the "stumbling" lately. In fact I'm still on crutches. :D