BD Rebuilder Beta - Bug Reports Only

[ChldsPlay]

@Childsplay

That routine is executed on every full backup made. This is the only report ever received of this type. Since the code is executed so often on so many systems, I have to believe the issue is local to your machine. That makes me think one of two things.

1. If the source is pointing to a local drive onto which you've ripped the disc, your drive is having issues with circular references. You may want to do a CHKDSK to find any issues. If this is a network or externally connected drive, it could also be a driver issue.

2. If you are reading directly from a disc it could either be a driver issue, or it could be a new type of copy protection that isn't being addressed by the ripping software.

I'll order the discs and see if I can repeat the issue in the case of #2.

I created a new target folder with a different name and it worked fine. I had noticed that when I selected my target folder previously, it wasn't displaying the full address (i.e. A:\The Big Bang Theory Season 2\backup was only showing up as A:\The Big Bang Theory Season 2).

[jdobbs]

I created a new target folder with a different name and it worked fine. I had noticed that when I selected my target folder previously, it wasn't displaying the full address (i.e. A:\The Big Bang Theory Season 2\backup was only showing up as A:\The Big Bang Theory Season 2)Interesting.

[Audiophile1178]

Jdobbs, do you have an answer to this question?

http://forum.doom9.org/showthread.php?p=1669758#post1669758

Just using BDRebuilder as is on 2-pass encoding without any modifications to it doesn't work. I also added those two config lines in the previous question without any luck.

FWIW, here's some info that might be tripping it up:

1. 104 playlists
2. 174 m2ts files

I don't know why when I set BD Rebuilder to DVD9 it sees most of the files but still not all. When I Set it to BD25 it ignores A LOT of m2ts files.


Maybe there's too many m2ts files for BD Rebuilder to handle?

[jdobbs]

Jdobbs, do you have an answer to this question?

http://forum.doom9.org/showthread.php?p=1669758#post1669758

Just using BDRebuilder as is on 2-pass encoding without any modifications to it doesn't work. I also added those two config lines in the previous question without any luck.

FWIW, here's some info that might be tripping it up:

1. 104 playlists
2. 174 m2ts files

I don't know why when I set BD Rebuilder to DVD9 it sees most of the files but still not all. When I Set it to BD25 it ignores A LOT of m2ts files.


Maybe there's too many m2ts files for BD Rebuilder to handle?If you set it to BD-9 and it ignores files, it is probably because they are unreferenced. Some discs have "filler" material added to make them larger than BD-25. BD-RB ignores anything that isn't referenced.

I'll go back and look a BD-25 -- there was some reasoning there, but it escapes me right now.

[Yordan5]

This was happening to me a month or so ago so I reinstalled BDR and it worked fine until now. I reinstalled it again with v.0.46.13 beta but still get this message about txmuxer not working. Can you tell me why this happens and what is the solution? This has happened several times. Thank you.

There is not an easy answer to this as anything could be causing this to happen. Do a system restore to the point where tsMuxeR was working fine and check what changes or installations you did before the problem started. This does not appear to be a BD-RB bug so you may not get many replies in this thread.

[jdobbs]

This was happening to me a month or so ago so I reinstalled BDR and it worked fine until now. I reinstalled it again with v.0.46.13 beta but still get this message about txmuxer not working. Can you tell me why this happens and what is the solution? This has happened several times. Thank you.There are a couple posts further back in this thread where DoctorM was having issues with the new TSMUXER. If I recall correctly it was because he had an exceptionally old processor that didn't support SSE2. Any chance that may be your issue?

[jdobbs]

If you set it to BD-9 and it ignores files, it is probably because they are unreferenced. Some discs have "filler" material added to make them larger than BD-25. BD-RB ignores anything that isn't referenced.

I'll go back and look a BD-25 -- there was some reasoning there, but it escapes me right now.I looked at it. The M2TS files that aren't included when MIN_M2TS_SIZE=0 are the ones that have no video, contain IGS (with IGS_ENABLE set off), BD-RB has determined to be menus, or BD-RB has determined to be made up of still images (and AUTO_BLANK is off).

[DoctorM]

Does BD Rebuilder not allow mpeg2 on AVCHD BD5/9 discs?
I added on a trailer (from a DVD) to my recent encoding, and although it is below the MIN_M2TS_SIZE value, it still forced a re-encoding.

That's a bit of a problem because I had added AVS filters for the movie, but I don't want those filters applied to the extras.

[jdobbs]

Does BD Rebuilder not allow mpeg2 on AVCHD BD5/9 discs?
I added on a trailer (from a DVD) to my recent encoding, and although it is below the MIN_M2TS_SIZE value, it still forced a re-encoding.

That's a bit of a problem because I had added AVS filters for the movie, but I don't want those filters applied to the extras.It's not a matter of BD-RB allowing it. The AVCHD standard doesn't allow it.

[Acerjen]

I am having difficulties getting SBS MKVs to properly convert to MVC 3D ISOs. The conversion completes successfully. On playback, the picture is somewhat blocky and does not play smooth. It is difficult to describe what is happening so I have provided a sample at the following link:

https://www.dropbox.com/s/zznnngx2r0ygfhb/FIRE_ANTS_-_THE_INVINCIBLE_ARMY_%283D%29_%28SAMPLE%29.ISO

If someone would be willing to download this file and try to play it on their system and tell me if they have any trouble, I would greatly appreciate your time. Here is a link to the original sample file I used from my Blu-ray disc.

https://www.dropbox.com/s/oa3hig5gl4mxlyr/Fire%20Ants%20-%20The%20Invincible%20Army%20%283D%29%20%28sample%29.mkv

And also, the support files that jdobbs usually asks for.

https://www.dropbox.com/s/geimtdsqhdwd1xd/support%20files.zip

Thanks for your time. Later.

-acerjen

[Audiophile1178]

Some discs have "filler" material added to make them larger than BD-25. BD-RB ignores anything that isn't referenced.

While I do agree with you that the newer discs are using this sort of trickery both of the X-Files discs came out in 2008 and back then they didn't do that sort of thing.

Just to be sure that this isn't the case, I used Procmon in conjunction with PowerDVD and had the disc loaded in BD Rebuilder to compare everything. I can assure you that everything that I'm questioning is referenced in the disc menu. My findings were that most of the material that BD Rebuilder doesn't see is contained in bonus material titled:

"The X-Files Complete Timeline"
"Still Galleries"

The X-Files Complete Timeline is very interesting and goes into specific details about everything regarding the X-Files and breaks it down by year/seasons/movies etc... The user has the choice. This feature is very tricky to navigate and has TONS of SD video of at least 87 m2ts files that are at least 2.4 GB in size along with interesting facts and pictures. It's hard to track everything down as there's so much material.

The "X-Files: I Want To Believe" is one of the most difficult discs that I've come across because of all these features.


FWIW, I also can't do the first film "Fight The Future" for two reasons

1. tsMuxeR is throwing up errors on 00003.m2ts file. The same error as Matrix789 is having here:

http://forum.doom9.org/showthread.php?p=1670576#post1670576

which has nothing directly to do with BD Rebuilder.

2. BD Rebuilder has the same issue as the second film of not seeing all the m2ts files. BD Rebuilder is ignoring the same bonus part as in disc two "Still Galleries". In this case, it isn't as bad as those "Still Galleries" consist of three files (I believe) which isn't that bad as I could manually encode that so it's not as much of a concern but is still the same problem with BD Rebuilder.


I guess it's not too surprising that both X-Files movie are having issues with BD Rebuilder as they were both released on the same exact day and have the same format but just different bonus content.


If there's anything that I can further do to help assist you let me know.

P.S. If you wish I could send you the Blu-ray structure of both discs (everything but the stream folder as including that folder would be too much to upload) to possibly help you analyze the disc. I could also tell you which playlists BD Rebuilder ignores.

[mparade]

There are a couple of changes I need to make for that mode anyway. There is still some dangling information remaining that indicates 3D after the backup.

Could you make these changes for the next release? Anyway, were you succeeded in processing Avatar 3D as 2D for full disc backup? I would be much concerned about that.

Thank you in advance!

[DoctorM]

It's not a matter of BD-RB allowing it. The AVCHD standard doesn't allow it.

I suspected. So I stopped the job, removed the filters, used 'Import Videofiles' and pointed it to the newly re-encoded M2TS of the film and the mpeg2 trailer file.

I figured it would build a psuedo BD and let me continue from there with BDRB copying the movie and re-encoding the trailer (now without the filter).

It isn't doing that. It STILL wants to re-encode the movie: SOURCE_SIZE=4314329992
SOURCE_VIDEO_SIZE=4314329088
TARGET_SIZE=4686086144
REDUCTION=1.0861677782147
[02/28/14] BD Rebuilder v0.46.13 (beta)
[15:18:21] Source: WORKFILES
- Input BD size: 4.02 GB
- Approximate total content: [01:38:53.552]
- Target BD size: 4.36 GB
- Windows Version: 5.1 [2600]
- Quick-Play Reauthoring mode enabled
- Quality: Highest (Very Slow), CRF
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[15:18:22] PHASE ONE, Encoding
- [15:18:22] Processing: VID_00001 (1 of 1)
- [15:18:22] Extracting A/V streams [VID_00001]
- [15:22:08] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1280x720
- Rate/Length: 23.976fps, 142,263 frames
- [15:22:08] Performing CRF Prediction...
- Analyzing 11.00 [11.00]

Apparently for BD5/9 discs there is no recognition if the video source is already compliant with AVCHD standard.

Also, I don't know if I'm alone on this, but I would think the AVS filter shouldn't (by default anyway) be applied to bonus features. Extras frequently aren't similar to the feature film and don't need the same treatment.

Finally, I now need some advice on how to rebuild what I've got. I have the film re-encoded in M2TS ready for BD5, but the trailer is still non-compliant mpeg-2. I have no idea how to rebuild this now.

Edit: Added FORCE_NOENCODE=1. It still want to encode that thing.
Edit 2: Okay, I've got a problem somewhere. Set BDRB with a BD-25 target and it still wants to re-encode. I'm lost.

[jdobbs]

Could you make these changes for the next release? Anyway, were you succeeded in processing Avatar 3D as 2D for full disc backup? I would be much concerned about that.

Thank you in advance!When I tried to back it up to 2D I had the same issue you had. There's a bug in which some of the playlists are kept 3D and some are not, and it causees a lot of confusion. I'll see what I can do for the next release, but it looks like it's not going to be a simple matter.

[jdobbs]

@Audiophile1178

Did you read this post (http://forum.doom9.org/showthread.php?p=1671090#post1671090)?

[mparade]

When I tried to back it up to 2D I had the same issue you had. There's a bug in which some of the playlists are kept 3D and some are not, and it causees a lot of confusion. I'll see what I can do for the next release, but it looks like it's not going to be a simple matter.

Thank you for your time. Truly appreciated your efforts!

[Audiophile1178]

@Audiophile1178

Did you read this post (http://forum.doom9.org/showthread.php?p=1671090#post1671090)?

Yes, I did as I quoted from it. I was responding to that post stating that I looked into both discs and the files that BD Rebuilder doesn't see do get referenced by the disc and I listed what those files contain, as well as, what accessed those files in the disc menu.

I know that you said that you're going to look into it. I just wanted to convey my findings and possibly help you out by providing the Blu-ray structure.

As I said before, "I Want To Believe" is one of the craziest discs that I've seen and would think that it would be a good test disc for you to use.


As it stands, I was simply stating that I'm currently unable to backup either of the X-Files movies because of these various issues.

[Sharc]

Does BD Rebuilder not allow mpeg2 on AVCHD BD5/9 discs?
I added on a trailer (from a DVD) to my recent encoding, and although it is below the MIN_M2TS_SIZE value, it still forced a re-encoding.

That's a bit of a problem because I had added AVS filters for the movie, but I don't want those filters applied to the extras.
Just in case you didn't know: You can control the application of the .avs scripts by using a prefix like f:, e: etc. It's documented in the changes.txt

[jdobbs]

Back by popular demand. From a previous post:

All settings that don't use the "a:" are assumed to be video. Some other prefixes:

i: means apply only to interlaced sources
p: means apply only to progressive sources
f: means apply only to the feature
e: means apply only to extras

The default of no prefix at all means apply it to all sources

They can be used together, for example:

f:a:Amplify(audio,1.25)

would mean to increase audio by 25% for the feature only.

[Sharc]

.......
Edit: Added FORCE_NOENCODE=1. It still want to encode that thing.
Edit 2: Okay, I've got a problem somewhere. Set BDRB with a BD-25 target and it still wants to re-encode. I'm lost.
I experienced and reported a similar problem some days ago. I found that the unwanted re-encoding was probably triggered by the selected resize option. Try to unselect the options (you don't need these for pure re-authoring), and your source should remain intact.

[DoctorM]

Back by popular demand. From a previous post:

All settings that don't use the "a:" are assumed to be video. Some other prefixes:

i: means apply only to interlaced sources
p: means apply only to progressive sources
f: means apply only to the feature
e: means apply only to extras

The default of no prefix at all means apply it to all sources

They can be used together, for example:

f:a:Amplify(audio,1.25)

would mean to increase audio by 25% for the feature only.

I didn't even know that was there. Thanks.

I experienced and reported a similar problem some days ago. I found that the unwanted re-encoding was probably triggered by the selected resize option. Try to unselect the options (you don't need these for pure re-authoring), and your source should remain intact.

Good thought, but no. I just cannot under any condition make BDRB leave a source alone for rebuilding. No matter the format or size, the target, the options, or anything else.

To rule out as much as possible I went back to v44.17 and I still find this behavior. I've been running test after test today under various conditions.

Am I misunderstanding? Does BDRB NEVER copy a source untouched even if there is more than enough room for it?

[DoctorM]

One more test. I figured I'd try a BD Quick Reauthor on the Pseudo BD. Unfortunately, the threshold is 15 minutes and I can find no hidden option for lowering that. Does it exist?

Sorry to be so needy, but this has been more difficult than anticipated.

[A.Fenderson]

Yes, I did as I quoted from it.

I'm guessing jdobbs meant to reference his most recent reply to you (http://forum.doom9.org/showthread.php?p=1671121#post1671121)instead of a previous one.

[jdobbs]

@DoctorM

BD-RB has to reencode anything that is destined for a BD-5/9. That's because a source that was created for BD has bitrates that CANNOT be played on a DVD+-R -- it can't spin fast enough. It doesn't check a BD source to determine whether it was previously encoded. As one might expect, it assumes that a BD source is a BD source.

[DoctorM]

I can understand the BD5/9 always reencoding, but even taking from a pseudo BD to a BD25 target, BDRB insists on a re-encode too.

So basically it appears if the format isn't a true BD to start with, BDRB will always encode.
Can a psuedo BD be used as a real BD(5) if the video files are properly encoded or are there other authoring differences?

[Sharc]

@jdobbs
BD-5/9 target selection then overrules the hidden option FORCE_NOENCODE=1?
I am asking because I imported compliant files (already processed before by BD-RB) on purpose for fixing the Quick-Menu. BD-RB insists on re-encoding despite FORCE_NOENCODE=1 unless I deselect all resizing tick boxes.
(Possibly a similar case as DoctorM reports)

[Capsbackup]

Perhaps an option to Re-Author without reencoding check box could be used for BD5-9/AVCHD? A warning message could say "may not be compatible with AVCHD, use at your own risk!"
I often do use multiAVCHD for this, but this would be an excellent alternative.
Not sure this is an option you would want to add jdobbs, since you know the potential problems that will happen, and people will assume it is the fault of BD-RB! :(

[jdobbs]

FORCE_NOENCODE=1 should keep the original either way as long as it is physically possible to follow it and still meet your other settings. But it has to reencode if you are resizing. You can't give it contradicting instructions and expect BD-RB to know which of those you really mean. It can also be overridden by FORCE_ENCODE.

The same applies if you are processing SBS into 3D or if you have filters set. It can't do that and not encode at the same time.

Trying to do two things at the same time that contradict each other is an operator error... not a bug. It's kinda' like stepping on the accelerator and the brake at the same time. Would you tell the manufacturer that they have a bug and one of the two should be ignored?

With that said... if you select FORCE_NOENCODE and there is no other contradicting setting, it should not reencode. I'll look at what happens with BD-5/9 and change it if necessary.

[mparade]

- [11:28:56] Processing: VID_00066 (55 of 102)
- [11:28:56] Extracting A/V streams [VID_00066]
- Error in attempt to MKVMERGE.
[11:29:36] - Failed to retrieve audio, aborted

Cannot get through this problem. The videos source is AVC and part of the main movie. (MPEG-4 (AVC), 1920x1080
Rate/Length: 23,976fps).

Please help. At the moment this is the only 2D BD I own which cannot be processed by BD-RB due to some reason.

Thank you!

[jdobbs]

The videos source is AVC and part of the main movie. What does this mean? If it is building to MKV the main movie is all there is -- and what do you mean by "part of" it?

[Edit] Ok, I see by looking at your log that you aren't encoding to MKV. MKVMERGE is necessary when processing secondary video or VC-1 interlaced sources (because they can't be demuxed/encoded properly from an M2TS).

[mparade]

What does this mean? If it is building to MKV the main movie is all there is -- and what do you mean by "part of" it?

Sorry for not being clear enough.

If I switch to "movie-only backup" mode to check the main movie content, it is shown that the main video contains several VIDs (22 pcs from VID_00050 to VID_00072) including the one I have problem with (VID_00066).
I meant only that VID_00066 is part of the main movie video content.

[jdobbs]

Sorry for not being clear enough.

If I switch to "movie-only backup" mode to check the main movie content, it is shown that the main video contains several VIDs (22 pcs from VID_00050 to VID_00072) including the one I have problem with (VID_00066).
I meant only that VID_00066 is part of the main movie video content. Is it the last part? It may be possible that BD-RB is attempting to extract the secondary video for reencoding... but for some reason it isn't there. By the standard -- it must be there. I've see a couple of other cases where the final segment of a multipart video violates requirements.

[Sharc]

FORCE_NOENCODE=1 should keep the original either way as long as it is physically possible to follow it and still meet your other settings. But it has to reencode if you are resizing. You can't give it contradicting instructions and expect BD-RB to know which of those you really mean. It can also be overridden by FORCE_ENCODE.

The same applies if you are processing SBS into 3D or if you have filters set. It can't do that and not encode at the same time.

Trying to do two things at the same time that contradict each other is an operator error... not a bug. It's kinda' like stepping on the accelerator and the brake at the same time. Would you tell the manufacturer that they have a bug and one of the two should be ignored?

With that said... if you select FORCE_NOENCODE and there is no other contradicting setting, it should not reencode. I'll look at what happens with BD-5/9 and change it if necessary.
Thank you for the clarification. Yes, I am well aware of the possibility of conflicting settings. The question is then always which is given priority. I assumed that FORCE_NOENCODE=1 would overrule everything in case of conflicts (as the "force" sounds very strong), but apparently I was wrong. Now it's clear that I have to reset/deselect other possibly conflicting settings when I want to avoid re-encoding.

[mparade]

Is it the last part? It may be possible that BD-RB is attempting to extract the secondary video for reencoding... but for some reason it isn't there. By the standard -- it must be there. I've see a couple of other cases where the final segment of a multipart video violates requirements.

No, this segment is from one of the biggests and located in the middle of the main movie. And you are right, the disc contains secondary video in each referenced main movie segment according to the stream view. I think this BD is a "tricky" one:

I have found that after selecting Movie-Only Backup Mode, "Other Movie-Only Playlists" contains 7 pcs of playlists. What is strange for me is that this problematic main video segment (VID_00066) has it's own playlist (Playlist 00066) in which it is located alone. The same situation with an other big main video segment as well (VID_00068). Maybe, this could cause some problem for BD-RB also.

[mparade]

Is it the last part? It may be possible that BD-RB is attempting to extract the secondary video for reencoding... but for some reason it isn't there. By the standard -- it must be there. I've see a couple of other cases where the final segment of a multipart video violates requirements.

Would it be possible to get around this problem by creating a hidden option like FORCE_SECONDARY_NOENCODE?
It would be great if you assigned a reason to it also. :o

[jdobbs]

Would it be possible to get around this problem by creating a hidden option like FORCE_SECONDARY_NOENCODE?
It would be great if you assigned a reason to it also. :oPossibly. But there are risks related to that. What if the bitrate of the secondary pushes you over the limit for BD-5/9? What if it uses an inordinate amount of space that is stolen from your primary video?

Have you tried switching to DirectshowSource() rather than LAVF?

[ricoman]

There are a couple posts further back in this thread where DoctorM was having issues with the new TSMUXER. If I recall correctly it was because he had an exceptionally old processor that didn't support SSE2. Any chance that may be your issue?
No, it's a 2 yr. old i7 so I don't think it's the processor. I was able to use DVDFabHD, but I generally like BDRebuilder better. It takes longer but the output seems crisper. This has happened to me 3 different times in the past yr. Usually reinstalling BDRB fixes it, not this time though. The only thing I can think of is that I seem to periodically have to reinstall Adobe Flash Player due to crashing issues (a lot of people have that problem). Do you think that could be affecting it? It's the only common clue I can think of because other than updating AnyDVDHD and DVDFabHD, I don't download much.

[jdobbs]

No, it's a 2 yr. old i7 so I don't think it's the processor. I was able to use DVDFabHD, but I generally like BDRebuilder better. It takes longer but the output seems crisper. This has happened to me 3 different times in the past yr. Usually reinstalling BDRB fixes it, not this time though. The only thing I can think of is that I seem to periodically have to reinstall Adobe Flash Player due to crashing issues (a lot of people have that problem). Do you think that could be affecting it? It's the only common clue I can think of because other than updating AnyDVDHD and DVDFabHD, I don't download much.I can't imagine how Adobe Flash could affect TSMUXER. But stanger things have happened I suppose.

Have you tried running TSMUXER from the command line using the META file BD-RB creates, and seeing if there is some indication of what might be happening before the crash?

[mparade]

Possibly. But there are risks related to that. What if the bitrate of the secondary pushes you over the limit for BD-5/9? What if it uses an inordinate amount of space that is stolen from your primary video?

Have you tried switching to DirectshowSource() rather than LAVF?

For my backup projects it is not a problem at all neither pushing over the limit for BD-5/BD-9 nor if it uses an inordinate amount of space that is stolen from primary video. The reason for that is that I always use FIXED_CRF option for the different video content types of the backups with unpredictable final sizes. Additionally, I always keep the HD audio tracks if available on the disk. I have found this method of processing quite effective and it results in very small backup sizes most of time.

With DirectshowSource I experienced the same problem, attached the log file. (The only difference in setup between the two encodings was unmarking "use X264's internal LAVF for decoding" in the setup dialog).

I really appreciate your efforts and time spent on this issue.

[Peter_A]

Hello, this is my first post.

I have been using BD Rebuilder for awhile now, and I seem to be having an issue that just started with the past couple of versions that I've used (I'm not sure if these correspond to the last 2 releases, as I may not have installed each release that was made). Now, the video will always be re-encoded, even when it will fit on the target (BD25). This used to work fine for me (prior to the past 2 versions that I've used). I've done several movies where converting the LPCM or DTS HD-Master to AC3 allowed the size to be small enough for the video to not be re-encoded. Now, this is not occurring. In fact, I have a movie now that I just tried. It's "The Artist" and it's 22.9 GB with the DTS HD-Master audio track. It's just barely above the BD25 threshold, and clearly by converting the DTS HD-Master to AC3, it would be below the BD25 threshold, but BD Rebuilder is still is trying to re-encode the video. Another example, I had A Clockwork Orange, with a few audio tracks (1 LPCM, and 2 AC3, I believe). I selected just 1 AC3 track (which ended up bringing the final size to well under 20 GB, but it still tried to re-encode the video. If I change the target size to BD50, it works (no re-encode), so I don't think that any of my other settings are forcing it to re-encode or anything in the video itself (interlaced, etc.). Did something change with the size calculations? Again, this just started happening with the past 2 versions that I've used (prior versions seemed to be OK). Any thoughts? Here are my settings and log(s).

---------
SETTINGS
---------
[Options]
VERSION=0.46.0.13
MODE=0
ENCODE_QUALITY=3
ONEPASS_ENCODING=0
AUTO_QUALITY=0
TARGET_SIZE=23500
AUTO_BURN=2
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=all
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=1
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=0
KEEP_HD_LPCM=0
AVCHD=1
REMOVE_WORKFILES=0
MOVIE_ONLY_LOOP=1
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
UNMASK_CHAPTER=0
COMPLETION_BEEP=0
DGDECNV=0
OUTPUT_3D=0
NEROAAC=0
SUPTITLE=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23500
IGNORE_3D=0
OUTPUT_SBS=0
[Paths]
SOURCE_PATH=H:\
WORKING_PATH=D:\TEMP\BD-RB\

---------------------------
LOG (with BD25 target size)
---------------------------
[03/02/14] BD Rebuilder v0.46.13 (beta)
[11:22:31] Source: THE_ARTIST
- Input BD size: 22.99 GB
- Approximate total content: [01:40:36.071]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[11:22:32] PHASE ONE, Encoding
- [11:22:32] Processing: VID_00015 (1 of 1)
- [11:22:32] Extracting A/V streams [VID_00015]
- [11:35:53] Reencoding video [VID_00015]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 144,721 frames
- Bitrate: 29,643 Kbs
- [11:35:53] Reencoding: VID_00015, Pass 1 of 2
[11:37:28]PHASE ONE aborted by user request

---------------------------
LOG (with BD50 target size)
---------------------------
[03/02/14] BD Rebuilder v0.46.13 (beta)
[11:38:57] Source: THE_ARTIST
- Input BD size: 22.99 GB
- Approximate total content: [01:40:36.071]
- Target BD size: 46.26 GB
- Windows Version: 6.1 [7601]
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[11:38:58] PHASE ONE, Encoding
- [11:38:58] Processing: VID_00015 (1 of 1)
- [11:38:58] Extracting A/V streams [VID_00015]
- [11:52:05] Reencoding video [VID_00015]
- [11:52:05] Keeping original video (no reencode)
- [11:52:05] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...

Thanks for any help. Sorry for the long post.
-Peter

[ricoman]

I can't imagine how Adobe Flash could affect TSMUXER. But stanger things have happened I suppose.

Have you tried running TSMUXER from the command line using the META file BD-RB creates, and seeing if there is some indication of what might be happening before the crash?

not sure how to do that. When I click on TSmuxer app it whizzes by so fast and disappears.

edit: Managed to stop the window, but it's Greek to me. I'm just a simple user and am a bit out of my depth when it comes to command line stuff. Didn't see anything in the window that indicated a problem.

[veggav]

I'll honk this horn once again.

Is there any plans to add srt subtitle support on BDMV folder structure?

I'm talking about adding a subtitle stream to a BD and leaving everything else intact.

Since TsMuxer does the job of converting it to sup structure BD-RE would just need to add the stream and replace mpls and clpi new files after insertion.

This is so simple compared to all the math this software does for re-encoding that I'm really surprised this feature wasn't added yet.

[Ch3vr0n]

simple in thought maybe yes, implementation i doubt it.

[AmigaFuture]

I'll honk this horn once again.

Is there any plans to add srt subtitle support on BDMV folder structure?

I'm talking about adding a subtitle stream to a BD and leaving everything else intact.

Since TsMuxer does the job of converting it to sup structure BD-RE would just need to add the stream and replace mpls and clpi new files after insertion.

This is so simple compared to all the math this software does for re-encoding that I'm really surprised this feature wasn't added yet.

From a Users view, a programmers job can seem less complex often. Because 1 programmer finds a way or is inspired, doesn't mean another programmer will come across the same....the same.

@jdobbs

Thanks a LOT for keeping FORCE_NOENCODE while creating the Target Size BD-50 option. I don't always check the Jar directory for unneeded files. I'm sure someone else will appreciate it for "Oh, Doh!" moments as I have. :D

[rusty666]

can anybody help i done a 3d sbs avchd bd9 from iso 3d but once i put it on disk it will noy play on power dvd or 2 blu ray players i have tried?

[jdobbs]

can anybody help i done a 3d sbs avchd bd9 from iso 3d but once i put it on disk it will noy play on power dvd or 2 blu ray players i have tried?BD players don't typically convert SBS. It will still show as two pictures. It is normally the monitor that does that via a 3D selection.

[rusty666]

i mean it will not play at all

[rusty666]

i had to use avchd patcher 106 worked first time on player after that . thanx for your hard work

[jdobbs]

What version of BD-RB did you use? There was an AVCHD fix in v0.46.13.

[rusty666]

yes im useing the latest you have