BD Rebuilder Beta - Bug Reports Only

[MrVideo]

I really don't care if you disagree. You are totally wrong. But, hey, if you want to pretend to be an expert despite my advice -- go ahead. But when you move on to a different player and it stops working, just remember what I said.
I am not wrong. It can work and does work. I've loaned a couple of these authored discs to a friend, who has a totally different BD player and they worked for him. Today's players are very forgiving, because they play so many other files. It stands to reason that they would play authored discs with video files that may not be 100% compliant. So what. If I pulled out the old Sony player, they might not work. Don't care. It didn't play a lot of other stuff either.

I just played one of the discs in my pre-Cinavia (over 5 yrs old) Samsung and it played the disc just fine. Could be luck. Don't know, don't care.

The point is that if it works for you, go for it. Whenever you can NOT recode, the better off the video file is, as encoding errors are introduced with each recode. Especially with the lower bitrates that come with many files.

Have I run across some videos that didn't work? Yes. Those were recoded. But, they are very few are far between.

If it ever happens that the disc won't play in a different player, then redo it and recode. Since the videos on the disc weren't recoded previously for the disc, they won't have gone through a double-recoding to make another disc.

The thing about BD specs is that the players have to play discs that meet those specs. Doesn't mean they can't play discs that don't. Seems that many players will play pretty much anything.

[jdobbs]

I am not wrong. It can work and does work. I've loaned a couple of these authored discs to a friend, who has a totally different BD player and they worked for him. Today's players are very forgiving, because they play so many other files. It stands to reason that they would play authored discs with video files that may not be 100% compliant. So what. If I pulled out the old Sony player, they might not work. Don't care. It didn't play a lot of other stuff either.

I just played one of the discs in my pre-Cinavia (over 5 yrs old) Samsung and it played the disc just fine. Could be luck. Don't know, don't care.

The point is that if it works for you, go for it. Whenever you can NOT recode, the better off the video file is, as encoding errors are introduced with each recode. Especially with the lower bitrates that come with many files.

Have I run across some videos that didn't work? Yes. Those were recoded. But, they are very few are far between.

If it ever happens that the disc won't play in a different player, then redo it and recode. Since the videos on the disc weren't recoded previously for the disc, they won't have gone through a double-recoding to make another disc.

The thing about BD specs is that the players have to play discs that meet those specs. Doesn't mean they can't play discs that don't. Seems that many players will play pretty much anything.That's just about the dumbest argument I have ever heard. Standards are there for a reason -- and have to be followed whether you, me, or anyone else likes it. Players are built to play discs that meet the blu-ray standard. Dumb-ass luck isn't the same thing as "right". Get over yourself and accept the fact that you are wrong. I know you hate being wrong -- but when you make up silly reasons like this rather than accept it -- you simply lose all credibility.:rolleyes:

[Ch3vr0n]

I'm with jdobbs on this one. Just because it plays because the player is "configured" to be less strict when it comes to playing files doesn't mean the files are up to the standard which the player should be ENFORCING instead of being less strict.

[MrVideo]

I'm with jdobbs on this one. Just because it plays because the player is "configured" to be less strict when it comes to playing files doesn't mean the files are up to the standard which the player should be ENFORCING instead of being less strict.
No reason to enforce. If the only thing the BD player did was to play CDs, authored DVDs and authored BDs, then I can understand that. But, they play pretty much everything under the sun and even stream from YouTube, Netflix, etc. Because of that, the player has to have hardware chipsets that will play pretty much any MPEG-2/MPEG-4 file thrown at it, Because that hardware is already there, by default, playback of BDs results in a broader spectrum of allowable videos.

You and jdobbs may consider that to be wrong, but that is the state of the world when it comes to players. Because of that, I take advantage of it. Doesn't mean that others can't either. Doesn't make me wrong for using the ability of the device.

[MrVideo]

That's just about the dumbest argument I have ever heard. Standards are there for a reason -- and have to be followed whether you, me, or anyone else likes it.
For someone who has to author discs that will play on ANY BD player, that is true. But, for those of us who can think outside of the box and use the features that the player has, it is another story. I like using the capabilities of the devices that I have.

[jdobbs]

For someone who has to author discs that will play on ANY BD player, that is true. But, for those of us who can think outside of the box and use the features that the player has, it is another story. I like using the capabilities of the devices that I have.OMG! Give it up. Violating standards isn't "thinking outside the box". Gee... maybe I'll make a yard 33 inches for my own personal usage. Sound stupid? That's because it is. With every response you dig yourself deeper into the "maybe I'm speaking goofy" category.

Standards are the only thing that separates order from chaos in science and engineering. Chaos is not "thinking outside the box". It's just chaos.

[MrVideo]

Nope. You should give up trying to convince me what I am doing is so wrong.

We can certainly agree to disagree.

Added: You seem to be completely missing the point. The Samsung player, as are most BD/DVD/CD players these days, are not just BD/DVD/CD players. They are MEDIA players. With the "media" coming in all shapes and forms. Because of that, it can, and does more. And I take advantage of that.

I can put those same MKV files on a BD-ROM and the Samsung will play them as if I had them on a flash drive. It is just nice to have a menu wrapped around those files, with a nice image background.

[AmigaFuture]

For someone who has to author discs that will play on ANY BD player, that is true. But, for those of us who can think outside of the box and use the features that the player has, it is another story. I like using the capabilities of the devices that I have.

You're missing the Bigger Picture.. That's what Sharc, JD, are commenting about. Those "Extra features" like YouTube and Netflix programs, don't have ANYthing to do with the Standards of playing BD. My older LG BD Player has the abilities to play MKV files also but that's outside the BD Standard specs. I'm very glad it does, it's an added bonus. Plays from USB, Data DVD and Data BD, but but doesn't have to do with BD standards. How a BD is played IS then referencing the standard.
From what I understand, the ability to play MKV files on a disc or USB..it's using different software than BD specific. Which is why JD really is so "anal" (Ahhh..pun from before) about not supporting (much) outside of the BD Specifications and is pretty ridged about Does It Play Correctly From disc??!?

This seems to be what you were missing. I hope it's helpful. Outside the Box is a form of thinking, of allowing yourself not to become ridged in Beliefs (long held patterns of thought) that CAN change from unhealthy to healthy are better awareness. It's not a Hardware related statement; nor BD related topic.

[MrVideo]

This seems to be what you were missing.
No, I'm not missing that point, and said so in an above posting.

The "final" output from BDRB needs to fit the spec so that it will play on "every" BD player. And no, the player doesn't have to switch to a mode that will only play discs that meet the spec, otherwise it would refuse to play the discs that I've created. It doesn't.

The intermediate BDMV file layout that BDRB produces meets the spec for menu playback, so that the BD player will read and display the menu. The MPEG-2/MPEG-4 video files may not meet the BD spec, but they must meet the MPEG-2/MPEG-4 spec, which allows the player to play those files.

Let's make another example. You purchased Adobe Photoshop in order to create background images for BDRB. Adobe writes that you need, at a minimum, a certain processor type and speed. A minumum amount of RAM, minimum video display resolution and a minimum amount of HDD space in which to load the program and be able to work with images. That doesn't stop you from having a computer with capabilities that are many times better than the spec. Does that mean when you run Photoshop you only run on a computer with the minumum specs? Nope. Same thing with a BD player. It meets the minimum specs to play authored discs, but doesn't stop it from playing BD discs with non-BD spec MPEG-2/MPEG-4 videos because the player can.

It is my responsibility to determine if the player can play the intermediate BDMV file structures that BDRB produces.

I'm pleased that the BD players that I have can play the BDRB intermediate BDMV file structures. That way I can have discs with menus, without having to recode the videos and degrade the quality of the video files.

[AmigaFuture]

I understand your reasoning and example. My older LG BD Player also plays outside of the Specs. Short example, I don't have to name the BD "THIS_IS_THE_NAME". I'm able to call it "This Is The Name" or "this is the name". But I prefer better grammar and punctuation; however I don't use punctuation within a BD name. So, you're meaning "tHIS is tHE nAME" is outside of BD specs but it still plays. I concur. I also really like that. BUT...JD, with BD-RB, is being strict to the Guidelines of BD. That's his point. YOU understand those, at least in part, as well as I do, in part, but many Do Not. His communication and program are aimed at those who Don't...and quotes Specific to avoid a LOT of possible headaches. Get it? :D

[Lathe]

C'mon, let me at 'im JD... Let me at 'im... Just give me 5 minutes with him man...

http://lathe-of-heaven.com/club.gif

[jdobbs]

Some people just won't admit when they are wrong. This guy is one of them. It's a character flaw, and we're not going to solve it here. Just remember this discussion the next time he is giving someone advice... take it with a grain of salt.

[gonca]

Some people just won't admit when they are wrong. This guy is one of them. It's a character flaw, and we're not going to solve it here. Just remember this discussion the next time he is giving someone advice... take it with a grain of salt.

You talking about Lathe?:rolleyes::rolleyes:

[MrVideo]

Some people just won't admit when they are wrong.
Look in the mirror. Obviously I'm not wrong if it works.

If I were to tell someone to do this, or that, and that it works, but really doesn't... then I would be wrong. But to tell someone that the process can work, because it does, doesn't make me wrong.

I must be seeing things when I watch the result of doing what I suggested. It never hurts to try. If it doesn't work for you, at least you can say you gave it a go.

[jdobbs]

Sure, sure... You prove the point with every post. Blah, blah, blah, silly ass statement, blah, blah, blah. Get over yourself.

I actually know what I'm talking about. You... not so much.

"Gee... it works sometimes, so it must be right" :eek: That's not how a professional engineer thinks.

[MrVideo]

You are totally missing the point. The BD specs, as stated many a time, are the minimum specs that a BD player must adhere to. Nothing stops them from going further, as pretty much every BD player on the market does. Try and tell a BD manufacturer that their BD player is not adhering to the BD specs. They will all tell you that they are.

If I were to use BDRB to produce a BD disc that I would end up selling to the general public and I ended up using the temporary BDMV file structure, then you would be very correct in that the BD disc might not be compliant and should not be sold.

But, I am not doing that. I am taking full advantage of what the BD player can do and creating a BD disc for me, myself and I. Therefore, it can be anything that the BD player that I own will accept. That does not make me wrong regarding what I posted a while ago that got all of this started. You said that it can't be - zero. Well, tell that to my BD player. It is perfectly happy playing the "can never happen" and "zero chance" disc.

I will continue to create discs that I supposedly shouldn't be able to, and play them in my BD player, that shouldn't be able to do so. I will continue to suggest to users to give it a try with their players, in order to avoid a recoding that will potentially degrade the quality of the video.

[Lathe]

Quote:

Originally Posted by jdobbs

Some people just won't admit when they are wrong. This guy is one of them. It's a character flaw, and we're not going to solve it here. Just remember this discussion the next time he is giving someone advice... take it with a grain of salt.

You talking about Lathe?:rolleyes::rolleyes:

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

[jdobbs]

You are totally missing the point. The BD specs, as stated many a time, are the minimum specs that a BD player must adhere to. Nothing stops them from going further, as pretty much every BD player on the market does. Try and tell a BD manufacturer that their BD player is not adhering to the BD specs. They will all tell you that they are.

If I were to use BDRB to produce a BD disc that I would end up selling to the general public and I ended up using the temporary BDMV file structure, then you would be very correct in that the BD disc might not be compliant and should not be sold.

But, I am not doing that. I am taking full advantage of what the BD player can do and creating a BD disc for me, myself and I. Therefore, it can be anything that the BD player that I own will accept. That does not make me wrong regarding what I posted a while ago that got all of this started. You said that it can't be - zero. Well, tell that to my BD player. It is perfectly happy playing the "can never happen" and "zero chance" disc.

I will continue to create discs that I supposedly shouldn't be able to, and play them in my BD player, that shouldn't be able to do so. I will continue to suggest to users to give it a try with their players, in order to avoid a recoding that will potentially degrade the quality of the video.Wrong. Wrong. Wrong. I know it's easy to get off point when you're grasping at straws to defend yourself, but let me remind you of the real issue. It's not what you personally do. I really don't give a rat's ass what you do. It's when you come in and advise others to ignore the standards (required for discs to work) in direct contradiction to the correct advice I gave them.

Next time I give advice to someone -- how about you simply stay out of it. You are telling people to do something that is COMPLETELY WRONG. Leave the advice to the knowledgable, ok. You obviously aren't.

Now this is where the moderator comes in. This thread isn't about you trying to defend your bad advice, and it's obvious you aren't going to stop coming up with silly reasons why you weren't wrong. The thread is about Rebuilder, the software I created. As a moderator I'm telling you to stop posting on this subject now -- or you will receive a strike. In addition, I will remove any posts you continue to make on this subject.

[Lathe]

I'm just finishing up The Avengers television episodes and I'm currently encoding disc 9 of the last season, and I notice that under the settings tab the encoding choices are 'live' and are not greyed out. In other words, it LOOKS like if I wanted to do so, I could change 'High' to 'Fast' mid-encode.

The reason why I wondered this is because I have it set using 'High' 1 pass CRF and it uses pretty decent values for the episodes. But, since it is an episode disc, I cannot really set it for a 'faster encode of extras' due to there being several episodes. However, if the encoding of all the main episodes is already done and it is just doing the rest of the 'extras', could I in mid-encode, just change the setting to 'Fast' for BDRB then to do the rest of the extras 'faster' Is that possible, or recommended, or will it somehow screw up the current disc or reset the whole thing or whatever...?

[Lathe]

Oh, and in using 1 pass CRF, I notice something that I hadn't before that BDRB occasionally does a 'performing size correcting 2nd pass' Never noticed that before...

[AmigaFuture]

My acquaintance, you're not the only one. I noticed the Encoding Speeds thing a while ago, but kept thinking "I'll check that soon." Which I still haven't done. Once the encode I have happening is done I'll check that (Giggling about the comment I _just_ typed).

Since you're using an episode BD, have you noticed the "Current Progress" changes to reflect the actual progress and current render progress? I was borrowed a friends' BD set and thought I would check some stuff since I don't have much in the way of episodes stuff. I noticed that, what about you, Lathe? I don't have "Quick Encode" set.

[Lathe]

My acquaintance, you're not the only one. I noticed the Encoding Speeds thing a while ago, but kept thinking "I'll check that soon." Which I still haven't done. Once the encode I have happening is done I'll check that (Giggling about the comment I _just_ typed).

Since you're using an episode BD, have you noticed the "Current Progress" changes to reflect the actual progress and current render progress? I was borrowed a friends' BD set and thought I would check some stuff since I don't have much in the way of episodes stuff. I noticed that, what about you, Lathe? I don't have "Quick Encode" set.

I'm not quite sure what you are asking, but since in an episode disk where you have multiple 'main' files, I don't think that there is a way to use 'faster encode for extras', because if you did, BDRB would simply choose the largest episode file, make IT the 'main' file, and then use a faster encode on everything else, including the other episodes.

I had just noticed with doing this last Avengers disc, that the settings were still 'live', which surprised me. Normally, I THOUGHT they were all greyed out while encoding was taking place. So, I was curious if you could change the encoder setting (High, Fast, etc.,) on the fly WHILE it was encoding one of the files...

[jdobbs]

Oh, and in using 1 pass CRF, I notice something that I hadn't before that BDRB occasionally does a 'performing size correcting 2nd pass' Never noticed that before...The best you can do with CRF is an estimate of the output size. Sometimes it is off. When the output is too large, a second pass has to be done in order to make sure it will fit on the target. This isn't something new -- BD-RB has had that feature for a long time. It just isn't used very often (since the estimation passes are usually pretty accurate).

[Lathe]

The best you can do with CRF is an estimate of the output size. Sometimes it is off. When the output is too large, a second pass has to be done in order to make sure it will fit on the target. This isn't something new -- BD-RB has had that feature for a long time. It just isn't used very often (since the estimation passes are usually pretty accurate).

Okidoke, thanks JD!

Uh... No comment about what I asked about changing the settings 'on the fly' since they are not greyed out...??? I honestly would really appreciate knowing what I can and can't do at that point in relation to what I asked specifically above, especially with regard to episode discs after the main encoding of the episodes is done, but it is still working on the actual Xtras.

Thank you!

[AmigaFuture]

Lathe,

Here's our answer...

[11/06/17] BD Rebuilder v0.50.25
[11:16:05] Source: GAMEOFTHRONES_S1_D2_(FULL_DISK_PROCESSED)_NOW_TESTING_ONFLY_ENCODE_CHANGE
- Input BD size: 9.86 GB
- Approximate total content: [04:37:15.614]
- Target BD size: 7.84 GB
- Windows Version: 6.1 [7601]
- Quality: High Quality (Default), CRF
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[11:16:06] PHASE ONE, Encoding
- [11:16:06] Blanking: VID_00002 (1 of 53)
- [11:16:06] Blanking: VID_00003 (2 of 53)
- [11:16:06] Blanking: VID_00004 (3 of 53)
- [11:16:06] Processing: VID_01016 (4 of 53)
- [11:16:06] Extracting A/V streams [VID_01016]
- [11:16:13] Reencoding video [VID_01016]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,901 frames
- [11:16:13] Performing CRF Prediction...
- Analyzing 11.00 30.50 16.55 20.55 19.50 [19.77]
- [11:16:34] Encoding using constant rate factor.
- [11:18:17] Video Encode complete
- [11:18:17] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:18:17] Multiplexing M2TS
- [11:18:22] Processing: VID_01017 (5 of 53)
- [11:18:22] Extracting A/V streams [VID_01017]
- [11:18:29] Reencoding video [VID_01017]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,901 frames
- Bitrate: 13,640 Kbs
- [11:18:29] Reencoding: VID_01017, Pass 1 of 2
- [11:19:05] Reencoding: VID_01017, Pass 2 of 2
- [11:19:26] Video Encode complete
- [11:19:26] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:19:26] Multiplexing M2TS
- [11:19:30] Processing: VID_01033 (6 of 53)
- [11:19:31] Extracting A/V streams [VID_01033]
- [11:19:37] Reencoding video [VID_01033]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,081 frames
- Bitrate: 13,634 Kbs
- [11:19:37] Reencoding: VID_01033, Pass 1 of 2
- [11:19:47] Reencoding: VID_01033, Pass 1 of 1
- [11:19:58] Video Encode complete
- [11:19:58] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:19:58] Multiplexing M2TS
- [11:20:03] Processing: VID_01034 (7 of 53)
- [11:20:03] Extracting A/V streams [VID_01034]
- [11:20:09] Reencoding video [VID_01034]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,081 frames
- Bitrate: 13,641 Kbs
- [11:20:09] Reencoding: VID_01034, Pass 1 of 1
- [11:20:20] Video Encode complete
- [11:20:20] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:20:20] Multiplexing M2TS
- [11:20:28] Processing: VID_01035 (8 of 53)
- [11:20:28] Extracting A/V streams [VID_01035]
- [11:20:34] Reencoding video [VID_01035]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,258 frames
- Bitrate: 9,502 Kbs
- [11:20:34] Reencoding: VID_01035, Pass 1 of 1
- [11:21:28] Video Encode complete
- [11:21:28] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:21:29] Multiplexing M2TS
- [11:21:33] Processing: VID_01036 (9 of 53)
- [11:21:33] Extracting A/V streams [VID_01036]
- [11:21:39] Reencoding video [VID_01036]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,260 frames
- Bitrate: 9,306 Kbs
- [11:21:39] Reencoding: VID_01036, Pass 1 of 1
- [11:22:34] Video Encode complete
- [11:22:34] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:22:35] Multiplexing M2TS
- [11:22:39] Processing: VID_01037 (10 of 53)
- [11:22:39] Extracting A/V streams [VID_01037]
- [11:22:45] Reencoding video [VID_01037]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,260 frames
- Bitrate: 9,309 Kbs
- [11:22:45] Reencoding: VID_01037, Pass 1 of 2
- [11:23:09] Reencoding: VID_01037, Pass 2 of 2
- [11:24:02] Video Encode complete
- [11:24:02] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:24:02] Multiplexing M2TS
- [11:24:07] Processing: VID_01038 (11 of 53)
- [11:24:07] Extracting A/V streams [VID_01038]
- [11:24:13] Reencoding video [VID_01038]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,258 frames
- Bitrate: 9,453 Kbs
- [11:24:13] Reencoding: VID_01038, Pass 1 of 2
- [11:24:35] Reencoding: VID_01038, Pass 1 of 1
- [11:25:31] Video Encode complete
- [11:25:31] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:25:31] Multiplexing M2TS
- [11:25:35] Processing: VID_01039 (12 of 53)
- [11:25:35] Extracting A/V streams [VID_01039]
- [11:25:47] Reencoding video [VID_01039]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,258 frames
- [11:25:47] Performing CRF Prediction...
- Analyzing 19.20 14.60 18.71 [18.65]
- [11:26:00] Encoding using constant rate factor.
- [11:26:54] Video Encode complete
- [11:26:54] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:26:55] Multiplexing M2TS
- [11:26:59] Processing: VID_01040 (13 of 53)
- [11:26:59] Extracting A/V streams [VID_01040]
- [11:27:05] Reencoding video [VID_01040]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,258 frames
- [11:27:05] Performing CRF Prediction...
- Analyzing 19.21 14.61 18.13 [18.02]
- [11:27:18] Encoding using constant rate factor.
- [11:28:16] Video Encode complete
- [11:28:16] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:28:17] Multiplexing M2TS
- [11:28:21] Processing: VID_01041 (14 of 53)
- [11:28:21] Extracting A/V streams [VID_01041]
- [11:28:28] Reencoding video [VID_01041]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,258 frames
- Bitrate: 9,448 Kbs
- [11:28:28] Reencoding: VID_01041, Pass 1 of 1
- [11:29:26] Video Encode complete
- [11:29:26] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:29:26] Multiplexing M2TS
- [11:29:30] Processing: VID_01042 (15 of 53)
- [11:29:30] Extracting A/V streams [VID_01042]
- [11:29:37] Reencoding video [VID_01042]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,408 frames
- Bitrate: 9,426 Kbs
- [11:29:37] Reencoding: VID_01042, Pass 1 of 1
- [11:30:44] Video Encode complete
- [11:30:44] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:30:44] Multiplexing M2TS
- [11:30:49] Processing: VID_01043 (16 of 53)
- [11:30:49] Extracting A/V streams [VID_01043]
- [11:30:55] Reencoding video [VID_01043]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,258 frames
- Bitrate: 9,485 Kbs
- [11:30:55] Reencoding: VID_01043, Pass 1 of 2
- [11:31:12] Reencoding: VID_01043, Pass 2 of 2


This is a very quick not completed test. Switch AFTER current encode and during multiplexing. Otherwise, are you able to spot the funky whoops?

[Lathe]

Lathe,

Here's our answer...

[11/06/17] BD Rebuilder v0.50.25
[11:16:05] Source: GAMEOFTHRONES_S1_D2_(FULL_DISK_PROCESSED)_NOW_TESTING_ONFLY_ENCODE_CHANGE
- Input BD size: 9.86 GB
- Approximate total content: [04:37:15.614]
- Target BD size: 7.84 GB
- Windows Version: 6.1 [7601]
- Quality: High Quality (Default), CRF
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[11:16:06] PHASE ONE, Encoding
- [11:16:06] Blanking: VID_00002 (1 of 53)
- [11:16:06] Blanking: VID_00003 (2 of 53)
- [11:16:06] Blanking: VID_00004 (3 of 53)
- [11:16:06] Processing: VID_01016 (4 of 53)
- [11:16:06] Extracting A/V streams [VID_01016]
- [11:16:13] Reencoding video [VID_01016]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,901 frames
- [11:16:13] Performing CRF Prediction...
- Analyzing 11.00 30.50 16.55 20.55 19.50 [19.77]
- [11:16:34] Encoding using constant rate factor.
- [11:18:17] Video Encode complete
- [11:18:17] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:18:17] Multiplexing M2TS
- [11:18:22] Processing: VID_01017 (5 of 53)
- [11:18:22] Extracting A/V streams [VID_01017]
- [11:18:29] Reencoding video [VID_01017]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,901 frames
- Bitrate: 13,640 Kbs
- [11:18:29] Reencoding: VID_01017, Pass 1 of 2
- [11:19:05] Reencoding: VID_01017, Pass 2 of 2
- [11:19:26] Video Encode complete
- [11:19:26] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:19:26] Multiplexing M2TS
- [11:19:30] Processing: VID_01033 (6 of 53)
- [11:19:31] Extracting A/V streams [VID_01033]
- [11:19:37] Reencoding video [VID_01033]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,081 frames
- Bitrate: 13,634 Kbs
- [11:19:37] Reencoding: VID_01033, Pass 1 of 2
- [11:19:47] Reencoding: VID_01033, Pass 1 of 1
- [11:19:58] Video Encode complete
- [11:19:58] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:19:58] Multiplexing M2TS
- [11:20:03] Processing: VID_01034 (7 of 53)
- [11:20:03] Extracting A/V streams [VID_01034]
- [11:20:09] Reencoding video [VID_01034]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,081 frames
- Bitrate: 13,641 Kbs
- [11:20:09] Reencoding: VID_01034, Pass 1 of 1
- [11:20:20] Video Encode complete
- [11:20:20] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:20:20] Multiplexing M2TS
- [11:20:28] Processing: VID_01035 (8 of 53)
- [11:20:28] Extracting A/V streams [VID_01035]
- [11:20:34] Reencoding video [VID_01035]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,258 frames
- Bitrate: 9,502 Kbs
- [11:20:34] Reencoding: VID_01035, Pass 1 of 1
- [11:21:28] Video Encode complete
- [11:21:28] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:21:29] Multiplexing M2TS
- [11:21:33] Processing: VID_01036 (9 of 53)
- [11:21:33] Extracting A/V streams [VID_01036]
- [11:21:39] Reencoding video [VID_01036]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,260 frames
- Bitrate: 9,306 Kbs
- [11:21:39] Reencoding: VID_01036, Pass 1 of 1
- [11:22:34] Video Encode complete
- [11:22:34] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:22:35] Multiplexing M2TS
- [11:22:39] Processing: VID_01037 (10 of 53)
- [11:22:39] Extracting A/V streams [VID_01037]
- [11:22:45] Reencoding video [VID_01037]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,260 frames
- Bitrate: 9,309 Kbs
- [11:22:45] Reencoding: VID_01037, Pass 1 of 2
- [11:23:09] Reencoding: VID_01037, Pass 2 of 2
- [11:24:02] Video Encode complete
- [11:24:02] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:24:02] Multiplexing M2TS
- [11:24:07] Processing: VID_01038 (11 of 53)
- [11:24:07] Extracting A/V streams [VID_01038]
- [11:24:13] Reencoding video [VID_01038]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,258 frames
- Bitrate: 9,453 Kbs
- [11:24:13] Reencoding: VID_01038, Pass 1 of 2
- [11:24:35] Reencoding: VID_01038, Pass 1 of 1
- [11:25:31] Video Encode complete
- [11:25:31] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:25:31] Multiplexing M2TS
- [11:25:35] Processing: VID_01039 (12 of 53)
- [11:25:35] Extracting A/V streams [VID_01039]
- [11:25:47] Reencoding video [VID_01039]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,258 frames
- [11:25:47] Performing CRF Prediction...
- Analyzing 19.20 14.60 18.71 [18.65]
- [11:26:00] Encoding using constant rate factor.
- [11:26:54] Video Encode complete
- [11:26:54] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:26:55] Multiplexing M2TS
- [11:26:59] Processing: VID_01040 (13 of 53)
- [11:26:59] Extracting A/V streams [VID_01040]
- [11:27:05] Reencoding video [VID_01040]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,258 frames
- [11:27:05] Performing CRF Prediction...
- Analyzing 19.21 14.61 18.13 [18.02]
- [11:27:18] Encoding using constant rate factor.
- [11:28:16] Video Encode complete
- [11:28:16] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:28:17] Multiplexing M2TS
- [11:28:21] Processing: VID_01041 (14 of 53)
- [11:28:21] Extracting A/V streams [VID_01041]
- [11:28:28] Reencoding video [VID_01041]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,258 frames
- Bitrate: 9,448 Kbs
- [11:28:28] Reencoding: VID_01041, Pass 1 of 1
- [11:29:26] Video Encode complete
- [11:29:26] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:29:26] Multiplexing M2TS
- [11:29:30] Processing: VID_01042 (15 of 53)
- [11:29:30] Extracting A/V streams [VID_01042]
- [11:29:37] Reencoding video [VID_01042]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,408 frames
- Bitrate: 9,426 Kbs
- [11:29:37] Reencoding: VID_01042, Pass 1 of 1
- [11:30:44] Video Encode complete
- [11:30:44] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [11:30:44] Multiplexing M2TS
- [11:30:49] Processing: VID_01043 (16 of 53)
- [11:30:49] Extracting A/V streams [VID_01043]
- [11:30:55] Reencoding video [VID_01043]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 1,258 frames
- Bitrate: 9,485 Kbs
- [11:30:55] Reencoding: VID_01043, Pass 1 of 2
- [11:31:12] Reencoding: VID_01043, Pass 2 of 2


This is a very quick not completed test. Switch AFTER current encode and during multiplexing. Otherwise, are you able to spot the funky whoops?

Ah, so you DID do it! Great! Thanks kindly for posting that. So then, like you say, wait until the primary CRF encodes are done and as the last episode is multiplexing, THEN switch the encode setting from CRF to, say, Fast ABR, or whatever, right?

[AmigaFuture]

That log is only a "Playing around With"... I don't "wait" for anything, but in the common vernacular, I understand. Hehe. I'd do it as the multiplexing is happening, aye. Remember, I'm NOT currently using "Quicker: Encode for extras". So you'll have to be aware of them yourself. I'll now do a more real...test check with High Speed encoding..and the switch after the last "big" video is multiplexing. Logic of BD-RB suggests this will do very well.

[Lathe]

That log is only a "Playing around With"... I don't "wait" for anything, but in the common vernacular, I understand. Hehe. I'd do it as the multiplexing is happening, aye. Remember, I'm NOT currently using "Quicker: Encode for extras". So you'll have to be aware of them yourself. I'll now do a more real...test check with High Speed encoding..and the switch after the last "big" video is multiplexing. Logic of BD-RB suggests this will do very well.

Very good! I'm really glad that you tested it out. By the time I thought of it, the disc had already gone about 8 hours and I didn't really feel like experimenting on it :)

Thanks again!

[AmigaFuture]

Gratitude profuseness is very humorous to me and not needed. Wink! Appreciate once and let that be. When it's genuine, it's always excepted well the first time. I'm now running a full backup "test"..which should produce a size fitting and good quality result. Unless there's something funky about JD's Logic.. Snickering with smile like the Cheshire Cat.

Update: High Speed and switching to CRF looked good. Also 21GB... For fun, I'm going a "Better" and switching to 1-pass ABR...

[Lathe]

I'm a bit curious... (what else is new... http://lathe-of-heaven.com/rolleyes2.gif)

I inadvertently left my BDRB frame server set to DirectShow because I had been doing The Avengers discs. So, when I went to do a movie like usual, I forgot to change it back to x264's internal one. I notice that with basically the same type / length film, and with all the other settings, including tweaks, exactly the same, for some odd reason the 2nd pass is taking a LOT longer than usual. For a movie if it is fairly good size, I usually set it at 'High' and use the same tweaks that I always do. So, normally using x264's encoder, the 2nd pass generally takes about 8-9 hours. In this case, it is still going and looks like it will take about 13 1/2 hours!

Just really curious as to why that would be...?

Thanks!

[gonca]

DirectShow is 32 bit
x264 internal might be 64 bit, if memory is still good (watch it Lathe)
I notice a fps difference of some 10% between 32 and 64 bit on my system

[Lathe]

DirectShow is 32 bit
x264 internal might be 64 bit, if memory is still good (watch it Lathe)
I notice a fps difference of some 10% between 32 and 64 bit on my system

Ahhhhh, yes, if DS is indeed 32 bit, that very well could be the difference.

Thanks gonca! I KNEW there must be some good reason why you were still here! :D

[gonca]

Thanks gonca! I KNEW there must be some good reason why you were still here! :D

So now we know my reason
What is yours, dear Lathe
P.S.
Like your doll avatar

[Lathe]

So now we know my reason
What is yours, dear Lathe
P.S.
Like your doll avatar

JD specifically pays me to keep an eye on you...

... and the Avatar is Anime, but thanks...

[AmigaFuture]

Heh, gonca got you and I think you missed it!

If JD pays you, then it's not a wonder he's talks about not making enough money, you extortionist! Butt (pun just for you Lathe), JD is a bit smarter than that. So, what's your next story? :D

[Lathe]

Heh, gonca got you and I think you missed it!

If JD pays you, then it's not a wonder he's talks about not making enough money, you extortionist! Butt (pun just for you Lathe), JD is a bit smarter than that. So, what's your next story? :D

As usual, AF, you have run rings around my logic and I am at a total loss... :cool:

[AmigaFuture]

Avatar....Doll....anime; from gonca. Sheesh.

[frank_zappa1]

thank so much this work with avisynth+ ?

[AmigaFuture]

thank so much this work with avisynth+ ?

I think I understand your question. From the first post of this thread that that gives all the details:

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.

[gonca]

thank so much this work with avisynth+ ?

No it does not

[LowDead]

No it does not

hmm.. I'm using AviSynth+ it doesn't work with dvd-rb though, so had to install the old one for that..

//LD

[frank_zappa1]

hmm.. I'm using AviSynth+ it doesn't work with dvd-rb though, so had to install the old one for that..

//LD

Why not AVS+ ??? :readrule::readrule::readrule:

[Groucho2004]

:readrule::readrule::readrule:Who is supposed to read which rule?

Why not AVS+ ???AVS+ behaves differently to the "classic" Avisynth in some scenarios and has additional dependencies. I think jdobbs simply wants to exclude another branch of potential bug reports that have nothing to do with his software.

[gonca]

Who is supposed to read which rule?

AVS+ behaves differently to the "classic" Avisynth in some scenarios and has additional dependencies. I think jdobbs simply wants to exclude another branch of potential bug reports that have nothing to do with his software.

All that he needs to do is switch between 32 bit AVS+ and AVS
Only takes a few seconds
Would be nice if BD_RB allowed AVS+, with no bug reports, but such is life

[MrVideo]

Would be nice if BD_RB allowed AVS+, with no bug reports, but such is life
But, would using AVS+ add any value to BDRB? Does AVS provide all of the necessary tools to do what is needed? I believe the answers are no and yes. As pointed out, using AVS+ will more than likely only add the potential for bug reports that are not related to BDRB.

[DoctorM]

Backing up Ladyhawke today (Warner Archive version). This is now the third WAC disc where BD Rebuilder does not recognize the trailer for re-encoding.
It is copied to the final disc untouched, but it does not appear on the stream list so it isn't re-encoded and tracks can't be blanked.

I always keep MIN_M2TS_SIZE & MIN_PLAYLIST_MINS at zero.
Yes I've tried: IGS_ENABLE=1

There is something weird with WAC discs, because I've never seen it happen to any other backups.

[RoyGBiv-inRI]

How do I prevent BDRebuilder from recoding to make programming completely fill a BD-R? I have a bunch of TV shows I've recorded onto a DVD-recorder. I am then putting them on my computer HDD as MKV files (so I can change the AR which is set incorrectly by the DVD-recorder), and then I am importing 10 to 12 at a time to make one BD using Quick Play Backup. The files are about 1.7 Gb each so 10 should make a disc about 17 Gb. However, the process takes nearly 2 hours, and I end up with a BD that is 22.3 Gb in size.

I have added FORCE_NOENCODE=1 to my BDRebuilder.ini file. Is there something else I need to do to prevent it recoding? I don't think I care that it completely fills the BD. I just don't want a lot of recoding going on unnecessarily.

TIA.

SMK

[Lathe]

How do I prevent BDRebuilder from recoding to make programming completely fill a BD-R? I have a bunch of TV shows I've recorded onto a DVD-recorder. I am then putting them on my computer HDD as MKV files (so I can change the AR which is set incorrectly by the DVD-recorder), and then I am importing 10 to 12 at a time to make one BD using Quick Play Backup. The files are about 1.7 Gb each so 10 should make a disc about 17 Gb. However, the process takes nearly 2 hours, and I end up with a BD that is 22.3 Gb in size.

I have added FORCE_NOENCODE=1 to my BDRebuilder.ini file. Is there something else I need to do to prevent it recoding? I don't think I care that it completely fills the BD. I just don't want a lot of recoding going on unnecessarily.

TIA.

SMK

I've found that in cases where size is not the issue (I'm talking about Blu-ray files, NOT my personal life, thank you...) usually, it is almost ALWAYS a case where the MKV files are simply not fully compliant with BD specifications. If BDRB notes that, a re-encode will always be done.

[RoyGBiv-inRI]

Thanks. I'll search around to see if I can try some other options.

SMK

[musiclover]

Backing up Ladyhawke today (Warner

I always keep MIN_M2TS_SIZE & MIN_PLAYLIST_MINS at zero.
Yes I've tried: IGS_ENABLE=1


What does IGS_ENABLE=1 do? I do not see it described in HIDDENOPTS.TXT