BD Rebuilder Beta - Bug Reports Only

[MrVideo]

I think this drives the nail into the coffin:
I have updated the first post of this thread with links to the latestd release of BD-RB (v0.43.01). Changes for this version:- Created a new Mode: "Quick-Play Mode". This mode
is similar to to Movie-Only in that it removes
menus, etc. -- but in Quick-Play mode all
significant playlists are kept. The feature will
play immediately upon insertion into the player
but you can switch to other playlists (extras) by
pushing the "Menu" remote key during playback.
This action will cycle through all playable
items individually. Note: It's possible to have
a Quick-Play that consists of only the movie when
all other playlists are below the threshold that
is considered significant.

So, it looks like I am going to have to have a 2nd dummy item for the menu, in order to even have a menu.

It would really be nice to be able to have a menu, even if there is only one item in an import selection (reason explained above).

[worknstiff]

@MrVideo; RE: It would really be nice to be able to have a menu, even if there is only one item.
You could always use CloneBD to generate a simple one item menu. But if you wanted to make one with custom backgrounds with audio, chapter's with picture icons and audio, subtitle selection screens then you can still use multiAVCHD 4.1. YES it does have a learning curve but it is really an excellent BD authoring program even though unlike BD_Rebuilder, it's not being supported anymore. I still use it occasionally to make a series disk to evenly place the same amount of episodes on each disk. I hate it when one disk has 5 episodes and the last disk has only 2 with tons of extras, lol. I think you will have to run it on Win7 though. I just use it make a 50gb disk and then use BD_Rebuilder to size it, cause it takes forever to encode.

[varekai]

I agree, MultiAVCHD is an excellent software to create your own BD-titles.
Lots of features and possibilities to make a neat menu.
Highly recommended! Really sad it's not developed anymore.

[MrVideo]

I haven't used multiAVCHD in ages. I didn't like how it went from choice to choice and didn't allow a simple selection list like BD-RB does. It just wasn't my cup of tea. OTOH, BD-RB is really great. Sure there are some features that would be nice to have, but pretty much every program has things that users would like to have. Jdobbs has even said that he is leaning toward to making it a full BD authoring program. He is well on his way.

Not sure why multiAVCHD needs to be used to create discs with evenly spaced episode count, since BD-RB lets you do that. It is what I am using to make discs. For example, for a season one set, I controlled which episodes were on a disc by having what I want on a disc in a directory of its own, one for each of the discs. With the ability to use the font I want, I can have the text on the menu use the font that the series uses (when I can get that font).

In the case of the latest issue, I'm adding a trailer for the movie, which now makes the menu have two items. Still doesn't mean I wouldn't like the ability to create single item menus, it doesn't.

[varekai]

Jdobbs has even said that he is leaning toward to making it a full BD authoring program. He is well on his way.
Wow, didn't know that! Wouldn't that be something! :D

[MrVideo]

Yes, it would be nice to have a full authoring package. Go back and read the post. It is not a commitment.

[jdobbs]

I can't remember why it doesn't create the menu on import. I'm sure there's a good reason -- I'll have to go back and check.

But. You can always import, and then do a quick-play backup of the import (instead of a Full Backup), and a menu will be created.

[MrVideo]

I've discovered a bug in the menu creation. View this image (http://vidiot.com/images/BD-RB-menu-error.jpg).

The area containing the error is circled. The settings are in the INI file posted above.

And yes, it is a photo of the screen and not a screen grab as I can't do a screen grab from a Blu-ray player. :D

UPDATE: It is related to the font that is being used. It is "aniron bold" and is available from here (http://www.thehutt.de/tolkien/fonts.html).

The "ringbearer medium" font works just fine.

[MrVideo]

But. You can always import, and then do a quick-play backup of the import (instead of a Full Backup), and a menu will be created.
That didn't work.

When I imported a single file in Full Backup mode and then switched the mode to Quick-Play, BD-RB wouldn't let me edit the menu because I didn't have a source path. When I hit the backup button, it too complained about no source path. There is no source, since the file has already been imported.

[MrVideo]

I just thought of something, because of the thing I found regarding the menu text and something else I saw with a menu.

The menu text appears to be placed within a "box" that has its background color set to the menu backdrop color. That means the menu text can never be placed over an image, because the text isn't within a transparent container. In a previous posting, I asked if there was a way to use the menu background video from a BD release (still haven't heard back on that one). But, if the menu text can't be placed on the menu background without the solid box, it isn't worth having a background image that isn't solid.

Is my understanding of this correct?

[jdobbs]

I just thought of something, because of the thing I found regarding the menu text and something else I saw with a menu.

The menu text appears to be placed within a "box" that has its background color set to the menu backdrop color. That means the menu text can never be placed over an image, because the text isn't within a transparent container. In a previous posting, I asked if there was a way to use the menu background video from a BD release (still haven't heard back on that one). But, if the menu text can't be placed on the menu background without the solid box, it isn't worth having a background image that isn't solid.

Is my understanding of this correct?No. It isn't. Menu text is indeed in a "box" (but that's required by the Blu-Ray standard, not BD-RB). But the background of the box is transparent.

In your post the problem isn't the background color. It's the fact that one piece of text (in a box) is overlapping another. BD-RB pulls the font height/width and sets the spacing based on that... apparently with that font it is wrong.

As for the background video, the only way to do it right now is to import from a BD -- and the background video from the BD will be used.

[jdobbs]

That didn't work.

When I imported a single file in Full Backup mode and then switched the mode to Quick-Play, BD-RB wouldn't let me edit the menu because I didn't have a source path. When I hit the backup button, it too complained about no source path. There is no source, since the file has already been imported.????? The source path is set to the imported Pseudo Structure after an import.

[jdobbs]

That didn't work.

When I imported a single file in Full Backup mode and then switched the mode to Quick-Play, BD-RB wouldn't let me edit the menu because I didn't have a source path. When I hit the backup button, it too complained about no source path. There is no source, since the file has already been imported.I just tried it, and it works exactly as it's supposed to. I'm not sure what you're talking about here.

1. Import the file. At completion the source path is pointing to the Pseudo Structure.
2. Set the backup type to Quick-Play
3. Click on "Edit Quick-Play Menu" from the MODE menu.

I just did it several times with several different files. No problem.

[MrVideo]

I just tried it, and it works exactly as it's supposed to. I'm not sure what you're talking about here.

Here are screen grabs of the steps I took (http://vidiot.com/images/BDRB-quick-play-steps.jpg).

Description:
1) Make sure BD-RB is in Full Backup mode
2) Import a single file
3) Results after import is done
4) Select Quick-Play Backup mode
5) Result after selection is made. Notice source is now empty.
6) Select Edit Quick-Play Menu
7) Result after selection

If those are not the correct steps, which seems to be what you did, please let me know what I need to do differently.

UPDATE: I tried it again, with the same results. But I manually looked in the source directory and all that is in the PSEUDO directory is a PINFO.INF file. There are BDMV and CERTIFICATE directories and the BDMV path contains all of the goodies.

[MrVideo]

No. It isn't. Menu text is indeed in a "box" (but that's required by the Blu-Ray standard, not BD-RB). But the background of the box is transparent.
Weird. I just did a test and purposely moved the menu text over the top of the logo and the text background is indeed transparent.

What got me to believe that the text background wasn't transparent was when I was working on the first disc for Legend of the Seeker. I didn't have the text down far enough and the bottom of the background image logo got clipped by the text box. I also saw a box that the text was in because when I sent the background fill color, I didn't notice that it was at ~10-10-10 (decimal), so the darker level of the text box was visible on the screen.

No idea what happened to cause that.

In your post the problem isn't the background color. It's the fact that one piece of text (in a box) is overlapping another. BD-RB pulls the font height/width and sets the spacing based on that... apparently with that font it is wrong.
I won't be using that font.
As for the background video, the only way to do it right now is to import from a BD -- and the background video from the BD will be used.
I'll stick with static images then.

[gonca]

Here are screen grabs of the steps I took (http://vidiot.com/images/BDRB-quick-play-steps.jpg).

Description:
1) Make sure BD-RB is in Full Backup mode
2) Import a single file
3) Results after import is done
4) Select Quick-Play Backup mode
5) Result after selection is made. Notice source is now empty.
6) Select Edit Quick-Play Menu
7) Result after selection

If those are not the correct steps, which seems to be what you did, please let me know what I need to do differently.

UPDATE: I tried it again, with the same results. But I manually looked in the source directory and all that is in the PSEUDO directory is a PINFO.INF file. There are BDMV and CERTIFICATE directories and the BDMV path contains all of the goodies.

Step 5 --- Just re point to source directory and it should work
I found that changing Mode sometimes clears the source field

[jdobbs]

Here are screen grabs of the steps I took (http://vidiot.com/images/BDRB-quick-play-steps.jpg).

Description:
1) Make sure BD-RB is in Full Backup mode
2) Import a single file
3) Results after import is done
4) Select Quick-Play Backup mode
5) Result after selection is made. Notice source is now empty.
6) Select Edit Quick-Play Menu
7) Result after selection

If those are not the correct steps, which seems to be what you did, please let me know what I need to do differently.

UPDATE: I tried it again, with the same results. But I manually looked in the source directory and all that is in the PSEUDO directory is a PINFO.INF file. There are BDMV and CERTIFICATE directories and the BDMV path contains all of the goodies.I notice you are trying to do a file that is only 76MB. It's kinda' out-there trying to make a complete disc with a menu for a trailer. That's probably the issue. The source probably went blank because there is nothing in the source path that meets the minimum size for quick-menu. Try adjusting QUICK_PLAY_THRESHOLD. It's default minimum is 10 minutes.

[gonca]

Step 5 --- Just re point to source directory and it should work
I found that changing Mode sometimes clears the source field

Apologies to all, can't reproduce this
If I ever run across it again I will try to note the sequence of steps:stupid:

[MrVideo]

I notice you are trying to do a file that is only 76MB. It's kinda' out-there trying to make a complete disc with a menu for a trailer. That's probably the issue. The source probably went blank because there is nothing in the source path that meets the minimum size for quick-menu. Try adjusting QUICK_PLAY_THRESHOLD. It's default minimum is 10 minutes.

The trailer was only being used because it was small, which means it doesn't take long to import. The real file is 22GB, so it takes too long when doing menu creation tests. I didn't think about the threshold because the IMPORT threshold is 15 and it is ignored. I'm able to import two < 15 min files without any issues.

That fixed that issue. But, I expected BD-RB to re-encode the selected file, and it did. As pointed out, I do not want any re-encoding to take place. The input files are to be used as is.

So, this means I'm back to Full Backup mode and stopping after the input stage. That means I will have to have at least two files on the menu. In this case, the feature and a trailer.

I am looking forward to the future where one item will be allowed to have a menu created.

[varekai]

Pardon me, but why go through all this for a BD-title you can buy for 10 bucks?
I can understand if you want to author/customize a BD from a collection of some series, but with this title?

[Ch3vr0n]

it's not up to us to say or question if he should or shouldn't do the thing he wants to do, the way he wants to do it. That's up to him.

[jdobbs]

The trailer was only being used because it was small, which means it doesn't take long to import. The real file is 22GB, so it takes too long when doing menu creation tests. I didn't think about the threshold because the IMPORT threshold is 15 and it is ignored. I'm able to import two < 15 min files without any issues.

That fixed that issue. But, I expected BD-RB to re-encode the selected file, and it did. As pointed out, I do not want any re-encoding to take place. The input files are to be used as is.

So, this means I'm back to Full Backup mode and stopping after the input stage. That means I will have to have at least two files on the menu. In this case, the feature and a trailer.

I am looking forward to the future where one item will be allowed to have a menu created.if you don't want it reencoded, then set the option to force no encoding. It isn't a "bug" when you refuse to read the documentation (as little as there is).

As for "IMPORT threshold is 15 and it is ignored", please note the highlighted info in the description:IMPORT_THRESHOLD=n n = Threshold size (in minutes), default=15, of BD/DVD titles listed for IMPORT selectionWhy in the world would I put a time threshold of an individual file when you are specifically selecting it? BDs and DVDs have lots of small extraneous titles, and the threshold is there to save you the time of reviewing them all, some of which may consist of no more than a single frame.

[varekai]

it's not up to us to say or question if he should or shouldn't do the thing he wants to do, the way he wants to do it. That's up to him.
Hi there, thought I'd see you sooner or later! lol
OK, to each his own... but it looks like MrVideo having more trouble than fun, and it's supposed to be fun being creative.

[Ch3vr0n]

You know what they say. 'No pain, no gain'. Note everything creative is easy :-)

Verstuurd vanaf mijn Nexus 6P met Tapatalk

[veggav]

When using QUICK_CRF, the higher the number the smaller the extras file size? Or is it the other way around?

[jdobbs]

When using QUICK_CRF, the higher the number the smaller the extras file size? Or is it the other way around?The first way. Smaller numbers mean higher quality and bigger file size, larger numbers mean lower quality and smaller file size.

[MrVideo]

Pardon me, but why go through all this for a BD-title you can buy for 10 bucks?

I have all three of the Lord of the Rings Extended editions. The problem with each one is that the movie is spread over two discs. I've re-encoded and edited th two parts together to make a single extended feature.

That is what is being authored to a disc. Then it will be added to the rest of the discs in the movie's set.

[jdobbs]

I have all three of the Lord of the Rings Extended editions. The problem with each one is that the movie is spread over two discs. I've re-encoded and edited th two parts together to make a single extended feature.

That is what is being authored to a disc. Then it will be added to the rest of the discs in the movie's set.I understand. I've done similar combinations myself.

[MrVideo]

if you don't want it reencoded, then set the option to force no encoding. It isn't a "bug" when you refuse to read the documentation (as little as there is).
Look at the INI file that I posted in a previous posting. It is set to 1, but is being ignored. I even have it in the main BDREBUILDER.INI, so that every job has that setting.

Here is the log file:
[20:06:15] Importing MKV: THE_LORD_OF_THE_RINGS-THE_FELLOWSHIP_OF_THE_RING-OFFICIAL_TRAILER_DD20
- Collecting audio/video streams from source...
- Building pseudo-BD source structure...
[20:06:23] Video import completed successfully.
----------------------
[10/14/16] BD Rebuilder v0.50.18
[20:06:51] Source: THE_LORD_OF_THE_RINGS-THE_FELLOWSHIP_OF_THE_RING-OFFICIAL_TRAILER_DD20
- Input BD size: 0.07 GB
- Approximate total content: [00:02:54.174]
- Target BD size: 22.95 GB
- Windows Version: 5.2 [3790]
- Quick-Play Reauthoring mode enabled
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[20:06:51] PHASE ONE, Encoding
- [20:06:51] Processing: VID_00000 (1 of 1)
- [20:06:51] Extracting A/V streams [VID_00000]
- [20:06:57] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1280x720
- Rate/Length: 23.976fps, 4,176 frames
- Bitrate: 35,000 Kbs
- [20:06:57] Reencoding: VID_00000, Pass 1 of 1
[20:07:16]PHASE ONE aborted by user request

As for "IMPORT threshold is 15 and it is ignored", please note the highlighted info in the description:IMPORT_THRESHOLD=n n = Threshold size (in minutes), default=15, of BD/DVD titles listed for IMPORT selectionWhy in the world would I put a time threshold of an individual file when you are specifically selecting it? BDs and DVDs have lots of small extraneous titles, and the threshold is there to save you the time of reviewing them all, some of which may consist of no more than a single frame.
Sorry, but since that setting is part of the main INI file, I never looked to see if it was in the HIDDEN file, as I didn't expect it to be there. That is because the first line of the HIDDEN file says that the following is a list of options that can be added to the main file. So, I never went looking for a description of it.

Live and learn.

[MrVideo]

Hi there, thought I'd see you sooner or later! lol
OK, to each his own... but it looks like MrVideo having more trouble than fun, and it's supposed to be fun being creative.

It is a learning curve. Things are definitely getting there. Try doing real authoring with Scenarist. That is a real PITA, hence I do not use it. I started to. BD-RB is a lot easier to use to make a simple menu of selectable items. I do not need anything fancy. In most cases I will be making Blu-rays that contain multiple episodes, like Legend of the Seeker, which was only released on DVD (ABC Studios has a habit of pretty much only releasing TV shows on DVD). Because I have the episodes as 35 Mbps MPEG-2 files (from the syndicated sat feeds), I've recoded to H.264 and now assembling the episodes on Blu-ray. I've been waiting for the right tool to come along, and BD-RB is it.

The only piece of the puzzle to yet arrive is the ability to make a menu only containing a single imported MKV file. So, for this run, I'm adding a trailer of the movie to each disc. When I get to the Hobbit trilogy, maybe it will be available.

[veggav]

The first way. Smaller numbers mean higher quality and bigger file size, larger numbers mean lower quality and smaller file size.


Thank you :)

[jdobbs]

The first way. Smaller numbers mean higher quality and bigger file size, larger numbers mean lower quality and smaller file size.


Thank you :)Yeah. I know it sounds a little backwards. But CRF is a more sophisticated implementation of constant quantizer settings. Increasing the quantization factor reduces filesize while increasing the risk of distortion.

[jdobbs]

Look at the INI file that I posted in a previous posting. It is set to 1, but is being ignored. I even have it in the main BDREBUILDER.INI, so that every job has that setting.Hmm... as mentioned before, that means that BD-RB (for some reason) thinks the source isn't compliant. I may have to introduce a new hidden option that tells it "Really, I know what I'm doing... don't reencode, dumbass."

1. Is there anything in the PSEUDO folder? Resizing to BD standards can force encoding.
2. Is your output set to DVD-5/9. If so, reencoding is required because of the lower maximum bitrate for DVD media.

[jdobbs]

@MrVideo

Ok. I looked at the code, and any source that has a PSEUDO folder is forced into encoding. So in order to trick it into not knowing it's an import, after you import, delete the PSEUDO folder (assuming it is empty), and then reopen it with BD-RB. The should allow the FORCE_NOENCODE to take effect (assuming no other reason exists like forced resizing to meet standards).

I'll look at how much work it might be to examine everything and see if I can delete it myself. But the problem is that there are SO MANY things that have to be checked (bitrates, maximums, GOP limitations, levels, b-frame counts, etc) that I'm not sure I want to go through all that. The bottom line is that you just can't trust an imported source to be compliant.

[worknstiff]

I always move the BD folder from the PSEUDO folder anyhow. I think when BD_Rebuilder first started creating quick play BD's with simple menu's, I kept having problems with it creating an extra bogus menu entry probably for the menu creation. I started using a custom size for the BD compilation of 50,000 to make sure it didn't re-encode the 4 episode m2ts video files. After it created the BD, I would then move it from the work folder drive back onto the drive I use for the source and do a full backup resized for a BD25 disk. I found that I could re-edit the quick play menu to remove the bogus entry and also the compilation would be far more accurate with the size limits I specified. Also I had no surprises with the disk structure being playable after spending hours to re-encode a broken menu or an episode in the wrong order. I even had some episodes from a series disk that only had 2 episodes on the final disk and I would use BD_Rebuilder to do only the oversized episodes to a custom size to get them to be comparable to some episodes from a more compressed disk before using them on a 4 episode BD disk. BD_Rebuilder has really become a great video authoring tool for my movie hobby. Many thanks to jdobbs for all the hard work. I wish there was some way I could help support it's development more.

[MrVideo]

@jdobbs:

This whole exercise has come about in order to try and get a menu created for a single import file. Might it be easier to just allow creation of a menu in Full Backup mode, if the option to create a menu with only one item is set to 1? Because then there will be zero recoding because an actual backup will not be done. The structure that is created after importing, and menu editing, is where I stop and burn the contents of the BDMV/CERTIFICATE directories.

I suspect that doing it this way will be a whole lot less work than doing any of the other things you mentioned above.

[jdobbs]

@jdobbs:

This whole exercise has come about in order to try and get a menu created for a single import file. Might it be easier to just allow creation of a menu in Full Backup mode, if the option to create a menu with only one item is set to 1? Because then there will be zero recoding because an actual backup will not be done. The structure that is created after importing, and menu editing, is where I stop and burn the contents of the BDMV/CERTIFICATE directories.

I suspect that doing it this way will be a whole lot less work than doing any of the other things you mentioned above.If you are creating a new menu, then by definition it isn't "Full Backup Mode". That pretty much defines the difference between Full-Backup Mode and Quick-Play Backup mode.

I'll look at allowing menu creation for single file imports.

[MrVideo]

If you are creating a new menu, then by definition it isn't "Full Backup Mode". That pretty much defines the difference between Full-Backup Mode and Quick-Play Backup mode.
Then I'm confused by the operation. Full Backup Mode is the only mode that allows for importing of various types of single video files. At that time, you are then provided the menu editing GUI. In Quick-Play Backup mode, you are not allowed to import files at all. The import selection is grayed out.

So, because of that, I use Full Backup mode in order to import the MKV files that I want on the disc. I then edit the menu contents and it then imports the files and builds the menu. After which it stops. I then burn that BDMV structure. I do not do the backup, as that would recode all of the files. Plus, since what I want is already in the BDMV structure, I do not have to do the backup.
I'll look at allowing menu creation for single file imports.
Thanks.

[gonca]

Full Backup Mode is the only mode that allows for importing of various types of single video files.

I'm importing MKVs right now and I believe the mode I am in is alternate movie only
I think that Backup Mode and Import function separately

[MrVideo]

I think that Backup Mode and Import function separately

It is hard to think that they function separately, when the Import option is grayed out when you are not in Full Backup mode.

[gonca]

I've just tested
The only time IMPORT is greyed out is on QUICK-PLAY BACKUP
FULL BACKUP / MOVIES & MENU /MOVIE ONLY / ALTERNATE BACKUP not greyed out

You can IMPORT and then change your back up mode prior to "encoding"

[jdobbs]

Then I'm confused by the operation. Full Backup Mode is the only mode that allows for importing of various types of single video files. At that time, you are then provided the menu editing GUI. In Quick-Play Backup mode, you are not allowed to import files at all. The import selection is grayed out.

So, because of that, I use Full Backup mode in order to import the MKV files that I want on the disc. I then edit the menu contents and it then imports the files and builds the menu. After which it stops. I then burn that BDMV structure. I do not do the backup, as that would recode all of the files. Plus, since what I want is already in the BDMV structure, I do not have to do the backup.

Thanks.Importing isn't a backup mode of any kind. That's why it's under the FILE menu, not MODE. It is simply taking files and converting them into a BD structure so it can later be backed up and made BD compliant (thus the term "pseudo structure") in whatever mode you select. The only reason you can't be in Quick-Play mode during an import is because importing uses quick-play to create the structure and menus resulting in a conflict.

[MrVideo]

Ah, OK. Learning more every day.

[raisingcanex]

As you know I had posted last week about failed to retrieve audio errors. Since then I have tried everything I can think of re-riped files from Anydvd to the hard drive (multiple times of the same movies which were store bought). Tried ripping Blu-Ray folders even ISO's. Tried BD-9 and BD-25 and the BD Quick BD-25. Freed up Hard drive. Run virus scan and defragement. Tried different versions of BD Rebuilder. Even tried on a different computer, which had never had the program on it before. To see if it's the computer or the OS. Both are two different OS's. I just tried to process a Blu-Ray that previously worked fine, since I knew it was okay before. I did it both Folder and ISO. But now the same result. Please help.

[10/17/16] BD Rebuilder v0.50.18
[12:16:38] Source: LONDONHASFALLEN_NA_00800
- Input BD size: 28.75 GB
- Approximate total content: [01:38:41.916]
- Target BD size: 7.84 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: High Quality (Default), ABR
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[12:16:39] PHASE ONE, Encoding
- [12:16:39] Processing: VID_00800 (1 of 1)
- [12:16:39] Extracting A/V streams [VID_00800]
- Error in attempt to extract audio/subs.
- Not enought buffer for parse video stream. Current frame num 919
[12:16:47] - Failed to retrieve audio, aborted
[10/17/16] Checking System Settings
- BD-Rebuilder v0.50.18
- Windows Version: 6.2 [9200]
- Working Path Free Space: 278.71GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[10/17/16] Systems Settings Check complete

[gonca]

Not enought buffer for parse video stream. Current frame num 919
Corrupt source?

[raisingcanex]

Corrupt source?

Please excuse my lack of knowledge. Can You please explain and what I can check or try. I tried multiple titles. I also tried another title while I was waiting on a reply and got the buffering in that one two. Before these two (as you can see in previous post from last week), I did not receive that error. Which is the first time I have seen that error. Before it would be Sometimes failed to receive video or Sometimes to retrieve audio (October 6th) with nothing about buffering. You can see that on my post on October 10th (just one of my post) it says failed to re encode. And nothing about buffering. All with different titles that I purchased.

[jdobbs]

Please excuse my lack of knowledge. Can You please explain and what I can check or try. I tried multiple titles. I also tried another title while I was waiting on a reply and got the buffering in that one two. Before these two (as you can see in previous post from last week), I did not receive that error. Which is the first time I have seen that error. Before it would be Sometimes failed to receive video or Sometimes to retrieve audio (October 6th) with nothing about buffering. You can see that on my post on October 10th (just one of my post) it says failed to re encode. And nothing about buffering. All with different titles that I purchased.Somethings wrong... that error comes from TSMUXER.

Are you positive the version of TSMUXER in the TOOLS folder hasn't changed? That is an error that I remember happening on some older versions of TSMUXER, but I haven't seen it in a long time.

[raisingcanex]

Somethings wrong... that error comes from TSMUXER.

Are you positive the version of TSMUXER in the TOOLS folder hasn't changed? That is an error that I remember happening on some older versions of TSMUXER, but I haven't seen it in a long time.

I haven't changed anything after the unzipped file. How can I check to see what version of TSMUXER is present and what should it be?

[Sharc]

I haven't changed anything after the unzipped file. How can I check to see what version of TSMUXER is present and what should it be?
Does it work when you unselect subtitles and/or change audio tracks (languages) in the Setup menu?

[gonca]

Please excuse my lack of knowledge. Can You please explain and what I can check or try. I tried multiple titles. I also tried another title while I was waiting on a reply and got the buffering in that one two. Before these two (as you can see in previous post from last week), I did not receive that error. Which is the first time I have seen that error. Before it would be Sometimes failed to receive video or Sometimes to retrieve audio (October 6th) with nothing about buffering. You can see that on my post on October 10th (just one of my post) it says failed to re encode. And nothing about buffering. All with different titles that I purchased.

You can try eac3to with one of its GUIs to demux the streams.
See if it lists any errors
Please note that it must be a decrypted source

[raisingcanex]

You can try eac3to with one of its GUIs to demux the streams.
See if it lists any errors
Please note that it must be a decrypted source

What is eac3to and where do I get it?

[gonca]

http://www.videohelp.com/software/eac3to

[Lathe]

Hey JD, I was trying to play around with Avisynth lately, and it appears that MANY of the plugins require version 2.8 according to the Wiki. I think for BDRB you require the version on page one of this thread, right? Isn't that like 2.6? Is there ANY way I can run 2.8 so that I can use a lot of these plugins that don't seem to work with 2.6?

I tried like 6 different degrainers / denoisers and none of them worked.

Thanks!

[Sharc]

Hey JD, I was trying to play around with Avisynth lately, and it appears that MANY of the plugins require version 2.8 according to the Wiki. .......

Avisynth 2.8? You mean Avisynth 2.5.8?

[jdobbs]

The latest official release of AVISYNTH is 2.60.

[MrVideo]

I have 2.5.8 installed on my system. It has been working great for me, so I haven't installed 2.6. If I ever run into a situation where I use a plugin that only works with 2.6, or later, then maybe I'll upgrade.

But, this discussion had me look at the BD-RB install area and I've noticed that the tons of DLL files that come with AVISynth are not there. Any particular reason for that?

It seems that BD-RB's 2.6 version is not conflicting with my 2.5.8 version. How is that possible? I've never looked into what exactly gets installed when the AVISynth package is installed.

Color me curious.

[jdobbs]

The v2.60 version referenced in the first post of this thread is the same as you'd download from anywhere else with no modifications. If you installed it, it should override any previous installations. There isn't a "BD-RB's 2.6 version". I just put it on my server for download so it is always available.

If you want to see what version is actually being used on your system, just create an AVS file that contains:

version()

Then open it with Media Player Classic. It will display the version that is in use.

[MrVideo]

Thanks for the memory refresh. Brain fart. I didn't install 2.6 as I will not be doing anything with BD-RB that will require the use of AVISynth, since all I am doing is creating discs with imported video files. Straight re-encoding doesn't appear to require it either, as BD-RB hasn't complained when it did do re-encodes.

Lathe, AVISynth can do a boatload of stuff. I haven't even scratched the surface with what I have done with it. It is THE tool for doing IVTC. There are two kinds of 23.976 -> 29.97 conversions. The most common that the industry uses is 2:3 pulldown. The other is repeat frame, whereby every 4th frame is repeated twice in the output. If you were able to watch Canadian TV, you'll find a lot of the Warner Bros. product being sat fed to Canada that way. AVISynth has a great tool for dropping said frame. The only gotchya is that the pattern has to be consistant throughout the video. So, if you record a show from OTA, you would have to edit it so that the pattern is consistent. I've done lots of other things, so have fun playing around with it.

BTW, I do not use MPC. Only VLC.

[Lathe]

Thanks for the memory refresh. Brain fart. I didn't install 2.6 as I will not be doing anything with BD-RB that will require the use of AVISynth, since all I am doing is creating discs with imported video files. Straight re-encoding doesn't appear to require it either, as BD-RB hasn't complained when it did do re-encodes.

Lathe, AVISynth can do a boatload of stuff. I haven't even scratched the surface with what I have done with it. It is THE tool for doing IVTC. There are two kinds of 23.976 -> 29.97 conversions. The most common that the industry uses is 2:3 pulldown. The other is repeat frame, whereby every 4th frame is repeated twice in the output. If you were able to watch Canadian TV, you'll find a lot of the Warner Bros. product being sat fed to Canada that way. AVISynth has a great tool for dropping said frame. The only gotchya is that the pattern has to be consistant throughout the video. So, if you record a show from OTA, you would have to edit it so that the pattern is consistent. I've done lots of other things, so have fun playing around with it.

BTW, I do not use MPC. Only VLC.

Heh, 2.58, NOT 2.8... yeah, I am indeed an idiot... GEEZ... :o

Thanks guys; another nice fellow on Doom9 reminded me of that, so my 'reputation', such as it is, is thrillingly spreading far and wide... :cool:

Anyway... YES my good friend, you are quite right! I am trying to learn to use Avisynth and it can do a HELL of a lot of stuff. I just dumped in a bunch of Dlls into my plugins directory. Now, if I can just make the damn things work!

Like you were saying (and MAN do I wish I had your understanding of the 'pulldowns' Inverse Telecine', etc. I don't have a bloody clue!) But, I will keep reading until either I learn, go blind, or go sterile...

Cheers!

[Lathe]

Ah, I just had to come here and laud the praises of both Sharc and JD!

I took Sharc's suggestion and ran my old movie capture clip through BDRB using the inverse telecine script in the ini (I STILL don't really understand what that does...) and I set it to make the movie 1280x720, and WOW! Damn does it look better!

Thank you Sharc! I think you just made up for all the times you've p*ssed me off! :D

So, JD... I think yet another sacrificial altar for Virgins is in order in your honour in my backyard (well, they might not actually still be virgins by the time they get to the altar, but...)

[bfrqrv]

Hello,

I hope someone can help me with this one. I don't think its very difficult but I can't find the reason for quiet a few days now.
I try to explain what I do.

I extract 3D iso files to BDMV
After thata I give it to BD Rebuilder, and most of the times it is perfect. But sometimes I get this error. Its strange because sometimes I can do the same iso with succes. I mean the very same iso that was wrong yesterday. I show you the log. It looks like some files are occupied but I close all the program's that can interfere.

10-19-16] BD Rebuilder v0.50.18
[15:32:18] Source: 80GB
- Input BD size: 45,74 GB
- Approximate total content: [03:44:16.567]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Very Fast), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[15:32:18] PHASE ONE, Encoding
- [15:32:18] Processing: VID_00469 (1 of 22)
- [15:32:18] Extracting A/V streams [VID_00469]
- [15:32:45] Reencoding video [VID_00469]
- [15:32:45] Keeping original video (no reencode)
- [15:32:45] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [15:32:46] Multiplexing M2TS
- [15:33:13] Processing: VID_00473 (2 of 22)
- [15:33:13] Extracting A/V streams [VID_00473]
- [15:33:23] Reencoding video [VID_00473]
- [15:33:23] Keeping original video (no reencode)
- [15:33:23] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [15:33:23] Multiplexing M2TS
- [15:33:32] Processing: VID_00474 (3 of 22)
- [15:33:32] Extracting A/V streams [VID_00474]
- [15:49:01] Reencoding video [VID_00474]
- [15:49:01] Keeping original video (no reencode)
- [15:49:01] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [15:49:01] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00474.meta
- Can't open file: F:\REMUXED\WORKFILES\00475.track_4114.mvc
[15:49:04] - Failed to build structure, aborted

I like this program so much that I must find the reason why this is happening.

[Ch3vr0n]

You don't extract 3D iso's. Doing that risks corrupting the file structure and make it twice the iso size. Which is exactly what happened.

[15:32:18] Source: 80GB
- Input BD size: 45,74 GB

You MOUNT the 3D iso in something like Virtual Clone Drive, and point the BDRB to the virtual drive.

[bfrqrv]

You don't extract 3D iso's. Doing that risks corrupting the file structure and make it twice the iso size. Which is exactly what happened.



You MOUNT the 3D iso in something like Virtual Clone Drive, and point the BDRB to the virtual drive.

Almost good but not totally right I think. I extract the iso and I call the map 80GB because I knwo the ISO will expand when you do that with 3d ISO. But the structure isnt ruined that way. And like I said sometimes the same movie with the same routing (extract) is not giving the error. So there must be another factor. I extract with winrar, windows, poweriso, thats not the issue. I think the file is occupied, but can someone confirm that looking at the error?

ps. I forgot telling you why I extract. I insert a subtitle file after the bdmv is made. There is no other way to to that then first extract. after that I have the good working movie with my subs, but I want it to be smaller again like 50GB or 25 GB. That is working but not each time with exact the same movie and procedure.

[Ch3vr0n]

There is another way. When the stream is demuxed, you abort the encode before remuxing is done and replace the stream. Either way you don't extract a 3d ssif structure to folders. A 45gb iso can easily grid to 1.5 or twice the size.

It's up to you.

[jdobbs]

All I can tell you is that it looks like F:\REMUXED\WORKFILES\00475.track_4114.mvc doesn't exist when BD-RB tries to remux.

[bfrqrv]

All I can tell you is that it looks like F:\REMUXED\WORKFILES\00475.track_4114.mvc doesn't exist when BD-RB tries to remux.

I must replace more then only the stream when I want to do the trick for a full menu bluray. But thx Ch3vr0n.

The analyse of jdobbs is almost equeal as mine conclusion. I think it does exists but has a rights issue or that the file is occupied. I try to restart the system before I give it to BD Rebuilder and hope it will work.

[MrVideo]

Heh, 2.58, NOT 2.8... yeah, I am indeed an idiot... GEEZ... :o
2.5.8, not 2.58. :D
Like you were saying (and MAN do I wish I had your understanding of the 'pulldowns' Inverse Telecine', etc. I don't have a bloody clue!) But, I will keep reading until either I learn, go blind, or go sterile...

Read the wiki info on pulldown (https://en.wikipedia.org/wiki/Three-two_pull_down).

IVTC is the method by which the four original frames are extracted from the five frames in order to get back to 23.976. The exact method by which the AVISynth plugin does that is beyond the scope of this forum.

[MrVideo]

I took Sharc's suggestion and ran my old movie capture clip through BDRB using the inverse telecine script in the ini (I STILL don't really understand what that does...) and I set it to make the movie 1280x720, and WOW! Damn does it look better!

Yes, 23.976 playback looks better than 2:3 pulldown 29.97 playback. There is always that "judder" with the 29.97 video. Wasn't as bad when displayed on old interlaced analog TVs. With digital display, not so much. Hence the reason I convert all 29.97 pulldown video back to 23.976 before watching it.

BTW here is the code segment that does the work:
assumetff()
telecide(guide=0)
decimate()

Jdobbs should be doing something along those lines.

[jdobbs]

Jdobbs should be doing something along those lines.BD-RB already does. Look at SETUP. You can also choose between iVTC with DECOMB (telecide/decimate) or TIVTC. You can also force inverse telecining on hard-telecined sources.

[Lathe]

2.5.8, not 2.58. :D

I'm really gonna hafta hurt ya man.. :devil:


Read the wiki info on pulldown (https://en.wikipedia.org/wiki/Three-two_pull_down).

IVTC is the method by which the four original frames are extracted from the five frames in order to get back to 23.976. The exact method by which the AVISynth plugin does that is beyond the scope of this forum.

Yes, I'm going to read more about that, but I'm STARTING to get the general idea, thanks.

Yes JD, this is the script BDRB used and you can be dang sure I copied it and put it in my AV encoding folder!

LoadPlugin("D:\EXECUTABLES\BD-RBV05018\BD_Rebuilder\tools\decomb521.dll")
ConvertToYV12()
Telecide(order=1,guide=1)
Decimate(cycle=5)
Spline16Resize(960,720).Addborders(160,0,160,0)
ConvertToYV12().AssumeFPS(24000,1001)

[MrVideo]

Like I said, it is something that you should be doing and you are.
You can also force inverse telecining on hard-telecined sources.
Wouldn't you want to do that anyway? I do. The playback results are visually so much better.

Every scripted TV show that is broadcast is sourced from 23.976 edited material and broadcast hard coded. The only exception that I have found (I'm sure there are others) are that shows like Game of Thrones on HBO, which are sent out soft telecined. But, editing programs like VideoReDo use those flags, which results in the edited output being 29.97 with hard telecine. I do not think I've ever recoded video that was soft telecined. All my videos go thru VideoReDo, so I've never had any weird results with recoding.

[Lathe]

Quote:
Originally Posted by jdobbs

You can also force inverse telecining on hard-telecined sources.




Wouldn't you want to do that anyway? I do. The playback results are visually so much better.

Every scripted TV show that is broadcast is sourced from 23.976 edited material and broadcast hard coded. The only exception that I have found (I'm sure there are others) are that shows like Game of Thrones on HBO, which are sent out soft telecined. But, editing programs like VideoReDo use those flags, which results in the edited output being 29.97 with hard telecine. I do not think I've ever recoded video that was soft telecined. All my videos go thru VideoReDo, so I've never had any weird results with recoding.

Very interesting and good to know, since the prints that I do have where I have to do all this stuff are indeed captured broadcasts in most cases, so it would be good to know what to do with those to improve them. Of course most of my movie collection (over 7500 films now) are concentrated with Blu-rays and when necessary DVDs. But, I have a small number of very rare and commercially unavailable films, and these are the ones that I am trying to concentrate on now and learn about Avisynth.

Well, not to take up too much space here on this thread, but that is definitely one of the things I need to read about because I have NO idea what 'hard telecining' is...

But, I will go and look it up now :)

[jdobbs]

Like I said, it is something that you should be doing and you are.

Wouldn't you want to do that anyway? I do. The playback results are visually so much better.

Every scripted TV show that is broadcast is sourced from 23.976 edited material and broadcast hard coded. The only exception that I have found (I'm sure there are others) are that shows like Game of Thrones on HBO, which are sent out soft telecined. But, editing programs like VideoReDo use those flags, which results in the edited output being 29.97 with hard telecine. I do not think I've ever recoded video that was soft telecined. All my videos go thru VideoReDo, so I've never had any weird results with recoding.You have to be careful because the Blu-Ray standard doesn't include 720x480/576 @ 23.976 for primary video -- so to strictly meet the standard you have to include the telecining. With that said, though, I have yet to see a player that won't play it.

Never reencoded soft telecining? That includes about 99% of all movies encoded at 720x480/576 (DVD). Telecining on HD is rare -- except maybe on video captures. I'm not sure I've ever seen it on BD sources.

[Lathe]

You have to be careful because the Blu-Ray standard doesn't include 720x480/576 @ 23.976 for primary video -- so to strictly meet the standard you have to include the telecining. With that said, though, I have yet to see a player that won't play it.

Never reencoded soft telecining? That includes about 99% of all movies encoded at 720x480/576 (DVD). Telecining on HD is rare -- except maybe on video captures. I'm not sure I've ever seen it on BD sources.

That's good to keep in mind, thanks JD. I don't quite have a handle on all this telecining yet, but from what I've heard / read so far, and what you just said, it sounds like standard DVDs (NTSC I'm guessing) from what I've seen in MediaInfo from their rips, look like they are at a 29.xxx frame rate, which I'm GUESSING the telecining has something to do with being at that frame rate and still being progressive. So, now that I know that the telecine thing is mainly related to DVDs (their captures and rips) that helps me see where it needs to be applied.

[MrVideo]

You have to be careful because the Blu-Ray standard doesn't include 720x480/576 @ 23.976 for primary video -- so to strictly meet the standard you have to include the telecining. With that said, though, I have yet to see a player that won't play it.
That is because today's Blu-ray players will play all sorts of input wrapper types and frame rates. Since the hardware will already do it, it doesn't care if the source is even Blu-rays. Probably easier to just let it play it than it is to restrict it from playing, just because it isn't in the Blu-ray standard.
Never reencoded soft telecining? That includes about 99% of all movies encoded at 720x480/576 (DVD). Telecining on HD is rare -- except maybe on video captures. I'm not sure I've ever seen it on BD sources.
I've never had any reason to take DVD video and recode for H.264. Nothing to gain from doing so. If I pull anything from DVD, it goes thru VRD, so any telecine flagging is honored.

It turns out that the Blu-ray standard does contain the ability to have 2:3 pulldown instructions for 720 and 1080 23.976 source material for 29.97 playback, depending on the connection and display type. I've certainly never seen VRD indicate that it has ever come across said material. Considering that the analog sunset clause has come about, new Blu-ray players can only have HDMI output connectors, meaning that displays have to honor 23.976 HD video.

I'm more pissed at the FCC for not shifting the audio subcarrier when color was defined, in order to keep true 30 frames/sec display rates. Where is that time machine when you really need it? :D

[MrVideo]

I don't quite have a handle on all this telecining yet, but from what I've heard / read so far, and what you just said, it sounds like standard DVDs (NTSC I'm guessing) from what I've seen in MediaInfo from their rips, look like they are at a 29.xxx frame rate, which I'm GUESSING the telecining has something to do with being at that frame rate and still being progressive.
You can't have 2:3 pulldown video and still be progressive @ 29.97 frames/sec. 2:3 pulldown @ 29.97 frames/sec requires interlaced video @ 59.94 fields/sec.

29.97p broadcast doesn't exist. Nor does 29.97p exist for Blu-ray.

[Lathe]

So, if I may please, just let me ask one thing about this...

Here are the specs basically for most of the files I will be dealing with. They are mostly captured to dvd on the fly I believe:

Video
ID : 1
ID in the original source medium : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@Main
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : M=3, N=15
Format settings, picture structure : Frame
Codec ID : V_MPEG2
Codec ID/Info : MPEG 1 or 2 Video
Duration : 1 h 14 min
Bit rate mode : Variable
Bit rate : 4 810 kb/s
Maximum bit rate : 9 200 kb/s
Width : 720 pixels
Height : 480 pixels
Display aspect ratio : 4:3
Frame rate mode : Constant
Frame rate : 29.970 (30000/1001) FPS
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.464
Time code of first frame : 00:00:18;00
Time code source : Group of pictures header
GOP, Open/Closed : Open
Stream size : 2.49 GiB (95%)
Language : English
Default : No
Forced : No

So, without all the technical stuff in the last few posts here, can you please just tell me what I should do first. I DO (I think...) want to convert them into a progressive format. I can see here that these are indeed interlaced like you said in the last post.

Do I do what Sharc suggested for the other file? Do I just import the MKV into BDRB and let it do it's inverse telecine thing like I posted before and have BDRB convert it to 1280x720 like the other file that came out so nice. That is the final format that I want these in, so that they ARE indeed Blu-ray complaint and will play normally like any other disc. I do NOT want to mess around with software players, etc. like you were talking about. I just want to end up with a nice, normal, Blu-ray complaint file. Is that what I should do then to get the file into a nice, 23.xxx progressive format so that I can get rid of all the combing, etc or whatever when it's interlaced? Then won't it be easier if I simply want to either manipulate it further using Avisynth, or just simply burn it to disc and play it on my OPPO?

Please, keep it simple... I haven't really understood all the technical complexity you guys have been talking about (yet...)

[MrVideo]

OK, I'll try and keep it within the idea of KISS.

I suspect that you are saying that these DVDs were done using a DVD recorder with the source being a TV/Cable/DBS channel. As such, you cannot tell from MediaInfo if the 29.97 video is pure video (for example from a live televised event) or contains 2:3 pulldown video. You have to physically look at the content to determine what the video format is.

Based upon the source, here are my suggestions.

1) 23.976 source to 29.97 via 2:3 pulldown (most TV scripted programming):
Do not de-interlace the material first, in order to convert it to progressive. That will totally wipe out the ability to IVTC it. Have BD-RB IVTC the input and upconvert to 720p. The normal process in AVISynth is to IVTC it first and then pass the video stream to the upconversion plugin. The end result should be a 720p that has pillar bars so the the 4:3 aspect ratio is kept.

If the source video is letterboxed, before upconversion to 720p, the 720x480 should be cropped to 720x360, so that the video will fill the 720p 16:9 frame. Otherwise you will end up with the video inside of a black box. I do not know if Jdobbs has that option available.

2) 29.97 pure video source:
There are a couple of ways to attack this, since you want 720p video, which can only be 59.94 fps and be compliant. If you deinterlace first, each resulting frame will have to be repeated in order to be 59.94 fps. Easily accomplished. But (here is where I get a little technical), deinterlacing reduces the time spacial information in half. By this I mean that with interlaced video, objects appear to move at 59.94 times a second. If you deinterlace, the objects can only move at 29.97 times a second. If you do not deinterlace, you can have the conversion program create a 720p frame from the 240 line field via interpolation. By doing that, you keep the time spatial information. I do not know what capabilities have been built into BD-RB.

It is a trade-off between deinterlacing interpolation of the two fields into a single field, or the interpolation of a single field into a single frame. I have no personal idea which is better visually, as I've never done it. I just let the TV/monitor up convert 480i video to 1080p for displaying.

A third option is to keep the 480i pure video as MPEG-2 video and burn that to the Blu-ray and let the display device handle it.

[Lathe]

OK, I'll try and keep it within the idea of KISS.

I suspect that you are saying that these DVDs were done using a DVD recorder with the source being a TV/Cable/DBS channel. As such, you cannot tell from MediaInfo if the 29.97 video is pure video (for example from a live televised event) or contains 2:3 pulldown video. You have to physically look at the content to determine what the video format is.

Based upon the source, here are my suggestions.

1) 23.976 source to 29.97 via 2:3 pulldown (most TV scripted programming):
Do not de-interlace the material first, in order to convert it to progressive. That will totally wipe out the ability to IVTC it. Have BD-RB IVTC the input and upconvert to 720p. The normal process in AVISynth is to IVTC it first and then pass the video stream to the upconversion plugin. The end result should be a 720p that has pillar bars so the the 4:3 aspect ratio is kept.

If the source video is letterboxed, before upconversion to 720p, the 720x480 should be cropped to 720x360, so that the video will fill the 720p 16:9 frame. Otherwise you will end up with the video inside of a black box. I do not know if Jdobbs has that option available.

2) 29.97 pure video source:
There are a couple of ways to attack this, since you want 720p video, which can only be 59.94 fps and be compliant. If you deinterlace first, each resulting frame will have to be repeated in order to be 59.94 fps. Easily accomplished. But (here is where I get a little technical), deinterlacing reduces the time spacial information in half. By this I mean that with interlaced video, objects appear to move at 59.94 times a second. If you deinterlace, the objects can only move at 29.97 times a second. If you do not deinterlace, you can have the conversion program create a 720p frame from the 240 line field via interpolation. By doing that, you keep the time spatial information. I do not know what capabilities have been built into BD-RB.

It is a trade-off between deinterlacing interpolation of the two fields into a single field, or the interpolation of a single field into a single frame. I have no personal idea which is better visually, as I've never done it. I just let the TV/monitor up convert 480i video to 1080p for displaying.

A third option is to keep the 480i pure video as MPEG-2 video and burn that to the Blu-ray and let the display device handle it.

Yes, thank you. I believe that I got most of that. All of the files I will be working with are movies, films, only. So, it SEEMS like your number 1 is the way to go. From the reading that I've done in the meantime, it looks like basically most NTSC DVDs are going to be this way whether a captured movie or whatever, since in all the cases that I have they have all been placed into DVD format (ISO's) So, I use MakeMKV first to create an MKV file from the ISO. I'm guessing that in just about all cases, I would likely want to use BDRB to do what you said. I guess I can always look at the result and see how it looks :)

Thanks again for taking the time to explain this!

[Sharc]

Hard-telecined stuff:
The source which Lathe uploaded in his other thread (http://forum.doom9.org/showthread.php?p=1782994#post1782994) was 2:3 hard-telecined (no pulldown flags). You can only say this by manually analyzing the stream; media info will always report such streams as interlaced which often misleads people (and tools) to blindly apply deinterlacers to hard telecined footage (why should they suspect something else....).
When you set IVTC_SELECTION=1 in the .ini, BD-RB lets you choose as dropdown menu (right click on the stream) to force IVTC on "interlaced" (in fact hard-telecined) streams. So when you are positive that the stream is in fact hard-telecined you can IVTC it; just don't apply IVTC to true interlaced content!

One still finds hard-telecined stuff as bonus material (extras) on BD's because the studios are sometimes lazy and take these from previous DVD releases, or compile hybrids of true interlaced video with telecined film .... lot from DVD-NTSC heritage.

True-interlaced:
A true interlaced 29.97i video can always be bobbed to 1280x720p@59.94fps in order to preserve the original time resolution and stay Blu-ray compliant. Bobbing instead of deinterlacing has its own cons, but QTGMC is an outstanding bobber in many respects (I prefer it over frame interpolation) -- and also use it sometimes to clean up IVTC-ed progressive material.

[MrVideo]

Bobbing instead of deinterlacing has its own cons, but QTGMC is an outstanding bobber in many respects.
Wow, I haven't heard that plugin name in a while. It is very slow, but indeed does a great job. I haven't used it in ages.

[jdobbs]

I actually prefer TIVTC to Telecide/Decimate for most sources (not all though). If I'm performing iVTC I usually try each and pick the one I think gives the clearer/stabler result. That's the reason I added both to BD-RB.

[Sharc]

I actually prefer TIVTC to Telecide/Decimate for most sources (not all though).
Ahh...., that's why you set IVTC_METHOD=1 per default.

[MrVideo]

I'm going to do a bunch of encodes using the following TFM settings:
tfm(order=1,mode=0,slow=2,display=false)
Yes, I know that the default for display is false. I have it there as a placeholder. If I spot some frames that do not look right, I can quickly change the false to true and rerun the job and look at the embedded info.

Jdobbs, What are the situations whereby you won't use TFM?

[Lathe]

Hard-telecined stuff:
The source which Lathe uploaded in his other thread (http://forum.doom9.org/showthread.php?p=1782994#post1782994) was 2:3 hard-telecined (no pulldown flags). You can only say this by manually analyzing the stream; media info will always report such streams as interlaced which often misleads people (and tools) to blindly apply deinterlacers to hard telecined footage (why should they suspect something else....).
When you set IVTC_SELECTION=1 in the .ini, BD-RB lets you choose as dropdown menu (right click on the stream) to force IVTC on "interlaced" (in fact hard-telecined) streams. So when you are positive that the stream is in fact hard-telecined you can IVTC it; just don't apply IVTC to true interlaced content!

One still finds hard-telecined stuff as bonus material (extras) on BD's because the studios are sometimes lazy and take these from previous DVD releases, or compile hybrids of true interlaced video with telecined film .... lot from DVD-NTSC heritage.

True-interlaced:
A true interlaced 29.97i video can always be bobbed to 1280x720p@59.94fps in order to preserve the original time resolution and stay Blu-ray compliant. Bobbing instead of deinterlacing has its own cons, but QTGMC is an outstanding bobber in many respects (I prefer it over frame interpolation) -- and also use it sometimes to clean up IVTC-ed progressive material.

There is a lot to this... This is very vital information, because I'm pretty sure that on one of the very first ones I tried some script on, I had assumed that it was interlaced because MediaInfo said it was, so I used BDRB decomb/blend filter. It came out 'okay', but I'm pretty sure now that it likely was as you say, hard telecined. I did 2 like that. One didn't turn out too bad (colour 'AND HOPE TO DIE') One looks pretty rough (B&W 'I ACCUSE')

I THINK that pretty much all of the films I will be trying to 'improve' are from DVD captures; So, I'm guessing that most of them will likely fall into this same category. It there a way visually to 'step through' a file frame by frame to observe whether every frame is 'combed' or interlaced looking, or if it has (if I've read correctly about telecined stuff) 3 good looking frames, and then 2 that look interlaced (or the other way around :) ) Right...?
This is VERY good to know...

[Lathe]

Just a quickie...

I tried putting a preset in as a Tweak, but it looks like BDRB ignored it. Are you not able to put an x264 preset as a Tweak?

[MrVideo]

It there a way visually to 'step through' a file frame by frame to observe whether every frame is 'combed' or interlaced looking, or if it has (if I've read correctly about telecined stuff) 3 good looking frames, and then 2 that look interlaced
You will need a program that will let you step through the file, a frame at a time and not de-interlace.. For that I use my video editing program. VLC will not let you do that. You can get it to slow down playback. But, I think VLC de-interlaces, so that doesn't help.

[jdobbs]

Just a quickie...

I tried putting a preset in as a Tweak, but it looks like BDRB ignored it. Are you not able to put an x264 preset as a Tweak?There are some tweaks that BD-RB doesn't allow -- for example, anything that would change the framerate.

You can step through a video a frame at a time with Media Player Classic (MPC) -- it is included in the BD-RB tools folder (mplayerc.exe).

[Lathe]

There are some tweaks that BD-RB doesn't allow -- for example, anything that would change the framerate.

You can step through a video a frame at a time with Media Player Classic (MPC) -- it is included in the BD-RB tools folder (mplayerc.exe).

Ah, good to know, thanks!

Thanks too, Mr. Video. Yeah, VLC will allow you to set up whether interlace is active / automatic / off and which type. But, you are right, you cannot step through a file frame by frame. I'll use MPC then and give it a try.

[Lathe]

Um... any other thought as to the 2 pass size fluctuation with BD25? Seems with LAVF it used to almost always come out to 22.95 or so. Now, it appears to be smaller a lot of the time, like around 21 Gigs.

[Sharc]

..... It there a way visually to 'step through' a file frame by frame to observe whether every frame is 'combed' or interlaced looking, or if it has (if I've read correctly about telecined stuff) 3 good looking frames, and then 2 that look interlaced (or the other way around .......
I am normally using AvsPmod (http://forum.doom9.org/showthread.php?p=1381211#post1381211)for this purpose. It's a very handy tool for trying out scripts and see the result immediately.

[Sharc]

@jdobbs
A question in the context of the IVTC discussion:
When incuding AVS scripts (Setup menu: "Use AVS filters during encoding") AND forcing IVTC, the custom filters are inserted before the IVTC in the final script, means the custom filters are applied to the telecined material.
Is there a way in BD-RB to swap the order, i.e. IVTC before the custom AVS filters? Or should the order be swapped automatically when forcing IVTC?

Edit:
I found the solution. One has to set the prefix r: in front of the custom filter. This puts the custom filter after the IVTC in the sequence.
(Question is perhaps still whether this swapping could/should be done automatically in this case).

[jdobbs]

Um... any other thought as to the 2 pass size fluctuation with BD25? Seems with LAVF it used to almost always come out to 22.95 or so. Now, it appears to be smaller a lot of the time, like around 21 Gigs.It really shouldn't matter. The specified bitrate is that same whether you use LAVF or any of the other frame-serving methods.

[gonca]

I am seeing references to prefixes for the AVS Editor
I knew they existed but I an seeing different prefixes mentioned that I am not familiar with; i.e. r:
I have used search and cannot find a list of all the allowed prefixes.
Is there such a list?

[jdobbs]

July 8th, 2010
- Added an AVS filter editor to the SETUP dialog. This
will allow you to add AVS filters to files. Note that
bug reports WILL NOT BE ACCEPTED when filters are in
use (as errors are almost always caused by the filter
usage). You can add "E:", "F:", "I:", or "P:" as a
prefix to a line added in the filter editor. The
prefixes represent "Extras", "Feature", "Interlaced",
and "Progressive" respectively. When specified, the
prefix will limit that filter to usage only when the
source to be encoded matches the prefix. For example,
if specifying "E:filter1()" the filter "filter1()"
would only be applied to segments that are determined
to be extras. Setting "e:i:filter2()" limits use of
"filter2()" to segments that are extras -- and are
also interlaced.
November 28th, 2011
- Added a new prefix for filter editing. By adding
the "r:" prefix, BD-RB will add the specified
filter after the resizing stage (rather than the
default of before). Note: If using more than one
prefix, the "r:" must be the last in the series. Also:

"a:" filter applies to the audio AVS
"m:" filter applies only to menus

Notes:

1. You can use either Upper or Lower case in the filter prefixes, it doesn't matter...
2. On a series disc, where there are multiple episodes -- don't use "F:" because it will only apply to the largest episode

[gonca]

Thank you

[Sharc]

@jdobbs
When I select "Use Deinterlacer on interlaced sources" (for an imported source), and set in the .ini
DEINTERLACER_TYPE=1
DB-RB aborts.

I assume it's due a script syntax error:
#Created by BD Rebuilder - v0.50.18
LoadPlugin("C:\Program Files Video\DGdecNV\DGDecodeNV.dll")
DGSource("C:\TEMP\BD REBUILDER\WORKFILES\VID_00000.DGI", fieldop=0)
ConvertToYV12()
LoadPlugin("C:\Program Files Video\BD_Rebuilder\tools\decomb521.dll")
FieldDeinterlace(blend=false,+blend=false)
ConvertToYV12().AssumeFPS(30000,1001)
The script is ok for the other DEINTERLACER_TYPE=n

[jdobbs]

@jdobbs
When I select "Use Deinterlacer on interlaced sources" (for an imported source), and set in the .ini
DEINTERLACE_TYPE=1
DB-RB aborts.

I assume it's due a script syntax error:
#Created by BD Rebuilder - v0.50.18
LoadPlugin("C:\Program Files Video\DGdecNV\DGDecodeNV.dll")
DGSource("C:\TEMP\BD REBUILDER\WORKFILES\VID_00000.DGI", fieldop=0)
ConvertToYV12()
LoadPlugin("C:\Program Files Video\BD_Rebuilder\tools\decomb521.dll")
FieldDeinterlace(blend=false,+blend=false)
ConvertToYV12().AssumeFPS(30000,1001)
The script is ok for the other DEINTERLACE_TYPE=nThat sure doesn't look right, does it? I'll look at it later today.

[Edit] Yep. I screwed the pooch on that one when I made the change. It has been fixed for the next release.

[geheim]

Any news about 3D subtitle depth??
I still loose all depth in my 3D subtitles after encoding with FRIM...

@jdobbs Could you take a look at MVCEnc from BDtoAVCHD?? Because this tool keeps 3D offsets intact after encoding. However, it cannot keep any menus, therefore I prefer using BDRebuilder.
But without 3d subtitle depth many movies don't give a pleasant view with subtitles "cutting" across picture elements...

I'd really appreciate it if you could figure out why BDtoAVCHD keeps offsets intact and BDRebuilder doesn't. I'd be very pleased if you could add an option to select a fixed offset value, no need for the original depth offsets to be kept if that is too diffcult to implement. But any depth at all would be really good for a loads of movies.

Thanks so much!!

[Lathe]

I am normally using AvsPmod (http://forum.doom9.org/showthread.php?p=1381211#post1381211)for this purpose. It's a very handy tool for trying out scripts and see the result immediately.

Yes, thanks, I do have that but I've not tried it out yet.

BTW, I'm glad you mentioned about AVS script running BEFORE the IVTC! I did not know this because sometimes I want to add filters, but I want to do it AFTER the IVTC is done. Hmmm...

So what is with the 'r'? Where exactly do you put it. Say I wanted to use Sharpen(.3), where would I put the 'r'? Would I enter the text in the Avisynth code area of BDRB like this: 'r Sharpen(.3)'...?

Oh, also, would I need to add an 'r' before each line of script?

[Sharc]

See changes.txt, and a few posts before:
http://forum.doom9.org/showpost.php?p=1783559&postcount=25096

r:Sharpen(0.15)

[Lathe]

See changes.txt, and a few posts before:
http://forum.doom9.org/showpost.php?p=1783559&postcount=25096

r:Sharpen(0.15)

Yeah, I know Bro, but I'm afraid that was to confusing to me. Besides it just said add the 'letter'; it didn't show the exact syntax, or if it did I didn't see it.

So, thanks for not just throwing me the link that I just saw anyway 2 posts ago, but I appreciate you actually including the line of script so I could see how it looks.

I STILL don't know whether I have to add the 'r' to EACH line of code though... So, do I do it like this:

r:Sharpen()
r:deen()
r:Crop()

etc...?

[Sharc]

How about making few quick tests yourself ???
Use one of your short mkv and see what you get in BD-RBs scripts. It takes you few minutes, often faster than posting back and forth.

[jdobbs]

Yeah, I know Bro, but I'm afraid that was to confusing to me. Besides it just said add the 'letter'; it didn't show the exact syntax, or if it did I didn't see it.

So, thanks for not just throwing me the link that I just saw anyway 2 posts ago, but I appreciate you actually including the line of script so I could see how it looks.

I STILL don't know whether I have to add the 'r' to EACH line of code though... So, do I do it like this:

r:Sharpen()
r:deen()
r:Crop()

etc...?You add the prefix to any line to want to clarify -- so you may have one line with an "r:" prefix, another with a "i:r:" prefix, and another with none. The "r:" would be included with any line to which you want it to apply. "r:" just moves where the filter is placed in the AVS file. The fact that they are called prefixes means they go before the filter. But, of course, English isn't everyone's first language -- so I guess I could have made that clearer.

[MrVideo]

BTW, I'm glad you mentioned about AVS script running BEFORE the IVTC! I did not know this because sometimes I want to add filters, but I want to do it AFTER the IVTC is done.
Technically the IVTC procedure is part of the AVS script.

But, running filters after the IVTC is a good idea, mainly because there will be less frames to work with and, in theory, won't take as long. It is also possible that a filter could screw with IVTC frame detection.

[jdobbs]

Technically the IVTC procedure is part of the AVS script.

But, running filters after the IVTC is a good idea, mainly because there will be less frames to work with and, in theory, won't take as long. It is also possible that a filter could screw with IVTC frame detection.Exactly. Most of the time you want filters to work on the progressive output, not the telecined source.

[Lathe]

You add the prefix to any line to want to clarify -- so you may have one line with an "r:" prefix, another with a "i:r:" prefix, and another with none. The "r:" would be included with any line to which you want it to apply. "r:" just moves where the filter is placed in the AVS file. The fact that they are called prefixes means they go before the filter. But, of course, English isn't everyone's first language -- so I guess I could have made that clearer.

Thanks JD...

Okay, I will go back and read it VERY carefully; granted, I might have just quickly scanned through it. Maybe it DOES say there specifically to start a script line with the letter first and then a ':' immediately after it and then leave a space and then place your code... :)

But, despite Sharc's snarkiness, I AM glad that he brought this up because I was totally unaware of it...

[Lathe]

July 8th, 2010
- Added an AVS filter editor to the SETUP dialog. This
will allow you to add AVS filters to files. Note that
bug reports WILL NOT BE ACCEPTED when filters are in
use (as errors are almost always caused by the filter
usage). You can add "E:", "F:", "I:", or "P:" as a
prefix to a line added in the filter editor. The
prefixes represent "Extras", "Feature", "Interlaced",
and "Progressive" respectively. When specified, the
prefix will limit that filter to usage only when the
source to be encoded matches the prefix. For example,
if specifying "E:filter1()" the filter "filter1()"
would only be applied to segments that are determined
to be extras. Setting "e:i:filter2()" limits use of
"filter2()" to segments that are extras -- and are
also interlaced.
November 28th, 2011
- Added a new prefix for filter editing. By adding
the "r:" prefix, BD-RB will add the specified
filter after the resizing stage (rather than the
default of before). Note: If using more than one
prefix, the "r:" must be the last in the series. Also:

"a:" filter applies to the audio AVS
"m:" filter applies only to menus

Notes:

1. You can use either Upper or Lower case in the filter prefixes, it doesn't matter...
2. On a series disc, where there are multiple episodes -- don't use "F:" because it will only apply to the largest episode

Yep, you do indeed state it pretty clearly. My humble apologies for not reading it carefully... :rolleyes:

Actually, and I hope I'm not being too impulsive AGAIN, but it appears in your examples above that there is NOT a space between the prefix letter & colon. It looks like it runs together. So, I'm glad you helped me clarify that.

[jdobbs]

Yep, you do indeed state it pretty clearly. My humble apologies for not reading it carefully... :rolleyes:

Actually, and I hope I'm not being too impulsive AGAIN, but it appears in your examples above that there is NOT a space between the prefix letter & colon. It looks like it runs together. So, I'm glad you helped me clarify that.You can't have a space between the letter and the colon. If you do, BD-RB won't recognize it as a prefix, and you'll get an error when you try to encode.

I also think I left one out. You can use "s:" to apply a filter only to secondary video (such as the picture-in-picture commentaries).

[Lathe]

You can't have a space between the letter and the colon. If you do, BD-RB won't recognize it as a prefix, and you'll get an error when you try to encode.

I also think I left one out. You can use "s:" to apply a filter only to secondary video (such as the picture-in-picture commentaries).

I was referring to the space between the colon and the function r: Sharpen() That was my first impression, but according to your examples above, it appears that there is NO space between, so the correct way would be:

r:Sharpen()

[Sharc]

....But, despite Sharc's snarkiness, I AM glad that he brought this up because I was totally unaware of it...
As a non-native English speaker I am always keen to add new words to my limited vocabulary.
So I asked Google Translator for translating "snarkiness" but it didn't find anything. Or did you mean "sharciness"? So, curious as I am, I probed further and eventually found the meaning of "snarky". Point taken, thanks! (Of course, I could also have posted asking you for help ;)).

[Lathe]

As a non-native English speaker I am always keen to add new words to my limited vocabulary.
So I asked Google Translator for translating "snarkiness" but it didn't find anything. Or did you mean "sharciness"? So, curious as I am, I probed further and eventually found the meaning of "snarky". Point taken, thanks! (Of course, I could also have posted asking you for help ;)).

Well, well now... I do believe that there is hope for you yet Sharc...

:D

... Wait a second... it just dawned on me that you are indeed STILL ripping on me you ^@@#*!! B@stard! :devil:

[Sharc]

Well, well now... I do believe that there is hope for you yet Sharc...

:D

... Wait a second... it just dawned on me that you are indeed STILL ripping on me you ^@@#*!! B@stard! :devil:

Darn..., lost again in Google translations .... but I assume it's something positive.....

[jdobbs]

Yeah. He maybe he meant "bestard"!

"best" - of the highest quality, excellence, or standing

suffix "ard" - a suffix forming nouns that denote persons who regularly engage in an activity, or who are characterized in a certain way, as indicated by the stem; now usually pejorative

So he was saying you are a person who regularly engages in an activity of the highest quality. Oh... how it fills my heart.

[Lathe]

Yeah. He maybe he meant "bestard"!

"best" - of the highest quality, excellence, or standing

suffix "ard" - a suffix forming nouns that denote persons who regularly engage in an activity, or who are characterized in a certain way, as indicated by the stem; now usually pejorative

So he was saying you are a person who regularly engages in an activity of the highest quality. Oh... how it fills my heart.

Oh boy... :rolleyes:

[gonca]

Yeah. He maybe he meant "bestard"!

"best" - of the highest quality, excellence, or standing

suffix "ard" - a suffix forming nouns that denote persons who regularly engage in an activity, or who are characterized in a certain way, as indicated by the stem; now usually pejorative

So he was saying you are a person who regularly engages in an activity of the highest quality. Oh... how it fills my heart.

You're good, real good

[jdobbs]

You're good, real goodI was partially familiar with this one... because of the number of times I've been referred to as a "dullard". :)

[Sharc]

Yeah. He maybe he meant "bestard"!

"best" - of the highest quality, excellence, or standing

suffix "ard" - a suffix forming nouns that denote persons who regularly engage in an activity, or who are characterized in a certain way, as indicated by the stem; now usually pejorative

So he was saying you are a person who regularly engages in an activity of the highest quality. Oh... how it fills my heart.
Ahhh..., Thank you jdobbs for enlightening me.
And thank you Lathe for the flowers :D

[Lathe]

Ahhh..., Thank you jdobbs for enlightening me.
And thank you Lathe for the flowers :D

Geez... http://lathe-of-heaven.com/doh.gif

[Peter_A]

Apologies, if these questions have been asked and answered already...

When importing an MKV file and outputting to BD, does BD Rebuilder always re-encode the video stream, or does it only do so if the input stream is non-compliant in some way? I ask, because I have an MKV file that when I convert to BD using tsMuxer, I have issues playing on a standalone player. If I import the same MKV file into BD Rebuilder and convert to BD, I see that BD Rebuilder re-encodes the video (not due to size, since it's much smaller than the chosen output size). So, I'm curious if BD Rebuilder was able to tell that the video was non-compliant in some way or if it just always re-encodes.

Another question, which may be off-topic, but is there an easy way to tell if the video stream in an MKV file is BD-compliant? I've converted many MKVs to BD, without issue, simply using tsMuxer, but I've had issues with a handful of them and am unsure how to tell ahead of time which will be the problem ones. I've viewed the details in MediaInfo, but I'm not sure what the offending properties are (or if they'd show up there at all). They are all 1920x1080(p) and have profile 4.1.

Thanks in advance, for any help that can be provided.

[jdobbs]

It will almost always reencode because there are too many required factors that are too hard to check. The BD "basic" specification is about 1500 pages long. Yes, some obvious factors are checked (things like compliant sizing, acceptable audio parameters, etc.) and they are corrected via information in the PSEUDO folder. Others (like GOP sizes, bitrate restrictions, b-frame limits, etc) aren't checked and would require reencoding to assure they are met.

The best advice is to always reencode when you are planning playback on a BD player. The problem is that some players are very forgiving, and they will play things that aren't even close to compliant -- so the fact that it will play on a certain player isn't a good standard to use. There is no guarantee it will play on another (or even the same player following a firmware upgrade) unless the BD restrictions are met.

But if you are 100% sure that the source is already compliant -- just import and delete the PSEUDO folder from within the generated BD structure and burn.

[Peter_A]

Thanks, jdobbs, for the response and very helpful info. I figured that the answer would be that it's probably best to re-encode to ensure compatibility. I'd rather not alter the original stream if I didn't have to, and since I've only had issues with a small percentage of MKV's, I was hoping that there would be a simple way to determine if a steam is incompatible in advance, rather than after burning to physical media. It appears that there is not a simple way. Then again, to your point, even the ones that "work" may not be totally compliant and just happen to work in my 2 players. Thanks again.

[MrVideo]

They are all 1920x1080(p) and have profile 4.1.
It is strange to have a MKV file with the video set for profile 4.1.

The profile value is just that a value, a label. In a nutshell, a 4.0 file will be less than a certain size, while 4.1 can be larger, i.e., the size used on Blu-rays.

That said, to test the file's playablility on your Blu-ray player is to do just that, play it on your Blu-ray player. But, via a USB thumbdrive. If your player can play standalone files, like MKV, via USB attached devices, or DVD/Blu-ray ROM, then place the video on a thumbdrive and see if the player will play it. If not, the player will normally tell you why. In the cases that I have run across, the file was wrapped incorrectly such that the audio was not correctly stored so that the player will not be handle it. In that case, I just re-wrap it with MKVmerge. That has fixed it every time.

As a side note, when burning the output, as suggested by Jdobbs, it is not really necessary to delete the pseudo directory. Just do not add it to the ImgBurn program. Even if you do, the Blu-ray player will ignore it. You can always add content to a Blu-ray disc that isn't part of the BDMV programming. That way you can put the disc into a computer and the extra material is considered as BD-ROM content. You could store images, PDFs, etc.

[MrVideo]

Then again, to your point, even the ones that "work" may not be totally compliant and just happen to work in my 2 players. Thanks again.

The players that have been released over the past few years have been designed to play all kinds of multimedia. As such, the "guts" are the same, no matter if the source is via USB or physical media. That is why content played via Blu-ray authored content will normally play even when not Blu-ray spec compliant. But, as noted in my above posting, sometimes a file may have other issues that keep the player from playing it, no matter the source.

[jdobbs]

The players that have been released over the past few years have been designed to play all kinds of multimedia. As such, the "guts" are the same, no matter if the source is via USB or physical media. That is why content played via Blu-ray authored content will normally play even when not Blu-ray spec compliant. But, as noted in my above posting, sometimes a file may have other issues that keep the player from playing it, no matter the source.I can tell you that hasn't been my experience. My Sony player, for example, will play almost anything that you have on USB media -- but that same content won't play if burned to a BD structure. That's because there are lots of required interdependence between the M2TS audio/video and the other BD components (CLPI files, MPLS files, etc.) The capability of the internal chipsets can be huge -- but that won't change the requirement to stick to the standard. For example, lots of MKV files have removed the black borders on widescreen sources. That plays fine as an MKV on an USB stick. But in the BD standard there is no code (used in the CLPI and MPLS) that describes that format.

[Lathe]

Thanks, jdobbs, for the response and very helpful info. I figured that the answer would be that it's probably best to re-encode to ensure compatibility. I'd rather not alter the original stream if I didn't have to, and since I've only had issues with a small percentage of MKV's, I was hoping that there would be a simple way to determine if a steam is incompatible in advance, rather than after burning to physical media. It appears that there is not a simple way. Then again, to your point, even the ones that "work" may not be totally compliant and just happen to work in my 2 players. Thanks again.

I do pretty much what you do most of the time, making files playable on my OPPO Blu-ray player (which can be VERY touchy sometimes...) So, I feel your pain about occasional MKV files that mysteriously just don't play either natively or when you place them in a BDMV folder (using TSMuxer, for example)

If you don't already have MediaInfo, I strongly suggest that you get it. It isn't always exactly right, but it will help you examine the MKV files and if you can become more familiar with the x264 settings (which I did until I became blind and sterile, and I STILL don't know much, as Sharc will tell you...) then you can open the MKV file in MediaInfo, choose 'text' in the view drop-down menu, and scroll down under the VIDEO section until you come to the x264 settings that usually start with cabac=1 ref=4, etc.

I know for my OPPO that if the ref or 'B' frames are too high for the resolution or the level (4.1) it won't play. I can fudge it a LITTLE, like get away with maybe ref=5 and B=7 on occasion, but not any higher or it simply will not play as an MKV. And, if you put that kind of file into a BDMV folder using say TSMuxer, the player still won't play it.

So, hopefully that might give you a bit of a start in being able to read these files ahead of time and maybe learn some of the 'acceptable' parameters for Blu-ray.

BUT... as JD said, you are best off with any 'off' MKV files letting BDRB re-encode them so that you KNOW that they will be compliant. It's no biggie really. When I have an MKV file that is pesky but I don't want to lose any real quality, even if the file is small, simply choose an output size slightly smaller than the MKV file size. If you choose a slightly smaller size, and then choose either 'auto' or whatever quality you want at that point, you won't lose any appreciable quality at all AND then the file will be encoded properly when done. And, as far as the audio, you can keep whatever you want.

Hope that helps...

[Ch3vr0n]

@jdobbs speaking of the blu-ray spec, i may have stumbled upon an incompatibility with bdrb and the spec. I needed to use one of the bdrb rebuilt discs in a third party application. Upon starting the job of what it needed to do, it instantly jumped to complete. The problem was in hou bdrb handles removed audio & subs. I know bdrb reassigns removed streams to the first english? or available PID which technically duplicates the same ID. This somehow made the 3rd party app think there was 4+hours of audio track when the video title was only 2.5hrs long. Thus it instantly jumped to complete. The only way the 3rd party would proceed with the job was to remove the HD audio track (which the other ones were reassigned to) and then it would encode just fine.

The solution was relatively simple, Open BDEdit, go to playlist tab, STN section and remove the duplicate entries under Au and PG. Unless i missunderstood the standard each stream identifier must be unique and in ascending order, duplicate entries violate the specification. Is there anything you could perhaps look at that even though the streams are removed, the PID's are properly assigned an ascending ID or am i mistaking?

[Peter_A]

I do pretty much what you do most of the time, making files playable on my OPPO Blu-ray player (which can be VERY touchy sometimes...) So, I feel your pain about occasional MKV files that mysteriously just don't play either natively or when you place them in a BDMV folder (using TSMuxer, for example)

If you don't already have MediaInfo, I strongly suggest that you get it. It isn't always exactly right, but it will help you examine the MKV files and if you can become more familiar with the x264 settings (which I did until I became blind and sterile, and I STILL don't know much, as Sharc will tell you...) then you can open the MKV file in MediaInfo, choose 'text' in the view drop-down menu, and scroll down under the VIDEO section until you come to the x264 settings that usually start with cabac=1 ref=4, etc.

I know for my OPPO that if the ref or 'B' frames are too high for the resolution or the level (4.1) it won't play. I can fudge it a LITTLE, like get away with maybe ref=5 and B=7 on occasion, but not any higher or it simply will not play as an MKV. And, if you put that kind of file into a BDMV folder using say TSMuxer, the player still won't play it.

So, hopefully that might give you a bit of a start in being able to read these files ahead of time and maybe learn some of the 'acceptable' parameters for Blu-ray.

BUT... as JD said, you are best off with any 'off' MKV files letting BDRB re-encode them so that you KNOW that they will be compliant. It's no biggie really. When I have an MKV file that is pesky but I don't want to lose any real quality, even if the file is small, simply choose an output size slightly smaller than the MKV file size. If you choose a slightly smaller size, and then choose either 'auto' or whatever quality you want at that point, you won't lose any appreciable quality at all AND then the file will be encoded properly when done. And, as far as the audio, you can keep whatever you want.

Hope that helps...

Thanks, Lathe. You hit the nail on the head about what I'm trying to do (and determine in advance). Yes, I have been using MediaInfo, but unfortunately, I'm not knowledgeable enough (yet), to determine if any of the reported video data is out of spec. For instance, these 2 below do not work. Does anything jump out as being out of spec, on these? Thanks in advance for any insight.

MKV #1:
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 h 41 min
Bit rate mode : Variable
Bit rate : 30.0 Mb/s
Maximum bit rate : 38.0 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.603
Stream size : 21.2 GiB (97%)
Title : MOVIE_1
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709


MKV #2:
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 2 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 h 36 min
Bit rate mode : Variable
Bit rate : 23.0 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.462
Stream size : 15.5 GiB (91%)
Title : MOVIE_2
Default : Yes
Forced : No

[MrVideo]

For example, lots of MKV files have removed the black borders on widescreen sources. That plays fine as an MKV on an USB stick. But in the BD standard there is no code (used in the CLPI and MPLS) that describes that format.
Great example. For the project that I am working on, in order to get menus I used the YouTube 1080p promos. Those files also had the letterbox bars removed. My Sansung player played the videos, but stretched them vertically to fill the screen. So, while they violated the spec, the player played them. I did recode them and add back the bars. On the final disc, they won't be there, because hopefully the single item menu will be working.

While it isn't perfect, the idea of doing the USB thumbdrive test is to see if the file won't play period.

[jdobbs]

For most of my personal use now I simply process a disc using ALTERNATE output and play it back via Serviio. It's a great streaming server, and both of my Sony BD players recognize it immediately and play back flawlessly.

[MrVideo]

I get Blu-ray discs not just because of the movie, or TV series, but because of the special features as well. I love how movies are put together.

When it comes to TV show MKV files, I have a QNAP TS-451A NAS that is used to play the video files using Kodi 17 via HDMI thru my amp. It will also play Blu-ray ISO files, but at this time can not handle BDJava menus. It doesn't handle BD-RB menus either. It handles all of the audio formats as well. I do not use it for ISO anyway. I use the Blu-ray player for that.

[Lathe]

Thanks, Lathe. You hit the nail on the head about what I'm trying to do (and determine in advance). Yes, I have been using MediaInfo, but unfortunately, I'm not knowledgeable enough (yet), to determine if any of the reported video data is out of spec. For instance, these 2 below do not work. Does anything jump out as being out of spec, on these? Thanks in advance for any insight.

MKV #1:
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 h 41 min
Bit rate mode : Variable
Bit rate : 30.0 Mb/s
Maximum bit rate : 38.0 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.603
Stream size : 21.2 GiB (97%)
Title : MOVIE_1
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709


MKV #2:
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 2 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 h 36 min
Bit rate mode : Variable
Bit rate : 23.0 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.462
Stream size : 15.5 GiB (91%)
Title : MOVIE_2
Default : Yes
Forced : No


Unfortunately, it looks like these files have deliberately hidden the x264 settings. From one of my MKV files I'll put the part of MediaInfo below to show you what you need to look for:

: AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 h 27 min
Bit rate : 12.8 Mb/s
Width : 1 920 pixels
Height : 1 040 pixels
Display aspect ratio : 1.85:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.268
Stream size : 7.65 GiB (87%)
Writing library : x264 core 148 r2705 3f5ed56
Encoding settings : cabac=1 / ref=4 / deblock=1:-3:-3 / analyse=0x3:0x133 / me=umh / subme=10 / psy=1 / psy_rd=1.15:0.00 / mixed_ref=1 / me_range=32 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=24 / lookahead_threads=4 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=8 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=240 / keyint_min=24 / scenecut=40 / intra_refresh=0 / rc_lookahead=60 / rc=2pass / mbtree=1 / bitrate=12846 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=3:0.70
Default : Yes
Forced : No
Statistics Tags Issue : no_variable_data 1970-01-01 00:00:00 / no_variable_data 2010-02-22 21:41:29
FromStats_BitRate : 12835737
FromStats_Duration : 01:27:12.519000000
FromStats_FrameCount : 125455
FromStats_StreamSize : 8395405052

The part in bold above is what you need to look at. But, on some encodes, people deliberately change the code to hide the x264 settings. I've tried to find other ways to 'read' these files, but to no avail.

This particular one of mine is a pretty run of the mill MKV that a person may 'run across'. You can see the important parts in red. The stream itself is not set up to force Blu-ray compatibility. The ref frames at 4 should be fine for any playback. But, more importantly, there are 8 'B' frames used which is too high to play in a Blu-ray folder (BDMV) however your player MIGHT play the MKV as is. 8 is a little higher than it should be but my OPPO MIGHT play it okay, or it might stutter or choke it completely. I'll hafta play it and see...

Basically though, as I think we've all pretty much stated here, if you are definitely going to play these files in a Blu-ray format or on a hardware player, unless you know fairly thoroughly what you are doing (not that I am one to speak...:rolleyes: ) it is ALWAYS best to use BDRB to re-encode the file as I suggested the way to do it above. That way, you don't lose quality and the resulting file will ALWAYS play as it is supposed to...

[Lathe]

I get Blu-ray discs not just because of the movie, or TV series, but because of the special features as well. I love how movies are put together.

When it comes to TV show MKV files, I have a QNAP TS-451A NAS that is used to play the video files using Kodi 17 via HDMI thru my amp. It will also play Blu-ray ISO files, but at this time can not handle BDJava menus. It doesn't handle BD-RB menus either. It handles all of the audio formats as well. I do not use it for ISO anyway. I use the Blu-ray player for that.

Yes, I also too love the Xtras! I don't go to all the detailed trouble that you do, but usually I will just basically encode the Movie Only onto a Blu-ray and throw the Xtras w/original menus on another DVD. For me personally, that is the simplest. That way, if I want to play the movie, I play the movie. If I want to see the Xtras, I have them with full original menus on another disc.

Or, if I don't have to compress too much, I'll do an entire disc encode, but normally I like to save the space for the film.

[jdobbs]

You don't have to lose the extras. You can add the entire set together and output to MKV in batch mode. The only thing you drop is the menus.

[MrVideo]

I don't go to all the detailed trouble that you do, but usually I will just basically encode the Movie Only onto a Blu-ray and throw the Xtras w/original menus on another DVD.
Samsung will not play Blu-ray authored formats burned to DVD. Unless it is on Blu-ray media, it will not play it. I find that a little stupid, but that is what they decided.

[Sharc]

Samsung will not play Blu-ray authored formats burned to DVD. Unless it is on Blu-ray media, it will not play it. I find that a little stupid, but that is what they decided.
Very much the same with other (and newer) standalones.
Old SONYs were pretty tolerant. This has definitely changed for the worse, for obvious reasons.

[Sharc]

.... Another question, which may be off-topic, but is there an easy way to tell if the video stream in an MKV file is BD-compliant? .....

http://forum.doom9.org/showpost.php?p=1399419&postcount=1

or draw your conclusions from the info you find here:
https://sites.google.com/site/x264bluray/

Not sure what you mean by "easy way", but check this against the MediaInfo (or similar) report.
Applies for the video part only. Audio etc. must be compliant as well. (And the medium itself .....)
Many reasons for BD-RB to decide to re-encode.

[worknstiff]

@ Lathe; RE: In response to Peter_A,
Unfortunately, it looks like these files have deliberately hidden the x264 settings.
I love mediainfo but then I use exiftool(-k) to get a second opinion on any troublesome files. Its a free open source file info reader that handles just about any type of media file and really gets down in the minutiae of file info. Check it out Peter_A,
(http://owl.phy.queensu.ca/~phil/exiftool/)

One of it's features is •Decodes a riddle wrapped in a mystery inside an enigma, lol.

[jdobbs]

Very much the same with other (and newer) standalones.
Old SONYs were pretty tolerant. This has definitely changed for the worse, for obvious reasons.You'll find that as long as you output in movie-only mode they will play even on Samsung (I have a Samsung player also). Full backups not so much. But with BD discs as cheap as they are these days, it's really not much cost savings to go to BD-5/9 anymore.

[Sharc]

You'll find that as long as you output in movie-only mode they will play even on Samsung (I have a Samsung player also). Full backups not so much. But with BD discs as cheap as they are these days, it's really not much cost savings to go to BD-5/9 anymore.
Yes, you are right. It's only those "ancient" BD5/9 with a menu which fail on my Samsung and LG. Easy enough to recompile these on BD25, or stream the .m2ts via NAS (or Serviio) to the TV.

[jdobbs]

It's likely I could make Quick-Play menus work on BD-5/9 simply by changing the version information in some files. But full-backup isn't possible because AVCHD doesn't support BD-J (which is way to common).

[Sharc]

Well, I have some doubts how popular BD5/9 still are since cost of BD25 are the same or even less today.

[MrVideo]

This has definitely changed for the worse, for obvious reasons.
What are the obvious reasons?

[MrVideo]

You'll find that as long as you output in movie-only mode they will play even on Samsung (I have a Samsung player also). Full backups not so much. But with BD discs as cheap as they are these days, it's really not much cost savings to go to BD-5/9 anymore.
IIRC, the DVD was a burn as the result of building an ISO via tsMuxer. The MKV was small enough, so I just used a DVD. It wasn't a movie, but a TV show episode.

I'll have to try it again.

[MrVideo]

Well, I have some doubts how popular BD5/9 still are since cost of BD25 are the same or even less today.
I never made BD5/9 full backups. Bitrate to low for me. It has always been BD25 media for me.

[DoctorM]

It's likely I could make Quick-Play menus work on BD-5/9 simply by changing the version information in some files. But full-backup isn't possible because AVCHD doesn't support BD-J (which is way to common).

Currently BD5/9 Quick-Play menus work if you load the final disc into MultiAVCHD in 'Blu-ray re-author mode' and then just output it again as an AVCHD Disc (regular or strict seems to make no difference).

The only other thing to remember is in BD-Rebuilder, uncheck "Keep DTS Audio". BD5/9 with Quick-Play bypasses whatever check prevents DTS from being put on movie-only DVD sized discs.

I've been doing this with bonus features for awhile for my old Sony standalone with no issues. (I then burn the movie-only to a BD-25 and put it in a double disc case.)

[Sharc]

What are the obvious reasons?
"Obvious" is perhaps not the correct expression.
I have slight doubts that player/chip manufacturers were only driven by cost optimization to reduce the playback capabilities of their players. Making players most picky can mean extra efforts, perhaps more efforts than being more tolerant to accepting certain deviations from the standard.

[Lathe]

Samsung will not play Blu-ray authored formats burned to DVD. Unless it is on Blu-ray media, it will not play it. I find that a little stupid, but that is what they decided.

Geez Bro, that's a shame. At least my (pretty old) OPPO does do that...

[Lathe]

Currently BD5/9 Quick-Play menus work if you load the final disc into MultiAVCHD in 'Blu-ray re-author mode' and then just output it again as an AVCHD Disc (regular or strict seems to make no difference).

The only other thing to remember is in BD-Rebuilder, uncheck "Keep DTS Audio". BD5/9 with Quick-Play bypasses whatever check prevents DTS from being put on movie-only DVD sized discs.

I've been doing this with bonus features for awhile for my old Sony standalone with no issues. (I then burn the movie-only to a BD-25 and put it in a double disc case.)

Yep, that is pretty much what I generally do too when the full disc size surpasses what I feel I want to compress. That is one thing that I REALLY love about BDRB is it is SO dang easy and fast to throw the Xtras onto a DVD (or another Blu-ray if they are extensive and I don't feel like waiting a couple of hours to reduce them) I USED to do that and then I realized that a Blu-ray disc only cost me about 30 cents more than a DVD and then I looked at myself in the mirror and saw how stupid I was... :cool:

[MrVideo]

Geez Bro, that's a shame. At least my (pretty old) OPPO does do that...
Why a shame? The disc wasn't for me. When it wouldn't work for me, I just put the file on a DVD-ROM. That way I knew the person would be able to play it.

[m.rup]

Hi, when backing up 'Insurgent', region B, I noticed that BD Rebuilder in Movie-Only mode did not select the main feature (21,13 GB) but instead went for some block of extras (14,33 GB). Interestingly, as well in Full Backup mode as in Movie & Menus mode the main feature is identified correctly. 'Divergent' and 'Allegiant' didn't cause any problems in Movie-Only mode.
Furthermore, three leading trailers that can not be skipped are not shown in BD Rebuilders stream list, so I could not blank them.
In multiAVCHD, these traillers appeared as 'menu SP' items. I blanked them there and then processed the output with BD Rebuilder, this seemed to work, but I haven't watched the movie yet.
Any ideas how 'Insurgent' differs from 'Divergent' and 'Allegiant'?
Maybe an option to select main feature manually in Movie-Only mode could help in such cases?

[MrVideo]

Furthermore, three leading trailers that can not be skipped are not shown in BD Rebuilders stream list, so I could not blank them.
When watching a Blu-ray disc that starts out with trailers, you either press the menu button, or the next chapter button. The next chapter button will skip to the end of that trailer and go to the next trailer.

[m.rup]

Yes, but I don't want to press some buttons repeatedly before watching a movie. Therefore, if there is Pop-Up menu and Top Menu functionality prohibited, I blank these trailers.

[gonca]

Hi, when backing up 'Insurgent', region B, I noticed that BD Rebuilder in Movie-Only mode did not select the main feature (21,13 GB) but instead went for some block of extras (14,33 GB). Interestingly, as well in Full Backup mode as in Movie & Menus mode the main feature is identified correctly. 'Divergent' and 'Allegiant' didn't cause any problems in Movie-Only mode.
Furthermore, three leading trailers that can not be skipped are not shown in BD Rebuilders stream list, so I could not blank them.
In multiAVCHD, these traillers appeared as 'menu SP' items. I blanked them there and then processed the output with BD Rebuilder, this seemed to work, but I haven't watched the movie yet.
Any ideas how 'Insurgent' differs from 'Divergent' and 'Allegiant'?
Maybe an option to select main feature manually in Movie-Only mode could help in such cases?

Other Movie-Only Playlist

[m.rup]

Shame!:(

Otherwise, I was wrong when saying that Movie & Menu mode works correctly. Indeed the correct stream is expanded, but the extras are still not set to be blanked.
Besides, what's the reason that I can't see the leading trailers (as well as legal warnings and such stuff that is displayed in multiAVCHD)? Are there other options I also missed? :o

[gonca]

From HIDDENOPTS
MIN_M2TS_SIZE=n n = minimum size required for BD-RB processing in MB, default is 100
MIN_PLAYLIST_MINS=n n = minimum size (in minutes, default=15) for a playlist to be a movie-only choice
Try adjusting the first one in DBRebuilder.ini

[m.rup]

Thanks, I will play around with this setting (at the moment, a backup is running), setting MIN_M2TS_SIZE to very small values will result in seeing that warning stuff?

[MrVideo]

Yes, but I don't want to press some buttons repeatedly before watching a movie.

Ah, OK. But, it is only a single button, not buttons. :D

[MrVideo]

Thanks, I will play around with this setting (at the moment, a backup is running), setting MIN_M2TS_SIZE to very small values will result in seeing that warning stuff?

I'm not sure why you would want those stupid warnings on your backup. Those warnings are obnoxious.

Since they are only about 5 seconds long, the MIN_M2TS_SIZE will need to be set to 4 seconds.

[m.rup]

I don't want the warnings on my backups! I want to see them in BD Rebuilders streams list, so I can blank them.

[Ch3vr0n]

add these settings under [options]

ENABLE_TEST=1
ENABLE_BLANKING=1

Then click on the discs volume label to enter blanking mode

[m.rup]

But I am already in edit mode and I can blank items in the streams list. My problem is that certain items are not present in the list. Therefore, when my current backup has been finished, I will do some testing with MIN_M2TS_SIZE.

[Ch3vr0n]

The thing is, sometimes those warnings aren't video clips but a static image that's displayed for X seconds. Maybe that's why, but the min size may matter too. Can't remember the last time I used blanking, sometimes there's literally 100+ entries of <50MB that showed up for blanking with the default settings! Too much of a hassle to preview them all and make sure legit titles didn't get blanked. Something that was sometimes the case, as bdrb can't differentiate 100% between an extra and a warning.

[MrVideo]

I don't want the warnings on my backups! I want to see them in BD Rebuilders streams list, so I can blank them.

Sorry, misunderstood.

[m.rup]

Sorry, misunderstood.

No problem. ;)

Can't remember the last time I used blanking, sometimes there's literally 100+ entries of <50MB that showed up for blanking with the default settings! Too much of a hassle to preview them all and make sure legit titles didn't get blanked.

Yeah, my normal workflow is to process a movie with BD Rebuilder and then run the output trough multiAVCHD to remove the warnings. That's indeed the most boring part of work, but I want to watch my movies the way I like after backing them up.
Unfortunately, in contrast to wonderful BD Rebuilder, multiAVCHD seems not to be maintained anymore, so in some cases, it is not able to process certain movies correctly. In such cases, I usually simply choose Movie-Only mode in BD Rebuilder, but in case of 'Insurgent', it seemed not to work properly (thanks again, gonca).

I will do some testing, maybe I can find a way to use BD Rebuilder for all processing I want to do.

[MrVideo]

I will do some testing, maybe I can find a way to use BD Rebuilder for all processing I want to do.
Here is what I have done to get Allegiant rebuilt with BD-RB. As you know, Allegiant has been plagued with Cinavia. DVDFab now has the capability to remove Cinavia. It is limited to discs that they have processed and can only be done to make a movie only version or a MKV rip. A complete backup cannot be done. All DVDFab customers can do one Cinavia removal, for testing purposes and whatever movie is used for the testing, is the only movie that the process can ever be done to again (without paying for the product). But, I wanted a disc that has the movie, without Cinavia, as well as all of the special features.

So, I had DVDFab make the MKV file with the Cinavia free Dolby DD5.1 AC3 file. I also had it extract all of the special features as well, but only because it was easier to do them all at once. But, because the main movie was 30GB in size, it would not fit on a 25GB piece of media. So I recoded it to a smaller size.

I went thru the special feature files by viewing them to determine which file was which special feature.

I then created a menu background image with photoshop, using the Allegiant logo. I also extracted the disc's background menu audio. The new movie MKV and the special feature files were put into a directory. BD-RB was used to import them. The files were then given the correct order and menu titles in the menu editor, making sure the menu title text was set to nothing.

Once the menu was set, the files were then imported. At that point, the Blu-ray structure was built and then burned to a BD-RE disc for testing. When all was well, the final Blu-ray disc was burned and a label printed on it (I use ink jet printable media).

So, how can BD-RB be used to do this from beginning to end (except for using photoshop to create the menu background)?

Because the Divergent series of movies are from Lionsgate, they have multiple M2TS files that make up the movie. You will have to use the BD-RB mode to create a single MKV file, but set a target size that will leave enough room for any of the extras that are on the disc. Let BD-RB recode the movie.

Next, pull all of the special feature M2TS files you want from the original disc. It is easy to find out what they are by watching them with VLC. Keep notes as to which M2TS file is which special feature.

Put the recoded movie and the special feature files into a directory. Create a background image and if desired, background audio.

Now, do what I did above and import all the files into BD-RB. Order the files as needed and enter the menu titles for the items. Let BD-RB build the BD structure. Burn it. Do not click on Backup after the files are imported and the quick-play menu created. Everything is ready at that point.

Now you have a rebuilt Blu-ray disc with only the material that you want on it, complete with a menu.

[Ch3vr0n]

@Jdobbs any remark to my previous post about the ID's?

Anyway, i'm having trouble getting DGdecNV to work now that my GTX 1080 is installed. BDRB goes through te first stage ok like "Extracting/indexing stream..." but once that's done, it goes to a SECOND stage of "Indexing stream...." and aborts.

[jdobbs]

@Jdobbs any remark to my previous post about the ID's?

Anyway, i'm having trouble getting DGdecNV to work now that my GTX 1080 is installed. BDRB goes through te first stage ok like "Extracting/indexing stream..." but once that's done, it goes to a SECOND stage of "Indexing stream...." and aborts.Can you remind me again?

The issue sure sounds like the card isn't supported. The second stage is simply a retry after failure of the first one (only limiting what is being extracted). Have you updated to a newer version of DGINDEX/DGDECODE? It might be necessary with your card.

[Ch3vr0n]

As to the ID's: http://forum.doom9.org/showpost.php?p=1784159&postcount=25128

I'm running the latest build 2052

edit: i'm on to something. Build 2050 works. Don't have 2051 anymore. Asked donald for a build. I'll keep you updated. I think i spotted the problem but can't confirm until i get my hands on build 2051.

edit 2: found build 2051. That one works too, it confirmed my suspicions. The problem is the 2052 currently creates index files with extension ".DGI.dgi" (yes double) and not the expected ".DGI" only. As such BDRB can't find the file it's looking for with expected ".DGI" extension, and since it doesn't have a frame index then, encode fails.

** edit 3 ** A new build of 2052 has been built, anyone using DGdecNV build 2052 downloaded prior to today needs to redownload that version and replace the old "DGIndexNV.exe" with the new one from the zip file. That will fix the issue.

[MrVideo]

1. Download and install AVISYNTH v2.57 or above -- it is free. If you are a DVD-RB user, it is compatible, so no worry. It is required for BD Rebuilder to work. AVISYNTH v2.60 can be downloaded from http://www.jdobbs.net/freeware/Avisynth_260.exe or from http://www.avisynth.org.
A warning: dgdecnv 2052 only supports AVISynth v2.6.0, or later.

[MrVideo]

edit 2: found build 2051. That one works too, it confirmed my suspicions. The problem is the 2052 currently creates index files with extension ".DGI.dgi" (yes double) and not the expected ".DGI" only. As such BDRB can't find the file it's looking for with expected ".DGI" extension, and since it doesn't have a frame index then, encode fails.
Extensions of ".dgi" or ".DGI" should not matter to any program. The issue in this case is that BD-RB is expecting "filename.dgi", instead getting "filename.dgi.dgi". Case does not matter.

[Ch3vr0n]

probably, i offered to test with lowercase if it would matter but there was no need he said. I did say due to the double file extension, bdrb couldn't find the file it needed. Anyway, anyone using build 2052 prior to today, needs to redo it or face possible issues.

[MrVideo]

probably, i offered to test with lowercase if it would matter but there was no need he said.
That is because it is M$, where filenames are not case sensitive, even though you can create filenames that are.

[Ch3vr0n]

No, he made a fix in the exe to 'allow for both' whatever that means. Feel free to check my topic over at dgdecnv's home forum. He had made a change in an earlier 2052 build where .DGI -o switch would crash in something because it expected .dgi. thus he had made a change to add .dgi if it did not exist. DGI isn't dgi, so the result was that .dgi was added to the end of .DGI even though the file itself was fine.

[MrVideo]

Interesting. I think I know where the issue was. When you use the CLI and the -o option and the user enters "FILENAME.DGI", M$ is not involved with the file name handling. Don's program is parsing for the extension and he wasn't looking for it "case insensitive."

I was thinking after the file was created, not before. :o

[MrVideo]

I got into a situation where I needed to use BD-RB to create a BD backup of a disc. All went well, except that I forgot that BD-RB will use the disc's menu background, if it finds it. It did. How do I tell BD-RB to not use that, but use the files I pointed to? Because it is a TV series, in this case, the disc's background doesn't include the TV series program name. I created a background that does.

[jdobbs]

I got into a situation where I needed to use BD-RB to create a BD backup of a disc. All went well, except that I forgot that BD-RB will use the disc's menu background, if it finds it. It did. How do I tell BD-RB to not use that, but use the files I pointed to? Because it is a TV series, in this case, the disc's background doesn't include the TV series program name. I created a background that does.From the SETTINGS menu, select "Import/Quick-Play Settings", and then uncheck "Attempt to find original background..."

[MrVideo]

From the SETTINGS menu, select "Import/Quick-Play Settings", and then uncheck "Attempt to find original background..."

Thanks.

[MrVideo]

Silly question...

After the video(s) are imported, one of the imported streams is expanded in the Stream view. Any particular reason why?

[jdobbs]

Silly question...

After the video(s) are imported, one of the imported streams is expanded in the Stream view. Any particular reason why?When BD-RB opens a disc it expands what it determines to be the main feature. Usually it is the largest of the files, but that can change based on a couple of other checks. When it's a series disc it's usually just the largest in the series.

[MrVideo]

Thanks for the update.

[MrVideo]

Houston... we have a major problem.

My newest Samsung 3D player updated its firmware today. Now it refuses to play BD-RB discs. One disc is a backup of a TV show. The other disc is one that I created with MKV files. The first one causes the player to hang and the only way to reset it is to pull the power cord and shortly after reapplying power, continuously press the eject button to get the disc out, otherwise I have to repeat the power cycle. Oh great, I think... Samsung has screwed up my player. But, I determined that it will play a produced disc and one that I downloaded.

So, I turn on the old 2D player and put in the disc of MKV sourced files. I hadn't tried BD-RB discs in the old players before. It churns on it for a little bit and them pops up a message about not being able to load the disc and to check the disc. Next, I try it in the old 3D player. Exact same result. I won't even try the backup disc, as I do not want it to freeze the players.

I have no idea what to do next.

Could explain why Kodi17 in my NAS refused to see the menu on BD-RB discs. Kodi17 is supposed to display non BD-J menus. DVDFab DVD/BD M$ player program won't play BD-RB discs either.

[jdobbs]

Bad media, maybe? It sure sounds like it.

[worknstiff]

@ MrVideo, RE: Houston... we have a major problem

I want to thank you for making me spend the last hour checking all my blue-ray players, lol. I have 5 blue-ray players in the house thanks to my fear of Cinavia and when you posted your comments I had to check them all. I usually play everything in my Oppo in the living room and have had no problems with any of the new or old BDRB disks. I have a Samsung BD-F5100 in the basement I bought so my grandson could play MKV's. Since he moved out I hardly go down there anymore to watch movies. I tried playing some recent blue-ray rebuilds and got the message you did, "this disk is unplayable". Next I got out some retail disks like Dark Knight, and Iron Man and neither one of those would play either. I decided what the hell and updated the firmware to 1022-1, hoping that it would at least play the "REAL" disks again but it still said unplayable. I brought it upstairs and opened the case, ejected the disk drawer and used some alcohol q-tips to clean and dry off the laser. With the drawer out you can go underneath the black T-shaped brace over the laser pickup, just be gentle with it. I then hooked it up and to make sure it wasn't any settings issues I reset it back to the "Factory Defaults" using the 0000 pin number. It now is back to playing all dvd's and blue-rays , retail and rebuilds just like it always did. It's really simple to open the case, only 2 screws. Hope this helps MrVideo.

[jdobbs]

@MrVideo

On the bright side -- at least your Samsung BD player isn't exploding. That's more than can be said for Samsung Phones and Samsung washing machines. :)

[MrVideo]

I want to thank you for making me spend the last hour checking all my blue-ray players, lol.
You needed something to do. :D

Now you are making me do further investigation. I will be reporting back.

[MrVideo]

The report:

The semi-final produced discs for Legend of the Seeker all play in the Samsung 3D player and I tested one on the old 2D player. No idea why a previously burned 25GB disc is no longer liked by the players.

So, I went back and burned a BD-RE of the backup run for a different disc of the TV series. That played just fine.

So, went went wrong with the first disc of the TV series? Good question. I went and looked at the BDMV stream directory and noticed that the menu background M2TS file was missing. So, I reburned the ISO that was created and put it in the computer to look at the content. Sure enough, the background menu M2TS file was missing.

The first run of the disc played just fine, but I noticed that the font was wrong and that the DTS-HD was just DTS. So, I found the setting option for that and hit Backup button again. The videos were re-encoded again, because space was needed for the HD audio.

I have no idea what went wrong that caused the M2TS menu file not to be built.

Here is the log info for all of the runs for that disc:
[00:01:11] Importing BDs: AHS_S3_D2
- Analyzing source playlists...
- Title Editing Dialog...
[00:03:49] Import cancelled...
-------------------------
[00:36:12] Importing BDs: AHS_S3_D2
- Analyzing source playlists...
- Title Editing Dialog...
- Importing BD: AHS_S3_D2 [ 1 of 1 ]
- Importing Playlist 00800 [00:41:45.544]
- Importing Playlist 00801 [00:42:20.579]
- Importing Playlist 00802 [00:48:05.924]
- Importing Playlist 00803 [00:44:13.692]
- Creating Quick-Play Menu...
- Building menu structure...
[01:01:08] Import completed successfully.
----------------------
[11/02/16] BD Rebuilder v0.50.18
[01:57:16] Source: AHS_S3_D2
- Input BD size: 44.43 GB
- Approximate total content: [02:57:28.137]
- Target BD size: 22.95 GB
- Windows Version: 5.2 [3790]
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[01:57:27] - Aborted per user request
----------------------
[11/02/16] BD Rebuilder v0.50.18
[01:58:29] Source: AHS_S3_D2
- Input BD size: 44.43 GB
- Approximate total content: [02:57:28.137]
- Target BD size: 22.95 GB
- Windows Version: 5.2 [3790]
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[01:58:36] - Aborted per user request
----------------------
[11/02/16] BD Rebuilder v0.50.18
[02:00:41] Source: AHS_S3_D2
- Input BD size: 44.43 GB
- Approximate total content: [02:57:28.137]
- Target BD size: 22.95 GB
- Windows Version: 5.2 [3790]
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[02:00:43] PHASE ONE, Encoding
- [02:00:43] Processing: VID_00001 (1 of 4)
- [02:00:43] Extracting A/V streams [VID_00001]
- [02:04:54] Reencoding video [VID_00001]
- [02:04:54] Keeping original video (no reencode)
- [02:04:54] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [02:04:54] Multiplexing M2TS
- [02:09:35] Processing: VID_00002 (2 of 4)
- [02:09:35] Extracting A/V streams [VID_00002]
- [02:13:53] Reencoding video [VID_00002]
- [02:13:53] Keeping original video (no reencode)
- [02:13:53] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [02:13:53] Multiplexing M2TS
- [02:18:46] Processing: VID_00003 (3 of 4)
- [02:18:46] Extracting A/V streams [VID_00003]
- [02:23:44] Reencoding video [VID_00003]
- [02:23:44] Keeping original video (no reencode)
- [02:23:44] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [02:23:44] Multiplexing M2TS
- [02:29:27] Processing: VID_00004 (4 of 4)
- [02:29:27] Extracting A/V streams [VID_00004]
- [02:34:05] Reencoding video [VID_00004]
- [02:34:05] Keeping original video (no reencode)
- [02:34:05] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [02:34:05] Multiplexing M2TS
[02:39:32]PHASE ONE complete
[02:39:32]PHASE TWO - Rebuild Started
- [02:39:32] Rebuilding BD file Structure
[02:39:34] - Encode and Rebuild complete
[02:39:34] Writing BD structure to ISO file
- ImgBurn completed successfully
[02:58:51] JOB: AHS_S3_D2 finished.
----------------------
[11/02/16] BD Rebuilder v0.50.18
[07:28:03] Source: AHS_S3_D2
- Input BD size: 44.43 GB
- Approximate total content: [02:57:28.137]
- Target BD size: 22.95 GB
- Windows Version: 5.2 [3790]
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
- Resuming from previously started job.
[07:28:14] PHASE ONE, Encoding
[07:28:14]PHASE ONE complete
[07:28:14]PHASE TWO - Rebuild Started
- [07:28:14] Rebuilding stream 00001 [1 of 4]
- [07:28:14] Multiplexing M2TS
- [07:33:20] Rebuilding stream 00002 [2 of 4]
- [07:33:20] Multiplexing M2TS
[07:33:26]PHASE ONE aborted by user request
-------------------------
[07:36:05] Importing BDs: AHS_S3_D2
- Analyzing source playlists...
- Title Editing Dialog...
- Importing BD: AHS_S3_D2 [ 1 of 1 ]
- Importing Playlist 00800 [00:41:45.544]
- Importing Playlist 00801 [00:42:20.579]
- Importing Playlist 00802 [00:48:05.924]
- Importing Playlist 00803 [00:44:13.692]
- Creating Quick-Play Menu...
- Building menu structure...
[07:54:15] Import completed successfully.
----------------------
[11/02/16] BD Rebuilder v0.50.18
[08:07:17] Source: AHS_S3_D2
- Input BD size: 44.28 GB
- Approximate total content: [02:56:25.741]
- Target BD size: 22.95 GB
- Windows Version: 5.2 [3790]
- Quick-Play Reauthoring mode enabled
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[08:07:17] PHASE ONE, Encoding
- [08:07:17] Processing: VID_00001 (1 of 4)
- [08:07:17] Extracting A/V streams [VID_00001]
- [08:11:30] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 60,073 frames
- Bitrate: 15,606 Kbs
- [08:11:30] Reencoding: VID_00001, Pass 1 of 1
- [08:45:21] Video Encode complete
- [08:45:21] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [08:45:21] Multiplexing M2TS
- [08:48:08] Processing: VID_00002 (2 of 4)
- [08:48:08] Extracting A/V streams [VID_00002]
- [08:52:27] Reencoding video [VID_00002]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 60,913 frames
- Bitrate: 15,466 Kbs
- [08:52:27] Reencoding: VID_00002, Pass 1 of 1
- [09:26:33] Video Encode complete
- [09:26:33] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:26:33] Multiplexing M2TS
- [09:29:56] Processing: VID_00003 (3 of 4)
- [09:29:56] Extracting A/V streams [VID_00003]
- [09:34:53] Reencoding video [VID_00003]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 69,193 frames
- Bitrate: 15,479 Kbs
- [09:34:53] Reencoding: VID_00003, Pass 1 of 1
- [10:09:22] Video Encode complete
- [10:09:22] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:09:22] Multiplexing M2TS
- [10:13:00] Processing: VID_00004 (4 of 4)
- [10:13:00] Extracting A/V streams [VID_00004]
- [10:17:34] Reencoding video [VID_00004]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 63,625 frames
- Bitrate: 15,469 Kbs
- [10:17:34] Reencoding: VID_00004, Pass 1 of 1
- [10:48:39] Video Encode complete
- [10:48:39] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:48:39] Multiplexing M2TS
[10:52:14]PHASE ONE complete
[10:52:14]PHASE TWO - Rebuild Started
- [10:52:14] Rebuilding BD file Structure
- [10:52:15] Creating Quick-Play Menu...
- Building menu structure...
[10:52:27] - Encode and Rebuild complete
[10:52:27] Writing BD structure to ISO file
- ImgBurn completed successfully
[11:02:45] JOB: AHS_S3_D2 finished.
----------------------
[11/04/16] BD Rebuilder v0.50.18
[01:15:48] Source: AHS_S3_D2
- Input BD size: 44.28 GB
- Approximate total content: [02:56:25.741]
- Target BD size: 22.95 GB
- Windows Version: 5.2 [3790]
- Quick-Play Reauthoring mode enabled
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
- Resuming from previously started job.
[01:15:53] PHASE ONE, Encoding
[01:15:53]PHASE ONE complete
[01:15:53]PHASE TWO - Rebuild Started
- [01:15:53] Rebuilding stream 00001 [1 of 4]
- [01:15:53] Multiplexing M2TS
- [01:19:31] Rebuilding stream 00002 [2 of 4]
- [01:19:31] Multiplexing M2TS
- [01:23:41] Rebuilding stream 00003 [3 of 4]
- [01:23:41] Multiplexing M2TS
- [01:44:21] Rebuilding stream 00004 [4 of 4]
- [01:44:21] Multiplexing M2TS
- [02:16:16] Rebuilding BD file Structure
- [04:11:15] Creating Quick-Play Menu...
- Encoding menu background...
- Building menu structure...
[05:15:52] - Encode and Rebuild complete
[05:15:53] Writing BD structure to ISO file
- ImgBurn completed successfully
[05:26:27] JOB: AHS_S3_D2 finished.
----------------------
[11/04/16] BD Rebuilder v0.50.18
[08:39:07] Source: AHS_S3_D2
- Input BD size: 44.28 GB
- Approximate total content: [02:56:25.741]
- Target BD size: 22.95 GB
- Windows Version: 5.2 [3790]
- Quick-Play Reauthoring mode enabled
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[08:39:10] PHASE ONE, Encoding
- [08:39:10] Processing: VID_00001 (1 of 4)
- [08:39:10] Extracting A/V streams [VID_00001]
- [08:43:40] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 60,073 frames
- Bitrate: 12,855 Kbs
- [08:43:40] Reencoding: VID_00001, Pass 1 of 1
- [09:17:13] Video Encode complete
- [09:17:13] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:17:13] Multiplexing M2TS
- [09:21:09] Processing: VID_00002 (2 of 4)
- [09:21:09] Extracting A/V streams [VID_00002]
- [09:25:52] Reencoding video [VID_00002]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 60,913 frames
- Bitrate: 12,992 Kbs
- [09:25:52] Reencoding: VID_00002, Pass 1 of 1
- [09:59:53] Video Encode complete
- [09:59:53] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:59:53] Multiplexing M2TS
- [10:03:45] Processing: VID_00003 (3 of 4)
- [10:03:45] Extracting A/V streams [VID_00003]
- [10:09:03] Reencoding video [VID_00003]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 69,193 frames
- Bitrate: 13,004 Kbs
- [10:09:03] Reencoding: VID_00003, Pass 1 of 1
- [10:43:22] Video Encode complete
- [10:43:22] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:43:22] Multiplexing M2TS
- [10:47:55] Processing: VID_00004 (4 of 4)
- [10:47:55] Extracting A/V streams [VID_00004]
- [10:52:52] Reencoding video [VID_00004]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 63,625 frames
- Bitrate: 13,003 Kbs
- [10:52:53] Reencoding: VID_00004, Pass 1 of 1
- [11:23:54] Video Encode complete
- [11:23:54] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:23:54] Multiplexing M2TS
[11:28:10]PHASE ONE complete
[11:28:10]PHASE TWO - Rebuild Started
- [11:28:10] Rebuilding BD file Structure
- [11:54:42] Creating Quick-Play Menu...
- Encoding menu background...
[11:54:50]ERROR: Failed quick menu creation. No menus.
[11:54:50] - Encode and Rebuild complete
[11:54:50] Writing BD structure to ISO file
- ImgBurn completed successfully
[12:05:10] JOB: AHS_S3_D2 finished.

Oh look, I see just above that it failed building the menu, but it went on to finish the job. Maybe BD-RB should have bailed at that error. I initially saw the finished line and went on to burn the ISO. An ISO should never have been created.

I did run out of disc space while building the next disc, but it got thru at least one re-encoding before complaining and bailing, which meant there was enough space to build the small menu and well as the 22GB ISO file of the above disc.

So, maybe I did find a minor bug afterall.

[Lathe]

@MrVideo

On the bright side -- at least your Samsung BD player isn't exploding. That's more than can be said for Samsung Phones and Samsung washing machines. :)

Thank GOODNESS I just read this thread!

I had JUST ordered some Samsung underwear from Amazon...

I really owe you guys!

[MrVideo]

Rotflmao!

[laserfan]

Musing here on the upcoming 8th anniversary of this beta, and the approach of 9 million views of this thread, and clicked on Donations... well it's not clear to me how to gift you jdobbs i.e. which email must one use to get a gc to you?

[gonca]

Musing here on the upcoming 8th anniversary of this beta, and the approach of 9 million views of this thread, and clicked on Donations... well it's not clear to me how to gift you jdobbs i.e. which email must one use to get a gc to you?

http://forum.doom9.org/showthread.php?p=1784130#post1784130

[jdobbs]

Musing here on the upcoming 8th anniversary of this beta, and the approach of 9 million views of this thread, and clicked on Donations... well it's not clear to me how to gift you jdobbs i.e. which email must one use to get a gc to you?Either dvd-rb@jdobbs.net or dvd-rb@dvd-rb.com should both work. The other alternative is to PM the card number as in gonca's link.

Thanks.

[Atak_Snajpera]

I wouldn't post emails as plain text on forums unless you want to be bombarded with spam by some bot.

[jdobbs]

Too late. That address has been bombarded ever since it was used for DVD-RB donations back in the early 2000's.

[Mark_Venture]

Any one work with Teenage Mutant Ninja Turtle: Out of the Shadows yet?

I'm trying to re-encode as as "alt-movie only MKV 1920x1080 intact audio" and fails with 50.18. It works with 50.17 and the same settings.

I've tried excluding the TrueHD audio track, setting for DirectShow and DGDecNV as frame serving. 50.18 still fails.

(v0.50.17 is currently running, so I'll grab logs, etc. and post them when its done)

[jdobbs]

Musing here on the upcoming 8th anniversary of this beta, and the approach of 9 million views of this thread, and clicked on Donations... well it's not clear to me how to gift you jdobbs i.e. which email must one use to get a gc to you?By the way, the $50 that shows up when you click isn't a suggested donation (I know that's a lot for most people). It's just what defaults when you go to the gift card link.

[jdobbs]

Any one work with Teenage Mutant Ninja Turtle: Out of the Shadows yet?

I'm trying to re-encode as as "alt-movie only MKV 1920x1080 intact audio" and fails with 50.18. It works with 50.17 and the same settings.

I've tried excluding the TrueHD audio track, setting for DirectShow and DGDecNV as frame serving. 50.18 still fails.

(v0.50.17 is currently running, so I'll grab logs, etc. and post them when its done)Thanks. If it works with the older version and not the new one I'd be interested in finding what changed.

[Mark_Venture]

Ok, 50.18 also fails with Eagle Eye (I'm running that under 50.17 now). They both have TrueHD audio, so I tried with the TrueHD track excluded and it still failed. I also tried with different decoding/frame serving options (I usually use DirectShow, but tried DGDecNV too since i have that). I've also tried with the "Keep HD Audio for BD25/Alternate Intact" checked and unchecked.

Originally I had 50.17 installed. To upgrade to 50.18 back in September... I took my BD-Rebuilder (C:\BD_Rebuilder), made a copy of it (C:\BD_Rebuilder - Copy), then unzipped 50.18 into C:\BD_Rebuilder overwriting everything. I had done many other movies successfully under 50.18 with the same settings. When I saw 50.18 fail on these two, I just ran 50.17 as C:\BD_Rebuilder - Copy\BDRB.exe.

Here is the failure running with 50.18... Let me know if there is anything else you need me to post.

BD-REBUILDER.LOG

----------------------
[11/07/16] BD Rebuilder v0.50.18
[11:55:36] Source: TMNT_2_OUT_OF_THE_SHADOWS_00800
- Input BD size: 29.28 GB
- Approximate total content: [01:52:07.595]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1920x1080, Intact Audio
- Quality: Better (Faster)
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[11:55:36] PHASE ONE, Encoding
- [11:55:36] Processing: VID_00800 (1 of 1)
- [11:55:36] Extracting A/V streams [VID_00800]
- [12:01:08] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 161,301 frames
- [12:01:08] Reencoding: VID_00800, Pass 1 of 1
- Encode failed. Aborting.
- BD-Rebuilder v0.50.18
- Windows Version: 6.1 [7601]
- Working Path Free Space: 56.25GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[12:01:08] - Failed video encode, aborted


TMNT_2_OUT_OF_THE_SHADOWS.INF

[Status]
LABEL=TMNT_2_OUT_OF_THE_SHADOWS
VERSION=v0.50.18
SOURCE_SIZE=31443320832
SOURCE_VIDEO_SIZE=31443320832
TARGET_SIZE=24641536000
REDUCTION=.783681091817828
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=eng;
BACKUP_MODE=1
MOVIEONLY_TYPE=11
USE_LAVF=0
INSTANCES=1
DGDECNV=-1
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
QUICK=0
ENCODE_STEP=1.5
[00800]
AUDIO=10001
PGS=11000
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=24641536000
SPLITS=1


BDREBUILDER.INI
[Options]
VERSION=0.50.0.18
ENCODER=0
MODE=3
ENCODE_QUALITY=1
ONEPASS_ENCODING=1
AUTO_QUALITY=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
DECODER=3
AVCHD=0
REMOVE_WORKFILES=1
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=1
NEROAAC=0
SUPTITLE=1
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23500
PRIORITY_CLASS=0
TARGET_SIZE=23500
MOVIEONLY_TYPE=11
ALTCRF=20
ALT_TARGET=8096
ALTMETHOD=0
ALTAUTOCROP=0
QUICK_EXTRAS=1
AUDIO_DRC=0
PGSTOSRT=0
ALT_CRF_TARGET=1024

[Paths]
SupTitlePath=C:\Program Files (x86)\AviSynth 2.5\plugins\SupTitle.dll
SOURCE_PATH=H:\BLURAY\TMNT_2_OUT_OF_THE_SHADOWS\
WORKING_PATH=F:\BLURAY-WORKING18\
DGIndexNV=C:\BD_Rebuilder\dgdecnv\DGIndexNV.exe
DGDecNV=C:\BD_Rebuilder\dgdecnv\DGDecodeNV.dll

Note: even though this shows path of AviSynth 2.5 for SupTitle, I've installed AviSynth 2.6 from the op recently.

LASTCMD.TXT
"C:\BD_Rebuilder\tools\x264.exe" "F:\BLURAY-WORKING18\WORKFILES\VID_00800.AVS" --preset faster --bluray-compat --b-pyramid none --weightp 1 --slow-firstpass --qpmin=0 --crf 20 --level 4.1 --qpfile "F:\BLURAY-WORKING18\WORKFILES\VID_00800.CHP" --aud --nal-hrd vbr --pic-struct --vbv-bufsize 15000 --keyint 48 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 15000 --threads auto --slices 4 --thread-input --stats "F:\BLURAY-WORKING18\WORKFILES\VID_00800.AVS.264.stats" --output "F:\BLURAY-WORKING18\WORKFILES\VID_00800.AVS.264"


Inspect...
[11/07/16] Checking System Settings
- BD-Rebuilder v0.50.18
- Windows Version: 6.1 [7601]
- Working Path Free Space: 56.25GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[11/07/16] Systems Settings Check complete

[MrVideo]

@jdobbs

So, did I manage to find a minor bug with the menu building section of the code? It is unimportant what the failure actually was, as I do not think that will ever be determined. But, the not stopping does matter.

[jdobbs]

@jdobbs

So, did I manage to find a minor bug with the menu building section of the code? It is unimportant what the failure actually was, as I do not think that will ever be determined. But, the not stopping does matter.The way it is supposed to work is that if the menu encode fails, you end up with a menu-less disc (it plays the disc titles sequentially). That doesn't seem to have worked in your case. I'll have to go back and check it.

[gonca]

@jdobbs and Mark_Venture
Testing the Ninja Turtle movie right now
Seems to be encoding fine

[gonca]

@jdobbs and Mark_Venture
quick encode of Ninja Turtle movie
All is good

[11/07/16] BD Rebuilder v0.50.18
[16:12:42] Source: TMNT_2_OUT_OF_THE_SHADOWS_00800
- Input BD size: 29.28 GB
- Approximate total content: [01:52:07.595]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- AVS Filtering is enabled
- Mode: MKV, CRF, Intact Audio
- Quality: Good (Very Fast)
- X264 Tweak(s) enabled
- Decoding/Frame serving: DGDecNV [4-way]
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[16:12:42] PHASE ONE, Encoding
- [16:12:42] Processing: VID_00800 (1 of 1)
- [16:12:42] Extracting A/V streams [VID_00800]
- [16:17:15] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 161,301 frames
- [16:17:15] Reencoding: VID_00800, Pass 1 of 1
- [16:38:43] Video Encode complete
- [16:38:43] Processing audio tracks
- Track 4352 (eng): Keeping original audio
[16:38:43]PHASE ONE complete
[16:38:43]PHASE TWO - Rebuild Started
- [16:38:43] Building ALTERNATE OUTPUT Structure
[16:43:08] - Encode and Rebuild complete
- WORKFILES folder removed.
[16:43:09] JOB: TMNT_2_OUT_OF_THE_SHADOWS finished.

[Status]
LABEL=TMNT_2_OUT_OF_THE_SHADOWS
VERSION=v0.50.18
SOURCE_SIZE=31443320832
SOURCE_VIDEO_SIZE=31443320832
TARGET_SIZE=24641536000
REDUCTION=.783681091817828
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=eng;
BACKUP_MODE=1
MOVIEONLY_TYPE=3
USE_LAVF=0
INSTANCES=4
DGDECNV=-1
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=1
[00800]
AUDIO=10000
PGS=11000
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=24641536000
SPLITS=4
NSIZE=0
FLINK=0
MLINK=0

[MrVideo]

The way it is supposed to work is that if the menu encode fails, you end up with a menu-less disc (it plays the disc titles sequentially). That doesn't seem to have worked in your case. I'll have to go back and check it.
Ah, OK. Correct. In this case, it locked up one player and just wouldn't play in the other two.

[Mark_Venture]

@jdobbs and Mark_Venture
Testing the Ninja Turtle movie right now
Seems to be encoding fineThanks for checking.

Now I guess its time to figure out what is going wrong with my system...

I just booted to my win10 partition.. and with 50.18, same INI, etc... and TMNT_2 worked.. So its got to be something with my Win 7 setup.

I guess I'll completely blow away my BDRB folder, and start it over.

[Lathe]

Either dvd-rb@jdobbs.net or dvd-rb@dvd-rb.com should both work. The other alternative is to PM the card number as in gonca's link.

Thanks.

Wow, I stay away for a couple of days and all kinds of great stuff happens! All right, good going whomever thought of that on the other thread from Toronto! (My Mom was born in Brandfort if I spelled that right...)

DAMN! That is awesome that we now FINALLY have a way to send JD something decent. Yeah, I get almost bloody EVERYTHING from Amazon, so that is a frigg'n great idea! :D

[jdobbs]

Thanks for checking.

Now I guess its time to figure out what is going wrong with my system...

I just booted to my win10 partition.. and with 50.18, same INI, etc... and TMNT_2 worked.. So its got to be something with my Win 7 setup.

I guess I'll completely blow away my BDRB folder, and start it over.Did you ever find out what was going on?

[Mark_Venture]

Did you ever find out what was going on?
Well.. No, but I got it working...

First I made a fresh new folder, unzipped 50.18 to it... When I started BDRB for the first time I got told about LAV not being configured, did I want to fix it? I said yes, It errored saying something like SetACL_x64 wasn't compatible with this version of Win 7. I got past that by copying the SetACL_x64 from my 50.17 folder. Trying an encode, it failed nearly immediately saying "Failed to retrieve audio, aborted." Again, 50.17 continued to perform just fine.

I verified FFDshow settings per the OP, even made sure what versions I was running, etc. Still 50.18 failed, but 50.17 continued to work.

Finally, I deleted all folders of 50.18 I made while trying to trouble shoot this. I unzipped again into a new "new folder." Again on first launch I got the LAV not configured.. I answered yes... and it didn't error. I manually setup my options and tried again with TMNT2, this time it worked.

While I've had issues upgrading in the past by just unzipping the new version on top of the old, in this case, I did that weeks ago (ok, month and a half?) and had been working fine. So I'm not sure why all of a sudden I ran into problems when I hadn't changed anything on BD-RB. And other than updates to windows, DVDFab Passkey, Nvidia Geforce drivers, and iTunes, I haven't changed anything on my Win 7 install or BD-Rebuilder since the end of September.

[gonca]

Well.. No, but I got it working...

First I made a fresh new folder, unzipped 50.18 to it... When I started BDRB for the first time I got told about LAV not being configured, did I want to fix it? I said yes, It errored saying something like SetACL_x64 wasn't compatible with this version of Win 7. I got past that by copying the SetACL_x64 from my 50.17 folder. Trying an encode, it failed nearly immediately saying "Failed to retrieve audio, aborted." Again, 50.17 continued to perform just fine.

I verified FFDshow settings per the OP, even made sure what versions I was running, etc. Still 50.18 failed, but 50.17 continued to work.

Finally, I deleted all folders of 50.18 I made while trying to trouble shoot this. I unzipped again into a new "new folder." Again on first launch I got the LAV not configured.. I answered yes... and it didn't error. I manually setup my options and tried again with TMNT2, this time it worked.

While I've had issues upgrading in the past by just unzipping the new version on top of the old, in this case, I did that weeks ago (ok, month and a half?) and had been working fine. So I'm not sure why all of a sudden I ran into problems when I hadn't changed anything on BD-RB. And other than updates to windows, DVDFab Passkey, Nvidia Geforce drivers, and iTunes, I haven't changed anything on my Win 7 install or BD-Rebuilder since the end of September.

Use win7dsfiltertweaker to see what filters you are using and then compare to when you start having issues

http://www.videohelp.com/software/Preferred-Filter-Tweaker

[Yordan5]

My OS is Win 7 64bit with NVIDIA GeForce GTX 750 graphics card. When shrinking BD movies I always use the "Highest (very slow)" encoder setting. This worked just fine with all versions of BD RB and on average took 3 to 4 hours to complete (movie only). For some reason with the lates build of BD RB (0.50.18) the processing time doubled. It now takes overnight to do the same job. I tried clean install of everything, tried it on freshly installed OS, tried with and without LAV filters and Matroska splitter installed but it still takes more than 8 hours to complete a job that would previously take 50% less time. Is there a known issue that I need to be aware of and also is there a solution that would reduce the Reencoding time to previous levels?

[jdobbs]

My OS is Win 7 64bit with NVIDIA GeForce GTX 750 graphics card. When shrinking BD movies I always use the "Highest (very slow)" encoder setting. This worked just fine with all versions of BD RB and on average took 3 to 4 hours to complete (movie only). For some reason with the lates build of BD RB (0.50.18) the processing time doubled. It now takes overnight to do the same job. I tried clean install of everything, tried it on freshly installed OS, tried with and without LAV filters and Matroska splitter installed but it still takes more than 8 hours to complete a job that would previously take 50% less time. Is there a known issue that I need to be aware of and also is there a solution that would reduce the Reencoding time to previous levels?Are you using X264's internal LAVF as your decoding option? If so, see this link (http://forum.doom9.org/showthread.php?p=1779038#post1779038) and associated posts.

[Yordan5]

Are you using X264's internal LAVF as your decoding option? If so, see this link (http://forum.doom9.org/showthread.php?p=1779038#post1779038) and associated posts.

I am using whatever BD RB (downloaded from page 1) comes with. Sounds like for the time I will have to accept slower processing speeds.

[jdobbs]

I am using whatever BD RB (downloaded from page 1) comes with. Sounds like for the time I will have to accept slower processing speeds.Not necessarily. From within BD-RB go to the SETUP page (Settings/Setup) and report what is checked under "Decoding/Frame Serving Options". The default changes based upon how your system is configured.

[mparade]

Will BD-RB support quicktime codecs to import? My projects include DNxHD 1080p 10-bit (50fps progressive) 4:2:2 output files coming directly from the editor program. I would like to import and reencode them into mkv format using the power of x264 in BD-RB.

Thank you for the help.

[jdobbs]

Will BD-RB support quicktime codecs to import? My projects include DNxHD 1080p 10-bit (50fps progressive) 4:2:2 output files coming directly from the editor program. I would like to import and reencode them into mkv format using the power of x264 in BD-RB.

Thank you for the help.It would have to be a Blu-Ray compatible CODEC (MPEG-2, AVC, VC-1, or HEVC) to import without forced reencoding during import. It will also import XVID or DIVX and reencode to AVC during the import process.

The source would have to be in a supported container as well.

[Yordan5]

Not necessarily. From within BD-RB go to the SETUP page (Settings/Setup) and report what is checked under "Decoding/Frame Serving Options". The default changes based upon how your system is configured.

The checked options are:Use DEINTERLACER on..., Do not convert DTS to AC3, Do not reencode AC3, Keep HD Audio for BD25, Use X264's internal LAVF for frame serving, Strict AVCHD for BD-5/9

[jdobbs]

The checked options are:Use DEINTERLACER on..., Do not convert DTS to AC3, Do not reencode AC3, Keep HD Audio for BD25, Use X264's internal LAVF for frame serving, Strict AVCHD for BD-5/9 The boldfaced setting above is your problem. Select DirectshowSource instead. If you can't select it, then you're not configured properly -- go back to the instructions in the first post of this thread and uninstall/reinstall.

[MrVideo]

Will BD-RB support quicktime codecs to import? My projects include DNxHD 1080p 10-bit (50fps progressive) 4:2:2 output files coming directly from the editor program. I would like to import and reencode them into mkv format using the power of x264 in BD-RB.
You have a lot of things going against you: 1) DNxHD 2) 50fps 3) 4:2:2

But, ffmpeg has support for VC-3, so you should be able to directly use ffmpeg to recode to H.264. So, take a look at ffmpeg.

[Yordan5]

The boldfaced setting above is your problem. Select DirectshowSource instead. If you can't select it, then you're not configured properly -- go back to the instructions in the first post of this thread and uninstall/reinstall.

Did as you suggested: clean install and selected DirectshowSource. Unfortunatelly it is still taking almost 8 hrs to process a movie that would previously take no more than 4 hrs. Thank you for the time to try and help.

[jdobbs]

Did as you suggested: clean install and selected DirectshowSource. Unfortunatelly it is still taking almost 8 hrs to process a movie that would previously take no more than 4 hrs. Thank you for the time to try and help.Then I'm guessing you are still using X264/LAVF -- and if that is selected automatically you didn't install LAV Filters (or FFDSHOW) correctly.

[mparade]

You have a lot of things going against you: 1) DNxHD 2) 50fps 3) 4:2:2

But, ffmpeg has support for VC-3, so you should be able to directly use ffmpeg to recode to H.264. So, take a look at ffmpeg.

I will do that way. The second option would be to output from DaVinci in AVC format and then import that file to BD-RB, but that would be a "unnecessary" extra step that may degrade the quality even more. In these specific projects of mine I will use ffmpeg instead. :thanks:

[brunchto]

Hi,

I rip my 3D discs to m2ts with film only mode. BD -> FILM ONLY folder, get m2ts. it's the only way i find to rip br3D and play on my oppo.

on some films, left and right eyes are inverted (edge of tomorrow, The Jungle Book). on my tv, i can invert while playing, but i don't have the option on my projector.

is there a way to invert eyes at the creation of the backup?

[Blurayhd]

Hi guys, I have a Bluray copy on my hd of Alice Through the looking Glass 3D and I don´t have any system that support 3D, I mean, My Bluray player, My Led TV etc dont support 3D, so, I can see on BD rebullder settings the "Process 3D video sources as 2d for backup" so I encoded this movie and I tried it on my computer with Powerdvd and ask me for 3D

So I wonder if this option of Bd rebuilder is to convert the 3D to 2d? or what exactly does that function? and there´s some way to encode with Bd rebuilder the 3D to 2d?

Thank you for your time guys

[jdobbs]

Hi guys, I have a Bluray copy on my hd of Alice Through the looking Glass 3D and I don´t have any system that support 3D, I mean, My Bluray player, My Led TV etc dont support 3D, so, I can see on BD rebullder settings the "Process 3D video sources as 2d for backup" so I encoded this movie and I tried it on my computer with Powerdvd and ask me for 3D

So I wonder if this option of Bd rebuilder is to convert the 3D to 2d? or what exactly does that function? and there´s some way to encode with Bd rebuilder the 3D to 2d?

Thank you for your time guysYou should be able to... I'll do some testing an make sure it's still working right.

[jdobbs]

Did as you suggested: clean install and selected DirectshowSource. Unfortunatelly it is still taking almost 8 hrs to process a movie that would previously take no more than 4 hrs. Thank you for the time to try and help.Then I'm guessing you are still using X264/LAVF -- and if that is selected automatically you didn't install LAV Filters (or FFDSHOW) correctly.In the next release of BD-RB there will a change that automatically uses an older version of X264 if you have selected X264/LAVF for decoding. That should solve your speed problem. I may post it later today or tomorrow.

[Ch3vr0n]

The thing with 3D is that even if you process it with the option to treat as 2D, that doesn't mean that the java code on the disc will allow it. Certain code can exist that enforces the need for a 3D capable playback device, regardless of the fact if BDRB made the video 2D or not. There's nothing BDRB can do about that.

[jdobbs]

The thing with 3D is that even if you process it with the option to treat as 2D, that doesn't mean that the java code on the disc will allow it. Certain code can exist that enforces the need for a 3D capable playback device, regardless of the fact if BDRB made the video 2D or not. There's nothing BDRB can do about that.True.

[jdobbs]

I have updated the first post of this thread with a link to the latest version of BD-RB (v0.50.19). Changes for this release:- Added the ASS/SSA subtitle format to those
supported during import (converts to SRT).
- Fixed an error during import in which weird
source size could result in an AddBorders()
filter appendix that causes encode failure
(YV12 AddBorders parameters must be MOD2).
- Corrected an issue in which framerates that
are slightly off might prevent import from
converting to pseudo-bd format.
- Modified code so that SRT files that exist
in an import folder that have the same name
as selected video files (except with an SRT
extension) will be automatically imported.
Also see the IMPORT_SRT_LANG hidden option
in HIDDENOPTS.TXT for setting a default
language for the imported SRT. Note that
SRTs that are embedded in a source stream
retain their specified language and are not
affected by the IMPORT_SRT_LANG setting.
- Included an older version of X264 for users
that use X264/LAVF frame serving. Newer
X264 versions run significantly slower in
this mode (probably due to libavformat
updates that are slower).
- Added code that will recognize when sources
using AC3 with variable bitrate might have
an incorrect bitrate in the header.
- Updated the included version of X264.EXE to
the latest release (r2721).
- Updated the included version of X264-64.EXE
to the latest release (r2721).
- Other minor corrections and cosmetic fixes.

[soneca]

Thank you jdobbs! :rolleyes:

[MrVideo]

In these specific projects of mine I will use ffmpeg instead. :thanks:
You are welcome. Hopefully that works just fine.

[jdobbs]

To Robert

Just wanted to let you know that I received your gift card -- but, for some reason, I didn't get a return address in the e-mail. So I'm posting here to let you know I got it -- and to thank you -- your generosity is greatly appreciated!

[MrVideo]

I have updated the first post of this thread with a link to the latest version of BD-RB (v0.50.19).
I have to assume, that based upon the change list, that allowing a single menu item is not in this release.

[TheEthic]

I have updated the first post of this thread with a link to the latest version of BD-RB (v0.50.19). Changes for this release:
- Included an older version of X264 for users
that use X264/LAVF frame serving. Newer
X264 versions run significantly slower in
this mode (probably due to libavformat
updates that are slower).

Hi! Thanks for another update...!!!

In this new update, I have the following error:


[11/14/16] Checking System Settings
- BD-Rebuilder v0.50.19
- Windows Version: 6.2 [9200]
- Working Path Free Space: 6,78GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- X264: Wrong version found
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[11/14/16] Systems Settings Check complete


Will the new version of x264 be the cause? How could you solve it?

[jdobbs]

I have to assume, that based upon the change list, that allowing a single menu item is not in this release.No. Sorry. I'll get to work on that tomorrow. I'm also going to work on the ability to make BD-5/9 menus that will work (AVCHD). I got a couple gift-card donations this week and got me thinking I might spend some more time on it.

[jdobbs]

Hi! Thanks for another update...!!!

In this new update, I have the following error:



Will the new version of x264 be the cause? How could you solve it?That's a mistake on my part -- It appears I forgot to update the X264 checksum when I released the new version. Just ignore it.

[jdobbs]

I wish I could somehow change the Amazon Gift card link to reflect something smaller than the $50 default -- that might turn people off. Does anybody know how to do that?

[MrVideo]

No. Sorry. I'll get to work on that tomorrow.
Thanks.

[Yordan5]

In the next release of BD-RB there will a change that automatically uses an older version of X264 if you have selected X264/LAVF for decoding. That should solve your speed problem. I may post it later today or tomorrow.

With the updated BD-RB version the longer encoding time issue for me is still present. I experimented using X264/LAVF and then DirectshowSource. With using X264/LAVF the encoding time was approximately an hour less but still almost 7 hours in total for the whole process. Another thing is that with the last two versions of BD-RB my CPU utilization seems to have become a lot heavier during Pass 1. The PC is now far less responsive even if used for web browsing. This was not the case before even during Pass 2.
CPU - Intel Core i7 4770, 8Gb RAM.

[Shuttle99]

This has probably been asked but I couldn't find the answer to help me decide. The question is in setup under decoding/frame serving there are 4 choices the only two I have used are the top two "Use DirectshowSource for frame serving or Use X264's internal". Which one is better to use and a quick explanation of why, or even the last two (I've never used the last two) but maybe their better.

Thanks,
Shuttle99

[jdobbs]

This has probably been asked but I couldn't find the answer to help me decide. The question is in setup under decoding/frame serving there are 4 choices the only two I have used are the top two "Use DirectshowSource for frame serving or Use X264's internal". Which one is better to use and a quick explanation of why, or even the last two (I've never used the last two) but maybe their better.

Thanks,
Shuttle99I just keep it on DirectshowSource. There are lots of features that require that aren't supported via X264/LAVF, like iVTC, some resizing, adding/removing borders, etc. The truth is that if you have LAV filters or FFDSHOW installed, and something is set that requires it -- it is used even if you have selected X264/LAVF. The only reason to really use X264/LAVF is if it is faster on your computer. I think that's rare (at least to any significant effect). But if you get a few fps more -- then you might want to use it. The downside is that some recent changes in X264 seem to make it slower...

If you are using an Intel processor that is supported by the Intel SDK library, you may get some extra speed out of FRIM -- but it's really there to support 3D, and it gets set automatically for that when needed.

DGDecNV is probably the best choice for everyday use -- but it costs money (you have to buy a license). It also requires a supported Nvidia video card, and if you are using Win10 the list of supported cards has shrunken (many older cards don't work anymore).

[Shuttle99]

Thanks jdobbs for the quick reply on which to use.

Shuttle99

[Blurayhd]

Hi guys, ther´s some way to extract the subtitles from Bluray disc? I mean, I have some movie and I need to extrat any language to SRT format, can Bd rebuilder do that? Have a good day

[jdobbs]

Hi guys, ther´s some way to extract the subtitles from Bluray disc? I mean, I have some movie and I need to extrat any language to SRT format, can Bd rebuilder do that? Have a good dayNo, not directly. Subtitles on BD are PGS (graphic) format and an SRT actually needs the text rather than the graphics. That means some type of OCR has to occur in between.

BD-RB does have the ability to convert it during output to ALTERNATE formats (see the selection in the SETUP dialog) -- but the OCR is unsupervised, so there is usually some required editing after the conversion.

There are a few good independent methods for PGS -> SRT conversion. Subtitle Edit is a pretty good one. You can use TSMUXER to extract the PGS (to a .SUP file), and then use Subtitle Edit to perform a supervised OCR conversion.

[MrVideo]

if you are using Win10 the list of supported carsd has shrunken (many older cards don't work anymore).
Really, M$ has made perfectly good cards unusable?

[jdobbs]

Really, M$ has made perfectly good cards unusable?The cards are usable with Win10, no problem. But Nvidia has stopped supporting them in their SDK that DGDecNV uses.

[MrVideo]

But Nvidia has stopped supporting them in their SDK that DGDecNV uses.
Well that sucks. Good thing I won't be going to Win10 any time soon, if ever.

[DoctorM]

This has probably been asked but I couldn't find the answer to help me decide. The question is in setup under decoding/frame serving there are 4 choices the only two I have used are the top two "Use DirectshowSource for frame serving or Use X264's internal". Which one is better to use and a quick explanation of why, or even the last two (I've never used the last two) but maybe their better.

Thanks,
Shuttle99
Since the internal LAVF got slow, I've been a big fan of using external LAVF with hardware acceleration turned on.
Not as fast as DgdecNV, but reliable and quick.

[Yordan5]

Since the internal LAVF got slow, I've been a big fan of using external LAVF with hardware acceleration turned on.
Not as fast as DgdecNV, but reliable and quick.


Yesterday I purchased a license for DgdecNV and tried it with BD-RB. (Nvidia card GeForce GTX 750, Intel Core i7 4770). Pointed BD-RB to the location of DgdecNV exe file and ran the job. There was no difference in encoding speed at all. Could someone suggest what I should pay attention to or be aware of when using BD-RB with DgdecNV? Do I need to have installed LAV Directshow Filters or FFDShow or Haali as well?

[jdobbs]

Yesterday I purchased a license for DgdecNV and tried it with BD-RB. (Nvidia card GeForce GTX 750, Intel Core i7 4770). Pointed BD-RB to the location of DgdecNV exe file and ran the job. There was no difference in encoding speed at all. Could someone suggest what I should pay attention to or be aware of when using BD-RB with DgdecNV? Do I need to have installed LAV Directshow Filters or FFDShow or Haali as well?DGDecNV works independently of LAV or FFDSHOW. Speed isn't everything you'd get with it. For example, it has frame accurate seeking -- so you can confidently use MULTIPROCESS. That's something you might want to try if you aren't using 100% of you processors during encoding.

[Weirdo]

When "Scanning source directory" is triggered, for example by changing Settings/Output options or selecting "Quicker Encode for Extras", all Blanked item selections are lost. Not sure if this is intended behaviour, doesn't seem like these selections interfere with these options.

[Seajunk]

Yesterday I purchased a license for DgdecNV and tried it with BD-RB. (Nvidia card GeForce GTX 750, Intel Core i7 4770). Pointed BD-RB to the location of DgdecNV exe file and ran the job. There was no difference in encoding speed at all.

You also have to keep in mind that DgdecNV is a hardware decoder only. It reduces the over all time of a job (usually significantly) but wont affect the encoding speed portion.

[Blurayhd]

No, not directly. Subtitles on BD are PGS (graphic) format and an SRT actually needs the text rather than the graphics. That means some type of OCR has to occur in between.

BD-RB does have the ability to convert it during output to ALTERNATE formats (see the selection in the SETUP dialog) -- but the OCR is unsupervised, so there is usually some required editing after the conversion.

There are a few good independent methods for PGS -> SRT conversion. Subtitle Edit is a pretty good one. You can use TSMUXER to extract the PGS (to a .SUP file), and then use Subtitle Edit to perform a supervised OCR conversion.

Thank you Jdobbs for the detailed explanation buddy

[Mark_Venture]

Need some help troubleshooting an issue..

After extracting... I get a pop-up error from windows saying.. BD Rebuilder experienced an error [time] CreateAVS() 00000

[11/16/16] BD Rebuilder v0.50.19
[10:34:16] Source: INDEPENDENCE_DAY_RESURGENCE_00801
- Input BD size: 31.58 GB
- Approximate total content: [01:59:44.176]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1920x1080, Intact Audio
- Quality: Better (Faster)
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[10:34:19] PHASE ONE, Encoding
- [10:34:19] Processing: VID_00600 (1 of 3)
- [10:34:19] Extracting A/V streams [VID_00600]
- [10:39:38] CreateAVS() 00000
[10:49:46] - Could not create AVS fileIts only this disc.

I know i had issues that were self inflicted before.. but they seem to be resolved. And I have this error with this disc, and only this disc. Other movies (like Ice Age Collision course, etc) are fine. ANd I've tried freshly unpacking BD-Rebuilder again.

This error happens on each of my 3 OS partitions (each with BD-Rebuilder installed).

Should I post any log, or ini file?

[jdobbs]

BD Rebuilder experienced an error [time] CreateAVS() 00000 That shouldn't be the time... is should be the error type. But I think I've seen time there before... I'll have to check and see how that's possible.

[Mark_Venture]

That shouldn't be the time... is should be the error type. But I think I've seen time there before... I'll have to check and see how that's possible.

I just ran it again... [12:55:58] and my pc clock just ticked to 12:56...

[jdobbs]

I just tested that call and got the time also. I have no idea how the time gets embedded in the error code...

[Edit] Ok, I see it now. The location of the error isn't provided, so the 0000 is actually the error number and the location is "blank".

The problem is: That call should never be executed with an error of 0 (meaning no-error).

[gonca]

@Mark_Venture
Do you have SupTitle selected in the settings

[Mark_Venture]

@Mark_Venture
Do you have SupTitle selected in the settings

YES.... and seeing your question.. I just unchecked it... its now "Reencoding: VID_00600, Pass 1 of 1" i.e. it got past the error and seems to be working... It will be a little before it fully finishes (assuming it continues without error).

Could this be something with the way subtitles are done in this movie?

Has anyone done INDEPENDENCE_DAY_RESURGENCE yet?

[gonca]

YES.... and seeing your question.. I just unchecked it... its now "Reencoding: VID_00600, Pass 1 of 1" i.e. it got past the error and seems to be working... It will be a little before it fully finishes (assuming it continues without error).

Could this be something with the way subtitles are done in this movie?

Has anyone done INDEPENDENCE_DAY_RESURGENCE yet?

Could be the way they are done or it could be something is missing in the subtitle in order for it to be recognized properly

I've done that movie, but I check for forced subs first and probably didn't use SupTitle on it

[jdobbs]

What I don't get is how it would cause an error in CreateAVS()? All that does is create the AVS file... it doesn't attempt the conversion.

@Mark_Venture

What language to you have selected as the default for subtitles? Are you using the default of English. I'll see if I can pick up that movie and give it a test.

[gonca]

@jdobbs
I have that movie, so if you want me to run some tests let me know

[Mark_Venture]

What I don't get is how it would cause an error in CreateAVS()? All that does is create the AVS file... it doesn't attempt the conversion.

@Mark_Venture

What language to you have selected as the default for subtitles? Are you using the default of English. I'll see if I can pick up that movie and give it a test.
English is the default language, and sub titles.

The INI I shared in Post #25199 (http://forum.doom9.org/showpost.php?p=1785246&postcount=25199) is what I'm using.

IF you don't already own this movie, don't buy it if its just me facing this issue!! I do have options to have a working back up. Since it ran with "Use SupTitle for Alternate Forced Subs" unchecked, I'm happy to just extract the subtitles using HdBrStreamExtractor and SubTitle Edit. Plus I have DVDFab Ripper which I've successfully used on this title. I mean I like BD Rebuilder better, and its the way I prefer to make my backups!! it gives me much better picture quality when I compare output of the same disc..
@jdobbs
I have that movie, so if you want me to run some tests let me know
If you have the ability to run, and see if you get the same error as I do, that would be appreciated.. I'd love to know if its something in my system (although since I get the same error on a fresh install of Win10 & BD Rebuilder, as well as the installs on my Win 7 partitions, I hope its not my system)..

[jdobbs]

English is the default language, and sub titles.

The INI I shared in Post #25199 (http://forum.doom9.org/showpost.php?p=1785246&postcount=25199) is what I'm using.

IF you don't already own this movie, don't buy it if its just me facing this issue!! I do have options to have a working back up. Since it ran with "Use SupTitle for Alternate Forced Subs" unchecked, I'm happy to just extract the subtitles using HdBrStreamExtractor and SubTitle Edit. Plus I have DVDFab Ripper which I've successfully used on this title. I mean I like BD Rebuilder better, and its the way I prefer to make my backups!! it gives me much better picture quality when I compare output of the same disc..

If you have the ability to run, and see if you get the same error as I do, that would be appreciated.. I'd love to know if its something in my system (although since I get the same error on a fresh install of Win10 & BD Rebuilder, as well as the installs on my Win 7 partitions, I hope its not my system)..I was in town today so I picked it up. I'll run it with your INI and see what happens. I hope I can repeat it, I want to see what could possibly cause it to crash win a Runtime Error 0.

[jdobbs]

I was in town today so I picked it up. I'll run it with your INI and see what happens. I hope I can repeat it, I want to see what could possibly cause it to crash win a Runtime Error 0.@Mark_Venture

Just so you know, I ran the job using your INI and, sure enough, I got the same error. I've already identified what is happening, now I just have to put my finger on why. I also found out why it is incorrectly reporting the error as 0. I should have it fixed for the next release.

Good bug report. Thanks.

[jdobbs]

I have made numerous encoding attempts on IP Man 3 Blu-ray, but the subtitles simply will not sync ... first time I have come across this issue. The subtitles are in sync when playing the AnyDVD HD rip. What elements should I address in BD-RD to attempt to correct the subtitle syncing?I had this listed in my bug to-do list, and noticed something related in something I was working on today. Can you tell me more about this error.

1. What type of encode are you doing (ALTERNATE, MOVIE-ONLY, FULL)?
2. Is this a multipart source for which you are trying movie-only backup?
3. Were subtitles forced ON from within the streams list?

[jdobbs]

Just wondering.
Any other thoughts on BD Rebuiler failure for this film?Don't know if I responded to this back in October... but, I haven't forgotten it, and I've updated BD-RB so it will be more specific as to what kind of error you got in CreateAVS() -- I suggest you try that disc one more time when I release version 0.50.20. It may not fix the problem -- but it could at least help identify what is happening.

Also, can you tell me whether you had any subtitles forced ON in that source? That may be an indicator of a problem I found/fixed for the next release.

[ggtop]

Don't know if I responded to this back in October... but, I haven't forgotten it, and I've updated BD-RB so it will be more specific as to what kind of error you got in CreateAVS() -- I suggest you try that disc one more time when I release version 0.50.20. It may not fix the problem -- but it could at least help identify what is happening.

Also, can you tell me whether you had any subtitles forced ON in that source? That may be an indicator of a problem I found/fixed for the next release.

I am looking forward solving the problem I had with e.g. Bridge of Spies and MP4 output :)
ggtop

[jdobbs]

I am looking forward solving the problem I had with e.g. Bridge of Spies and MP4 output :)
ggtopI'm pretty sure this latest fix will work for that one as well.

[Mark_Venture]

@Mark_Venture

Just so you know, I ran the job using your INI and, sure enough, I got the same error. I've already identified what is happening, now I just have to put my finger on why. I also found out why it is incorrectly reporting the error as 0. I should have it fixed for the next release.

Good bug report. Thanks.
Thank you! Glad to know it wasn't just something on my end this time :)

[Lathe]

Thank you! Glad to know it wasn't just something on my end this time :)

If you have something on your end, you probably should get it looked at...

[jdobbs]

If you have something on your end, you probably should get it looked at...Or wipe it off.

[Mark_Venture]

If you have something on your end, you probably should get it looked at...
wow.. um.. yeah, i guess that didn't come across right... :eek:

[gonca]

wow.. um.. yeah, i guess that didn't come across right... :eek:
Don't worry, doctors can do amazing things with needles now a days

[MrVideo]

wow.. um.. yeah, i guess that didn't come across right... :eek:

It came across so that that you can be made the butt of their jokes. :eek:

[gonca]

It came across so that that you can be made the butt of their jokes. :eek:

No pun intended?

[MrVideo]

No pun intended?

Spelling is correct. :D

[jdobbs]

@gonca

Sorry about your image. I enabled it, but it was way too big so I removed it.

[gonca]

@gonca

Sorry about your image. I enabled it, but it was way too big so I removed it.
Okay, I should have checked closer

[Marban]

[11.29.16] Checking System Settings
- BD-Rebuilder v0.50.19
- Windows Version: 6.2 [9200]
- Working Path Free Space: 47,76GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- X264: Wrong version found
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok

bug? i downloaded the new Version from her.

[jdobbs]

[11.29.16] Checking System Settings
- BD-Rebuilder v0.50.19
- Windows Version: 6.2 [9200]
- Working Path Free Space: 47,76GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- X264: Wrong version found
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok

bug? i downloaded the new Version from her.See this post (http://forum.doom9.org/showthread.php?p=1785827#post1785827). My mistake.

[lauguru]

hello @jdobbs

It would be possible to add these values, in ARCHIVE MODE

main 10
level 5.1
bt.2020

http://image.prntscr.com/image/5741d2ab8769416da34c16da7327c4a8.png




http://www.dvd-logic.com/kite/screenshots.html

[jdobbs]

I have updated the first post of this thread with a link to the latest release of BD-RB (v0.50.20). Changes for this version:- Improved BD-5/9 full-backups. Sources that
do not use BD-J can be reencoded using the
full-backup mode, and should play on any
AVCHD compatible device. This includes all
imported and quick-play authored discs. A
small asterisk will display in the upper
left corner of the streams list next to
the disc title for any source/mode that
meets the criteria for an AVCHD compatible
full backup to BD-5/9.
- Updated code so that X264/LAVF can also be
used for ALTERNATE encoding. In previous
releases ALTERNATE encoding forced the use
of DirectshowSource (for resizing). Now
X264's internal resizing filters are used
when X264/LAVF is selected. This reduces
BD-RB's dependence on LAVF or FFDSHOW.
- Modified processes so the MENU_FORCE_QUICK
hidden option also applies to imports. This
makes if possible to create a menu even for
only one imported item.
- Corrected an issue in which the presence of
the MENU_ITEMS_PAGE hidden option would add
NEXT and LAST selections to a menu, even
though there is only one menu page created.
- Fixed an problem in which multipart sources
could cause an error 0000 in CreateAVS()
when SupTitle support is requested during
an ALTERNATE movie-only backup.
- Reinstituted the Donations popup. It only
appears once at startup for each version
release.
- Updated the included version of X264.EXE to
the latest release (r2744).
- Updated the included version of X264-64.EXE
to the latest release (r2744).
- Other minor corrections and cosmetic fixes.

[MrVideo]

I have updated the first post of this thread with a link to the latest release of BD-RB (v0.50.20). Changes for this version:- Modified processes so the MENU_FORCE_QUICK
hidden option also applies to imports. This
makes if possible to create a menu even for
only one imported item.
Thanks.

[jdobbs]

Thanks.You betcha', just trying to keep making it better.

[soneca]

Thanks for the new version jdobbs! https://s20.postimg.org/ug06pxifh/image.gif

[peris977]

Hello, when i inspect bd rebuilder, the voice x264 have this result: wrong version found, but i have install all programs in the list of this forum. Why i have this situation?
Thanks.

[MrVideo]

Hello, when i inspect bd rebuilder, the voice x264 have this result: wrong version found, but i have install all programs in the list of this forum. Why i have this situation?
Download the latest version.

[varekai]

Thanks for the update!

- Updated the included version of X264-64.EXE
to the latest release (r2744).

Is there still a slower fps speed issue using X264 internal LAVF for frameserving with the latest build of X264?
http://forum.doom9.org/showthread.php?p=1779038#post1779038

If so I'm gonna switch to DirectshowSource or DGDecNV, old habits die hard...

Is there any fps difference, maybe faster, using DGDecNV with SLI GPU's?

[jdobbs]

Thanks for the update!

- Updated the included version of X264-64.EXE
to the latest release (r2744).

Is there still a slower fps speed issue using X264 internal LAVF for frameserving with the latest build of X264?
http://forum.doom9.org/showthread.php?p=1779038#post1779038

If so I'm gonna switch to DirectshowSource or DGDecNV, old habits die hard...

Is there any fps difference, maybe faster, using DGDecNV with SLI GPU's?I haven't tested that version with LAVF yet, but for the last couple releases BD-RB includes an older version of X264 that gets used automatically when X264/LAVF is selected -- so it shouldn't matter anyway.

I don't know the answer to your SLI GPU question.

[Seajunk]

Is there any fps difference, maybe faster, using DGDecNV with SLI GPU's?

Cuda, nvdec and nvenc dont support SLI configurations directly, they will see all your cards but as a developer you have to address them individually and its far easier just to hit one card with one job. DGDecNV is probably hitting card 0, the primary card.

[videoh]

DGDecNV is probably hitting card 0, the primary card. By default, yes, but the desired device can be specified with an INI file option. DGDecNV does not use SLI, nor does CUVID.

[varekai]

OK, thanks guys for the info!
Next encode I'll try both X264 internal LAVF and DGDecNV, using primary card and then compare the time for complete encode.

[Lathe]

I haven't tested that version with LAVF yet, but for the last couple releases BD-RB includes an older version of X264 that gets used automatically when X264/LAVF is selected -- so it shouldn't matter anyway.

I'm sorry JD, but I don't understand... You say that you have included the newest x264.exe and x264-64.exe, and yet before you suggested using an older version (such as the one 5012) because the newer versions WERE indeed slower using LAVF, which I always use. But, you say here that it doesn't matter... I'm afraid I don't get it. Is this indeed the NEWEST version and you included it because it DOES run correctly now. Or you put the OLD version in as before so that there is no slowdown...???

Oh, wait a minute... I think I just answered myself... :cool: Do you mean ONLY when LAVF is selected THEN an older version is used, right...? So, it is all built in now and we DON'T have to go back and substitute the x264.exe & x264-64.exe from version 5012? We can just use it as is?

[varekai]

If I understand it right the
x264L.exe
x264L-64.exe
are the old (faster) build 0.148.2665.0
which will automatically load when X264 internal LAVF is chosen.

[jdobbs]

If I understand it right the
x264L.exe
x264L-64.exe
are the old (faster) build 0.148.2665.0
which will automatically load when X264 internal LAVF is chosen.Yes. BD-RB automatically uses the older version if you select X264/LAVF. So, you don't have to do any renaming or replacement.

[Lathe]

Yes. BD-RB automatically uses the older version if you select X264/LAVF. So, you don't have to do any renaming or replacement.

Great, thanks JD!

[jdobbs]

I haven't tested that version with LAVF yet, but for the last couple releases BD-RB includes an older version of X264 that gets used automatically when X264/LAVF is selected -- so it shouldn't matter anyway.

I don't know the answer to your SLI GPU question.This is really weird. I tested the new version, and it seems that the problem has gone away. Running in X264/LAVF is just as fast as the DirectshowSource() encode (actually a couple of fps faster). That's good, right?

But then I went back through all the X264 versions, and I can't seem to be able to repeat the issue at all anymore. All of them seem to be about the same speed. I'm really confused now.

[Djuby]

Hi,

Not sure if I'm doing something wrong, but since I upgraded to the latest version I have the following issue: in Movie-Only Backup with Alternate Movie-Only Output (MKV Container, 1920x1080, 640Kbs DD5.1) and two pass target size 8152 I only get 10 min of the movie encoded. Any help will be greatly appreciated. Here is the log from the last encode:

----------------------
[12/09/16] BD Rebuilder v0.50.20
[15:17:28] Source: ARIES_DISC1_WL_00800
- Input BD size: 36.51 GB
- Approximate total content: [02:12:56.301]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1920x1080, 640Kbs DD5.1
- Quality: High Quality (Default)
- Automatic cropping of borders enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[15:17:29] PHASE ONE, Encoding
- [15:17:29] Processing: VID_00800 (1 of 1)
- [15:17:29] Extracting A/V streams [VID_00800]
- [15:19:26] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 191,240 frames
- Bitrate: 7,732 Kbs
- [15:19:26] Reencoding: VID_00800, Pass 1 of 2
- [15:29:25] Reencoding: VID_00800, Pass 2 of 2
[15:30:15]PHASE ONE aborted by user request
----------------------

Best regards,
Djuby

[Mark_Venture]

I have updated the first post of this thread with a link to the latest release of BD-RB (v0.50.20). Changes for this version:
- Fixed an problem in which multipart sources
could cause an error 0000 in CreateAVS()
when SupTitle support is requested during
an ALTERNATE movie-only backup.

Looks great!! Thank you!!

[jdobbs]

Hi,

Not sure if I'm doing something wrong, but since I upgraded to the latest version I have the following issue: in Movie-Only Backup with Alternate Movie-Only Output (MKV Container, 1920x1080, 640Kbs DD5.1) and two pass target size 8152 I only get 10 min of the movie encoded. Any help will be greatly appreciated. Here is the log from the last encode:

----------------------
[12/09/16] BD Rebuilder v0.50.20
[15:17:28] Source: ARIES_DISC1_WL_00800
- Input BD size: 36.51 GB
- Approximate total content: [02:12:56.301]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1920x1080, 640Kbs DD5.1
- Quality: High Quality (Default)
- Automatic cropping of borders enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[15:17:29] PHASE ONE, Encoding
- [15:17:29] Processing: VID_00800 (1 of 1)
- [15:17:29] Extracting A/V streams [VID_00800]
- [15:19:26] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 191,240 frames
- Bitrate: 7,732 Kbs
- [15:19:26] Reencoding: VID_00800, Pass 1 of 2
- [15:29:25] Reencoding: VID_00800, Pass 2 of 2
[15:30:15]PHASE ONE aborted by user request
----------------------

Best regards,
DjubyTry turning off auto-cropping and see if you get the same results.

[Djuby]

Try turning off auto-cropping and see if you get the same results.
Will try it and report back.

Edit: Same result :-(

[HWK]

Hi,

Not sure if I'm doing something wrong, but since I upgraded to the latest version I have the following issue: in Movie-Only Backup with Alternate Movie-Only Output (MKV Container, 1920x1080, 640Kbs DD5.1) and two pass target size 8152 I only get 10 min of the movie encoded. Any help will be greatly appreciated. Here is the log from the last encode:

----------------------
[12/09/16] BD Rebuilder v0.50.20
[15:17:28] Source: ARIES_DISC1_WL_00800
- Input BD size: 36.51 GB
- Approximate total content: [02:12:56.301]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1920x1080, 640Kbs DD5.1
- Quality: High Quality (Default)
- Automatic cropping of borders enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[15:17:29] PHASE ONE, Encoding
- [15:17:29] Processing: VID_00800 (1 of 1)
- [15:17:29] Extracting A/V streams [VID_00800]
- [15:19:26] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 191,240 frames
- Bitrate: 7,732 Kbs
- [15:19:26] Reencoding: VID_00800, Pass 1 of 2
- [15:29:25] Reencoding: VID_00800, Pass 2 of 2
[15:30:15]PHASE ONE aborted by user request
----------------------

Best regards,
Djuby

is this only disc in question causing issues or other as well.

[Lathe]

This is really weird. I tested the new version, and it seems that the problem has gone away. Running in X264/LAVF is just as fast as the DirectshowSource() encode (actually a couple of fps faster). That's good, right?

But then I went back through all the X264 versions, and I can't seem to be able to repeat the issue at all anymore. All of them seem to be about the same speed. I'm really confused now.

Oh great... Our Leader in confused...

Talk about your world of Reality being shaken... :eek:

[Djuby]

is this only disc in question causing issues or other as well.
Good call HWK. Did another disk and all was OK. With the problem one I imported the M2TS and looks like there is no issue so far - first pass was OK, now doing the second one. The question is, why with the previous version of the BD Rebuilder (v0.50.18) the issue was not present?

Best regards,
Djuby

[MrVideo]

[15:30:15]PHASE ONE aborted by user request
I'm curious as to why it said that you requested that the job be stopped.

[Lathe]

FWIW, as far as any of you who also use x264 presets on occasion, I just did an encode with the x264-64.exe used in the latest version of BDRB and I was surprised that with the preset=slow setting (blu-ray compatible added too of course) that now that setting uses me=hex instead of umh. I don't fully understand everything about it, but I had asked on Videohelp because my encode had that parameter change and I wondered why. According to the VideoLan link in the answer I was given, the developers apparently decided to swap out me=umh with hex AND substitute trellis=2 instead of 1 because they said the net effect was better and took about the same amount of time. So, those 2 changes AFAIK were made to the Slow setting if any of you happened to be unaware of it, because I sure didn't know...

[Djuby]

Will try it and report back.

Edit: Same result :-(

is this only disc in question causing issues or other as well.

I'm curious as to why it said that you requested that the job be stopped.

There was no reason to continue with the second pass after just 10 min of encoding in the first one.

[Djuby]

I'm curious why sometimes it happens that the audio goes out of sync in the rebuilt MKV file. It plays well for some time and after a scene with a lot of action (explosion for instance) the audio is out of sync, regardless if the original audio was kept or re-encoded into DD5.1.

Djuby

[jdobbs]

I'm curious why sometimes it happens that the audio goes out of sync in the rebuilt MKV file. It plays well for some time and after a scene with a lot of action (explosion for instance) the audio is out of sync, regardless if the original audio was kept or re-encoded into DD5.1.

DjubyI haven't had that problem. Anyone else seen this?

[MrVideo]

I'm curious why sometimes it happens that the audio goes out of sync in the rebuilt MKV file. It plays well for some time and after a scene with a lot of action (explosion for instance) the audio is out of sync, regardless if the original audio was kept or re-encoded into DD5.1.
I personally believe that there is something wrong with your playback equipment.

Until it is played and the audio stream decoded by the amp, it is just a digital stream. There is no way to know what the audio contains when handled by a program like BDRB. Even if recoded, a "loud" section or a "quiet" section isn't going to cause anything to go wrong with the sync.

Play it on another device, computer, etc.

[MrVideo]

While building an import disc I've noticed a few minor strange things.

After I imported the files, it said that all 12 files met the 10 min import criteria. But, two of the files are well under 10 minutes.
After the job was done importing and putting together the menu and BD file layout, the list of streams did not include the two files under 10 minutes; but the two files are on the disc and included in the menu.
The disc only has two menus, yet there is a PREV on the first page and a NEXT on the 2nd page. Technically there is no page before 1 and no page after 2. While the menu selections work just fine, it is just a little strange.


I wish there was a way in order to be able to go back and keep the text that is on the menu so that if I have to remake the structure, because I had to replace one of the video files (for example), I wouldn't have to re-enter all of the text in the menu.

After redoing the import, maybe BDRB can ask if the previous menu should be used and presented for editing. If the number of imported items is different, then the user should be presented with a fresh menu to edit.

[Djuby]

I personally believe that there is something wrong with your playback equipment.

Until it is played and the audio stream decoded by the amp, it is just a digital stream. There is no way to know what the audio contains when handled by a program like BDRB. Even if recoded, a "loud" section or a "quiet" section isn't going to cause anything to go wrong with the sync.

Play it on another device, computer, etc.

I use MPC-HC for playback. The audio problem is always on the same spot when played over again. I also noticed there is an image distortion (maybe a bad transfer from the BD), like very low bitrate (blocks). Maybe those couple of bad frames are causing the misalignment of audio and video?!

[MrVideo]

I use MPC-HC for playback. The audio problem is always on the same spot when played over again. I also noticed there is an image distortion (maybe a bad transfer from the BD), like very low bitrate (blocks). Maybe those couple of bad frames are causing the misalignment of audio and video?!
It does help in trouble shooting that all of the info be provided. This is an important piece of information.

When there is a glitch in the video and audio, sync loss is very much an issue. When that glitched area is run thru programs like BD-RB, things like this can and do happen.

You need a clean source.

[jdobbs]

While building an import disc I've noticed a few minor strange things.

After I imported the files, it said that all 12 files met the 10 min import criteria. But, two of the files are well under 10 minutes.
After the job was done importing and putting together the menu and BD file layout, the list of streams did not include the two files under 10 minutes; but the two files are on the disc and included in the menu.
The disc only has two menus, yet there is a PREV on the first page and a NEXT on the 2nd page. Technically there is no page before 1 and no page after 2. While the menu selections work just fine, it is just a little strange.


I wish there was a way in order to be able to go back and keep the text that is on the menu so that if I have to remake the structure, because I had to replace one of the video files (for example), I wouldn't have to re-enter all of the text in the menu.

After redoing the import, maybe BDRB can ask if the previous menu should be used and presented for editing. If the number of imported items is different, then the user should be presented with a fresh menu to edit.The "Prev" on the first page goes to the last page, which is your case is page 2. The "Next" on the last page goes to the first page (which in your case is page 1).

It's meant as a time saver so you don't have to click back through or forward through all interim pages. But in your case it is a little odd, since there are only two choices and they both go to the same page. I'll look at it, and maybe change it so the "Prev" on the first page and the "Next on the last page aren't there for some small number of pages.

As for remembering the titles, BD-RB will do what you're asking for DVDs and BD imports, but it's a little harder for files (because you may be importing only a couple of files from a directory filled with files). But I'll see what I can do.

[jdobbs]

I use MPC-HC for playback. The audio problem is always on the same spot when played over again. I also noticed there is an image distortion (maybe a bad transfer from the BD), like very low bitrate (blocks). Maybe those couple of bad frames are causing the misalignment of audio and video?!The image distortion you mentioned is almost always an indicator of a bad rip. There are frames missing (or inserted) at that point, and that is why the audio goes out of sync. About all you can do is a re-rip.

[MrVideo]

The "Prev" on the first page goes to the last page, which is your case is page 2. The "Next" on the last page goes to the first page (which in your case is page 1).
Yep, that is exactly what it does.
It's meant as a time saver so you don't have to click back through or forward through all interim pages. But in your case it is a little odd, since there are only two choices and they both go to the same page. I'll look at it, and maybe change it so the "Prev" on the first page and the "Next on the last page aren't there for some small number of pages.
I see what you are trying to accomplish. Let's take for example a three-page menu. If on the last page, instead of clicking on PREV twice to get to the first page, you just click on NEXT. If on the first page, click on PREV to get to the last. Instead of NEXT and PREV for button names, how about FIRST and LAST, respectively. Then the button names will better describe the actual function. (Only on the first and last pages, otherwise PREV and NEXT on all other pages.)
As for remembering the titles, BD-RB will do what you're asking for DVDs and BD imports, but it's a little harder for files (because you may be importing only a couple of files from a directory filled with files). But I'll see what I can do.
Ah yes. I wasn't thinking about only some files from the many. :D In my case, I work from a directory only containing the files I'll be including, as they will always be from projects. Even with only choosing some files from a bunch, asking the user if they wanted to re-edit the menu could still apply. If importing from a completely different directory, the question would not be asked.

Even if a user imported different files from the same directory, they might be related and re-editing a previous menu might be easier than starting from scratch, i.e., it would act as a template.

I look forward to what you come up with.

Thanks.

[Mark_Venture]

Anyone try a "Alt Movie Only w/intact audio" on The Secret Life of Pets (USA)?

I'm getting the attach pop-up message when BD Rebuilder is starting to extract... If I choose YES, it continues processing, completes fine, and I get my output MKV.

Playing the MKV on my Fire TV in Kodi/SPMC, it reports track 1 as Dolby TrueHD 7.1. Track 2 is unknown 5.1, and track 3 is AC3 Stereo. All three sound the way I expect (sounds the same as when using the disc in my bluray player).

This is the first time I got that message. I'm guessing its something specific with this disc?

EDIT: I also get this message (a few times with other PID's) when doing a full backup output BD-25.

[jdobbs]

Anyone try a "Alt Movie Only w/intact audio" on The Secret Life of Pets (USA)?

I'm getting the attach pop-up message when BD Rebuilder is starting to extract... If I choose YES, it continues processing, completes fine, and I get my output MKV.

Playing the MKV on my Fire TV in Kodi/SPMC, it reports track 1 as Dolby TrueHD 7.1. Track 2 is unknown 5.1, and track 3 is AC3 Stereo. All three sound the way I expect (sounds the same as when using the disc in my bluray player).

This is the first time I got that message. I'm guessing its something specific with this disc?That message comes from DGIndexNV. You can make that go away and take the default with an INI setting (DGIndexNV.ini in the folder where you have it installed). I believe it is ResponseOnAudioMismatch=0 (at least that's what I have in my INI).

Or, easier I guess, you can open up DGIndexNV and set the default response under the Options menu.

[Mark_Venture]

That message comes from DGIndexNV. You can make that go away and take the default with an INI setting (DGIndexNV.ini in the folder where you have it installed). I believe it is ResponseOnAudioMismatch=0 (at least that's what I have in my INI).

Or, easier I guess, you can open up DGIndexNV and set the default response under the Options menu.Awesome! Thanks! I didn't know that. (I just installed and left defaults)

If I go into the DGIndexNV app, and select "use PAT/PMT" it sets ResponseOnAudioMismatch=1 in the ini. ResponseOnAudioMismatch=0 is "prompt" which is how it was set.

Which is normally preferred? PAT/PMT or Detected? (for now, I've set it for Use PAT/PMT)

[jdobbs]

Yeah, I think that's right, but it's been a while. I just noticed that setting it to "0" tells it to prompt myself, so that wouldn't be it. Since my card is no longer supported by DGDecNV (because of Windows 10), I've been using DirectShowSource.

[jdobbs]

Well I'll be damned. I'm glad you mentioned this. When I installed Windows 10 I read the information that DGDecNV wouldn't work with older cards (and mine is pretty old) -- and I just shrugged my shoulders and stopped using it. When I was opening DGIndexNV responding your your bug report, I tried an index a file for the hell of it. It told me the key was not valid. "Huh?" I thought. So I downloaded another key from Neuron2's site. Well... it started working again. All this time I though it was my card -- when what happened was that Windows 10 changed my machine ID.

Too bad I wasn't born smarter. I should have noticed that a long time ago.

That's great. I've always preferred DGDecNV!

[videoh]

Which is normally preferred? PAT/PMT or Detected? (for now, I've set it for Use PAT/PMT) It's an option because it is possible that the PAT/PMT could be wrong, and it is possible that the detected type could be wrong. I have seen both. If I had to, I would say that it's less likely that the PAT/PMT would be wrong, so if you must set a default behavior, then PAT/PMT may be preferable. Just remember if you run into audio problems for a specific stream to try it the other way.

In your case, the detected type was likely wrong. It is a heuristic detection that can be spoofed by header emulation.

Well I'll be damned. I'm glad you mentioned this. When I installed Windows 10 I read the information that DGDecNV wouldn't work with older cards (and mine is pretty old) -- and I just shrugged my shoulders and stopped using it. When I was opening DGIndexNV responding your your bug report, I tried an index a file for the hell of it. It told me the key was not valid. "Huh?" I thought. So I downloaded another key from Neuron2's site. Well... it started working again. All this time I though it was my card -- when that happened was that Windows 10 changed my machine ID. Actually, it was the case that Windows could change the machine ID only for earlier releases of DGDecNV. For recent versions, it is only the motherboard serial number that controls things. Perhaps you upgraded from an earlier version and ran into the new licensing mechanism.

What card do you have? We can't rule out that nVidia has improved the Win10 support for older cards in recent driver releases.

I've always preferred DGDecNV! Me too.

[jdobbs]

What card do you have? We can't rule out that nVidia has improved the Win10 support for older cards in recent driver releases.GeForce GT 520

[Sharc]

For 3D backups I can select mode "Movie and menus" and "SBS output" which will keep the original menu and put the movie SBS in the .m2ts container / BD file structure.
My HW player will however stall. Now my questions:
- Is this only an issue of my player/TV?
- or is the SBS setting illegal for BD output, and only applicable for alternate output .mkv / .mp4? (and if so, should the selection be greyed out in the BD RB menu?)
- or should the original clipinf / playlist be modified to instruct the player/TV to play the SBS .m2ts as 3D?

Thanks.

[jdobbs]

For 3D backups I can select mode "Movie and menus" and "SBS output" which will keep the original menu and put the movie SBS in the .m2ts container / BD file structure.
My HW player will however stall. Now my questions:
- Is this only an issue of my player/TV?
- or is the SBS setting illegal for BD output, and only applicable for alternate output .mkv / .mp4? (and if so, should the selection be greyed out in the BD RB menu?)
- or should the original clipinf / playlist be modified to instruct the player/TV to play the SBS .m2ts as 3D?

Thanks.Half SBS isn't illegal. The player has no idea that it is side-by-side, since it is simply two pictures combined into a standard 1920x1080 format (typically, you could also do 720p or 480/576 if you wanted). The player just sends the 1080p picture to the playback device which then does the splitting/stretching of the SBS for 3D playback.

It would be, however, illegal to attempt to create a Full-SBS 3840x1080p picture and attempt to play it SBS from a BD player. To get full SBS you need standard 3D output to a 3D player. But I don't think I even allow that in BD-RB (I'd have to check, as it's been a while since I worked on the 3D code).

[videoh]

GeForce GT 520 Good to hear that nVidia is progressing with the Win10 driver support for older architectures. ;)

[sieve]

I have a 4 DVD set of a Sweedish TV show. I wanted to compile all episodes onto 1 BD that will play in the U.S. The source is 576i 25fps. I tried a couple different methods and have been unsuccessful in getting the video on the output BD to display when played in a BD player. Subtitles and audio play fine. I'll note that audio and video play fine on the same TV if I play the BD through a computer.

My config settings are pasted below.

[Options]
VERSION=0.50.0.20
ENCODER=0
MODE=3
ENCODE_QUALITY=3
ONEPASS_ENCODING=0
AUTO_QUALITY=0
TARGET_SIZE=23500
AUTO_BURN=2
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=0
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=1
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=1
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=22000
PRIORITY_CLASS=0
MOVIEONLY_TYPE=0
ALTCRF=23
ALT_TARGET=2000
ALT_CRF_TARGET=1024
ALTMETHOD=2
ALTAUTOCROP=0
IMPORT_PAL_TO_FILM=1
[Paths]
SOURCE_PATH=C:\WORKING\IMPORTS\BRIDGE_S3\
WORKING_PATH=C:\WORKING\


The first time I tried, I imported DVD(s) quick reauthored. The one thing I notices in the stream window as that each video chapter (episode) was MPEG-2, 576i, 25fps. I assumed that the 25fps would be a problem. I thought that IMPORT_PAL_TO_FILM=1 was supposed to convert that to 23.975fps in the import process, but apparently it didn't. I then ran a full backup to a BD-25 .iso. The burned BD w.ould not display video when played in a BD player. Video remained at 576i 25 fps.

The second time I tried, I imported DVD(s) quick reauthored. Same 576i 25fps in the stream window. I then did alternate movie-only output to MKV, Intact Video, Intact Audio. I then imported these video files. Same 576i 25 fps. I then ran full backup to a BD-25 .iso. Same problem as above.

So, my questions are:
Is it possible to do what I am attempting to do in BD rebuilder?
If so, what settings/steps am I doing incorrectly?

Thanks in advance!

[Sharc]

@sieve
576i25 is perfectly Blu-ray compliant, even for U.S. There is no need to deinterlace and to convert it to 23.976fps for U.S.
If I interpret your settings correctly you try to produce a 576p23.976 output which is not Blu-Ray compliant, hence your player may refuse to play.
I would try again without deinterlacing and without frame rate conversion.

[Sharc]

Half SBS isn't illegal. The player has no idea that it is side-by-side, since it is simply two pictures combined into a standard 1920x1080 format (typically, you could also do 720p or 480/576 if you wanted). The player just sends the 1080p picture to the playback device which then does the splitting/stretching of the SBS for 3D playback.

It would be, however, illegal to attempt to create a Full-SBS 3840x1080p picture and attempt to play it SBS from a BD player. To get full SBS you need standard 3D output to a 3D player. But I don't think I even allow that in BD-RB (I'd have to check, as it's been a while since I worked on the 3D code).
It's definitely Half-SBS in my case.
It seems to be a player issue (or perhaps a poor burn):
- Samsung BD-J5500 fails
- Samsung HT-F4500 works
- LG BP440 fails
"Fail" means it loads the BD25 Disc but refuses to play the menu. The player spins full speed (noisy), TV screen is black....
Anyway, Half-SBS in .mkv container works with all 3 players.

Edit:
... No, it was not a bad burn. There seems to be a problem with the original menu which appears to make reference to the no longer existing MVC (dependent) stream. Possibly the culprit are the 3D buttons in the original menu. It's all a bit speculative though ....

I re-imported the disc and made a Quick Menu instead of keeping the original menu. Now the half-SBS BD plays fine on all 3 players with the quick-menu using the original backdrop.

Edit2:
Some more findings:
- The original menu backdrop (a static picture) and the feature are both 3D ssif structured on the original disk.
- BD-RB recreates the menu as in-muxed stereo, and converts the feature (as requested) to Half-SBS. The in-muxed 3D menu does however not play with 2 of my players.
- When I re-import the disc, the menu backdrop is encoded as 2D (base view) and plays ok in 2D. The Half-SBS feature plays correctly stereoscopic after setting the TV to SBS.
After all my conclusion is that it seems to be a player issue, as these players apparently refuse to play the in-muxed menu backdrop.

[jdobbs]

I tried a couple different methods and have been unsuccessful in getting the video on the output BD to display when played in a BD player.@sieve
576i25 is perfectly Blu-ray compliant, even for U.S. There is no need to deinterlace and to convert it to 23.976fps for U.S.
If I interpret your settings correctly you try to produce a 576p23.976 output which is not Blu-Ray compliant, hence your player may refuse to play.
I would try again without deinterlacing and without frame rate conversion.I'd be very surprised if 576p/23.976 didn't play. The player is required to support it (for secondary video) -- and I've never seen a player that wouldn't play SD @ 23.976 for primary video, even though it isn't strictly compliant.

I'd have to see what the video and audio AVS files looks like that were used for the encode. Since I'm in an NTSC zone, I convert 50fps to 23.976 all the time. All I set is IMPORT_PAL_TO_FILM=1.

I'll play around with it today if I get some extra time.

[Sharc]

I'd be very surprised if 576p/23.976 didn't play. The player is required to support it (for secondary video) ....
Are you really positive that 576p23.976 is included for secondary video for Blu-ray? I thought that only 480p23.976 is accepted for secondary video, but not 576p. Maybe I am wrong. I agree however that players will usually play it anyway.

[jdobbs]

Are you really positive that 576p23.976 is included for secondary video for Blu-ray? I thought that only 480p23.976 is accepted for secondary video, but not 576p. Maybe I am wrong. I agree however that players will usually play it anyway.Hmm.. I'll go back and look. But, if you are converting to NTSC you would be resizing to 480p anyway.

[Edit]

According to Chapter 8 of that standard (para. 8.3.1), when the primary video is 1920x1080, 1440x1080 or 1280x720 the secondary video can be 720x480 or 720x576. Also 576p is an acceptable video type (it is video_format=7) in the StreamCodingInfo() table.

I assumed that would infer that a primary stream that is progressive would also require a progressive secondary stream at the same frame rate.

But... when looking at Table 9-49 in the standard, – which shows the allowed combinations of primary/secondary video formats, it appears that 720x576 (p or i) is only allowed when the primary frame rate is either 25fps or 50fps. So the bottom line is that 576p is supported -- but only at 25fps, not at 23.976fps.

So you are correct. 576p/23.976 is not a legal format.

[Sharc]

.... So the bottom line is that 576p is supported -- but only at 25fps, not at 23.976fps.
Yep, exactly.

[ggtop]

I have updated the first post of this thread with a link to the latest release of BD-RB (v0.50.20). Changes for this version:- Fixed an problem in which multipart sources
could cause an error 0000 in CreateAVS()
when SupTitle support is requested during
an ALTERNATE movie-only backup.
- Reinstituted the Donations popup. It only
appears once at startup for each version
release.

Hi jdobbs,
many thanks for the current version. Just want to let you know it fixes MP4 output with hard-codes subs on "Brigde of spies". Just tested it.

Regarding donation which I would to like to do I have a question: Do you want "us" to adress any gift cards directly to your mail address from amazon.com or send just the code to you (which I did earlier)?

ggtop

[meadrocks]

What email address do we use for the Amazon donation?

[jdobbs]

What email address do we use for the Amazon donation?Either dvd-rb@jdobbs.net or dvd-rb@dvd-rb.com. Alternatively a PM with the code works just as well.

Thanks for asking.

[Lathe]

This is weird... I've done this many times before with BDRB, which is after creating a movie only disc I go back and blank the main feature and have BDRB create an Xtras only disc with full menus. I always leave the output size to BD-25 or thereabouts and BDRB always creates a disc WITHOUT re-encoding anything. In the past, it always has used 'keeping original video'. However, this time, even though as you can see I have specifically includes the force no encode in the ini, it STILL is re-encoding all the video files.

Does anyone know why...? Did I miss some setting in the setup?

[Options]
VERSION=0.50.0.20
ENCODER=0
MODE=0
ENCODE_QUALITY=1
ONEPASS_ENCODING=0
AUTO_QUALITY=1
FORCE_NOENCODE=1
IVTC_480i=0
IVTC_METHOD=0
AUTO_QUALITY=0

AUTO_BIAS=3
B_PYRAMID=1
QUICK_CRF=24
ENABLE_TEST=1
ENABLE_BLANKING=1

ARCHIVE_ENABLE=1
ARCHIVE_LIMIT=1
ARCHIVE_265=0
ARCHIVE_AUDIO_100
ARCHIVE_CRF=18

KEEP_HD_LPCM=1
USE_ZLIB=0

ALTERNATE_BLURAY=0
ENCODER_MENU=1
MBTREE=1

IMPORT_THRESHOLD=1
QUICK_PLAY_THRESHOLD=1
MENU_AUTO_BACKGROUND=1
MENU_AUTO_DVDAUDIO=1
AUTO_QUALITY=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;

QUICK_EXTRAS=1


TARGET_SIZE=23500
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=1
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=2
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=1
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23700
PRIORITY_CLASS=0
[Paths]
WORKING_PATH=C:\_______MEDIA\_BDRB\
SOURCE_PATH=F:\00000\

Here is the partial log before I aborted the process:


----------------------
[12/15/16] BD Rebuilder v0.50.20
[23:57:36] Source: 00000
- Input BD size: 8.54 GB
- Approximate total content: [04:36:32.008]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Better (Faster), Two Pass
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[23:57:45] PHASE ONE, Encoding
- [23:57:45] Processing: VID_00021 (1 of 24)
- [23:57:45] Extracting A/V streams [VID_00021]
- [23:57:49] Reencoding video [VID_00021]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 483 frames
- [23:57:49] Reencoding: VID_00021, Pass 1 of 1
[23:57:56]PHASE ONE aborted by user request

***EDIT

Wait a minute... I THINK I might know why... This is what the VID.avs looks like:

#Created by BD Rebuilder - v0.50.20
DirectshowSource("F:\00000\00021.m2ts", fps=29.97, framecount=483, audio=false)
ConvertToYV12()
LoadPlugin("D:\EXECUTABLES\BD-RBV05020\BD_Rebuilder\tools\decomb521.dll")
FieldDeinterlace(blend=true)
ConvertToYV12().AssumeFPS(30000,1001)

So, apparently it is deinterlacing the video which means it has to re-encode, right? Maybe I need to UNcheck 'deinterlace' in the setup menu. I will try that now...

***EDIT 2

DANG! No, that didn't do it, Grrrrr! :mad:

***EDIT 3

Okay, I tried the last version of BDRB (5018) and it is doing it just fine. Clearly I MUST have something set wrong / differently in the ini or something...

***EDIT 4

Yeah... it was SOMETHING in the ini, I don't know what yet, but I just simply copied the ini of version 5018 over to the new one and re-ran it and it is just fine. I guess I'll poor over the two different ini's to see what it was...

Isn't it nice that I can come here and just talk to myself for about half an hour and then I feel ALL better... :)

[Sharc]

@jdobbs
Did you change anything in the Quick-Play backup?
The quick menu shows as expected, but when I press the feature the player stops and returns to the Home screen. There is no way to play the movie.
It's a movie-only backup, so the quick-menu has only a single selection: the feature.

The quick-menu works fine with older disk from former releases.

Edit:
Importing the non-playable disc (using the BD folder structure which was still on the HD) and re-authoring the quick-menu eventually produced a playable disc.
I am wondering now whether the first attempt failed because the original source was an .iso (3D) on an external USB Drive?
Also to mention that the default text for the quick-menu was kept in the first run, although I edited it. The edit was effective with the re-authored disc from the 2nd run.

[sieve]

@sieve
576i25 is perfectly Blu-ray compliant, even for U.S. There is no need to deinterlace and to convert it to 23.976fps for U.S.
If I interpret your settings correctly you try to produce a 576p23.976 output which is not Blu-Ray compliant, hence your player may refuse to play.
I would try again without deinterlacing and without frame rate conversion.

I tried. Unchecked "use deinterlaced on interlaced sources". Removed IMPORT_PAL_TO_FILM=1. Same result. Blu-Ray player would not display video.

[sieve]

I'd have to see what the video and audio AVS files looks like that were used for the encode. Since I'm in an NTSC zone, I convert 50fps to 23.976 all the time. All I set is IMPORT_PAL_TO_FILM=1.

I think this is what I'm trying to accomplish also...
I just can't seem to get the settings right to make it happen.

[jdobbs]

I tried. Unchecked "use deinterlaced on interlaced sources". Removed IMPORT_PAL_TO_FILM=1. Same result. Blu-Ray player would not display video.Can you provide me with a short clip of the output?

[sieve]

Can you provide me with a short clip of the output?

Sure. Which specific file should I send, and what can I use to extract a short section?

[jdobbs]

Sure. Which specific file should I send, and what can I use to extract a short section?You can use the split/cut function of TSMUXER. But, before we go to that trouble, let me find a short PAL source and do some testing.

[sieve]

You can use the split/cut function of TSMUXER. But, before we go to that trouble, let me find a short PAL source and do some testing.

I split off some video, but even 1 second is too large to attach.

[jdobbs]

I split off some video, but even 1 second is too large to attach.Send it via e-mail to dvd-rb@jdobbs.net

[jdobbs]

Sure. Which specific file should I send, and what can I use to extract a short section?I think the problem is in the conversion to FILM. As was mentioned by Sharc, it may be that the video is staying 720x576 and only the framerate was changing. I normally import HD -- and in that instance changing only the framerate would work. In fact, it may even be possible that nothing is being changed at all during import (because it is an SD and DVD source).

Testing in progress.

[jdobbs]

Yep. I'd forgotten. The IMPORT_PAL_TO_FILM parameter only applies to video file imports (not DVD), note what I've highlighted:

IMPORT_PAL_TO_FILM=n n = 0/1 - Default=0, if set to 1, imported 25fps video file sources are converted to 23.976

I'll have to create another setting for this.

In the meantime, what you can do is import the DVD, then output it to MKV files using the "MKV, Intact Video, Intact Audio" setting. You can then select all the MKV files and import them. Assuming IMPORT_PAL_TO_FILM is set, they will be converted to 720x480@23.976 when the pseudo-BD source is reencoded.

[sieve]

In the meantime, what you can do is import the DVD, then output it to MKV files using the "MKV, Intact Video, Intact Audio" setting. You can then select all the MKV files and import them. Assuming IMPORT_PAL_TO_FILM is set, they will be converted to 720x480@23.976 when the pseudo-BD source is reencoded.

I read that in the thread somewhere and did try that the second time (see below). But it didn't work. It didn't change the resolution or frame rate.

The first time I tried, I imported DVD(s) quick reauthored. The one thing I notices in the stream window as that each video chapter (episode) was MPEG-2, 576i, 25fps. I assumed that the 25fps would be a problem. I thought that IMPORT_PAL_TO_FILM=1 was supposed to convert that to 23.975fps in the import process, but apparently it didn't. I then ran a full backup to a BD-25 .iso. The burned BD w.ould not display video when played in a BD player. Video remained at 576i 25 fps.

The second time I tried, I imported DVD(s) quick reauthored. Same 576i 25fps in the stream window. I then did alternate movie-only output to MKV, Intact Video, Intact Audio. I then imported these video files. Same 576i 25 fps. I then ran full backup to a BD-25 .iso. Same problem as above.

[Sharc]

Well, apart from squashing a possible bug, my question would still be why people want to convert 576i/25fps to 480p/23.976fps? Blu-ray is a global standard, there is no need to convert from "PAL" to "NTSC" .....

[jdobbs]

I read that in the thread somewhere and did try that the second time (see below). But it didn't work. It didn't change the resolution or frame rate.When is it failing? Do you have a menu? Is it failing when you try the menu or when you select a title? I just did the procedure I mentioned with no menu and it worked fine. I'll try one with a menu next. I have my doubts, though, since the menu is always 1920x1080...

[sneaker_ger]

Well, apart from squashing a possible bug, my question would still be why people want to convert 576i/25fps to 480p/23.976fps? Blu-ray is a global standard, there is no need to convert from "PAL" to "NTSC" .....
Not all BD-ROM Players support 50Hz video formats.
http://www.blu-raydisc.com/assets/Downloadablefile/BD-ROM_Audio_Visual_Application_Format_Specifications-18780.pdf (3.3.1 + 3.3.2)

[sieve]

When is it failing? Do you have a menu? Is it failing when you try the menu or when you select a title? I just did the procedure I mentioned with no menu and it worked fine. I'll try one with a menu next. I have my doubts, though, since the menu is always 1920x1080...

There is a menu that lists the 12 episodes. That displays fine. When I select an episode to play, it does play, but does not display video. Only audio and subtitles work. The TV does flash a message that the resolution changed. Oddly, it says "576p" even though the actual source is 576i.

[sieve]

Send it via e-mail

I sent you a 3 second clip

[jdobbs]

When is it failing? Do you have a menu? Is it failing when you try the menu or when you select a title? I just did the procedure I mentioned with no menu and it worked fine. I'll try one with a menu next. I have my doubts, though, since the menu is always 1920x1080...I sent you a 3 second clipI just tried one with a menu, and it worked fine as well. The video is 480p/23.976.

[sieve]

I just tried one with a menu, and it worked fine as well. The video is 480p/23.976.

Then that's what I need to achieve.... The clip I sent you is 575i 25, which is the same as the original source. The methods and settings I've been using don't seem to convert it.

[MrVideo]

I guess I'll poor over the two different ini's to see what it was...
I think you mean pour. :D

[MrVideo]

Blu-ray is a global standard, there is no need to convert from "PAL" to "NTSC" .....
Especially since in the digital world there is no such thing as NTSC, or PAL (both are analog specifications). I gather that is why you quoted the terms.

Just transfer the video files from the DVD to a Blu-ray. BD-RB can be used to create Blu-rays with menus, without recoding. Recoding MPEG-2 video from DVDs to H.264 is not recommended. The DVD MPEG-2 bitrate is too low. Recoding will add encoding errors.

[Ch3vr0n]

No such thing as PAL or NTSC huh? You try telling that to the DVD alliance. Try playing a PAL DVD on a NTSC player. You'll have either A) no video, B) no audio, C) glitchy B&W video, D) all of the previous. There's no such thing as pal or ntsc FOR BLU-RAY only. On DVD's it's very much existing.

[jdobbs]

Especially since in the digital world there is no such thing as NTSC, or PAL (both are analog specifications). I gather that is why you quoted the terms.

Just transfer the video files from the DVD to a Blu-ray. BD-RB can be used to create Blu-rays with menus, without recoding. Recoding MPEG-2 video from DVDs to H.264 is not recommended. The DVD MPEG-2 bitrate is too low. Recoding will add encoding errors.I wish people would stop saying that. They both still exist. Things still fail when attempting to use the wrong standard in the other parts of the world. Constantly telling people they can ignore it is incorrect and not helpful.

By the way, I just did a search and the term NTSC is referenced more than 40 times in the Blu-Ray standard.

[Lathe]

I think you mean pour. :D

DOHHHHHHHHH! http://lathe-of-heaven.com/doh.gif

[Lathe]

No such thing as PAL or NTSC huh? You try telling that to the DVD alliance. Try playing a PAL DVD on a NTSC player. You'll have either A) no video, B) no audio, C) glitchy B&W video, D) all of the previous. There's no such thing as pal or ntsc FOR BLU-RAY only. On DVD's it's very much existing.

Oh great... you woke up Ch3vr0n...

Thanks a LOT Mr. Video! :cool:

[MrVideo]

No such thing as PAL or NTSC huh? You try telling that to the DVD alliance. Try playing a PAL DVD on a NTSC player. You'll have either A) no video, B) no audio, C) glitchy B&W video, D) all of the previous. There's no such thing as pal or ntsc FOR BLU-RAY only. On DVD's it's very much existing.
The digital video is neither PAL, nor NTSC. It is either 480i59.94 or 576i50. It is the ANALOG OUTPUT of the player that is either NTSC or PAL. So, 480i DVDs are meant for NTSC output DVD players and 576i DVDs are meant for PAL output DVD players.

Take that same DVD and play it in your computer and I'll bet that it won't have any problem being displayed, no mater the resolution or frame rate. The only issue could possibly be the damn region coding.

Overseas you will find it really difficult to find a DVD player that will not play both 480i and 576i DVDs. It has been that way for ages, because people imported a lot of US releases and basically forced the selling of multi-standard DVD players. Many TVs/monitors were also multi-standard.

That said, I have an older DVD player that will handle all regions and both frame rates. Because it is sold in the U.S., it outputs the video as NTSC. Only because multi-standard TVs were not the norm here.

I now have a Blu-ray/DVD player that is all region (BD or DVD) and will play all resolutions.

[MrVideo]

I wish people would stop saying that. They both still exist. Things still fail when attempting to use the wrong standard in the other parts of the world. Constantly telling people they can ignore it is incorrect and not helpful.
I never say that anyone can ignore the frame rate on a DVD. You have to know what your playback equipment is capable of. In the old analog only days, especially here in the U.S., the playing of 576i DVDs was pretty difficult. The playing of 480i DVDs overseas was a lot more common (see previous posting). Since we in the U.S. had the wealth of DVDs available, the demand for 576i playback just wasn't called for. Because I prefer the original 576i50 DVD releases for Doctor Who, I bought a modified DVD player that was region free and would convert 576i50 to 480i59.94 so that I could watch them on my NTSC only TV.

Since DVD encryption was hacked ages ago, software became available that not only allowed for the copying of DVDs, it also allowed for the ignoring of the region codes. That allowed people to play 576i region 2,4 DVDs on their computers. No such thing as PAL/NTSC when playing DVDs on a computer system.
By the way, I just did a search and the term NTSC is referenced more than 40 times in the Blu-Ray standard.
I'd have to see how the terms PAL and NTSC are used. The Blu-ray standard is many years old and terms like PAL and NTSC can be mis-used easily. Look up the technical definitions of PAL and NTSC and you will find that they are analog only, not digital in any shape or form, especially since digital video was unheard of when the standards were created.

I will always try and point out that NTSC and PAL no longer exists in the mainstream. Yes, there are still those that only have DVD players and possibly only analog TVS. But, the main stream these days is digital, either HD or SD (for those damn subchannels). Ever since Jan 1, 2014, Blu-ray players could no longer be manufactured with analog outputs, HDMI only (there were execptions). No more NTSC, or PAL, analog outputs. No more NTSC, or PAL, period. The HDMI display device needed to be able to handle the frame rates of the user's discs. Hard to believe, but there seem to be display devices that do not handle 576i50. While looking for a computer display device (VGA/DVI/HDMI), it was hard find those that listed the complete specs. Most were generic listings.

I hope you all can see where I am coming from.

[MrVideo]

Oh great... you woke up Ch3vr0n...

Thanks a LOT Mr. Video! :cool:
It is a dirty job, but someone has to do it. :D

[jdobbs]

Just a general rule of thumb -- anytime it takes that many words to explain why you're right... you usually aren't.

[Lathe]

Just a general rule of thumb -- anytime it takes that many words to explain why you're right... you usually aren't.

Heh heh... you really are terrible JD...

I think we are just dealing with 'semantics' here guys... :sly:

[Sharc]

3D source with several 3D clips:
a. When selecting Full backup mode all 3D clips are reencoded/remuxed in MVC format
b. When selecting Full backup mode and selecting "Enable SBS/OU 3D Movie-Only output", all clips are encoded as 2D only, and none as 3D SBS.
Would it be possible to have all 3D clips encoded SBS/OU for case b. (=Full backup in SBS/OU format)?

[MrVideo]

Just a general rule of thumb -- anytime it takes that many words to explain why you're right... you usually aren't.
And sometimes a short explanation isn't good enough. :D

[MrVideo]

I think we are just dealing with 'semantics' here guys... :sly:
There have been people who have labeled 1080i/p 59.94/29.97 as NTSC and 1080i50 as PAL. Impossible. DGDecNV's status column on the left used to label HD video as NTSC as well. Several versions ago after I posted on his forum that NTSC/PAL HD doesn't exist, he removed the label. I do not remember if he still labels SD video as NTSC/PAL, since I haven't sent 480i, or 576i, thru the program in ages.

What started all of this off was a poster wanted to convert 576i to 480i Blu-ray. I should run a test with a Doctor Who DVD to see if just repackaging the MPEG-2 files onto a Blu-ray will play in one of my older Blu-ray players. I know it will play in the newest player as it will play the DVD itself just fine. If the Samsung player that I have does, it wouldn't mean that every other manufacturer's Blu-ray player will. It isn't mandatory that U.S. players play 25/50.

Now I'm curious to see if it will work, or not.

[Sharc]

A player with the Blu-Ray logo (certified) must play 720x576i25 and 720x576p25. I don't think that this is an option which is left to the mood or preference of the manufacturer.

[MrVideo]

A player with the Blu-Ray logo (certified) must play 720x576i25 and 720x576p25. I don't think that this is an option which is left to the mood or preference of the manufacturer.
Not according the Blu-ray Demystified book. It is the layman's book to the Blu-ray specification.

[jdobbs]

Not according the Blu-ray Demystified book. It is the layman's book to the Blu-ray specification.Are you sure about that? According to the spec it must play 720x576i@25. It should also support 720x576p@25 for secondary video (usually PiP usage) -- but I'll have to check and see if that is actually required in order to be certified.

Either way -- let's get back on topic. This is a bug thread. If we want to discuss it more, let's open another thread for it.

[Mikeyb123]

I think you mean pour. :D It should be pore.

[MrVideo]

Are you sure about that?
Table 6.4 General Characteristics of BDMV Presentation Data
Frame rate: 24/23.976 fps (film) [sic!]
29.97/59.94 fps (NTSC) [sic!]
25/50 fps (mandatory in PAL regions only)

I've marked two of the entries as sic because the one marked film is not necessarily true. Scripted drama TV shows are shot at 23.976 here in the U.S. The NTSC as a generic label is wrong because there is no such thing as HD NTSC.

[jdobbs]

Table 6.4 General Characteristics of BDMV Presentation Data
Frame rate: 24/23.976 fps (film) [sic!]
29.97/59.94 fps (NTSC) [sic!]
25/50 fps (mandatory in PAL regions only)

I've marked two of the entries as sic because the one marked film is not necessarily true. Scripted drama TV shows are shot at 23.976 here in the U.S. The NTSC as a generic label is wrong because there is no such thing as HD NTSC.I just went through the specification and especially references to 720x576 (and notes) and I couldn't find anything that supports the "mandatory in PAL regions only" statement. About the only time regions are mentioned (other than things like text and screen regions) is where they are documented in tables or for playback control. On the other hand the A/V specification volume is well of 1400 pages long -- so saying anything definitively always has to come with the caveat "from what I could find".

[MrVideo]

I'm currently extracting an episode of Primeval from its U.K. DVD release. So, I'll be putting together a single item menu BD disc as a test.

[gonca]

@MrVideo

Table 6.4 General Characteristics of BDMV Presentation Data
Frame rate: 24/23.976 fps (film) [sic!]
29.97/59.94 fps (NTSC) [sic!]
25/50 fps (mandatory in PAL regions only)

I've marked two of the entries as sic because the one marked film is not necessarily true. Scripted drama TV shows are shot at 23.976 here in the U.S. The NTSC as a generic label is wrong because there is no such thing as HD NTSC.

You of all people use reference material that refer to NTSC and PAL
OH...the irony!!!

[Sharc]

@jdobbs
Any thoughts on this (http://forum.doom9.org/showpost.php?p=1790015&postcount=25367)?
Is there a good reason why SBS/OU is not available with full backups?

[MrVideo]

You of all people use reference material that refer to NTSC and PAL
OH...the irony!!!
You need to read the book. NTSC/PAL is used correctly in many places in referring to the terms with television standard. It is unfortunate how the author used the terms in that particular table.

[jdobbs]

@jdobbs
Any thoughts on this (http://forum.doom9.org/showpost.php?p=1790015&postcount=25367)?
Is there a good reason why SBS/OU is not available with full backups?Have you tried the hidden option TYPE_OF_3D, or am I missing something?TYPE_OF_3D=n n = 0-3 - 0=Side-by-side (SBS, default), 1=Over/Under (O/U), 2=RC Anaglyph, 3=GM Anaglyph

[MrVideo]

OK, my test of creating a BD with content from a 576i50 DVD is complete. First off, the new feature to allow menu creation with a single menu item works. Thanks for that.

The video played just fine in my pre-Cinavia infested Blu-ray player. But, that doesn't mean that it will in all players. My guess is that it will. It seems rather dumb that a Blu-ray player has to play 1080i50 and not be able to play 576i50 MPEG-2 videos.

So, there is no need to convert 576i50 to 480i59.94.

You just need to copy the VOB files on the DVD into one big TS file (VOB files are TS files). In the case of the DVD in my test, there are three episodes on the disc, so there are three separate VOB groups, one for each episode. You can then import the TS files from all the DVD VOBs that you copied to TS files. By copy I actually mean concatenate. When you import the TS files in BDRB, you will first edit the menu. Then you will let it import the files. When the importing and menu creation is completed, do not hit the backup button. At this point, burn the BDMV and CERTIFICATE directories onto a BD. I do suggest burning a test BD on BD-RE media first.

There is one big issue with the above method and that is that there are no chapter marks. Because I have the VideoReDo program, I can extract stuff from DVDs and keep the chapter marks. By having VRD output a MKV file, the chapter marks are intact and BD-RB will use those chapter marks. I do not know of any other way to keep chapter marks. Other forum members might have ways of doing it.

[Sharc]

Have you tried the hidden option TYPE_OF_3D, or am I missing something?TYPE_OF_3D=n n = 0-3 - 0=Side-by-side (SBS, default), 1=Over/Under (O/U), 2=RC Anaglyph, 3=GM Anaglyph
No..., I didn't include this in my .ini. I assumed it isn't required because it defaults to 0 (SBS) which is what I wanted....
I'll try again after the current encode has completed.

[jdobbs]

No..., I didn't include this in my .ini. I assumed it isn't required because it defaults to 0 (SBS) which is what I wanted....
I'll try again after the current encode has completed.Sorry, I misunderstood what you were asking.

[Sharc]

Sorry, I misunderstood what you were asking.
Eventually I found the reason for the failing full backup SBS encode:
The original disc (ripped as 3D .iso) was small enough to fit on a BD25 without re-encoding (from a file size point of view).
In addition to enabling SBS in the settings and putting TYPE_OF_3D=0 in the .ini, I have to put FORCE_ENCODE=1 in the .ini. Otherwise the 3D clips are just getting remuxed as 2D (base stream only).
I think it would probably make sense to trigger the forced encoding automatically in this case, because SBS encoding of 3D MVC sources will always require re-encoding, independent of any size constraints. Any thoughts?

[jdobbs]

Eventually I found the reason for the failing full backup SBS encode:
The original disc (ripped as 3D .iso) was small enough to fit on a BD25 without re-encoding (from a file size point of view).
In addition to enabling SBS in the settings and putting TYPE_OF_3D=0 in the .ini, I have to put FORCE_ENCODE=1 in the .ini. Otherwise the 3D clips are just getting remuxed as 2D (base stream only).
I think it would probably make sense to trigger the forced encoding automatically in this case, because SBS encoding of 3D MVC sources will always require re-encoding, independent of any size constraints. Any thoughts?That's a bug. Even if it will fit, it should force a reencode of a 3D source when SBS/OU is selected. I'll make sure I fix it for the next release.

[Edit] It has been fixed for the next release.

[LowDead]

- Improved BD-5/9 full-backups. Sources that
do not use BD-J can be reencoded using the
full-backup mode, and should play on any
AVCHD compatible device. This includes all
imported and quick-play authored discs. A
small asterisk will display in the upper
left corner of the streams list next to
the disc title for any source/mode that
meets the criteria for an AVCHD compatible
full backup to BD-5/9.

Have now tested this with success on PS3 :thanks: . Sadly it borked the playback on my older Sony BDP-S560, which I find strange as it should handle proper AVCHD format.

[jdobbs]

Have now tested this with success on PS3 :thanks: . Sadly it borked the playback on my older Sony BDP-S560, which I find strange as it should handle proper AVCHD format.So by "borked" you're saying it won't play, I assume. I tried it on two different Sony players and it worked. I think I may have an older one in storage, I'll see if I can dig it out.

[LowDead]

Yes, I got message "invalid disc" when trying on the old Sony.

[jdobbs]

Yes, I got message "invalid disc" when trying on the old Sony.Wow. That's truly a surprise. It should be 100% AVCHD now.

Will your Sony play discs re-authored by multiAVCHD?

[LowDead]

Yes, it plays everything done with other software, it even played BD5 & BD9 done with BD-RB up until the latest version, when instead it worked on the PS3.

//LD

[Sharc]

Yes, it plays everything done with other software, it even played BD5 & BD9 done with BD-RB up until the latest version, when instead it worked on the PS3.

//LD
Does the "invalid disc" show up with new backups or with imported/quick re-authored material from earlier backups? Is the video/audio getting (re-)encoded, or is it just copied as is to the new disc?

[Sharc]

That's a bug. Even if it will fit, it should force a reencode of a 3D source when SBS/OU is selected. I'll make sure I fix it for the next release.

[Edit] It has been fixed for the next release.

Thanks.

Another issue for Full 3D backup (and similar for Movie + Menu backup):
- The disc plays correctly for FRIM/MVC backups.
- The disc loads but the Menu fails to play for (forced) Half-SBS backups (player stops, black screen).

For Half-SBS, all but one of the menu and intro clips are left untouched (monoscopic) or remuxed (in-mux) as MVC, but one is getting Half-SBS encoded. Does this mixture of MVC/in-mux and Half-SBS possibly fool the player? Or is this perhaps another bug?

Edit:
If it helps I could send you the playlists and Clipinf of the 2 versions (FRIM/MVC and Half-SBS).
Disc is for example Legend of Tarzan.

[LowDead]

Does the "invalid disc" show up with new backups or with imported/quick re-authored material from earlier backups? Is the video/audio getting (re-)encoded, or is it just copied as is to the new disc?

I haven't tested yet imported or quick reauthored, only full. The video/audio is encoding as it should.

//LD

[Jake802]

What does it mean when it says no video header found? Sorry, I made my own bluray. I was trying to shrink it down to fit on a single layer disc. I get an error popping up saying no video header found and then No Data Check Your PIDS. It then goes to completing remainder of indexing and it hangs. I was thinking it was my homemade disc, but I just tried starting the program and it doesnt even want to start, its hanging at the splash screen. I am now getting an error box that I am having trouble posting but it says Error Condition and BD Rebuilder experienced an error 2501 [12:15:22] ScanDirectory() 00009 2501

[jdobbs]

What does it mean when it says no video header found? Sorry, I made my own bluray. I was trying to shrink it down to fit on a single layer disc. I get an error popping up saying no video header found and then No Data Check Your PIDS. It then goes to completing remainder of indexing and it hangs. I was thinking it was my homemade disc, but I just tried starting the program and it doesnt even want to start, its hanging at the splash screen. I am now getting an error box that I am having trouble posting but it says Error Condition and BD Rebuilder experienced an error 2501 [12:15:22] ScanDirectory() 00009 2501My guess is that the M2TS stream is illegally formatted.

[Jake802]

Thanks JDobbs!

[jdobbs]

Thanks JDobbs!I believe that error is coming from DGIndexNV -- you may want to take a look at the standard used for M2TS files (ISO/IEC 13818-1) for more details. If you search for it, it should be available for download.

[Sharc]

@jdobbs
My Blu-ray source is 1080i, 25fps.
I don't apply a deinterlacer because the video is progressive. Alternate output to mkv container 1280x720 produces 1280x720p25 which is not blu-ray compliant. I think it should be 50fps using frame duplication, i.e. changefps() rather than assumefps() in the script for this type of source, no?
Is this a bug, or a "don't care" for .mkv ouput?

P.S.
It does it right for Blu-Ray structure output, so the question is only for alternate outputs.

[MrVideo]

Is this a bug, or a "don't care" for .mkv ouput?
IMHO it is a don't care. The last thing you need is a file twice the size it needs to be. 720p25 MKV file are playable in any Blu-ray player that plays MKV files.

Frankly, I'd bet that you would be hard pressed to find a relatively new Blu-ray player that wouldn't play 720p25 videos even when authored as a Blu-ray disc.

[jdobbs]

BD-RB doesn't put the same restrictions on ALTERNATE output files (e.g. MKV) that it would on a BD. For example, if you have auto GOP set, it can have GOPs that are 250 frames, which would be illegal for BD. At one point I was trying to create them to be compatible, but I gave up on that idea for the sake of encoding efficiency.

[Sharc]

IMHO it is a don't care. The last thing you need is a file twice the size it needs to be. ...
File size is not a problem at all. The file will become only slightly bigger, because x264 encodes the duplicated frames very very efficiently (another method I didn't mention would be to apply --pulldown). But let's hope that you are right and very most Blu-ray players will actually play 720p25.

[jdobbs]

File size is not a problem at all. The file will become only slightly bigger, because x264 encodes the duplicated frames very very efficiently (another method I didn't mention would be to apply --pulldown). But let's hope that you are right and very most Blu-ray players will actually play 720p25.As an MKV I'd pretty much bet it would. The BD restrictions aren't supposed to be applicable to video file playback. But, on the other hand, there really aren't a lot of rules for those, so the limits are really up to the OEM.

[MrVideo]

File size is not a problem at all. The file will become only slightly bigger, because x264 encodes the duplicated frames very very efficiently (another method I didn't mention would be to apply --pulldown).
Right you are.
But let's hope that you are right and very most Blu-ray players will actually play 720p25.
I know my Samsungs will play 720p25 MKV files. I do not know about 720p25 authored discs. I prefer all of my HD to be 1080p.

[Sharc]

BD-RB doesn't put the same restrictions on ALTERNATE output files (e.g. MKV) that it would on a BD. For example, if you have auto GOP set, it can have GOPs that are 250 frames, which would be illegal for BD. At one point I was trying to create them to be compatible, but I gave up on that idea for the sake of encoding efficiency.
Oh I see, it's not a bug.
I just wonder about the default option ALTERNATE_BLURAY=1 which serves for steering the alternate outputs towards Blu-ray compatibility ... ;)
But most important, it comes out right when outputting to Blu-ray structure :)

[Sharc]

@jdobbs
Coming back to this post (http://forum.doom9.org/showpost.php?p=1790438&postcount=25392):
Any thoughts why FULL backup of 3D blu-rays as Half-SBS produce non-playable menus? Is Full backup mode only supported for FRIM/MVC?

[jdobbs]

@jdobbs
Coming back to this post (http://forum.doom9.org/showpost.php?p=1790438&postcount=25392):
Any thoughts why FULL backup of 3D blu-rays as Half-SBS produce non-playable menus? Is Full backup mode only supported for FRIM/MVC?Could you send me your settings at the time you tried it and it failed? I'll run a 3D job and see what happens.

[jdobbs]

Yes, it plays everything done with other software, it even played BD5 & BD9 done with BD-RB up until the latest version, when instead it worked on the PS3.

//LDI don't have my old Sony player anymore -- I must have given it away to somebody. My old Sony also played full-backups on BD-5/9 (that weren't AVCHD compliant). But my newer Sony players wouldn't play anything with menus until my latest changes. I'm a little confused when you say your player will work with multiAVCHD. I used it as a baseline (along with some notes DeanK sent me a long time ago) for how I make BD-RB AVCHD compliant in it's menus.

I'm not sure what to do... maybe add a flag that can make it revert it's behavior? The problem with that is that when you replace your player -- your discs may not work anymore. I had several like that and had to restructure them.

[Sharc]

Could you send me your settings at the time you tried it and it failed? I'll run a 3D job and see what happens.
My settings:
[Options]
VERSION=0.50.0.20

ENABLE_TEST=1
NEW_CRF_PREDICTION=1
#ENCODER_MENU=1
SHOW_ENCODER=1
HC_PROFILE=BEST
ALTERNATE_PAL=1
IMPORT_PAL_TO_FILM=0

IMPORT_HEVC_INTACT=1

ARCHIVE_265=1
ARCHIVE_AUDIO=50
ARCHIVE_CRF=22
ARCHIVE_ENABLE=1
ARCHIVE_LIMIT=1

#FIXED_CRF=18
#10..50 - force CRF encoding to use this CRF value (output size control disappears)

QUICK_CRF=22
QUICK_USE_QUALITY=1
SECONDARY_USE_QUALITY=1
ALTERNATE_QUALITY=2
ARCHIVE_QUALITY=2

FORCE_ENCODE=1
FORCED_SUB_LANG=ger;deu

TYPE_OF_3D=0

MENU_FORCE_QUICK=1

ALTAUTOAUDIO=50
DOWNRESIZE=BilinearResize

B_PYRAMID=1
KEEP_MBTREE=1
EXTENDED_GOP=1

DEINTERLACER_TYPE=4

IVTC_SELECTION=1

ENCODER=0
MODE=0
ENCODE_QUALITY=0
ONEPASS_ENCODING=2
AUTO_QUALITY=1
AUTO_BIAS=3
MOVIEONLY_TYPE=8
ALTCRF=19
ALT_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
TARGET_SIZE=23500
AUDIO_TO_KEEP=deu;eng;ger;
SUBS_TO_KEEP=deu;eng;ger;
SD_CONVERT=0
OPEN_GOP=1
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=0
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=1
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=0
AUDIO_DRC=0
DECODER=3
AVCHD=0
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=1
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=1
NEROAAC=1
SUPTITLE=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23600
QUICK_EXTRAS=0
MENU_BACKGROUND=C:\Program Files Video\BD_Rebuilder\Misc\abstract_blue.jpg
IMPORT_THRESHOLD=15
QUICK_PLAY_THRESHOLD=10
MENU_AUTO_BACKGROUND=1
MENU_AUTO_DVDAUDIO=1
MENU_PLAY_SEQUENTIAL=0
MENU_START_WITH_MENU=1
MENU_BACKDROP_AUTOSIZE=1
IMPORT_LIMIT_LANG=1
IMPORT_KEEP_PLAYALL=0
VERBOSE_STATUS=1
ENABLE_BLANKING=1
ALT_CRF_TARGET=128
PGSTOSRT=0
AVSFilter01=#f:hqdn3d(4)
AVSFilter02=#f:r:Sharpen(0.15)
AVSFilter03=#f:Grayscale()
AVSFilter04=#r:QTGMC(InputType=3,Preset="fast")
MENU_AUDIO=C:\Program Files Video\BD_Rebuilder\tools\blankclip\blank.ac3

[Paths]
WORKING_PATH=C:\TEMP\BD REBUILDER\
DGIndexNV=C:\Program Files Video\DGdecNV\DGIndexNV.exe
DGDecNV=C:\Program Files Video\DGdecNV\DGDecodeNV.dll
NeroAACPath=C:\Program Files (x86)\Nero-AAC\win32\neroAacEnc.exe

SOURCE_PATH=F:\

The only difference between the non-working Half-SBS and the working FRIM/MVC mode is the SBS selection/deselection in the settings menu.

I also noticed that for FRIM/MVC the scanning of the CLPI seems to be done more thoroughly. The resulting .clpi are quite different for the 2 cases.

Added:
It looks to me as there may be a problem with the .clpi for the Half-SBS backup:
For example, in the working FRIM/MVC backup all .clpi of the dependent views (of the original files) are stripped off and the .clpi of the newly created in-muxed stereofiles are created/modified, while in the non-working SBS backup all .clpi of the dependent views are copied back intact from the original and the .clpi for the newly created Half-SBS clips are created/modified.

I could send the Playlist ans Clipinf of the 3 variants (original, FRIM/MVC and SBS) if this would help.

[LowDead]

I don't have my old Sony player anymore -- I must have given it away to somebody. My old Sony also played full-backups on BD-5/9 (that weren't AVCHD compliant). But my newer Sony players wouldn't play anything with menus until my latest changes. I'm a little confused when you say your player will work with multiAVCHD. I used it as a baseline (along with some notes DeanK sent me a long time ago) for how I make BD-RB AVCHD compliant in it's menus.

I'm not sure what to do... maybe add a flag that can make it revert it's behavior? The problem with that is that when you replace your player -- your discs may not work anymore. I had several like that and had to restructure them.

I'm in the middle of testing right now, although not that much time this time of year ^^ I think it must be my player that needs a newer firmware, but I really don't want to update it because it's not cinavia infected.

Anyhow, Merry Christmas to all!

/LD

[MrVideo]

but I really don't want to update it because it's not cinavia infected.
Don't worry, it won't be infected with a firmware update. Besides, after a certain period of time, players are no longer updated. There hasn't been an update for my older Samsung players in ages. Manufacturers just do not bother with older models.

[LowDead]

Don't worry, it won't be infected with a firmware update. Besides, after a certain period of time, players are no longer updated. There hasn't been an update for my older Samsung players in ages. Manufacturers just do not bother with older models.

I know there is new FW updates to this model. I haven't updated out of fear of getting it infected. So it's safe to update you say?

//LD

[jdobbs]

The only difference between the non-working Half-SBS and the working FRIM/MVC mode is the SBS selection/deselection in the settings menu.

I also noticed that for FRIM/MVC the scanning of the CLPI seems to be done more thoroughly. The resulting .clpi are quite different for the 2 cases.

Added:
It looks to me as there may be a problem with the .clpi for the Half-SBS backup:
For example, in the working FRIM/MVC backup all .clpi of the dependent views (of the original files) are stripped off and the .clpi of the newly created in-muxed stereofiles are created/modified, while in the non-working SBS backup all .clpi of the dependent views are copied back intact from the original and the .clpi for the newly created Half-SBS clips are created/modified.

I could send the Playlist ans Clipinf of the 3 variants (original, FRIM/MVC and SBS) if this would help.When doing in-mux I have to make modifications to the CLPI myself (since TSMUXER's won't work). I'll run a couple SBS 3D jobs and let you know what I find.

[Sharc]

When doing in-mux I have to make modifications to the CLPI myself (since TSMUXER's won't work). I'll run a couple SBS 3D jobs and let you know what I find.
I see. My guessing is now that the 3D menu and intro files are not SBS encoded because these files are too small. These small 3D menu files are however changed from MVC to in-muxed format, which would require your CLPI modification. Apparently these modifications are missing at present, at least in my tests the CLPI are just getting copied.
Thanks for looking at it.

[jdobbs]

I see. My guessing is now that the 3D menu and intro files are not SBS encoded because these files are too small. These small 3D menu files are however changed from MVC to in-muxed format, which would require your CLPI modification. Apparently these modifications are missing at present, at least in my tests the CLPI are just getting copied.
Thanks for looking at it.It might be a couple of days -- I've got a lot of company visiting for Christmas and won't be able to get to the computer much.

[jdobbs]

All,

Merry Christmas, Happy Holidays, Happy Hanukkah, Milad Un-Nabi, Winter Solstice or whatever other December event happens to float your boat this holiday season. It's been a pleasure conversing with you all on the forum this year.

I hope you all also have a safe and fulfilling New Year.

[gonca]

Merry Christmas everyone
@jdobbs
Careful hanging decorations, wouldn't do to have you fall and hurting yourself (roof)

[MrVideo]

I know there is new FW updates to this model. I haven't updated out of fear of getting it infected. So it's safe to update you say?
Google search your model. I'm sure there are forums out there that discuss this issue. Get your hands on the firmware's change list. But, do check out the forums.

[LowDead]

Have now updated FW on the S560. Still doesn't work.

Have also made some quick tests for comparison:

AVCHDCoder 15.12.27 BD9(intro, no menu): Sony BDP-S560 OK!, PS3 OK!
multiAVCHD v4.1 build 771 BD5 (strict AVCHD, simple menu): Sony BDP-S560 OK!, PS3 OK!
multiAVCHD v4.1 build 771 BD5 (AVCHD, motion menu): Sony BDP-S560 OK!, PS3 OK!
multiAVCHD v4.1 build 771 BD5 (Bluray, motion menu): Sony BDP-S560 OK!, PS3 NO!
BD-RB v0.50.19 Full BD5/BD9: Sony BDP-S560 OK!, PS3 NO!
BD-RB v0.50.20 Full BD5/BD9 Sony BDP-S560 NO!, PS3 OK!

//LD

[MrVideo]

Have now updated FW on the S560.
That is an old model. Mine is the S350. I don't even know where it is. I found the box though. :D

[varekai]

Happy Holidays jdobbs and forum!

[Capsbackup]

All,

Merry Christmas, Happy Holidays, Happy Hanukkah, Milad Un-Nabi, Winter Solstice or whatever other December event happens to float your boat this holiday season. It's been a pleasure conversing with you all on the forum this year.

I hope you all also have a safe and fulfilling New Year.

Happy holidays to you and your family!
Wishing you a great new year for 2017. :)

[HWK]

All,

Merry Christmas, Happy Holidays, Happy Hanukkah, Milad Un-Nabi, Winter Solstice or whatever other December event happens to float your boat this holiday season. It's been a pleasure conversing with you all on the forum this year.

I hope you all also have a safe and fulfilling New Year.


To Jdobbs and all doom9 folks,
Happy holidays and wishing you warm and prosper new year.

[soneca]

All,

Merry Christmas, Happy Holidays, Happy Hanukkah, Milad Un-Nabi, Winter Solstice or whatever other December event happens to float your boat this holiday season. It's been a pleasure conversing with you all on the forum this year.

I hope you all also have a safe and fulfilling New Year.

Thank you! A great Christmas, happy holidays and everything good for you and everyone at doom9.

[MrVideo]

A little late, but Merry Xmas (or whatever you celebrate) and Happy New Year.

[videoh]

Not too late here, MrVideo! Thanks and same to you and all forum members.

[jdobbs]

It's never too late for a Merry Christmas. Right back at you.

And a special thanks to you videoh for all the things you contributed over the years. I want to be just like you when I grow up.

[videoh]

He he. Trust me, I never grew up so don't try to emulate me if you are planning to grow up.

[jetli]

is this tool capable of hevc compression from 10bit hevc, mkv source files to make it fit on a bd50 disc
that could play on a new 4k bluray machine?
are there any plans to do anything like this? if so, what specifically?

[jdobbs]

There are plans for 4K backups... but until there is a 4K compatible burner available it's just on the "wish list". An MKV is another matter. I don't have a 4K compatible player -- and frankly it's still a little too expensive, so I'm not sure when I could do any developmental testing. But I would guess that all you'd need to make it work is to replace the existing version of X265 with the 10 bit version. Not sure though. For all I know it might work as-is. Of course you'd have to get your hands on a 4K source and have a way to rip it.

[Ch3vr0n]

LG has been approved & licensed by the BDA to develop an UHD pc consumer drive, and Cyberlink a UHD powerDVD but that was only a couple weeks ago. I wouldn't expect one well into next year (or even later)

[Lathe]

All,

Merry Christmas, Happy Holidays, Happy Hanukkah, Milad Un-Nabi, Winter Solstice or whatever other December event happens to float your boat this holiday season. It's been a pleasure conversing with you all on the forum this year.

I hope you all also have a safe and fulfilling New Year.

Uh, you kind of left out 'Happy Greased Weasel Season' you know... Geez man, I think that I am feeling a little put out at that JD...

http://lathe-of-heaven.com/dogsee.gif

[Sharc]

jdobbs,
Finally something for the 2017 pipeline:
Based on tests with the current deinterlacer options I suggest following modifications in the hiddenopts.txt:

DEINTERLACER_TYPE=n n = 1-5 - 1=DECOMB. 2 (default): None for HD sources, DECOMB with field blending for SD sources. 3=SmoothDeinterlace. 4=Progressive (fake). 5=3+1
DEINTERLACER_BLEND=n n = 0/1 - 0=No field blending during deinterlacing (default). 1=Blending during deinterlacing. This setting applies for DEINTERLACER_TYPE=1,3,5 only.

Alternatively you may want to change the DEINTERLACER_TYPE=2 such as to adopt the DEINTERLACER_BLEND= setting for SD sources.

With best wishes for a seamless branching into the next year!

:thanks:

[Djuby]

Quick question - why there is no difference in the calculated video bitrate when I choose to encode the audio in DD5.1@448kbs instead of 640kbs? The video bit rate should go slightly up, right?

Best regards,
Djuby

[jdobbs]

Quick question - why there is no difference in the calculated video bitrate when I choose to encode the audio in DD5.1@448kbs instead of 640kbs? The video bit rate should go slightly up, right?

Best regards,
DjubyYes, the bitrate should change slightly. Make sure, though, that you haven't selected the option to not convert or reencode. With that set the 448Kbs option would have no effect. On short sources it is also possible for the bitrate to hit its maximum. If that happens it also won't be changed.

[gonca]

Encode Fails
Its a new win10 system
I believe I have it set up right
Extracts fine but fails immediately when the encode fails
Tried both DGDecNV and Lav

LASTCMD
"C:\Program Files (Portable)\BD-RB\tools\x264.exe" "W:\HD\WORKFILES\VID_00000.AVS" --preset medium --bluray-compat
--seek 107898 --b-pyramid none --weightp 1 --slow-firstpass --qpmin=0 --crf 18 --level 4.1 --qpfile "W:\HD\WORKFILES\VID_00000.CHP"
--aud --nal-hrd vbr --pic-struct --vbv-bufsize 30000 --keyint 24 --min-keyint 1
--ipratio 1.1 --pbratio 1.1 --vbv-maxrate 30000 --threads auto --slices 4 --thread-input --tune film
--stats "W:\HD\WORKFILES\VID_00000.AVS.4.264.stats" --output "W:\HD\WORKFILES\VID_00000.AVS.4.264"

LOG
[12/31/16] BD Rebuilder v0.50.20
[16:37:27] Source: #JASON_BOURNE_00000
- Input BD size: 22.73 GB
- Approximate total content: [01:40:00.411]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV, CRF, Intact Audio
- Quality: High Quality (Default)
- X264 Tweak(s) enabled
- Decoding/Frame serving: DGDecNV [4-way]
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[16:37:27] PHASE ONE, Encoding
- [16:37:27] Processing: VID_00000 (1 of 1)
- [16:37:27] Extracting A/V streams [VID_00000]
- [16:39:45] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 143,866 frames
- [16:39:45] Reencoding: VID_00000, Pass 1 of 1
- Encode failed. Aborting.
- BD-Rebuilder v0.50.20
- Windows Version: 6.2 [9200]
- Working Path Free Space: 385.13GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[16:39:45] - Failed video encode, aborted

INI
[Options]
VERSION=0.50.0.20
FORCE_ENCODE=0
FORCE_NOENCODE=0
MULTIPROCESS=1
FIXED_CRF=18
HC_PROFILE=BEST
DEFAULT_LANG=eng
ENABLE_TEST=1
ENABLE_BLANKING=0
IMPORT_HEVC_INTACT=1
IMPORT_FOLDER=T:\
REMOVE_IMPORT=0
KEEP_HD_LPCM=1
SD_PROGRESSIVE=1
MOVIE_ONLY_LOOP=0
USE_ZLIB=0
MIN_M2TS_SIZE=1
UNMASK_CHAPTER=0
OUTPUT_3D=0
NEROAAC=0
AUTO_BURN=2
ENCODER=0
MODE=3
ENCODE_QUALITY=2
ONEPASS_ENCODING=1
AUTO_QUALITY=0
MENU_BACKGROUND=C:\Program Files (Portable)\BD_RB\misc\menuback.jpg
IMPORT_THRESHOLD=30
QUICK_PLAY_THRESHOLD=10
MENU_AUTO_BACKGROUND=1
MENU_AUTO_DVDAUDIO=1
MENU_PLAY_SEQUENTIAL=0
MENU_START_WITH_MENU=1
IMPORT_LIMIT_LANG=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=1
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
DECODER=3
AVCHD=0
REMOVE_WORKFILES=1
REMOVE_OUTPUT=1
USE_FILTERS=0
BDMV_CERT_ONLY=1
IVTC_PULLDOWN=1
IVTC_METHOD=1
IVTC_SELECTION=1
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=8600
TWEAK_PASS_ONE= --tune film
TWEAK_PASS_TWO= --tune film
MOVIEONLY_TYPE=3
ALTCRF=18
ALT_TARGET=10870
ALTMETHOD=0
ALTAUTOCROP=0
TARGET_SIZE=23500
AUDIO_DRC=0
QUICK_EXTRAS=0
MENU_AUDIO=C:\Program Files (Portable)\BD_RB\tools\blankclip\blank.ac3
IMPORT_KEEP_PLAYALL=1
ALT_CRF_TARGET=9592
PGSTOSRT=0
#AVSFilter01=hqdn3d(2,1,3,1)
#AVSFilter01=Removegrain()
[Paths]
SOURCE_PATH=T:\IMPORTS\#JASON_BOURNE\
TesseractPath=C:\Program Files (Portable)\BD_RB\Tools\Tesseract\tesseract.exe
SupTitlePath=C:\Program Files (x86)\AviSynth\plugins\suptitle_v2.0.8_x86\SupTitle.dll
WORKING_PATH=W:\HD\
DGIndexNV=C:\Program Files (Portable)\dgdecnv\DGIndexNV.exe
DGDecNV=C:\Program Files (Portable)\dgdecnv\DGDecodeNV.dll

EDIT
Seems that Windows Defender is the culprit

[gonca]

Seems that Windows Defender isn't the only culprit.
The avisynth filters cause the encode to fail, and I disabled Defender

EDIT
Seems that Visual C++ 2010 does not come with win10
Problem solved

[jdobbs]

Seems that Windows Defender isn't the only culprit.
The avisynth filters cause the encode to fail, and I disabled Defender

EDIT
Seems that Visual C++ 2010 does not come with win10
Problem solvedGlad you got it fixed. I personally had no problem with installing/running on Windows 10. I guess it just depends on the build or image used.

[gonca]

Glad you got it fixed. I personally had no problem with installing/running on Windows 10. I guess it just depends on the build or image used.

I guess Microsoft can't make up its mind about what to put in Win10

[Djuby]

Yes, the bitrate should change slightly. Make sure, though, that you haven't selected the option to not convert or reencode. With that set the 448Kbs option would have no effect. On short sources it is also possible for the bitrate to hit its maximum. If that happens it also won't be changed.

Thanks jdobbs.

[Blurayhd]

Hi guys I have Knight Rider tv Show from 80s in full Bluray, as you know each disc has 3 or 4 episodies and I need to extract each one on MKV file in 720p and 1080p but I just don´t know how can I do that with BD rebuilder?

I´ll appreciate your help, and I hope all of you have a very good year

[worknstiff]

@ Blurayhd; RE: I need to extract each one on MKV file in 720p and 1080p but I just don´t know how can I do that with BD rebuilder?
You just load the Blu-ray and then go to "MODE" tab and select "Movie Only" instead of "Full" and select the episode you want by looking at the time and after selecting the episode go into the "Alternate" output settings and choose what kind of MKV you want and the audio and picture size you want to use. It's really simple once you do a few.

[jdobbs]

Hi guys I have Knight Rider tv Show from 80s in full Bluray, as you know each disc has 3 or 4 episodies and I need to extract each one on MKV file in 720p and 1080p but I just don´t know how can I do that with BD rebuilder?

I´ll appreciate your help, and I hope all of you have a very good yearThe easiest way is to choose ALTERNATE output and select a format. For example, if you want to keep them intact, you can choose an intact option. If not, choose the one you want (720p, 1080p etc.), and then choose a quality level. The default of 23 is very good, but if you want near-perfect change it to 18. There are other options too, depending on your preference.

After you select the disc as your source, go to the BATCH tab and right click on it. Select "Add multiple Playlists to Queue" and choose the playlists for each of the episodes. Then just run the batch job. When it's done you will have all 3 or 4 episodes each in a separate MKV file. Repeat for all discs.

[Buckskin]

I am trying to create a BD with menu from a collection of mkvs and I am having some issues and I am not sure if they are bugs or me not setting things up properly.
1. The files all import OK, the menu shows all the files and allows me to edit the menu titles, however, one of the files is just under 3 mins long but even with both Import time & Menu time set to 1 the BD created includes the option on the menu but the m2ts is not included in the Stream directory. When the menu option is selected nothing happens (no crash). I can copy the m2ts file and associated cli files from the import directories into the BD directories and everything works.
2. In another set of files I have an audio track that imports OK but the timing delay is ignored, so although in sync when playing the mkv it is not in sync in the BD
3. In another set everything is fine except I can't get a required subtitle track to be forced even though it works in the mkv file (I tried both Full Backup & Quick Play)

A query, if I import an mkv file (of say 17Gb) and specify a custom target the BD is expanded to be close to this size (importing a BD direct does not do this) so the question is, is this supposed to happen and does it result in a better picture? (I am assuming that the bit rate is increased to cause this)

Thank you in advance for any advice.

Config ini for Set 3 but apart from the Menu Background I do not change anything

[Options]
VERSION=0.50.0.20
ENCODER=0
MODE=2
ENCODE_QUALITY=0
ONEPASS_ENCODING=0
AUTO_QUALITY=1
AUDIO_TO_KEEP=eng;jpn;
SUBS_TO_KEEP=eng;jpn;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=0
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=1
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=1
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=24400
AUTO_BURN=2

IMPORT_THRESHOLD=1
QUICK_PLAY_THRESHOLD=1

IMPORT_LIMIT_LANG=0
IMPORT_KEEP_PLAYALL=0

MENU_BACKGROUND=F:\Film\Ghost in the Shell Arise\Menu Background.png
MENU_AUDIO=E:\Video Utility\BD Rebuilder\tools\blankclip\blank.ac3
MENU_FONT=Arial Rounded MT Bold
MENU_AUTO_BACKGROUND=1
MENU_AUTO_DVDAUDIO=0
MENU_PLAY_SEQUENTIAL=0
MENU_START_WITH_MENU=1
MENU_ACTIVE_COLOR=YELLOW
MENU_TOP=300

TARGET_SIZE=24400
[Paths]
NeroAACPath=E:\Video Utility\EAC3to\neroAacEnc.exe
WORKING_PATH=H:\WORKING\
SOURCE_PATH=H:\WORKING\IMPORTS\GHOST_IN_THE_SHELL_ARISE\

[Blurayhd]

The easiest way is to choose ALTERNATE output and select a format. For example, if you want to keep them intact, you can choose an intact option. If not, choose the one you want (720p, 1080p etc.), and then choose a quality level. The default of 23 is very good, but if you want near-perfect change it to 18. There are other options too, depending on your preference.

After you select the disc as your source, go to the BATCH tab and right click on it. Select "Add multiple Playlists to Queue" and choose the playlists for each of the episodes. Then just run the batch job. When it's done you will have all 3 or 4 episodes each in a separate MKV file. Repeat for all discs.

Thank you for your help but I don´t know what I doing wrong but When I select Full appears the various episodes that the disc contain but when I select Movie only just appears one episode and just don´t let me to do nothing. Again I´ll appreciate some help

Screens

Full mode
http://s2.subirimagenes.com/otros/previo/thump_9669028screen1.jpg

Movie only

http://s2.subirimagenes.com/otros/previo/thump_9669031screen2.jpg

[MrVideo]

A query, if I import an mkv file (of say 17Gb) and specify a custom target the BD is expanded to be close to this size (importing a BD direct does not do this) so the question is, is this supposed to happen and does it result in a better picture?
Yes and no. I do not know why jdobbs does recode and make a file larger in order to fit the custom size. IMHO, if all the files that are being placed on the disc fit under the requested size, leave them alone. Recoding files because they would be over the requested size is when recoding should be done. That said, there are MKV wrapped files that are not compliant with the Blu-ray specs, so recoding is needed, no matter what. I believe that jdobbs recodes no matter what so that he knows the video will be compliant.

Recoding to a larger size can not, and will not, improve the quality. That is not the way digital works. You can't get something from nothing.

If you go back thru the posts, you will find a posting from me describing what it takes to build a Blu-ray from imported MKV files, without any recoding. If I have issues with a video, I do all of my recoding myself. The steps I takes to build a disc, may, or may not, solve your issues. But, it sounds like it won't.

[MrVideo]

Thank you for your help but I don´t know what I doing wrong but When I select Full appears the various episodes that the disc contain but when I select Movie only just appears one episode and just don´t let me to do nothing. Again I´ll appreciate some help
Your images are too small, therefore unreadable.

Post your INI config file.

[jdobbs]

Thank you for your help but I don´t know what I doing wrong but When I select Full appears the various episodes that the disc contain but when I select Movie only just appears one episode and just don´t let me to do nothing. Again I´ll appreciate some helpYou have to select Movie-Only in order to set an ALTERNATE output. That's the only way you can create an MKV. You can then select a playlist one at a time if you want to. But, when you want to do all the episodes at once, you can just go to the Batch tab, right click, and select "Add multiple Playlists to Queue" and select the ones you want to process. That way you can add all the episodes in a single step (they will be processed one-at-a-time automatically).

[jdobbs]

Yes and no. I do not know why jdobbs does recode and make a file larger in order to fit the custom size. IMHO, if all the files that are being placed on the disc fit under the requested size, leave them alone. Recoding files because they would be over the requested size is when recoding should be done. That said, there are MKV wrapped files that are not compliant with the Blu-ray specs, so recoding is needed, no matter what. I believe that jdobbs recodes no matter what so that he knows the video will be compliant.

Recoding to a larger size can not, and will not, improve the quality. That is not the way digital works. You can't get something from nothing.

If you go back thru the posts, you will find a posting from me describing what it takes to build a Blu-ray from imported MKV files, without any recoding. If I have issues with a video, I do all of my recoding myself. The steps I takes to build a disc, may, or may not, solve your issues. But, it sounds like it won't.It's very rare that an imported MKV is blu-ray compatible. That's why the default is to encode. You can set the hidden option to force no encoding -- but only rarely is it a good idea, and only if you KNOW DEFINITELY that the source meets all the Blu-Ray compatibility requirements. Frankly I don't think I've ever seen one that does unless it was created by BD-RB using the Intact Audio/Intact Video setting from a pristine BD source.

[Blurayhd]

The easiest way is to choose ALTERNATE output and select a format. For example, if you want to keep them intact, you can choose an intact option. If not, choose the one you want (720p, 1080p etc.), and then choose a quality level. The default of 23 is very good, but if you want near-perfect change it to 18. There are other options too, depending on your preference.

After you select the disc as your source, go to the BATCH tab and right click on it. Select "Add multiple Playlists to Queue" and choose the playlists for each of the episodes. Then just run the batch job. When it's done you will have all 3 or 4 episodes each in a separate MKV file. Repeat for all discs.

Thank you Jdbbs but in few words? When I select Full movie, on Bd rebulder appears the three episodies that contain the disc but if I select Only movie on the Bd rebuilder appears the option to only one episode and very long (just like if Bd rebuilder takes the three episodes as one)

That is all my problem, I select Only movie and Bd rebuilder appears that, if I select full movie, appears all three:scared:

[LowDead]

Have made some more thinking and testing..

multiAVCHD puts a couple of avchd folders on the structure, but AVCHDCoder don't so those are not the issue. The only thing I could think of was the index.bdmv and MovieObject.bdmv and after comparing I definately can see they differ from the BD-RB generated ones. I must say though, that I don't have the knowledge as to what these files really do. Also there is probably more files that come into play, that I don't know of. Anyhow just to test I copied the multiAVCHD ones to the BD-RB discs folder and the result is no more error message on the old Sony. Ofcourse the movie didn't start but hey it's a tiny bit of progress, right? :D

//LD

[MrVideo]

Frankly I don't think I've ever seen one that does unless it was created by BD-RB using the Intact Audio/Intact Video setting from a pristine BD source.
Except those few of use who do their own H.264 encoding. :eek:

[jdobbs]

Thank you Jdbbs but in few words? When I select Full movie, on Bd rebulder appears the three episodies that contain the disc but if I select Only movie on the Bd rebuilder appears the option to only one episode and very long (just like if Bd rebuilder takes the three episodes as one)

That is all my problem, I select Only movie and Bd rebuilder appears that, if I select full movie, appears all three:scared:I've answered you clearly twice, but you're asking the same question again. Please go back and read my original answer and the follow-up. What shows in the window means nothing... go to the Batch tab, right click, and select the playlists...

[Blurayhd]

The easiest way is to choose ALTERNATE output and select a format. For example, if you want to keep them intact, you can choose an intact option. If not, choose the one you want (720p, 1080p etc.), and then choose a quality level. The default of 23 is very good, but if you want near-perfect change it to 18. There are other options too, depending on your preference.

After you select the disc as your source, go to the BATCH tab and right click on it. Select "Add multiple Playlists to Queue" and choose the playlists for each of the episodes. Then just run the batch job. When it's done you will have all 3 or 4 episodes each in a separate MKV file. Repeat for all discs.

Thank you dear Jdobbs and sorry (my mistake, I don´t read all that, but that was without bad intention), so I just tryied that you said but I get the same, I know what you mind but I can´t get it works

An example, the disc as you know has three episodes and when I right click on BATCH I should see the playlist for each one for each episode (please tell me if I get wrong?) but when click right this appears (only one playlist with almost 3hs

http://i65.tinypic.com/243grqc.jpg

So, I honestly do not want to bother you but I have this problem. And I do not know what else to try all I need is to extract each episode

[jdobbs]

Thank you dear Jdobbs and sorry (my mistake, I don´t read all that, but that was without bad intention), so I just tryied that you said but I get the same, I know what you mind but I can´t get it works

An example, the disc as you know has three episodes and when I right click on BATCH I should see the playlist for each one for each episode (please tell me if I get wrong?) but when click right this appears (only one playlist with almost 3hs

http://i65.tinypic.com/243grqc.jpg

So, I honestly do not want to bother you but I have this problem. And I do not know what else to try all I need is to extract each episodeYeah, that's a little different. In that case they've probably used one playlist to hold 3 episodes. It's possible they use the chapter points as the indicators. I've seen that on DVDs before (see the hidden option IMPORT_DVD_CHAPS), but never on a Blu-ray disc. It's more likely they've combined multiple M2TS files into a single playlist and use jump points (I think I've seen that before). I may need to see if I can find a disc from that series... I really don't want to buy the whole series just to have a look at it. It's weird that there is only one playlist available in the list -- that's for sure.

[MrVideo]

The BDEdit program can be used to look at the disc's playlists.

[Blurayhd]

Yeah, that's a little different. In that case they've probably used one playlist to hold 3 episodes. It's possible they use the chapter points as the indicators. I've seen that on DVDs before (see the hidden option IMPORT_DVD_CHAPS), but never on a Blu-ray disc. It's more likely they've combined multiple M2TS files into a single playlist and use jump points (I think I've seen that before). I may need to see if I can find a disc from that series... I really don't want to buy the whole series just to have a look at it. It's weird that there is only one playlist available in the list -- that's for sure.

Thank you jdobbs I just do that for see whats happens but still the problem

[MrVideo]

Thank you jdobbs I just do that for see whats happens but still the problem
Download the BDEdit program, as mentioned, and use it to look at the disc's playlist structure. The program is free.

[ggtop]

Hi,

I'm having an audio delay when backing up "Now you see me 2" as alternatate output. Movie is multi-part (00003.mpls) and consists of 3 M2TS files:
1. studio logo clip (23 sec) 00003.m2ts
2. movie (2:09h) 00006.m2ts
3. short clip (1 sec) 00005.m2ts

Audio seems to be off exactly by the length of the first file.
I also tried to import the original rip and created a quick authored BD which behaves the same. Just wanted to see if a single M2TS has the same issue.
If I demux 00003.m2ts manually with TSMuxerGUI there are audio files with 23 sec of silence.

Along some screenshots from BD-RB and BDEdit if that helps.

It is the German version of that movie. Maybe someone has the same disc...

Just doing a BD 25 backup. Curious how that one comes out.

Thank you in advance
ggtop

[jdobbs]

@ggtop

I'll try the US version and see if it has the same issue.

[ggtop]

Just doing a BD 25 backup. Curious how that one comes out.

Just tested a BD25 backup. Audio is fine. Next test is an alternate movie-only output from BD25 input.

ggtop

[ggtop]

Next test is an alternate movie-only output from BD25 input.

Just created an MP4 with intact video and AAC from BD-RB processed BD25 output and it has the same ~ 23 sec delay.
Obviously the audio from segment 00003.m2ts is not taken into account on demuxing as I can see/hear that extracted file 00003.track_4352.dts does not contain 23 sec silence in the beginning.

ggtop

[Sharc]

BD-RB exits with an error when trying to import a captured .avi source.
Could it be that the lossless video format which in this case is either Huffyuf (Codec ID: HFYU) or Lagarith (Codec ID: LAGS) is not recognized?

- [10:35:07] Importing video file: (1 of 1)
- Preparing AVI for processing...
- Collecting audio/video streams from source...
[10:35:15] ERROR: Collecting video file streams. Aborted.

[jdobbs]

Just created an MP4 with intact video and AAC from BD-RB processed BD25 output and it has the same ~ 23 sec delay.
Obviously the audio from segment 00003.m2ts is not taken into account on demuxing as I can see/hear that extracted file 00003.track_4352.dts does not contain 23 sec silence in the beginning.

ggtopI looked at the US version yesterday -- and it is nothing like yours. It is broken up in to many parts.

[jdobbs]

BD-RB exits with an error when trying to import a captured .avi source.
Could it be that the lossless video format which in this case is either Huffyuf (Codec ID: HFYU) or Lagarith (Codec ID: LAGS) is not recognized?Definitely.

[Sharc]

Definitely.
I see. So the *.avi import accepts video in mpeg-1, mpeg-2, mpeg-4 (AVC), VC-1, DivX format, but not lossless, right?
If so, I have to convert the lossless VHS captures to one of the accepted import formats. It's not a big obstacle because I will normally have to preprocess the tape captures anyway.

[jdobbs]

I see. So the *.avi import accepts video in mpeg-1, mpeg-2, mpeg-4 (AVC), VC-1, DivX format, but not lossless, right?
If so, I have to convert the lossless VHS captures to one of the accepted import formats. It's not a big obstacle because I will normally have to preprocess the tape captures anyway.I went for the most common import types. If I add things that aren't accepted by TSMUXER, BD-RB has to reencode them into an acceptable format before allowing it into the pseudo-BD structure (as happens now with DIVX). Right now BD-RB accepts:

V_MPEG4/ISO/AVC
V_MPEGH/ISO/HEVC
V_MS/VFW/FOURCC / WVC1
V_MS/VFW/WVC1
V_MPEG2
V_MS/VFW/FOURCC / XVID, V_MS/VFW/FOURCC / DX50,
V_MS/VFW/FOURCC / DIV3, V_MS/VFW/FOURCC / DIV4,
V_MS/VFW/FOURCC / DIV5, V_MPEG1, V_MS/VFW/FOURCC / DIVX
A_DTS
A_AC3
A_AAC
S_TEXT/UTF8
S_TEXT/ASS
A_PCM, A_LPCM
A_MPEG/L3
A_MPEG/L2
A_MPEG/L1
S_HDMV/PGS

So what ID does MediaInfo report for your source? If LAV filters supports it and you think it is common enough to be included, I should be able to import and reencode automatically. I reencode to AVC with CRF and it defaults to crf=18. But... there is an undocumented hidden option called IMPORT_CONVERT_CRF that can change that to whatever you want (even lossless AVC). Of course, it will dramatically affect the size of the pseudo-BD structure.

[Sharc]

I went for the most common import types. If I add things that aren't accepted by TSMUXER, BD-RB has to reencode them into an acceptable format before allowing it into the pseudo-BD structure (as happens now with DIVX). Right now BD-RB accepts:

V_MPEG4/ISO/AVC
V_MPEGH/ISO/HEVC
V_MS/VFW/FOURCC / WVC1
V_MS/VFW/WVC1
V_MPEG2
V_MS/VFW/FOURCC / XVID, V_MS/VFW/FOURCC / DX50,
V_MS/VFW/FOURCC / DIV3, V_MS/VFW/FOURCC / DIV4,
V_MS/VFW/FOURCC / DIV5, V_MPEG1, V_MS/VFW/FOURCC / DIVX
A_DTS
A_AC3
A_AAC
S_TEXT/UTF8
S_TEXT/ASS
A_PCM, A_LPCM
A_MPEG/L3
A_MPEG/L2
A_MPEG/L1
S_HDMV/PGS

So what ID does MediaInfo report for your source? If LAV filters supports it and you think it is common enough to be included, I should be able to import and reencode automatically. I reencode to AVC with CRF and it defaults to crf=18. But... there is an undocumented hidden option called IMPORT_CONVERT_CRF that can change that to whatever you want (even lossless AVC). Of course, it will dramatically affect the size of the pseudo-BD structure.
From MediaInfo:
Format : HuffYUV
Format version : Version 2
Codec ID : HFYU
or:
Format : Lagarith
Codec ID : LAGS
I think theses codecs/compressors are widely used for lossless video tape captures.

[Torrentted84]

First thanks for this program, been using it for a few years already and still glad that I've found it.

Maybe these are noob questions, but can't find other place to ask them.
1. Is it normal that the bitrate stays the same when using 1080 or converterting them to 720? When having a serie which is more than 3Hours I mostly change it to 720 in setup. But the bitrate is still the same as the 1080 option.

2. When using edit mode I can decide to blank extra's, but is it possible to lower the quality for only a few extra's
- I know tthat the option "quicker encode for extra's" exist but when doing this with series it is not always clear which stream is considered as an extra.

I don't have any programming skills so I don't know how it works behind the scenes or how difficult it is.
- For instances 720 @ specific bitrate 4mbps for some (interviews or similar)
- 480 for bloopers and/or deleted scenes

[ggtop]

I looked at the US version yesterday -- and it is nothing like yours. It is broken up in to many parts.

Hi jdobbs,

it seems I found the root cause.
I played around with tsmuxer and those META files that are created by BD-RB to control the demuxing.
I created my own META file and demuxed 00003.m2ts (rather than 00003.mpls) and both DTS tracks came out with 0 KB file size. This does not happen with AC3 tracks. They have 23 sec silence and choosing one of them for the alternate output results in a perfectly in sync MP4.

00003.META
MUXOPT --no-pcr-on-video-pid --new-audio-pes --demux --vbr --vbv-len=500 --start-time=27000000

V_MPEG4/ISO/AVC, "E:\BDMV\STREAM\00003.m2ts", fps=23.976, track=4113

A_DTS, "E:\BDMV\STREAM\00003.m2ts", track=4352, lang=deu
A_AC3, "E:\BDMV\STREAM\00003.m2ts", track=4353, lang=deu
A_DTS, "E:\BDMV\STREAM\00003.m2ts", track=4354, lang=eng
A_AC3, "E:\BDMV\STREAM\00003.m2ts", track=4355, lang=eng

Is there anything BD-RB can do in cases like this?

ggtop

[jdobbs]

First thanks for this program, been using it for a few years already and still glad that I've found it.

Maybe these are noob questions, but can't find other place to ask them.
1. Is it normal that the bitrate stays the same when using 1080 or converterting them to 720? When having a serie which is more than 3Hours I mostly change it to 720 in setup. But the bitrate is still the same as the 1080 option.

2. When using edit mode I can decide to blank extra's, but is it possible to lower the quality for only a few extra's
- I know tthat the option "quicker encode for extra's" exist but when doing this with series it is not always clear which stream is considered as an extra.

I don't have any programming skills so I don't know how it works behind the scenes or how difficult it is.
- For instances 720 @ specific bitrate 4mbps for some (interviews or similar)
- 480 for bloopers and/or deleted scenes1. Yes, if you are using a target. But... since the bitrate is the same while the resolution is smaller -- it would be reasonable to say the quality would improve (assuming it isn't at/near its max).

2. Not currently.

[jdobbs]

Hi jdobbs,

it seems I found the root cause.
I played around with tsmuxer and those META files that are created by BD-RB to control the demuxing.
I created my own META file and demuxed 00003.m2ts (rather than 00003.mpls) and both DTS tracks came out with 0 KB file size. This does not happen with AC3 tracks. They have 23 sec silence and choosing one of them for the alternate output results in a perfectly in sync MP4.

00003.META
MUXOPT --no-pcr-on-video-pid --new-audio-pes --demux --vbr --vbv-len=500 --start-time=27000000

V_MPEG4/ISO/AVC, "E:\BDMV\STREAM\00003.m2ts", fps=23.976, track=4113

A_DTS, "E:\BDMV\STREAM\00003.m2ts", track=4352, lang=deu
A_AC3, "E:\BDMV\STREAM\00003.m2ts", track=4353, lang=deu
A_DTS, "E:\BDMV\STREAM\00003.m2ts", track=4354, lang=eng
A_AC3, "E:\BDMV\STREAM\00003.m2ts", track=4355, lang=eng

Is there anything BD-RB can do in cases like this?

ggtopNot really... if the DTS tracks is missing it means the the source is actually illegal, since all M2TS files of the same playlist are required to have the same track mapping.

[Sharc]

@jdobbs
Did you already have a chance to look into this. (http://forum.doom9.org/showpost.php?p=1790776&postcount=25414) (The non-playable discs for full backup SBS encodes).

[jdobbs]

@jdobbs
Did you already have a chance to look into this. (http://forum.doom9.org/showpost.php?p=1790776&postcount=25414) (The non-playable discs for full backup SBS encodes).Not yet. But I will soon.

[Lathe]

I don't have any programming skills so I don't know how it works behind the scenes or how difficult it is.
- For instances 720 @ specific bitrate 4mbps for some (interviews or similar)
- 480 for bloopers and/or deleted scenes

Ah... careful with that screen name... I can see Ch3vr0n now, sharpening his daggers and knives and polishing his sniper rifle... :sly:

Heh, well what I do with my Xtras is that you can set an overall CRF value (as oppose to bit rate) for all Xtras. I have mine set at 24, which for Xtras I find is an overall good compromise. I mean, I LOVE the Xtras in films and if I really like the movie, I generally keep all the Xtras. BUT... in most cases we ARE talking about just interviews (maybe interspersed with film clips) and like you said, Bloopers, etc. So, to me it's not like the film itself where you have to sweat the quality so much.

So, what I would suggest is find a good compromise CRF value for Xtras (I think you set that in the hidden options and add to your ini file) so that you will get an acceptable overall quality for all Xtras and yet still save a good amount of space. Many times I've noticed recently even when I have Xtras that add up to say 5 Gigs and I have BDRB encode JUST the Xtras only to make a BD5 disc (AVCHD) and I set the quality for say 'Very Fast', since I've instructed BDRB to use the alternate CRF for Xtras, usually the disc will come out only about 1.75 - 2 Gigs as opposed to filling the BD5. At first, I was wondering why and then it dawned on me that BDRB was using the alternate CRF rate for the Xtras that I had set in the ini.

I hope that helps...

[Ch3vr0n]

@lathe don't bring me in over something I've got nothing to do with. I could care less about someone's username.

Sent from my Nexus 6P with Tapatalk.

[Torrentted84]

1. Yes, if you are using a target. But... since the bitrate is the same while the resolution is smaller -- it would be reasonable to say the quality would improve (assuming it isn't at/near its max).

2. Not currently.


Thanks for the information jdobbs about the bitrate. Thought that I consult the experts with this question

Ah... careful with that screen name... I can see Ch3vr0n now, sharpening his daggers and knives and polishing his sniper rifle...

Heh, well what I do with my Xtras is that you can set an overall CRF value (as oppose to bit rate) for all Xtras. I have mine set at 24, which for Xtras I find is an overall good compromise. I mean, I LOVE the Xtras in films and if I really like the movie, I generally keep all the Xtras. BUT... in most cases we ARE talking about just interviews (maybe interspersed with film clips) and like you said, Bloopers, etc. So, to me it's not like the film itself where you have to sweat the quality so much.

So, what I would suggest is find a good compromise CRF value for Xtras (I think you set that in the hidden options and add to your ini file) so that you will get an acceptable overall quality for all Xtras and yet still save a good amount of space. Many times I've noticed recently even when I have Xtras that add up to say 5 Gigs and I have BDRB encode JUST the Xtras only to make a BD5 disc (AVCHD) and I set the quality for say 'Very Fast', since I've instructed BDRB to use the alternate CRF for Xtras, usually the disc will come out only about 1.75 - 2 Gigs as opposed to filling the BD5. At first, I was wondering why and then it dawned on me that BDRB was using the alternate CRF rate for the Xtras that I had set in the ini.

I hope that helps...

Thanks Lathe. I will definitely have a look at this.

[colinhunt]

Okay, I know pretty much nobody cares about 3D anymore. Regardless: I did The Hobbit 3D Extended Edition disc 2 last night on version 0.50.20 using FRIMSource and QSV acceleration, and while the encoding & building of .ISO happened in less than an hour (which is nice), the output has left and right views swapped. And unfortunately neither my player nor my projector offers an option for swapping the views.

I did a couple of other 3D titles as well but haven't checked them yet for this issue. Actually, I think this is not the first time I've mentioned this phenomenon in this thread. Hmm.

[jdobbs]

Okay, I know pretty much nobody cares about 3D anymore. Regardless: I did The Hobbit 3D Extended Edition disc 2 last night on version 0.50.20 using FRIMSource and QSV acceleration, and while the encoding & building of .ISO happened in less than an hour (which is nice), the output has left and right views swapped. And unfortunately neither my player nor my projector offers an option for swapping the views.

I did a couple of other 3D titles as well but haven't checked them yet for this issue. Actually, I think this is not the first time I've mentioned this phenomenon in this thread. Hmm.Did you do it in SBS or OU mode? If not then the left/right would remain unchanged -- as it is set by the original disc as flagged by the MPLS file. That, of course, would indicate a player issue unless you have set the SWAP_3D hidden option by mistake and are using SBS/OU.

Please post your log and ini, as it's hard to help when blind.

[colinhunt]

Did you do it in SBS or OU mode? If not then the left/right would remain unchanged -- as it is set by the original disc. That, of course, would indicate a player issue unless you have set the SWAP_3D hidden option by mistake (for SBS/OU).
Sorry, not SBS or OU. Full 1080p frame-packed, main movie only, to 3D .iso.

I went through my recent 3D backups, and discovered several that had their L/R views swapped. Going through .LOG I noticed I'd used both 0.50.19 and 0.50.20, and the ones done on .19 did not have their views swapped.

.INI for 0.50.19:

[Options]
VERSION=0.50.0.19
ENCODER=0
MODE=3
ENCODE_QUALITY=3
QUALITY_ULTRA=1
FRIM_SW_DECODE=0
FRIM_SW_ENCODE=0
OUTPUT_3D_ISO=1
IGNORE_3D=0
ONEPASS_ENCODING=0
AUTO_QUALITY=0
TARGET_SIZE=25300
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
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=0
AC3_REENCODE=0
AC3_640=0
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=2
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=1
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=25550
[Paths]
SOURCE_PATH=H:\
WORKING_PATH=F:\_BDRB_OUTPUT\
OUTPUT_FOLDER=Q:\_ENCODES\

Logs for titles done on .19:

[11/22/16] BD Rebuilder v0.50.19
[23:56:55] Source: STAR_TREK_BEYOND_3D_00800
- Input BD size: 42.32 GB
- Approximate total content: [02:02:22.209]
- Target BD size: 24.71 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[23:56:58] PHASE ONE, Encoding
- [23:56:58] Processing: VID_00800 (1 of 1)
- [23:56:58] Extracting A/V streams [VID_00800]
- [00:07:20] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 176,037 frames
- Bitrate: 19,700 Kbs
- Using FRIMEncoder for MVC encoding
- [00:07:20] Reencoding: VID_00800, Pass 1 of 1
- [00:54:48] Video Encode complete
- [00:54:48] Processing audio tracks
- Track 4352 (eng): Keeping original audio
[00:54:48]PHASE ONE complete
[00:54:48]PHASE TWO - Rebuild Started
- [00:54:48] Rebuilding BD-3D file Structure
[01:04:52] - Encode and Rebuild complete
[01:04:52] JOB: STAR_TREK_BEYOND_3D finished.

[11/23/16] BD Rebuilder v0.50.19
[18:49:29] Source: THE_BFG_00000
- Input BD size: 33.39 GB
- Approximate total content: [01:57:09.105]
- Target BD size: 24.95 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[18:49:31] PHASE ONE, Encoding
- [18:49:31] Processing: VID_00000 (1 of 1)
- [18:49:31] Extracting A/V streams [VID_00000]
- [18:56:25] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 168,530 frames
- Bitrate: 21,010 Kbs
- Using FRIMEncoder for MVC encoding
- [18:56:25] Reencoding: VID_00000, Pass 1 of 1
- [19:36:49] Video Encode complete
- [19:36:49] Processing audio tracks
- Track 4352 (eng): Keeping original audio
[19:36:49]PHASE ONE complete
[19:36:49]PHASE TWO - Rebuild Started
- [19:36:49] Rebuilding BD-3D file Structure
[19:46:47] - Encode and Rebuild complete
[19:46:47] JOB: THE_BFG finished.

.INI for 0.50.20:

[Options]
VERSION=0.50.0.20
ENCODER=0
MODE=3
OUTPUT_FOLDER=Q:\_ENCODES
ENCODE_QUALITY=3
QUALITY_ULTRA=1
FRIM_SW_DECODE=0
FRIM_SW_ENCODE=0
OUTPUT_3D_ISO=1
IGNORE_3D=0
ONEPASS_ENCODING=0
AUTO_QUALITY=0
TARGET_SIZE=25300
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
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=0
AC3_REENCODE=0
AC3_640=0
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=2
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=1
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=24900
[Paths]
SOURCE_PATH=H:\
WORKING_PATH=F:\_BDRB_OUTPUT\

Logs for titles done on .20; all these had their views swapped, even the one that wasn't re-encoded.

[01/11/17] BD Rebuilder v0.50.20
[20:17:06] Source: HOBBIT_EXT_PT1_D2_00100
- Input BD size: 27.62 GB
- Approximate total content: [01:23:28.378]
- Target BD size: 24.95 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[20:17:09] PHASE ONE, Encoding
- [20:17:09] Processing: VID_00006 (1 of 1)
- [20:17:09] Extracting A/V streams [VID_00006]
- [20:22:03] Reencoding video [VID_00006]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 120,081 frames
- Bitrate: 33,388 Kbs
- Using FRIMEncoder for MVC encoding
- [20:22:03] Reencoding: VID_00006, Pass 1 of 1
- [20:48:52] Video Encode complete
- [20:48:52] Processing audio tracks
- Track 4352 (eng): Keeping original audio
[20:48:52]PHASE ONE complete
[20:48:52]PHASE TWO - Rebuild Started
- [20:48:52] Rebuilding BD-3D file Structure
[20:59:20] - Encode and Rebuild complete
[20:59:20] JOB: HOBBIT_EXT_PT1_D2 finished.


[01/11/17] BD Rebuilder v0.50.20
[21:49:14] Source: IT_CAME_FROM_OUTER_SPACE_00230
- Input BD size: 20.10 GB
- Approximate total content: [01:20:18.271]
- Target BD size: 24.95 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), ABR
- Output folder: Q:\_ENCODES\
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[21:49:18] PHASE ONE, Encoding
- [21:49:18] Processing: VID_00300 (1 of 1)
- [21:49:18] Extracting A/V streams [VID_00300]
- [21:53:33] Reencoding video [VID_00300]
- [21:53:33] Keeping original video (no reencode)
- [21:53:33] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (eng): Keeping original audio
[21:53:33]PHASE ONE complete
[21:53:33]PHASE TWO - Rebuild Started
- [21:53:33] Rebuilding BD-3D file Structure
[22:00:37] - Encode and Rebuild complete
[22:00:37] JOB: IT_CAME_FROM_OUTER_SPACE finished.

[01/12/17] BD Rebuilder v0.50.20
[16:16:25] Source: STORKS_00098
- Input BD size: 27.70 GB
- Approximate total content: [01:26:57.879]
- Target BD size: 24.32 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), ABR
- Output folder: Q:\_ENCODES\
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[16:16:27] PHASE ONE, Encoding
- [16:16:27] Processing: VID_00042 (1 of 1)
- [16:16:27] Extracting A/V streams [VID_00042]
- [16:21:58] Reencoding video [VID_00042]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 125,104 frames
- Bitrate: 33,863 Kbs
- Using FRIMEncoder for MVC encoding
- [16:21:58] Reencoding: VID_00042, Pass 1 of 1
- [16:52:39] Video Encode complete
- [16:52:39] Processing audio tracks
- Track 4352 (eng): Keeping original audio
[16:52:39]PHASE ONE complete
[16:52:39]PHASE TWO - Rebuild Started
- [16:52:39] Rebuilding BD-3D file Structure
[17:01:13] - Encode and Rebuild complete
[17:01:13] JOB: STORKS finished.

There was one more title done on .20, a German oddity titled Lichtmond, but I can't be sure if its views were swapped or not. It's basically a demo of extreme 3D, and watching it feels like someone's trying to yank my eyeballs out of my head.

[brunchto]

There is a SWAP_3D hidden option? I missed it 😭... I will try

[jdobbs]

@colinhunt

Nothing changed related to 3D between 0.50.19 and 0.50.20 -- so that isn't likely. As I said, if you aren't doing OU/SBS then the determination of which is right/left is in the MPLS file. It isn't something that BD-RB manipulates. I can check and see if there might be something at play in the FRIM command line -- but it is unlikely.

[jdobbs]

There is a SWAP_3D hidden option? I missed it 😭... I will tryJust remember that it only applies to SBS/OU.

[colinhunt]

Nothing changed related to 3D between 0.50.19 and 0.50.20 -- so that isn't likely. As I said, if you aren't doing OU/SBS then the determination of which is right/left is in the MPLS file. It isn't something that BD-RB manipulates. I can check and see if there might be something at play in the FRIM command line -- but it is unlikely.
Something's wonky for sure, since the views are correct on the original discs. I'm re-doing a couple of titles on .19 now that were previously done on .20 to see if output is any different views-wise.

Additional datapoints:

Did "Storks" on 0.50.19: output has swapped views.
Played original on same player & projector in 3D: views are correct.

Checked "It Came From Outer Space" original (i.e. the one that was not re-encoded but output had swapped views regardless): views are correct.

Could this have something to do with FRIMdecoder? I'll test by running another backup of Storks, this time with FRIMdecoder set to software.

[brunchto]

Just remember that it only applies to SBS/OU.



Ahh, thats why i miss it. I convert 3d br to iso, then extract m2ts file which works on my oppo. To bad i cannot switch L/R😢 since some m2ts have swapped eyes

[jdobbs]

Something's wonky for sure, since the views are correct on the original discs. I'm re-doing a couple of titles on .19 now that were previously done on .20 to see if output is any different views-wise.Are you using the version of FRIM that comes with BD-RB? There's just no changes to 3D between those versions.

[colinhunt]

Are you using the version of FRIM that comes with BD-RB? There's just no changes to 3D between those versions.
The ones in BD-RB's Tools directory? Yes, I haven't touched those.

The only reason I mentioned .19 and .20 is that the titles I did earlier on .19 had correct views. But I've now done Storks on both .19 and .20, and both outputs had swapped views so yeah, that's not the explanation.

[MrVideo]

I could care less about someone's username.
So, you can care less about someone's username. :eek:

[jdobbs]

The ones in BD-RB's Tools directory? Yes, I haven't touched those.

The only reason I mentioned .19 and .20 is that the titles I did earlier on .19 had correct views. But I've now done Storks on both .19 and .20, and both outputs had swapped views so yeah, that's not the explanation.What player are you using? It's possible that your player isn't heeding the MPLS specified left/right configuration.

[colinhunt]

What player are you using? It's possible that your player isn't heeding the MPLS specified left/right configuration.
It's a Pioneer stand-alone player. I don't think it's the culprit here, to be honest.

I've just finished another backup of Storks, this time with FRIMdecoder set to software instead of "automatic", and about to check whether it made a difference.

update: Nope, views swapped again.

Running one more backup, this time on a rig that does not have QSV.

Although... thinking about this logically, the issue's not in the encoding since views got swapped even when there was no need for re-encoding.

[colinhunt]

Something very odd is happening with 3D titles. I hope someone here can shed some light on it.

I used MakeMKV to create an MKV file which has a Stereo AVC video stream in it. Note that the MKV was created directly from data which played correctly on a stand-alone Blu-ray player. I played the MKV on Stereoscopic Player which is capable of reading and displaying Stereo streams muxed into an MKV container. To my surprise, the left and right views are swapped in the MKV -- just like they were in the 3D Blu-ray I created using BD-RB. But again, the views are not swapped in the original data/disc.

What the heck is going on here? Is there something in the data that "forces" applications into reading l/r configuration data incorrectly?

[jdobbs]

Something very odd is happening with 3D titles. I hope someone here can shed some light on it.

I used MakeMKV to create an MKV file which has a Stereo AVC video stream in it. Note that the MKV was created directly from data which played correctly on a stand-alone Blu-ray player. I played the MKV on Stereoscopic Player which is capable of reading and displaying Stereo streams muxed into an MKV container. To my surprise, the left and right views are swapped in the MKV -- just like they were in the 3D Blu-ray I created using BD-RB. But again, the views are not swapped in the original data/disc.

What the heck is going on here? Is there something in the data that "forces" applications into reading l/r configuration data incorrectly?I would be almost willing to bet that the views aren't being swapped -- but that they are just different from the offset. Normally the base part of the MVC pair is the left view and the dependent portion is right. But there is a flag in the MPLS that can indicate that the base part represents the right view (called Base_view_R_flag in the AppInfoPlayList() table). More than likely the programs you are using aren't looking at that flag and always assumes it is left. BD-RB just leaves the flag as-is and and reencodes the MVC when doing a full backup.

[colinhunt]

I would be almost willing to bet that the views aren't being swapped -- but that they are just different from the offset. Normally the base part of the MVC pair is the left picture. But there is a flag in the MPLS that can indicate that the base part represents the right view. More than likely the programs you are using aren't looking at that flag and always assumes it is left.
Forgetting MakeMKV and Stereoscopic Player for now as I used them this one time to test a theory, the only program involved in addition to BD-RB is the decrypter which is also used for making the .iso file. That .iso file (the data contained within it, to be precise) plays perfectly on a stand-alone player, no problem with L/R views being swapped.

But after that very same data in that .iso file is processed by BD-RB (or MakeMKV, it seems), the output suffers from swapped views. Even when the 3D video has not been re-encoded.

Can you think of any explanation for why that is happening? Could it be that whatever piece of code is in charge of reading the flag you mentioned is not working properly?

Theory: the 3D titles that don't suffer from swapped views after processing have the base part as the left view. The 3D titles that suffer from swapped views have right view as the base part, and for some reason BD-RB (and MakeMKV) are not reading -- or copying to output -- that piece of information.

[jdobbs]

It's possible that BD-RB isn't setting that flag when doing a movie-only backup (for some reason I was thinking you were doing a full backup). I'll do some checking. In the meantime, if you have a hex editor you can look at the byte at offset 0x38 in the MPLS file of the output. If bit 4 (masked by 0x10) isn't set -- it probably should be. If it isn't set, try setting it, burn to a BD-RW, and that should fix it.

[colinhunt]

(for some reason I was thinking you were doing a full backup).
I would love to do a full backup but BD-RB outputs it into a BDMV directory structure, even when I have the "output to iso" set to 1.

In the meantime, if you have a hex editor you can look at the byte at offset 0x38 in the MPLS file of the output. If bit 4 (masked by 0x10) isn't set -- it probably should be. If it isn't set, try setting it, burn to a BD-RW, and that should fix it.
That was all gobbledygook to me, but I'll look into it, thanks. Perhaps an old dog can learn new tricks after all.

[Lathe]

So, you can care less about someone's username. :eek:

NO! Don't wake him up again...

When will I learn... http://lathe-of-heaven.com/doh.gif

[jdobbs]

I would love to do a full backup but BD-RB outputs it into a BDMV directory structure, even when I have the "output to iso" set to 1.


That was all gobbledygook to me, but I'll look into it, thanks. Perhaps an old dog can learn new tricks after all.You can't do full backup to ISO format (keeping the SSIF folder) because TSMUXER can't support it. The only way I could do that would be to create the ISO myself -- and I think that's beyond the scope of what I want BD-RB to do.

[jdobbs]

I would love to do a full backup but BD-RB outputs it into a BDMV directory structure, even when I have the "output to iso" set to 1.


That was all gobbledygook to me, but I'll look into it, thanks. Perhaps an old dog can learn new tricks after all.If you send me the original MPLS file for the main feature and the new one created for movie-only I can at least see whether that is the issue.

Thinking about it, though, that may be the issue. I can't modify an MPLS that has been output to ISO...

[jdobbs]

If you send me the original MPLS file for the main feature and the new one created for movie-only I can at least see whether that is the issue.

Thinking about it, though, that may be the issue. I can't modify an MPLS that has been output to ISO...Never mind. There is an option available in TSMUXER to set the base to right-eye, and I'm not setting it for movie-only. I'm surprised I haven't gotten this reported before -- but I think the vast majority of discs default to having the left eye in the base stream.

I'm pretty sure that is the issue you're experiencing. I'll get a fix in for the next release. It might be a few days, though, as I want to also address Sharc's issue (http://forum.doom9.org/showthread.php?p=1793045#post1793045) in that release as well.

[Donuts]

hi

i have two mkv movie files that have a truehd 7.1 track. according to the listing on blu-ray.com these also have a dolby atmos track. i don't see that listing in my mediainfo app. i use bdrebuilder cause the two mkvs have a resolution of 1920 and a number close to 1080. for example 804. id like to burn these for more convenience. these are color regraded copies so i'd like to archive these. the size of both of these mkvs look like they can be put on bd25's. everytime i use bdrebuilder using these instructions i got from a friend who does the same thing the resulting bd folder's movie file has only dolby ac3 5.1. i can play the original mkv in truehd 7.1 so i don't think there's a incompatibility issue. here are my settings:

custom target size: 24200mb
high priority
highest very slow
one pass ABR encoding

https://puu.sh/tkAYf/dfe641b1b9.png

i thought i read on the faq that if you set your settings to encode to bd50 it will retain the truehd 7.1. i tried that last night and i woke up to find that it still only had the ac3 5.1 track.

here's the log file for when i tried to make a bd50. unfortunately i can't find a log file for when i last tried to make a bd25 for this mkv. but if you need one lemme know. thanks in advance!!!

[Lathe]

hi

i have two mkv movie files that have a truehd 7.1 track. according to the listing on blu-ray.com these also have a dolby atmos track. i don't see that listing in my mediainfo app. i use bdrebuilder cause the two mkvs have a resolution of 1920 and a number close to 1080. for example 804. id like to burn these for more convenience. these are color regraded copies so i'd like to archive these. the size of both of these mkvs look like they can be put on bd25's. everytime i use bdrebuilder using these instructions i got from a friend who does the same thing the resulting bd folder's movie file has only dolby ac3 5.1. i can play the original mkv in truehd 7.1 so i don't think there's a incompatibility issue. here are my settings:

custom target size: 24200mb
high priority
highest very slow
one pass ABR encoding

https://puu.sh/tkAYf/dfe641b1b9.png

i thought i read on the faq that if you set your settings to encode to bd50 it will retain the truehd 7.1. i tried that last night and i woke up to find that it still only had the ac3 5.1 track.

here's the log file for when i tried to make a bd50. unfortunately i can't find a log file for when i last tried to make a bd25 for this mkv. but if you need one lemme know. thanks in advance!!!

Well, 2 things I notice right away:

1. when a Blu-ray is rendered into an MKV file and also happens to have a TrueHD audio track, the AC3 core is ALWAYS ripped out. What that means is that when you then go from the MKV back to a playable Blu-ray or a BDMV folder, all that remains is just an AC3 @640 track. This took me a while to learn when I kept encountering all these TrueHD audio tracks, and apparently like you, I also like to keep the full HD audio if possible.

The ONLY way that I know to go from MKV to Blu-ray and retain the full TrueHD audio is to use a free program called eac3to. I use the GUI or interface with it called UsEac3to. When you drop the full MKV into the interface, in the dropdown menu where you 'read' the existing tracks, you choose the 'TRUE' track. Next to it in the dropdown menu you then choose the 'TRUE + AC3' option, which is the form in which you will be rendering it. THAT way, the resulting audio track will have the full TrueHD audio WITH the AC3 core put back in. NOW, you can then use this restored track and drop it in another free program TSMuxer (which BDRB uses in reconstructing the BDMV folder) and now it WILL keep the full HD audio.

Also, 2. When you have an illegal AR like 1920x800 (that means that the normal black bars in the full Blu-ray have been cropped out) remember that your Blu-ray player may NOT play the picture properly. My OPPO Blu-ray player will NOT if the AR (aspect ratio) is not a fully legal 1920x1080. Otherwise, what it does is STRETCH the picture to fill the screen since the black bars that would normally border the picture are gone. So, with my OPPO I absolutely CANNOT do that. I CAN get away with it IF the AR is 1.85:1 by changing the playback on my player to render the screen in a 4x3 Letterboxed mode. But, that does NOT work with the much more common 2.35:1 and 2.40:1 AR seen in most movies.

That is the trouble that I run into a LOT when I, uh, 'come across' certain MKV files where the black bars have been stripped out. In those cases I have 2 choices. 1) I can give up the full HD audio (because my OPPO ONLY plays HD audio within BDMV folders, NOT in MKV files) and just play the MKV's on my player as is. Or 2) I can re-encode the video and put the black bars back in using either BDRB or more simply the CMD line using x264. But, unfortunately, that means an additional re-encoding which isn't ideal. I HAVE to do one or the other if I want to be able to play the movie and have it look right.

I hope that that made some sense and I hope that it helps...

[MrVideo]

Well, 2 things I notice right away:

1. when a Blu-ray is rendered into an MKV file and also happens to have a TrueHD audio track, the AC3 core is ALWAYS ripped out. What that means is that when you then go from the MKV back to a playable Blu-ray or a BDMV folder, all that remains is just an AC3 @640 track. This took me a while to learn when I kept encountering all these TrueHD audio tracks, and apparently like you, I also like to keep the full HD audio if possible.
You can't rip out the AC3 core and have AC3 5.1 to put back into a Blu-ray. If you rip out the AC3 core, you are left with only the TrueHD portion. While doing some digging, I found an old posting:
There are 2 different TrueHD streams:

(1) TrueHD+AC3. This is a mixed format. There are both (alternating) TrueHD and AC3 frames in the stream.

(2) TrueHD. This stream only contains TrueHD frames and no AC3 frames.

All Blu-Ray TrueHD streams are (1). All HD DVD TrueHD streams are (2). eac3to can convert between both stream types. Converting from (1) to (2) is very easy: The AC3 frames are simply removed. Converting from (2) to (1) is more difficult: The TrueHD stream must be decoded and reencoded to AC3 and then the AC3 frames must be injected into the TrueHD stream in a specific way.

When muxing to MKV, the AC3 frames are usually removed, so MKV TrueHD streams are usually type (2).

There's no special metadata which tells anyone how to convert TrueHD to AC3, AFAIK.
So, if you have a MKV file that contains only AC3, because the TrueHD was thrown away, there is no way to get back the TrueHD.

As for mkvmerge's handling of TrueHD+AC3, I found the following:
The Matroska specs state that one track must only contain data for one codec. Therefore mkvmerge cannot keep the AC-3 interleaved with the TrueHD part in a single track.

Starting with release 7.7.0, mkvmerge's solution is to present the AC-3 core as an additional track. This applies to TrueHD tracks read from any source file, be it from e.g. a raw TrueHD file, from a Matroska file or an MPEG transport stream. Before release 7.6.0, mkvmerge was silently discarding the AC-3 core.

Now comes the tricky part. If you've created a MKV file with a newer mkvmerge, so that you have both audio tracks, getting it back into the required Blu-ray spec is going to be tough. Why? Because the two audio tracks must be interleaved in a very special way. The first quote seems to imply that eac3to can be used to interleave the two streams into a single TrueHD+AC3 for Blu-ray use. I've never tried it.

[colinhunt]

I'm surprise I haven't gotten this reported before
I have a feeling I probably did, or at least tried to, quite a long time ago... but it's likely I didn't provide you with enough data back then.

I'm pretty sure that is the issue you're experiencing. I'll get a fix in for the next release. It might be a few days, though, as I want to also address Sharc's issue (http://forum.doom9.org/showthread.php?p=1793045#post1793045) in that release as well.
This is fantastic news - looking forward to testing the fix! Thank you!

[jdobbs]

I have a feeling I probably did, or at least tried to, quite a long time ago... but it's likely I didn't provide you with enough data back then.


This is fantastic news - looking forward to testing the fix! Thank you!Fixed for the next release.

[jdobbs]

@Sharc

I started looking at the issue you reported -- and, while it's been awhile since I worked on it, I don't think I ever intended for output to SBS to work with full backups. It was meant for Movie-Only (mainly ALTERNATE output).

So the question is: Are you reporting this as a bug because setting that flag is causing issues on full backups (when it shouldn't) -- or do you actually want to create a full backup in which all the 3D sources are converted to SBS? The only reason I can think that anyone would ever want the latter is if they have a 3D monitor hooked up to a 2D player. That seems counter-intuitive since a 3D monitor is a lot more expensive than a 3D player.

Can you clarify?

[Lathe]

You can't rip out the AC3 core and have AC3 5.1 to put back into a Blu-ray. If you rip out the AC3 core, you are left with only the TrueHD portion. While doing some digging, I found an old posting:

So, if you have a MKV file that contains only AC3, because the TrueHD was thrown away, there is no way to get back the TrueHD.

As for mkvmerge's handling of TrueHD+AC3, I found the following:


Now comes the tricky part. If you've created a MKV file with a newer mkvmerge, so that you have both audio tracks, getting it back into the required Blu-ray spec is going to be tough. Why? Because the two audio tracks must be interleaved in a very special way. The first quote seems to imply that eac3to can be used to interleave the two streams into a single TrueHD+AC3 for Blu-ray use. I've never tried it.

Yes, my friend... But, you are overthinking it... All I am saying is that when you have an MKV file that MediaInfo SHOWS has a TrueHD audio stream, that stream has had the core removed. So, simply by using UsEac3to (or eac3to) you can generate and add back in the AC3 core. I've done it many times.

This guy above says that when he tries to mux his MKV file into a playable Blu-ray, the resulting file is only the AC3 @640 part of it. I don't know the 'ins & outs' of it in detail, but quite a while ago I was having the exact same thing happen and I found threads (probably here) that explained how to use eac3to to add the 'core' back in so that TSMuxer can recognize and process it.

That's all...

[Sharc]

@Sharc

I started looking at the issue you reported -- and, while it's been awhile since I worked on it, I don't think I ever intended for output to SBS to work with full backups. It was meant for Movie-Only (mainly ALTERNATE output).

So the question is: Are you reporting this as a bug because setting that flag is causing issues on full backups (when it shouldn't) -- or do you actually want to create a full backup in which all the 3D sources are converted to SBS? The only reason I can think that anyone would ever want the latter is if they have a 3D monitor hooked up to a 2D player. That seems counter-intuitive since a 3D monitor is a lot more expensive than a 3D player.

Can you clarify?
I reported is as a bug, but probably I mis-interpreted the documentation: The selection in the setting menu is indeed for "Enable 3D SBS/OU Movie-only output", but from the changes.txt:
April 7th, 2014 - v0.47.04
- Implemented 3D Full Backup Mode. Note that
BD-RB converts 3D method so that the SSIF
folder is no longer required -- the method
is 100% compliant with the BD standard.
(v0.47.03)
So my (generous) conclusion was that when selecting "Full backup" plus "Enable 3D SBS/OU Movie-only output", the feature will be encoded SBS and the rest (menus + extras) will be encoded as in-muxed MVC/FRIM. I found that this actually happens with the files, but the disc is not playable (because playlists and clpi are not processed accordingly, I think).

But as you write SBS has been intended for Movie-only, it's not a bug, and I shouldn't select "Full backup".
Could it be read as a feature request? Well, I understand that the 3D wave seems to have swapped over us, so maybe it's not worth the efforts....

[jdobbs]

I reported is as a bug, but probably I mis-interpreted the documentation: The selection in the setting menu is indeed for "Enable 3D SBS/OU Movie-only output", but from the changes.txt:

So my (generous) conclusion was that when selecting "Full backup" plus "Enable 3D SBS/OU Movie-only output", the feature will be encoded SBS and the rest (menus + extras) will be encoded as in-muxed MVC/FRIM. I found that this actually happens with the files, but the disc is not playable (because playlists and clpi are not processed accordingly, I think).

But as you write SBS has been intended for Movie-only, it's not a bug, and I shouldn't select "Full backup".
Could it be read as a feature request? Well, I understand that the 3D wave seems to have swapped over us, so maybe it's not worth the efforts....The interesting thing is that whether I meant to or not, the setting does have an effect on full backup mode. So I have to either fix that, or make it work for both modes.

[Lathe]

Hmmm, for some odd (but excellent) reason, now with this current version my CRF is working for the very first time. As my log of the running process shows below, the constant rate factor IS indeed being used in the current pass encode, and this for the very first time ever! So, that is good...

I was curious though, the log also shows a set output size (my poor@ss guess, really) BUT, it is indeed using the constant rate factor on the 2nd video stream, and I'm assuming that it will also do so on the last video stream, which is the primary movie file.

Sooooo... why is it showing an output size...?

----------------------
[01/13/17] BD Rebuilder v0.50.20
[21:35:49] Source: VID00000
- Input BD size: 29.49 GB
- Approximate total content: [02:04:23.014]
- Target BD size: 14.36 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), CRF
- X264 Tweak(s) enabled
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=192
[21:35:49] PHASE ONE, Encoding
- [21:35:49] Processing: VID_00003 (1 of 3)
- [21:35:49] Extracting A/V streams [VID_00003]
- [21:35:55] Reencoding video [VID_00003]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,374 frames
- [21:35:55] Reencoding: VID_00003, Pass 1 of 1
- [21:36:24] Video Encode complete
- [21:36:24] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [21:36:24] Multiplexing M2TS
- [21:36:28] Processing: VID_00004 (2 of 3)
- [21:36:28] Extracting A/V streams [VID_00004]
- [21:37:03] Reencoding video [VID_00004]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 34,330 frames
- [21:37:03] Encoding using constant rate factor.


My ini:

[Options]
VERSION=0.50.0.20
ENCODER=0
MODE=0
ENCODE_QUALITY=2

TWEAK_PASS_TWO=--ref 4 --deblock -3:-3 --psy-rd 1.00:0.25 --me umh --subme 8 --trellis 2 --direct auto
ONEPASS_ENCODING=1
IVTC_480i=0
IVTC_METHOD=0
AUTO_QUALITY=0
FIXED_CRF=20
AUTO_BIAS=3
B_PYRAMID=1
QUICK_CRF=24
ENABLE_TEST=1
ENABLE_BLANKING=1

ARCHIVE_ENABLE=1
ARCHIVE_LIMIT=1
ARCHIVE_265=0
ARCHIVE_AUDIO_100
ARCHIVE_CRF=18

KEEP_HD_LPCM=1
USE_ZLIB=0

ALTERNATE_BLURAY=0
ENCODER_MENU=1
MBTREE=1

MENU_BACKGROUND=D:\EXECUTABLES\BD-RBV05017\BD_Rebuilder\misc\menuback.jpg
MENU_AUDIO=D:\EXECUTABLES\BD-RBV05017\BD_Rebuilder\tools\blankclip\blank.ac3
IMPORT_THRESHOLD=1
QUICK_PLAY_THRESHOLD=1
MENU_AUTO_BACKGROUND=1
MENU_AUTO_DVDAUDIO=1
AUTO_QUALITY=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;

SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=1
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=0
AC3_192=1
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=0
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=14700
TARGET_SIZE=23700
PRIORITY_CLASS=0
QUICK_EXTRAS=1
WIDE_PERCENT=40
WIDE_OFFSET=.85
AVSFilter01=Sharpen(.3)
[Paths]
WORKING_PATH=C:\_______MEDIA\_BDRB\
SOURCE_PATH=J:\_______VID00000

[Lathe]

So, the encode finished and coincidentally the overall finished size was about 14.6 Gigs... Uh, that was uncannily very close to the wild 'guess' I made when I set the output size (see above)

BUT... the video was definitely using a CRF of 20 when it re-encoded. Sooooo, was I just amazingly brilliant in my guess as to what I THOUGHT the output size should be using a CRF of 20, or did BDRB in some way use the expected output size even though it did indeed use CRF 1 pass on the encode...???

I thought when you use CRF 1 pass that the output size is disregarded, right...? So:

1. Why did the log file show an intended output size...?

2. Although definitely using a CRF 1 pass encode, how the hell could have hit so close to what I just happened to have put in as an output size...?

3. When using CRF 1 pass, shouldn't the output size be greyed out anyway?

I mean, I am ecstatic that the CRF is finally working and I'm not getting the constant, stupid, meaningless, and inaccurate 'AnyDVD short titles' error that I ALWAYS got before when I tried to use CRF encoding, but I don't understand how the supposedly 'disregarded' output size factored into it this time.

[gonca]

Can you post LASTCMD.txt Lathe?

[jdobbs]

So, the encode finished and coincidentally the overall finished size was about 14.6 Gigs... Uh, that was uncannily very close to the wild 'guess' I made when I set the output size (see above)

BUT... the video was definitely using a CRF of 20 when it re-encoded. Sooooo, was I just amazingly brilliant in my guess as to what I THOUGHT the output size should be using a CRF of 20, or did BDRB in some way use the expected output size even though it did indeed use CRF 1 pass on the encode...???

I thought when you use CRF 1 pass that the output size is disregarded, right...? So:

1. Why did the log file show an intended output size...?

2. Although definitely using a CRF 1 pass encode, how the hell could have hit so close to what I just happened to have put in as an output size...?

3. When using CRF 1 pass, shouldn't the output size be greyed out anyway?

I mean, I am ecstatic that the CRF is finally working and I'm not getting the constant, stupid, meaningless, and inaccurate 'AnyDVD short titles' error that I ALWAYS got before when I tried to use CRF encoding, but I don't understand how the supposedly 'disregarded' output size factored into it this time.Choosing CRF should hit your target. BD-RB is supposed to do a couple of sample passes to predict what CRF is needed to hit the target. But I didn't see the prediction in you log...

[edit]. Oh, I see, you used a forced CRF. That just means you had a lucky guess at the CRF needed to hit your output size.

The target size will show in the log, even if you've chosen to ignore it.

[jdobbs]

Could it be read as a feature request? Well, I understand that the 3D wave seems to have swapped over us, so maybe it's not worth the efforts....Can you give me an example of where it would be useful? I don't think I get the actual application of such an output? If the extras, etc., were encoded in normal (in-mux) 3D -- that would imply you have a 3D player. So what is the advantage of having the feature in SBS format?

[Sharc]

Can you give me an example of where it would be useful? I don't think I get the actual application of such an output? If the extras, etc., were encoded in normal (in-mux) 3D -- that would imply you have a 3D player. So what is the advantage of having the feature in SBS format?
Yes, I do have a 3D player. My justification of SBS is the compression for the NAS. SBS gives better visual quality than MVC/FRIM when compressing to <<BD25. So I could make a full disc backup say at CRF20 which results in an SBS feature size of say 6 .. 10GB (depending on the source of course). I can then copy the compressed SBS feature .m2ts to the NAS for streaming and keep the full backup on a (underutilized) BD25 with the menu and Extras.
It is not terribly important, so you could perhaps just gray out the "Enable 3D SBS/OU movie-only output" when "Full backup" is selected which would prevent users to produce non-playable discs.

[Lathe]

Choosing CRF should hit your target. BD-RB is supposed to do a couple of sample passes to predict what CRF is needed to hit the target. But I didn't see the prediction in you log...

[edit]. Oh, I see, you used a forced CRF. That just means you had a lucky guess at the CRF needed to hit your output size.

The target size will show in the log, even if you've chosen to ignore it.

Oh, I see (I think...) So, when choosing CRF 1 pass generally, you WOULD select an output size and BDRB would then approximate what CRF value to use to render that output size, right?

BUT... if you use FORCED CRF as I have in my ini, THEN BDRB, although showing whatever output size was entered, goes ahead and just uses the Forced CRF and ignores the output size, right?

This is just frigg'n AWESOME man because this is the very first time it has actually worked without throwing that stupid error! :D

[geheim]

@jdobbs
Did you ever look into the issue where 3D subtitle depth is lost if reencoding with FRIM?? You said some time ago that you would try if it would be possible to set a constant depth value to the Subs which would be good because flat subtitles often cut through objects in 3D movies which makes a bad visual Feeling...
Thanks for your effort!

[raul124]

@jdobbs
Did you ever look into the issue where 3D subtitle depth is lost if reencoding with FRIM?? You said some time ago that you would try if it would be possible to set a constant depth value to the Subs which would be good because flat subtitles often cut through objects in 3D movies which makes a bad visual Feeling...
Thanks for your effort!:goodpost: I too need to turn off the subtitles because of bad visual feeling.

[LowDead]

@jdobbs: Seems to be problem with the clpi files. The header looks wrong, should be HDMV0100 for AVCHD, now it only says HDMV. Tried to hexedit that but didn't help. So seems to be more problem with that as BDedit complains about the file packets and also no info comes up. index.bdmv, MovieObject.bdmv and the mpls files looks to be fine.

/LD

[MrVideo]

I found a minor bug with the Page/Prev/Next labels.

It seems that the left margin of the page label is set to the left margin of the selection text. The right margin of the prev/next text is equal to the right margin of the selection text.

The problem is that when the titles of the selection text is only one word long, the total length is too short, resulting in the text for PREV to be situated on top of the page # text.

I think the temporary cure, in my case, is to put a bunch of spaces at the end of the text of one of the titles.

[jdobbs]

@jdobbs: Seems to be problem with the clpi files. The header looks wrong, should be HDMV0100 for AVCHD, now it only says HDMV. Tried to hexedit that but didn't help. So seems to be more problem with that as BDedit complains about the file packets and also no info comes up. index.bdmv, MovieObject.bdmv and the mpls files looks to be fine.

/LDHave you run any other software on them or edited them? I just checked several AVCHD titles that I've done recently -- and they all have the HDMV0100 header and BDEdit opens them fine. I'll do a couple more as a test and see if I can find anything.

[Edit] Never mind. I found it. It has been fixed for the next release. It can only happens when doing non-movie-only AVCHD backups.

[jdobbs]

I have updated the first post of this thread with a link to the latest version of BD-RB (v0.50.21). Changes for this release:- Corrected an error in which 3D sources in
SBS/OU output mode were not forced to be
encoded when the original was small enough
to fit on the target.
- Added a new hidden option. IVTC_1080p will
force inverse telecining on 1080p sources
that have a framerate of 29.97fps. Care
should be taken -- as this should only be
set when you know the source was originally
filmed at 24fps (23.976).
- Added a new filter prefix. "L:nnnnn". It
applies the specified filter only when the
M2TS being encoded is found in the playlist
specified by "nnnnn". As an example, a line
containing "l:00001Tweak(bright=10.0)" would
increase the brightness only on video that
is a part of playlist 00001.
- Corrected a "CreateQuickMenu(), 0000, 4020"
error that can occur when using a complex
font for a Quick Menu or Import.
- Fixed an issue in which reencoding audio to
ALTERNATE/Auto-AC3 from an Auto-AC3 (VBR)
source could result in blank output.
- Fixed an issue in which a 3D source feature
that is flagged for the base view to be the
right picture (atypical) was not carrying
over when outputting to a non-ALTERNATE
movie-only structure. The result would be
an apparent swapped left/right picture.
- Corrected a problem in which .SRT files
that had the same name (minus extension) as
an imported file source were not being
imported on containers other than the .MKV
format.
- Fixed an issue in which selecting output to
3D/SBS for movie-only encoding could have
and unexpected impact on a full 3D backup.
- Corrected a problem in which variable frame
rate sources could, under certain conditions
result in out-of-sync audio during the file
import process.
- Fixed an issue in which the HDMV header on
CLPI files of AVCHD backups could be created
incorrectly.
- Updated the included version of X265.EXE to
the latest release (v2.2.17).
- Updated the included version of X265-64.EXE
to the latest release (v2.2.17).
- Other minor corrections and cosmetic fixes.

[MrVideo]

- Added a new hidden option. IVTC_1080p will
force inverse telecining on 1080p sources
that have a framerate of 29.97fps. Care
should be taken -- as this should only be
set when you know the source was originally
filmed at 24fps (23.976).
Dumb question. How can you IVTC 1080p video? 720p59.94, but not 1080p. IVTC is done on 1080i video.

1080p means that the 1080i was deinterlaced, making IVTC impossible.

[jdobbs]

Dumb question. How can you IVTC 1080p video? 720p59.94, but not 1080p. IVTC is done on 1080i video.

1080p means that the 1080i was deinterlaced, making IVTC impossible.Nope. That is an incorrect statement. I do it all the time. If you capture from satellite, for example, it's 1080p at 29.97fps. If you look at it (and it is an original film source) you'll see that every 5th frame is repeated. Telecining doesn't imply interlaced video. In this case it just represents converting 23.976fps original video to 29.97fps by repeating a frame. It's hard-telecined (meaning it doesn't use flags to create the additional frame). Mixing odd/even fields from two frames of an interlaced source to add an additional frame is one type of telecining -- but not the only one.

Anyway, it's meant as an additional tool for those who need it (like me), not as a focus for a debate on semantics.

[LowDead]

- Fixed an issue in which the HDMV header on
CLPI filse of AVCHD backups could be created
incorrectly.

Thanx. Will try it tonight.

//LD

[MrVideo]

If you look at it (and it is an original film source) you'll see that every 5th frame is repeated. Telecining doesn't imply interlaced video. In this case it just represents converting 23.976fps original video to 29.97fps by repeating a frame.
Must be DirecTV or Dish, since 1080p isn't allowed for ATSC compliant transmissions. All 1080 cable channel sources (AMC, TNT, etc.) that have scripted dramas will be 1080i 2:3 pulldown.

Here is some tidbit info. Warner Bros. programs that are fed to Canada (CTV, etc.) can either be 1080i 2:3 pulldown or 1080i repeat frame. If they feed from a file source, it is repeat frame. If they feed from a tape source, it is 2:3 pulldown. It is 1080i because it is for OTA.

Lately they have mostly been feeding from files. Programs include shows like Supergirl, Flash, Arrow, Big Bang Theory, Lucifer.

Oh, there are no 1080p feeds via my satellite captures. :rolleyes:

[jdobbs]

Must be DirecTV or Dish, since 1080p isn't allowed for ATSC compliant transmissions. All 1080 cable channel sources (AMC, TNT, etc.) that have scripted dramas will be 1080i 2:3 pulldown.

Here is some tidbit info. Warner Bros. programs that are fed to Canada (CTV, etc.) can either be 1080i 2:3 pulldown or 1080i repeat frame. If they feed from a file source, it is repeat frame. If they feed from a tape source, it is 2:3 pulldown. It is 1080i because it is for OTA.

Lately they have mostly been feeding from files. Programs include shows like Supergirl, Flash, Arrow, Big Bang Theory, Lucifer.

Oh, there are no 1080p feeds via my satellite captures. :rolleyes:The 1080i sources that have the repeated frame usually aren't actually 1080i. They are progressive (meaning there is no temporal difference between the two fields). So you have a 1080p source at 23.976 -- with a repeated frame thrown in to make it 29.97 that is just flagged as 1080i to make it compliant with ATSC transmission standards. That's a good thing -- because you can recover the original film source easily as progressive. It can also be true with those using pulldown flags.

Oh, there are no 1080p feeds via my satellite captures.Must be component capture, eh?

[jdobbs]

Thanx. Will try it tonight.

//LDSee if it fixes the playback problem on your old Sony player as well... I'm hoping it might.

[MrVideo]

The 1080i sources that have the repeated frame usually aren't actually 1080i. They are progressive (meaning there is no temporal difference between the two fields). So you have a 1080p source at 23.976 -- with a repeated frame thrown in to make it 29.97 that is just flagged as 1080i to make it compliant with ATSC transmission standards. That's a good thing -- because you can recover the original film source easily as progressive. It can also be true with those using pulldown flags.
OK, I see where you are coming from. I strictly call 1080i video as 1080i video, even if it has progressive content. And yes, recovering the 23.976 content from the repeat frame source is easy with the AVS selectevery() filter. The 2:3 pulldown has a couple of AVS filter ways in which to do that. I then get true 1080p23.976. Plays nice and smooth that way.

GDMX does the 2:3 pulldown, or repeat frame, conversion on the fly. Their sources are 1080p23.976.

Must be component capture, eh?
Nope, direct satellite IRD (PCI card & USB) controlled via TSReader to TS (Transport Stream) file, or professional satellite IRD via ASI card/TSReader to TS file. 10' and 12' dishes.

[MrVideo]

I found a minor bug with the Page/Prev/Next labels.

[...]

I think the temporary cure, in my case, is to put a bunch of spaces at the end of the text of one of the titles.

That worked. Until a permanent fix is found, I'll have to do this trick if I have more than one page and short title text.

[jdobbs]

OK, I see where you are coming from. I strictly call 1080i video as 1080i video, even if it has progressive content. And yes, recovering the 23.976 content from the repeat frame source is easy with the AVS selectevery() filter.Since the repeated frame might change at scene changes or cuts, I use Decimate(cycle=5) or tDecimate() depending upon the selection in the INI file.

[MrVideo]

Since the repeated frame might change at scene changes or cuts, I use Decimate(cycle=5) or tDecimate() depending upon the selection in the INI file.
Because my files are from the 1080p23.976 sub-masters, the repeat frame cadence is intact throughout the file. When I edit the file, with VideoReDo, to tighten up the commercial blacks, I remove frames in groups of 5, so that the cadence is kept. That way the selectevery() won't have an issue.

Using selectevery() with BDRB is possible, only if the user knows which frame is the first of the two repeat frames, and there is an INI setting for it. Not worth doing though.

The repeated frame should never change at scene changes. All scripted shows are produced/edited at 23.976. So, when converted to 2:3 pulldown or repeat frame, the cadence of either is kept throughout the telecined file. Only when commercials are added during play out can the cadence be lost. That is where editing programs like VideoReDo can allow you to edit telecined sources and get back the repeat frame cadence. But, my files do not have commercials, so that isn't a problem.

[LowDead]

See if it fixes the playback problem on your old Sony player as well... I'm hoping it might.

The clpi works in bdedit now and seems to be ok. No luck with the old sony though. I can't think of anything else to check. Would it be possible for you, if you have the time, to do a quick comparison with either multiAVCHD (with avchd output) or AVCHDCoder. The output from them both work in the old sony.

//LD

[Lathe]

I have updated the first post of this thread with a link to the latest version of BD-RB (v0.50.21). Changes for this release:- Corrected an error in which 3D sources in
SBS/OU output mode were not forced to be
encoded when the original was small enough
to fit on the target.
- Added a new hidden option. IVTC_1080p will
force inverse telecining on 1080p sources
that have a framerate of 29.97fps. Care
should be taken -- as this should only be
set when you know the source was originally
filmed at 24fps (23.976).
- Added a new filter prefix. "L:nnnnn". It
applies the specified filter only when the
M2TS being encoded is found in the playlist
specified by "nnnnn". As an example, a line
containing "l:00001Tweak(bright=10.0)" would
increase the brightness only on video that
is a part of playlist 00001.
- Corrected a "CreateQuickMenu(), 0000, 4020"
error that can occur when using a complex
font for a Quick Menu or Import.
- Fixed an issue in which reencoding audio to
ALTERNATE/Auto-AC3 from an Auto-AC3 (VBR)
source could result in blank output.
- Fixed an issue in which a 3D source feature
that is flagged for the base view to be the
right picture (atypical) was not carrying
over when outputting to a non-ALTERNATE
movie-only structure. The result would be
an apparent swapped left/right picture.
- Corrected a problem in which .SRT files
that had the same name (minus extension) as
an imported file source were not being
imported on containers other than the .MKV
format.
- Fixed an issue in which selecting output to
3D/SBS for movie-only encoding could have
and unexpected impact on a full 3D backup.
- Corrected a problem in which variable frame
rate sources could, under certain conditions
result in out-of-sync audio during the file
import process.
- Fixed an issue in which the HDMV header on
CLPI files of AVCHD backups could be created
incorrectly.
- Updated the included version of X265.EXE to
the latest release (v2.2.17).
- Updated the included version of X265-64.EXE
to the latest release (v2.2.17).
- Other minor corrections and cosmetic fixes.

WOW! You were seriously busy JD! Thank you!

BTW, are there any updates with x264? I didn't notice any new versions in this build mentioned. Do you know if there are still any speed issues using it with LAVF? Is BDRB still using x264L-64.exe for LAVF?

[Sharc]

- Fixed an issue in which selecting output to
3D/SBS for movie-only encoding could have
and unexpected impact on a full 3D backup.

This means, when selecting "Full backup" mode the setting "Enable 3D SBS/OU for Movie-only output" is now just ignored, right?

[colinhunt]

I have updated the first post of this thread with a link to the latest version of BD-RB (v0.50.21).
Aww yeah - thank you! I'll start running tests immediately. Y'know, this might merit another donation from yours truly...

[Yordan5]

Interesting results. I shrank Jack Reacher Never Go Back (movie only) from approx. 28Gb to 14.5Gb twice for testing purposes. Using BD-RB Default settings (Auto Quality: Good (Very Fast), ABR) took approx 1h 50min and the resulting copy according to BDInfo was with 16mb average bitrate. Second job was with High Quality (Default), ABR and took 6hrs with the copy having average bitrate of 10Mb. I cannot see obvious difference in visual quality but thought that the Higher Quality setting should've produced higher bitrates copy. Might as well stick with the faster settings then.

[jdobbs]

The clpi works in bdedit now and seems to be ok. No luck with the old sony though. I can't think of anything else to check. Would it be possible for you, if you have the time, to do a quick comparison with either multiAVCHD (with avchd output) or AVCHDCoder. The output from them both work in the old sony.

//LDI know they aren't the same. I found a couple of inconsistencies in multiAVCHD that I corrected based upon the specification.

What I will do, though, is look for other things (like the header issue you reported).

[jdobbs]

WOW! You were seriously busy JD! Thank you!

BTW, are there any updates with x264? I didn't notice any new versions in this build mentioned. Do you know if there are still any speed issues using it with LAVF? Is BDRB still using x264L-64.exe for LAVF?That's a tough one for me -- as the speed issue seems to come and go at will when I'm testing it. For right now, yes, it is still using X264L-64.exe for LAVF.

[jdobbs]

This means, when selecting "Full backup" mode the setting "Enable 3D SBS/OU for Movie-only output" is now just ignored, right?Yes. So you can leave it checked and it shouldn't affect full backups anymore. I haven't given up on your request -- but I wanted to correct the obvious error for this release.

[jdobbs]

Interesting results. I shrank Jack Reacher Never Go Back (movie only) from approx. 28Gb to 14.5Gb twice for testing purposes. Using BD-RB Default settings (Auto Quality: Good (Very Fast), ABR) took approx 1h 50min and the resulting copy according to BDInfo was with 16mb average bitrate. Second job was with High Quality (Default), ABR and took 6hrs with the copy having average bitrate of 10Mb. I cannot see obvious difference in visual quality but thought that the Higher Quality setting should've produced higher bitrates copy. Might as well stick with the faster settings then.Actually it would be the opposite. Using high quality settings uses more "bells and whistles" (at the expense of encoding speed) that can get the same quality with a lesser size (lower bitrate). This was a CRF encode, I assume?

[Sharc]

I am still getting the error when trying to import HUFFYUV compressed .avi sources. I assume that the codec has not yet been added to the list (http://forum.doom9.org/showpost.php?p=1792828&postcount=25467) in v0.50.21, or do I miss something?

[LowDead]

I know they aren't the same. I found a couple of inconsistencies in multiAVCHD that I corrected based upon the specification.

What I will do, though, is look for other things (like the header issue you reported).

Thank you for looking into it. I also tested an avchd output made from tsMuxeR just to see and it too worked on both the old Sony and the PS3.

//LD

[jdobbs]

I am still getting the error when trying to import HUFFYUV compressed .avi sources. I assume that the codec has not yet been added to the list (http://forum.doom9.org/showpost.php?p=1792828&postcount=25467) in v0.50.21, or do I miss something?No. Sorry it hasn't. Just for testing, can you provide me with a short clip to use for importing?

[jdobbs]

Thank you for looking into it. I also tested an avchd output made from tsMuxeR just to see and it too worked on both the old Sony and the PS3.

//LDThe problem with TSMUXER is that it doesn't provide a capability to include a menu or to have multiple selectable items.

[LowDead]

The problem with TSMUXER is that it doesn't provide a capability to include a menu or to have multiple selectable items.

Yes, it was only a quick test.

//LD

[jdobbs]

Yes, it was only a quick test.

//LDTo be honest, at this point I think the problem is with the player... but I'm open to being proven wrong -- so I'll do some investigation.

I really wish I hadn't given that old Sony player away. I could sure use if for testing...

[MrVideo]

I really wish I hadn't given that old Sony player away. I could sure use if for testing...
I have a Sony BDP-S350 that you can have for the cost of shipping. I even have the original box. I will never use it again.

[Sharc]

No. Sorry it hasn't. Just for testing, can you provide me with a short clip to use for importing?
Here a .zip (http://www.mediafire.com/file/2hgacw58h1rc9n2/Captures.zip) with 3 samples of lossless captures in .avi container: HFYU (Huffyuv), ULY2 (from the UTVideo suite) and LAGS (Lagarith).
My preference for importing in BD-RB would be HFYU.

[colinhunt]

jdobbs, I hate to be the bearer of bad news... but I did Hobbit 3D disc 2 (movie only to .iso) on 05021, and the L/R views are still reversed.

[jdobbs]

Here a .zip (http://www.mediafire.com/file/2hgacw58h1rc9n2/Captures.zip) with 3 samples of lossless captures in .avi container: HFYU (Huffyuv), ULY2 (from the UTVideo suite) and LAGS (Lagarith).
My preference for importing in BD-RB would be HFYU.I assume you know that they will be converted to AVC when they are imported.

[jdobbs]

jdobbs, I hate to be the bearer of bad news... but I did Hobbit 3D disc 2 (movie only to .iso) on 05021, and the L/R views are still reversed.Which Hobbit? I have Hobbit, Desolation of Smaug, 3D (bought for a bug report) -- any chance that's the one?

Are you absolutely positive they are reversed? It's not something left over from a previous attempt? I tested it pretty thoroughly.

Outline exactly what you're doing and also provide the log and INI contents -- and I'll look at it. Also make sure you mention any "tweaking" you may be doing with other tools.

[Sharc]

I assume you know that they will be converted to AVC when they are imported.
Yes (same as DivX).

Edit:
Captures to x264 AVC lossless (format profile High 4:4:4 Predictive@L3) can be imported without conversion. I tested it with x264vfw which is available from Komisar or MasterNobody.

[jdobbs]

Yes (same as DivX).

Edit:
Captures to x264 AVC lossless (format profile High 4:4:4 Predictive@L3) can be imported without conversion. I tested it with x264vfw which is available from Komisar or MasterNobody.If you want to keep the conversion lossless you can always set IMPORT_CONVERT_CRF=0 in your INI. Of course it will make the pseudo-BD structure pretty big in your IMPORT folder.

[Sharc]

If you want to keep the conversion lossless you can always set IMPORT_CONVERT_CRF=0 in your INI. Of course it will make the pseudo-BD structure pretty big in your IMPORT folder.
Good point. This will reduce the lossy conversion to the final reencoding step. The size of the intermediate import file shouldn't matter as the video clips are normally short.

[colinhunt]

Which Hobbit? I have Hobbit, Desolation of Smaug, 3D (bought for a bug report) -- any chance that's the one?
The first movie in the trilogy, An Unexpected Journey. Extended version of that, in fact.

Are you absolutely positive they are reversed?
100% certain. Burned output to disc, played on an Oppo player connected to a 3D projector. Verified reversal by viewing movie and reversing glasses to see proper depth.

It's not something left over from a previous attempt?
Nope, I've deleted all .iso files created on 05020 and earlier versions so there's no change of a mix-up.

Outline exactly what you're doing and also provide the log and INI contents -- and I'll look at it. Also make sure you mention any "tweaking" you may be doing with other tools.
1) Created an .iso image of the Hobbit disc 2 using last version of AnyDVD HD
2) Mounted .iso image in Windows 10 using its internal image mounter
3) Opened drive letter H: (i.e. the mounted .iso) on BD-RB 05021
4) Selected "Movie-Only Backup"
5) Disc has two playlists: 00100 with 16 chapters and 00960 with 1 chapter. BD-RB chose the correct one (00100) automatically
6) BD-RB tends to make undersized outputs of 3D movie-only backups when target is set to BD-25 so I used a Custom Target Size of 24300MB
7) Ran backup, burned resulting .iso on disc, tested output as described above

Note: I have checked the .iso image created in step 1 and verified views are not reversed in it. As for tweaks, I can think of nothing else besides the custom target size.

LOG
[01/24/17] BD Rebuilder v0.50.21
[20:44:15] Source: HOBBIT_EXT_PT1_D2_00100
- Input BD size: 27.62 GB
- Approximate total content: [01:23:28.378]
- Target BD size: 23.73 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), ABR
- Output folder: Q:\_ENCODES\
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[20:44:17] PHASE ONE, Encoding
- [20:44:17] Processing: VID_00006 (1 of 1)
- [20:44:17] Extracting A/V streams [VID_00006]
- [20:58:47] Reencoding video [VID_00006]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 120,081 frames
- Bitrate: 31,442 Kbs
- Using FRIMEncoder for MVC encoding
- [20:58:47] Reencoding: VID_00006, Pass 1 of 1
- [21:36:37] Video Encode complete
- [21:36:38] Processing audio tracks
- Track 4352 (eng): Keeping original audio
[21:36:38]PHASE ONE complete
[21:36:38]PHASE TWO - Rebuild Started
- [21:36:38] Rebuilding BD-3D file Structure
[21:42:24] - Encode and Rebuild complete
[21:42:24] JOB: HOBBIT_EXT_PT1_D2 finished.

INI
[Options]
VERSION=0.50.0.21
ENCODER=0
MODE=3
OUTPUT_FOLDER=Q:\_ENCODES
ENCODE_QUALITY=3
QUALITY_ULTRA=1
FRIM_SW_DECODE=0
FRIM_SW_ENCODE=0
OUTPUT_3D_ISO=1
IGNORE_3D=0
ONEPASS_ENCODING=0
AUTO_QUALITY=0
TARGET_SIZE=25300
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
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=0
AC3_REENCODE=0
AC3_640=0
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=4
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=1
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=24800
[Paths]
SOURCE_PATH=I:\
WORKING_PATH=F:\_BDRB_OUTPUT\

Note wrt to .INI: I've changed target size since running the Hobbit backup which is why the size above differs from the 24300MB I used for Hobbit. I've made no other changes to any BD-RB setting since running the Hobbit backup.

[colinhunt]

jdobbs, didn't BD-RB use to have a hidden option for setting whether it would create the SSIF directory or, alternatively, stereo .m2ts files (i.e. no SSIF directory) when making Full Disc backups of 3D titles?

I thought I'd try to make a Full Disc Backup of Hobbit disc 2 and use other tools to create an .iso image file from the STREAM + STREAM/SSIF directory structure, but the Backup does not have SSIF. Instead, .m2ts files have two video streams, and I can't seem to find that "SSIF or stereo m2ts" option anymore.

update: Played the Full Disc backup's main movie stereo .m2ts on Stereoscopic Player, and had to use player's "swap views" button to correct for reversed L/R views. I'll burn the data on disc to verify on Oppo + 3D projector combo.

[Sharc]

jdobbs, didn't BD-RB use to have a hidden option for setting whether it would create the SSIF directory or, alternatively, stereo .m2ts files (i.e. no SSIF directory) when making Full Disc backups of 3D titles?

I thought I'd try to make a Full Disc Backup of Hobbit disc 2 and use other tools to create an .iso image file from the STREAM + STREAM/SSIF directory structure, but the Backup does not have SSIF. Instead, .m2ts files have two video streams, and I can't seem to find that "SSIF or stereo m2ts" option anymore.
Colin:
From the HIDDENOPTS.TXT
OUTPUT_3D_ISO=n n = 0/1 - 0=Off (default) - if set to "1", movie-only output is to an ISO rather than a folder

and from the CHANGES.TXT
April 7th, 2014 - v0.47.04
- Implemented 3D Full Backup Mode. Note that
BD-RB converts 3D method so that the SSIF
folder is no longer required -- the method
is 100% compliant with the BD standard.
(v0.47.03)
- Due to the changes in the way 3D is handled,
BD-RB no longer outputs to ISO by default on
movie-only 3D encodes. It can be enabled by
using the OUTPUT_3D_ISO hidden option. Note:
This option only applies to movie-only 3D
encodes. (v0.47.03)

[colinhunt]

Colin:
From the HIDDENOPTS.TXT
OUTPUT_3D_ISO=n n = 0/1 - 0=Off (default) - if set to "1", movie-only output is to an ISO rather than a folder

and from the CHANGES.TXT
That's not the hidden option I was asking about.

[Sharc]

That's not the hidden option I was asking about.
Output to ISO means the ISO will contain the SSIF structure. It works for movie-only though, not for full backups IIRC.

[colinhunt]

Output to ISO means the ISO will contain the SSIF structure. It works for movie-only though, not for full backups IIRC.
Yes, I know. But unless my memory totally fails, I'm fairly certain that at some in the past it was possible to make Full Disc backups where BD-RB output Blu-ray directory structure (i.e. not .iso) that contained the SSIF directory. And also that it was possible to use a hidden option to change that so that instead of outputting SSIF, BD-RB created "in-mux" m2ts files that had both views in them as two separate video streams.

edit: Found it in Changes.txt:

- Made in-mux (single M2TS) 3D multiplexing
mode the default on full-backup 3D. This
can be changed back with the hidden option
FORCE_INMUX_3D=0.

[colinhunt]

jdobbs, I'm happy to report that the L/R views are not reversed on Hobbit's Full Disc backup containing in-muxed stereo .m2ts files. I was actually surprised that my ancient Oppo Blu-ray player had no issues with in-muxed stereo files. I know they are supposedly 100% compliant with the BD spec but I've always suspected it's one of those features that is not mandatory and hence not supported by all manufacturers.

Despite this success I'd still prefer to be able to make movie-only .iso backups that don't have their views reversed. For example, this Hobbit disc has several GBs worth of unnecessary data on it that only serves to lower the bitrate of the main feature when present on the same BD-25 backup.

[jdobbs]

I know they are supposedly 100% compliant with the BD spec but I've always suspected it's one of those features that is not mandatory and hence not supported by all manufacturers.In-mux is not "supposedly" anything. I know what I'm doing, and when I say it is 100% compliant -- it is 100% compliant. Support is required by the spec -- so if there is a 3D player out there that doesn't support it THE PLAYER IS NOT COMPLIANT. It is used on many commercial discs. Frankly I think the SSIF format is ridiculous (with its faux appearance of two files that really only exists due to exotic use of sector pointers) and can see no good reason why it is used. I think it's just there to make copying difficult.

Can you send me the MPLS of the playlist that is reversed?

[colinhunt]

In-mux is not "supposedly" anything. I know what I'm doing, and when I say it is 100% compliant -- it is 100% compliant. Support is required by the spec -- so if there is a 3D player out there that doesn't support it THE PLAYER IS NOT COMPLIANT.
Apologies, I did not mean it like that. I was referring to the fact that the spec contains also optional, non-mandatory features that are not supported by all manufacturers. I have no idea whether in-mux stereo is a mandatory or an optional feature.

Frankly I think the SSIF format is ridiculous
Agreed.

Can you send me the MPLS of the playlist that is reversed?
Sure thing!

[jdobbs]

Apologies, I did not mean it like that. I was referring to the fact that the spec contains also optional, non-mandatory features that are not supported by all manufacturers. I have no idea whether in-mux stereo is a mandatory or an optional feature.


Agreed.


Sure thing!I looked at the MPLS. It is in the standard format in which the left view is in the main stream (AVC) portion of the video. So it shouldn't need to be swapped. I'll look at it and make sure I didn't screw up the standard configuration by trying to account for the unusual.

[colinhunt]

I looked at the MPLS. It is in the standard format in which the left view is in the main stream (AVC) portion of the video. So it shouldn't need to be swapped. I'll look at it and make sure I didn't screw up the standard configuration by trying to account for the unusual.
Wait. I sent you the playlist from the movie-only backup that had its views reversed. Did you want the original's playlist instead? /confused

[jdobbs]

Wait. I sent you the playlist from the movie-only backup that had its views reversed. Did you want the original's playlist instead? /confusedYes. Also, can you send me the .meta file from the working folder?

[colinhunt]

Yes. Also, can you send me the .meta file from the working folder?
I've run a few backups since the Hobbit so it's probably gone. I'll run Hobbit again using same settings.

[jdobbs]

I've run a few backups since the Hobbit so it's probably gone. I'll run Hobbit again using same settings.Wrong meta file. I need the one entitled MUX_MOVIE_ONLY.meta. I should have been clearer.

[jdobbs]

@colinhunt

I just did several tests with 3D sources and output to ISO. It worked correctly every time. I'll look at it some more -- but it sure looks like it's working from here.

[Edit] Never mind. I was able to repeat it. I traced it and I see how it happens now. I'll get a fix in for the next release.

[colinhunt]

@colinhunt
[Edit] Never mind. I was able to repeat it. I traced it and I see how it happens now. I'll get a fix in for the next release.
Fantastic, thank you!

[Lathe]

Aww yeah - thank you! I'll start running tests immediately. Y'know, this might merit another donation from yours truly...

Whadaya mean 'Might'...??? :devil:

Pay the man... http://lathe-of-heaven.com/club.gif

[colinhunt]

Whadaya mean 'Might'...??? :devil:
I've donated several times over the years. jdobbs even told me once not to donate again, but I'm guessing he was seriously distracted at the moment :D

Regardless, I was planning on donating when the movie-only 3D backup bug was squashed.

[Lathe]

I've donated several times over the years. jdobbs even told me once not to donate again, but I'm guessing he was seriously distracted at the moment :D

Regardless, I was planning on donating when the movie-only 3D backup bug was squashed.

Good man! http://lathe-of-heaven.com/yes.gif

Yes, I actually do remember that...

[jdobbs]

I have updated the first post of this thread with a link to the latest version of BD-RB (v0.50.22). Changes for this release:- Added three more supported CODECs to the
import capability (HFYU, LAGS, and ULY2).
Automatic conversion to AVC will occur
during import.
- Made changes to the way VFR is handled
on import. Now it is converted, during
import, to CFR. Avoids annoying desync,
and makes handling much cleaner.
- Added new hidden option. IMPORT_VFR_FILM
(see HIDDENOPTS.TXT) allows you to choose
between importing VFR sources to FILM or
VIDEO (23.976/29.97 fps) rates.
- Added new hidden option. IMPORT_VFR_SCAN
(see HIDDENOPTS.TXT). Sometime MediaInfo
does not catch a VFR source. This option
tells BD-RB to perform a complete scan of
all frame timecodes in a source file to
look for VFR. Especially useful when you
can't get a file's audio to sync during
import because VFR isn't detected. It can
add a couple minutes to import time.
- Corrected an issue in which importing to
an existing import folder could result in
previous PSEUDO settings remaining even if
they no longer apply.
- Fixed an issue that remained in v0.50.21
in which a 3D source feature that is
flagged for the base view to be the right
picture was not carrying over when
outputting to a non-ALTERNATE movie-only
structure. The result would be an apparent
swapped left/right picture.
- Updated the included version of mkvextract
and mkvmerge to v9.7.1.
- Other minor corrections and cosmetic fixes.

[colinhunt]

I have updated the first post of this thread with a link to the latest version of BD-RB (v0.50.22).
jdobbs is on fire! Happy dance! Thank you once again!

[Sharc]

@jdobbs
BD-RB 0.50.22. Trying to import any of the newly added 3 lossless formats (thanks!) throws the error:
[20:17:25] Importing: HFYU
- [20:17:27] Importing video file: (1 of 1)
- Preparing AVI for processing...
- Collecting audio/video streams from source...
- Converting VFR source to CFR format...
[20:17:29]ERROR: Failed VFR conversion. Aborted
The input is CFR 25fps (according to the capture settings and in line with what MediaInfo reports) so I wonder why DB-RB wants to convert VFR to CFR.
I assume you still have my 3 testclips. Did you try with these? Do I have to force a full timecode scan?

[jdobbs]

@jdobbs
BD-RB 0.50.22. Trying to import any of the newly added 3 lossless formats (thanks!) throws the error:
[20:17:25] Importing: HFYU
- [20:17:27] Importing video file: (1 of 1)
- Preparing AVI for processing...
- Collecting audio/video streams from source...
- Converting VFR source to CFR format...
[20:17:29]ERROR: Failed VFR conversion. Aborted
The input is CFR 25fps (according to the capture settings and in line with what MediaInfo reports) so I wonder why DB-RB wants to convert VFR to CFR.
I assume you still have my 3 testclips. Did you try with these? Do I have to force a full timecode scan?Wierd. Run MediaInfo and see if it says the source is Variable Frame Rate. I'll import the examples you gave me and see what happens.


[Edit] DAMN!!! I had added a hidden option called IMPORT_VFR_FORCE for testing -- and I mistakenly defaulted it to ON. Damn. Damn. Damn. I'll fix it and post a new release in a little while. In the meantime you can set IMPORT_VFR_FORCE=0 in your INI file.

[Sharc]

[Edit] DAMN!!! I had added a hidden option called IMPORT_VFR_FORCE for testing -- and I mistakenly defaulted it to ON. Damn. Damn. Damn. I'll fix it and post a new release in a little while. In the meantime you can set IMPORT_VFR_FORCE=0 in your INI file.
No worry, no rush! Glad you found it :)

[jdobbs]

I have updated the first post of this thread with a link to the latest release of BD-RB (v0.50.23). Changes for this release:January 27th, 2016 - v0.50.23
- Added three more supported CODECs to the
import capability (HFYU, LAGS, and ULY2).
Automatic conversion to AVC will occur
during import.
- Made changes to the way VFR is handled
on import. Now it is converted, during
import, to CFR. Avoids annoying desync,
and makes handling much cleaner.
- Added new hidden option. IMPORT_VFR_FILM
(see HIDDENOPTS.TXT) allows you to choose
between importing VFR sources to FILM or
VIDEO (23.976/29.97 fps) rates.
- Added new hidden option. IMPORT_VFR_SCAN
(see HIDDENOPTS.TXT). Sometime MediaInfo
does not catch a VFR source. This option
tells BD-RB to perform a complete scan of
all frame timecodes in a source file to
look for VFR. Especially useful when you
can't get a file's audio to sync during
import because VFR isn't detected. It can
add a couple minutes to import time.
- Corrected an issue in which importing to
an existing import folder could result in
previous PSEUDO settings remaining even if
they no longer apply.
- Fixed an issue that remained in v0.50.21
in which a 3D source feature that is
flagged for the base view to be the right
picture was not carrying over when
outputting to a non-ALTERNATE movie-only
structure. The result would be an apparent
swapped left/right picture.
- Corrected an error introduced in v0.50.22
that forced VFR to CFR conversion during
import.
- Updated the included version of mkvextract
and mkvmerge to v9.7.1.
- Other minor corrections and cosmetic fixes. If you attempt to download v0.50.22 after this post -- it will also have this update included.

[jdobbs]

No worry, no rush! Glad you found it :)I had to fix it fast. Otherwise every IMPORT would result in reencoding to a huge pseudo-BD folder.

[colinhunt]

Hobbit 3D disc 2 movie-only to .ISO backup job finished, and happy to report L/R views display correctly! Thank you jdobbs; donation made.

[Sharc]

I had to fix it fast. Otherwise every IMPORT would result in reencoding to a huge pseudo-BD folder.
Still no luck. This time I am getting for all 3 codecs the error
[00:04:04] Importing: ULY2
- [00:04:06] Importing video file: (1 of 1)
- Preparing AVI for processing...
- Scanning for Variable Frame Rate...
- Collecting audio/video streams from source...
- Converting codec to compatible format...
[00:04:09]ERROR: Failed codec conversion. Aborted.

Edit:
Sorry, the problem was here: A typo in the .INI. :o
Never mind.

[Sharc]

I noticed that interlaced HFUY sources 720x576i25 get AVC converted as progressive (profile: baseline Level 3.0, scantype: progressive) during import.

MediaInfo reports the HFYU (.avi) source as interlaced. Stream inspection confirms that it is interlaced video, TFF, as expected.
But after importing, MediaInfo and DGIndexNV report the converted .m2ts as progressive. Field separation however indicates that the video is in fact still true interlaced (50 temporal fields per second).

Is this interlaced/progressive ambiguity ok, or should the import process include --tff for the conversion of interlaced (HFUY) sources? :confused:

[jdobbs]

I noticed that interlaced HFUY sources 720x576i25 get AVC converted as progressive (profile: baseline Level 3.0, scantype: progressive) during import.

MediaInfo reports the HFYU (.avi) source as interlaced. Stream inspection confirms that it is interlaced video, TFF, as expected.
But after importing, MediaInfo and DGIndexNV report the converted .m2ts as progressive. Field separation however indicates that the video is in fact still true interlaced (50 temporal fields per second).

Is this interlaced/progressive ambiguity ok, or should the import process include --tff for the conversion of interlaced (HFUY) sources? :confused:I simply use DirectshowSource() in an AVS and pass the video to X264. I would have thought that the frame format would be recognized correctly. I should have known better than to assume anything. I'll add some code to check for interlacing (bff/tff) and pass the parameter to X264..

[jdobbs]

I noticed that interlaced HFUY sources 720x576i25 get AVC converted as progressive (profile: baseline Level 3.0, scantype: progressive) during import.

MediaInfo reports the HFYU (.avi) source as interlaced. Stream inspection confirms that it is interlaced video, TFF, as expected.
But after importing, MediaInfo and DGIndexNV report the converted .m2ts as progressive. Field separation however indicates that the video is in fact still true interlaced (50 temporal fields per second).

Is this interlaced/progressive ambiguity ok, or should the import process include --tff for the conversion of interlaced (HFUY) sources? :confused:Interesting. During import all non-MKV files are remuxed into an MKV for consistency (MediaInfo reports different information, even for the same CODECs, depending upon the container). If I run MediaInfo against the AVI, it tells me the scan type is interlaced -- but if I run it against the MKV it doesn't. I guess I'm going to have to manually set the field order in MKVMERGE. That's kinda' disappointing -- you'd think something as obvious as progressive/interlaced formatting would be detected automatically.

[Edit] It gets even worse. The version of MediaInfo included with BD-RB doesn't even report the scan type as interlaced on the HFYU.avi file you sent me. And I've avoided updating it because the newer one seems to be worse at recognizing variable frame rates. And, even if I used the new one -- it doesn't tell you the field order. A wrong field order would look much worse than combining the fields and playing it as progressive.

[Sharc]

Interesting. During import all non-MKV files are remuxed into an MKV for consistency (MediaInfo reports different information, even for the same CODECs, depending upon the container). If I run MediaInfo against the AVI, it tells me the scan type is interlaced -- but if I run it against the MKV it doesn't. I guess I'm going to have to manually set the field order in MKVMERGE. That's kinda' disappointing -- you'd think something as obvious as progressive/interlaced formatting would be detected automatically.

[Edit] It gets even worse. The version of MediaInfo included with BD-RB doesn't even report the scan type as interlaced on the HFYU.avi file you sent me. And I've avoided updating it because the newer one seems to be worse at recognizing variable frame rates. And, even if I used the new one -- it doesn't tell you the field order. A wrong field order would look much worse than combining the fields and playing it as progressive.
Ufff....I didn't imagine that adding these codecs for importing the .avi would cause such headaches. Sorry for the trouble. You are right MediaInfo does not tell the field order even when it detects interlaced, and maybe the info is not even available from the .avi (or is codec/mux dependent). Pretty inconsistent and confusing, I think.
It seems now that manual analysis of the source is required and x264 must then be manually forced to encode --tff or --bff. That's what I have been doing until now, using BD-RB at the end for quick-authoring a number of pre-encoded compliant .m2ts. So BD-RB still holds its strong place in this scenario :)

[jdobbs]

Ufff....I didn't imagine that adding these codecs for importing the .avi would cause such headaches. Sorry for the trouble. You are right MediaInfo does not tell the field order even when it detects interlaced, and maybe the info is not even available from the .avi (or is codec/mux dependent). Pretty inconsistent and confusing, I think.
It seems now that manual analysis of the source is required and x264 must then be manually forced to encode --tff or --bff. That's what I have been doing until now, using BD-RB at the end for quick-authoring a number of pre-encoded compliant .m2ts. So BD-RB still holds its strong place in this scenario :)There's always a way. I'll probably have to analyze the stream myself. Look for something in the next release.

[Sharc]

There's always a way. I'll probably have to analyze the stream myself. Look for something in the next release.
Btw., capturing the tapes with x264 in lossless mode with field order specification seems to keep the interlace and field order information correctly and consistently during import. So I could capture the tapes again, but unfortunately the tapes have aged (like me) and deteriorated (like me) since the original capture in HFYU format about 8 years ago.

Now I am curious and patiently waiting for the next release of BD-RB :cool:

[MrVideo]

You have issues with tapes that are only 8 years old? I have VHS/S-VHS/Umatic/DVCAM tapes that are many years (decades even) older than that and I do not have issues with them.

[Lathe]

You have issues with tapes that are only 8 years old? I have VHS/S-VHS/Umatic/DVCAM tapes that are many years (decades even) older than that and I do not have issues with them.

Hmmmm... Can anyone say, 'BETA'...! :D

[Lathe]

...but unfortunately the tapes have aged (like me) and deteriorated (like me)...


Geez JD, do you think you could throw a little something into the next build to help ol' Sharc...?

He's decomposing before our eyes, poor fellow... http://lathe-of-heaven.com/no.gif

[MrVideo]

Hmmmm... Can anyone say, 'BETA'...! :D
Beta, VHS, whatever. It should not be giving you issues.

[Sharc]

Geez JD, do you think you could throw a little something into the next build to help ol' Sharc...?

He's decomposing before our eyes, poor fellow... http://lathe-of-heaven.com/no.gif
Nothing to really worry about, Lathe. It's in no respect as dramatic as what we see from your selfie here (http://forum.doom9.org/showpost.php?p=1791038&postcount=25431) :eek:

[Sharc]

You have issues with tapes that are only 8 years old? I have VHS/S-VHS/Umatic/DVCAM tapes that are many years (decades even) older than that and I do not have issues with them.
The tapes are actually much older, about 25....30 years old, but I captured (digitized) these lossless only about 8 years ago. For few of the tapes I noticed visible deterioration recently.
I posted a sample here (http://forum.doom9.org/showthread.php?p=1794052#post1794052)of a VHS tape which was still reasonably clean some years ago.

[jdobbs]

Ufff....I didn't imagine that adding these codecs for importing the .avi would cause such headaches. Sorry for the trouble. You are right MediaInfo does not tell the field order even when it detects interlaced, and maybe the info is not even available from the .avi (or is codec/mux dependent). Pretty inconsistent and confusing, I think.
It seems now that manual analysis of the source is required and x264 must then be manually forced to encode --tff or --bff. That's what I have been doing until now, using BD-RB at the end for quick-authoring a number of pre-encoded compliant .m2ts. So BD-RB still holds its strong place in this scenario :)Here's how I'm doing it. If the source is 25fps or 29.97fps, and mediainfo doesn't specifically find it to be progressive -- I will assume it is interlaced. In my testing it seems to detect and specify "Progressive" 100% correctly. Since TFF is much more common than BFF (except maybe in DV) I will make that the default. But I'll add a hidden option that can override that. It's pretty obvious when the field order is backwards -- so that will be easy to detect and correct manually.

[jdobbs]

The tapes are actually much older, about 25....30 years old, but I captured (digitized) these lossless only about 8 years ago. For few of the tapes I noticed visible deterioration recently.
I posted a sample here (http://forum.doom9.org/showthread.php?p=1794052#post1794052)of a VHS tape which was still reasonably clean some years ago.I think all my very old tapes show degradation. But since it happens gradually, you don't really notice it and you just assume it always looked that way. But when I look at an old digital capture from the same tape I can easily see it.

[Sharc]

Here's how I'm doing it. If the source is 25fps or 29.97fps, and mediainfo doesn't specifically find it to be progressive -- I will assume it is interlaced. In my testing it seems to detect and specify "Progressive" 100% correctly. Since TFF is much more common than BFF (except maybe in DV) I will make that the default. But I'll add a hidden option that can override that. It's pretty obvious when the field order is backwards -- so that will be easy to detect and correct manually.
I think this is a good strategy.

[datman]

I'm guessing this is a bug but its such an obscure use for BDRB it might be unfixable.

I posted awhile back how I was capturing video either from the DVR or the computer. The OEM software quality was lost if I processed and burned down to a BD-5 disc. I figured out that I could process it to a BD-25 size within the software then use BDRB to encode down to a BD-5 disc. Worked well but a lot of processing time from both programs.

So I tried to side step it by importing the capture TS file and it appeared to work. When I tried this prior I got nothing but coasters and it appeared that the AAC audio from the capture, which was unchanged would cause the discs not to play.

This time I unchecked both the "do not convert DTS to AC3 and do not encode AC3" This time the audio was converted to multi-ch AC3 and it plays in my BD player. The two different captures I did both sound like it's playing at 5X speed.

I tried tsMuxerGUI and it seems the AAC audio is my biggest issue. If I process it in Power Director I can convert it to DD.

[Blurayhd]

Hi guys, hi jdobbs, I have a question, lets say I want to pass to bd25 in Only movie mode but I wish to keep the Splash menu (that is calling?), You know, when you play the movie and you want to change some language or subtitles there´s some way to push the control so the Spalsh java menu appears? I know you can set all this with changing subtitles and audios but I so wish to know
Thank you for your time!!

[MrVideo]

The tapes are actually much older, about 25....30 years old
I've got a bunch of 1/4" reel-to-reel tapes that are 40-46 years old. Not one of which had issues when I played them back for capturing. And yes, the Sony reel-to-reel deck is also functioning after all these years. Storage conditions were not ideal either.

[Lathe]

Nothing to really worry about, Lathe. It's in no respect as dramatic as what we see from your selfie here (http://forum.doom9.org/showpost.php?p=1791038&postcount=25431) :eek:

I swear... you try to show a little concern and this is what you get... :rolleyes:

[Lathe]

I've got a bunch of 1/4" reel-to-reel tapes that are 40-46 years old. Not one of which had issues when I played them back for capturing. And yes, the Sony reel-to-reel deck is also functioning after all these years. Storage conditions were not ideal either.

Reel-to-Reel...???! Holy Smokes! What's next, you gonna break out your Edison wire spools...?

How frigg'n OLD are you, for God's sake!? :eek:

(this almost reminds me of the old Monty Python sketch, 'Well, when I was young, we had to etch our own recordings in granite...')

[MrVideo]

(this almost reminds me of the old Monty Python sketch, 'Well, when I was young, we had to etch our own recordings in granite...')
Doesn't go back far enough. :D

[thekiller]

Hello,
How to have an HEVC + AC3 profile instead of AAC in the Alternate Output profile?
Thank you

[jdobbs]

Hello,
How to have an HEVC + AC3 profile instead of AAC in the Alternate Output profile?
Thank youJust add a new profile to the ALTERNATE.TXT file in the MISC folder. At the top of the file you'll see the settings that can be used. Here is an example of an HEVC profile with AC3 that could be added to the end of the file (assuming it hasn't been altered):[00039]
caption=MKV Container, HEVC 1920x1080, 448Kbs DD5.1
vEncoder=1
vBitrate=2000
vKeyint=Auto
aBitrate=448
aType=0
vFormat=5
cType=1

[CV91913]

I obviously have some setting screwed up somewhere as every DVD import to Alternate MP4 output I do has problems with "jumpy" video anytime there is action. I have never gotten a DVD conversion to work properly.

The psudo BD structure in the Import directory plays just fine. It is only the resulting MP4 that is jumpy.

Here are my logs and Alternate output settings.

[23:07:28] Importing DVD: SNOWDEN
- Processing DVD title [1 of 1 ]
- Collecting audio/video/subtitle streams...
- Converting subtitles to BD format...
- Multiplexing audio/video/subtitles...
- Creating Quick-Play Menu...
[23:13:38] DVD import completed successfully.
----------------------
[02/03/17] BD Rebuilder v0.50.20
[23:17:53] Source: SNOWDEN_00001
- Input BD size: 5.46 GB
- Approximate total content: [02:14:49.581]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: DVD to MP4, No Resize, Stereo-AAC
- Quality: Good (Very Fast)
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[23:17:53] PHASE ONE, Encoding
- [23:17:53] Processing: VID_00001 (1 of 1)
- [23:17:53] Extracting A/V streams [VID_00001]
- [23:21:14] Reencoding video [VID_00001]
- Source Video: MPEG-2, 720x480
- Rate/Length: 29.970fps, 242,445 frames
- Bitrate: 3,288 Kbs
- [23:21:14] Reencoding: VID_00001, Pass 1 of 2
- [23:52:47] Reencoding: VID_00001, Pass 2 of 2
- [00:23:54] Video Encode complete
- [00:23:54] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AAC...
[00:30:26]PHASE ONE complete
[00:30:26]PHASE TWO - Rebuild Started
- [00:30:26] Building ALTERNATE OUTPUT Structure
[00:35:41] - Encode and Rebuild complete
- WORKFILES folder removed.
[00:35:41] JOB: SNOWDEN finished.

[Status]
LABEL=SNOWDEN
VERSION=v0.50.20
SOURCE_SIZE=5861591040
SOURCE_VIDEO_SIZE=5861591040
TARGET_SIZE=24641536000
REDUCTION=4.20389887862255
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=0
SUBS_TO_KEEP=eng;
BACKUP_MODE=1
MOVIEONLY_TYPE=42
USE_LAVF=-1
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=1
[00001]
AUDIO=1
PGS=100
MSCAN=2
SCANCOUNT=193960
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=24641536000
SPLITS=1
NSIZE=0
FLINK=0
MLINK=0

[00042]
caption=DVD to MP4, No Resize, Stereo-AAC
vBitrate=2500
aBitrate=256
aType=1
vFormat=7
cType=5

[02/04/17] Checking System Settings
- BD-Rebuilder v0.50.20
- Windows Version: 6.1 [7601]
- Working Path Free Space: 347.16GB
- AVISYNTH Version: 2.5.8.0, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[02/04/17] Systems Settings Check complete

Hope someone has some ideas.

[jdobbs]

@CV91913

Have you tried turning on "IVTC sources with 3:2 pulldown" in the SETUP dialog. I think you almost always need that on when converting from an NTSC DVD.

[Matrix789]

Hi everybody,

I demuxed a movie with eac3to, put only the video track into an mkv with mkvtoolnix and then encoded with bd rebuilder (best video quality and custom size 10240MB).
The encoding went fine but, when I made my final mkv with the encoded video track and the untouched audio, I noticed that the movie is now out of sync. The video track is in fact 5 seconds longer than the audio/original video track.

Do you know why, how to fix it and how to prevent it to happen again? I encoded only the video track because I wanted the target output size to be only focused on the video track.

Thank you

EDIT: I actually noticed that the video track appears to be 5 seconds longer even before the encoding. How is it even possible?

[CV91913]

@CV91913

Have you tried turning on "IVTC sources with 3:2 pulldown" in the SETUP dialog. I think you almost always need that on when converting from an NTSC DVD.
I just tried that and can see no difference. Still jumpy. Creating MP4 from Bluray works great. Just DVD's are a problem.

I have tried constant and variable bitrates and 1 pass and 2 pass. Nothing seems to fix it. Any other suggestions?

[jdobbs]

I just tried that and can see no difference. Still jumpy. Creating MP4 from Bluray works great. Just DVD's are a problem.

I have tried constant and variable bitrates and 1 pass and 2 pass. Nothing seems to fix it. Any other suggestions?Is there any way you can create a snippet of the jumpy section so I can see what you mean?

[jdobbs]

Hi everybody,

I demuxed a movie with eac3to, put only the video track into an mkv with mkvtoolnix and then encoded with bd rebuilder (best video quality and custom size 10240MB).
The encoding went fine but, when I made my final mkv with the encoded video track and the untouched audio, I noticed that the movie is now out of sync. The video track is in fact 5 seconds longer than the audio/original video track.

Do you know why, how to fix it and how to prevent it to happen again? I encoded only the video track because I wanted the target output size to be only focused on the video track.

Thank you

EDIT: I actually noticed that the video track appears to be 5 seconds longer even before the encoding. How is it even possible?Sometimes the audio has a different start time than the video. You see that with intro studio symbols (not typically, but every now and again).

Why not just create a profile that leaves the audio untouched -- and let BD-RB do all the work? It automatically adjusts when the audio timestamp deviates from that of the video.

[meadrocks]

I'm having challenges with this title. I'm doing movie only, alternate output, mkv file, auto-aac, auto-gop. It is Playlist 00001. The audio is out of sync and there are no subtitles being displayed. I selected original swedish audio & english subtitles, not forced on.

Here is the setup info.
[Status]
LABEL=GIRL_WITH_THE_DRAGON_TATTOO
VERSION=v0.50.23
SOURCE_SIZE=19614609408
SOURCE_VIDEO_SIZE=19614609408
TARGET_SIZE=4686086144
REDUCTION=.238907951034127
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=0
SUBS_TO_KEEP=all
BACKUP_MODE=1
MOVIEONLY_TYPE=17
USE_LAVF=0
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=4
REBUILD_COMPLETE=1
[00001]
AUDIO=
PGS=1
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=1397394
NSIZE=0
FLINK=0
MLINK=0
[00000]
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=4684376098
SPLITS=1
AUDIO=10
NSIZE=0
FLINK=0
MLINK=0
[00017]
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=54310
SPLITS=1
AUDIO=
NSIZE=0
FLINK=0
MLINK=0
[00018]
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=258342

Here's the output from bd-rebuilder log file.

==========================
[19:58:45] BD Rebuilder v0.50.23
[19:58:45] BEGIN - BATCH SEQUENCE
==========================
-----------------------
[19:58:45] PROCESSING BATCH FILE [1]
----------------------
[02/02/17] BD Rebuilder v0.50.23
[04:21:40] Source: GIRL_WITH_THE_DRAGON_TATTOO_00001
- Input BD size: 18.27 GB
- Approximate total content: [02:33:02.214]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1920x1080, Auto-AAC, AutoGOP
- Quality: High Quality (Default)
- SHUTDOWN at completion enabled
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[04:21:41] PHASE ONE, Encoding
- [04:21:41] Processing: VID_00001 (1 of 4)
- [04:21:41] Extracting A/V streams [VID_00001]
- [05:03:47] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 240 frames
- [05:03:47] Reencoding: VID_00001, Pass 1 of 1
- [05:03:58] Video Encode complete
- [05:03:58] Processing audio tracks
- Track 4352 (swe): Reencoding audio to AAC...
- [05:22:25] Processing: VID_00000 (2 of 4)
- [05:22:25] Extracting A/V streams [VID_00000]
- [05:31:33] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 219,720 frames
- [05:31:33] Reencoding: VID_00000, Pass 1 of 1
- [10:30:15] Video Encode complete
- [10:30:15] Processing: VID_00017 (3 of 4)
- [10:30:15] Extracting A/V streams [VID_00017]
- [10:30:21] Reencoding video [VID_00017]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 96 frames
- [10:30:21] Reencoding: VID_00017, Pass 1 of 1
- [10:30:25] Video Encode complete
- [10:30:25] Processing: VID_00018 (4 of 4)
- [10:30:25] Extracting A/V streams [VID_00018]
- [10:30:29] Reencoding video [VID_00018]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 97 frames
- [10:30:29] Reencoding: VID_00018, Pass 1 of 1
- [10:30:33] Video Encode complete
[10:30:34]PHASE ONE complete
[10:30:34]PHASE TWO - Rebuild Started
- [10:30:34] Building ALTERNATE OUTPUT Structure
[10:35:18] - Encode and Rebuild complete
[10:35:18] JOB: GIRL_WITH_THE_DRAGON_TATTOO finished.
==========================
[10:35:18] END - BATCH SEQUENCE
==========================
- Computer SHUTDOWN initiated.

Thanks.

[CV91913]

Is there any way you can create a snippet of the jumpy section so I can see what you mean?
No problem. I have about 2 min that should demonstrate the problem. It is about 43mb. Where should I upload it?

[Matrix789]

Sometimes the audio has a different start time than the video. You see that with intro studio symbols (not typically, but every now and again).

Why not just create a profile that leaves the audio untouched -- and let BD-RB do all the work? It automatically adjusts when the audio timestamp deviates from that of the video.


Thank you for your reply.
The reason why I don't encode all together is because I want the video track to be the size that I set and not the whole file.
Also, I tried to encode the whole thing (leaving the dts audio untouched) but at the end of the process I couldn't hear any audio and on MediaInfo it looked like the audio track had been "touched" anyway.

Will it work I delay the audio track by 5 seconds with mkvtoolnix? And if yes, do I have to delay also the subtitles and chapters tracks or they are fine?

Thanks

EDIT: ok this is weird. I demuxed everything from the blu ray and I put it into a mkv: the movie duration is correct, 1hr 30min 40sec.
If I import the same mkv into bd rebuilder it shows that the movie length is 5 sec longer, 1hr 30min 45 sec. That's why after encoding the video track I can't put it back with the untouched audio: bd rebuilder "thinks" that the video is 5 sec longer than it actually is.
How do I fix it? I need bd rebuilder to see the correct length. Delaying or stretching the audio track didn't work.

[mparade]

Hello,

I was away from this forum for a long time...
Sorry for asking such things here, but can someone send a link/tell how the donation is working now?

After pushing "donation" I was linked to "Amazon.com eGift Cards"
page. E.g. what to write into the "to" field?

Sorry for asking such things that may have been answered here several times already.

[meadrocks]

Hello,

I was away from this forum for a long time...
Sorry for asking such things here, but can someone send a link/tell how the donation is working now?

After pushing "donation" I was linked to "Amazon.com eGift Cards"
page. E.g. what to write into the "to" field?

Sorry for asking such things that may have been answered here several times already.

Buy an Amazon Gift card & PM jdobbs the code. Don't need anything in the To field.

[gonca]

Hello,

I was away from this forum for a long time...
Sorry for asking such things here, but can someone send a link/tell how the donation is working now?

After pushing "donation" I was linked to "Amazon.com eGift Cards"
page. E.g. what to write into the "to" field?

Sorry for asking such things that may have been answered here several times already.

http://forum.doom9.org/showthread.php?p=1784130#post1784130

[jdobbs]

Buy an Amazon Gift card & PM jdobbs the code. Don't need anything in the To field.Or send it to dvd-rb@jdobbs.net

[CV91913]

Is there any way you can create a snippet of the jumpy section so I can see what you mean?
Yes, I uploaded a 8mb snippet to your dvd-rb@jdobbs.net email.

[jdobbs]

I've been doing some interesting testing recently. I've been thinking about using HEVC for my SERVIIO playback rather than AVC. I've been using X264 and X265 as the encoders with CRF encoding. I'm kinda' disappointed with the results I'm seeing in the tests. It seems that, while the same CRF value on the surface appears to save space, HEVC/X265 is actually using more space to get equivalent SSIM results. This definitely isn't what I was expecting. In fact the only time I'm seeing comparable or better results is at high CRF values that I wouldn't normally use.

Has anyone else seeing this kind of behavior? I saw a report that Netflix did some tests that disagree with what I'm seeing. In fact, they're saying X265 can compete with X264 at half the bitrate. Only at very-low bitrates, maybe?

Also -- at what value does SSIM reach a point that is generally considered "acceptable"? (I know this is really subjective and probably changes based on resolution, but I'm hoping that there's a consensus somewhere).

I think I'm going to run some tests using fixed bitrates rather than CRF and see what happens.

[Sharc]

I've been doing some interesting testing recently. I've been thinking about using HEVC for my SERVIIO playback rather than AVC. I've been using X264 and X265 as the encoders with CRF encoding. I'm kinda' disappointed with the results I'm seeing in the tests. It seems that, while the same CRF value on the surface appears to save space, HEVC/X265 is actually using more space to get equivalent SSIM results. This definitely isn't what I was expecting. In fact the only time I'm seeing comparable or better results is at high CRF values that I wouldn't normally use.

Has anyone else seeing this kind of behavior? I saw a report that Netflix did some tests that disagree with what I'm seeing. In fact, they're saying X265 can compete with X264 at half the bitrate. Only at very-low bitrates, maybe?

Also -- at what value does SSIM reach a point that is generally considered "acceptable"? (I know this is really subjective and probably changes based on resolution, but I'm hoping that there's a consensus somewhere).

I think I'm going to run some tests using fixed bitrates rather than CRF and see what happens.
I think that we have to take CRF out of the equation for comparing x264 with x264 because the CRF are not really calibrated (aligned) between the two encoders. So SSIM (or similar) and file size are probably the only objective measures for comparison (apart from subjective visual impression, and encoding speed if this matters).
There exist some threads in doom9 comparing the two encoders, and if I remember this correctly a sort of general consensus was (or still is?) that x265 shines at low bitrates (where x264 collapses), and at high resolutions (4k), but the savings in bitrate of 1:2 as a rule of thumb seems still very ambitious. It's certainly worth to follow the discussion in the relevant threads.
I haven't been doing much testing with x265.

[jdobbs]

I think that we have to take CRF out of the equation for comparing x264 with x264 because the CRF are not really calibrated (aligned) between the two encoders. So SSIM (or similar) and file size are probably the only objective measures for comparison (apart from subjective visual impression, and encoding speed if this matters).
There exist some threads in doom9 comparing the two encoders, and if I remember this correctly a sort of general consensus was (or still is?) that x265 shines at low bitrates (where x264 collapses), and at high resolutions (4k), but the savings in bitrate of 1:2 as a rule of thumb seems still very ambitious. It's certainly worth to follow the discussion in the relevant threads.
I haven't been doing much testing with x265.Yeah, I'm aware that the CRF values aren't aligned. But the surprising part is that to get the same SSIM result, the file size of the X265 encode is sometimes larger than that of X264 (especially when the SSIM value is larger than .99xxx). I never would have expected that.

[Sharc]

Yeah, I'm aware that the CRF values aren't aligned. But the surprising part is that to get the same SSIM result, the file size of the X265 encode is sometimes larger than that of X264 (especially when the SSIM value is larger than .99xxx). I never would have expected that.
Does this happen mainly for grainy/noisy sources? There have been lot of discussions about grain retention with x265.

[jdobbs]

Does this happen mainly for grainy/noisy sources? There have been lot of discussions about grain retention with x265.No. I ran encodes on over 300 different movies doing a 1% sample (SelectRangeEvery(4800,48)). They ranged in size from 720x480 to 1920x1080. It seems to be consistent across all of them.

[jdobbs]

No. I ran encodes on over 300 different movies doing a 1% sample (SelectRangeEvery(4800,48)). They ranged in size from 720x480 to 1920x1080. It seems to be consistent across all of them.I may have spoken too soon. Rather than just looking at the numbers randomly, I decided to write a program that scans through them and does calculations on the results. It's not as bad as I thought -- but a lot less impressive than I would have expected -- and nowhere near halving the output size. I'm running it again, but instead of doing the first 300 files in the database -- I'm having it randomly select the files to encode.

[gonca]

And then the big question
Is the size reduction worth the extra computing power and time to compress and then view?

[jdobbs]

And then the big question
Is the size reduction worth the extra computing power and time to compress and then view?With what I know at this point, no. I think the price of disc space is shrinking faster than any savings you'd get over time. If I were a company like Netflix that had to pay for transmission bandwidth it might be different.

We'll see what I get in this second round. It'll take most of the day to run.

[gonca]

I would say that for the same quality results you might be looking at 3x encode time to come down to 75% size
Plus the softening/blurring effect of x265
This is at 1080p though
At 4k it might be different

[Lathe]

Yep...

Long Live x264!

http://lathe-of-heaven.com/Rock On1.gif

[CraigWally]

Quick Menu question
This is the first time I've tried this, so still learning
I have imported 17 episodes (The Prisoner) into BDRB.
The Menu it creates lists episode 1-16 in a column then episode 17 on it's own in a second column. This looks rather silly.
How can I tell BDRB to even things up a bit
eg 1-9, then 10-17
or 1-6, 7-12, 13-17

TIA Wally

[jdobbs]

Quick Menu question
This is the first time I've tried this, so still learning
I have imported 17 episodes (The Prisoner) into BDRB.
The Menu it creates lists episode 1-16 in a column then episode 17 on it's own in a second column. This looks rather silly.
How can I tell BDRB to even things up a bit
eg 1-9, then 10-17
or 1-6, 7-12, 13-17

TIA WallyRight now the row count is fixed. I'll probably change that at some point. But you could add MENU_MAXITEMS=9, and it would create two pages with 9 items on the first and 8 on the second.

[CraigWally]

Right now the row count is fixed. I'll probably change that at some point. But you could add MENU_MAXITEMS=9, and it would create two pages with 9 items on the first and 8 on the second.

Thanks for quick answer

[thekiller]

Just add a new profile to the ALTERNATE.TXT file in the MISC folder. At the top of the file you'll see the settings that can be used. Here is an example of an HEVC profile with AC3 that could be added to the end of the file (assuming it hasn't been altered):[00039]
caption=MKV Container, HEVC 1920x1080, 448Kbs DD5.1
vEncoder=1
vBitrate=2000
vKeyint=Auto
aBitrate=448
aType=0
vFormat=5
cType=1

Thank you very much, by cons I have as problem on 2 movies


[02/16/17] BD Rebuilder v0.50.23
[21:44:17] Source: MAGNIFICENT_SEVEN_00356
- Input BD size: 34,11 GB
- Approximate total content: [02:53:07.752]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, HEVC 1920x1080, 448Kbs DD5.1
- Quality: Highest (Very Slow)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=448
[21:44:19] PHASE ONE, Encoding
- [21:44:19] Processing: VID_00350 (1 of 40)
- [21:44:19] Extracting A/V streams [VID_00350]
- [21:55:02] Reencoding video [VID_00350]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 2*011 frames
- Bitrate: 1*480 Kbs
- [21:55:02] Reencoding: VID_00350, Pass 1 of 2
[21:55:08] - Failed video encode, aborted



is there a solution ??

thank

[gonca]

Can you post your inspect results?

[jdobbs]

Thank you very much, by cons I have as problem on 2 movies


[02/16/17] BD Rebuilder v0.50.23
[21:44:17] Source: MAGNIFICENT_SEVEN_00356
- Input BD size: 34,11 GB
- Approximate total content: [02:53:07.752]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, HEVC 1920x1080, 448Kbs DD5.1
- Quality: Highest (Very Slow)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=448
[21:44:19] PHASE ONE, Encoding
- [21:44:19] Processing: VID_00350 (1 of 40)
- [21:44:19] Extracting A/V streams [VID_00350]
- [21:55:02] Reencoding video [VID_00350]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 2*011 frames
- Bitrate: 1*480 Kbs
- [21:55:02] Reencoding: VID_00350, Pass 1 of 2
[21:55:08] - Failed video encode, aborted



is there a solution ??

thank1. Please post the contents of your ALTERNATE.TXT file so I can see if it's entered correctly.
2. Are any other encodes working?
3. As gonca suggested, please post INSPECT results.

[colinhunt]

Looks like PS4 won't play "inmux 3D" as 3D. Anybody else tested on PS4? Just wondering if it's only on my PS4 set-up for some reason.

[jdobbs]

Looks like PS4 won't play "inmux 3D" as 3D. Anybody else tested on PS4? Just wondering if it's only on my PS4 set-up for some reason.If it doesn't -- it is in violation of the standard. But I have my doubts that is the issue.

[jdobbs]

1. Please post the contents of your ALTERNATE.TXT file so I can see if it's entered correctly.
2. Are any other encodes working?
3. As gonca suggested, please post INSPECT results.I guess it's more fun to post a report than to post information that might be required to fix it?

[Lathe]

I guess it's more fun to post a report than to post information that might be required to fix it?

C'mon guys... you get the Boss all worked up and then leave him hangin'... http://lathe-of-heaven.com/no.gif

[gonca]

4 posts in 7 years...

[jetli]

hi, how can i get a quick play disk
with each video getting a subtitle forced on?

is this possible?

thanks tony

[Avinash KN]

Hi, I am observing issues with subtitle when i try to back up my multi file BD movies. These are standard movie discs purchased from store. The video and audio has no problem. But subtitle goes out of sync after first file. I see the text for second file getting displayed for some other file after merger. This issue doesn't happen for all split file movies. But only for some of them. I am not able to differentiate between the two types of split file movies, one which works and another which wouldn't. My setting are listed below. Any help will be greatly appreciated. Let me know if any more details are needed. Thanks.

[Options]
VERSION=0.50.0.23
ENCODER=0
MODE=3
ENCODE_QUALITY=0
ONEPASS_ENCODING=2
AUTO_QUALITY=1
TARGET_SIZE=47366
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=0
AVCHD=1
REMOVE_WORKFILES=1
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=60000
QUICK_EXTRAS=0
[Paths]
SOURCE_PATH=E:\SHERLOCK\
WORKING_PATH=D:\NEW FOLDER\

Warm Regards,
Avinash K N

[Avinash KN]

Sorry. missed out some more info:

I have enabled Movie-only backup option. Alternate output is not enabled.

[Weirdo]

I think I got confirmation on something I've always wanted to ask: can the user-set settings of LAV filters (outside of BD-RB) interfere with a a backup? I completed a backup (I've deleted it) of a Blu-Ray with 1080i/25fps content and everything played in slow motion in the backup. This also happens with "Preview this item" in BD-RB.

In the LAV Video Configuration, I have Software Deinterlacing/YADIF enabled. If I disable it, the Preview plays fine in BD-RB with this Blu-Ray and I assume a new backup will also work fine.

Can BD-RB ignore the LAV user-settings or do the LAV Filters always need to be set in a specific way?

[Lathe]

...everything played in slow motion

Hmmm, so, uh..., were you maybe smok'n a little somethin...?





http://lathe-of-heaven.com/shroom.gif

[Weirdo]

Hmmm, so, uh..., were you maybe smok'n a little somethin...?
Much slower speed, if you prefer. No smoking involved and I still have the BD anyway so it's easily reproduced.

[Lathe]

Much slower speed, if you prefer. No smoking involved and I still have the BD anyway so it's easily reproduced.

:D

That really IS odd... JD or one of the other experts here will likely know why...

[Weirdo]

Just created another backup and indeed it works perfectly with YADIF disabled in the LAV settings. The problem is obviously with the interlaced videos. Also note that when YADIF is enabled on the 25p/30p setting, the problem also doesn't appear. My original setting was 50p/60p, and that's what causes trouble.

[colinhunt]

If it doesn't -- it is in violation of the standard. But I have my doubts that is the issue.
Was there a hidden option that would force BD-RB to make BDMV + SSIF directory structure for 3D back-ups? My memory's kinda hazy on that.

[jdobbs]

Was there a hidden option that would force BD-RB to make BDMV + SSIF directory structure for 3D back-ups? My memory's kinda hazy on that.Only for movie-only backups. But, as I said, it's likely something other than in-mux -- since that is a standard backup that is also present on commercial discs. I suspect you are blaming the wrong problem.

[jdobbs]

I think I got confirmation on something I've always wanted to ask: can the user-set settings of LAV filters (outside of BD-RB) interfere with a a backup? I completed a backup (I've deleted it) of a Blu-Ray with 1080i/25fps content and everything played in slow motion in the backup. This also happens with "Preview this item" in BD-RB.

In the LAV Video Configuration, I have Software Deinterlacing/YADIF enabled. If I disable it, the Preview plays fine in BD-RB with this Blu-Ray and I assume a new backup will also work fine.

Can BD-RB ignore the LAV user-settings or do the LAV Filters always need to be set in a specific way?There are lots of ways you can create an issue in a backup. Using filters is a good example. I don't see how deinterlacing would do it -- but if combined with certain settings maybe... of possibly it is showing up as 1080i/25p (which is illegal)?

I'd need an example and your settings to test it.

[Weirdo]

I'd need an example and your settings to test it.
http://thumbnails117.imagebam.com/53370/ff2b82533699114.jpg (http://www.imagebam.com/image/ff2b82533699114)

----------------------
[02-20-17] BD Rebuilder v0.50.23
[10:25:44] Source:
- Input BD size: 20.40 GB
- Approximate total content: [03:29:08.428]
- Target BD size: 4.36 GB
- Windows Version: 6.2 [9200]
- Resize: 1080p to 720p enabled
- Quality: Better (Faster), CRF
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=1 HD=1 Kbs=640
[10:25:58] PHASE ONE, Encoding
- [10:25:58] Processing: VID_00002 (1 of 26)
- [10:25:58] Extracting A/V streams [VID_00002]
- [10:26:23] Reencoding video [VID_00002]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25.000fps, 10,941 frames
- Convert: 1280x720, 50.000fps, 21,882 frames
- [10:26:23] Encoding using constant rate factor.
- [10:33:27] Video Encode complete
- [10:33:27] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:33:27] Multiplexing M2TS
- [10:33:33] Blanking: VID_00011 (2 of 26)
- [10:33:33] Blanking: VID_00012 (3 of 26)
- [10:33:33] Blanking: VID_00013 (4 of 26)
- [10:33:33] Processing: VID_00019 (5 of 26)
- [10:33:33] Extracting A/V streams [VID_00019]
- [10:33:39] Reencoding video [VID_00019]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,051 frames
- [10:33:39] Encoding using constant rate factor.
- [10:34:31] Video Encode complete
- [10:34:31] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:34:31] Multiplexing M2TS
- [10:34:35] Processing: VID_00021 (6 of 26)
- [10:34:35] Extracting A/V streams [VID_00021]
- [10:34:39] Reencoding video [VID_00021]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 240 frames
- [10:34:39] Encoding using constant rate factor.
- [10:34:44] Video Encode complete
- [10:34:44] Processing audio tracks
- [10:34:44] Multiplexing M2TS
- [10:34:48] Blanking: VID_00072 (7 of 26)
- [10:34:48] Blanking: VID_00079 (8 of 26)
- [10:34:48] Blanking: VID_00080 (9 of 26)
- [10:34:48] Processing: VID_00087 (10 of 26)
- [10:34:48] Extracting A/V streams [VID_00087]
- [10:36:13] Reencoding video [VID_00087]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25.000fps, 48,678 frames
- Convert: 1280x720, 50.000fps, 97,356 frames
- [10:36:13] Encoding using constant rate factor.
- [11:07:51] Video Encode complete
- [11:07:51] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:07:51] Multiplexing M2TS
- [11:08:05] Blanking: VID_00098 (11 of 26)
- [11:08:05] Processing: VID_00099 (12 of 26)
- [11:08:05] Extracting A/V streams [VID_00099]
- [11:08:50] Reencoding video [VID_00099]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 27,414 frames
- Convert: 1280x720, 24.000fps, 27,414 frames
- [11:08:50] Encoding using constant rate factor.
- [11:20:49] Video Encode complete
- [11:20:49] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:20:49] Multiplexing M2TS
- [11:20:57] Processing: VID_00100 (13 of 26)
- [11:20:57] Extracting A/V streams [VID_00100]
- [11:21:08] Reencoding video [VID_00100]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 4,617 frames
- Convert: 1280x720, 24.000fps, 4,617 frames
- [11:21:08] Encoding using constant rate factor.
- [11:24:11] Video Encode complete
- [11:24:11] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:24:11] Multiplexing M2TS
- [11:24:16] Processing: VID_00101 (14 of 26)
- [11:24:16] Extracting A/V streams [VID_00101]
- [11:24:28] Reencoding video [VID_00101]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 5,178 frames
- Convert: 1280x720, 24.000fps, 5,178 frames
- [11:24:28] Encoding using constant rate factor.
- [11:27:26] Video Encode complete
- [11:27:26] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:27:26] Multiplexing M2TS
- [11:27:30] Processing: VID_00102 (15 of 26)
- [11:27:30] Extracting A/V streams [VID_00102]
- [11:27:39] Reencoding video [VID_00102]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 3,061 frames
- Convert: 1280x720, 24.000fps, 3,061 frames
- [11:27:39] Encoding using constant rate factor.
- [11:29:18] Video Encode complete
- [11:29:18] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:29:18] Multiplexing M2TS
- [11:29:22] Processing: VID_00103 (16 of 26)
- [11:29:22] Extracting A/V streams [VID_00103]
- [11:29:36] Reencoding video [VID_00103]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 6,792 frames
- Convert: 1280x720, 24.000fps, 6,792 frames
- [11:29:36] Encoding using constant rate factor.
- [11:33:34] Video Encode complete
- [11:33:34] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:33:34] Multiplexing M2TS
- [11:33:39] Processing: VID_00104 (17 of 26)
- [11:33:39] Extracting A/V streams [VID_00104]
- [11:33:51] Reencoding video [VID_00104]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 5,287 frames
- Convert: 1280x720, 24.000fps, 5,287 frames
- [11:33:51] Encoding using constant rate factor.
- [11:36:53] Video Encode complete
- [11:36:53] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:36:53] Multiplexing M2TS
- [11:36:57] Processing: VID_00105 (18 of 26)
- [11:36:57] Extracting A/V streams [VID_00105]
- [11:37:10] Reencoding video [VID_00105]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 5,715 frames
- Convert: 1280x720, 24.000fps, 5,715 frames
- [11:37:10] Encoding using constant rate factor.
- [11:40:11] Video Encode complete
- [11:40:11] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:40:11] Multiplexing M2TS
- [11:40:16] Processing: VID_00106 (19 of 26)
- [11:40:16] Extracting A/V streams [VID_00106]
- [11:40:28] Reencoding video [VID_00106]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 4,825 frames
- Convert: 1280x720, 24.000fps, 4,825 frames
- [11:40:28] Encoding using constant rate factor.
- [11:43:26] Video Encode complete
- [11:43:26] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:43:26] Multiplexing M2TS
- [11:43:31] Processing: VID_00107 (20 of 26)
- [11:43:31] Extracting A/V streams [VID_00107]
- [11:43:42] Reencoding video [VID_00107]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 4,727 frames
- Convert: 1280x720, 24.000fps, 4,727 frames
- [11:43:42] Encoding using constant rate factor.
- [11:46:10] Video Encode complete
- [11:46:10] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:46:10] Multiplexing M2TS
- [11:46:15] Processing: VID_00108 (21 of 26)
- [11:46:15] Extracting A/V streams [VID_00108]
- [11:46:24] Reencoding video [VID_00108]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 3,738 frames
- Convert: 1280x720, 24.000fps, 3,738 frames
- [11:46:24] Encoding using constant rate factor.
- [11:48:37] Video Encode complete
- [11:48:37] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:48:37] Multiplexing M2TS
- [11:48:41] Processing: VID_00109 (22 of 26)
- [11:48:41] Extracting A/V streams [VID_00109]
- [11:48:54] Reencoding video [VID_00109]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 4,936 frames
- Convert: 1280x720, 24.000fps, 4,936 frames
- [11:48:54] Encoding using constant rate factor.
- [11:51:51] Video Encode complete
- [11:51:51] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:51:51] Multiplexing M2TS
- [11:51:55] Processing: VID_00110 (23 of 26)
- [11:51:55] Extracting A/V streams [VID_00110]
- [11:52:07] Reencoding video [VID_00110]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 4,640 frames
- Convert: 1280x720, 24.000fps, 4,640 frames
- [11:52:07] Encoding using constant rate factor.
- [11:54:59] Video Encode complete
- [11:54:59] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:54:59] Multiplexing M2TS
- [11:55:04] Processing: VID_00111 (24 of 26)
- [11:55:04] Extracting A/V streams [VID_00111]
- [11:55:13] Reencoding video [VID_00111]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 3,340 frames
- Convert: 1280x720, 24.000fps, 3,340 frames
- [11:55:13] Encoding using constant rate factor.
- [11:57:16] Video Encode complete
- [11:57:16] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:57:16] Multiplexing M2TS
- [11:57:21] Processing: VID_00112 (25 of 26)
- [11:57:21] Extracting A/V streams [VID_00112]
- [11:57:31] Reencoding video [VID_00112]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 3,988 frames
- Convert: 1280x720, 24.000fps, 3,988 frames
- [11:57:31] Encoding using constant rate factor.
- [11:59:37] Video Encode complete
- [11:59:37] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:59:37] Multiplexing M2TS
- [11:59:41] Processing: VID_00113 (26 of 26)
- [11:59:41] Extracting A/V streams [VID_00113]
- [11:59:55] Reencoding video [VID_00113]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24.000fps, 6,479 frames
- Convert: 1280x720, 24.000fps, 6,479 frames
- [11:59:55] Encoding using constant rate factor.
- [12:03:34] Video Encode complete
- [12:03:34] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [12:03:34] Multiplexing M2TS
[12:03:39]PHASE ONE complete
[12:03:39]PHASE TWO - Rebuild Started
- [12:03:39] Rebuilding BD file Structure
[12:03:41] - Encode and Rebuild complete
- WORKFILES folder removed.
[12:03:41] JOB: finished.

[02-20-17] Checking System Settings
- BD-Rebuilder v0.50.23
- Windows Version: 6.2 [9200]
- Working Path Free Space: 50.76GB
- AVISYNTH Version: 2.6.0.5, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[02-20-17] Systems Settings Check complete

[jdobbs]

Can you post your settings (the contents of the BDREBUILDER.INI file)?

Note this in your log, it's probably the root of the problem:

- Resize: 1080p to 720p enabled
- Convert: 1280x720, 50.000fps, 21,882 frames

[Weirdo]

Can you post your settings (the contents of the BDREBUILDER.INI file)?
Oh ok, sorry. I now see in the preview that the 1080p/24 files do not display video speed issues (with the same LAV/YADIF setting enabled) but the audio goes out of sync. The 1080i/25 ones are worse, as described.

[Options]
ENABLE_TEST=1
VERSION=0.50.0.23
FORCE_ENCODE=1
FIXED_CRF=19
ENCODER=0
MODE=0
ENCODE_QUALITY=1
ONEPASS_ENCODING=1
AUTO_QUALITY=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=all
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=1
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
WIDE_PERCENT=100
WIDE_OFFSET=1
DTS_REENCODE=1
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=0
AVCHD=1
REMOVE_WORKFILES=1
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=7000
MINIMIZE_TO_TRAY=1
TARGET_SIZE=4469
PGSTOSRT=0
ENABLE_BLANKING=1
PRIORITY_CLASS=1
MOVIEONLY_TYPE=11
ALTCRF=19
ALT_TARGET=1024
ALT_CRF_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
[Paths]
SOURCE_PATH=
WORKING_PATH=

[bebopper]

I've not posted before, but recently experiencing some issues, all 1080i source related (both 23.97 & 29.97fps content). This started happening with v0.50.19, which prompted a switch to v0.50.23 but with same results. The output video is 1920x2160i, fps is unchanged, but audio is then out of sync with video (audio plays faster, I think). I'm using all suggested ffdshow settings. Any help or suggestions would be greatly appreciated. Thanks.

My BD-RB settings are as follows:
VERSION=0.50.0.23
ENCODER=0
MODE=0
ENCODE_QUALITY=2
ONEPASS_ENCODING=0
AUTO_QUALITY=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=1
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=0
AUDIO_DRC=0
DECODER=4
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
SHUTDOWN_SLEEP=1
CUSTOM_TARGET_SIZE=4574
TARGET_SIZE=26550
AUTO_BURN=0

[thekiller]

1. Please post the contents of your ALTERNATE.TXT file so I can see if it's entered correctly.
2. Are any other encodes working?
3. As gonca suggested, please post INSPECT results.

hello, thank you for the reponse

# The options below show up in the Alternate Output Dialog
# Settings:
# caption=Text to show on alternate selection list
# vEncoder=Video encoder, 0=x264 (default), 1=x265, 2=HC Encoder (MPEG-2)
# Note: A cType of 3 or 4 (see below) forces MPEG-2 via HCEncoder
# vBitrate=Bitrate to use for two-pass video encoding, * = variable (DVD only)
# aBitrate=Bitrate to use for audio encoding, * = automatic (constant quality encode, not allowed for iPod & iPad)
# aType=Output Audio Type, 0=AC3, 1=AAC (Note: Audio bitrate less than 384Kbs implies stereo downmix)
# 2=[Intact audio -- MKV & MP4 only]
# vFormat=Video Format: 0=320x240/180, 1= 480x360/270, 2= 640x480/360, 3= 1024x768/576,
# 4= 1280x720, 5= 1920x1080, 6= 720x480/576, 7= No Resizing, 8=Intact
# vKeyint=Video GOP size (interval): Default=24, "Auto" = 10x framerate (MKV & MP4 only)
# cType= Container/limits type, 0=iPod (mp4), 1=MKV, 2=iPad (mp4), 3=DVD-5, 4=DVD-9, 5=MP4 6=iPad 2+ (MP4)

[00001]
caption=DVD-5, 720x480/576, AC3 Audio
vBitrate=*
aBitrate=*
aType=0
vFormat=6
cType=3
[00002]
caption=DVD-9, 720x480/576, AC3 Audio
vBitrate=*
aBitrate=*
aType=0
vFormat=6
cType=4
[00003]
caption=iPod MP4, 640x480/360, 128Kbs AAC
vBitrate=583
aBitrate=128
aType=1
vFormat=2
cType=0
[00004]
caption=iPod MP4, 480x360/270, 112Kbs AAC
vBitrate=421
aBitrate=112
aType=1
vFormat=1
cType=0
[00005]
caption=iPod MP4, 320x240/180, 64Kbs AAC
vBitrate=281
aBitrate=96
aType=1
vFormat=0
cType=0
[00006]
caption=MKV Container, 720x480/576, 128Kbs AC3
vBitrate=872
aBitrate=128
aType=0
vFormat=6
cType=1
[00007]
caption=MKV Container, 1280x720, 192Kbs AC3
vBitrate=1230
aBitrate=192
aType=0
vFormat=4
cType=1
[00008]
caption=MKV Container, 1280x720, 448Kbs DD5.1
vBitrate=1230
aBitrate=448
aType=0
vFormat=4
cType=1
[00009]
caption=MKV Container, 1920x1080, 192Kbs AC3
vBitrate=1941
aBitrate=192
aType=0
vFormat=5
cType=1
[00010]
caption=MKV Container, 1920x1080, 640Kbs DD5.1
vBitrate=1941
aBitrate=640
aType=0
vFormat=5
cType=1
[00011]
caption=MKV Container, 1920x1080, Intact Audio
vBitrate=3000
aBitrate=0
aType=2
vFormat=5
cType=1
[00012]
caption=iPad MP4 HD, 1280x720, 128Kbs AAC
vBitrate=1500
aBitrate=128
aType=1
vFormat=4
cType=2
[00013]
caption=iPad MP4 HD, 1024x768/576, 128Kbs AAC
vBitrate=1009
aBitrate=128
aType=1
vFormat=3
cType=2
[00014]
caption=iPad MP4 SD, 640x480/360, 128Kbs AAC
vBitrate=583
aBitrate=128
aType=1
vFormat=2
cType=2
[00015]
caption=iPad MP4 SD, 480x360/270, 112Kbs AAC
vBitrate=421
aBitrate=112
aType=1
vFormat=1
cType=2
[00016]
caption=iPad MP4 SD, 720x480/576, 128Kbs AAC
vBitrate=872
aBitrate=128
aType=1
vFormat=6
cType=2
[00017]
caption=MKV Container, 1920x1080, Auto-AAC
vBitrate=3000
aBitrate=*
aType=1
vFormat=5
cType=1
[00018]
caption=MKV Container, 1280x720, Auto-AAC
vBitrate=2000
aBitrate=*
aType=1
vFormat=4
cType=1
[00019]
caption=MP4 Container, 1920x1080, AutoGOP, Auto-AAC
vBitrate=3000
aBitrate=*
aType=1
vFormat=5
vKeyint=Auto
cType=5
[00020]
caption=MP4 Container, 1280x720, AutoGOP, Auto-AAC
vBitrate=2000
aBitrate=*
aType=1
vFormat=4
vKeyint=Auto
cType=5
[00021]
caption=MP4 Container, NO_RESIZE, AutoGOP, Auto-AAC
vBitrate=2000
aBitrate=*
aType=1
vFormat=7
vKeyint=Auto
cType=5
[00022]
caption=MKV Container, NO_RESIZE, AutoGOP, Auto-AAC
vBitrate=2000
aBitrate=*
aType=1
vFormat=7
vKeyint=Auto
cType=1
[00023]
caption=iPad 2+/iPhone 4s+, 1920x1080, 160Kbs AAC
vBitrate=3000
aBitrate=160
aType=1
vFormat=5
cType=6
[00024]
caption=iPad 2+/iPhone 4s+, 1280x720, 128Kbs AAC
vBitrate=2000
aBitrate=128
aType=1
vFormat=4
cType=6
[00025]
caption=iPad 2+/iPhone 4s+, 720x480/576, 128Kbs AAC
vBitrate=872
aBitrate=128
aType=1
vFormat=6
cType=6
[00026]
caption=MP4, Intact Video, AutoGOP, Auto-AAC
vBitrate=2000
aBitrate=*
aType=1
vFormat=8
vKeyint=Auto
cType=5
[00027]
caption=MKV, Intact Video, AutoGOP, Auto-AAC
vBitrate=2000
aBitrate=*
aType=1
vFormat=8
vKeyint=Auto
cType=1
[00028]
caption=MKV, Intact Video, Intact Audio
aType=2
vFormat=8
cType=1
[00029]
caption=MP4, Intact Video, Intact Audio
aType=2
vFormat=8
cType=5
[00030]
caption=MKV Container, 720x480/576, Intact Audio
vBitrate=872
aType=2
vFormat=6
cType=1
[00031]
caption=MP4 Container, Full-SBS (3D), Intact Audio
vBitrate=4000
aType=2
vFormat=7
cType=5
[00032]
caption=MKV Container, Full-SBS (3D), Intact Audio
vBitrate=4000
aType=2
vFormat=7
cType=1
[00033]
caption=MKV Container, HEVC 1920x1080, Auto-AAC
vEncoder=1
vBitrate=2000
vKeyint=Auto
aBitrate=*
aType=1
vFormat=5
cType=1
[00034]
caption=MKV Container, HEVC 1280x720, Auto-AAC
vEncoder=1
vBitrate=1300
vKeyint=Auto
aBitrate=*
aType=1
vFormat=4
cType=1
[00035]
caption=MKV Container, HEVC Full-SBS 3D,Auto-AAC
vEncoder=1
vBitrate=2000
vKeyint=Auto
aType=1
aBitrate=*
vFormat=7
cType=1
[00036]
caption=MKV Container, HEVC Half-SBS 3D, Intact Audio
vEncoder=1
vBitrate=2000
vKeyint=Auto
aType=2
vFormat=5
cType=1
[00037]
caption=MKV Container, NO_RESIZE, AutoGOP, Auto-AC3
vBitrate=2000
aBitrate=*
aType=0
vFormat=7
vKeyint=Auto
cType=1
[00038]
caption=MP4 Container, NO_RESIZE, AutoGOP, Auto-AC3
vBitrate=2000
aBitrate=*
aType=0
vFormat=7
vKeyint=Auto
cType=5
[00039]
caption=MKV Container, HEVC 1920x1080, 448Kbs DD5.1
vEncoder=1
vBitrate=2000
vKeyint=Auto
aBitrate=448
aType=0
vFormat=5
cType=1


INSPECT -->

[02/20/17] Checking System Settings
- BD-Rebuilder v0.50.23
- Windows Version: 6.2 [9200]
- Working Path Free Space: 3*242,76GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[02/20/17] Systems Settings Check complete


On the other hand it takes me by default not the video bonn of the film, it takes me a long version!

[jdobbs]

I've not posted before, but recently experiencing some issues, all 1080i source related (both 23.97 & 29.97fps content). This started happening with v0.50.19, which prompted a switch to v0.50.23 but with same results. The output video is 1920x2160i, fps is unchanged, but audio is then out of sync with video (audio plays faster, I think). I'm using all suggested ffdshow settings. Any help or suggestions would be greatly appreciated. Thanks.1. 1920x2160i ? Is it a 3D source? If so, how could it have been interlaced?
2. Audio plays faster? I don't see how that is even possible -- it is never adjusted.

[bebopper]

1. 1920x2160i ? Is it a 3D source? If so, how could it have been interlaced?
2. Audio plays faster? I don't see how that is even possible -- it is never adjusted.

1. Not a 3D source; titles I'm having trouble with are nature documentaries from BBC or (US) PBS Nature. I really don't know how the output becomes interlaced (goes from 1920x1080i 16:9, verified with BDInfo, VLC player etc, to 1920x2160i 8:9). As you can see from my settings, I use almost all default settings except choosing a custom target size and whether to convert DTS to DD. I've tried turning deinterlacer off, but output is exactly the same.

2. By audio playing faster, I mean relative to the video image, after BD-RB processing. The audio becomes out of sync with video very quickly when starting from the beginning.

I just noticed there is the "IVTC with 3:2 pulldown" option in setup menu, which I've not tried before, should I try it to see what the output looks like? Thanks.

[jdobbs]

1. Not a 3D source; titles I'm having trouble with are nature documentaries from BBC or (US) PBS Nature. I really don't know how the output becomes interlaced (goes from 1920x1080i 16:9, verified with BDInfo, VLC player etc, to 1920x2160i 8:9). As you can see from my settings, I use almost all default settings except choosing a custom target size and whether to convert DTS to DD. I've tried turning deinterlacer off, but output is exactly the same.

2. By audio playing faster, I mean relative to the video image, after BD-RB processing. The audio becomes out of sync with video very quickly when starting from the beginning.

I just noticed there is the "IVTC with 3:2 pulldown" option in setup menu, which I've not tried before, should I try it to see what the output looks like? Thanks.I'm definitely confused. BD-RB hasn't even an option to possibly output 1920x2160i.

Are you using a Blu-Ray disc as your source, or are you importing first?

[bebopper]

I'm definitely confused. BD-RB hasn't even an option to possibly output 1920x2160i.

Are you using a Blu-Ray disc as your source, or are you importing first?

I've tried processing from a ripped BD image to HDD and from a main movie only BD file structure extracted from ripped BD image (using clownBD), but not direct from BD. In both cases I've tried, the results are the same.

So, I misspoke in my earlier post. The BD-RB processed video playback is faster than the audio, not the other way around. Sorry.

And, thinking about it more, the IVTC with 3:2 pulldown option won't help since I'm not looking to convert into a "film". Apologize for the brain fart. Thanks.

[jdobbs]

I've tried processing from a ripped BD image to HDD and from a main movie only BD file structure extracted from ripped BD image (using clownBD), but not direct from BD. In both cases I've tried, the results are the same.

So, I misspoke in my earlier post. The BD-RB processed video playback is faster than the audio, not the other way around. Sorry.

And, thinking about it more, the IVTC with 3:2 pulldown option won't help since I'm not looking to convert into a "film". Apologize for the brain fart. Thanks.This one is weird. Can you post the log?

[bebopper]

This one is weird. Can you post the log?

Ok, here are 2 logs: (1) used BD-RB on just the main movie, (2) used BD-RB on blu-ray disk image:

----------------------
[02/05/17] BD Rebuilder v0.50.23
[21:56:10] Source: SUPER_HUMMINGBIRDS_PCM
- Input BD size: 13.04 GB
- Approximate total content: [00:52:59.209]
- Target BD size: 4.58 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), Two Pass
- SHUTDOWN at completion enabled
- Decoding/Frame serving: FRIMSource
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[21:56:10] PHASE ONE, Encoding
- [21:56:10] Processing: VID_00000 (1 of 1)
- [21:56:10] Extracting A/V streams [VID_00000]
- [21:58:30] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 95,281 frames
- Bitrate: 10,749 Kbs
- [21:58:30] Reencoding: VID_00000, Pass 1 of 2
- [22:29:47] Reencoding: VID_00000, Pass 2 of 2
- [23:43:09] Video Encode complete
- [23:43:09] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [23:43:26] Multiplexing M2TS
[23:44:11]PHASE ONE complete
[23:44:11]PHASE TWO - Rebuild Started
- [23:44:11] Rebuilding BD file Structure
[23:44:11] - Encode and Rebuild complete
- Computer SLEEP initiated.
[06:11:41] JOB: SUPER_HUMMINGBIRDS_DTS-CORE finished.
----------------------
[02/06/17] BD Rebuilder v0.50.23
[06:30:12] Source: SUPER_HUMMINGBIRDS
- Input BD size: 14.18 GB
- Approximate total content: [00:54:09.421]
- Target BD size: 4.53 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), Two Pass
- SHUTDOWN at completion enabled
- Decoding/Frame serving: FRIMSource
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[06:30:12] PHASE ONE, Encoding
- [06:30:12] Processing: VID_00000 (1 of 5)
- [06:30:12] Extracting A/V streams [VID_00000]
- [06:30:20] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,382 frames
- Bitrate: 10,762 Kbs
- [06:30:20] Reencoding: VID_00000, Pass 1 of 2
- [06:30:52] Reencoding: VID_00000, Pass 2 of 2
- [06:32:07] Video Encode complete
- [06:32:07] Processing audio tracks
- Track 4352 (und): Keeping original audio
- [06:32:07] Multiplexing M2TS
- [06:32:12] Processing: VID_00001 (2 of 5)
- [06:32:12] Extracting A/V streams [VID_00001]
- [06:32:15] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 217 frames
- Bitrate: 632 Kbs
- [06:32:15] Reencoding: VID_00001, Pass 1 of 2
- [06:32:17] Reencoding: VID_00001, Pass 2 of 2
- [06:32:19] Video Encode complete
- [06:32:19] Processing audio tracks
- [06:32:19] Multiplexing M2TS
- [06:32:23] Processing: VID_00002 (3 of 5)
- [06:32:23] Extracting A/V streams [VID_00002]
- [06:32:27] Reencoding video [VID_00002]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 225 frames
- Bitrate: 7,998 Kbs
- [06:32:27] Reencoding: VID_00002, Pass 1 of 2
- [06:32:32] Reencoding: VID_00002, Pass 2 of 2
- [06:32:42] Video Encode complete
- [06:32:42] Processing audio tracks
- Track 4352 (und): Reencoding audio to AC3...
- [06:32:42] Multiplexing M2TS
- [06:32:46] Processing: VID_00003 (4 of 5)
- [06:32:46] Extracting A/V streams [VID_00003]
- [06:32:50] Reencoding video [VID_00003]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 225 frames
- Bitrate: 9,086 Kbs
- [06:32:50] Reencoding: VID_00003, Pass 1 of 2
- [06:32:55] Reencoding: VID_00003, Pass 2 of 2
- [06:33:05] Video Encode complete
- [06:33:05] Processing audio tracks
- Track 4352 (und): Reencoding audio to AC3...
- [06:33:06] Multiplexing M2TS
- [06:33:09] Processing: VID_00004 (5 of 5)
- [06:33:09] Extracting A/V streams [VID_00004]
- [06:35:31] Reencoding video [VID_00004]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 95,282 frames
- Bitrate: 10,394 Kbs
- [06:35:31] Reencoding: VID_00004, Pass 1 of 2
- [07:07:29] Reencoding: VID_00004, Pass 2 of 2
- [08:20:37] Video Encode complete
- [08:20:37] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [08:20:56] Multiplexing M2TS
[08:22:08]PHASE ONE complete
[08:22:08]PHASE TWO - Rebuild Started
- [08:22:08] Rebuilding BD file Structure
[08:22:08] - Encode and Rebuild complete
- Computer SLEEP initiated.
[08:34:25] JOB: SUPER_HUMMINGBIRDS finished.

Thanks very much for your help.

[jdobbs]

- Decoding/Frame serving: FRIMSource1. Have you tried using a different decoder than FRIMSource? I'd like to see if that is related to the issue. I'd suggest using LAV filters. It seems to be likely more than coincidence that FRIMSource is used most often for 3D encoding (such as O/U) -- and your output is doubling the horizontal size.

2. Are you using the version of FRIM that is included with BD-RB, or have you "upgraded"?

[colinhunt]

Only for movie-only backups. But, as I said, it's likely something other than in-mux -- since that is a standard backup that is also present on commercial discs. I suspect you are blaming the wrong problem.
That's certainly possible. What do you think is behind my PS4 playing those inmux-titles in 2D only?

I'd like to test SSIF output, even if it's for movie-only backup. What hidden options do I need to set for that? Thank you!

[marco421]

this is a new issue. on the last 2 movies I decoded (inferno and Jason bourne) the sound quit due to cineavia. the bd-rb version I used was 50.23. unfortunately, I don't remember if I've gotten a playable movie using that version. I know that version 50.21 works ok. how do I get around being bitten by cineavia or do I just go back to an older version?

[gonca]

how do I get around being bitten by cineavia

BD_RB doesn't deal with Cinavia, never has.

Get a player that doesn't enforce Cinavia

[jdobbs]

this is a new issue. on the last 2 movies I decoded (inferno and Jason bourne) the sound quit due to cineavia. the bd-rb version I used was 50.23. unfortunately, I don't remember if I've gotten a playable movie using that version. I know that version 50.21 works ok. how do I get around being bitten by cineavia or do I just go back to an older version?BD-RB can't attempt to defeat any type of protection mechanism -- otherwise it would be illegal in the U.S. and would get shut down.

There is software out there that can remove cinavia -- but mechanisms for defeating copyright protection isn't the purpose of this thread, so it's better to discuss it elsewhere.

[bebopper]

1. Have you tried using a different decoder than FRIMSource? I'd like to see if that is related to the issue. I'd suggest using LAV filters. It seems to be likely more than coincidence that FRIMSource is used most often for 3D encoding (such as O/U) -- and your output is doubling the horizontal size.

2. Are you using the version of FRIM that is included with BD-RB, or have you "upgraded"?

No, I've just been using whatever BD-RB's default setup is (i.e. no upgrading). I'll be happy to try with LAV filters. To do so, is it simply de-selecting "use FRIMSource for frame serving" option and selecting "Use x264's internal LAVF for frame serving" in BD-RB's setup? If some other change required, I'll need a pointer as to how to make that selection/change. Thanks.

[gonca]

No, I've just been using whatever BD-RB's default setup is (i.e. no upgrading). I'll be happy to try with LAV filters. To do so, is it simply de-selecting "use FRIMSource for frame serving" option and selecting "Use x264's internal LAVF for frame serving" in BD-RB's setup? If some other change required, I'll need a pointer as to how to make that selection/change. Thanks.

Select use DirectShowSource
Frim isn't the "Default"

[bebopper]

Select use DirectShowSource
Frim isn't the "Default"

Thank you, gonca. If FRIMSource is not the BD-RB default, I don't know how I ended up with that selected....

[jdobbs]

Thank you, gonca. If FRIMSource is not the BD-RB default, I don't know how I ended up with that selected....If you didn't install LAV Filters or FFDSHOW it might have ended up there.

I wasn't talking about LAVF in X264 (although that would be fine to test as well). I was talking about LAV Filters. See the first post of this thread for instructions on how to install.

[Lathe]

this is a new issue. on the last 2 movies I decoded (inferno and Jason bourne) the sound quit due to cineavia. the bd-rb version I used was 50.23. unfortunately, I don't remember if I've gotten a playable movie using that version. I know that version 50.21 works ok. how do I get around being bitten by cineavia or do I just go back to an older version?

I have an older OPPO BDP-83 that is still considered one of the finest Blu-ray players if you don't need streaming or 3D. It is Pre-Cinavia. I don't remember when OPPO had to begin implementing Cinavia in their players. You can get my model and others all over the place, eBay, etc. They still really hold their value...

[MrVideo]

I don't remember when OPPO had to begin implementing Cinavia in their players.
All Blu-ray players that were built in Feb 2012, and after, were required to have Cinavia detection.

[bebopper]

If you didn't install LAV Filters or FFDSHOW it might have ended up there.

I wasn't talking about LAVF in X264 (although that would be fine to test as well). I was talking about LAV Filters. See the first post of this thread for instructions on how to install.

I did indeed install both LAV filters and FFDSHOW from the start, so still not sure how I ended up with FRIMSource selected. In any case, the good news is in switching frame serving choice to DirectshowSource, post processed videos are now as they should be (though still interlaced; I thought the x264 encoder turns into progressive?; will need to check previous logs with interlaced source to confirm). Thank you jdobbs and gonca for your help in getting this resolved.

[jdobbs]

I did indeed install both LAV filters and FFDSHOW from the start, so still not sure how I ended up with FRIMSource selected. In any case, the good news is in switching frame serving choice to DirectshowSource, post processed videos are now as they should be (though still interlaced; I thought the x264 encoder turns into progressive?; will need to check previous logs with interlaced source to confirm). Thank you jdobbs and gonca for your help in getting this resolved.They won't be made progressive unless you have selected "Use DEINTERLACER on interlaced sources" from the SETUP menu. The default is to keep them in their original format.

Glad it fixed it for you -- but there is obviously a problem in the way I'm using FRIMSource() -- so I still have a bug to fix.

[bebopper]

They won't be made progressive unless you have selected "Use DEINTERLACER on interlaced sources" from the SETUP menu. The default is to keep them in their original format.


Thanks, jdobbs for the explanation. One option I always have selected is "use DEINTERLACER", which explains why I thought all interlaced videos post processing are progressive.... except for this latest Hummingbird one. Not a big issue, and I'm not asking for more cycles to be spent on this, especially since you already FRIMSource() to address. Again, thanks very much for your help.

[MrVideo]

Thanks, jdobbs for the explanation. One option I always have selected is "use DEINTERLACER" ...
Why do you want to de-interlace 1080i material that is sourced from video cameras? If the 1080i material is from a 23.976 source, then it needs to be IVTC'd, not de-interlaced.

The reason for not de-interlacing 1080i raw video is that you remove 1/2 of the time spatial information. Instead of objects moving at 59.94 times per second, they are now moving at 29.97 times per second. You also compromise some of the vertical resolution as well. The software has to combine two field images into a single frame. If the images are drastically different, it becomes a WAG as to what the new image should look like. The software has gotten better in this regard, but losing 1/2 of time spatial info is a downer.

Just my opinion. :D

[jdobbs]

Why do you want to de-interlace 1080i material that is sourced from video cameras? If the 1080i material is from a 23.976 source, then it needs to be IVTC'd, not de-interlaced.

The reason for not de-interlacing 1080i raw video is that you remove 1/2 of the time spatial information. Instead of objects moving at 59.94 times per second, they are now moving at 29.97 times per second. You also compromise some of the vertical resolution as well. The software has to combine two field images into a single frame. If the images are drastically different, it becomes a WAG as to what the new image should look like. The software has gotten better in this regard, but losing 1/2 of time spatial info is a downer.

Just my opinion. :DAgreed. The only time I can see a good reason is if you are playing it back on a device that can't handle actual interlaced sources (like a computer w/monitor). Of course a computer/monitor will most likely have the ability to deinterlace at playback.

[thekiller]

hello, thank you for the reponse

# The options below show up in the Alternate Output Dialog
# Settings:
# caption=Text to show on alternate selection list
# vEncoder=Video encoder, 0=x264 (default), 1=x265, 2=HC Encoder (MPEG-2)
# Note: A cType of 3 or 4 (see below) forces MPEG-2 via HCEncoder
# vBitrate=Bitrate to use for two-pass video encoding, * = variable (DVD only)
# aBitrate=Bitrate to use for audio encoding, * = automatic (constant quality encode, not allowed for iPod & iPad)
# aType=Output Audio Type, 0=AC3, 1=AAC (Note: Audio bitrate less than 384Kbs implies stereo downmix)
# 2=[Intact audio -- MKV & MP4 only]
# vFormat=Video Format: 0=320x240/180, 1= 480x360/270, 2= 640x480/360, 3= 1024x768/576,
# 4= 1280x720, 5= 1920x1080, 6= 720x480/576, 7= No Resizing, 8=Intact
# vKeyint=Video GOP size (interval): Default=24, "Auto" = 10x framerate (MKV & MP4 only)
# cType= Container/limits type, 0=iPod (mp4), 1=MKV, 2=iPad (mp4), 3=DVD-5, 4=DVD-9, 5=MP4 6=iPad 2+ (MP4)

[00001]
caption=DVD-5, 720x480/576, AC3 Audio
vBitrate=*
aBitrate=*
aType=0
vFormat=6
cType=3
[00002]
caption=DVD-9, 720x480/576, AC3 Audio
vBitrate=*
aBitrate=*
aType=0
vFormat=6
cType=4
[00003]
caption=iPod MP4, 640x480/360, 128Kbs AAC
vBitrate=583
aBitrate=128
aType=1
vFormat=2
cType=0
[00004]
caption=iPod MP4, 480x360/270, 112Kbs AAC
vBitrate=421
aBitrate=112
aType=1
vFormat=1
cType=0
[00005]
caption=iPod MP4, 320x240/180, 64Kbs AAC
vBitrate=281
aBitrate=96
aType=1
vFormat=0
cType=0
[00006]
caption=MKV Container, 720x480/576, 128Kbs AC3
vBitrate=872
aBitrate=128
aType=0
vFormat=6
cType=1
[00007]
caption=MKV Container, 1280x720, 192Kbs AC3
vBitrate=1230
aBitrate=192
aType=0
vFormat=4
cType=1
[00008]
caption=MKV Container, 1280x720, 448Kbs DD5.1
vBitrate=1230
aBitrate=448
aType=0
vFormat=4
cType=1
[00009]
caption=MKV Container, 1920x1080, 192Kbs AC3
vBitrate=1941
aBitrate=192
aType=0
vFormat=5
cType=1
[00010]
caption=MKV Container, 1920x1080, 640Kbs DD5.1
vBitrate=1941
aBitrate=640
aType=0
vFormat=5
cType=1
[00011]
caption=MKV Container, 1920x1080, Intact Audio
vBitrate=3000
aBitrate=0
aType=2
vFormat=5
cType=1
[00012]
caption=iPad MP4 HD, 1280x720, 128Kbs AAC
vBitrate=1500
aBitrate=128
aType=1
vFormat=4
cType=2
[00013]
caption=iPad MP4 HD, 1024x768/576, 128Kbs AAC
vBitrate=1009
aBitrate=128
aType=1
vFormat=3
cType=2
[00014]
caption=iPad MP4 SD, 640x480/360, 128Kbs AAC
vBitrate=583
aBitrate=128
aType=1
vFormat=2
cType=2
[00015]
caption=iPad MP4 SD, 480x360/270, 112Kbs AAC
vBitrate=421
aBitrate=112
aType=1
vFormat=1
cType=2
[00016]
caption=iPad MP4 SD, 720x480/576, 128Kbs AAC
vBitrate=872
aBitrate=128
aType=1
vFormat=6
cType=2
[00017]
caption=MKV Container, 1920x1080, Auto-AAC
vBitrate=3000
aBitrate=*
aType=1
vFormat=5
cType=1
[00018]
caption=MKV Container, 1280x720, Auto-AAC
vBitrate=2000
aBitrate=*
aType=1
vFormat=4
cType=1
[00019]
caption=MP4 Container, 1920x1080, AutoGOP, Auto-AAC
vBitrate=3000
aBitrate=*
aType=1
vFormat=5
vKeyint=Auto
cType=5
[00020]
caption=MP4 Container, 1280x720, AutoGOP, Auto-AAC
vBitrate=2000
aBitrate=*
aType=1
vFormat=4
vKeyint=Auto
cType=5
[00021]
caption=MP4 Container, NO_RESIZE, AutoGOP, Auto-AAC
vBitrate=2000
aBitrate=*
aType=1
vFormat=7
vKeyint=Auto
cType=5
[00022]
caption=MKV Container, NO_RESIZE, AutoGOP, Auto-AAC
vBitrate=2000
aBitrate=*
aType=1
vFormat=7
vKeyint=Auto
cType=1
[00023]
caption=iPad 2+/iPhone 4s+, 1920x1080, 160Kbs AAC
vBitrate=3000
aBitrate=160
aType=1
vFormat=5
cType=6
[00024]
caption=iPad 2+/iPhone 4s+, 1280x720, 128Kbs AAC
vBitrate=2000
aBitrate=128
aType=1
vFormat=4
cType=6
[00025]
caption=iPad 2+/iPhone 4s+, 720x480/576, 128Kbs AAC
vBitrate=872
aBitrate=128
aType=1
vFormat=6
cType=6
[00026]
caption=MP4, Intact Video, AutoGOP, Auto-AAC
vBitrate=2000
aBitrate=*
aType=1
vFormat=8
vKeyint=Auto
cType=5
[00027]
caption=MKV, Intact Video, AutoGOP, Auto-AAC
vBitrate=2000
aBitrate=*
aType=1
vFormat=8
vKeyint=Auto
cType=1
[00028]
caption=MKV, Intact Video, Intact Audio
aType=2
vFormat=8
cType=1
[00029]
caption=MP4, Intact Video, Intact Audio
aType=2
vFormat=8
cType=5
[00030]
caption=MKV Container, 720x480/576, Intact Audio
vBitrate=872
aType=2
vFormat=6
cType=1
[00031]
caption=MP4 Container, Full-SBS (3D), Intact Audio
vBitrate=4000
aType=2
vFormat=7
cType=5
[00032]
caption=MKV Container, Full-SBS (3D), Intact Audio
vBitrate=4000
aType=2
vFormat=7
cType=1
[00033]
caption=MKV Container, HEVC 1920x1080, Auto-AAC
vEncoder=1
vBitrate=2000
vKeyint=Auto
aBitrate=*
aType=1
vFormat=5
cType=1
[00034]
caption=MKV Container, HEVC 1280x720, Auto-AAC
vEncoder=1
vBitrate=1300
vKeyint=Auto
aBitrate=*
aType=1
vFormat=4
cType=1
[00035]
caption=MKV Container, HEVC Full-SBS 3D,Auto-AAC
vEncoder=1
vBitrate=2000
vKeyint=Auto
aType=1
aBitrate=*
vFormat=7
cType=1
[00036]
caption=MKV Container, HEVC Half-SBS 3D, Intact Audio
vEncoder=1
vBitrate=2000
vKeyint=Auto
aType=2
vFormat=5
cType=1
[00037]
caption=MKV Container, NO_RESIZE, AutoGOP, Auto-AC3
vBitrate=2000
aBitrate=*
aType=0
vFormat=7
vKeyint=Auto
cType=1
[00038]
caption=MP4 Container, NO_RESIZE, AutoGOP, Auto-AC3
vBitrate=2000
aBitrate=*
aType=0
vFormat=7
vKeyint=Auto
cType=5
[00039]
caption=MKV Container, HEVC 1920x1080, 448Kbs DD5.1
vEncoder=1
vBitrate=2000
vKeyint=Auto
aBitrate=448
aType=0
vFormat=5
cType=1


INSPECT -->

[02/20/17] Checking System Settings
- BD-Rebuilder v0.50.23
- Windows Version: 6.2 [9200]
- Working Path Free Space: 3*242,76GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[02/20/17] Systems Settings Check complete


On the other hand it takes me by default not the video bonn of the film, it takes me a long version!

For this to happen I first converted:
Caption = MKV, Intact Video, Intact Audio
AType = 2
VFormat = 8
CType = 1

And then I reconvert to hevc

Caption = MKV Container, HEVC No Resizing, Intact Audio
VEncoder = 1
VBitrate = 2000
VKeyint = Auto
AType = 2
VFormat = 7
CType = 1

And I have no more

thank

[gonca]

Just wondering
Why do you convert twice?
Why not convert the first time to
MKV Container, HEVC No Resizing, Intact Audio

Or use the source to convert to both formats

[DrinkLyeAndDie]

I have an older OPPO BDP-83 that is still considered one of the finest Blu-ray players if you don't need streaming or 3D. It is Pre-Cinavia. I don't remember when OPPO had to begin implementing Cinavia in their players. You can get my model and others all over the place, eBay, etc. They still really hold their value...

Not meaning to sidetrack this thread but in reply to this:

The Oppo BDP-8x and BDP-9x players were free of Cinavia. Beginning with the BDP-10x players and onward Cinavia has been manditorily implemented.

[thekiller]

Just wondering
Why do you convert twice?
Why not convert the first time to


Or use the source to convert to both formats

The first is the bluray in x264 and after I re import the mkv obtained in bdrebuilder and I do a reencoding in hevc

[HWK]

The first is the bluray in x264 and after I re import the mkv obtained in bdrebuilder and I do a reencoding in hevc

You can go from Blu-ray to hevc directly. Yes it will output mkv file.

[thekiller]

Not most of the time it works but not on some

[HWK]

Not most of the time it works but not on some

Can you share example which doesn't work.

[HWK]

@ Jdobbs for alternate output can I request option to have ability to downconvert DTS-HD to DTS.
Currently it only accept ac3, aac, and intact. I was think to add third option dts-hd to dts

[jdobbs]

Not most of the time it works but not on someIt works every time I've tried it -- and I'm pretty sure I've tried it more than anyone else on the planet.

[HWK]

@ Jdobbs for alternate output can I request option to have ability to downconvert DTS-HD to DTS.
Currently it only accept ac3, aac, and intact. I was think to add third option dts-hd to dts

Never mind I found it.

[thekiller]

Can you share example which doesn't work.

rebelle and the Magnificient seven

[jdobbs]

Never mind I found it.Yeah. You just have to uncheck "Keep HD Audio" in the SETUP dialog.

[thekiller]

It works every time I've tried it -- and I'm pretty sure I've tried it more than anyone else on the planet.

I did not say that it did not work all the time but on some movies at home I am obliged to do in x264 at first and then redo from x264 to hevc. By cons I just try the automatic cropping and it cuts me part of the video has the vertical

[jdobbs]

rebelle and the Magnificient sevenI'll test it on "The Magnificent Seven" later today -- but I'm pretty sure it will work. I assume you are talking about the 2016 version.

[raul124]

hi everyone, what's the different between x264 and HEVC?

[jfcarbel]

What is the default AC3 encoder used in BD Rebuilder and can and should it be replaced with something else for highest AQ?

I could only find only and older FAQ that mentioned it used Aften and that encoder had some quality issues.

[jdobbs]

What is the default AC3 encoder used in BD Rebuilder and can and should it be replaced with something else for highest AQ?

I could only find only and older FAQ that mentioned it used Aften and that encoder had some quality issues.The default is Aften. There's always someone who will say something negative about anything. I can only say that IMHO the version of Aften included with BD-RB is a very good AC3 encoder and rivals commercial encoders. The only valid criticism would be that it hasn't been in development for a long while. If someone would point out a better AC3 encoder that is either free or very inexpensive and readily available -- it wouldn't be that hard to implement an alternative.

The funny thing is that I've read comments about other options (that people say are better) that actually use the Aften library as their engine.

[thekiller]

I'll test it on "The Magnificent Seven" later today -- but I'm pretty sure it will work. I assume you are talking about the 2016 version.

Yes version 2016 with cinavia encryption

[MrVideo]

If someone would point out a better AC3 encoder that is either free or very inexpensive and readily available -- it wouldn't be that hard to implement an alternative.
I personally also use aften. It is a relatively quick encoder. That said, ffmpeg will do AC3 and well as EAC3.

[MrVideo]

Yes version 2016 with cinavia encryption
Just to clarify, Cinavia is not any kind of encryption. It is a watermark.

[jdobbs]

Just to clarify, Cinavia is not any kind of encryption. It is a watermark.Yeah, it would be better to call it "copyright protection". Or more accurately: "A way to make you pay for something, but not really be able to use it the way you want".

[LowDead]

Update to the AVCHD problem... By chance I tried today full backup BD5 with Java menus in the old Sony, and guess what... it worked! :)

I haven't checked yet, but is it done "the old way" when Java menus is located on the disc?

[jdobbs]

Update to the AVCHD problem... By chance I tried today full backup BD5 with Java menus in the old Sony, and guess what... it worked! :)

I haven't checked yet, but is it done "the old way" when Java menus is located on the disc?Yeah. My old Sony would play full backups with Java too. It was much better back before Sony "fixed" all their players.

Yes. It is done the "old way" when there is Java. There isn't a choice, since it can't do a legal AVCHD disc. It's simply a full BD backup. Just a warning, though -- there are fewer and fewer players these days that will play those kinds of discs.

[jfcarbel]

The default is Aften. There's always someone who will say something negative about anything. I can only say that IMHO the version of Aften included with BD-RB is a very good AC3 encoder and rivals commercial encoders. The only valid criticism would be that it hasn't been in development for a long while. If someone would point out a better AC3 encoder that is either free or very inexpensive and readily available -- it wouldn't be that hard to implement an alternative.

The funny thing is that I've read comments about other options (that people say are better) that actually use the Aften library as their engine.

Thanks, great to know, was just asking, don't have an opinion myself.

[Moviewatcher666]

Greetings,

Strange problem. Surprised it is happening on an older movie.

I did a full disc encode of the Blu-ray of Pirates of the Caribbean - At World's End Disk 2 Extras so that I can fit on single layer disk.

Encode successfully. Burned to rewritable disc and popped into Samsung Blu-ray player. Copy plays fine until the menu. The background video plays but the menu never displays. The background video just keeps looping and no menu.

I am attaching the log and the ini file.

Anybody got any great ideas for a quick fix for this problem?

Thanks!

Edit - Crap! Never mind. Bad rip. Ripped again and all OK.

[bebopper]

Why do you want to de-interlace 1080i material that is sourced from video cameras? If the 1080i material is from a 23.976 source, then it needs to be IVTC'd, not de-interlaced.....

Just my opinion. :D

I started to deinterlace when converting interlaced bonus features, so there would be no need to have projector/computer w/display do the conversion during playback. It's been a while, so I'd actually forgotten the disadvantages of doing so with the main program material; I'll have to be cognizant of that going forward. Thanks for the reminder.

[Lathe]

All Blu-ray players that were built in Feb 2012, and after, were required to have Cinavia detection.

Hmmm, that's a shame... I guess they really got us on this one :(

I will definitely be holding on to my BDP-83 then...

[Lathe]

hi everyone, what's the different between x264 and HEVC?

Hmmm, I think that we just might have to take this one out to the fields and beat him...


http://lathe-of-heaven.com/Beating a dead horse3.gif

[jdobbs]

hi everyone, what's the different between x264 and HEVC?That's a little complicated and beyond the scope of this thread, but I'll give you a short answer.

- HEVC is High Efficiency Video Coding (also known as H.265)
- AVC is Advanced Video Coding (also known as H.264)

X264 is a program that encodes AVC. X265 is a program that encodes HEVC.

AVC has been around for a while and is in use in many areas -- including Blu-Ray. HEVC is newer and more efficient but it isn't as widely implemented. It is especially good at giving you better pictures at low bitrates. HEVC is in-use in Blu-Ray only in players that support Ultra High Resolution (UHD) which are still pretty new and expensive.

In my testing of X264 and X265, I'm not seeing a lot of difference between the two (in terms of SSIM, a quality measuring metric) at typical HD bitrates. But that's likely because X264 has been around a while and has had a lot of tweaks that get maximum efficiency out of AVC. X265 is fairly new. Generally it should be expected that you can get an equivalent quality picture with HEVC at a lower bitrate (meaning less bandwidth for broadcast, and less required storage). Tests I've read about that were done by Netflix seem to show significant savings with HEVC.

Hope that helps.

[jdobbs]

Hmmm, I think that we just might have to take this one out to the fields and beat him... Bad Lathe! BAD! SIT!

[jdobbs]

Not most of the time it works but not on somerebelle and the Magnificient sevenI'll test it on "The Magnificent Seven" later today -- but I'm pretty sure it will work. I assume you are talking about the 2016 version.I ran "The Magnificent Seven" overnight. I plays perfectly.

[AmigaFuture]

The 1080i sources that have the repeated frame usually aren't actually 1080i. They are progressive (meaning there is no temporal difference between the two fields). So you have a 1080p source at 23.976 -- with a repeated frame thrown in to make it 29.97 that is just flagged as 1080i to make it compliant with ATSC transmission standards. That's a good thing -- because you can recover the original film source easily as progressive. It can also be true with those using pulldown flags.

Must be component capture, eh?

I just want to swear a "Ahhhh...haaa!" here because that makes sense, though I've been attempting to understand it for over 2 years now. I get a lot of this stuff, but I also very much don't!!! I so appreciate you guys that do. I can LOOK a my HD TV, something Comcast is broadcasting, or in Wal-Mart, and attempt to explain it to friends and family, but have challenges doing so. I think Lathe and I are in the same boat here, hahaha!
I'm going to try this will some stuff and see what happens.

[Lathe]

Bad Lathe! BAD! SIT!

Sorry boss... :rolleyes:

[Lathe]

I think Lathe and I are in the same boat here...

Hey...!



........................................http://lathe-of-heaven.com/I Fart in Your General Direction.gif

[gonca]

Lathe, Lathe, Lathe
Time to up your meds again.

[MrVideo]

I just want to swear a "Ahhhh...haaa!" here because that makes sense, though I've been attempting to understand it for over 2 years now. I get a lot of this stuff, but I also very much don't!!! I so appreciate you guys that do.
Jdobb is right in 29.97 fps video with repeat frame "telecine" is a lot easier to recover. I capture (from BUD satellite) a lot of videos that are repeat frame. Getting back to 23.976 is as simple as using selectevery() in the AVS script. Jdobb doesn't support it because there are a couple of requirements that just about every user will not know: 1) the repeated frame location must be constant throughout the video; 2) you need to know which frame is being repeated. In order to know the requirements and make sure that the repeat frame cadence is throughout the video, requires a video editing program, like VideoReDo, in order to go through the frames to see which one is being repeated and to make sure the cadence is intact.

Using selectevery() speeds up the recoding process since the software isn't going thru the time consuming frame doubling and field extraction to find the 2:3 pattern. The AVS script just drops a frame out of every five, resulting in the new frame rate: 23.976.

You gotta love what can be done with AVS scripts.

[jdobbs]

Jdobb is right in 29.97 fps video with repeat frame "telecine" is a lot easier to recover. I capture (from BUD satellite) a lot of videos that are repeat frame. Getting back to 23.976 is as simple as using selectevery() in the AVS script. Jdobb doesn't support it because there are a couple of requirements that just about every user will not know: 1) the repeated frame location must be constant throughout the video; 2) you need to know which frame is being repeated. In order to know the requirements and make sure that the repeat frame cadence is throughout the video, requires a video editing program, like VideoReDo, in order to go through the frames to see which one is being repeated and to make sure the cadence is intact.

Using selectevery() speeds up the recoding process since the software isn't going thru the time consuming frame doubling and field extraction to find the 2:3 pattern. The AVS script just drops a frame out of every five, resulting in the new frame rate: 23.976.

You gotta love what can be done with AVS scripts.It's easier to just use the tDecimate() which is part of TIVTC or Decimate(cycle=5) which is part of DECOMB. Either one of those will examine each group of 5 frames and find/remove the frame that is repeated. They are both included in the BD-RB tools folder. They don't do the field extraction, as that is another function withing the DLLs.

[MrVideo]

It's easier to just use the tDecimate() which is part of TIVTC or Decimate(cycle=5) which is part of DECOMB.
I haven't tried Decimate() [default cycle is 5] on these files. I'll give it a go. Thanks for the tip.

But, that said, selectevery() should be faster, as it doesn't have to spend time comparing frames. The un-selected frame is just dropped.

[Lathe]

Lathe, Lathe, Lathe
Time to up your meds again.

Where are my damn PILLS!!?



....................................... http://lathe-of-heaven.com/Cat Machine Gun.gif

[jdobbs]

Where are my damn PILLS!!?
I stole 'em. You're not the only one with social issues.

[Lathe]

I stole 'em. You're not the only one with social issues.

Well, at least I'm in good company...

[gonca]

Good Lathe

[Lathe]

Good Lathe

Dude, if I've told you ONCE, I've told you TWICE... DON'T sneak into my house and take bloody pictures of me!!! :angry:

[thekiller]

I ran "The Magnificent Seven" overnight. I plays perfectly.

Bd rebuilder takes me the version of 2h52 instead of that of 2h12
Impossible to choose the right one

[jdobbs]

Bd rebuilder takes me the version of 2h52 instead of that of 2h12
Impossible to choose the right oneYou can choose any playlist you want. Just click on MODE/OTHER MOVIE-ONLY PLAYLIST. If there are a lot of them, there are plenty of places online to look that will tell you the best one.

[thekiller]

This is what I do, I take number 355, I select it, it does a scann and it keeps the selection, weird

Well it does not matter I succeeded to do otherwise, what derrange me the most it is the autocrop that resize me the vertical

thank

[jdobbs]

This is what I do, I take number 355, I select it, it does a scann and it keeps the selection, weird

Well it does not matter I succeeded to do otherwise, what derrange me the most it is the autocrop that resize me the vertical

thankThere are certain actions that require a reset, like changing settings or editing the INI file. If you do any of those things it will default back to what it thinks is the main feature. You just have to make sure you change the playlist as the last thing you do before running the job.

[meadrocks]

Hey jdobbs, Have you had a chance to do Girl With The Dragon Tattoo? Thanks.

--Andrew

[jdobbs]

Hey jdobbs, Have you had a chance to do Girl With The Dragon Tattoo? Thanks.

--AndrewSorry, but no. Did I say I would? If so, I think I lost the bubble on it.

[meadrocks]

Sorry, but no. Did I say I would? If so, I think I lost the bubble on it.

No you didn't say you would. I posted a problem with it last week. Its actually problems with all 3 of The Girl With trilogy movies. I posted the ini files too.

[thekiller]

There are certain actions that require a reset, like changing settings or editing the INI file. If you do any of those things it will default back to what it thinks is the main feature. You just have to make sure you change the playlist as the last thing you do before running the job.






thanks, I'll try

[DarWun]

No you didn't say you would. I posted a problem with it last week. Its actually problems with all 3 of The Girl With trilogy movies. I posted the ini files too.

I think I experienced the same issue you are facing with the Millennium Trilogy "The Girl With the Dragon Tattoo" bluray. I never did figure out how to fix it. I had the same issue with the Dead Snow 2 bluray as well, which I posted about a couple of years ago. This is the link to the post which includes a description of the problem:

http://forum.doom9.org/showthread.php?p=1706160#post1706160

I mention a couple of posts later that I had the same issue with The Girl with The Dragon Tattoo.

http://forum.doom9.org/showpost.php?p=1706168&postcount=22118

[thekiller]

Hello, I am rebuilding, I have the option Automatic cropping of borders enabled, the original video made 1920x1080, bd rebuilder should release me a video of 1920x804, out it out a video of 1692x720, why Please?

thank you

[jdobbs]

Hello, I am rebuilding, I have the option Automatic cropping of borders enabled, the original video made 1920x1080, bd rebuilder should release me a video of 1920x804, out it out a video of 1692x804, why Please?

thank youThe automatic cropping filter seems to have determined that you video is only 1692 pixels wide. If it's wrong, you can always use the filter editor to manually remove the borders instead.

[thekiller]

Thank you for your reply, that it filter editor please? Must convert 1920x1080 without cropping and after passing the editor? Currently nothing is centered, it has cut to the left
This happened with the cartoon brave
On the other hand dvdfab me detect the correct resolution, but bd rebuilder still better quality

[jdobbs]

Thank you for your reply, that it filter editor please? Must convert 1920x1080 without cropping and after passing the editor? Currently nothing is centered, it has cut to the left
This happened with the cartoon brave
On the other hand dvdfab me detect the correct resolution, but bd rebuilder still better qualityThe filter editor is in the SETUP dialog. For example, in your example you could enter:

Crop(0,140,1920,800)

That would result in cropping a 1920x1080 source to 1920x800.

[thekiller]

Ok thanks and it works in MOVIE-ONLY / ALTERNATE OUTPUT mode enabled?

[ggtop]

Hi,
currently I'm struggling a bit with alternate output. My latest MP4s are missing the hard coded subs.
I use Suptitle is ticked under settings.
I examined the encoding process and saw that BDRB calls x264L-64.exe which is an indicator (AFAIK) that internal LAVF is used instead of LAVFilter + Avisynth. Therefore the AVS file is not used (which includes the subtitle line).
But I do not use "Use X264's internal..." I have "Use DirectShow.." selected.
If I enter an AVS filter through settings Dialog such as "Version()" I see BDRB switches to Avisynth processing. Weird...

Any suggestions?

Edit: Maybe I could add a dummy value as a filter which forces Avisynth and does not harm encoding Performance.

ggtop

[ggtop]

I think I experienced the same issue you are facing with the Millennium Trilogy "The Girl With the Dragon Tattoo" bluray. I never did figure out how to fix it. I had the same issue with the Dead Snow 2 bluray as well, which I posted about a couple of years ago. This is the link to the post which includes a description of the problem:

http://forum.doom9.org/showthread.php?p=1706160#post1706160

I mention a couple of posts later that I had the same issue with The Girl with The Dragon Tattoo.


Hi DarWun,

you are writing here:
http://forum.doom9.org/showpost.php?p=1706168&postcount=22118

the movie has a short studio logo (Yellowbird).
I suggest you demux that m2ts with TSMUXER and see if it has 0 (zero) KB audio tracks. Especially the track you have chosen for output.
I experienced the same issue on at least one other movie. If that's the case the Audio is delayed by the length of that clip (or maybe more if there are other clips before the movie starts). These empty dts tracks get somehow truncated by TSMUXER (maybe because it violates the Standard). For that reason BDRB cannot circumvent anything.

In order to fix it you can add silence to your Audio track using eac3to and remux the files with MP4Box which is shipped with BDRB. I could advise you to do so if you wish but I suggest you have a look first into your source.

ggtop

[jdobbs]

Ok thanks and it works in MOVIE-ONLY / ALTERNATE OUTPUT mode enabled?Yes. In fact that's the only time you would use that particular filter -- as doing it in a BD type backup would make the output illegal and possibly cause the disc to fail.

[jdobbs]

Hi,
currently I'm struggling a bit with alternate output. My latest MP4s are missing the hard coded subs.
I use Suptitle is ticked under settings.
I examined the encoding process and saw that BDRB calls x264L-64.exe which is an indicator (AFAIK) that internal LAVF is used instead of LAVFilter + Avisynth. Therefore the AVS file is not used (which includes the subtitle line).
But I do not use "Use X264's internal..." I have "Use DirectShow.." selected.
If I enter an AVS filter through settings Dialog such as "Version()" I see BDRB switches to Avisynth processing. Weird...

Any suggestions?

Edit: Maybe I could add a dummy value as a filter which forces Avisynth and does not harm encoding Performance.

ggtopI'll look at it and see how that is possible. But, I'm surprised -- as BD-RB has a preference for Directshow. There are things that force Directshow when you have "Use X264's..." selected -- but none that go the other way.

[thekiller]

Yes. In fact that's the only time you would use that particular filter -- as doing it in a BD type backup would make the output illegal and possibly cause the disc to fail.

I have to add the line Crop (0,136,1920,804) in view / edit files that is it? As well as?

[[Options]
VERSION=0.50.0.23
ENCODER=0
MODE=3
ENCODE_QUALITY=3
ONEPASS_ENCODING=0
AUTO_QUALITY=0
AUDIO_TO_KEEP=fra;fre;
SUBS_TO_KEEP=fra;fre;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=1
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=0
AUDIO_DRC=0
DECODER=0
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=1
BDMV_CERT_ONLY=1
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=3000
TARGET_SIZE=47366
MOVIEONLY_TYPE=11
ALTCRF=20
ALT_TARGET=1900
ALT_CRF_TARGET=2500
ALTMETHOD=3
ALTAUTOCROP=0
AUTO_BURN=2
QUICK_EXTRAS=0
VERBOSE_STATUS=1
AVSFilter01=crop(0,136,1920,804)
[Paths]
SOURCE_PATH=V:\IMPORTS\BRAVE\
WORKING_PATH=V:\

[jdobbs]

@thekiller

No. That's not how you do it.

1. You go to the SETUP dialog (from the Settings menu).
2. Then click on "Use AVS Filters during encoding".
3. Within the editor dialog, just at the text: Crop(0,140,1920,800)
4. Save it.

[gamete]

if i install LAV instead of FFDSHOW + Haali ....the bdrebuilder setting changes?



Thanks

[ggtop]

I'll look at it and see how that is possible. But, I'm surprised -- as BD-RB has a preference for Directshow. There are things that force Directshow when you have "Use X264's..." selected -- but none that go the other way.

Hi jdobbs,
just tested on another machine. Same there. X264L-64.exe is called. I even started with a new ini file.
Using a playlist containing a 30 min extra (because demuxing is quicker) everything is normal. x264.exe is called and feeded with the AVS script.
Seems it only happens with the main movie playlist... Movie is Sherlock Holmes 2 by the way. The one with Robert Downey Jr.
Looking into some INF files I still had and they are all saying "USE_LAVF=0". Is that correct? (only a guess)

ggtop

[jdobbs]

Hi jdobbs,
just tested on another machine. Same there. X264L-64.exe is called. I even started with a new ini file.
Using a playlist containing a 30 min extra (because demuxing is quicker) everything is normal. x264.exe is called and feeded with the AVS script.
Seems it only happens with the main movie playlist... Movie is Sherlock Holmes 2 by the way. The one with Robert Downey Jr.
Looking into some INF files I still had and they are all saying "USE_LAVF=0". Is that correct? (only a guess)

ggtopIt must have something to do with my adding X264L to correct for the slow decoding of the newer versions. I'll see what I can find.

[ggtop]

It must have something to do with my adding X264L to correct for the slow decoding of the newer versions. I'll see what I can find.

I see this in version 0.50.20 changelog:
December 5th, 2016 - v0.50.20
- Updated code so that X264/LAVF can also be used for ALTERNATE encoding. In previous releases ALTERNATE encoding forced the use of DirectshowSource (for resizing).
Now X264's internal resizing filters are used when X264/LAVF is selected. This reduces BD-RB's dependence on LAVF or FFDSHOW.

From my ini file: DECODER=0

ggtop

[LoneSwan]

Quickplay has option for "finding" the original BD menu background video and using that instead of a static image. My question is: Why not let user select the correct *.m2ts file to use from the BDMV\Stream folder?

I frequently run into this issue when trying to re-author BD's, especially problem ones like Mockingjay 2(Hunger Games). This BD uses playlist obfuscation, which leads to multiple issues using BD Rebuilder. Using TSMuxer I create a new BD structure by selecting the correct playlist and de-selecting unwanted audio and subtitle streams. It is good to go at this point: under 25GB so will fit on a single disc. However, it would be really nice to add an opening "Quickplay" menu using the background video from the original disc.

Read earlier posts: there is a problem where BD Rebuilder will always re-encode. This is such a case. Would be great if BD Rebuilder had option to really _FORCE No Encode_ for testing purposes. I tried multiple tricks attempting to get BD Rebuilder to "find" that background video. I know the correct *.m2ts and the *.mpls; can make a guess on the matching *.clpi... but my knowledge on BD structure is minimal.

Is there a way to copy the necessary files to the structure(BDMV folder) to help BD Rebuilder "find" the menu background video... if implementing a direct choice under Quickplay options is too troublesome?

I have found numerous work-arounds to create nice Quickplay menus, and would like to add a "tutorial" post to this thread to share tips. The _FORCE No Encode_ option (for testing) and (somehow?) choose original background video for Quickplay menu, would be a big help.

Thanks JD for your continued efforts!!!

Walker (in Virginia's Northern Neck)

[ggtop]

Hi LoneSwan,

from Hiddenopts.txt:
This file contains descriptions of settings that can be added to the BDREBUILDER.INI file (via the Config/INI
editor) that may change the handling of files during conversion, reencode, and rebuild.

[Options]
FORCE_NOENCODE=n n = 0/1 - if set to 1, BD-RB will always use original video (sizing will not be checked)

You could also set your Output size to BD-50 which would prevent re-encoding as long as your output type is compliant.

BTW I had no problems with MockingJay 2. Prerequisite is of course it is decrypted properly.

ggtop

[MrVideo]

v0.50.20

Bug selecting BLANK.AC3 from BDRB install directory.

When I go down the path: C:\Program Files (x86)\BD.... to select the BLANK.AC3 file, all that shows up is: C:\Program Files

The rest of the path is missing. To get around the issue, I just copied the AC3 file into the same directory as the background menu.

Unrelated issue:

What is the darkest black that can be used for the active color? I discovered that selecting 0x000000, results in default green being used. I'm down to 0x202020. Thinking about it, you need some margin to be able to subdue it when the menu item isn't active, hence the not liking 0x000000.

[jdobbs]

v0.50.20

Bug selecting BLANK.AC3 from BDRB install directory.

When I go down the path: C:\Program Files (x86)\BD.... to select the BLANK.AC3 file, all that shows up is: C:\Program Files

The rest of the path is missing. To get around the issue, I just copied the AC3 file into the same directory as the background menu.

Unrelated issue:

What is the darkest black that can be used for the active color? I discovered that selecting 0x000000, results in default green being used. I'm down to 0x202020. Thinking about it, you need some margin to be able to subdue it when the menu item isn't active, hence the not liking 0x000000. I don't think I understand your first question. But, as the instructions say, I don't recommend installing in the "C:\Program Files" folder -- because of virtualization.

The MENU_ACTIVE_COLOR value can be anything greater than zero. So 0x010101 would be the darkest evenly distributed color. Of course you could use 0x000001 -- but that's not even. The reason is because 0 (which is the same as no setting) indicates the default color.

[MrVideo]

I don't think I understand your first question. But, as the instructions say, I don't recommend installing in the "C:\Program Files" folder -- because of virtualization.
I'm on XP-64. I do not believe that virtualization exists. Even if it does, I have no issues with other programs finding things via that path.

The long path to the BLANK.AC3 file has "(x86)" as part of it. I'm guessing that your program doesn't like the part of the path containing the ( ) characters, therefore truncating the rest of the path from those characters onward. Just a WAG.

Try installing to C:\jdobbs (x86)\BDRebuilder\... and then see if you can get the program to point to the BLANK.AC3 file that is in that path.
The MENU_ACTIVE_COLOR value can be anything greater than zero. So 0x010101 would be the darkest evenly distributed color. Of course you could use 0x000001 -- but that's not even. The reason is because 0 (which is the same as no setting) indicates the default color.
Who would guess that a legal color would indicate no color. :confused:
To me, MENU_ACTIVE_COLOR="" or MENU_ACTIVE_COLOR= is equal to no setting. Blame it on my Linux scripting programming where a variable such as this is not binary True/False (1/0), so anything would be a value. :D

IIRC, I did try 0x010101 and the text was white.

[jdobbs]

I'm on XP-64. I do not believe that virtualization exists. Even if it does, I have no issues with other programs finding things via that path. The problem with virtualization is that BD-RB uses an INI path in the same path as the executable. The O/S may virtualize any writes to the INI -- and programmatic changes are physically written to a different (hidden) path. So you could, for example, go into the INI file and attempt to make a change -- and it won't take effect because the real INI is somewhere else. This is one of those things Microsoft introduced starting with Vista that is nothing more than a headache. They are trying to make it more secure -- but it really doesn't.

The solution is for me to change my code to use the registry instead of an INI -- but I just don't feel like putting that much effort into it.

[MrVideo]

OK, so I do not have virtualization. Even if I did, it has nothing to do with this problem. I think you may be misunderstanding the issue.

Install BDRB into the normal M$ location on a 64-bit system, where BDRB will end up in C:\Program Files (x86). Start BDRB. Then do Settings->Import/Quick-Play Settings. Now browse (audio) to the location of the installed BLANK.AC3 audio file. Select the BLANK.AC3 file and then click on Open. The path shown will now only be C:\Program Files. All of this before anything is ever attempted to be written to any INI file. Again, I believe that BDRB doesn't like any path with ( ) characters.

I agree with not putting this stuff in the registry. Makes it very difficult to look thru the parameters.

[jdobbs]

Well... actually it does have something to do with the problem. If you'd followed the instructions you wouldn't be in that folder and you wouldn't be having that problem.

Also, I just tried browsing from within that folder while choosing the .AC3 file for the menu, and had no issues. Are you sure you have privileges?

[MrVideo]

Well... actually it does have something to do with the problem. If you'd followed the instructions you wouldn't be in that folder and you wouldn't be having that problem.
I seriously doubt that virtualization is an issue, since XP-64 doesn't have it. IMHO, no user should be forced to not use the default M$ install path. While virtualization is an issue for M$ after my version, users do not have to directly edit the INI file, since you have full editing of the INI file in the program.
Also, I just tried browsing from within that folder while choosing the .AC3 file for the menu, and had no issues. Are you sure you have privileges?
I am the only user on my systems, having full admin rights. Never an issue installing files, or access to anything, anywhere on the system.

So, I did some more testing. I copied the blankclip directory, and its contents to the same path you searched. No problem with that path. So, I copied BLANK.AC3 to the BD_Rebuilder and Tools directories. There was no problem when searching those two locations. The path it does not like is: C:\Program Files (x86)\BD_Rebuilder\Tools\blankclip\BLANK.AC3. So, I copied BLANK.AC3 into the dvdauthor directory and that path is not liked either.

Lastly I created a C:\jdobbs\jdobbs path and copied the BD_Rebuilder directory, and its contents into it. Searching that longer path worked.

I have no clue as to why BDRB doesn't like any directory under Tools when the path is C:\Program Files (x86)\BD_Rebuilder\Tools.

[gonca]

When I was on win7 I had no problems with Program Files (x86)
Just tried on my win10 machine and I can navigate to the blank.ac3 file just fine. In fact I moved BD_RB to Program Files (x86) temporarily to test

[jdobbs]

I seriously doubt that virtualization is an issue, since XP-64 doesn't have it. IMHO, no user should be forced to not use the default M$ install path. While virtualization is an issue for M$ after my version, users do not have to directly edit the INI file, since you have full editing of the INI file in the program.

I am the only user on my systems, having full admin rights. Never an issue installing files, or access to anything, anywhere on the system.

So, I did some more testing. I copied the blankclip directory, and its contents to the same path you searched. No problem with that path. So, I copied BLANK.AC3 to the BD_Rebuilder and Tools directories. There was no problem when searching those two locations. The path it does not like is: C:\Program Files (x86)\BD_Rebuilder\Tools\blankclip\BLANK.AC3. So, I copied BLANK.AC3 into the dvdauthor directory and that path is not liked either.

Lastly I created a C:\jdobbs\jdobbs path and copied the BD_Rebuilder directory, and its contents into it. Searching that longer path worked.

I have no clue as to why BDRB doesn't like any directory under Tools when the path is C:\Program Files (x86)\BD_Rebuilder\Tools.Ok. I see it now. The value is actually being collected and stored correctly, but, because of it's length it is wrapping to another line that can't be seen in that text window. I'm not sure whether there is anything I can do about that, but I'll try. It's a Microsoft control that I'm just referencing. Interesting, as it has a "Wrap" attribute that I have turned off.

[MrVideo]

I was thinking that length had something to do with it, but not the length of characters. Why? Because in the menu background result box, the numbers of characters is larger than the available space and the characters to the right are just truncated. No wrapping. Then again, there are no spaces in that line in which the line can be cut to wrap.

I just did a test with the menu background in that I was able to change a "-" to a space and sure enough, it wrapped.

The bug might be with M$ if it has a no-wrap attribute and you have it enabled, but it wraps anyway. If it is still bad with Win10, it has been around for a very long time.

Can you make that dialog box user resizable so that a user can make it wider, allowing for the text to fit and not wrap?

[Lathe]

I might have mentioned this a while back, I don't remember, but is it possible to be able to use more characters in the titles of the Quick Play menu? Many times I use it to put the Xtras, and usually the titles of each of the xtras is cut off (looks like about maybe 36 characters total including spaces) Any chance of being able to have longer titles in the Quick Play menu. They currently only take up about 1/2 the length of the screen.

Thanks!

[jdobbs]

I might have mentioned this a while back, I don't remember, but is it possible to be able to use more characters in the titles of the Quick Play menu? Many times I use it to put the Xtras, and usually the titles of each of the xtras is cut off (looks like about maybe 36 characters total including spaces) Any chance of being able to have longer titles in the Quick Play menu. They currently only take up about 1/2 the length of the screen.

Thanks!The number of allowed characters is variable. It is calculated based upon the font, the graphic width of the text to be displayed, and the size of the screen area dedicated to each title. So there really isn't a way to simply add characters. The actual space allocated to each title is a lot more complicated -- based upon the number of titles and the number of columns needed, and I'm not willing, at the moment, to go through all that again. There are a lot of variables.

What is possible is that I could add a hidden option that reduces the font size by some specified amount. For example, if you set a value of .75, the size of the font would be reduced to 3/4 of the default. It would give you more horizontal space. It may not be exact, since most fonts don't use fixed spacing. But it would make it more controllable. The downside is that when you reduce the font size, both the vertical and horizontal size is affected.

[Lathe]

The number of allowed characters is variable. It is calculated based upon the font, the graphic width of the text to be displayed, and the size of the screen area dedicated to each title. So there really isn't a way to simply add characters. The actual space allocated to each title is a lot more complicated -- based upon the number of titles and the number of columns needed, and I'm not willing, at the moment, to go through all that again. There are a lot of variables.

What is possible is that I could add a hidden option that reduces the font size by some specified amount. For example, if you set a value of .75, the size of the font would be reduced to 3/4 of the default. It would give you more horizontal space. It may not be exact, since most fonts don't use fixed spacing. But it would make it more controllable. The downside is that when you reduce the font size, both the vertical and horizontal size is affected.

Thanks JD! No, don't sweat it; for stuff like this, I truly do not know what exactly goes into it, so it's good you explain that it is indeed more involved than one may think. If the hidden option is no big deal for you, then sure, that would be interesting to try. In the meantime (like my posts and EVERYTHING else) this will give me an opportunity to refine my 'skills' at succinctness and brevity..

Now, to expand upon this... :cool:

[MrVideo]

I have some MKV H.264 videos that I want to put on a couple of discs. First, I wasn't sure if the H.264 video would play in the Blu-ray player, untouched, so I created a test disc with a single video. When I put the disc into the player, the video was fine, but there wasn't any audio. Going back to the computer, I looked at the M2TS file, and sure enough, no audio. Then I noticed that when the BDRB job finished, it only showed the video file. No explanation as to why BDRB rejected the audio stream.

The audio is E-AC3 5.1. MediaInfo and txMuxer both claim it is 640 kbps, while VideoReDo says it is 1280 kbps. E-AC3 is a legit Blu-ray audio format, so why would BDRB reject it?

I can supply a 30 sec segment of the video for downloading from my server.

[Lathe]

I have some MKV H.264 videos that I want to put on a couple of discs. First, I wasn't sure if the H.264 video would play in the Blu-ray player, untouched, so I created a test disc with a single video. When I put the disc into the player, the video was fine, but there wasn't any audio. Going back to the computer, I looked at the M2TS file, and sure enough, no audio. Then I noticed that when the BDRB job finished, it only showed the video file. No explanation as to why BDRB rejected the audio stream.

The audio is E-AC3 5.1. MediaInfo and txMuxer both claim it is 640 kbps, while VideoReDo says it is 1280 kbps. E-AC3 is a legit Blu-ray audio format, so why would BDRB reject it?

I can supply a 30 sec segment of the video for downloading from my server.

Yeah, my OPPO will not play MKV files with E-AC3 audio (Dolby+) I always have to use UsEac3to to covert it to either AC3 or DTS depending on the bit rate. But, I have no idea why BDRB won't process it; I don't think I've ever run a file through it with that codec...

[MrVideo]

Yeah, my OPPO will not play MKV files with E-AC3 audio (Dolby+) I always have to use UsEac3to to covert it to either AC3 or DTS depending on the bit rate. But, I have no idea why BDRB won't process it; I don't think I've ever run a file through it with that codec...
My Samsung will play any audio codec I can throw at it, either via Blu-ray or MKV. But, in this case the Blu-ray player doesn't decode the audio, as it is passed to the amp via HDMI, which will handle all of the DTS and Dolby codecs (only that the core of ATMOS is handled). It will even handle AAC.

[jdobbs]

I have some MKV H.264 videos that I want to put on a couple of discs. First, I wasn't sure if the H.264 video would play in the Blu-ray player, untouched, so I created a test disc with a single video. When I put the disc into the player, the video was fine, but there wasn't any audio. Going back to the computer, I looked at the M2TS file, and sure enough, no audio. Then I noticed that when the BDRB job finished, it only showed the video file. No explanation as to why BDRB rejected the audio stream.

The audio is E-AC3 5.1. MediaInfo and txMuxer both claim it is 640 kbps, while VideoReDo says it is 1280 kbps. E-AC3 is a legit Blu-ray audio format, so why would BDRB reject it?

I can supply a 30 sec segment of the video for downloading from my server.Please provide the segment so I can see what BD-RB sees when trying to import it.

[jdobbs]

Yeah, my OPPO will not play MKV files with E-AC3 audio (Dolby+) I always have to use UsEac3to to covert it to either AC3 or DTS depending on the bit rate. But, I have no idea why BDRB won't process it; I don't think I've ever run a file through it with that codec...I'll have to go back and look -- but if I remember correctly, support for E-AC3 is optional -- and, I believe it is required to have an AC3 core to be compliant.

[Lathe]

I'll have to go back and look -- but if I remember correctly, support for E-AC3 is optional -- and, I believe it is required to have an AC3 core to be compliant.

Ah... the ol' 'core' thing, like TrueHD. Makes sense...

[Lathe]

BTW, just a quickie (my usual style...) Just out of curiosity, and you know that I am FULL of it (curiosity, that is...) If I take a Blu-ray that is just, say, maybe a couple of Gigs larger than a BD25 and I'm doing a full backup with faster encoding for Xtras (set at CRF-24) Will BDRB simply JUST re-encode the Xtras since that will likely make enough room to leave the movie file untouched, or will it simply process everything equally because it determines that the entire disc is too big?

In other words, will it necessarily re-encode the movie file too, even though after encoding the Xtras there would really be no need for it?

[Lathe]

Hmmm, I may just now have the answer. I was processing 'FINAL DESTINATION' and the full disc is about 23.6 Gigs, about .3 or .4 Gigs too large to fit on a BD25. BDRB did indeed just re-encode the Xtras and left the movie file untouched. I don't know if it will ALWAYS do that and if that is standard behaviour, but that's what it did in this case.

[MrVideo]

I'll have to go back and look -- but if I remember correctly, support for E-AC3 is optional -- and, I believe it is required to have an AC3 core to be compliant.
Therein may lie the answer. It seems that no encoder is creating an AC3 core. Even Amazon isn't adding a core. I personally use ffmpeg and it does not add a core.

How about accepting an E-AC3 stream even if it doesn't have a core and maybe add a little warning to the log file about the AC3 core missing and that may result in no audio.

I know my amp will play it just fine. I do so from my NAS box, using Kodi 17 to my amp via HDMI.

[gonca]

@Lathe
and you know that I am FULL of it
We know:p

[Lathe]

@Lathe

We know:p


http://lathe-of-heaven.com/Suspicious Cat.gif

[Sharc]

^^^^^
:goodpost:

[MrVideo]

Is a sample still desired, even though we know that it doesn't have a core?

[ggtop]

It must have something to do with my adding X264L to correct for the slow decoding of the newer versions. I'll see what I can find.

Hi jdobbs,

is there something I can help with? Such as ini or inf files or something else...I will surely do.

ggtop

[flash]

Been using BD rebuilder for years, only just realized that you can use it to also covert to DVD :) The only thing I would like to see is some sort of quality meter in %. So you can see how its going to fit onto BD25.
Can you donate through Paypal also ?

[Sharc]

Been using BD rebuilder for years, only just realized that you can use it to also covert to DVD :) The only thing I would like to see is some sort of quality meter in %. So you can see how its going to fit onto BD25.
Can you donate through Paypal also ?
It's not unusual that a DVD created from the BD source by BD-RB looks better than the original DVD from the shop.

No, you can't donate via Paypal anymore. It's their insane decision. But you can always donate by means of the amazon gift card.

[jdobbs]

It's not unusual that a DVD created from the BD source by BD-RB looks better than the original DVD from the shopThat's been my experience as well. I'm guessing it's because X264 just does a much better job with the same bitrate than whatever encoder they use.

[jdobbs]

Hi jdobbs,

is there something I can help with? Such as ini or inf files or something else...I will surely do.

ggtopI found it and fixed it for the next release. It wasn't checking for the use of SupTitle as it should. It was switching to X264L, I'm guessing, because of its preference with an ATCDelta flag. I'd forgotten that happens. It was the only way I could find where it is used when DirectshowSource is selected.

[MrVideo]

That's been my experience as well. I'm guessing it's because X264 just does a much better job with the same bitrate than whatever encoder they use.
But, DVDs are MPEG-2, not H.264.

[HWK]

Can you donate through Paypal also ?

Paypal stopped doing business with jdobbs in first place.

[Sharc]

But, DVDs are MPEG-2, not H.264.

Yes, but still true even with HCenc.

[MrVideo]

I guess the sample (http://vidiot.com/Sample_EAC3_video.mkv) is desired.

[ggtop]

I found it and fixed it for the next release...

Thank you. Looking forward for the release then.
ggtop

[jdobbs]

But, DVDs are MPEG-2, not H.264.Uhh... yep... HCEncoder then... :D

[sirig]

Hello dear BD-Rebuilder Users!
Must admit I'm new to BD-Rebuilder. I have backed just 2 BD's with BD-R till yet and with my third attempt I ran into problems. :(
Have tried to backup the Doctor Strange 2D+3D BD's but with half success.
2D without any problems, BD-R has made great job but with the 3D version the software has some issues.
This is the error message that I'm get:
- Error in attempt to multiplex: MUX_00800.meta
- Can't open file: F:\DOCTOR_STRANGE_3D_IMI\WORKFILES\00801.track_4114.mvc
[07:41:52] - Failed to build structure, aborted
Has someone already tried to backup the 3D version and got the same error message?

[03. 15. 17] BD Rebuilder v0.50.23
[07:24:47] Source: DOCTOR_STRANGE_3D
- Input BD size: 41,45 GB
- Approximate total content: [02:08:39.502]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Very Fast), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[07:24:47] PHASE ONE, Encoding
- [07:24:47] Processing: VID_00006 (1 of 3)
- [07:24:47] Extracting A/V streams [VID_00006]
- [07:24:55] Reencoding video [VID_00006]
- [07:24:55] Keeping original video (no reencode)
- [07:24:55] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [07:24:55] Multiplexing M2TS
- [07:25:00] Processing: VID_00007 (2 of 3)
- [07:25:00] Extracting A/V streams [VID_00007]
- [07:25:05] Reencoding video [VID_00007]
- [07:25:05] Keeping original video (no reencode)
- [07:25:05] Processing audio tracks
- [07:25:05] Multiplexing M2TS
- [07:25:08] Scanning for 3D CLPI info...
- [07:25:09] Processing: VID_00800 (3 of 3)
- [07:25:09] Extracting A/V streams [VID_00800]
- [07:41:48] Reencoding video [VID_00800]
- [07:41:48] Keeping original video (no reencode)
- [07:41:48] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (eng): Keeping original audio
- Track 4354 (fra): Keeping original audio
- Track 4355 (spa): Keeping original audio
- [07:41:48] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00800.meta
- Can't open file: F:\DOCTOR_STRANGE_3D_IMI\WORKFILES\00801.track_4114.mvc
[07:41:52] - Failed to build structure, aborted


[Status]
LABEL=DOCTOR_STRANGE_3D
VERSION=v0.50.23
SOURCE_SIZE=44507341122
SOURCE_VIDEO_SIZE=43134898176
TARGET_SIZE=49666850816
REDUCTION=1.11961335049287
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=all
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=all
BACKUP_MODE=0
MOVIEONLY_TYPE=0
USE_LAVF=-1
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
QUICK=0
ENCODE_STEP=4
COMPLETED=2
[00006]
USE_ORIGINAL=1
AUDIO=1
PGS=
APULLDOWN=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=143851649
NSTART=27000000
NEND=28820568
NSIZE=123942912
FLINK=0
MLINK=0
[00007]
USE_ORIGINAL=1
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=337066
NSTART=27000000
NEND=27011261
NSIZE=12288
FLINK=0
MLINK=0
[00800]
USE_ORIGINAL=1
AUDIO=1111
PGS=11100
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=48150219154


[03. 15. 17] Checking System Settings
- BD-Rebuilder v0.50.23
- Windows Version: 6.2 [9200]
- Working Path Free Space: 251,68GB
- AVISYNTH Version: 2.6.0.6, Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[03. 15. 17] Systems Settings Check complete

[worknstiff]

@ sirig; RE: Can't open file: F:\DOCTOR_STRANGE_3D_IMI\WORKFILES\00801.track_4114.mvc
[07:41:52] - Failed to build structure, aborted
Has someone already tried to backup the 3D version and got the same error message?

I did Doctor Strange 3D and had no problems. I was wondering how you were processing the original disk. Did you try to process it from the blue ray disk itself in real time? I all ways create an image on the hardrive and then use Virtual Clone Drive to open it. Sometime the disk errors out because of all the seeking and decryption taking place. Or at least that's what I think happens, especially if you have an older machine doing the processing. Either that or a bad disk, rip or even a failing drive. Good luck sirig.

[ggtop]

Hi all,

I experienced an issue with one of my BDs. It's Tango & Cash encoded with VC-1. My MP4 encode suffered from audio out of sync. After some investigation I noticed a glitch at around 6:00 into the movie which makes the AVS file (and the result) playback at double speed for around 20 sec (with DirectShow). I decided to use another frameserver so I bought a license for DGDecNV (didn't think about FRIM) and the problems were gone. As I don't have a NVIDIA Card on my main machine I wondered if I can also use DGDecIM there. I searched the whole thread, did find something about some hidden options like

DGDECIM_SW_DECODE

[PATH]
DGIndexIM=...DGIndexIM.exe
DGDecIM=...DGDecodeIM.dll

but they do not seem to work. Is DecIM (still) supported or shall I use FRIM Decoding in SW mode?

Thanks

ggtop

[jdobbs]

Anybody else experiencing issues with e-mail delivery of notifications related to new posts? Until today I don't think I've gotten any in over a week at least -- even though there have been plenty of posts.

[jdobbs]

Hi all,

I experienced an issue with one of my BDs. It's Tango & Cash encoded with VC-1. My MP4 encode suffered from audio out of sync. After some investigation I noticed a glitch at around 6:00 into the movie which makes the AVS file (and the result) playback at double speed for around 20 sec (with DirectShow). I decided to use another frameserver so I bought a license for DGDecNV (didn't think about FRIM) and the problems were gone. As I don't have a NVIDIA Card on my main machine I wondered if I can also use DGDecIM there. I searched the whole thread, did find something about some hidden options like

DGDECIM_SW_DECODE

[PATH]
DGIndexIM=...DGIndexIM.exe
DGDecIM=...DGDecodeIM.dll

but they do not seem to work. Is DecIM (still) supported or shall I use FRIM Decoding in SW mode?

Thanks

ggtopIt should still be supported -- but it's more-or-less undocumented. You'd need to add DGDECIM=1 to your INI as well.

[ggtop]

It should still be supported -- but it's more-or-less undocumented. You'd need to add DGDECIM=1 to your INI as well.

Thank you. That line did it :-)
Maybe you could add this info to hiddenopts.

Do you and of course all others reading this have any experience if DecIM should be avoided in HW mode? I saw my framerates jumping from 80 to 120 fps, but I don't want to risk bad decoding...

ggtop

[gonca]

@jdobbs
Check your PMs, please

[ggtop]

Anybody else experiencing issues with e-mail delivery of notifications related to new posts? Until today I don't think I've gotten any in over a week at least -- even though there have been plenty of posts.

Not for me. Received a mail after you posted and the same for gonca's reply.

[jdobbs]

Not for me. Received a mail after you posted and the same for gonca's reply.It's started to work again for me too. Just a temporary glitch, I guess.

[MrVideo]

@jdobbs:

Any update on the eac3 issue? Did you get the sample OK?

[jdobbs]

@jdobbs:

Any update on the eac3 issue? Did you get the sample OK?Yes, I got the sample. No, I haven't worked on it yet.

[MrVideo]

Here's a strange bug, which does not affect the result...

I just did a build which contained four 42 min episodes (H.264) and 16 ~5 min special features (MPEG-2). When it was done with the menu building, it only showed one stream (VID_00002), which is one of the four episodes. The total length was 42:48, which is way off the mark, but right for the only stream listed.

[ggtop]

Here's a strange bug, which does not affect the result...

Did you choose "Movie & Menus" instead of "Full backup" perhaps? Log file could be helpful.


ggtop

[MrVideo]

Did you choose "Movie & Menus" instead of "Full backup" perhaps? Log file could be helpful.
Nope, "Full Backup," even though I stop at the point right after the menus are created. I then burn the disc at that point. Nothing exciting in the log. The job runs as expected and produces the expected results.

I just started BDRB again and low and behold, all of the streams are now listed from the last run.

Like I said, something strange going on.

[MrVideo]

Yes, I got the sample. No, I haven't worked on it yet.
I look forward to your results, as I have a boatload more files that have DD+ audio.

[MrVideo]

When setting up your customized menus, have you ever run into the issue as to what values to use for the X/Y placement of the text? Needless to say, I have. So, I created some grids on 100 pixel spacing. One with white lines and one with black lines. Both include text to indicate the X/Y location and both are on transparent backgrounds. The ZIP file (http://vidiot.com/HD-grid-templates.zip) contains both AI (Adobe Illustrator) and PNG versions of both grids. The AI version can be loaded by Adobe Illustrator or PhotoShop. Or you can use your favorite image editor that supports layers. You can easily make your menu background image and overlay it with one of the grids. You can then save the necessary JPG file. You can then burn a test disc on BD-RE media. Once you have the layout you want, you can save a new JPG file without the grid.

Enjoy.

[LoneSwan]

Is there a way to specify a menu background video? BD Rebuilder ini has the parameter: MENU_BACKGROUND=
I don't understand why this is limited to an image file, since BD Rebuilder can (and does, sometimes) find and use an original background video when creating the Quick Play menu.

I'm trying to use BDedit to "fix" the 00002.mpls and associated 99001.clpi BMDV folder support files... but not quite getting there. Could really use a bump in the right direction. ;)

[jdobbs]

Is there a way to specify a menu background video? BD Rebuilder ini has the parameter: MENU_BACKGROUND=
I don't understand why this is limited to an image file, since BD Rebuilder can (and does, sometimes) find and use an original background video when creating the Quick Play menu.

I'm trying to use BDedit to "fix" the 00002.mpls and associated 99001.clpi BMDV folder support files... but not quite getting there. Could really use a bump in the right direction. ;)I plan to add video capability as well, but haven't gotten around to it.

[Yordan5]

The heart of my current PC setup is Intel Core i7-4770. BD-RB now takes around 7 hours (High Quality VBR) to shrink a BD movie. Just wondered if the new AMD Ryzen 1800X (8 cores) processessor (and the rumored 16 cores one) would be able to halve the processing time?

[jdobbs]

The heart of my current PC setup is Intel Core i7-4770. BD-RB now takes around 7 hours (High Quality VBR) to shrink a BD movie. Just wondered if the new AMD Ryzen 1800X (8 cores) processessor (and the rumored 16 cores one) would be able to halve the processing time?Can't say about the Ryzen... but 7 hours seems like a lot. I run an AMD FX8350, which should be inferior to your i7, and it takes about half that long. Of course it would depend a lot on the particular disc and total length of the encoding... but 7 hrs still seems long.

[Rodger]

@jdobbs...your FX8350 is hardly faster than a i7-3770.
i7-4770 has about 10% more power than the i7-3770. That should make it a little faster than the FX8350.
Ryzen is a completely different thing. It has a lot more horsepower per clock and it has it strength offsides from gaming. Encoding should be one of the best things to run on Ryzen. While gaming my i7-7700K is clearly the better choice, but it stands no chance while encoding.

I´d recommend the x1700 over the x1800. The price gap is too big for the little more performance I think.
And I strongly recommend x370 boards if you have plans for many m.2 SSDs aka Top speed storage.

[jdobbs]

@jdobbs...your FX8350 is hardly faster than a i7-3770.
i7-4770 has about 10% more power than the i7-3770. That should make it a little faster than the FX8350.
Ryzen is a completely different thing. It has a lot more horsepower per clock and it has it strength offsides from gaming. Encoding should be one of the best things to run on Ryzen. While gaming my i7-7700K is clearly the better choice, but it stands no chance while encoding.

I´d recommend the x1700 over the x1800. The price gap is too big for the little more performance I think.
And I strongly recommend x370 boards if you have plans for many m.2 SSDs aka Top speed storage.Well... I guess you missed my point completely. Maybe you should re-read my post. Yes, his i7 should be significantly faster than the FX8350. But, based on his post, it isn't. So the point is: he may have some other issue if it's taking that long to do a disc.

[Rodger]

naah....just a vocabulary error on my side. Sorry for that.
"inferior" is worse not better :o

7 hours is really a long run...I guess he is using some extreme settings with a doubtful result as I find.
Using the preset with maximum quality in BD Rebuilder should be the way to go for him.

[Yordan5]

I would very much appreciate suggestions on what settings I should be using to speed up (without noticeable loss of quality) the processing time of BD movies. I also have licence for dgdecnv2052 and Nvidia card if that helps. Less than a year ago it would take approx 3.5 hours to process a movie with two pass, Highest Quality, but after the changes in x264 it now takes much, much longer. Should I be installing LAV Directshow Filters, FFDSHOW or Haali Matroska Splitter and how to setup BD-RB to reduce the encoding times?

[jdobbs]

I would very much appreciate suggestions on what settings I should be using to speed up (without noticeable loss of quality) the processing time of BD movies. I also have licence for dgdecnv2052 and Nvidia card if that helps. Less than a year ago it would take approx 3.5 hours to process a movie with two pass, Highest Quality, but after the changes in x264 it now takes much, much longer. Should I be installing LAV Directshow Filters, FFDSHOW or Haali Matroska Splitter and how to setup BD-RB to reduce the encoding times?I would suggest you install LAV filters (see the first post of this thread), and then simply select "DirectshowSource" from the SETUP menu.

[mparade]

Is there an alternative way in BD-RB to make 3D full-backups (output is BD-25, keeping 3D content as 3D, 2D content as 2D on the same disc) compared to Frim Encoder?

Is it possible to make full 3D-backups in e.g. half-sbs, full-sbs formats as well?

I would like to start to archive my 3D BDs as well with the "best possible quality".
Is the "only" current solution to use Frim Encoder with 1-pass ABR?

Thank you for an answer in advance.

[worknstiff]

Don't know if this constitutes a "Bug" or not but I am having a hard time getting BD Rebuilder to allow blanking of quite a few extras on the Fantastic Beasts blue ray. I have tried to change the min m2ts size setting and there is still a load of m2ts files not listed in FULL or EDIT mode. Is this just a limitation of how many items can be listed or are they hidden from BD Rebuilder's processing somehow? Thanks again jdobbs for the most excellent BD Rebuilder program, I only wish other video editing programs were designed to be as simple to use as this one.

[Sharc]

Is there an alternative way in BD-RB to make 3D full-backups (output is BD-25, keeping 3D content as 3D, 2D content as 2D on the same disc) compared to Frim Encoder?

Is it possible to make full 3D-backups in e.g. half-sbs, full-sbs formats as well?

I would like to start to archive my 3D BDs as well with the "best possible quality".
Is the "only" current solution to use Frim Encoder with 1-pass ABR?

Thank you for an answer in advance.
Similar has been discussed a while ago. Summarizing -- as far as I remember:
- SBS (full or half) is limited to movie-only backups
- Full 3D backup with BD-RB requires FRIM
- There is no free 3D MVC alternative to FRIM

Edit:
I found the last post of this discussion. You may want to trace the full discussion backwards from there.
I have been asking about full disk 3D backups SBS.
http://forum.doom9.org/showpost.php?p=1794225&postcount=25538

[jdobbs]

Yeah. I wasn't positive, but looked at it, and it doesn't do SBS full backups right now. I'm going to go back and see how hard it would be to make the changes... but no promises. In order to do that, it will have to appear like a 2D disc that just happens to have half SBS or half O/U where the 3D features used to be.

[Mark_Venture]

I would very much appreciate suggestions on what settings I should be using to speed up (without noticeable loss of quality) the processing time of BD movies. I also have licence for dgdecnv2052 and Nvidia card if that helps. Less than a year ago it would take approx 3.5 hours to process a movie with two pass, Highest Quality, but after the changes in x264 it now takes much, much longer. Should I be installing LAV Directshow Filters, FFDSHOW or Haali Matroska Splitter and how to setup BD-RB to reduce the encoding times?If you want to... take a look at this thread -> http://forum.doom9.org/showthread.php?t=173601 my INI file is posted there, and some times from tests I ran (with both my old PC and after upgrades)... try those settings to see if it speeds things up. If you have the same exact blurays, you can better compare to the speeds I see.

Granted I'm going for good quality that doesn't take "all night" (i.e. I'm trying to balance video quality and speed), I'm not going for "exact quality" (i.e. I'm not looking for "best quality no matter how long it takes).

Since I setup BD-Rebuilder long ago, I followed the OP exactly. At that time for step 2, only step 2B was available. When 2A & 2C was added, I did that. And I usually have set as DGDecNV for Frame Serving (since i donated and have a license)

[mparade]

@Sharc and jdobbs

I think I will start to make some tests on a BD-25 media using the Frim Encoder in BD-RB. In the worst case, hopefully it is enough to
cut down the HD and throw out the unused audio tracks to reach a similar quality level to x264's CRF~18-20. I am very satisfied with the results of x264 but don't know Frim at all.

[Sharc]

@mparade
I think you won't be disappointed by the FRIM quality when backing up to a 25GB disc as the bitrate is comfortable.

[jdobbs]

@mparade
I think you won't be disappointed by the FRIM quality when backing up to a 25GB disc as the bitrate is comfortable.I agree. It might be different if you're trying to squeeze everything into the size of a DVD -- but at BD-25 bitrates I think it looks great (at least for most discs, there may be a giant one out there somewhere that might be an exception).

[meadrocks]

Boondock Saints works great on x264, fails in hevc. I included all the input files. This is a brand new PC I built, I've only installed bd-rebuilder. My old PC would take 6-10 hours to do a rebuild, this 1 did the x264 in 75 minutes.

alternate:
[00001]
caption=MKV Container, 1920x1080, AutoGOP, Auto-AC3
vBitrate=3000
aBitrate=*
aType=0
vFormat=5
vKeyint=Auto
cType=1
[00002]
caption=MKV Container, HEVC 1920x1080, Auto-AC3
vEncoder=1
vBitrate=2000
vKeyint=Auto
aBitrate=*
aType=0
vFormat=5
cType=1

bdrebuilder.ini:
[Options]
VERSION=0.50.0.23
ENCODER=0
MODE=3
ENCODE_QUALITY=2
ONEPASS_ENCODING=0
AUTO_QUALITY=1
MOVIEONLY_TYPE=2
ALTCRF=22
ALT_TARGET=1024
ALT_CRF_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
[Paths]
WORKING_PATH=E:\T1\
SOURCE_PATH=C:\DVDRIP\BOONDOCK_SAINTS\

bd-rebuilder.log
[04/06/17] Checking System Settings
- BD-Rebuilder v0.50.23
- Windows Version: 6.1 [7601]
- Working Path Free Space: 104.87GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[04/06/17] Systems Settings Check complete
----------------------
[04/06/17] BD Rebuilder v0.50.23
[12:07:49] Source: BOONDOCK_SAINTS_00001
- Input BD size: 32.94 GB
- Approximate total content: [01:48:21.661]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, HEVC 1920x1080, Auto-AAC
- Quality: High Quality (Default)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[12:07:49] PHASE ONE, Encoding
- [12:07:49] Processing: VID_00115 (1 of 7)
- [12:07:49] Extracting A/V streams [VID_00115]
- [12:12:02] Reencoding video [VID_00115]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 56,920 frames
- [12:12:02] Reencoding: VID_00115, Pass 1 of 1
[12:12:03] - Failed video encode, aborted

boondocksaints.inf
[Status]
LABEL=BOONDOCK_SAINTS
VERSION=v0.50.23
SOURCE_SIZE=35370577920
SOURCE_VIDEO_SIZE=35370577920
TARGET_SIZE=4686086144
REDUCTION=.132485427707708
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=0
SUBS_TO_KEEP=all
BACKUP_MODE=1
MOVIEONLY_TYPE=2
USE_LAVF=0
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
QUICK=0
ENCODE_STEP=1.5
[00115]
AUDIO=100
PGS=11
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=1716350997

Thanks for your time & help.

[MrVideo]

Enhancement suggestions:

Both of these apply to the editing of the menu text.

1) Allow the ability to select multiple titles to move. I've run into a situation where time would have been saved if I could have moved more than one title at once.

2) When titles are too long, instead of just removing the text, how about turning those characters red instead. There are times when looking at the titles where I have missed that text had been truncated. By having the text changed to red instead, it tends to catch the eye more than missing text. Plus, by still having the text on the line, when other characters are removed, they will be there so that they can again be used and turned black.

Thanks.

[jdobbs]

1) Allow the ability to select multiple titles to move. I've run into a situation where time would have been saved if I could have moved more than one title at once.I don't understand this request.

[Denner]

Hi, I have built a dedicated x264 encoding rig, it has a Ryzen 1700, 750gb SSD and 16gb ram, only thing on the machine is Windows 10 and BD-Rebuilder as it will only be used for blu-ray re-encoding.
System is stress tested and with Prime 95 ( 24 hour run ) and OCCT ( 12 hour run ) and is 100% stable when overclocked to 3800GHz and ofcause at stock speed of 3000GHz.

Problem is that I BD-Rebuilder keeps crashing or x264 does and I keep getting a pop up window with this message "x264.exe has stopped working...." , I have now tried installing RipBot to see if this crashes x264 too, but no problems there at all, RipBot have been running for 12 hours straight encoding a lot of blu-ray rips that crashes BD-Rebuilder without crashing, so I tried encoding with BD-Rebuilder again this morning and same problem is still there, I am at a loss, because I have the excact same setup on my "normal" pc except it is an intel processor and it never crashes, even on the same disk ?

Here is the log from BD-Rebuilder:

[04-09-17] BD Rebuilder v0.50.23
[14:42:53] Source: UPB1_625529
- Input BD size: 32,05 GB
- Approximate total content: [02:18:19.248]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- X264 Tweak(s) enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[14:42:54] PHASE ONE, Encoding
- [14:42:54] Processing: VID_00013 (1 of 23)
- [14:42:54] Extracting A/V streams [VID_00013]
- [14:42:59] Reencoding video [VID_00013]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 648 frames
- Bitrate: 19.105 Kbs
- [14:42:59] Reencoding: VID_00013, Pass 1 of 2
- [14:43:04] Reencoding: VID_00013, Pass 2 of 2
- [14:43:23] Video Encode complete
- [14:43:23] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [14:43:23] Multiplexing M2TS
- [14:43:27] Processing: VID_00046 (2 of 23)
- [14:43:27] Extracting A/V streams [VID_00046]
- [14:43:31] Reencoding video [VID_00046]
- [14:43:31] Keeping original video (no reencode)
- [14:43:31] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [14:43:31] Multiplexing M2TS
- [14:43:35] Processing: VID_00270 (3 of 23)
- [14:43:35] Extracting A/V streams [VID_00270]
- [14:43:40] Reencoding video [VID_00270]
- [14:43:40] Keeping original video (no reencode)
- [14:43:40] Processing audio tracks
- [14:43:40] Multiplexing M2TS
- [14:43:44] Processing: VID_00301 (4 of 23)
- [14:43:44] Extracting A/V streams [VID_00301]
- [14:44:55] Reencoding video [VID_00301]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 103.173 frames
- Bitrate: 21.909 Kbs
- [14:44:55] Reencoding: VID_00301, Pass 1 of 2
- Encode failed. Aborting.
- BD-Rebuilder v0.50.23
- Windows Version: 6.2 [9200]
- Working Path Free Space: 350,12GB
- AVISYNTH Version: 2.6.0.5, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4504, 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
- FRIMEncode: Ok
- FRIMDecode: Ok
[14:57:07] - Failed video encode, aborted

I am using x264's internal LAVF for frameserving and the only tweak I have enabled is tune film for BD-Rebuilders second pass, have tried with no tweaks enabled but it still crashes :(

Have anyone had the same prolem and what did you do to solve it ?

[jdobbs]

Your system probably isn't stable. I've seen this a hundred times with people trying other stress tests -- they are meaningless. The only real stress test is X264. Slow down your clock and see if it goes away.

It's also possible it could be an incompatibility with the version of X264 included with BD-RB that is used for X264/LAVF (it's different than the one used for other frame-serving types). Try using DirectshowSource.

[mparade]

@jdobbs

Maybe a bug?:

I have just finished testing a bit the Quick-play menu feature of BD-RB. After importing my complete Tom&Jerry Classic DVD Collection Volume 1. I just wanted to burn them (6xDVD5) directly to a BD-25 media. I have used my own menu page for this job. The bug I recognized described in steps as follows to be able to repeat:

- I played an item from the Quick-play menu;
- During play I changed audio from English to e.g. Hungarian and the subtitle language to e.g. Hungarian;
- After watching 3 items sequentially I entered the Quick-play menu to play an other item from the end;
- During watching that one I realized that both the audio and subtitle language had set back to English, however I finished playing the previous item with a Hungarian audio and subtitle language chosen;

It seems after entering the Quick-play menu both the audio and subtitle language tracks chosen set back to the defaults due to some unknown reason. If I play items sequentially without entering the menu, the tracks will not be set back.

It is not really convenient because each time I enter the menu (for the purpose of playing an other item among the 70-80pcs in this case) and play an other item I have to set back my preferred language manually using my remote controller both for the subtitle and the audio tracks which has already been done previously.

Please help.

Thank you very much.

[Denner]

Your system probably isn't stable. I've seen this a hundred times with people trying other stress tests -- they are meaningless. The only real stress test is X264. Slow down your clock and see if it goes away.

It's also possible it could be an incompatibility with the version of X264 included with BD-RB that is used for X264/LAVF (it's different than the one used for other frame-serving types). Try using DirectshowSource.

Just tried a DirectshowSource encode, no problems at all, no x264 crashing, but problem is that both first and second pass are way slower than using x264 LAVF, is there any way of settin up BD-Rebuilder so that it can mach the encoding speed achieved by x264 LAVF ?

If not what is the fastest setting when not using x264 LAVF ?

Also tried replacing the x264L-64 with the x264 version RipBot is using and just renamed it to x264L-64, and encoding with that version of x264 using x264/LAVF as fremserver caused no crashing, ut it had a painfully slow first pass with around 40fps and with the original x264L-64 i get aroud 160fps in the first pass.....

[jdobbs]

Just tried a DirectshowSource encode, no problems at all, no x264 crashing, but problem is that both first and second pass are way slower than using x264 LAVF, is there any way of settin up BD-Rebuilder so that it can mach the encoding speed achieved by x264 LAVF ?

If not what is the fastest setting when not using x264 LAVF ?

Also tried replacing the x264L-64 with the x264 version RipBot is using and just renamed it to x264L-64, and encoding with that version of x264 using x264/LAVF as fremserver caused no crashing, ut it had a painfully slow first pass with around 40fps and with the original x264L-64 i get aroud 160fps in the first pass.....That's the reason a different version is used. Something has changed in X264 that makes the use of LAVF extremely slow. So I used one of the old versions for X264/LAVF encoding. You could try other old version (look at the version of X264L-64 in BD-RB and work back from there).

My own tests of X264 don't show much difference between X264/LAVF and DirectshowSource -- but different processors can make a big difference.

[jdobbs]

@jdobbs

Maybe a bug?:

I have just finished testing a bit the Quick-play menu feature of BD-RB. After importing my complete Tom&Jerry Classic DVD Collection Volume 1. I just wanted to burn them (6xDVD5) directly to a BD-25 media. I have used my own menu page for this job. The bug I recognized described in steps as follows to be able to repeat:

- I played an item from the Quick-play menu;
- During play I changed audio from English to e.g. Hungarian and the subtitle language to e.g. Hungarian;
- After watching 3 items sequentially I entered the Quick-play menu to play an other item from the end;
- During watching that one I realized that both the audio and subtitle language had set back to English, however I finished playing the previous item with a Hungarian audio and subtitle language chosen;

It seems after entering the Quick-play menu both the audio and subtitle language tracks chosen set back to the defaults due to some unknown reason. If I play items sequentially without entering the menu, the tracks will not be set back.

It is not really convenient because each time I enter the menu (for the purpose of playing an other item among the 70-80pcs in this case) and play an other item I have to set back my preferred language manually using my remote controller both for the subtitle and the audio tracks which has already been done previously.

Please help.

Thank you very much.I'll have to look at it. But I'm guessing it's because the menu is using the default track and doesn't have other languages as an option.

[MrVideo]

I don't understand this request.
With BDRB, multiple menu items cannot be selected. If you click on one item and then do a ctrl-left-mouse click on another item, the first one is deselected. (Or shift-left-mouse click to select a range of items).

The selection of an item is to allow for editing of the text and potential moving of the item within the menu.

If multiple items are selected, just blank the area that is used for text editing until only a single item is selected. This will still allow for the move of the selected items to a new location in the menu.

[Lathe]

Anybody else experiencing issues with e-mail delivery of notifications related to new posts? Until today I don't think I've gotten any in over a week at least -- even though there have been plenty of posts.

Yep, just realized the other day that I hadn't gotten any notifications from this thread in a LONG time (I'm a bit slow... :rolleyes: ) so, I'm just NOW seeing your post about 3 weeks later :)

[Lathe]

It's started to work again for me too. Just a temporary glitch, I guess.

It must be because of something with my personal system or setup, but like when I've used CC Cleaner before, I always have to come back and choose 'instant e'mail notifications' on the threads or I won't get notified. Perhaps whatever happened here had the same effect where in MY case it didn't come back on.

[Lathe]

Hi, I have built a dedicated x264 encoding rig, it has a Ryzen 1700, 750gb SSD and 16gb ram, only thing on the machine is Windows 10 and BD-Rebuilder as it will only be used for blu-ray re-encoding.
System is stress tested and with Prime 95 ( 24 hour run ) and OCCT ( 12 hour run ) and is 100% stable when overclocked to 3800GHz and ofcause at stock speed of 3000GHz.

Problem is that I BD-Rebuilder keeps crashing or x264 does and I keep getting a pop up window with this message "x264.exe has stopped working...." , I have now tried installing RipBot to see if this crashes x264 too, but no problems there at all, RipBot have been running for 12 hours straight encoding a lot of blu-ray rips that crashes BD-Rebuilder without crashing, so I tried encoding with BD-Rebuilder again this morning and same problem is still there, I am at a loss, because I have the excact same setup on my "normal" pc except it is an intel processor and it never crashes, even on the same disk ?

Here is the log from BD-Rebuilder:


I am using x264's internal LAVF for frameserving and the only tweak I have enabled is tune film for BD-Rebuilders second pass, have tried with no tweaks enabled but it still crashes :(

Have anyone had the same prolem and what did you do to solve it ?

Hmmm, don't know if it's relevant, but I've not been able to use 'tunings' in BDRB or 'tune film' as a 'tweak' It didn't accept it. I just put in the cmd line codes separately.

[gonca]

I've not been able to use 'tunings' in BDRB or 'tune film' as a 'tweak'
It's working fine on my system
Must be on your end, Lathe:cool:

[Lathe]

It's working fine on my system
Must be on your end, Lathe:cool:

Gonca, if I've told you once, I've told you twice...

Don't talk about my END! :angry:

... and, if it's any of your business, the last time I checked it, there was nothing ON it!

[mparade]

I'll have to look at it. But I'm guessing it's because the menu is using the default track and doesn't have other languages as an option.

OK. Thank you. Simpler said, I think the missing feature of the current Quick-Play Menu is that it should simply "recall" (because the problem only happens when entering the menu) the audio and subtitle language tracks that were set by the user last time manually on remote.

Maybe you should even consider adding hidden opts (to help for the Quick-Play Menu to choose the language required at first loading) like:

IMPORT_DEFAULT_SUB_LANG=s
IMPORT_DEFAULT_AUDIO_LANG=s

Your help is much appreciated.

[Denner]

That's the reason a different version is used. Something has changed in X264 that makes the use of LAVF extremely slow. So I used one of the old versions for X264/LAVF encoding. You could try other old version (look at the version of X264L-64 in BD-RB and work back from there).

My own tests of X264 don't show much difference between X264/LAVF and DirectshowSource -- but different processors can make a big difference.

Cool and thanks, is there a place where I can download older versions of bd-rebuilder?
On ryzen 8 core cpu the difference is huge...

Noticed that when encoding with DirectshowSource x264 32bit version is used, is this normal or am i doing something wrong?

[gonca]

the last time I checked it, there was nothing ON it!
How can you see all the way back there:D

[jdobbs]

Cool and thanks, is there a place where I can download older versions of bd-rebuilder?
On ryzen 8 core cpu the difference is huge...

Noticed that when encoding with DirectshowSource x264 32bit version is used, is this normal or am i doing something wrong?You can't use the 64 bit version with 32 bit AVISYNTH. In my tests the difference in speed between the 32 and 64 bit versions is negligible.

[Denner]

You can't use the 64 bit version with 32 bit AVISYNTH. In my tests the difference in speed between the 32 and 64 bit versions is negligible.

Cool, thanks, right now I am testing with the x264 64bit version from BD-RBV04414 and so far no problem /crashing with this version of x264, best thing is that I am getting 35fps on second pass using the Highest ( very slow) compared to 22fps ( second pass ) on the same settings encoder settings using directshow, so that is quiet a boost in encoding speed using x264 vs directshow :)

Thanks for the help so far :thanks:

[AmigaFuture]

Anybody else experiencing issues with e-mail delivery of notifications related to new posts? Until today I don't think I've gotten any in over a week at least -- even though there have been plenty of posts.

Yep. I've been occupied by other things and hadn't gotten a message in a bit. Recently I got 2 and there were more than 2 new replies.

[Denner]

A quick update, I found a version of x264, that seemes to be optimal for encoding with Ryzen 8 core cpu's, where I am hitting 40 to 60fps, slowest setting, on the second pass, depending on the encoding bitrate and it almost maxes out all 8 cores in both first and second pass... and most important no crashes....
If any one am having the same problems with Ryzen and bd-rb crashing I would be glad to help and share the x264 version I am using :)

[Taurus]

@ Denner:
Please share your insight.
I'm about to buy a Ryzen and everything cleared beforehand
is stopping me from wasting time on experiments.:D
Thank you.

[Lathe]

A quick update, I found a version of x264, that seemes to be optimal for encoding with Ryzen 8 core cpu's, where I am hitting 40 to 60fps, slowest setting, on the second pass, depending on the encoding bitrate and it almost maxes out all 8 cores in both first and second pass... and most important no crashes....
If any one am having the same problems with Ryzen and bd-rb crashing I would be glad to help and share the x264 version I am using :)

Wow, dude that REALLY is fast! Getting that speed using the ridiculously ultra-slow setting is bloody amazing! I just use the 'High' setting 2 Pass when I'm trying to be 'Mr. Anal' (so to speak, no cracks please...) and, granted, with a couple of x264 'tweaks' on the 2nd pass I MIGHT get like 5 or 6 fps, usually slower... I guess that's what 8 frigg'n smok'n cores will do for you :)

[gonca]

:sly:@Lathe
Mr. Anal,... cracks
You are trying to make it easy

[Denner]

@ Denner:
Please share your insight.
I'm about to buy a Ryzen and everything cleared beforehand
is stopping me from wasting time on experiments.:D
Thank you.

I am using the x264 64bit version from BD-RBV05011 and just renamed it to x264L-64 and replaced the one in the current BD-RB with it :)

You can find the version here:https://www.videohelp.com/software/BD-Rebuilder/old-versions

[Denner]

Wow, dude that REALLY is fast! Getting that speed using the ridiculously ultra-slow setting is bloody amazing! I just use the 'High' setting 2 Pass when I'm trying to be 'Mr. Anal' (so to speak, no cracks please...) and, granted, with a couple of x264 'tweaks' on the 2nd pass I MIGHT get like 5 or 6 fps, usually slower... I guess that's what 8 frigg'n smok'n cores will do for you :)


Yup the power of a Ryzen 1700 overclocked to 3.8 GHz, love this CPU, easiest overclock I ever did :)

[mparade]

Hello,

I am using FORCE_NOENCODE=1 and FORCE_ENCODE=0
without any resizing, ivtc, filters, etc. and BD-RB still wants to reencode the main feature. I have set target size to BD-50 (Original is BD-50, too). Any idea?

[jdobbs]

Hello,

I am using FORCE_NOENCODE=1 and FORCE_ENCODE=0
without any resizing, ivtc, filters, etc. and BD-RB still wants to reencode the main feature. I have set target size to BD-50 (Original is BD-50, too). Any idea?Post the settings from BDREBUILDER.INI, and I'll see if there are any settings that are forcing it.

[mparade]

Post the settings from BDREBUILDER.INI, and I'll see if there are any settings that are forcing it.

Sorry...I left IVTC turned on in the setup dialog. I thought it had no effect on pure progressive content at all. But now, I see.

[Yordan5]

I am using the x264 64bit version from BD-RBV05011 and just renamed it to x264L-64 and replaced the one in the current BD-RB with it :)

You can find the version here:https://www.videohelp.com/software/BD-Rebuilder/old-versions

Thank you so much. My encoding times and CPU utilisation are now back to more "Normal" times. On High Quality with two pass encoding it now takes approx. 8.5 hours compared to nearly double that with the latest versions of x264.

[Lathe]

:sly:@Lathe

Quote:
Mr. Anal,... cracks

You are trying to make it easy

You ask, you plead, you beg, and this is what you get...


http://lathe-of-heaven.com/sigh1.gif

[Lathe]

Thank you so much. My encoding times and CPU utilisation are now back to more "Normal" times. On High Quality with two pass encoding it now takes approx. 8.5 hours compared to nearly double that with the latest versions of x264.

That's about what mine runs at the same setting. If I add a couple of x264 'tweaks', it might take a bit longer.

JD, do YOU recommend replacing the current BDRB version with this particular version of x264 (BDRB 5011) and renaming it as suggested above?

[Thaddäus]

I've been using BD Rebuilder for many discs during the last months and recognized that there's always more than 1 GB space left on a BD25 when I'm using the BD25 target size-preset. Sometimes there's even more left - last week I tried a backup of "Deepwater Horizon" and the output-size was only 20,9 GB so 10% of the disc space (should be around 23,1 GB) is still free.

Has someone tested BD Rebuilder with a custom-target size to use the whole capacity of a BD25? I'm using the highest quality-settings and two pass-encoding, so BD Rebuilder should be able to calculate the optimal bitrate and make the most of the availiable space. I'm only keeping the German and English audio-tracks in HD (if availiable) and do a backup of the full disc with all bonus features. I read about the problem in other boards and they were discussing that deleting some audio tracks can result in miscalculation of the target size. But in the case of "Deepwater Horizon" those two were the only audio-tracks availiable, so that can't be the reason for that big miscalculation BD Rebuilder did. Did someone recognize similar problems and is there a workaround for this (maybe a certain custom target size) to get the best results possible?

EDIT: Don't know if it's going to help but here's the logfile of my "Deepwater Horizon"-backup

----------------------
[04.16.17] BD Rebuilder v0.50.23
[12:28:07] Source: DEEPWATER_HORIZON
- Input BD size: 45,62 GB
- Approximate total content: [04:20:30.916]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[12:28:07] PHASE ONE, Encoding
- [12:28:07] Processing: VID_00005 (1 of 15)
- [12:28:07] Extracting A/V streams [VID_00005]
- [12:28:17] Reencoding video [VID_00005]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24,000fps, 2.193 frames
- Bitrate: 11.316 Kbs
- [12:28:17] Reencoding: VID_00005, Pass 1 of 2
- [12:28:41] Reencoding: VID_00005, Pass 2 of 2
- [12:30:27] Video Encode complete
- [12:30:27] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [12:30:27] Multiplexing M2TS
- [12:30:33] Processing: VID_00006 (2 of 15)
- [12:30:33] Extracting A/V streams [VID_00006]
- [12:30:46] Reencoding video [VID_00006]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24,000fps, 3.373 frames
- Bitrate: 11.640 Kbs
- [12:30:46] Reencoding: VID_00006, Pass 1 of 2
- [12:31:23] Reencoding: VID_00006, Pass 2 of 2
- [12:34:12] Video Encode complete
- [12:34:12] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [12:34:12] Multiplexing M2TS
- [12:34:17] Processing: VID_00007 (3 of 15)
- [12:34:17] Extracting A/V streams [VID_00007]
- [12:34:29] Reencoding video [VID_00007]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24,000fps, 3.332 frames
- Bitrate: 11.634 Kbs
- [12:34:29] Reencoding: VID_00007, Pass 1 of 2
- [12:35:03] Reencoding: VID_00007, Pass 2 of 2
- [12:37:54] Video Encode complete
- [12:37:54] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [12:37:54] Multiplexing M2TS
- [12:38:00] Processing: VID_00021 (4 of 15)
- [12:38:00] Extracting A/V streams [VID_00021]
- [12:52:40] Reencoding video [VID_00021]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24,000fps, 155.028 frames
- Bitrate: 4.059 Kbs
- [12:52:40] Reencoding: VID_00021, Pass 1 of 2
- [13:21:01] Reencoding: VID_00021, Pass 2 of 2
- [14:46:33] Video Encode complete
- [14:46:33] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- Track 4353 (eng): Keeping original audio
- [14:46:33] Multiplexing M2TS
- [14:51:41] Processing: VID_00101 (5 of 15)
- [14:51:41] Extracting A/V streams [VID_00101]
- [14:53:50] Reencoding video [VID_00101]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 73.335 frames
- Bitrate: 5.650 Kbs
- [14:53:50] Reencoding: VID_00101, Pass 1 of 2
- [15:05:52] Reencoding: VID_00101, Pass 2 of 2
- [15:49:51] Video Encode complete
- [15:49:52] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [15:49:52] Multiplexing M2TS
- [15:50:21] Processing: VID_00102 (6 of 15)
- [15:50:21] Extracting A/V streams [VID_00102]
- [15:51:05] Reencoding video [VID_00102]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 26.229 frames
- Bitrate: 6.615 Kbs
- [15:51:05] Reencoding: VID_00102, Pass 1 of 2
- [15:55:28] Reencoding: VID_00102, Pass 2 of 2
- [16:12:39] Video Encode complete
- [16:12:39] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [16:12:39] Multiplexing M2TS
- [16:12:53] Processing: VID_00103 (7 of 15)
- [16:12:53] Extracting A/V streams [VID_00103]
- [16:13:40] Reencoding video [VID_00103]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 24.797 frames
- Bitrate: 6.636 Kbs
- [16:13:40] Reencoding: VID_00103, Pass 1 of 2
- [16:17:45] Reencoding: VID_00103, Pass 2 of 2
- [16:33:31] Video Encode complete
- [16:33:31] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [16:33:31] Multiplexing M2TS
- [16:33:46] Processing: VID_00104 (8 of 15)
- [16:33:46] Extracting A/V streams [VID_00104]
- [16:34:52] Reencoding video [VID_00104]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 39.288 frames
- Bitrate: 5.650 Kbs
- [16:34:52] Reencoding: VID_00104, Pass 1 of 2
- [16:40:57] Reencoding: VID_00104, Pass 2 of 2
- [17:03:25] Video Encode complete
- [17:03:25] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:03:25] Multiplexing M2TS
- [17:03:47] Processing: VID_00105 (9 of 15)
- [17:03:47] Extracting A/V streams [VID_00105]
- [17:04:27] Reencoding video [VID_00105]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 23.385 frames
- Bitrate: 5.656 Kbs
- [17:04:27] Reencoding: VID_00105, Pass 1 of 2
- [17:07:52] Reencoding: VID_00105, Pass 2 of 2
- [17:20:36] Video Encode complete
- [17:20:37] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:20:37] Multiplexing M2TS
- [17:20:51] Processing: VID_00106 (10 of 15)
- [17:20:51] Extracting A/V streams [VID_00106]
- [17:21:01] Reencoding video [VID_00106]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 24,000fps, 3.030 frames
- Bitrate: 5.386 Kbs
- [17:21:01] Reencoding: VID_00106, Pass 1 of 2
- [17:21:33] Reencoding: VID_00106, Pass 2 of 2
- [17:23:19] Video Encode complete
- [17:23:19] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [17:23:19] Multiplexing M2TS
- [17:23:24] Processing: VID_00401 (11 of 15)
- [17:23:24] Extracting A/V streams [VID_00401]
- [17:23:32] Reencoding video [VID_00401]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 2.204 frames
- Bitrate: 5.388 Kbs
- [17:23:32] Reencoding: VID_00401, Pass 1 of 2
- [17:23:55] Reencoding: VID_00401, Pass 2 of 2
- [17:25:03] Video Encode complete
- [17:25:03] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [17:25:03] Multiplexing M2TS
- [17:25:08] Processing: VID_00402 (12 of 15)
- [17:25:08] Extracting A/V streams [VID_00402]
- [17:25:17] Reencoding video [VID_00402]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 3.384 frames
- Bitrate: 5.385 Kbs
- [17:25:17] Reencoding: VID_00402, Pass 1 of 2
- [17:25:57] Reencoding: VID_00402, Pass 2 of 2
- [17:28:01] Video Encode complete
- [17:28:01] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [17:28:01] Multiplexing M2TS
- [17:28:07] Processing: VID_00403 (13 of 15)
- [17:28:07] Extracting A/V streams [VID_00403]
- [17:28:14] Reencoding video [VID_00403]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 2.162 frames
- Bitrate: 5.678 Kbs
- [17:28:14] Reencoding: VID_00403, Pass 1 of 2
- [17:28:38] Reencoding: VID_00403, Pass 2 of 2
- [17:29:49] Video Encode complete
- [17:29:49] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [17:29:49] Multiplexing M2TS
- [17:29:54] Processing: VID_00404 (14 of 15)
- [17:29:54] Extracting A/V streams [VID_00404]
- [17:30:02] Reencoding video [VID_00404]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 2.880 frames
- Bitrate: 5.387 Kbs
- [17:30:02] Reencoding: VID_00404, Pass 1 of 2
- [17:30:30] Reencoding: VID_00404, Pass 2 of 2
- [17:31:58] Video Encode complete
- [17:31:58] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [17:31:58] Multiplexing M2TS
- [17:32:03] Processing: VID_00405 (15 of 15)
- [17:32:03] Extracting A/V streams [VID_00405]
- [17:32:14] Reencoding video [VID_00405]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 3.480 frames
- Bitrate: 6.341 Kbs
- [17:32:14] Reencoding: VID_00405, Pass 1 of 2
- [17:32:52] Reencoding: VID_00405, Pass 2 of 2
- [17:35:22] Video Encode complete
- [17:35:22] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [17:35:22] Multiplexing M2TS
[17:35:27]PHASE ONE complete
[17:35:27]PHASE TWO - Rebuild Started
- [17:35:27] Rebuilding BD file Structure
[17:35:37] - Encode and Rebuild complete
[17:35:37] JOB: DEEPWATER_HORIZON finished.

[jdobbs]

I haven't had any issues with sizing. But, then again, I never use the "Highest (Very Slow)" setting for encoding. I'm guessing that is the source of the sizing impact. No matter what setting you choose BD-RB will calculate a set of bitrates that is required to fill the target size. It's possible, though, that if you set a higher quality setting, the encoder might reach its maximum quality level and not output at a size that matches the specified bitrate.

[Thaddäus]

Thanks for your reply!
As you can see it took around 5 hours to do the backup of that disc which had 4:20 h of material on it - so I can't complain about slow encoding even with the "Highest (Very Slow)"-settings. ;)
I just did a scan of the main movie's video bitrate with Bitrate Viewer - and it says the average bitrate is 4.058 kbps which exactly matches BD Rebuilder's calculated bitrate from the logfile. Maybe I'm trying it again with a custom target size of 24500 MB and see what happens.

By the way: Although the bitrate of that backup was quite low BD Rebuilder did a fantastic job when it comes to the picture quality which is still quite good! Wasn't expecting that when I saw the calculated bitrate but that tool keeps still surprising me in a very positive way. :)

[MrVideo]

By the way: Although the bitrate of that backup was quite low BD Rebuilder did a fantastic job when it comes to the picture quality which is still quite good!
The x264 encoder is a fantastic H.264 encoder, especially when used in two-pass mode.

[Lathe]

I've been using BD Rebuilder for many discs during the last months and recognized that there's always more than 1 GB space left on a BD25 when I'm using the BD25 target size-preset. Sometimes there's even more left - last week I tried a backup of "Deepwater Horizon" and the output-size was only 20,9 GB so 10% of the disc space (should be around 23,1 GB) is still free.

Has someone tested BD Rebuilder with a custom-target size to use the whole capacity of a BD25? I'm using the highest quality-settings and two pass-encoding, so BD Rebuilder should be able to calculate the optimal bitrate and make the most of the availiable space. I'm only keeping the German and English audio-tracks in HD (if availiable) and do a backup of the full disc with all bonus features. I read about the problem in other boards and they were discussing that deleting some audio tracks can result in miscalculation of the target size. But in the case of "Deepwater Horizon" those two were the only audio-tracks availiable, so that can't be the reason for that big miscalculation BD Rebuilder did. Did someone recognize similar problems and is there a workaround for this (maybe a certain custom target size) to get the best results possible?


Yeah, that is pretty much what most of mine come out to also. Generally if I choose the BD-25 output size, no matter whether I'm using 'Fast' 2 Pass or 'High' 2 Pass, invariably the resulting encodes will be 22.1-22.5, sometimes 22.9. If I am really trying to squeeze an encode where it BARELY will fit, I usually select a custom size of about 23,700. But, even with that, most times the size is still 1 or 1 1.5 Gigs less than a full disc. If it's REALLY pushing it, I will try to go a bit more, but one time I tried 23,800 and it came out just a tad too big.

Of course, I've never been accused of playing with a full disc anyway... :cool:

[gonca]

playing with a full disc anyway.

yeah, yeah

[jdobbs]

Yeah, that is pretty much what most of mine come out to also. Generally if I choose the BD-25 output size, no matter whether I'm using 'Fast' 2 Pass or 'High' 2 Pass, invariably the resulting encodes will be 22.1-22.5, sometimes 22.9. If I am really trying to squeeze an encode where it BARELY will fit, I usually select a custom size of about 23,700. But, even with that, most times the size is still 1 or 1 1.5 Gigs less than a full disc. If it's REALLY pushing it, I will try to go a bit more, but one time I tried 23,800 and it came out just a tad too big.

Of course, I've never been accused of playing with a full disc anyway... :cool:22.1 to 22.5 would be within the range of correct sizing. As I've said before, that's purposeful because the outer edges of the disc are much more prone to failure/error. By keeping the disc in a smaller size range you are less likely to experience problems. It also keeps me from having to respond to people who think the failed burn is BD-RB's fault. But the 20.9 (as reported) would be outside what should be expected.

Just my opinion/advice, but a disc written to capacity will hold about 23.3GB and that last 1GB (about 4%) or so isn't going to get you a noticeable improvement in quality, especially considering the risk. Of course, as always, I've added the ability to change the target size for anyone who disagrees.

[nozuul]

Is there an easy way to brighten the output of a video? I was looking back at change logs, and one from January 2016 mentioned a filter, but I was unsure how that works? Is that a hidden option?

Thanks for the help.

[jdobbs]

Is there an easy way to brighten the output of a video? I was looking back at change logs, and one from January 2016 mentioned a filter, but I was unsure how that works? Is that a hidden option?

Thanks for the help.You can use the filter editor (see SETUP) to add the tweak filter (http://www.avisynth.org.ru/docs/english/corefilters/tweak.htm). Example: Tweak(bright=20). That filter also lets you adjust other parameters such as contrast, hue, and saturation.

[Lathe]

22.1 to 22.5 would be within the range of correct sizing. As I've said before, that's purposeful because the outer edges of the disc are much more prone to failure/error. By keeping the disc in a smaller size range you are less likely to experience problems. It also keeps me from having to respond to people who think the failed burn is BD-RB's fault. But the 20.9 (as reported) would be outside what should be expected.

Just my opinion/advice, but a disc written to capacity will hold about 23.3GB and that last 1GB (about 4%) or so isn't going to get you a noticeable improvement in quality, especially considering the risk. Of course, as always, I've added the ability to change the target size for anyone who disagrees.

Yes, I fully agree. It's best not to push it to the outer edges of the disc.

[Lathe]

Is there an easy way to brighten the output of a video? I was looking back at change logs, and one from January 2016 mentioned a filter, but I was unsure how that works? Is that a hidden option?

Thanks for the help.

As JD mentions above, 'tweak' is a simple but excellent Avisynth filter to use. I use it a LOT for films where I feel that the contrast could be boosted a little, or the colours need a tad more saturation, etc. Many times if you want to boost the contrast, it naturally also gets brighter, so many times I will boost the contrast and lower the brightness at the same time. You probably already do this, but if you take a small snippet of the film and use an .avs script to preview it, you can tweak it a number of times and change the settings to see how it will look in the final encode. Here are some of the scripts I've used for certain films:

LADY IN THE WATER: (cont=1.2, Sat=1.2) This was one of my very first tries, so I probably overdid it a little :) But, for me, I just can't stand really washed out looking films and prefer a 'sharper' or more contrasted image. I KNOW videophiles will pale in horror, but that is just my personal taste with some films. I only usually go to the trouble to do it if the print REALLY bugs me.

http://lathe-of-heaven.com/litw01.jpg


http://lathe-of-heaven.com/litw02.jpg

Another film that was REALLY washed out was 'GODZILLA VS. BIOLLANTE' But, that was likely just due to the film stock used at the time. I used these settings on that print:

Sharpen(.8)
tweak(cont=1.20, bright=-12)

In this case, the film is already pretty bright, but I wanted more sharpness and delineation, so in boosting the contrast I had to lower the brightness. The Avisynth 'sharpness' setting is pretty primitive, so I only use it sparingly. Normally, just using contrast, brightness, and sometimes saturation is enough. Again, this is one of my very first tries at Avisynth; I've since found better 'sharpness' filters.

Other films where I've used Avisynth are 'FORTRESS' & 'THE THIRTEENTH FLOOR'. Both 'DRACULA' (1979) and 'SEA OF LOVE' were SO bloody dark and washed out, that I REALLY had to tweak those two a lot. These were the settings I used for them:

DRACULA: tweak(cont=1.40, bright=1, Sat=1.3, startHue=325, endHue=15, maxSat=75)

SEA OF LOVE: tweak(cont=1.5, bright=-4)

I've probably only done around 12-15 films total.

[MrVideo]

I KNOW videophiles will pale in horror
:eek: :eek: :eek: :eek: :eek: You certainly got that right.

[Thaddäus]

22.1 to 22.5 would be within the range of correct sizing. As I've said before, that's purposeful because the outer edges of the disc are much more prone to failure/error. By keeping the disc in a smaller size range you are less likely to experience problems. It also keeps me from having to respond to people who think the failed burn is BD-RB's fault. But the 20.9 (as reported) would be outside what should be expected.

I tried "Girl on the Train" yesterday with a custom target size of 24500 MB (I was really trying to push it there) and it resulted in 23,2 GB and only 67 MB free space left on the disc. I never had any issues with burning discs even when almost the full capacity was used but I admit - only 67 MB left was quite close to the edge. ;)

Then I gave "Deepwater Horizon" another try with those settings which resulted in 21,9 GB and something came to my mind: Could the Dolby Atmos-tracks on that disc be the reason for BD Rebuilder's miscalculation? Both audio-tracks in the main movie are in Dolby Atmos 7.1.4 with a Dolby True HD 7.1-core. Maybe BD Rebuilder only gets something wrong here. The other discs I checked and which all were around 21,9 GB with the BD25-preset didn't have Atmos-tracks, so maybe that's the cause.

Just my opinion/advice, but a disc written to capacity will hold about 23.3GB and that last 1GB (about 4%) or so isn't going to get you a noticeable improvement in quality, especially considering the risk. Of course, as always, I've added the ability to change the target size for anyone who disagrees.

You're right - under usual circumstancers 1 GB more or less for the whole disc shouldn't make a big difference in picture quality but I think when the bitrate gets as low as in my "Deepwater Horizon"-backup (only 4 MBit/s are very low, especially for such a film) it could make a difference. While I'm typing this I'm trying another backup of the film, now with a custom size of 25500 MB. If it follows the previous results this should now end up with around 22,9 GB which would be absolutely fine. And the main movie now got 5.687 kbps - compared to the 4.058 from the first backup with the BD25-preset this should be an improvement. Let's see what happens - fingers crossed. ;)

EDIT: Not exactly 22,9 GB but hey - 22,8 GB are also OK. ;)

[nozuul]

You can use the filter editor (see SETUP) to add the tweak filter (http://www.avisynth.org.ru/docs/english/corefilters/tweak.htm). Example: Tweak(bright=20). That filter also lets you adjust other parameters such as contrast, hue, and saturation.

Thanks Jdobbs for the info, and Lathe for the example. I will give this a try and see if the results are more to my liking for my particular case.

[AmigaFuture]

... setting 2 Pass when I'm trying to be 'Mr. Anal' (so to speak, no cracks please...) and, ....

Uhh-heh - heh - heh...he typed anal and crack..uhhh-huh-huh-hehe hehe...

I couldn't pass it over... :D :goodpost:

[AmigaFuture]

Sorry...I left IVTC turned on in the setup dialog. I thought it had no effect on pure progressive content at all. But now, I see.

I had to remember that a few times also to switch it off.

[MrVideo]

Sorry...I left IVTC turned on in the setup dialog. I thought it had no effect on pure progressive content at all. But now, I see.
Technically there are two progressive video formats that can have telecine video:
1) 1080p with repeat frame to get 23.976 to 29.97 fps.
2) 720p 59.94 with 2:3 pulldown.

[Lathe]

Uhh-heh - heh - heh...he typed anal and crack..uhhh-huh-huh-hehe hehe...

I couldn't pass it over... :D :goodpost:

Just trying to provide the top quality humour that this group has come to expect.

JD has taught us well... http://lathe-of-heaven.com/yes.gif

[AmigaFuture]

Technically there are two progressive video formats that can have telecine video:
1) 1080p with repeat frame to get 23.976 to 29.97 fps.
2) 720p 59.94 with 2:3 pulldown.

I've still not gotten 2) to render to 23.976 or 29.97 correctly. Always jerky or 59.94 results. I haven't check into it for a while (private matters)...hence the lack of my replies.

[MrVideo]

I've still not gotten 2) to render to 23.976 or 29.97 correctly. Always jerky or 59.94 results.
The IVTC setting should do the job correctly. The AVISynth filter that Jdobb uses works with 720p 59.94 fps telecine video. Converting 59.94 to 29.97 with telecine material is not going to look pretty.

[raisingcanex]

Not sure if it's possible. But would like to know. What's the best settings to save or rebuild a Blu-Ray movie to a format that can be saved on a external drive connected to an Xbox One S and keep the original file size and audio (ex. Dolby Atmos). Where Xbox would recognize it like it was a Disc. Where you don't have to search the Blu-Ray folder looking for the right movie file to play. But hopefully like a disc.

[mparade]

Hello,

In Full-backup mode there is no chance to blank some of the very annoying m2ts files (mostly warnings) because they are not included in streamlist (even with MIN_M2TS_SIZE=0 set).
If I change to menu&movie only mode they can be blanked in the streamlist but the menu will be not fully functional finally(e.g. after changing the language from English to an other in the menu and then playing the movie until the end, the viewer will not get back to the menu automatically (permanent black screen). If I do not change the language from English in the menu the menu seems to be fully functional). This is not happening in Full-backup mode but at the same time I cannot blank the unwanted, annoying m2ts files.

Please help. My menus are not functioning this way.

[AmigaFuture]

The IVTC setting should do the job correctly. The AVISynth filter that Jdobb uses works with 720p 59.94 fps telecine video. Converting 59.94 to 29.97 with telecine material is not going to look pretty.

So far, 59.94 to 23.976 is producing a very slight jerky output. I'm checking a few other files to see if the same.

[MrVideo]

So far, 59.94 to 23.976 is producing a very slight jerky output. I'm checking a few other files to see if the same.
Any chance you can post a snippet of the original, say 30 sec worth, and the same snippet after recoding. I can then look at them to see if I can see anything that sticks out. M2TS, TS, MKV or MP4 wrappers would be fine.

[MrVideo]

So far, 59.94 to 23.976 is producing a very slight jerky output. I'm checking a few other files to see if the same.
OK, got the videos and it took me all of <30 sec to determine why you are having issues.

It is not 2:3 pulldown telecine source. You have to leave it as 59.94. Why? Because the source contains true 59.94 fps source and 29.97 fps source repeat framed to 59.94 fps. There is zero 23.976 source telecined. Even if there was in other portions of the complete video, what I've seen is enough to stop you from trying to do IVTC.

Sorry, but that is why you are having issues.

[AmigaFuture]

OK, got the videos and it took me all of <30 sec to determine why you are having issues.

It is not 2:3 pulldown telecine source. You have to leave it as 59.94. Why? Because the source contains true 59.94 fps source and 29.97 fps source repeat framed to 59.94 fps. There is zero 23.976 source telecined. Even if there was in other portions of the complete video, what I've seen is enough to stop you from trying to do IVTC.

Sorry, but that is why you are having issues.

Nothing to be sorry about. Ahhh...I think this help me come closer to understanding why some 59.94 fps will go to 23.976 and why some I have to use HandBrake still to get 29.97. When I use HandBrake I leave the Detelecine option "Off" in the Filters Tab, and the other filters "off" as well, but in the Video Tab I change the "framerate" to 23.976 or 29.97, and with this video I used 29.97. Then switch "Peak Framerate" to "Constant Framerate" and I notice totally smooth video. But I haven't found any info through HandBreak to find any filter switches like you can for AVISynth. But since it doesn't use AVISynth.. I'm not able to repeat this with BD-RB. HandBreak is a transcoder ONLY. But the video result is smooth, and I'm...not...a fan of transcoding. Since too much is "yanked" from the video which is already lower quality from Cable TV.

With a previous version of BD-RB, (49.xx)...??... I'd have to go back to check, anyway, then BD-RB was able to get 59.94 to 23.976 with IVTC, but since then it hasn't. So, I think there was a bug that JD caught. Laughing, I remember thinking, "Ahhh, man!! Back to HandBreak" since it wouldn't do it anymore.

Anyway, now I know there are 2 possible differences in 59.94, not just a "bug" causing a challenge. This is what's really complex to me and I'm attempting to understand it. Hence the joking friendly comment to Lathe a while back.

This is why I wondered if there's "switch" that could be added to BD-RB (not really knowing how else to ask the question) to "force?" a 23.976 or 29.97 framerate which HandBreak "seems" to do so a rerender without transcoding becomes possible. Hmm.. Really appreciate the continuity help with this. I also understand why JD prefers sources like this to be kept in original form.

[m.rup]

Hello,

In Full-backup mode there is no chance to blank some of the very annoying m2ts files (mostly warnings) because they are not included in streamlist (even with MIN_M2TS_SIZE=0 set).


That's also my experience, from some discs you can remove all boring warnings, from other ones (e.g. Teenage Mutant Ninja Turtles 2) you can't. I use MultiAVCHD in that cases, but since it seems to be not longer developed, it fails on new movies more and more. It would be really great if BR would allow to blank all warnings, regardles where they are hidden.

[MrVideo]

Nothing to be sorry about. Ahhh...I think this help me come closer to understanding why some 59.94 fps will go to 23.976 and why some I have to use HandBrake still to get 29.97.
Why do you want to convert 59.94 source material to 29.97, when the source contains true 59.94 fps video? By doing so, you've reduced the time spatial info.
This is why I wondered if there's "switch" that could be added to BD-RB (not really knowing how else to ask the question) to "force?" a 23.976 or 29.97 framerate which HandBreak "seems" to do so a rerender without transcoding becomes possible.
Transcoding is generally when you go from one video codec to another, i.e., MPEG-2 to H.264, or H.264 to H.265. This requires a re-encoding, which you are calling a rerender.

Keep in mind that changing frame rates also requires a re-encoding. There is no way around that. You can't just "drop" frames in a 59.94 fps video to get to 29.97 fps. That isn't the way digital video works.

[AmigaFuture]

I can see the difference between using CloneDVD 2 from Elaborate Bytes if allowing it to clone a DVD using DVD-5 transcoding for rerendering vs DVD-RB's BEST 2-pass rerendering using HC as the encoder after disabling CloneDVD 2's transcoding using DVD DL. As an example. That means to me, using CloneDVD 2 to clone to a DVD-5 uses it's transcoder to rerender. Using it to process in conjunction with AnyDVD to rip a DVD but using DVD DL disables the transcoder and makes it all lossless to then use DVD-RB to rerender in 2-pass in BEST quality produces a much better looking DVD, I can see very well. I can also see the transcoded CloneDVD 2 version looking much worse, but to "normal eyes" of friends, it looks ok or GOOD.

When using BD-RB and disabling CRF/ABR I can see a difference in quality in whatever video I'm having it rerender. To me, and I'm realizing now that I might have been misunderstanding something in the reencoding process for some years now, that means transcodiing is disabled and quality encoding is happening.

I understand it doesn't "drop" the frames, I'm lacking in technical words to explain and attempting to get it across. :-) I understand when I used 29.97 and changed to Constant Framerate that means clicking "Start" means it starts a rerendering process otherwise it would all be lossless, or untouched.

In my mind, and I'm realizing I might have accepted something incorrectly for some years, that if the video is rerendered to it's actual source framerate that it's in better quality, AND...you can change the size of the file to fit projects. I'm still considering I might have taken on some misunderstandings. Ahhh, evolution.

[MrVideo]

There is no such thing as lossless recoding. Any time a video is recoded, there are digital losses. Depending on the bitrate involved, the loss can be so subtle that the viewer cannot see it. But, each and every re-encoding results in added digital artifacts. Initially, the broadcast industry was kinda worried about the re-encoding that goes on from the production stage up thru the broadcast stage. But, that point is kinds moot now that the video that is broadcast (OTA/cable/DBS) is so bit starved that it can look horrible.

You also cannot have something re-encoded and have it "look better" than the original. It is impossible to create something from nothing. It it like those TV shows where a still image, or surveillance video, is "enhanced" to get a sharp clear image. A crappy pixel image is going to stay a crappy pixel image.

When you re-encode from 59.94 fps to 29.97 fps, one of two things has to happen: 1) every other frame is dropped, or 2) two consecutive frames are blended together to create a single frame. You didn't say why you want to go to 29.07 fps, instead of keeping the original 59.94 fps video.

The general rule of thumb is that when you re-encode, in order to reduce the added artifacts, is to have at least a 2:1 bitrate difference. That means if the resulting bitrate is 10 Mbps, the source bitrate needs to be 20 Mbps, or more. Keep in mind that 20 Mbps MPEG-2 video is approximately equal to H.264 video at 40 Mbps. So, recoding 10 Mbps MPEG-2 video to 10 Mbps MPEG-2 video does nothing but add digital artifacts. It will not result in a better looking video. Recoding from 10 Mbps MPEG-2 video to 10 Mbps H.264 video will result in fewer digital artifacts due to the 2:1 ratio and the better H.264 encoder. But, in all cases, the resultant recoded video will not look better than the original.

[Lathe]

Why do you want to convert 59.94 source material to 29.97, when the source contains true 59.94 fps video? By doing so, you've reduced the time spatial info.

Transcoding is generally when you go from one video codec to another, i.e., MPEG-2 to H.264, or H.264 to H.265. This requires a re-encoding, which you are calling a rerender.

Keep in mind that changing frame rates also requires a re-encoding. There is no way around that. You can't just "drop" frames in a 59.94 fps video to get to 29.97 fps. That isn't the way digital video works.

I THINK, if I understand this correctly, that in the past I've just left the video at 59.94 (I can't remember exactly what I did to 'double' the rate - IDK if it had something to do with it being interlaced or something...) Anyway, the 'doubled' rate at 59.94 looked a LOT better than when I tried to convert it to, what, 23.xx, I don't remember. But, since my player simply played the 59.94 perfectly fine 'as is', I just left it.

Now, you were saying that you cannot change the frame rate without re-encoding. How then does TSMuxer allow you to change the frame rate for the video track when it is simply remuxing the file...? Many times I get 'a hold of' an MKV file where when I drop it into TSMuxer it shows an improper frame rate of 90,000 fps (or something like that) I just choose the correct fps from the drop down menu. I can choose 24,000/0001, 24, 25, 30, 30,000/0001 if I remember correctly, and when I remux it, the actual frame rate DOES change to whatever I've chosen. So, if it is the wrong one, the A/V sync will be off.

How can it do this without re-encoding?

[MrVideo]

You aren't changing the frame rate, you are setting it to the correct one. The frame rate is set in the file. When you see that 90k frame rate, it means that it was not set, or not set correctly.

[jdobbs]

There is no such thing as lossless recoding.Actually there is. It's typically huge, but you can use a lossless setting in X264 and get an exact duplicate of the original in which the rendered picture will match bit-for-bit. There are also several lossless codecs that will do the same.

[jdobbs]

How then does TSMuxer allow you to change the frame rate for the video track when it is simply remuxing the file...? I think he's talking about changing the framerate but staying temporally accurate. You can change the frame rate without reencoding by only changing the internal flags (that indicate framerate) -- but (unless it is using pulldown flags and you're doing iVTC) the video will speed up or slow down and not be accurate temporally.

In telecining the video is actually 23.976fps (24fps)... and then pulldown flags are used to repeat fields and a new frame is generated for every 4 that actually exists during playback. In simple iVTC you can just reset those flags and the result comes out at the original frame rate. Telecining was created so that 24fps films could be easily converted to NTSC (29.97fps) for broadcast.

Pulldown flags can also be used for other conversions (like PAL->NTSC or FILM->PAL) but you don't see that as often.

[MrVideo]

Actually there is. It's typically huge, but you can use a lossless setting in X264 and get an exact duplicate of the original in which the rendered picture will match bit-for-bit.
Then just copy the original video file. :D

[MrVideo]

In telecining the video is actually 23.976fps (24fps)... and then pulldown flags are used to repeat fields and a new frame is generated for every 4 that actually exists during playback. In simple iVTC you can just reset those flags and the result comes out at the original frame rate.
The only service that I know of that uses pulldown flags is HBO.

[Sharc]

Then just copy the original video file. :D
And how to convert the format by just copying?

[MrVideo]

And how to convert the format by just copying?
You can't convert the format and have a bit-for-bit copy. Maybe our ideas of what a format change is, is a little different.

[Sharc]

You can't convert the format and have a bit-for-bit copy. Maybe our ideas of what a format change is, is a little different.
I think our ideas of "lossless compression" are different.
The comparison is after decoding, i.e. after reconstruction of the original data.

[MrVideo]

I think our ideas of "lossless compression" are different.
The comparison is after decoding, i.e. after reconstruction of the original data.
It therefore cannot be lossless. As soon as you decode the video, it is turned into raw video. When you then run it through a MPEG-2, H.264 or H.265 encoder, it is compressed. Especially at the bitrates that we typically use.

An example of a lossless compressor is a program that produces TIFF images. MPEG-2, H.264 or H.265 encoders are lossy.

Take a look at: http://stackoverflow.com/questions/768999/what-is-a-good-lossless-video-codec

Google lossless video encoder for more places to look.

[jdobbs]

The only service that I know of that uses pulldown flags is HBO.Well, that, and pretty much every DVD that has ever been encoded for US distribution. That's millions...

[jdobbs]

You can't convert the format and have a bit-for-bit copy. Maybe our ideas of what a format change is, is a little different.Listen, I know you think you know what you're talking about -- but you're completely wrong. What, exactly, do you think "lossless" means? It means no loss.

[jdobbs]

You can't convert the format and have a bit-for-bit copy. Maybe our ideas of what a format change is, is a little different.Yes. You can. It's completely silly to say otherwise and just shows that you don't understand how it works. I'm sorry -- but that is a fact.

Example: You display the individual frames and save them with no encoding. Is that not lossless? When you look at the frames after encoding it will match bit-for-bit. Now -- use a lossless encoding method (there are hundreds of them) -- when it recreates the image it is EXACTLY THE SAME BIT-FOR-BIT PICTURE as the original.

Just because you don't understand something doesn't make it any less a fact. H.264, MPEG-2, etc are not typically lossless. But there are many, many encoding methods that reduce size without losing a single bit. When you zip a file, do you expect the same output as input? Yes, because a zip uses lossless compression. There are also video codecs that use lossless compression methods that are designed specifically for video.

[jdobbs]

I think our ideas of "lossless compression" are different.
The comparison is after decoding, i.e. after reconstruction of the original data.A true lossless encoding doesn't change the original. It is an EXACT duplicate. That's the whole purpose of lossless encoding -- it has no changes between encoding generations. You could do 9000 generations and have absolutely no difference between the original and the 900th encode. I'm not talking about "almost lossless" I mean lossless. You'd probably also find that the intermediate (compressed) files are exact duplicates as well.

[MrVideo]

Well, that, and pretty much every DVD that has ever been encoded for US distribution. That's millions...
I said service. DVD releases are not a service.

[MrVideo]

Listen, I know you think you know what you're talking about -- but you're completely wrong. What, exactly, do you think "lossless" means? It means no loss.
Exactly. Yet, posters seem to think that they can get lossless recoding using H.264, which is defined as a lossy codec.

[MrVideo]

Example: You display the individual frames and save them with no encoding. Is that not lossless? When you look at the frames after encoding it will match bit-for-bit. Now -- use a lossless encoding method (there are hundreds of them) -- when it recreates the image it is EXACTLY THE SAME BIT-FOR-BIT PICTURE as the original.
Yes, using a lossless encoder. We are talking about MPEG-2, H.264 and H.265 encoders. You can't burn lossless encoder output to a Blu-ray using BD-RB. Lossy encoders cannot create lossless output. That is the point I've been trying to make. While you can set the encoders to be as near lossless (not truly lossless), it can create unmanageable file sizes.
Just because you don't understand something doesn't make it any less a fact. H.264, MPEG-2, etc are not typically lossless. But there are many, many encoding methods that reduce size without losing a single bit. There are also video codecs that use lossless compression methods that are designed specifically for video.
See above about using lossless encoders by users of BD-RB.

I do understand what I am talking about. I just do not seem to be getting the info across.

[jdobbs]

You will also note that X264 has a lossless mode.Lossy encoders cannot create lossless output. That is the point I've been trying to make. You're misrepresenting your position. Your statement quoted exactly was There is no such thing as lossless recoding. Any time a video is recoded, there are digital losses. That statement was wrong, no matter how hard to try to change it or its intent.In telecining the video is actually 23.976fps (24fps)... and then pulldown flags are used to repeat fields and a new frame is generated for every 4 that actually exists during playback. In simple iVTC you can just reset those flags and the result comes out at the original frame rate.
The only service that I know of that uses pulldown flags is HBO.I said service. DVD releases are not a service.Why would you respond to my post talking just about "service" when you know the description is accurate in response to the original subject of how framerate can be changed in a video file without changing the underlying video. Sounds to me, again, like you're trying to misrepresent the intent of your post in order to attempt to be "right". Why even post a response at all?

[AmigaFuture]

There is no such thing as lossless recoding. Any time a video is recoded, there are digital losses. Depending on the bitrate involved, the loss can be so subtle that the viewer cannot see it. But, each and every re-encoding results in added digital artifacts. Initially, the broadcast industry was kinda worried about the re-encoding that goes on from the production stage up thru the broadcast stage. But, that point is kinds moot now that the video that is broadcast (OTA/cable/DBS) is so bit starved that it can look horrible.

CloneDVD 2 with DVD DL active will pass the video/audio through (lossless) and remove Layer Break as well as languages if you choose. I usually don't, I allow other software to remove it. But for ripping, it's a nice GUI.

You also cannot have something re-encoded and have it "look better" than the original. It is impossible to create something from nothing. It it like those TV shows where a still image, or surveillance video, is "enhanced" to get a sharp clear image. A crappy pixel image is going to stay a crappy pixel image.

I wasn't meaning it would look better. I meant that I can see the difference in rerendering in transcoding and higher quality. Many people I know don't see it, but I do. Upscaling a video can look really good, but I do agree...not better than the original. Some Star Trek TNG is showing through Cable and they've "upscaled" the video some, and I can see the "fuzziness" but I like the show..so I "ignore it", haha.

When you re-encode from 59.94 fps to 29.97 fps, one of two things has to happen: 1) every other frame is dropped, or 2) two consecutive frames are blended together to create a single frame. You didn't say why you want to go to 29.07 fps, instead of keeping the original 59.94 fps video.

File size for storage and making disks...or discs. Also, sometimes, for keeping it closer to "original" framerates. But TV shows I'm starting to think..if it's 59.94 then just remove the commercials and it's in great quality since it IS from TV and they aren't using Blu-ray or HD great quality. That's saved for the series/moves we buy.

The general rule of thumb is that when you re-encode, in order to reduce the added artifacts, is to have at least a 2:1 bitrate difference. That means if the resulting bitrate is 10 Mbps, the source bitrate needs to be 20 Mbps, or more. Keep in mind that 20 Mbps MPEG-2 video is approximately equal to H.264 video at 40 Mbps. So, recoding 10 Mbps MPEG-2 video to 10 Mbps MPEG-2 video does nothing but add digital artifacts. It will not result in a better looking video. Recoding from 10 Mbps MPEG-2 video to 10 Mbps H.264 video will result in fewer digital artifacts due to the 2:1 ratio and the better H.264 encoder. But, in all cases, the resultant recoded video will not look better than the original.[/QUOTE]

Argh, that 2:1 stuff is still very confusing to me. I under 4:3 is SD and 16:9 is Letterbox or HD...but otherwise...

I don't think I'll ever be a fan of MiB and Mbps. I still love and understand MB and KB or Kb. But I get your idea. :-)

[AmigaFuture]

Actually there is. It's typically huge, but you can use a lossless setting in X264 and get an exact duplicate of the original in which the rendered picture will match bit-for-bit. There are also several lossless codecs that will do the same.

Okay!! Ahhh, yeah, this I have read and I have used them some years ago. They are uncompressed images. Thanks, JD, I knew I remembered correctly. Like BMP can be compressed or not, same as the old IFF format the Amiga used to name a couple. Indeed, very large. A lot of people don't know what compression is that I know. When I talk about it I'm usually asked what it means. I don't go into the details that MrVideo does but it gets it across. :D

[MrVideo]

You will also note that X264 has a lossless mode.
I admit that I didn't know that x264/ffmpeg had a lossless mode. I found the following in the ffmpeg site:
[code]Note that lossless output files will likely be huge, and most non-FFmpeg based players will not be able to decode lossless, so if compatibility or file size issues you should not use lossless. If you're looking for an output that is roughly "visually lossless" but not technically lossless use a -crf value of around 17 or 18 (you'll have to experiment to see which value is acceptable for you). It will likely be indistinguishable from the source and not result in a huge, possibly incompatible file like true lossless mode.[/quote]

A lot of my wording indeed left a lot to be desired. Posts, not just by me, went astray from just changing the frame rate.

I got the impression from posts that usable lossless output could be created for use with BD-RB, or at least desired. Yes, I did not include DVD sources. I limited responses to HD sources and should have said so.

For files that members want to change from 29.97 to 23.976 that do not have pulldown flags (a majority of MPEG-2/H.264 HD videos), lossless recoding is not really a choice. The files will be way too large and more-than-likely not playable. Most certainly can't be burned to Blu-ray by BD-RB, as is.

So, in a broad sense, the way HD videos are used with BD-RB, lossless recoding doesn't exist. As noted in the above quote, "visually lossless" output is very possible. I do it all the time.

Time to move on. We've each made our points.

[MrVideo]

Argh, that 2:1 stuff is still very confusing to me. I under 4:3 is SD and 16:9 is Letterbox or HD...but otherwise...
Ah, but there is 4:3 HD. Your ST:TNG mention is a prime example. They went back to the original film negatives and rescanned for HD. While the actual video that is displayed is 16:9, the 4:3 content is pillarboxed within the 16:9 frame.

BTW, the 2:1 ratio tends to be moot at extremely high bit rates. :D

[Lathe]

I think he's talking about changing the framerate but staying temporally accurate. You can change the frame rate without reencoding by only changing the internal flags (that indicate framerate) -- but (unless it is using pulldown flags and you're doing iVTC) the video will speed up or slow down and not be accurate temporally.

Hmmm... I don't quite understand the 'accurate temporarally' part. All I know is that with TSMuxer if I take a file and use the drop-down box by the video file where it says 'change the fps to' and I change that, then the 'speed' of the video file WILL indeed either slow down or speed up with reference to the audio track. I think I DO understand that what it is doing is changing the 'headers', right? In other words, it's merely telling the player to render it at such 'n' such frame rate which will either speed it up or slow it down.

So, are what you are saying is that the ACTUAL frame rate doesn't change, but you can kind of 'fool' the player into playing it faster or slower...?

I THINK you can do something similar to that with MKVMerge with the aspect ratio, right? Can't you change the 'headers' or whatever they are in the file when you remux it that will cause the player to play it in a different AR then the ACTUAL file is in? That would be GREAT if I can figure out how to do that, and I have a strong suspicion that SOMEHOW if I could do that then my OPPO would play the 1440x1080 HD 4x3 files correctly instead of stretching them across the screen. But, I've never quite figured out the secret to that. Especially when I have to render a film in a BDMV format in order for my OPPO to recognize and play the HD audio.

Also too... Isn't FLAC a good example of what you were talking about where the size is compressed but none of the original information is lost? And, it seems that I remember that AVI files can be rendered lossless, right? You get a HUGE file, but that is truly lossless, right?

[MrVideo]

Hmmm... I don't quite understand the 'accurate temporarally' part.
In short, space and time. Temporally accurate means something that originally took 10 seconds, plays back taking 10 seconds. That is the time portion. Spatial accuracy is what I was referring to regarding 59.94 fps vs. 29.97 fps. If the 59.94 fps video contains 59.94 unique images, that is its spatial accuracy. If you convert to 29.97 fps, you cut the spatial accuracy in half. While the time it takes hasn't changed, the number of images that show what happens during that time is reduced.
So, are what you are saying is that the ACTUAL frame rate doesn't change, but you can kind of 'fool' the player into playing it faster or slower...?
In a nutshell, yes. That is how slo-mo works. The recording is done at a much higher frame rate and then that file is told to play back at a different frame rate.
I THINK you can do something similar to that with MKVMerge with the aspect ratio, right? Can't you change the 'headers' or whatever they are in the file when you remux it that will cause the player to play it in a different AR then the ACTUAL file is in? That would be GREAT if I can figure out how to do that, and I have a strong suspicion that SOMEHOW if I could do that then my OPPO would play the 1440x1080 HD 4x3 files correctly instead of stretching them across the screen. But, I've never quite figured out the secret to that.
Have you tried playing with the three aspect ratio settings in mkvmerge:
--aspect-ratio <TID:f|a/b>
--aspect-ratio-factor <TID:f|a/b>
--display-dimensions <TID:width>x<height>
Run mkvmerge without any options to get the help output. You should be able to google it as well. There is a really detailed help for this program. I have a printout around here somewhere.

Oh, and you can ask in the Doom9 mkvmerge thread.
Also too... Isn't FLAC a good example of what you were talking about where the size is compressed but none of the original information is lost?
Yes
And, it seems that I remember that AVI files can be rendered lossless, right? You get a HUGE file, but that is truly lossless, right?
AVI is a wrapper. It is the content that could be lossless. As for AVI wrappers containing lossless codecs, I do not know.

[Lathe]

In short, space and time. Temporally accurate means something that originally took 10 seconds, plays back taking 10 seconds. That is the time portion. Spatial accuracy is what I was referring to regarding 59.94 fps vs. 29.97 fps. If the 59.94 fps video contains 59.94 unique images, that is its spatial accuracy. If you convert to 29.97 fps, you cut the spatial accuracy in half. While the time it takes hasn't changed, the number of images that show what happens during that time is reduced.

In a nutshell, yes. That is how slo-mo works. The recording is done at a much higher frame rate and then that file is told to play back at a different frame rate.

Have you tried playing with the three aspect ratio settings in mkvmerge:
--aspect-ratio <TID:f|a/b>
--aspect-ratio-factor <TID:f|a/b>
--display-dimensions <TID:width>x<height>
Run mkvmerge without any options to get the help output. You should be able to google it as well. There is a really detailed help for this program. I have a printout around here somewhere.

Oh, and you can ask in the Doom9 mkvmerge thread.

Yes

AVI is a wrapper. It is the content that could be lossless. As for AVI wrappers containing lossless codecs, I do not know.

Thanks for the cmd line stuff for MKVMerge; I know it has a LOT of options, but I've never really gone through them. I'll check those out concerning the aspect ratio.

Yeah, I understood about the 59.xx Again, I don't remember WHY something rendered a file to 59.xx; it was to correct SOMETHING else, but I don't remember. But, the resulting file played just fine at 59.xx I would THINK that you would NOT want to convert it to half the frame rate and lose half the information (or do a 'blend' either...)

[AmigaFuture]

Also too... Isn't FLAC a good example of what you were talking about where the size is compressed but none of the original information is lost? And, it seems that I remember that AVI files can be rendered lossless, right? You get a HUGE file, but that is truly lossless, right?

Correct, but depends on codec even for AVI. I use FLAC and sometimes APE for my CD backups as well as other sound samples instead of keeping them in "wave".

[Lathe]

Hey, are all you guys all right...???

Has JD introduced an insidious virus into his program that has sucked you all into his Evil world?

:eek:

[AmigaFuture]

Evil is a mental illusion. But he has created a virus that I'm enjoying using. It is propagating my BDs. Haha. Other than that, shhhhhhh....let people sleep for a bit.

[jdobbs]

Has anyone else noticed some weird behavior with DGIndexNV? It seems to be crashing (or at least not running) when BD-RB tries to run it. The result is failed encodes -- and when I investigate there is no .DGI file. The issue appears to be at least partially random, as sometimes it will be ok if I re-run the job. I think it may have started about the same time that I upgraded Windows 10 to version 1703, but I'm not positive that there's a link.

Hey, are all you guys all right...???

Has JD introduced an insidious virus into his program that has sucked you all into his Evil world?It has been unusually quiet here, hasn't it? I guess it's because it has been so long since I've released a new version. I got a little busy with another project and haven't been giving BD-RB the attention it needs.

[gonca]

DGIndexNV is working fine on my system with the Anniversary Update version

[jdobbs]

DGIndexNV is working fine on my system with the Anniversary Update versionGood to know. So I guess it must be something other than the update then. Maybe it's one of the changes I put in for the next release... I'm going to look at it today.

[Ch3vr0n]

@jdobbs No. It's still possible it's that update. Several users on the redfox forums reported issues with anydvd that were fixed after a reinstall of it. You're mixing up the Anniversary update (build 1607) with the Creators Update (build 1701, that you're using). 2 different builds. I can't test that yet as CU has yet to be pushed to my system and i'm not going to do it manually.

[videoh]

Good to know. So I guess it must be something other than the update then. Maybe it's one of the changes I put in for the next release... I'm going to look at it today. All working fine for me too with Creators Update (1703 build 15063.296). Make sure you have the latest DGDecNV version, which you can download from DG site. If you still encounter issues, I can give you a debug build. One thing to remember, a recent change requires you to have a copy of the license.txt file together with DGDecodeNV.dll if it is not in the same directory as DGIndexNV.exe.

I'll do some testing with BDRB today.

[jdobbs]

@jdobbs No. It's still possible it's that update. Several users on the redfox forums reported issues with anydvd that were fixed after a reinstall of it. You're mixing up the Anniversary update (build 1607) with the Creators Update (build 1701, that you're using). 2 different builds. I can't test that yet as CU has yet to be pushed to my system and i'm not going to do it manually.Yeah, you're right, I was thinking "Anniversary" was 1703.

[jdobbs]

All working fine for me too with Creators Update (1703 build 15063.296). Make sure you have the latest DGDecNV version, which you can download from DG site. If you still encounter issues, I can give you a debug build. One thing to remember, a recent change requires you to have a copy of the license.txt file together with DGDecodeNV.dll if it is not in the same directory as DGIndexNV.exe.

I'll do some testing with BDRB today.I thought I was using the latest... but it turns out I was using v2051. I just updated to v2053 and it seems to be working on a job that I'd had problems with consistently. I'll let you know if I find anything else -- but right now it seems to be working.

Thanks

[videoh]

Good to hear. Those earlier versions had a race issue that can account for the things you saw.

[AmigaFuture]

I also won't go Windows 10, I just..do....not...like....the Metro GUI at all and all the hidden snooping. Maybe if StarDock gets a Win7 Skin made, which I also haven't checked for in a while. Anyway, DGIndexNV 2051 is doing well with Windows 7 Pro 64-bit. I'll check for a new version...maybe some cool new updates?

Edit: OOhh, some nice updates for DGIndexNV. Computers: Not always possible to keep with updates, past age 25. Especially when nature and face to face connections are also more cool. :D

[gonca]

maybe some cool new updates?
You could say that

[Lathe]

It has been unusually quiet here, hasn't it? I guess it's because it has been so long since I've released a new version. I got a little busy with another project and haven't been giving BD-RB the attention it needs.

No, no, not at all Boss... Just thought I'd shake up the crickets a bit...

[Jake802]

Does BD shrink a 3D Blu-Ray and still leave it 3D?

[jdobbs]

Does BD shrink a 3D Blu-Ray and still leave it 3D?Yes, it does.

[Lathe]

Does BD shrink a 3D Blu-Ray and still leave it 3D?

Only if you send J Dobbs your youngest child. Then he sends you a special key to unlock this ability.

A steep price, but it does a beautiful job...

[jdobbs]

"Your children... we want to buy your children." - John Belushi, The Blues Brothers

[varekai]

“A child of five could understand this. Send someone to fetch a child of five.”
― Groucho Marx

[AmigaFuture]

Not sure what's happening. Downloaded DGIndexNV.exe 2052, make a new directory as I do for each new version. Setup BD-RB as per usual. Ran the first run..and failed. Used 2053 next...failed.

Switched back to DGIndexNV.exe 2051 and all is well again. Anyone come across this? If I run DGIndexNV.exe from it's directory and have it read the file, it does fine. License is in the text file as per normal. Hmm.. Bug with BD-RB?

[06/03/17] BD Rebuilder v0.50.23
[02:17:51] Source: MONTY_PYTHON_D1
- Input BD size: 42.66 GB
- Approximate total content: [03:39:39.432]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[02:17:54] PHASE ONE, Encoding
- [02:17:54] Blanking: VID_00007 (1 of 7)
- [02:17:54] Blanking: VID_00005 (2 of 7)
- [02:17:54] Blanking: VID_00006 (3 of 7)
- [02:17:54] Processing: VID_00000 (4 of 7)
- [02:17:54] Extracting A/V streams [VID_00000]
- [02:19:05] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 92,396 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 12,546 Kbs
- [02:19:06] Reencoding: VID_00000, Pass 1 of 2
- Encode failed. Aborting.
- BD-Rebuilder v0.50.23
- Windows Version: 6.1 [7601]
- Working Path Free Space: 358.51GB
- AVISYNTH Version: 2.5.8.0, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[02:19:06] - Failed video encode, aborted
----------------------
[06/03/17] BD Rebuilder v0.50.23
[02:20:15] Source: MONTY_PYTHON_D1
- Input BD size: 42.66 GB
- Approximate total content: [03:39:39.432]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[02:20:19] PHASE ONE, Encoding
- [02:20:19] Blanking: VID_00007 (1 of 7)
- [02:20:19] Blanking: VID_00005 (2 of 7)
- [02:20:19] Blanking: VID_00006 (3 of 7)
- [02:20:19] Processing: VID_00000 (4 of 7)
- [02:20:19] Extracting A/V streams [VID_00000]
- [02:21:37] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 92,396 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 12,296 Kbs
- [02:21:37] Reencoding: VID_00000, Pass 1 of 2

It's doing fine...

[videoh]

Later versions of DGDecNV no longer support Avsynth 2.5.8.

[AmigaFuture]

OOpps...I forgot about that though I read it. Heh!

[Jake802]

LMAO! Thanks JDobbs. I thought I read it did but I was not sure.

[AmigaFuture]

I removed AviSynth 2.5.8 and installed 2.6.0 and then 2.6.1 but still encountering this error. Went back to AviSynth 2.6.0. I'm still checking into this, but anyone have any suggestions?

[06/05/17] BD Rebuilder v0.50.23
[06:40:52] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[06:40:54] PHASE ONE, Encoding
- [06:40:54] Processing: VID_00000 (1 of 39)
- [06:40:54] Multiplexing M2TS
- [06:40:55] CreateBDFiles() 00063 2004
[06:40:58]PHASE ONE aborted by user request
----------------------
[06/05/17] BD Rebuilder v0.50.23
[07:11:20] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[07:11:21] PHASE ONE, Encoding
- [07:11:21] Processing: VID_00000 (1 of 39)
- [07:11:21] Extracting A/V streams [VID_00000]
- [07:13:08] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 97,163 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 11,983 Kbs
- [07:13:08] Reencoding: VID_00000, Pass 1 of 2
- [07:13:09] Reencoding: VID_00000, Pass 2 of 2
- [07:46:20] Video Encode complete
- [07:46:20] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [07:46:25] Multiplexing M2TS
- [07:46:25] CreateBDFiles() 00063 2004
[07:59:06]PHASE ONE aborted by user request
----------------------
[06/05/17] BD Rebuilder v0.50.23
[08:43:23] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[08:43:26] PHASE ONE, Encoding
- [08:43:26] Processing: VID_00000 (1 of 39)
- [08:43:26] Extracting A/V streams [VID_00000]
- [08:45:13] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 97,163 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 11,983 Kbs
- [08:45:13] Reencoding: VID_00000, Pass 1 of 2
- [08:45:14] Reencoding: VID_00000, Pass 2 of 2
- [09:17:55] Video Encode complete
- [09:17:55] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [09:18:02] Multiplexing M2TS
- [09:18:02] CreateBDFiles() 00063 2004
[09:29:22]PHASE ONE aborted by user request

[06/05/17] BD Rebuilder v0.50.23
[09:34:53] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
- Resuming from previously started job.
[09:34:54] PHASE ONE, Encoding
- [09:34:54] Processing: VID_00000 (1 of 39)
- [09:34:54] Multiplexing M2TS
- [09:36:29] Processing: VID_00001 (2 of 39)
- [09:36:29] Extracting A/V streams [VID_00001]
- [09:38:08] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 90,158 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 11,996 Kbs
- [09:38:08] Reencoding: VID_00001, Pass 1 of 2
- [09:38:08] Reencoding: VID_00001, Pass 2 of 2
- [10:07:00] Video Encode complete
- [10:07:00] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [10:07:05] Multiplexing M2TS
- [10:07:05] CreateBDFiles() 00063 2004
[10:09:16]PHASE ONE aborted by user request
[06/05/17] Checking System Settings
- BD-Rebuilder v0.50.23
- Windows Version: 6.1 [7601]
- Working Path Free Space: 257.73GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[06/05/17] Systems Settings Check complete

[jdobbs]

Error 63 is a "bad record number" when reading from a file. Best guess would be a corrupt file.

[AmigaFuture]

During multiplexing? That should happen during extraction and rerendering, only, right?

[jdobbs]

During multiplexing? That should happen during extraction and rerendering, only, right?Not necessarily. I looked at that section of code, indicated by the "2004" in the error message, SUP and IGS files can be manipulated directly (e.g. resizing or making empty). It really only involves a couple of subroutine calls -- and that seems to be the only possibility.

[ggtop]

During multiplexing? That should happen during extraction and rerendering, only, right?

Maybe you came across a regression issue

From the changelog:
April 11th, 2012 - v0.40.9
- Corrected the type of DGDecNV field operation used when IVTC is enabled. This should correct audio sync issues with IVTC/DGDecNV/MPEG-2 pulldown combinations.
- Modified processing so that MULTIPROCESS is not used when the source that are to be processed for inverse telecining.

From your log:
Decoding/Frame serving: DGDecNV [3-way]
...
Inverse Telecining in effect (IVTC)

Does deactivating MULTIPROCESS make any difference?

ggtop

[AmigaFuture]

Checking....nope. I also got around to re-ripping it and...still the same.

[videoh]

Maybe you came across a regression issue...DGDecNV... Or not. No indication of a DG problem. DG has nothing to do with multiplexing. If the poster doubts it, test DG stuff manually, outside of BDRB.

[AmigaFuture]

I also did that before I re-ripped it. Scanned through fine. I had DGIndexNV.exe 2053 save the video and demux audio. Everything went fine.

[videoh]

Do you and of course all others reading this have any experience if DecIM should be avoided in HW mode? I saw my framerates jumping from 80 to 120 fps Only if you want to give up 40fps. Don't worry, be happy.

[videoh]

I also did that before I re-ripped it. Scanned through fine. I had DGIndexNV.exe 2053 save the video and demux audio. Everything went fine. Maybe jdobbs can try to recreate the 63 error. He's usually very kind and diligent about getting disks to try to fix things. A great developer, one for the ages. One special guy.

[AmigaFuture]

I agree. I've changed IVTC_1080i to "0" and see if that's the cause and so far, it's going well.

[videoh]

IVTC? What's being used? TFM/TDecimate? DG fieldop=1? DGTelecide/DGDecimate (CUDA filters)?

Can you give us a sample? Seems maybe strange to be doing IVTC on 1080i.

[AmigaFuture]

I had BD-RB use the hidden option IVTC_1080i=1. I've changed it to 0 now it's going through all using High Speed to test. I wasn't using anything else other than IVTC active in Setup.

[jdobbs]

I had BD-RB use the hidden option IVTC_1080i=1. I've changed it to 0 now it's going through all using High Speed to test. I wasn't using anything else other than IVTC active in Setup.That's confusing. What does that have to do with a failure during multiplexing?

[AmigaFuture]

I don't know yet. If I have BD-RB use IVTC_1080i=1 or disable that and use Inverse Tel with Right Click, it gives an error during multiplexing. I haven't modified the Config much, but I'll try an almost clear Config and see.

What the above meant is that I'm not using added AviSynth scripting stuff as was asked about.

[MrVideo]

Seems maybe strange to be doing IVTC on 1080i.
IVTC is done on 1080i video. That is how 23.976p is converted to 1080i29.97, via 2:3 pulldown on the video fields. If the video is 1080p, then IVTC can't be used, as it cannot contain 2:3 pulldown.

IVTC is done on progressive video when it is 720p59.94.

Too me it would seem correct to use IVTC_1080i=1 when the source is 1080i with 2:3 pulldown at 29.97 frames/sec. I have no idea what setting the option to 0 would do.

[videoh]

1080i refers to pure interlaced, which should not be IVTC'ed. Not worth quibbling about unless your goal is pedantry.

[jdobbs]

IVTC is done on 1080i video. That is how 23.976p is converted to 1080i29.97, via 2:3 pulldown on the video fields. If the video is 1080p, then IVTC can't be used, as it cannot contain 2:3 pulldown.

IVTC is done on progressive video when it is 720p59.94.

Too me it would seem correct to use IVTC_1080i=1 when the source is 1080i with 2:3 pulldown at 29.97 frames/sec. I have no idea what setting the option to 0 would do.It defaults to 0. It's just there for the rare instances where you might need it. An example might be a film recorded from a cable box that has it's output set to 1080i.

[AmigaFuture]

Part 1 of 2.

Config:

[Options]
VERSION=0.50.0.23
ENCODER=0
ENABLE_TEST=1
MULTIPROCESS=3 (This doesn't make any difference...)
IVTC_SELECTION=1
FORCE_ENCODE=0
FORCE_NOENCODE=0
IMPORT_VFR_SCAN=1
IMPORT_VFR_FILM=0
MODE=1
ENCODE_QUALITY=5
ONEPASS_ENCODING=0
AUTO_QUALITY=0
QUICK_EXTRAS=0
ENABLE_BLANKING=1
TARGET_SIZE=23500
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=0
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=1
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=0
AUDIO_DRC=0
DECODER=3
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=1
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=1
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23500
MOVIEONLY_TYPE=34
ALTCRF=23
ALT_TARGET=624
ALT_CRF_TARGET=624
ALTMETHOD=2
ALTAUTOCROP=0
[Paths]
SOURCE_PATH=P:\MONTY PYTHON- ALMOST THE TRUTH\MONTY PYTHON D2\
WORKING_PATH=G:\OUTPUT\
DGIndexNV=C:\Users\User\Desktop\BD_Rebuilder\nVidia\2053\DGIndexNV.exe
DGDecNV=C:\Users\User\Desktop\BD_Rebuilder\nVidia\2053\DGDecodeNV.dll


IVTC_1080i=1 being used.
----------------------
[06/08/17] BD Rebuilder v0.50.23
[07:19:42] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[07:19:44] PHASE ONE, Encoding
- [07:19:44] Processing: VID_00000 (1 of 39)
- [07:19:44] Extracting A/V streams [VID_00000]
- [07:20:59] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 97,163 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 11,287 Kbs
- [07:20:59] Reencoding: VID_00000, Pass 1 of 2
- [07:20:59] Reencoding: VID_00000, Pass 2 of 2
- [07:55:26] Video Encode complete
- [07:55:26] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (eng): Keeping original audio
- [07:55:33] Multiplexing M2TS
- [07:55:33] CreateBDFiles() 00063 2004
[07:55:42]PHASE ONE aborted by user request

[AmigaFuture]

Part 2 of 2.

Now IVTC_1080i=1 is removed and not just switched to 0...
----------------------
[06/08/17] BD Rebuilder v0.50.23
[07:57:19] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[07:57:21] PHASE ONE, Encoding
- [07:57:21] Processing: VID_00000 (1 of 39)
- [07:57:21] Extracting A/V streams [VID_00000]

[......]

- [09:31:38] Reencoding video [VID_00082]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 98 frames
- Bitrate: 1,610 Kbs
- [09:31:38] Reencoding: VID_00082, Pass 1 of 2
- [09:31:38] Reencoding: VID_00082, Pass 2 of 2
- [09:31:40] Video Encode complete
- [09:31:40] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [09:31:40] Multiplexing M2TS
- [09:31:43] Processing: VID_00083 (39 of 39)
- [09:31:43] Extracting A/V streams [VID_00083]
- [09:31:48] Reencoding video [VID_00083]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 98 frames
- Bitrate: 1,895 Kbs
- [09:31:48] Reencoding: VID_00083, Pass 1 of 2
- [09:31:48] Reencoding: VID_00083, Pass 2 of 2
- [09:31:50] Video Encode complete
- [09:31:50] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [09:31:50] Multiplexing M2TS
[09:31:54]PHASE ONE complete
[09:31:54]PHASE TWO - Rebuild Started
- [09:31:54] Rebuilding BD file Structure
[09:31:56] - Encode and Rebuild complete
[09:31:56] JOB: MONTY_PYTHON_D2 finished.
[06/08/17] Checking System Settings
- BD-Rebuilder v0.50.23
- Windows Version: 6.1 [7601]
- Working Path Free Space: 320.58GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[06/08/17] Systems Settings Check complete


BD-RB identifies all the 1080 videos for this BD as 1080i. I've re-ripped the BD a few times now, same error. I'm enabling Interlace now to see if that's playing a role.

[MrVideo]

1080i refers to pure interlaced, which should not be IVTC'ed.
I do it every day. The material I capture is 1080i, with 2:3 telecined video.

That is why 2:3 telecine exists, i.e., to be able to put 23.976p video onto 1080i29.97 video.

To get back to 1080p23.976, it requires doing IVTC of the 1080i video.

[MrVideo]

It defaults to 0. It's just there for the rare instances where you might need it. An example might be a film recorded from a cable box that has it's output set to 1080i.
Or you captured any 1080i video from DBS/cable that has 2:3 pulldown. It doesn't have to be a movie, it could be a drama.

I do not know of any Blu-ray that is released where the source is 23.976/24p and it is converted to 1080i29.97. When it is other than Blu-ray, there are lots of 1080i sources. Prime examples in the U.S. are the OTA networks: CBS, The CW and NBC.

[MrVideo]

BD-RB identifies all the 1080 videos for this BD as 1080i.
What does mediainfo say about the M2TS files?

Please supply the UPC of the Blu-ray.

[videoh]

2:3 telecine exists MrVideo thinks we don't know about hard telecine. Pedantry!

[MrVideo]

MrVideo thinks we don't know about hard telecine. Pedantry!
My response was to your posting about how true 1080i should not be IVTC. That is a very false statement.

I did not say that you, or anyone else, does not know about hard telecine. True 1080i has hard 2:3 pulldown telecine and the only way to remove the 2:3 pulldown, and return the video back to 23.976p, is to IVTC it. That directly contradicts your statement about it.

If you have some other magical way to return 1080i29.97 2:3 pulldown telecine video back to 1080p23.976, without using IVTC, I'm sure that we would all like the read about it.

[videoh]

True 1080i has hard 2:3 pulldown MrVideo believes true interlaced video must be hard telecined film. Nonsense!

[MrVideo]

MrVideo believes true interlaced video must be hard telecined film. Nonsense!
Explain your statement. Provide examples.

[geheim]

Hey jdobbs,
do you have any plans for adding UHD support to BD Rebuilder??

[Sharc]

@MrVideo
Unless I misread your posts it seems to me that you are putting "True interlaced" and "Telecined" somehow into the same "interlaced" basket.

True interlaced
Each frame consists of 2 fields taken at different points in time. Typical for footage shot with video cameras.
It can be re-encoded as interlaced, de-interlaced or bobbed, but NEVER IVTCed.

Telecined
It is NOT true interlaced. It may just use interlacing techniques for framerate conversion (e.g. 24fps film to 29.97fps).
Telecining can be done by
- "Soft telecining" using control flags (like RFF and TFF) which instruct the player how to play the fields and frames during playback (pulldown)
- "Hard telecining": The progressive and "interlaced" frames (with fields form differenst pictures of the original source) are hard coded in the stream.
- A "dumb" variant of telecining is simple frame repetition with horrible judder when played back at 29.97.
Telecined material can be converted to the original film sequence by discarding the flags or by applying IVTC (field matching + decimation). It shouldn't be deinterlaced, (and bobbing is not supported by BD-Rebuilder).

In short: "Telecined" (hard or soft) is totally different from "True Interlaced" and require different treatment. Tools however report hard telecined material typically just as "interlaced" and one needs to analyze the video manually to find out what this really stands for. (Therefore the warning in BD-Rebuilder against forcing IVTC on all "xxxi" sources and to invoke IVTC only when one is 100% positive that the video is telecined, i.e. not "true interlaced". In case of doubt it is better to re-encode hard telecined material as interlaced.)

[Glarioo]

Hey jdobbs,
do you have any plans for adding UHD support to BD Rebuilder??

And how do you rip your UHD Disc to your hard drive? That new copy protection (AACS 2.0) is still not cracked...

[geheim]

And how do you rip your UHD Disc to your hard drive? That new copy protection (AACS 2.0) is still not cracked...

I know that, but I'm not only talking about retail backups. I do have some UHD TV recordings which I'd like to burn to a UHD BluRay via BD-Rebuilder's Import feature.

I don't know any other software for simple UHD authoring, that's why I asked about adding UHD file support to BD Rebuilder.

[Sharc]

Too me it would seem correct to use IVTC_1080i=1 when the source is 1080i with 2:3 pulldown at 29.97 frames/sec. I have no idea what setting the option to 0 would do.
As I understand it, hard telecined material would be encoded as interlaced, unless one forces a deinterlacer to kick in (not recommended). You can however force IVTC for hard telecined material AND add the Deinterlacer_Type=3 (smart deinterlacer) in the .ini for "cleaning up".
Soft telecined 2:3 material can optionally be IVTCed (Settings menu).

[MrVideo]

@MrVideo
Unless I misread your posts it seems to me that you are putting "True interlaced" and "Telecined" somehow into the same "interlaced" basket.
Yes. And here is why:
True interlaced
Each frame consists of 2 fields taken at different points in time. Typical for footage shot with video cameras.
It can be re-encoded as interlaced, de-interlaced or bobbed, but NEVER IVTCed.
Ah, now I see where you are coming from. Our definitions of true interlaced are different. I can find no definition online that indicates that interlacing is reserved for only video from cameras and cannot contain 2:3 pulldown material. Many examples shows 2:3 pulldown telecine being saved to interlaced video. I actually have been capturing video from a company that is using repeat frame conversion to interlaced video, i.e., every 4th frame is repeated. I have no idea why they do that. The AVISynth IVTC plugins will work on that material as well, but I prefer to use SelectEvery() as that takes less processing time (therefore quicker).

Actually, for today's television and movie production, film is hardly ever used anymore. There are some films still shot on film, but no TV shows that I know of. So, telecining isn't done anymore, at least via the definition of telecining. The conversion of 23.976p video to 29.97i video is all done electronically. But, you already know that. IVTC is an old term that will stick around, as "inverse 2:3 pulldown" (I23P) isn't really going to stick. :D
- "Hard telecining": The progressive and "interlaced" frames (with fields form differenst pictures of the original source) are hard coded in the stream.
There is zero, I repeat zero, progressive frames in broadcast video. The video is 100% interlaced, i.e., true interlaced. Out of every 5 frames, it just appears that 3 of the interlaced frames are progressive. The same holds true for most of the DBS/Cable 1080i channels. As such, the true interlaced video contains 23.976 2:3 pulldown material. Video which I IVTC all the time.

HBO is the only one that I know of that tends to use "soft telecining." Those posted captures show up in VideoReDo with special markers showing where the pulldown flags are.

[MrVideo]

As I understand it, hard telecined material would be encoded as interlaced.
Correct. The only way that 23.976 2:3 pulldown can be done on 29.97 frame/s video is when the video is true interlaced. 720p59.94 video, on the other hand, has 2:3 pulldown applied to the progressive frames, where every 10 progressive frames contain 4 source 23.976 frames.

[malves]

Just click on "Donations" in the signature block below.

Thanks for thinking about me...

[Edit] I'm late with my answer again... this is becoming a habit.

There is a site for internet business that you can use other then Paypal. It is called Stripe at stripe.com. They get good reviews and handle large or small business accounts. Take a look and see what you think.

[AmigaFuture]

The BD I'm processing is called "Monty Python: Almost the Truth - The Laywer's Cut"...

I went back a few version of BD-RB using the same Config. Each did as I replied with until 50.14 which doesn't have IVTC_1080i=n added.

[06/09/17] BD Rebuilder v0.50.14
[07:48:15] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[07:48:17] PHASE ONE, Encoding
- [07:48:17] Processing: VID_00000 (1 of 39)
- [07:48:17] Extracting A/V streams [VID_00000]
- [07:49:37] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 97,163 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 11,287 Kbs
- [07:49:37] Reencoding: VID_00000, Pass 1 of 2
- [07:49:37] Reencoding: VID_00000, Pass 2 of 2
- [08:13:28] Video Encode complete
- [08:13:28] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (eng): Keeping original audio
- [08:13:34] Multiplexing M2TS
- [08:13:34] CreateBDFiles() 00063 2004
[10:07:28]PHASE ONE aborted by user request

Which does the same thing. So, I'm checking into it more as I create the time to do so.

[ggtop]

Only if you want to give up 40fps. Don't worry, be happy.

Thank you for your Feedback.

ggtop

[ggtop]

Quote:
Originally Posted by ggtop View Post
Maybe you came across a regression issue...DGDecNV...

Or not. No indication of a DG problem. DG has nothing to do with multiplexing. If the poster doubts it, test DG stuff manually, outside of BDRB. Or not. No indication of a DG problem. DG has nothing to do with multiplexing. If the poster doubts it, test DG stuff manually, outside of BDRB.

Hi,

I have full respect of your work on DGDecNV and I use it personally with great results, but for the records: You are not understanding and quoting me incorrectly. I didn't say with any word it could be a problem with DGDecNV itself. I highlighted a potential issue with MULTIPROCESS and the way DGDecNV is called within BDRB.

ggtop

[videoh]

Thanks for the clarification, ggtop. Just wanted to avoid possible confusion. You've made great contributions!

[Sharc]

There is zero, I repeat zero, progressive frames in broadcast video. The video is 100% interlaced, i.e., true interlaced. Out of every 5 frames, it just appears that 3 of the interlaced frames are progressive.

Sure, and this is why I wouldn't call it "true interlaced" because the 2 fields of the "progressive looking" frames are taken from the same original film picture i.e. from the same point in time.
And yes, "true interlaced" may not be an official term. Nevertheless I like it and use it to distinguish "true interlaced video" from "progressive video using interlacing principles", like telecining.

[MrVideo]

Sure, and this is why I wouldn't call it "true interlaced" because the 2 fields of the "progressive looking" frames are taken from the same original film picture i.e. from the same point in time.
And yes, "true interlaced" may not be an official term. Nevertheless I like it and use it to distinguish "true interlaced video" from "progressive video using interlacing principles", like telecining.
You are going to love this. There is widespread industry use of 1080i 29.97 progressive segmented frame (psf or pf), where they shoot 23.976 onto 1080i29.97, not using 2:3 pulldown, but psf. So, your "progressive video using interlacing principles" is the industry's term for psf.

There are several professional editing systems that can deal with psf video.

You and I will never see psf video in the consumer arena.

As far as the industry is concerned, 1080i29.97 is interlaced, no matter if the video is from a 1080i/p camera, 2:3 pulldown of 23.976p video or repeat frame from 23.976p video.

[MrVideo]

The BD I'm processing is called "Monty Python: Almost the Truth - The Laywer's Cut"...
BTW, it is Lawyer. :eek:

Is this the U.K. or U.S. release?

You will not be able to IVTC this because the source of this is from the BBC documentary, which was shot at either 1080i25 or 1080p25.

The U.K. release will be interlaced @ 50 fields/sec., as required by the Blu-ray specification.

The U.S. release might be either 1080i29.97 or 1080p29.97. depending on how the documentary was shot.

IMHO, your only choice is to leave it at whatever format is on the Blu-ray.

[videoh]

You and I will never see psf video in the consumer arena. There are many consumer-grade cameras, ranging from DV to AVCHD, that shoot PSF. Canon makes several of them and we even have threads about them here.

[MrVideo]

I wasn't googling PsF. I was talking about 1080i23.976 PsF (sometimes labeled on tape slates as 23.98 PsF).

But, I did do a little looking and Canon seems to only use PsF on their 29.97p frame rate. If the camera is switched to 24p, it is true 24p.

Is there a consumer 23.976 PsF camera?

[AmigaFuture]

BTW, it is Lawyer. :eek:

Is this the U.K. or U.S. release?

You will not be able to IVTC this because the source of this is from the BBC documentary, which was shot at either 1080i25 or 1080p25.

The U.K. release will be interlaced @ 50 fields/sec., as required by the Blu-ray specification.

The U.S. release might be either 1080i29.97 or 1080p29.97. depending on how the documentary was shot.

IMHO, your only choice is to leave it at whatever format is on the Blu-ray.

U.S. release. Yeah, it was a typo I missed and I usually notice them all before clicking Submit Reply. Oh, well, the Earth is still spinning...and there are still many cellphone users who don't use any capitalization or punctuation in the world, hehe.

I started using IVTC_1080i=1 because I was testing it before checking if it's truly Interlaced or not. It wasn't a big deal, and I wasn't sure if it was BD-RB or not. But then I noticed the bug / problem and I'm trying to find what's causing that.

Since all the files are showing their sizes correctly...and if I have BD-RB exit, and start again...it still stops because of that error. I'll clean by BD LG drive and see if that produces a better rip, if that's it.

[Sharc]

....I started using IVTC_1080i=1 because I was testing it before checking if it's truly Interlaced or not. It wasn't a big deal, and I wasn't sure if it was BD-RB or not. But then I noticed the bug / problem and I'm trying to find what's causing that.....
So you are positive that the source which fails after IVTC during multiplexing is (hard)telecined, right?
Something which comes to my mind: Is it possible that the telecine cadence is badly broken or otherwise borked (e.g. by poor editing after telecining) and hence the IVTC algo is fooled leaving a stream which no longer is in synchronism with the audio, and hence the muxer throws an error? Just speculating.....

You could also change the IVTC algo and see if this makes a difference. In the .ini:
IVTC_METHOD=n #n = 0/1 = Default=1, 1=Use TIVTC for IVTC, 0=Use DECOMB for IVTC

Can you upload a few seconds of the source?

[Sharc]

You are going to love this. There is widespread industry use of 1080i 29.97 progressive segmented frame (psf or pf), where they shoot 23.976 onto 1080i29.97, not using 2:3 pulldown, but psf. So, your "progressive video using interlacing principles" is the industry's term for psf.
Oh yes, I love it. So there is an official term "PSF" for what I tried to
describe. I added it to my video vocabulary. Thanks!

Edit:
And how would you call and process this clip for playback on a progressive monitor?
http://www.mediafire.com/file/b770wew9m5rrc7b/ma_576i25.mkv

[MrVideo]

Is it possible that the telecine cadence is badly broken or otherwise borked
See my post above about this BD release. There is no telecine. The source is 25 frames/sec., from the BBC. It is standards converted to 29.97 fps.

As a side note: I try and buy anything that I want that was produced overseas at 25 fps, from amazon.co.uk, so that I get the original frame rate. That specifically includes all Doctor Who releases: BD and DVD.

[MrVideo]

Oh yes, I love it. So there is an official term "PSF" for what I tried to
describe. I added it to my video vocabulary. Thanks!
Actually it is PsF. My bad for using "psf" before.
And how would you call and process this clip for playback on a progressive monitor?
The source is 576/50i. Personally I would leave it alone and let the monitor do the work. If you deinterlace it and delete the original, you can never go back. There are those that I know that cannot stand the "jaggies" as a result of interlacing and deinterlace the video.

So, if you keep the original, you can deinterlace it yourself and produce a 576p25 video. The AVISynth plugins will handle it just fine.

[Sharc]

The source is 576/50i. Personally I would leave it alone and let the monitor do the work. If you deinterlace it and delete the original, you can never go back. There are those that I know that cannot stand the "jaggies" as a result of interlacing and deinterlace the video.

So, if you keep the original, you can deinterlace it yourself and produce a 576p25 video. The AVISynth plugins will handle it just fine.
Well well well ...... hold your horses and save your breath. :D
It's actually what one may call "field shifted progressive video" (or similar, if there exists an official term for it).
The ONLY correct way to restore the original is to apply Field Matching, for example TFM(), without decimation. Such material should NOT be deinterlaced (although some deinterlacers may produce more or less acceptable results, but try yourself).
To be honest, I recently fell terribly on my belly when I wanted to test and compare various deinterlacers on such "interlaced" footage, until a forum member (guess who) asked the question whether I am positive that this is really "True Interlaced".....

I posted this crap just to demonstarte how misleading "interlaced" alone can be..... But never mind (hopefully) ;)

[AmigaFuture]

@Sharc

Along that line "..how misleading 'interlaced' alone can be.." which is why I was using IVTC_1080i=1 with Setup's IVTC active. That was it, I didn't change any other settings. I figured that would probably result in what I was expecting. Then I noticed the other error, and thought it was related.

Interestingly, I loaded VideoTV Suite V5 and drug the 00000.m2ts from the ripped but not yet processed D2 on it and VideoTV Suite crashed. I thought that interesting, so loaded it again and drug the same file from a rerendered BD25 (without IVTC_108i=n), and it read it in fine. It might not mean much, I was surprised it crash since it handles most stuff very well.
Anyway, BD-RB handles the Monty Python BD files fine when I don't have IVTC_1080i=1 in use and doesn't present that error. Not meaning IVTC_1080i=n IS the error, I don't know what is at the moment. All file sizes are fine..

[MrVideo]

It's actually what one may call "field shifted progressive video" (or similar, if there exists an official term for it).
The ONLY correct way to restore the original is to apply Field Matching, for example TFM(), without decimation. Such material should NOT be deinterlaced (although some deinterlacers may produce more or less acceptable results, but try yourself).
Damn, that is very hard to see in the editing program that I use. Very easily missed.
To be honest, I recently fell terribly on my belly when I wanted to test and compare various deinterlacers on such "interlaced" footage, until a forum member (guess who) asked the question whether I am positive that this is really "True Interlaced".....
As pointed out in other postings, there really isn't a term called "true interlaced," other than to say that the video is 100% interlaced, no matter to content. VideoReDo declares it as interlaced (MBAFF). There is progressive video, and there is interlaced video. There is no inbetween.
I posted this crap just to demonstarte how misleading "interlaced" alone can be..... But never mind (hopefully) ;)
Progressive video converted to interlaced video, poorly, is still interlaced video. It is very unfortunate that the user that has the video has to know that it is screwed up. You just can't tell by quickly looking at it.

I have a bunch of DVCAM tapes that were recorded Sony DSR-20 decks. The sync detection was screwed up to the point that if I wasn't watching correctly, the A & B fields of a frame would get placed across two frames. While the video would play correctly at speed (downshifted one line), editing was a bitch because originally the edits were on frame boundaries, but now that boundary was spread across two consecutive frames. If I ever need to use the video on any of those tapes, I'll have to run it through AVISynth in order to correct it. But, at this point in time I have no need.

I do not know what the exact settings for TFM() would be to restore this video. If you have them, I'd like to try it in order to see the results.

[MrVideo]

BD-RB handles the Monty Python BD files fine when I don't have IVTC_1080i=1 in use and doesn't present that error. Not meaning IVTC_1080i=n IS the error, I don't know what is at the moment. All file sizes are fine..
As pointed out, since the source is 25 fps, IVTC_1080i=1 should not be there, since there isn't any 2:3 pulldown to IVTC. Using it should only result in video that just doesn't look right. It certainly shouldn't cause any errors.

[videoh]

It is very unfortunate that the user that has the video has to know that it is screwed up. You just can't tell by quickly looking at it. You want some metadata that declares "this video is screwed up"?

Actually, one can tell quickly by looking at it. You have to separate the fields and step through by field. Then, people with experience can immediately recognize the patterns.

With all due respect, it's pretty clear that you are lecturing us without that experience. Blind leading the blind! I wish I had time to correct more of your misconceptions.

[MrVideo]

Actually, one can tell quickly by looking at it. You have to separate the fields and step through by field.
The video editing software that I have does not allow stepping through by fields, only frames. At first glance it looks like a video that was produced @ 59.94 fields a second.

Hell, I don't even think that Adobe Premiere allows field stepping. It never did when i was using it way back when.

And what makes you think that you do not have misconceptions?

[AmigaFuture]

As pointed out,

Then why point to it again?

I decided to use IVTC_1080i=1 because I wanted to confirm something for myself. Weird stuff and all that is possible. I disabled all SUP. This is what happened.

[06/10/17] BD Rebuilder v0.50.23
[16:12:38] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[16:12:40] PHASE ONE, Encoding
- [16:12:40] Processing: VID_00000 (1 of 39)
- [16:12:40] Extracting A/V streams [VID_00000]
- [16:14:56] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 97,163 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 11,287 Kbs
- [16:14:56] Reencoding: VID_00000, Pass 1 of 2
- [16:14:56] Reencoding: VID_00000, Pass 2 of 2
- [16:48:26] Video Encode complete
- [16:48:26] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (eng): Keeping original audio
- [16:48:31] Multiplexing M2TS
- [16:49:39] Processing: VID_00001 (2 of 39)
- [16:49:39] Extracting A/V streams [VID_00001]
- [16:52:05] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 90,158 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 11,302 Kbs
- [16:52:05] Reencoding: VID_00001, Pass 1 of 2
- [16:52:05] Reencoding: VID_00001, Pass 2 of 2
- [17:21:13] Video Encode complete
- [17:21:13] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (eng): Keeping original audio
- [17:21:19] Multiplexing M2TS

[...]

- [19:09:50] Processing: VID_00083 (39 of 39)
- [19:09:50] Extracting A/V streams [VID_00083]
- [19:09:55] Reencoding video [VID_00083]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 98 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 1,895 Kbs
- [19:09:55] Reencoding: VID_00083, Pass 1 of 2
- [19:09:55] Reencoding: VID_00083, Pass 2 of 2
- [19:09:58] Video Encode complete
- [19:09:58] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [19:09:58] Multiplexing M2TS
[19:10:02]PHASE ONE complete
[19:10:02]PHASE TWO - Rebuild Started
- [19:10:02] Rebuilding BD file Structure
[19:10:05] - Encode and Rebuild complete
[19:10:05] JOB: MONTY_PYTHON_D2 finished.


Then the only change is, enabled all English...SUP.

[06/10/17] BD Rebuilder v0.50.23
[20:23:17] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[20:23:19] PHASE ONE, Encoding
- [20:23:19] Processing: VID_00000 (1 of 39)
- [20:23:19] Extracting A/V streams [VID_00000]
- [20:25:35] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 97,163 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 11,287 Kbs
- [20:25:35] Reencoding: VID_00000, Pass 1 of 2
- [20:25:36] Reencoding: VID_00000, Pass 2 of 2
- [20:58:59] Video Encode complete
- [20:58:59] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (eng): Keeping original audio
- [20:59:05] Multiplexing M2TS
- [20:59:05] CreateBDFiles() 00063 2004
[20:59:23]PHASE ONE aborted by user request


All files look to be there and all sizes look to be valid.

[Sharc]

I decided to use IVTC_1080i=1 because I wanted to confirm something for myself. Weird stuff and all that is possible. I disabled all SUP. This is what happened..............

So it looks like the subtitles caused the conflict with the falsely (your experimentally) applied IVTC which changed the framerate of the video (decimation).
Anyway, I understand when you run BD RB with its default settings all is ok, right?

As a sidenote, if the BBC original was produced as 25i there is actually no need to convert it to 29.97i because 25i is perfectly blu-ray compliant even when upscaled to 1080i. So I wonder how the movie "benefited" from this unnecessary framerate conversion. But apparently the industry still locks some blu-ray players from playing 25 fps material. Oh well .....

[videoh]

The video editing software that I have does not allow stepping through by fields, only frames. MrVideo does not know about Avisynth and VirtualDub.

[Sharc]

Just to mention shekh's VirtualDub FilterMod based on 1.10.5 with some very useful extensions, e.g. wrt. video formats
https://sourceforge.net/projects/vdfiltermod/

[Sharc]

I do not know what the exact settings for TFM() would be to restore this video. If you have them, I'd like to try it in order to see the results.
It's as simple as this for this clip:
TFM()

alternatively, you may also want to try
telecide()

or in case you are using DGDecNV
DGTelecide()

[MrVideo]

As a sidenote, if the BBC original was produced as 25i there is actually no need to convert it to 29.97i because 25i is perfectly blu-ray compliant even when upscaled to 1080i. So I wonder how the movie "benefited" from this unnecessary framerate conversion. But apparently the industry still locks some blu-ray players from playing 25 fps material. Oh well .....
AFAIK, this was a 1080 production, not 576 upscaled to 1080.

I do not know of any Blu-ray players that are locked from playing 25 fps material. That said, I've not researched it either. I buy Samsung players. There are some monitors that do not, so that can cause an issue. But, pretty much anything these days will handle 25 fps material. That still doesn't stop the companies that release material that was originally 25 fps as 29.97 fps for the U.S. That is why I buy the U.K. releases so that I can keep the original frame rate.

[MrVideo]

MrVideo does not know about Avisynth and VirtualDub.
I just haven't used that combo in years. Never thought to use it in this case. I should have suspected something fishy as to why that video was being offered up for inspection. :D

[MrVideo]

Just to mention shekh's VirtualDub FilterMod based on 1.10.5 with some very useful extensions, e.g. wrt. video formats
Thanks, I've downloaded it. I hoping it can deal with H.264/4.2.2 video. CBS/CW network is now in the process of changing over their network feeds from MPEG2/4.2.2 to H.264/4.2.2. I can view the video with VLC, but can't currently edit and convert to H.264/4.2.0.

[MrVideo]

It's as simple as this for this clip:
TFM() [...]
I thought that not having any options (other than the defaults), was too easy. So, I asked.

[videoh]

CBS/CW network is now in the process of changing over their network feeds from MPEG2/4.2.2 to H.264/4.2.2. Please cite your source for this. Thank you. Are you possibly confusing internal feeds with what is actually broadcasted? If you are talking about internal feeds, it's hardly relevant to the average person capturing video from a broadcast.

I can view the video with VLC, but can't currently edit and convert to H.264/4.2.0. I suppose again you never thought to use Avisynth with an appropriate source filter.

[Sharc]

I just haven't used that combo in years. Never thought to use it in this case.....
How could you survive in the video world without these? :eek:

[Sharc]

Thanks, I've downloaded it. I hoping it can deal with H.264/4.2.2 video.....
Menu Video/Decode format .....

[videoh]

Simply cropping the first field will also match the fields on that sample, because the field shift is constant throughout.

[MrVideo]

Please cite your source for this. Thank you. Are you possibly confusing internal feeds with what is actually broadcasted?
Key words: network feeds.

This means the satellite transmission from NY to the affiliates. I receive those feeds on my 12' BUD. Yes, it has a limited scope of users.
I suppose again you never thought to use Avisynth with an appropriate source filter.
The nVidia card that I have doesn't support H.264/4.2.2, so I can't frame serve it to AVISynth via DGDecNV.

[MrVideo]

How could you survive in the video world without these? :eek:
Ever heard of VideoReDo?

[videoh]

I can't frame serve it to AVISynth via DGDecNV. There are other source filters.

[MrVideo]

There are other source filters.
I've never needed to have to look into them before. If you have any suggestions, please pass them along.

[videoh]

If you have any suggestions, please pass them along. Take up knitting?

[MrVideo]

Take up knitting?
I guess I needed to be more specific in my request. :eek: