BD Rebuilder Beta - Bug Reports Only

[Ch3vr0n]

@ripburnlearn: it would help if you would post the entire log from the rebuild attempt and not just the inspect.exe results. Those alone don't mean a damn thing.

[ripburnlearn]

Love you guys! That was the problem, my overclock was causing the crashes. I have an AMD FX 8350 and I overclocked it to 4.3GHz. It was causing problems with other apps, I guess this BD Rebuilder app is a true CPU tester. I have to go back to 4GHz now, boooo. haha. I'm getting about 72FPS encoding speeds. Is that good? It was at 74-75FPS with the overclock.

It looks like the new Robocop 4K Remastered Edition has been compressed (the movie title is confusing, the film isn't in 4K its in 1080P). Consider me very happy! You can get the movie at Best Buy for $8, it comes with $7.50 of free Hollywood Movie Cash which can be used at almost all movie theaters. I think you can only use it for the new Robocop movie that is coming out though. Still, that's a really awesome movie deal!

[jdobbs]

Love you guys! That was the problem, my overclock was causing the crashes. I have an AMD FX 8350 and I overclocked it to 4.3GHz. It was causing problems with other apps, I guess this BD Rebuilder app is a true CPU tester. I have to go back to 4GHz now, boooo. haha. I'm getting about 72FPS encoding speeds. Is that good? It was at 74-75FPS with the overclock.

It looks like the new Robocop 4K Remastered Edition has been compressed (the movie title is confusing, the film isn't in 4K its in 1080P). Consider me very happy! You can get the movie at Best Buy for $8, it comes with $7.50 of free Hollywood Movie Cash which can be used at almost all movie theaters. I think you can only use it for the new Robocop movie that is coming out though. Still, that's a really awesome movie deal!I'm also running an FX-8350 on my main video encoding computer. I run at 4.2Ghz and I'm cooling with a Corsair water-cooled system. Even with that I have to clean out the radiator every month or two to keep my system from overheating.

X264 is the ultimate test for overclocking.

[jdobbs]

I have updated the first post of this thread with links to a new version of BD-RB (v0.46.03). Changes for this release:- Added fully BD compliant 3D support for
movie-only backups. SBS and O/U 3D output
is still supported via selection of the
"Enable SBS 3D Movie-Only output" option
in the setup menu and the "TYPE_OF_3D"
hidden option output, but is not the pre-
ferred 3D method. NOTE: This feature
requires Windows 7 or higher, and will be
disabled on lower O/S versions.
- Created a new hidden option, OUTPUT_3D_ISO.
By default movie-only backups are written
directly to an ISO image for burning rather
than a folder. Setting this option to "0"
will create a folder instead. Note: Using
the folder option will result in degraded
output due to the structure of 3D discs.
- Added a hidden option "MENU_FORCE_QUICK=1"
that will create a quick menu even when
only one playlist is selected to be kept.
This applies only to Quick-Play backups,
not to imports.
- Updated code to fully support DTS Express
secondary streams without the need for
special processing.
- Fixed an issue in which the Quick-Plan and
import MENU's IGS M2TS file could be
incorrectly timed -- which could cause
problems on some players.
- Corrected an error in which the SupTitle
checkbox was not being properly initiated
when the SETUP dialog form is loaded.
- Corrected an error in which some PGCs could
be incorrectly ignored during DVD imports.
- Added a new hidden option, ALTPATH, that is
read at program start. This creates a path
to a customized ALTERNATE.TXT file that can
be created by a user. Note that the option
must be placed in the "[Paths]" area of the
config/INI file. See HIDDENOPTS.TXT for more
details.
- Corrected an issue in which menu backgrounds
created for IMPORT/Quick-Play could have
GOP lengths that are too long when a target
size of BD-5 or BD-9 has been selected.
- Fixed an error in backup of 3D sources to
SBS or O/U format that could result in sizes
that are significantly smaller than selected
targets.
- Corrected an error in which multipart VC-1
interlaced sources or secondary video in
movie-only mode could cause BD-RB to stop
with "Error in attempt to MKVMERGE" during
A/V extraction.
- Corrected an error in which the main feature
could (under odd circumstances) be ignored
and not appear in the BD IMPORT list.
- Fixed a problem in which collecting/using
a menu background that used VC-1 was not
working during BD IMPORT.
- Added FRIMDecode and FRIMEncode (v1.19) to
BD-RB's included set of tools.
- Updated the included version of TSMUXER to
a newer release (v2.6.11).
- Other minor corrections and cosmetic fixes. Note that there have been significant modifications to this release in order to implement 3D movie-only processing and to reorganize the process flow for the future possibility of full 3D backups -- please report any newly found issues in this thread. Another example of why the software is in a seemingly never-ending "beta" state. Next up -- enabling the software to run without a requirement for AVISYNTH, HAALI, and FFDSHOW.

[Ch3vr0n]

Jdobbs, can you explain why 3d requires w7? Why won't it work with vista for example. That is my main rig and I can't upgrade it without risking issues with custom software that would require a costly technician to come round to the house. There isn't that much difference between vista and w7. W7 is built on vista.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[laserfan]

Changes for this release:
- Updated the included version of TSMUXER to
a newer release (v2.6.11).

I have been wondering whether 2.6.11 was "ready for prime-time" yet. Your endorsement is good enough for me. Thanks!

[jdobbs]

Jdobbs, can you explain why 3d requires w7? Why won't it work with vista for example. That is my main rig and I can't upgrade it without risking issues with custom software that would require a costly technician to come round to the house. There isn't that much difference between vista and w7. W7 is built on vista.

Verstuurd vanaf mijn Nexus 7 met TapatalkIt needs to be decoded with FRIMDecode and encoded with FRIMEncode. They require Windows 7. There is no other viable option, nor one that I see on the near horizon.

[jdobbs]

I have been wondering whether 2.6.11 was "ready for prime-time" yet. Your endorsement is good enough for me. Thanks! It still has some things that need to be worked out. But from my testing either those things don't have an impact, or I've found a workaround for use in BD-RB's operation. We'll know more after this version gets some good rubber-on-the-road testing from everyone.

[Ch3vr0n]

Ah well, I suppose I can fire up that dual boot on the rig one you manage to implement full disc 3d backup. Got w7 installed, Just never use it unless I have to.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[laserfan]

It still has some things that need to be worked out. But from my testing, either those things don't have an impact, or I've found a workaround for use in BD-RB's operation. We'll know more after this version gets some good rubber-on-the-road testing from everyone.
Thank you for cautioning. :)

[jdobbs]

Ah well, I suppose I can fire up that dual boot on the rig one you manage to implement full disc 3d backup. Got w7 installed, Just never use it unless I have to.

Verstuurd vanaf mijn Nexus 7 met Tapatalk Not sure what might be the issue with the upgrade. From my own experience, Win7 is much better (a lot more stable) than Vista.

I don't have Vista installed on any of my systems right now, so I can't test it. What version number shows when BD-RB runs under Vista (I can't remember)?

[Ch3vr0n]

well there won't be issues with windows itself, but their may be issues with the custom (accounting) software. For pdf functionality, it relies on a custom built (by them) of a pdf printer (non-adobe) which may stop working on the upgrade, same for in-app invoice mailing capabilities.

Inspect shows: windows version 6.0 [6002] for vista

[jdobbs]

well there won't be issues with windows itself, but their may be issues with the custom (accounting) software. For pdf functionality, it relies on a custom built (by them) of a pdf printer (non-adobe) which may stop working on the upgrade, same for in-app invoice mailing capabilities.

Inspect shows: windows version 6.0 [6002] for vistaIf you want I can create a test version for you that will accept 6.0 for testing (now it looks for 6.1) -- and you can test it to see if it works.

[Ch3vr0n]

that would be AWESOME, it would both help me and perhaps even you as you'd know if vista (ultimate x64 in my case) would work or not. Got a couple 3D discs i can test it on :)

[rendez2k]

Quick question with the new 3D mode - is there anywhere that states its a 3D disc before conversion? For instance, should I be seeing a '3D Movie Only' option in the menu?

[Sharc]

I have updated the first post of this thread with links to a new version of BD-RB (v0.46.03). Changes for this release:- Added fully BD compliant 3D support for
movie-only backups. SBS and O/U 3D output
is still supported via selection of the
"Enable SBS 3D Movie-Only output" option
in the setup menu and the "TYPE_OF_3D"
hidden option output, but is not the pre-
ferred 3D method. NOTE: This feature
requires Windows 7 or higher, and will be
disabled on lower O/S versions.
- Created a new hidden option, OUTPUT_3D_ISO.
By default movie-only backups are written
directly to an ISO image for burning rather
than a folder. Setting this option to "0"
will create a folder instead. Note: Using
the folder option will result in degraded
output due to the structure of 3D discs.
- Added a hidden option "MENU_FORCE_QUICK=1"
that will create a quick menu even when
only one playlist is selected to be kept.
This applies only to Quick-Play backups,
not to imports.
- Updated code to fully support DTS Express
secondary streams without the need for
special processing.
- Fixed an issue in which the Quick-Plan and
import MENU's IGS M2TS file could be
incorrectly timed -- which could cause
problems on some players.
- Corrected an error in which the SupTitle
checkbox was not being properly initiated
when the SETUP dialog form is loaded.
- Corrected an error in which some PGCs could
be incorrectly ignored during DVD imports.
- Added a new hidden option, ALTPATH, that is
read at program start. This creates a path
to a customized ALTERNATE.TXT file that can
be created by a user. Note that the option
must be placed in the "[Paths]" area of the
config/INI file. See HIDDENOPTS.TXT for more
details.
- Corrected an issue in which menu backgrounds
created for IMPORT/Quick-Play could have
GOP lengths that are too long when a target
size of BD-5 or BD-9 has been selected.
- Fixed an error in backup of 3D sources to
SBS or O/U format that could result in sizes
that are significantly smaller than selected
targets.
- Corrected an error in which multipart VC-1
interlaced sources or secondary video in
movie-only mode could cause BD-RB to stop
with "Error in attempt to MKVMERGE" during
A/V extraction.
- Corrected an error in which the main feature
could (under odd circumstances) be ignored
and not appear in the BD IMPORT list.
- Fixed a problem in which collecting/using
a menu background that used VC-1 was not
working during BD IMPORT.
- Added FRIMDecode and FRIMEncode (v1.19) to
BD-RB's included set of tools.
- Updated the included version of TSMUXER to
a newer release (v2.6.11).
- Other minor corrections and cosmetic fixes. Note that there have been significant modifications to this release in order to implement 3D movie-only processing and to reorganize the process flow for the future possibility of full 3D backups -- please report any newly found issues in this thread. Another example of why the software is in a seemingly never-ending "beta" state. Next up -- enabling the software to run without a requirement for AVISYNTH, HAALI, and FFDSHOW.
Wow!!! Busy weekend for testing in sight!
Thanks a lot for the new version.

[Sharc]

Quick question with the new 3D mode - is there anywhere that states its a 3D disc before conversion? For instance, should I be seeing a '3D Movie Only' option in the menu?
Good question.
Is 3D enabled "silently"? The menu structure and Settings look like before for 2D. I may probably be missing something ..... ?

Edit:
I just found that 3D encoding gets automatically enabled for "movie only" if the source is 3D. No special settings required. :o
Now the question remains what to do it if I want the Movie Only backup in 2D? :devil:

[jdobbs]

Quick question with the new 3D mode - is there anywhere that states its a 3D disc before conversion? For instance, should I be seeing a '3D Movie Only' option in the menu?You'll see "MVC 3D Output Mode enabled" and "Decoding/Frame serving: FRIMDecode" in the log.

[jdobbs]

that would be AWESOME, it would both help me and perhaps even you as you'd know if vista (ultimate x64 in my case) would work or not. Got a couple 3D discs i can test it on :)Check your PM.

[Monty11]

When BD-RB v0.45.05 processes a 704x464 pixel MKV file I have, it imports the file OK, but when I press Backup the process fails with the message "Haali Media Splitter. Error: can't open file: The media type of this file is not recognized." The file was produced by VidCoder (= Handbrake). Inspect.exe gives OK for all tests.

Here are the MKV file details: Width : 704 pixels Height : 464 pixels Display aspect ratio : 4:3 Original display aspect ratio : 4:3 Frame rate : 29.970 fps Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Bits/(Pixel*Frame)

[jdobbs kindly commented on this problem in the tsMuxeR GUI thread, but moved the discussion (by mistake, I think) to the DVD Rebuilder thread rather than the BD-RB thread.]

[Sharc]

...Note that there have been significant modifications to this release in order to implement 3D movie-only processing and to reorganize the process flow for the future possibility of full 3D backups -- please report any newly found issues in this thread. Another example of why the software is in a seemingly never-ending "beta" state. Next up -- enabling the software to run without a requirement for AVISYNTH, HAALI, and FFDSHOW.
I want to report back that a 3-D backup on BD-9 finished successfully without issues. Quality is quite good for the 90 minutes movie.
It is perhaps a bit irritating that the log lists the irrelevant settings for 2-D as well, like
- RESIZE 1920 to 1440 enabled
- X264 Tweak(s) enabled
These have no effect though; pure cosmetics.

[Sharc]

They are ignored when BD-RB gets an error trying to decode them. I'm not familiar with that disc. Is there any way you can send me a short sample where the subtitle is ignored?

BD-RB doesn't use TSMUXER to demux DVDs, it does it itself.
These subs are still ignored by the latest version 0.46.03.
I sent you a short sample; anything special with the format? Not terribly important as I had this problem only with this particular disc so far.

[brunchto]

Hi,

thanks for the last BDRB version !!!
I 've tried to make a BR3D movie only backup. i wish to do this without reencoding, but i cannot find how.
for BR2D, if final size is lower than destination, then there is no reencode. but for 3D, there is always reencoding of the video part.

Is there a way to do 3DBR without reencoding?

[Sharc]

Hi,

thanks for the last BDRB version !!!
I 've tried to make a BR3D movie only backup. i wish to do this without reencoding, but i cannot find how.
for BR2D, if final size is lower than destination, then there is no reencode. but for 3D, there is always reencoding of the video part.

Is there a way to do 3DBR without reencoding?
Did you try with
FORCE_NOENCODE=1
in the BDREBUILDER.ini ?
(see hiddenopts.txt)

[jdobbs]

When BD-RB v0.45.05 processes a 704x464 pixel MKV file I have, it imports the file OK, but when I press Backup the process fails with the message "Haali Media Splitter. Error: can't open file: The media type of this file is not recognized." The file was produced by VidCoder (= Handbrake). Inspect.exe gives OK for all tests.

Here are the MKV file details: Width : 704 pixels Height : 464 pixels Display aspect ratio : 4:3 Original display aspect ratio : 4:3 Frame rate : 29.970 fps Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Bits/(Pixel*Frame)

[jdobbs kindly commented on this problem in the tsMuxeR GUI thread, but moved the discussion (by mistake, I think) to the DVD Rebuilder thread rather than the BD-RB thread.]I moved it to a thread of its own.

[jdobbs]

I want to report back that a 3-D backup on BD-9 finished successfully without issues. Quality is quite good for the 90 minutes movie.
It is perhaps a bit irritating that the log lists the irrelevant settings for 2-D as well, like
- RESIZE 1920 to 1440 enabled
- X264 Tweak(s) enabled
These have no effect though; pure cosmetics.I'll have to add code to suppress those messages. I'd made a note to do that but never got around to it.

[jdobbs]

These subs are still ignored by the latest version 0.46.03.
I sent you a short sample; anything special with the format? Not terribly important as I had this problem only with this particular disc so far.Sorry, I haven't worked on it yet.

[jdobbs]

Hi,

thanks for the last BDRB version !!!
I 've tried to make a BR3D movie only backup. i wish to do this without reencoding, but i cannot find how.
for BR2D, if final size is lower than destination, then there is no reencode. but for 3D, there is always reencoding of the video part.

Is there a way to do 3DBR without reencoding?Currently it doesn't do the "keep original" check. It's related to the code I've added for future full 3D backup. I'll have to fix that.

[minhjirachi]

Can I use this soft to fix bug on 3D Blu-ray Disc? Because I have a problem with pop-up menu. So that if I keep the Pop-Up menu, it can play in 3D. But if I remove the Pop-Up menu in the playlist, I can play 3D clip normally. I think it's a problem when I using tsmuxer to remux the main clip and when I re-add the old Pop-up menu in to that playlist, it does not match the ID anymore. So does your software can correct that problem?

So I want to know clearly before going to use your software.

Thank you so much.

[jdobbs]

Can I use this soft to fix bug on 3D Blu-ray Disc? Because I have a problem with pop-up menu. So that if I keep the Pop-Up menu, it can play in 3D. But if I remove the Pop-Up menu in the playlist, I can play 3D clip normally. I think it's a problem when I using tsmuxer to remux the main clip and when I re-add the old Pop-up menu in to that playlist, it does not match the ID anymore. So does your software can correct that problem?

So I want to know clearly before going to use your software.

Thank you so much.I'm not positive I understand what you're saying. But if it failed when adding after-the-fact with TSMUXER, it's likely going to have the same result when you do the it with BD-RB.

How are you re-adding the pop-up, with BDEDIT? 3D gets tricky because there is additional stream information kept in MPLS and CLPI extensions.

[Ch3vr0n]

Well i figure it' be worth mentioning here for all the ppl here that might still use vista like myself. 3D rebuild will NOT work on vista, the test build i received from Jdobbs works fine on the extraction part but FRIM errors out on the actual frameserving / encoding part. So w7 and up is mandatory.

[Yordan5]

Thanks for the heads up but I don't imagine many people would be on Vista as even Microsoft admitted it was one to forget.

[DoctorM]

Sooo... I assume that means no XP support. :-)

[HWK]

Sooo... I assume that means no XP support. :-)

No, need to assume. You can be assured no XP support and no it is not Jdobbs fault. Program he uses require win 7 at minimum to work.

[Ch3vr0n]

@hwk pretty sure he was being a bit sarcastic. Smiley at the back.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[DarWun]

When doing a movie only copy of Hugo 3D to BD-9 on a Windows 8.1 system, the reencode using FRIMEnoder has failed on two attempts. On the first, it failed on the first pass at around 99%, and on the second it failed on the first pass at around 83%. The log file simply says Failed video encode.

Let me know if what I need to provide to help in the troubleshooting. In the mean time I'm going to attempt a rebuild of a different movie to see if the same thing occurs.

[Limobar]

Does the new 3D mode only use ABR? I started a 2-pass encode, but an ABR encode does actually start.

[jdobbs]

Does the new 3D mode only use ABR? I started a 2-pass encode, but an ABR encode does actually start.Yes. FRIMEncode only supports 1 pass encoding.

[minhjirachi]

I'm not positive I understand what you're saying. But if it failed when adding after-the-fact with TSMUXER, it's likely going to have the same result when you do the it with BD-RB.

How are you re-adding the pop-up, with BDEDIT? 3D gets tricky because there is additional stream information kept in MPLS and CLPI extensions.

Yup. You're right. I'm using BDEdit to add the Pop-Up menu. With those movies, which contain IGS Menu, I have to use Scenarist to remux in order to keep the original menu. But if I using the Scenarist, I will lost the original 3D Offset. If you gain something, you also lose something. If we have a software, which can export the OFS file to re-import into Scenarist, it's pretty good. But if your software can fix that problem, I hope I will be the first person to test it.

Thank you for your answer.

[Limobar]

Yes. FRIMEncode only supports 1 pass encoding.
OK and only ABR, not CRF.

I have a question about the quality of the new 3D mode. Does it make a difference in quality to use the existing (x264) quality profiles, or is there just one quality?

I assume that the tweak lines concerning encoder settings do not work in this new 3D mode. Am I right?

[jdobbs]

OK and only ABR, not CRF.

I have a question about the quality of the new 3D mode. Does it make a difference in quality to use the existing (x264) quality profiles, or is there just one quality?

I assume that the tweak lines concerning encoder settings do not work in this new 3D mode. Am I right?Yes. Tweaking relates specifically to X264 settings, so it wouldn't apply. As for CRF, FRIMEncode does appear to have a QP mode, but that generally creates a larger file than CRF for the same quality -- and currently there is no reasonable method for seeking, so estimating output size is out of the question.

I could add tweak settings that are specifically aimed at FRIMEncode if that's any help.

[HWK]

Jdobbs, not sure if you considered this but I was wondering if you process 3d disc, does you program give option to copy as 2D or will it force 3D output. If it does 3D can you add option to have final output 2D instead of 3D.

Also I think we don't need this anymore as a hidden option, what do you think.

DTSX_ENABLE=n n = 0/1 - 0=Ignore DTS Express secondary audio, 1= Enable experimental DTS Express muxing

Since you added full DTS Express Processing

- Updated code to fully support DTS Express secondary streams without the need for special processing.

[jdobbs]

Jdobbs, not sure if you considered this but I was wondering if you process 3d disc, does you program give option to copy as 2D or will it force 3D output. If it does 3D can you add option to have final output 2D instead of 3D.

Also I think we don't need this anymore as a hidden option, what do you think.



Since you added full DTS Express ProcessingThere is an undocumented hidden option called IGNORE_3D that can be used. It's only undocumented because I forgot... You'd just add IGNORE_3D=1 to the [Options] area of the Config/INI file.

I need to remove the DTSX_ENABLE setting and add the new one (IGNORE_3D). DTSX_ENABLE has no effect now.

[Yordan5]

My impression was that if you do not specifically chose 3D iso output option, BD-RB will produce a 2D BD from a 3D title. Thx for the clarification above.

[HWK]

Jdobbs, Can BD-RB capable of handling of secondary video processing with new version of tsmuxer.

[jdobbs]

Jdobbs, Can BD-RB capable of handling of secondary video processing with new version of tsmuxer.BD-RB has always been able to handle secondary video. It shouldn't have changed.

[HWK]

BD-RB has always been able to handle secondary video.

I am not thinking straight :D coffee time for me.

[HWK]

Also may I suggest to add check of frim decoder and encoder version to inspect.exe report

[jdobbs]

Also may I suggest to add check of frim decoder and encoder version to inspect.exe reportI'll do that.

[HWK]

I'll do that.

While you are at it, you may want to check the following. Basically I replace tsmuxer.exe with new version from Roman (tsMuxeR_2.6.12) and inspect said ok in my case, it shouldn't be doing that or it is expected.