BD Rebuilder Beta - Bug Reports Only

[Ch3vr0n]

That's setting has no effect on full backup. As it said: 'movie-only output' and all that does is converting normal 3d to side-by-side. Post your settings INI file so jdobbs can take a look. And a conversion log for both outputs. You have to be doing something wrong

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[jdobbs]

1. Full backup. In settings "Enable SBS 3d movie-only output" NOT enabled. Results in only 2d output.

2. Full backup. In settings "Enable SBS 3d movie-only output" enabled. Results in only 3d output.I'd need to see your log and INI. As Ch3vr0n said -- that setting should have effect on a full backup.

[musiclover]

I'd need to see your log and INI. As Ch3vr0n said -- that setting should have effect on a full backup.

Sorry guys. It was a false alarm and not a bug. After a clean install all works fine.

[AmigaFuture]

BD Player's Hard Drive? What kind of player has a hard drive? Or possibly it's a hard drive connected via USB? It sounds as if your player possibly couldn't handle the original bitrate/maxrate when it was packed within an MKV. But that's a stab in the dark. Weird.

The LG BD590 has an Internal 250GB HDD and a single USB 2.0 port. If it weren't able to handle the bitrate/maxrate then why do many other 1080p MKVs (made by BD-RB) play without need of rerendering? That's what I'm wondering.

I think your are mistaken, you should check your INI file (which wasn't posted). It appears you don't actually have OUTPUT_3D_ISO=1 set. If you did, you would see "Creating MOVIE-ONLY BD-3D ISO..." in your log rather than "Rebuilding BD-3D file Structure"

Mmm..seem like you might need another vacation, JD. :) ;)

[Yordan5]

jdobbs, any chance you take another look at 3D subtitle effect when processing MVC 3D titles? If I remux a movie using TSmuxeR only, the remuxed image still plays with 3D subs but once the movie is processed with BD-RB the subs lose the 3D effect.

[jdobbs]

jdobbs, any chance you take another look at 3D subtitle effect when processing MVC 3D titles? If I remux a movie using TSmuxeR only, the remuxed image still plays with 3D subs but once the movie is processed with BD-RB the subs lose the 3D effect.Yeah, I'll at look finding a way to do it. But it isn't as easy as you might think. The reason you are keeping them when using only TSMUXER is because the 3D effect is a part of the original video stream. It goes away when you reencode. If I use that same (most common) method I would have to modify the video stream itself -- which takes additional time in processing.

[gonca]

$50 on the way to help with your efforts.

[jdobbs]

Wow. Thanks!

[gonca]

I guess donations are really slow in coming in,sadly, if I get a Wow for a small donation.

[jdobbs]

Slow is an understatement. It isn't unusual these days to go a week between donations -- and they are typically much smaller than yours. I truly appreciate those like yourself who keep it going.

Actually I think someone else donated today as well, so I may just run down tomorrow and look at new releases to test.

But... like I've said before -- if I were in it for the money I'd be mowing lawns instead.

[Yordan5]

Slow is an understatement. It isn't unusual these days to go a week between donations...

I'll send another $30 your way today. Hopefully you'll get a chance to have a look at the 3D subs one day. Thank you for developing BD-RB.

[jdobbs]

I'll send another $30 your way today. Hopefully you'll get a chance to have a look at the 3D subs one day. Thank you for developing BD-RB.Thank you very much. I'm looking at the spec to see what would be the best way to do it.

[Acerjen]

Thank you very much. I'm looking at the spec to see what would be the best way to do it.

Jdobbs,
I was just reading up on the other free 3D MVC encoder called MVCenc at the following thread:

http://forum.doom9.org/showthread.php?t=170315&page=4

It was recently updated to "preserve 3D depth information". Something about a "nesting SEI message"? Maybe FRIM Encoder will do the same kind of thing concerning 3D subtitle depth? Maybe this thread can help point you in the right direction concerning the 3D subtitle depth, assuming your not already there. If so, please ignore this message.

Thanks for a great program. Your support is second to none. Quite frankly, most software companies could follow your lead when it comes to support.

Have a nice day. Later.
Acerjen

[jdobbs]

I know FRIM can't do it yet -- but maybe in a later release. I'm aware of the way the information is maintained -- but I don't have any routines yet that scan through AVC streams, find the proper point, and insert them -- so I'd have to write it from scratch.

[HWK]

Jdobbs, where you able look into post I made, it basically talks about import function can't handle mp2 sound and PAL sources keyint set wrong.

http://forum.doom9.org/showthread.php?p=1713105#post1713105

[jdobbs]

I've fixed the problem with MPEG-1 Layer 1 & 2 audio import (MP1, MP2). In fixing it I also noticed that there were some issues importing MPEG-1 video and some older DIVX FOURCCs as well. They have also been fixed. I haven't looked at the keyint thing, but I'll have it fixed for the next release.

Was the keyint issue with a regular BD backup, ALTERNATE output, or both?

[HWK]

I've fixed the problem with MPEG-1 Layer 1 & 2 audio import (MP1, MP2). In fixing it I also noticed that there were some issues importing MPEG-1 video and some older DIVX FOURCCs as well. They have also been fixed. I haven't looked at the keyint thing, but I'll have it fixed for the next release.

Was the keyint issue with a regular BD backup, ALTERNATE output, or both?

Let me check for all options which affect it.

[jdobbs]

Let me check for all options which affect it.That's ok. I can check it. I was just asking in case you already knew.

[HWK]

That's ok. I can check it. I was just asking in case you already knew.

I already did and yes you are correct keyint is 48 for 50fps source for both.

[Lathe]

I guess donations are really slow in coming in,sadly, if I get a Wow for a small donation.

Heh, if you think YOURS is small, you should see MINE...

(Uh... donation, that is... :cool: )

[Lathe]

But... like I've said before -- if I were in it for the money I'd be mowing lawns instead.

Ah... but I bet the lawns would look frigg'n LOVELY! :D

[jdobbs]

Heh, if you think YOURS is small, you should see MINE...

(Uh... donation, that is... :cool: )Ok. This one got me laughing.

[SoniG]

Super Coder!

[Sharc]

I wanted to do a full backup in 1-pass fixed CRF mode (i.e. without CRF prediction, no size control). Therefore I put in the .ini:
FIXED_CRF=20
QUICK_CRF=22
FORCE_ENCODE=1

I assumed that FIXED_CRF=20 would discard any output size control. Now it seems that the output size control still kicks in, and one file got a "-Performing size correcting 2nd pass". Why?
I think the size correcting second pass should only kick in for "1-pass with CRF prediction" (i.e. without the FIXED_CRF=xx in the .ini), when the target size is exceeded.
Maybe I am missing something?

[jdobbs]

Hmmm... I guess I forgot about checking and adjusting for the FIXED_CRF setting when I added the size correction code. That's the problem with adding so many "special" settings -- sometimes you forget they are there. I'll fix it for the next release.

[Sharc]

Hmmm... I guess I forgot about checking and adjusting for the FIXED_CRF setting when I added the size correction code. That's the problem with adding so many "special" settings -- sometimes you forget they are there. I'll fix it for the next release.
Yes, in view of the long list of options and settings, regression testing after each change becomes a herculean task .....

Now I have a second issue:
In the same job as before, I selected to resize 1920x1080 to 1440x1080, which set RESIZE_1440=1 in the .ini, so it's there and the log says "-Resize: 1920 to 1440 enabled"
The feature (VC-1 format) is currently in progress but encodes with the original size of 1920x1080, and the resize command is missing in the script.

Could it be that my .ini is incorrectly read because I inserted some blank lines in order to structure the hidden options a bit? I am also putting a # in front of unwanted options in order to disable these. Maybe I should fully remove unwanted hidden options rather than just commenting them out? It seemed to have worked in the past, but now I have some doubts.

[jdobbs]

Yes, in view of the long list of options and settings, regression testing after each change becomes a herculean task .....

Now I have a second issue:
In the same job as before, I selected to resize 1920x1080 to 1440x1080, which set RESIZE_1440=1 in the .ini, so it's there and the log says "-Resize: 1920 to 1440 enabled"
The feature (VC-1 format) is currently in progress but encodes with the original size of 1920x1080, and the resize command is missing in the script.

Could it be that my .ini is incorrectly read because I inserted some blank lines in order to structure the hidden options a bit? I am also putting a # in front of unwanted options in order to disable these. Maybe I should fully remove unwanted hidden options rather than just commenting them out? It seemed to have worked in the past, but now I have some doubts.Blank lines are ignored, and so are those with # in front of them. The only thing you have to be careful of is bracketed values (like "[test]") because they begin a new section and anything after it will be ignored (most of the settings are in the "[Options]" area).

I don't think your INI is the problem -- as the indicator "-Resize: 1920 to 1440 enabled" means the value had been read properly. I'll do some testing.

[jdobbs]

I just tested a short title and it works correctly for me. Are you positive the source is 1920x1080? You should also see something similar to this in your log: - [11:00:28] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 4,427 frames
- Convert: 1440x1080, 23.976fps, 4,427 frames

[Sharc]

I just tested a short title and it works correctly for me. Are you positive the source is 1920x1080? You should also see something similar to this in your log: - [11:00:28] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 4,427 frames
- Convert: 1440x1080, 23.976fps, 4,427 frames
Yes, the source is 1920x1080. The log reports:
- [13:32:48] Reencoding video [VID_00002]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23.976fps, 187'987 frames
- [13:32:48] Encoding using constant rate factor.
- Performing size-correcting second pass...

Up to now the resize to 1440 has always worked. This time the "Strict AVCHD compliance" was selected (which I normally don't tick), if this should matter.....

[Edit:]
Now trying again with "Strict AVCHD compliance" deselected....

[Edit2:]
No joy. The resize command is just missing in the script even with "Strict AVCHD compliance" deselected.
Must be something else .......

[Edit3:]
It's a 2D source, but I have still selected "SBS" for 3D encodes. Could this possibly prevent the resizing to 1440?

[Edit4:]
Bingo! That was it. Deselecting "SBS" brought the resizing to 1440 back to life!

[Capsbackup]

[Edit4:]
Bingo! That was it. Deselecting "SBS" brought the resizing to 1440 back to life!
:goodpost:

Impressive find!
Powertester if I may say so Sharc. :cool:

[jdobbs]

Bingo! That was it. Deselecting "SBS" brought the resizing to 1440 back to life!Hmm... I'll take a look at that. It really shouldn't have any effect on a non-3D source.

[Edit] It was a simple logic error in a routine that sets the resizing options for each stream (it should have done an OR instead of an AND). I've fixed it for the next release.

[Sharc]

Hmm... I'll take a look at that. It really shouldn't have any effect on a non-3D source.

[Edit] It was a simple logic error in a routine that sets the resizing options for each stream (it should have done an OR instead of an AND). I've fixed it for the next release.
Glad you found it. Cool. Thanks!

[jdobbs]

I have updated the first post of this thread with a link to the latest version of BD-RB (v0.50.07). Changes for this release:- Corrected proper log reporting of selected
decoder type when a 2D movie-only playlist
is used on a disc containing 3D content.
- Corrected an issue in which original audio
may be kept for ALTERNATE backup -- even
though "*" (constant quality) is selected
as the audio bitrate.
- Corrected an incorrect representation of
audio encoding completion (%) status when
an ALTERNATE constant quality encode is in
the process of executing for the AC3 format.
- Corrected an issue in which encoding could
fail on imported SBS 3D video sources when
using LAV filters for decoding.
- Added two additional hidden options related
to menus. MENU_FONT_BOLD can boldface the
selected menu font, and MENU_FONT_ITALIC is
used to set the menu font to italics mode.
- Added a new option to the Import/Quick Play
Setup dialog that allows you to select an
AC3 audio file to use as background audio
for menus. This will be used when no DVD
or BD background audio is automatically
detected and selected.
- Modified file access routines to be more
robust when accessing network shares that
have no drive letter associated with it.
- Updated the X264 keyint variable to better
match frame rates.
- Updated video file import routine so that
several older DIVX FOURCC's, MPEG-1, and
MPEG-1/L2 & L1 audio are accepted for input.
- Fixed an error in which setting the switch
to output SBS (for 3D sources) was causing
resizing functions to be ignored for non-3D
activity.
- Updated the included version of X265.EXE to
a newer release (04/22/2015).
- Other minor corrections and cosmetic fixes.

[soneca]

Thanks for the new version! ;)

[Sharc]

Thank you for the new version. Did you fix the FIXED_CRF= issue to discard any sizing and not to kick in the size correcting 2nd pass?

[jdobbs]

Thank you for the new version. Did you fix the FIXED_CRF= issue to discard any sizing and not to kick in the size correcting 2nd pass?Yes. It's fixed.

[AmigaFuture]

"Fifty Shades of Grey" - Removed bug report because it's related to AnyDVD after changing some settings. I'll modify this after I know which. Haven't had much opportunity, yet.

[jdobbs]

It seems after doing a Windows 7 reinstall, I missed an AnyDVD setting. Testing some more. So far, all looks good and I'll delete the posts if all is once finished.Please let me know... also, if it fixes it, let me know what setting was the cause.

Thanks.

[Glarioo]

- Updated the X264 keyint variable to better
match frame rates.

Mr. Jdobbs, can you explain what this means, please.

[HWK]

- Updated the X264 keyint variable to better
match frame rates.

Mr. Jdobbs, can you explain what this means, please.

It means BD-RB account for different frame rate found in various sources.

Example if you do 25fps source, it will set keyint 25fps not 24 unlike before which it did.

Keyint instructs encoder after how many frames, I frame need to be inserted.

[Sharc]

I made a Quick-Play Backup of a 3D Blu-Ray disc, with SBS 3D output enabled. The burnt disc plays the quick-menu, but the feature does not start when selecting the title. The standalone just resets. (The SBS-encoded .m2ts of the feature exists on the disc.)
Is 3D SBS with Quick-Play menu not BD compliant?

[jdobbs]

I made a Quick-Play Backup of a 3D Blu-Ray disc, with SBS 3D output enabled. The burnt disc plays the quick-menu, but the feature does not start when selecting the title. The standalone just resets. (The SBS-encoded .m2ts of the feature exists on the disc.)
Is 3D SBS with Quick-Play menu not BD compliant?It is compliant as long as it is Half SBS @ 1920x1080 or less. As far as the standard is concerned it is just another 1080p source -- the conversion to 3D is done by the display.

[AmigaFuture]

@JD

"50 Shades of Grey" update: I am not able to get it to repeat, yet. I've removed AnyDVD completely from Windows 7, and reinstalled. I first noticed it with last version of BD-RB and a previous version of AnyDVD so I'll revert to those soon. I'm very curious now.

[Sharc]

It is compliant as long as it is Half SBS @ 1920x1080 or less. As far as the standard is concerned it is just another 1080p source -- the conversion to 3D is done by the display.
Yes, it is half SBS. So the problem with this disc (Maleficent, Disney) not starting from the Quick menu must be somewhere else. I'll try again.

Is the 3D flag embedded in the .m2ts, or is it part of the .clpi or ...? In other words, when I stream the half-SBS .m2ts to the TV, should the TV switch automatically to 3D? Now I can't even switch it manually to 3D. It displays it SBS only.
I remuxed the .m2ts file to .mkv, set the 3D flag when muxing, and the TV displays the remuxed .mkv correctly in 3D, but I have not seen a similar flag setting option for tsmuxer.

[jdobbs]

No. The TV normally wouldn't automatically recognize it as 3D since is is SBS. You'd have to set it manually on the monitor.

There is a flag that is set in a couple of places for a BD saying it is 3D, as well as some MPLS and CLPI extension data -- but they only apply if it is presented as MVC (not SBS). In that case the 3D player then changes the signal so the TV recognizes it as 3D.

If you're outputting to a BD-R for playback in 3D, it is a much better solution to output to MVC. But, of course, that takes a lot longer to encode.

The advantage, on the other hand, of SBS output is that you don't need a 3D capable BD player.

[Sharc]

No. The TV normally wouldn't automatically recognize it as 3D since is is SBS. You'd have to set it manually on the monitor.

There is a flag that is set in a couple of places for a BD saying it is 3D, as well as some MPLS and CLPI extension data -- but they only apply if it is presented as MVC (not SBS). In that case the 3D player then changes the signal so the TV recognizes it as 3D.

If you're outputting to a BD-R for playback in 3D, it is a much better solution to output to MVC. But, of course, that takes a lot longer to encode.

The advantage, on the other hand, of SBS output is that you don't need a 3D capable BD player.
I see, thank you.
The problem remains that I can't start the movie from the Quick-menu for whatever reason. Seems to be a problematic disc or menu structure. I'll re-author it as movie-only. This should work, I guess.

[Edit:]
Hmmm..... Is the reason for the playback failure possibly that the Quick-Play disc is flagged as 3D in the MPLS and CLPI extensions although the video is encoded as half-SBS?

[jdobbs]

Hmmm..... Is the reason for the playback failure possibly that the Quick-Play disc is flagged as 3D in the MPLS and CLPI extensions although the video is encoded as half-SBS? I don't think I flag them or add the extensions for SBS, but I'll check just to be sure. Quick Play does use the original MPLS and CLPI, so I could have missed it.

As an alternative, instead of using Quick Play for the backup, try importing instead. I rarely use Quick Play, as I typically import if I want to reauthor. One advantage of an import is that you get rid of multipart.

[Sharc]

I don't think I flag them or add the extensions for SBS, but I'll check just to be sure. Quick Play does use the original MPLS and CLPI, so I could have missed it.

As an alternative, instead of using Quick Play for the backup, try importing instead. I rarely use Quick Play, as I typically import if I want to reauthor. One advantage of an import is that you get rid of multipart.

I checked the Quick Play version with BDedit. I don't understand this tool very well, but from what I have seen it appears that the index.bdmv flags the video as "SS" and "Stereoscopic" is ticked. Probably because it's just copied from the original, as you mention. Maybe this flag confuses my standalone when the video is half SBS rather than MVC.

As an alternative to Quick Play I tried importing from the mounted .iso. It imports the base view only, then wants to backup. The dependent view does not get imported, it seems .....

[jdobbs]

I checked the Quick Play version with BDedit. I don't understand this tool very well, but from what I have seen it appears that the index.bdmv flags the video as "SS" and "Stereoscopic" is ticked. Probably because it's just copied from the original, as you mention. Maybe this flag confuses my standalone when the video is half SBS rather than MVC.

As an alternative to Quick Play I tried importing from the mounted .iso. It imports the base view only, then wants to backup. The dependent view does not get imported, it seems .....Yeah, that's probably it. The SS flag wouldn't likely make a difference -- but the extensions will confuse it because they would be saying there is MVC information.

I'll look at it and fix it. I'll also look at the import function to make sure it extracts and includes MVC info.

[Sharc]

Yeah, that's probably it. The SS flag wouldn't likely make a difference -- but the extensions will confuse it because they would be saying there is MVC information........

Yep. The 00001.mpls includes Extension Data for the Base AND Dependent (MVC) stream which isn't there for SBS.

No rush to fix it. I can always remux the .m2ts to .mkv and stream the file to the TV and watch it 3D. No problem. BD-RB is a great tool.