BD Rebuilder Beta - Bug Reports Only

[AmigaFuture]

noticed when encoding its using the 32bit version of x264 ?? why is it not using 64 bit

also how do you add stuff to the avisynth script, i want to enable the MT mode ?

Thanks

I've noticed that, and I've wondered why "it's" not doing it also. The rest is redundant. :)

[Michi]

Error on Wizard of OZ:

[11.21.19] BD Rebuilder v0.60.29
[19:50:51] Source: WIZARD_OF_OZ
- Input BD size: 77,81 GB
- Approximate total content: [02:46:04.245]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Fastest, BD-25+), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[19:50:51] PHASE ONE, Encoding
- [19:50:51] Processing: VID_00000 (1 of 9)
- [19:50:51] Extracting A/V streams [VID_00000]
- [19:50:55] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 486 frames
- Bitrate: 12.895 Kbs
- [19:50:55] Reencoding: VID_00000, Pass 1 of 1
- [19:51:23] Video Encode complete
- [19:51:23] Processing audio tracks
- [19:51:23] Multiplexing M2TS
- [19:51:27] Processing: VID_00001 (2 of 9)
- [19:51:27] Extracting A/V streams [VID_00001]
- [19:51:31] Reencoding video [VID_00001]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 457 frames
- Bitrate: 5.393 Kbs
- [19:51:31] Reencoding: VID_00001, Pass 1 of 1
- [19:51:57] Video Encode complete
- [19:51:57] Processing audio tracks
- [19:51:57] Multiplexing M2TS
- [19:52:00] Processing: VID_00002 (3 of 9)
- [19:52:01] Extracting A/V streams [VID_00002]
- [19:53:56] Reencoding video [VID_00002]
- Source Video: HEVC, 1920x1080
- Rate/Length: 23,976fps, 74.301 frames
- Bitrate: 32.449 Kbs
- [19:53:56] Reencoding: VID_00002, Pass 1 of 1
- [20:13:41] Video Encode complete
- [20:13:41] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [20:13:41] Multiplexing M2TS
- [20:18:53] Processing: VID_00004 (4 of 9)
- [20:18:53] Extracting A/V streams [VID_00004]
- [20:19:00] Reencoding video [VID_00004]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 8.160 frames
- Bitrate: 8.020 Kbs
- [20:19:00] Reencoding: VID_00004, Pass 1 of 1
- [20:26:27] Video Encode complete
- [20:26:27] Processing audio tracks
- [20:26:27] Multiplexing M2TS
- [20:26:39] Processing: VID_00007 (5 of 9)
- [20:26:39] Extracting A/V streams [VID_00007]
- [20:31:17] Reencoding video [VID_00007]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 146.383 frames
- Bitrate: 35.000 Kbs
- [20:31:17] Reencoding: VID_00007, Pass 1 of 1
- [22:56:20] Video Encode complete
- [22:56:20] Processing audio tracks
- Track 4354 (deu): Keeping original audio
- [22:56:20] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00007.meta
- Bitstream exception Unknown exception. It does not have to be! Please contact application support team for more information.
[22:56:44] - Failed to build structure, aborted

[Alleycat]

I rebuilt a concert blu-ray which had 720 x 480i mpeg 2 source with a 16:9 display aspect ratio. I noticed that the rebuilt version has small black bars at the top and bottom and the picture was of reduced height (slightly squashed) compared to the original. When I used the hidden option show_encoder=1, x264 reported the following: "lav [info]: 720x480i 32:27 @ 30000/101 fps (cfr)"
I could see that bd-rb was then telling x264 to use SAR=40/33 when doing the re-code, which I believe is the cause of this problem. Is there a way of forcing bd-rb to preserve the original SAR value?

[prologic]

Tried to remux Game of thrones S8 disc1(BLURAY) , Bd rebuilder came back with , error reading disc .. went back to version 60.04 and all read ok

[Ch3vr0n]

Tried to remux Game of thrones S8 disc1(BLURAY) , Bd rebuilder came back with , error reading disc .. went back to version 60.04 and all read ok

Now how about you post the encoding log of the build that fails, so @jdobbs actually has something to work with and maybe fix?

[jdobbs]

Now how about you post the encoding log of the build that fails, so @jdobbs actually has something to work with and maybe fix?Yeah. Especially since "error reading disc" isn't an error from within BD-RB.

[Michi]

Muxing Error on RED 2:

[11.24.19] BD Rebuilder v0.60.29
[09:54:01] Source: RED_2
- Input BD size: 59,23 GB
- Approximate total content: [03:02:05.879]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Fastest, BD-25+), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[09:54:03] PHASE ONE, Encoding
- [09:54:03] Processing: VID_00000 (1 of 8)
- [09:54:03] Extracting A/V streams [VID_00000]
- [09:58:45] Reencoding video [VID_00000]
- [09:58:45] Keeping original video (no reencode)
- [09:58:45] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [09:58:45] Multiplexing M2TS
- [10:07:08] Processing: VID_00001 (2 of 8)
- [10:07:08] Extracting A/V streams [VID_00001]
- Extracting video streams [VID_00001]
- Extracting audio/subtitle streams [VID_00001]
- Network Optix tsMuxeR. Version 2.6.12. www.networkoptix.com
- Extracting audio streams [VID_00001]
- Error in attempt to extract audio.
- Network Optix tsMuxeR. Version 2.6.12. www.networkoptix.com
- Network Optix tsMuxeR. Version 2.6.12. www.networkoptix.com
[10:09:20] - Failed to retrieve audio, aborted

[ggtop]

Hi,

when opening the source path to a mounted ISO I get an error message "Error Condition" "BD Rebuilder experienced an error 2503 [timestamp] SourceCheck() 0006 2503".
It's a Multi Part BluRay interesstingly it only happens in Movie Only Mode. Switching to Full Backup mode lets BDRB show the stream overview as expected.

As a workaround I used TSMuxer to create a new structure (ISO) with the desired MPLS and used that which worked so far as I can say.

What kind of "illegal source" is this error indicating?

Glad to help and Thank you in advance,
ggtop

[jdobbs]

Hi,

when opening the source path to a mounted ISO I get an error message "Error Condition" "BD Rebuilder experienced an error 2503 [timestamp] SourceCheck() 0006 2503".
It's a Multi Part BluRay interesstingly it only happens in Movie Only Mode. Switching to Full Backup mode lets BDRB show the stream overview as expected.

As a workaround I used TSMuxer to create a new structure (ISO) with the desired MPLS and used that which worked so far as I can say.

What kind of "illegal source" is this error indicating?

Glad to help and Thank you in advance,
ggtopIt wasn't necessarily an illegal source. It looks like BD-RB experienced an overflow error while doing a source check. Can you provide the log? I'm kinda flying blind without it.

[terrykuntz]

Will an 8 core CPU be able to complete a bd rebuild twice as fast as an 4 core CPU? Would it be better to get an 8 core intel processor than an 16 core AMD processor?

[Atak_Snajpera]

Will an 8 core CPU be able to complete a bd rebuild twice as fast as an 4 core CPU? Would it be better to get an 8 core intel processor than an 16 core AMD processor?

x264 and x265 can utilize more than 8 cores so buying Intel CPU makes zero sense.

[jdobbs]

Will an 8 core CPU be able to complete a bd rebuild twice as fast as an 4 core CPU? Would it be better to get an 8 core intel processor than an 16 core AMD processor?An 8 core CPU will likely complete faster than a 4 core -- but not twice as fast. That's not how multiprocessing works.

[SquallMX]

An 8 core CPU will likely complete faster than a 4 core -- but not twice as fast. That's not how multiprocessing works.

Sometimes the gains are even bigger. Going from an 8 core Ryzen 1700x to a 12 core Ryzen 3900 I got a 2X speed boost with only 50% more cores, something to do with optimizations for AVX instruction sets.

[gg72]

Is there any option to disable the 4-way splitting in DirectShow mode?

[Ch3vr0n]

Not "just" for DS mode no. There is a general one, disable multiprocess in bdrebuilder.ini (either comment out the line with # in front of it, or just delete it entirely). That's the only possibility

[jdobbs]

Is there any option to disable the 4-way splitting in DirectShow mode?The default is no splitting. The only way it has 4 way splitting is if you've (at some point) set MULTIPROCESS=4 in your INI file or MULTIPROCESS=1 in your INI file and you have 6 (or more) processors.

[jdobbs]

Thought I'd share an interesting point I discovered. I recently got a UHD television and have been experimenting with playback with different 2160p files. Then I decided to disable 4K upscaling on my Sony UBP-X800 so I could make sure I am really getting UHD.

I was a little shocked to find that many of the reencoded UHD MKV/MP4 files weren't actually playing in UHD -- they were playing in 1080p and were being upscaled. Some experimenting showed that only the files I'd reencoded with BD-RB (ALTERNATE mode), or original BD files, were actually playing in true 2160p. My guess is that the player requires the files to be encoded with settings that are uhd-bd compatible (which BD-RB does via X265) and many downloads are not encoded that way.

Just thought I'd pass that on as food for thought. It may be peculiar to my player, I don't know, but I think there are possibly people out there who think they are getting 2160p output when they are actually only getting 1080p upscaled to 2160p on reencoded MKV/MP4 UHD files.

[jdobbs]

Sometimes the gains are even bigger. Going from an 8 core Ryzen 1700x to a 12 core Ryzen 3900 I got a 2X speed boost with only 50% more cores, something to do with optimizations for AVX instruction sets.That's pretty cool.

[gg72]

Thanks jdobbs & Ch3vr0n ;-)

[MrVideo]

[...]but I think there are possibly people out there who think they are getting 2160p output when they are actually only getting 1080p upscaled to 2160p on downloaded UHD files.
Are you saying that some 2160p files are being reduced to 1080p by your player before being sent to the display? If so, that player, IMHO, is seriously flawed.

[Sharc]

I rebuilt a concert blu-ray which had 720 x 480i mpeg 2 source with a 16:9 display aspect ratio. I noticed that the rebuilt version has small black bars at the top and bottom and the picture was of reduced height (slightly squashed) compared to the original. When I used the hidden option show_encoder=1, x264 reported the following: "lav [info]: 720x480i 32:27 @ 30000/101 fps (cfr)"
I could see that bd-rb was then telling x264 to use SAR=40/33 when doing the re-code, which I believe is the cause of this problem. Is there a way of forcing bd-rb to preserve the original SAR value?
Is your source a DVD? 32:27 = 1.1852 is the 'Generic' PAR of anamorph 16:9 NTSC DVDs. It is an assumption because the true PAR of DVDs/mpeg2 cannot be read from the video stream. The DVD could also have been authored using the ITU PAR of 1.212954 for 16:9. We simply don't know.
BD-RB uses the mpeg4 SAR of 40:33 = 1.212121... for x264 16:9 anamorph 720x480 encoding. It is AVC/mpeg4/blu-ray compliant and a very close approximation to the ITU PAR of 1.212945, but exhibits the well known aspect ratio difference of 2.3% compared to the 'Generic' PAR of 1.1852. This slight difference is normally not even noticed. As far as I remember you can't change the SAR in BD-RB to avoid non-compliant mpeg4/AVC video.

Thinking about it and hoping I remembered all this correctly, I am now wondering why BD-RB added top and bottom borders rather than left and right 8 pixels each. Did your original already come with any borders? Did you resize? What is your playback scenario? Does your player/TV add the top/bottom borders rather than BD-RB? Does your player read the SAR or force 16:9 DAR playback?

[Mike-uk]

Thought I'd share an interesting point I discovered. I recently got a UHD television and have been experimenting with playback with different 2160p files. Then I decided to disable 4K upscaling on my Sony UBP-X800 so I could make sure I am really getting UHD.

I was a little shocked to find that many of the reencoded MKV/MP4 UHD files weren't actually playing in UHD -- they were playing in 1080p and were being upscaled. Some experimenting showed that only the files I'd reencoded with BD-RB (ALTERNATE mode), or original BD files, were actually playing in true 2160p. My guess is that the player requires the files to be encoded with settings that are uhd-bd compatible (which BD-RB does via X265) and many downloads are not encoded that way.

Just thought I'd pass that on as food for thought. It may be peculiar to my player, I don't know, but I think there are possibly people out there who think they are getting 2160p output when they are actually only getting 1080p upscaled to 2160p on reencoded MKV/MP4 UHD files.

what does mediainfo say about the file you are trying to play ? does it report the file as 1080p ??
also what is the file size of said 2160p file ?

[jdobbs]

Are you saying that some 2160p files are being reduced to 1080p by your player before being sent to the display? If so, that player, IMHO, is seriously flawed.I'd say it's more likely that the source is seriously flawed. Players have built-in downscaling to cover being attached to non-UHD monitors and other non-compliance issues.

[jdobbs]

what does mediainfo say about the file you are trying to play ? does it report the file as 1080p ??
also what is the file size of said 2160p file ?No. It is UHD. But, some of them, at least, aren't 3840x2160. For example one that I'm looking at now is 3840x1600. So there may be more to it than just the encoding parameters.

[Edit] In fact, several of the files I've looked at (that I had previously tested) are actually 3840x1600, which seems to be a fairly common format for reencoded MKV/MP4 files (even though the file title says "2160p"). In the end it may turn out to be the non-compliant sizing that is the real issue. But the original point is still valid. People may think they are watching these in UHD when they are actually simply watching an upscaled representation of it from a picture that was downscaled to 1080p. I know that is true at least on my Sony player, I can't speak for other units.

[Sharc]

... People may think they are watching these in UHD when they are actually simply watching an upscaled representation of it from a picture that was downscaled to 1080p.....
LOL, who cares as long as people are happy with placebos … :devil:

[jdobbs]

Placebos work. That's the reason so many "natural cures" are sold.

I'll take of a couple of these and reencode them with the borders that bring it up to 2160. I suspect that will fix the issue.

I have to say... I'm pretty impressed with the UHD blu-rays I've been watching since getting my UHD TV. It's more noticable than I thought it would be (on some discs, not all). Some of the reviews I read say that most people won't see the difference between HD and UHD from a normal viewing distance. But to me it looks more crisp (from about 10 feet where I usually watch).

But then again... there's always the placebo effect. :)

[MrVideo]

NIn fact, several of the files I've looked at (that I had previously tested) are actually 3840x1600, which seems to be a fairly common format for reencoded files (even though the file title says "2160p").
Well, that explains it. Many of the groups have it in their little heads that removing the letterbox bars from widescreen videos will reduce the file size. While it is true that it will, it obviously causes issues like this.

If I play a MKV file thru my Samsung and if it is 1920x800, the player will add the letterbox bars. But, if I author the file onto a BD, the player will vertically expand the video to fill the screen. Those cropped videos are a PITA. :devil:

[SeeMoreDigital]

If I play a MKV file thru my Samsung and if it is 1920x800, the player will add the letterbox bars. But, if I author the file onto a BD, the player will vertically expand the video to fill the screen. Those cropped videos are a PITA. :devil:Indeed.... It's a shame that the Blu-ray 'HD' disc format does not support 'cropped' video. And even a bigger shame that the Blu-ray 'UHD' disc format followed suit :eek:

[cartman0208]

I have to say... I'm pretty impressed with the UHD blu-rays I've been watching since getting my UHD TV. It's more noticable than I thought it would be (on some discs, not all). Some of the reviews I read say that most people won't see the difference between HD and UHD from a normal viewing distance. But to me it looks more crisp (from about 10 feet where I usually watch).


I totally agree... I had an UHD TV before, but with the new one UHD sources look even better ... WAY better. You can already see it during the first few seconds when the Warner Bros Logo turns up, for example.
And at 5 feet even the blindest will see a difference ;)

[Glarioo]

I'll take of a couple of these and reencode them with the borders that bring it up to 2160. I suspect that will fix the issue.



How do you do that?
Adding "black bars" to cropped videos?

[MrVideo]

How do you do that?
Adding "black bars" to cropped videos?
With AVISynth and one of the many available plugins that do many different kinds of video processing.

[jdobbs]

How do you do that?
Adding "black bars" to cropped videos?Use BD-RB to import and reencode. It adds them automatically.

[Glarioo]

Use BD-RB to import and reencode. It adds them automatically.

Thanks.
And use alternate output?

[Glarioo]

Just reencode an 1920x808 file an the result was 1920x1080. Thanks jdobbs.

[Alleycat]

Is your source a DVD? 32:27 = 1.1852 is the 'Generic' PAR of anamorph 16:9 NTSC DVDs. It is an assumption because the true PAR of DVDs/mpeg2 cannot be read from the video stream. The DVD could also have been authored using the ITU PAR of 1.212954 for 16:9. We simply don't know.
BD-RB uses the mpeg4 SAR of 40:33 = 1.212121... for x264 16:9 anamorph 720x480 encoding. It is AVC/mpeg4/blu-ray compliant and a very close approximation to the ITU PAR of 1.212945, but exhibits the well known aspect ratio difference of 2.3% compared to the 'Generic' PAR of 1.1852. This slight difference is normally not even noticed. As far as I remember you can't change the SAR in BD-RB to avoid non-compliant mpeg4/AVC video.

Thinking about it and hoping I remembered all this correctly, I am now wondering why BD-RB added top and bottom borders rather than left and right 8 pixels each. Did your original already come with any borders? Did you resize? What is your playback scenario? Does your player/TV add the top/bottom borders rather than BD-RB? Does your player read the SAR or force 16:9 DAR playback?

Thanks for replying, Sharc. The source was "Out of Season" by the band Marillion. It's a triple disc set which was originally released on DVD, but now is out on Blu-Ray to take advantage of the higher quality sound. The small black bars only appeared on the rebuilt copy. Funnily enough I did try upscaling to 1080 and found there were no black bars. But this introduced a different problem: When using the pop-up menu, if I hovered the mouse over a chapter near the top of the page, it highlighted and activated one several lines below!
So I decided to keep it at 720x480, but the only way I could get a perfect copy was to grab the output of lastcmd.txt after each pass and manually recode each affected file in x264 replacing --sar 40:33 with --sar 32:27, then remuxing to m2ts myself. I then replaced the files created by BDRB with my own, which obviously broke the chapters. I fixed this by getting BDRB to rebuild the copy containing the replaced files, this time with no encoding of the video (as the file sizes were now correct for BD25). All menus and chapters work fine and the video is identical to the original. I've no idea if the new copy is blu-ray compliant, but it works perfectly on both the PS4 and in J River media centre. Obviously this was a very laborious way of doing a 3 disc set, but I could find no other method, and wondered if I could have done anything to make BDRB work automatically with these discs.

[AmigaFuture]

LOL, who cares as long as people are happy with placebos … :devil:

Placebos work. That's the reason so many "natural cures" are sold.

I'll take of a couple of these and reencode them with the borders that bring it up to 2160. I suspect that will fix the issue.

I have to say... I'm pretty impressed with the UHD blu-rays I've been watching since getting my UHD TV. It's more noticable than I thought it would be (on some discs, not all). Some of the reviews I read say that most people won't see the difference between HD and UHD from a normal viewing distance. But to me it looks more crisp (from about 10 feet where I usually watch).

But then again... there's always the placebo effect. :)

The body can do its own healing very, very well without intervention. I saw much of this so far. But there are times when intervention is required. I can also still see some differences in upscaling from DVD to 720P, but it's becoming more challenging when it's happening with hardware.

I still adore 1080P, but I don't really embrace the 4K thing as so many. Yes, video looks larger, from my phone, yes, outside video of events and nature are really sweet that way. But movies and T.V. shows where there are a lot of makeup and and all that...acne, and stuff...I don't see any reason for that to be really huge. Now, you present Mars photos that large, and other pictures of our planets...I'm alllllllll in! I want to see all that very clearly. I guess it's a "catch 22" to me. Hmm..

[MrVideo]

@Alleycat: Are the original BD discs dual layer 50GB? If so, are you trying to get each one to fit on a 25GB disc?

[Alleycat]

Yes, the 3 original discs are BD50. I was simply creating a backup of each onto 3 separate 25GB discs. The SD video files inside the m2ts containers are mpeg-2.
When starting the x264 encoder, the first line shows "lav [info]: 720x480i 32:27 @ 30000/1001 fps (cfr)". If you import the same file into Handbrake, the dimensions tab shows: "Source 720x480, PAR 32/27".
Those references to 32:27 made me suspect the black bars on the BDRB copy were caused by the SAR 40:33 in BDRB's x264 command line. I found that if I used SAR 32:27, or if I just omitted the SAR parameter completely, both scenarios produced video identical to the source, with no black bars.

[MrVideo]

The SAR of 40:33 is based upon a 704x480 video. With NTSC analog conversion to digital, 8 pixels are removed from each side of the 720 video to get you the 704 video. But, if the 16 total pixels are not removed, you end up with the situation you found yourself in. You could have added an AVISynth plugin command to crop 8 pixels off each side and you should have come up with the correct result [crop(8,0,-8,0)].

The reason for doing the cropping is that in correctly digitized video, there are about 8 pixels of vertical black on each side of the video. By removing it, you get video out to each side, without any annoying vertical black bars.

[Alleycat]

Thanks for your suggestion re cropping. I gave it a try and found that it did indeed remove the bars. The bars had been at the top and bottom, not the sides, but cropping 8 pixels from each side made them disappear. Compared with the original, the height of the picture was now the same, with no part of the original frame missing. The width of the picture was very slightly stretched, with a very small part of each side cropped. Viewed in isolation, I probably would not have noticed, so that's preferable to the black bars.

What I can't figure out is this: If I get BD-RB to convert it from SD to 1080, there are no bars, and nothing is cropped from the edges.

Also, given that the source disc has the SAR of 32:27, does that mean the original BD is not compliant? Or it is allowed for MPEG-2 on BD but not AVC?
That may explain why they stuck with MPEG-2 coding on the original.

[MrVideo]

The 704x480 is really only for DVDs. The BD spec only has 720x480, which would only mean supporting 32:27 (for 16:9 video). No idea why BDRB was not getting it right. Doing the cropping trick does end up distorting the image, as you noted.

The original BDs are compliant. The BD spec allows for MPEG-2/AVC/VC1 as codecs for 720x480 video.

JDobbs is going to have to respond as to what is happening.

EDIT: Add "IMPORT_OVERSCAN=0" to the options file. Don't do the cropping. I'm curious as to what this does.

[jdobbs]

The BD spec only has 720x480, which would only mean supporting 32:27 (for 16:9 video). Maybe I misunderstood what you're saying? The BD Spec supports 4:3 video in 720x480. 720x480 at 4:3 is mentioned more times than I can even reference. For example, see page 1-147, Table 5-17 of the spec, and look under primary video formats. Adjusting for overscan is normal for 720x480 sources. Often people just forget about it and leave the aspect slightly stretched (by removing the overscan areas).

I'd have to see the source to decide what is going on in Alleycat's case. The part about bars being at the top and bottom (rather than the sides) throws me. Overscan adjustments should only apply to the sides??? I guess I need to go back and read his posts again.

I can tell you that I, for one, am happy to see the 1:1 ratios used in HD and UHD. Having to adjust for the leftovers from analog television (like overscan) is a real pain. These days trying to decide whether to adjust for overscan depends on what mood the original author was in at the time the disc was created. Many MKV files out there that hold old TV shows, for example, typically just resize the original 720x480 sources (minus overscan) to 640x480 with a 1:1 ratio (which means they are stretched slightly). But that depends on what the person doing the encoding knew or didn't know about video.

It's nothing if not confusing.

[Alleycat]

@ Mr. Video: I tried adding IMPORT_OVERSCAN=0 to the ini file, but it made no difference. I was using the full backup mode, so maybe that function only operates when using the import mode.

@jdobbs: In my fist post I noticed BD-RB was re-encoding my disc with an SAR of 40:33 in X264, but the original has an SAR of 32:27, due to the video being in MPEG-2 blu-ray.

Would the problem not be solved by removing the --SAR X:X from the X264 command line when full back up mode is used? As the source is already a blu-ray, the original SAR must be compliant, so the BD-RB copy need not be any different?

[MrVideo]

Maybe I misunderstood what you're saying? The BD Spec supports 4:3 video in 720x480.
We were discussing the OP's original files, which are 16:9 720x480, which only has the one SAR. No discussion of 4:3 video.

[MrVideo]

@ Mr. Video: I tried adding IMPORT_OVERSCAN=0 to the ini file, but it made no difference. I was using the full backup mode, so maybe that function only operates when using the import mode.
It was worth a try. No idea what JDobbs intended that option for.

[Sharc]

@Alleycat
Can you upload a sample of a few seconds duration of the original file?
Without a sample all the discussions remain speculative.

[Lathe]

Well, that explains it. Many of the groups have it in their little heads that removing the letterbox bars from widescreen videos will reduce the file size. While it is true that it will, it obviously causes issues like this.

If I play a MKV file thru my Samsung and if it is 1920x800, the player will add the letterbox bars. But, if I author the file onto a BD, the player will vertically expand the video to fill the screen. Those cropped videos are a PITA. :devil:

Fully agree... Same here with my OPPO. I've Always thought it was nonsense removing the black bars, it doesn't save that much space and automatically makes it noncompliant. Stupid...

[gamete]

Im trying to backup for the first time bluray 4k

My pc is
Win10 64bit
Intel i7 2.94ghz 4core(i Think)
6 gb ram

If i make backup of bluray 2k in bd25 is necessary 5 hours about

In my first 4k bluray backup time estimated from 55gb to 25gb in two pass is 40 hours
0.95 fps

Im trying using " x264 internal LAVF for frame serving"
Is it correct ?
40 hours for 4k backup ?
Thank to all

[raul124]

Im trying to backup for the first time bluray 4k

My pc is
Win10 64bit
Intel i7 2.94ghz 4core(i Think)
6 gb ram

If i make backup of bluray 2k in bd25 is necessary 5 hours about

In my first 4k bluray backup time estimated from 55gb to 25gb in two pass is 40 hours
0.95 fps

Im trying using " x264 internal LAVF for frame serving"
Is it correct ?
40 hours for 4k backup ?
Thank to all

Same here...

[jdobbs]

Im trying to backup for the first time bluray 4k

My pc is
Win10 64bit
Intel i7 2.94ghz 4core(i Think)
6 gb ram

If i make backup of bluray 2k in bd25 is necessary 5 hours about

In my first 4k bluray backup time estimated from 55gb to 25gb in two pass is 40 hours
0.95 fps

Im trying using " x264 internal LAVF for frame serving"
Is it correct ?
40 hours for 4k backup ?
Thank to allI'd recommend you set your encoder to "Very Good (Fast)" and "One Pass (ABR) Encoding" if you want to speed up encoding. On my system (which is pretty old) it usually takes about 10-12 hours with that setting (I typically get 4 - 4.5 fps). Honestly, there is plenty of room on a 25GB disc even for UHD, and you don't need higher settings. Of course people have different opinions about that. But, I've done tests using different CRF settings to get constant quality to see how much space is needed, and I rarely hit anywhere near 25GB even when using high quality CRF values. With that said, it depends a lot on how much content is on the disc you're backing up.

If encode time isn't important to you... then ignore what I just said and use a higher quality setting and/or keep two pass encoding enabled.

It makes no difference what frame-serving option you select when doing UHD. BD-RB is going to use FFMPEG anyway so that the HDR10 settings get passed along to the encoder. I'm assuming you are doing a full or movie-only backup? If so, X264 isn't used either. UHD on blu-ray requires HEVC (X265).

[gamete]

Tks @jdobbs
Its my first 4k bluray backup
Only movie
For the next bluray ill try with your configuration

[gamete]

Hi, I wanted to know what is the recommended size to set in bdrebuilder for the bd50, thanks

Is the remaining time calculated based on the video compression percentage?

is it possible that a future version of bd rebuilder marks how many mb uses every single audio of the film?

[jdobbs]

Hi, I wanted to know what is the recommended size to set in bdrebuilder for the bd50, thanks

Is the remaining time calculated based on the video compression percentage?

is it possible that a future version of bd rebuilder marks how many mb uses every single audio of the film?There is a default size already established for BD-50. Just select BD-50 from Settings/Output Options.

The remaining time is based on overall size and is updated based upon the speed up to that point.

The size of the audio is already taken into account when BD-RB calculates the bitrate needed for the video.

[gamete]

The size of the audio is already taken into account when BD-RB calculates the bitrate needed for the video.

I mean if there will be the possibility in new release of bdrebuilder to know the size each one of audio included in bluray

Tks

[jdobbs]

I mean if there will be the possibility in new release of bdrebuilder to know the size each one of audio included in bluray

TksI have no plans to show the sizes of each audio stream.

But, you can go into the working folder after BD-RB extracts them and see the sizes. Each of the audio streams are extracted into individual files. You they will look like this:

00000.track_4352.dts

The "00000" is the M2TS they came from and the 4352 is the PID. The extension will tell you the type of audio (like dts or ac3). The audio tracks will have PIDs in the range of 4352-4383 (depending on how many audio tracks exist).

Those are the original tracks. After processing you may see the new ones. They will start with the text "AUD", will also include the PID number, and will end with an extension like ".AC3"

[MrVideo]

I mean if there will be the possibility in new release of bdrebuilder to know the size each one of audio included in bluray
Why do you need to know that?

[Priapismic]

Hi,
I am trying to rip American Made, which contains only DTS audio but BDRB is unable to extract the audio. Any solution?



- [10:46:52] BuildTreeList() 35602 2702
----------------------
[12/20/19] BD Rebuilder v0.60.29
[10:47:07] Source: AMERICANMADEUHD_UPK75_00800
- Input BD size: 60.19 GB
- Approximate total content: [01:54:53.886]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[10:47:08] PHASE ONE, Encoding
- [10:47:08] Processing: VID_00007 (1 of 2)
- [10:47:08] Extracting A/V streams [VID_00007]
- Extracting video streams [VID_00007]
- Bitstream exception Unknown exception. It does not have to be! Please contact application support team for more information.
- Error in attempt to extract video.
- Bitstream exception Unknown exception. It does not have to be! Please contact application support team for more information.
- Bitstream exception Unknown exception. It does not have to be! Please contact application support team for more information.
[10:47:15] - Failed to retrieve audio, aborted

[jdobbs]

Not sure about that. That error is coming from TSMUXER. Are you sure it's a good rip?

[MrVideo]

In other words...
1) What does MediaInfo have to say about the M2TS file(s)?
2) Start up tsmuxer and have it read the M2TS file(s) and report back.

[Priapismic]

Hopefully I am using BDRB as designed; I understand it processes UHD 4k files. Yes; the rip is fine and I've re-ripped several times.
I finally achieved my goal of ripping the disc to the HD for play on our Samsung QLED TV using MakeMKV, which reencoded the DTS audio (unsupported on Samsung TV) to AAC. But would prefer BDRB (it's been awhile since I donated - need to again...) since it is familiar and can output AC3.
Hope this helps:
17071

[laserfan]

...it's been awhile since I donated - need to again...
As we approach the anniversary of BD-RB's "release...for beta testing", it seems to me that anyone who has used the software during the year should think about a donation, lest Santa declare them "naughty" and leave a lump of coal in their stocking.

;)

And as jdobbs said that fateful Christmas Eve 11 years ago...

Happy Holidays!

[jdobbs]

As we approach the anniversary of BD-RB's "release...for beta testing", it seems to me that anyone who has used the software during the year should think about a donation, lest Santa declare them "naughty" and leave a lump of coal in their stocking.

;)

And as jdobbs said that fateful Christmas Eve 11 years ago...

Happy Holidays!Wow. 11 years... I need to get a life.

@Priapismic

I must have missed that the source was UHD. That bitstream error pops up every now and then on UHD sources. While the team over at GitHub works on it, I'm implementing a workaround for the next release (along with a group of fixes that will improve the reliability of UHD processing). Barring anything unexpected, you should see the release in the next couple of days.

[Priapismic]

Thank you kindly. And, however one thanks a community - thank you all as well.
I'll put something in your stocking on payday.

[Mike-uk]

Merry Christmas all

and thanks to jdobbs for this wonderfull program

and thanks to the tech supports more notably mrvideo and the other less so

[Ch3vr0n]

Wow. 11 years... I need to get a life.

Or at the least publish a stable version and put the uhd builds as beta ;)

[jdobbs]

I have updated the first post of this thread with a link to the latest version of BD-RB (v0.61.01). Changes for this release: - Updated build with a new version of TSMUXER
that supports UHD. Disabled correction
of UHD M2TS, saving considerable time.
- Added code to prevent non-compatible sources
that have been imported but are not compliant
from flagging a "keep original" signal.
- Updated encoding parameters of UHD sources
so that master-display settings using values
of zero are not output for encoding.
- Changed the default so that, on UHD sources,
an original imported file is used for input
for encoding if it is still available.
- Fixed an error that resulted in a "- Source
issue found, attempting correction..." to
popup unnecessarily during UHD muxing and
cause special muxing to take place.
- Corrected an issue that could cause several
odd problems (including a possible wrong
language track) when importing some sources
with TrueHD audio tracks with Atmos.
- Fixed an error in which HDR could (rarely)
not be transferred to newly encoded file.
- Added code to improve muxing speed during
import of UHD video file sources.
- Made numerous changes to make UHD processing
more stable.
- Other minor corrections and cosmetic fixes.A special thanks to a5180007, who has made TSMUXER much more UHD friendly -- taking the burden off of BD Rebuilder.

Also, I want to wish everyone who contributes to this thread Happy Holidays! I hope you all enjoy it.

[MrVideo]

Thanks for the update and Happy Holidays to all.

[MrVideo]

I'm looking into getting a 4K burner. But, here is the issue... the Sony X800M2 4K/BD/3D/DVD/CD player will not play BDXL media. The burners that I've seen offered do BDXL. So, how do you 4K users play copied UHD-4K discs,.i.e., what do you use to burn discs that the player will play?

If you use BDRB to create BD25/BD50 discs, does that get around the issue?

Thanks for any hints. I should be springing for the 4K upgrade in early spring.

[Priapismic]

.i.e., what do you use to burn discs that the player will play?
If you use BDRB to create BD25/BD50 discs, does that get around the issue?
Thanks for any hints. I should be springing for the 4K upgrade in early spring.My 'workaround' came from experienced users; our Samsung QLED has an HDD input port, and supports .m2ts, MKV, etc.
So, rather than play the OEM player restrictions game, I obtained an Asus BW-16D1HT (firmware 3.03) and downgraded it to 3.02 via instructions at MakeMKV. That done, files are transferred to an HD, which is put in a Startech dock (I'm sure many other makes are compatible but I have two others that are not) connected by USB to the TV. The Samsung TV has a built-in software player. Voilà, I can play all of my BDs from one source.
Hope this helps.

[Priapismic]

For those wondering; send the Amazon gift card to email: DVD-RB@JDOBBS.NET

[jdobbs]

I'm looking into getting a 4K burner. But, here is the issue... the Sony X800M2 4K/BD/3D/DVD/CD player will not play BDXL media. The burners that I've seen offered do BDXL. So, how do you 4K users play copied UHD-4K discs,.i.e., what do you use to burn discs that the player will play?

If you use BDRB to create BD25/BD50 discs, does that get around the issue?

Thanks for any hints. I should be springing for the 4K upgrade in early spring.I burn everything to BD-25 or BD-50 discs. Of course that means that almost everything has to be reencoded and that takes a considerable amount of time.

[FilipeAmadeuO]

@jdobbs
Can you please add the possibility to replace the subtitles/audio and change language of subtitles/audio diretly on BDRebuilder GUI ?
Something like right click on subtitle/audio and select file to use for replace…
That would be a nice improvement...

[jdobbs]

@jdobbs
Can you please add the possibility to replace the subtitles/audio and change language of subtitles/audio diretly on BDRebuilder GUI ?
Something like right click on subtitle/audio and select file to use for replace…
That would be a nice improvement...I'll look at it.

[MrVideo]

My 'workaround' came from experienced users; our Samsung QLED has an HDD input port, and supports .m2ts, MKV, etc.
The ultimate plan is for a DLP 4K/3D projector. The reason is that LED flat panels and LED projectors have a delay issue that causes crosstalk when displaying 3D. DLP doesn't have that issue. So, no USB connections. But, there are other ways to read files off the LAN to the projector. It'll be somewhat like what you do.

[MrVideo]

I burn everything to BD-25 or BD-50 discs. Of course that means that almost everything has to be reencoded and that takes a considerable amount of time.
Thanks, I figured that that trick would work.

[Ch3vr0n]

The ultimate plan is for a DLP 4K/3D projector. The reason is that LED flat panels and LED projectors have a delay issue that causes crosstalk when displaying 3D. DLP doesn't have that issue. So, no USB connections. But, there are other ways to read files off the LAN to the projector. It'll be somewhat like what you do.

I suppose you missed out on this one then?

Cause that's exactly what it is 4k capable 3D DLP projector :)

https://www.kickstarter.com/projects/nbl/nebula-cosmos-max-worlds-first-4k-home-cinema-with-3d-audio/

campaign just ended a couple days ago

4k was out of my budget range & i don't own any 4K stuff (for decrypting, or discs themselves). So i grabbed the 1080p version and it my plans work, it'll replace my 42" TV :p

Plans are:

TV decoder to HDMI 1
Chromecast Ultra to HDMI 2
Logitech Z-5500 via toslink for audio

100" TV at a fraction of the cost :p

[MrVideo]

I didn't miss out. BTW, it isn't 3D. This is potentially the projector: www.ebay.com/itm/BenQ-HT3550-True-4K-HDR-Home-Theater-Projector-Refurbished/153747212368?hash=item23cc0c4850:g:~owAAOSwtQxd5Sjn

Potentially 180". 7.1 receiver @ 100w per each of 7 channels. A self powered sub-woofer that can rattle the foundation.

Best to have a projector without keystone, or if it has it, to not use it. Keystone correction means that all of the pixels are not used.

If I were to win the lottery (ya right), the dream projector would be the same ones used in theaters with RealD 3D projection. Those projectors are damn expensive. :eek:

[Ch3vr0n]

It supports DLP 3D just like you talked about.

Sent from my Pixel 3 XL using Tapatalk

[worknstiff]

@ MrVideo; RE: the dream projector would be the same ones used in theaters with RealD 3D projection. Those projectors are damn expensive.

I'm saving my money for 8K and passive 3D that is just around the corner. In a couple of years an OLED 100" 8K is what I am holding out for, lol.

[Michi]

The new version have problems with Dolby Vision discs. My Sony X800M2 plays the rebuilded DV discs "Cold Pursuit" and "The Secret Life Of Pets 2" only with DV off. When I turn DV on, the film is completely black.

With 60.29 the rebuild of Cold Pursuit stops with error, but Pets2 with 60.29 play my X800M2 wit DV fine.

[MrVideo]

It supports DLP 3D just like you talked about.
It does not. Look at the web page again. It supports 3D Audio, not 3D video.

Plus, it does not support lens shift, a needed requirement to avoid the use of keystone correction. Sorry, but IMHO, the projector that I pointed out, fits my needs. YMMV.

[MrVideo]

I'm saving my money for 8K and passive 3D that is just around the corner. In a couple of years an OLED 100" 8K is what I am holding out for, lol.
You better save a lot of money. Getting source material in 8K is going to be really tough. You're lucky if a movie gets shot with 5K gear, let alone 8K. Doing special effects in 8K is extremely expensive.

I discovered something yesterday. While a majority of movie theater projectors are 4K, the DCI spec for 3D is that they are only 2K. Could be why there is no UHD 3D Blu-ray, since there will never be a 3D movie in 4K.

[jdobbs]

The new version have problems with Dolby Vision discs. My Sony X800M2 plays the rebuilded DV discs "Cold Pursuit" and "The Secret Life Of Pets 2" only with DV off. When I turn DV on, the film is completely black.

With 60.29 the rebuild of Cold Pursuit stops with error, but Pets2 with 60.29 play my X800M2 wit DV fine.I need more details. A log would be a good start.

Was it an imported source or UHD-BD?
Was it a movie-only or full backup?
Is is BD output? MP4? MKV?
Was it reencoded, or did you keep the original?

A bug report with nothing to go on leaves me with no choice but to ignore it.

[Ch3vr0n]

We've had the same report over at the redfox forums that there's problems with DV support. (in the german section) users. I don't understand enough german to actually read it. I just understand a word here and there. I can link to the topic if wanted

[Michi]

Both sources are DV UHD-BDs and I made Full Backups with reencoding to BD 50 as output.

[MrVideo]

When editing the config file, the version is still listed as 0.60.0.29.

I'm doing a test UHD of Hunger Games to BD50, pretty much using the defaults, except that the minimum import threshold is 1. I have no idea if it is going to do a single pass or a two-pass encoding.

[jdobbs]

When editing the config file, the version is still listed as 0.60.0.29.

I'm doing a test UHD of Hunger Games to BD50, pretty much using the defaults, except that the minimum import threshold is 1. I have no idea if it is going to do a single pass or a two-pass encoding.By default it will do two pass at high quality. You may be waiting a while.

If you want to do it faster, change the settings to "One Pass (ABR)" and "Good (Fast)". If you that isn't fast enough, you can edit the INI and set ENCODE_QUALITY=5. That will run X265 at it's highest speed. No UHD encode is going to go very fast compared to HD -- but it will be faster that HQ mode. Honestly, if you are outputting to BD-25 or BD-50, you are unlikely see a noticeable quality difference when compared to HQ.

Sorry about the version thing, I forgot to update the internal version number to v0.61.01... it won't hurt anything.

[jdobbs]

By default it will do two pass at high quality. You may be waiting a while.Unfortunately I don't have a BD Player that supports Dolby Vision, so I have to rely on people testing it here.

[jdobbs]

Both sources are DV UHD-BDs and I made Full Backups with reencoding to BD 50 as output.Just as a test:

1. Download the executable at this link (v0.61.02) (https://jammernhilftnichts.de/jdobbs/BDRB.exe).
2. Replace the EXE in the BD-RB folder
3. Add the following line to the [Options] area of your BDREBUILDER.INI file:

UHD_TSMUXER=0

4. Report back and let me know the results. If it works, it will help me in determining what is wrong with the tsmuxer4k Dolby output.

That line in the INI tells BD-RB to use the old method (using the old TSMUXER version and remuxing it within BD-RB). It has some fixes that weren't in v0.60.29. You need this new version, though, as that line will cause a problem in v0.61.01.

[MrVideo]

The computer that it is being recoded on is pretty much only used for this kind of stuff, so it can take as long as it wants.

I don't have the UHD player yet. That won't happen until early next year. This is to just test the whole recoding process. The audio is Dolby Atmos and I will be setting up for that capability. At least that is the plan. Certain things must take place first.

[Michi]

The log-file of the DV disc Cold Pursuit:

[12.28.19] BD Rebuilder v0.61.01
[15:57:21] Source: COLD_PURSUIT
- Input BD size: 78,62 GB
- Approximate total content: [02:04:46.291]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Fastest, BD-25+), CRF
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[15:57:29] PHASE ONE, Encoding
- [15:57:29] Processing: VID_00000 (1 of 14)
- [15:57:29] Extracting A/V streams [VID_00000]
- [15:57:34] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 1.046 frames
- [15:57:34] Performing CRF Prediction...
- Analyzing 1,00 13,25 12,75 [13,00]
- [15:57:54] Encoding using constant rate factor.
- [15:59:10] Video Encode complete
- [15:59:10] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [15:59:10] Multiplexing M2TS
- [15:59:14] Processing: VID_00001 (2 of 14)
- [15:59:14] Extracting A/V streams [VID_00001]
- [15:59:18] Reencoding video [VID_00001]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 631 frames
- [15:59:18] Performing CRF Prediction...
- Analyzing 10,50 5,75 3,38 2,19 1,59 1,30 1,15 1,07 1,04 [1,00]
- [16:02:36] Encoding using constant rate factor.
- [16:03:21] Video Encode complete
- [16:03:21] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [16:03:21] Multiplexing M2TS
- [16:03:24] Processing: VID_00002 (3 of 14)
- [16:03:24] Extracting A/V streams [VID_00002]
- [16:03:48] Reencoding video [VID_00002]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 8.582 frames
- [16:03:48] Performing CRF Prediction...
- Analyzing 1,00 9,95 8,00 [8,30]
- [16:04:12] Encoding using constant rate factor.
- [16:14:16] Video Encode complete
- [16:14:16] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [16:14:16] Multiplexing M2TS
- [16:14:25] Processing: VID_00003 (4 of 14)
- [16:14:25] Extracting A/V streams [VID_00003]
- [16:14:29] Reencoding video [VID_00003]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 211 frames
- Bitrate: 35.000 Kbs
- [16:14:29] Reencoding: VID_00003, Pass 1 of 2
- [16:14:43] Reencoding: VID_00003, Pass 2 of 2
- [16:15:00] Video Encode complete
- [16:15:00] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [16:15:00] Multiplexing M2TS
- [16:15:04] Processing: VID_00008 (5 of 14)
- [16:15:04] Extracting A/V streams [VID_00008]
- Extracting video streams [VID_00008]
- Extracting secondary video [VID_00008]
- Extracting audio/subtitle streams [VID_00008]
- [16:33:58] Reencoding video [VID_00008]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 160.215 frames
- [16:33:58] Performing CRF Prediction...
- Analyzing 1,00 8,90 8,15 8,53 8,34 8,43 8,38 [8,35]
- Aborted...
[17:32:36]PHASE ONE aborted by user request
----------------------
[12.28.19] BD Rebuilder v0.61.01
[17:32:41] Source: COLD_PURSUIT
- Input BD size: 78,62 GB
- Approximate total content: [02:04:46.291]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Fastest, BD-25+), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[17:32:42] PHASE ONE, Encoding
- [17:32:42] Processing: VID_00008 (5 of 14)
- [17:33:14] Reencoding video [VID_00008]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 160.215 frames
- Bitrate: 35.000 Kbs
- [17:33:14] Reencoding: VID_00008, Pass 1 of 1
- [21:57:07] Video Encode complete
- [21:57:07] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [21:57:07] Multiplexing M2TS
- [21:59:06] Processing: VID_00020 (6 of 14)
- [21:59:06] Extracting A/V streams [VID_00020]
- [21:59:10] Reencoding video [VID_00020]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 240 frames
- Bitrate: 1.489 Kbs
- [21:59:10] Reencoding: VID_00020, Pass 1 of 1
- [21:59:26] Video Encode complete
- [21:59:26] Processing audio tracks
- [21:59:26] Multiplexing M2TS
- [21:59:29] Processing: VID_00021 (7 of 14)
- [21:59:29] Extracting A/V streams [VID_00021]
- [21:59:33] Reencoding video [VID_00021]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 167 frames
- Bitrate: 1.244 Kbs
- [21:59:33] Reencoding: VID_00021, Pass 1 of 1
- [21:59:44] Video Encode complete
- [21:59:44] Processing audio tracks
- [21:59:44] Multiplexing M2TS
- [21:59:47] Processing: VID_00022 (8 of 14)
- [21:59:47] Extracting A/V streams [VID_00022]
- [21:59:51] Reencoding video [VID_00022]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 168 frames
- Bitrate: 1.339 Kbs
- [21:59:51] Reencoding: VID_00022, Pass 1 of 1
- [22:00:01] Video Encode complete
- [22:00:01] Processing audio tracks
- [22:00:01] Multiplexing M2TS
- [22:00:05] Processing: VID_00025 (9 of 14)
- [22:00:05] Extracting A/V streams [VID_00025]
- [22:00:08] Reencoding video [VID_00025]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 120 frames
- Bitrate: 791 Kbs
- [22:00:08] Reencoding: VID_00025, Pass 1 of 1
- [22:00:16] Video Encode complete
- [22:00:16] Processing audio tracks
- [22:00:16] Multiplexing M2TS
- [22:00:20] Processing: VID_00026 (10 of 14)
- [22:00:20] Extracting A/V streams [VID_00026]
- [22:00:23] Reencoding video [VID_00026]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 192 frames
- Bitrate: 2.790 Kbs
- [22:00:23] Reencoding: VID_00026, Pass 1 of 1
- [22:00:35] Video Encode complete
- [22:00:35] Processing audio tracks
- [22:00:35] Multiplexing M2TS
- [22:00:39] Processing: VID_00027 (11 of 14)
- [22:00:39] Extracting A/V streams [VID_00027]
- [22:00:42] Reencoding video [VID_00027]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 192 frames
- Bitrate: 1.400 Kbs
- [22:00:42] Reencoding: VID_00027, Pass 1 of 1
- [22:00:55] Video Encode complete
- [22:00:55] Processing audio tracks
- [22:00:55] Multiplexing M2TS
- [22:00:58] Processing: VID_00028 (12 of 14)
- [22:00:58] Extracting A/V streams [VID_00028]
- [22:01:02] Reencoding video [VID_00028]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 120 frames
- Bitrate: 500 Kbs
- [22:01:02] Reencoding: VID_00028, Pass 1 of 1
- [22:01:10] Video Encode complete
- [22:01:10] Processing audio tracks
- [22:01:10] Multiplexing M2TS
- [22:01:13] Processing: VID_00029 (13 of 14)
- [22:01:13] Extracting A/V streams [VID_00029]
- [22:01:17] Reencoding video [VID_00029]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 480 frames
- Bitrate: 29.360 Kbs
- [22:01:17] Reencoding: VID_00029, Pass 1 of 1
- [22:02:13] Video Encode complete
- [22:02:13] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:02:13] Multiplexing M2TS
- [22:02:17] Processing: VID_00031 (14 of 14)
- [22:02:17] Extracting A/V streams [VID_00031]
- [22:02:21] Reencoding video [VID_00031]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 168 frames
- Bitrate: 16.925 Kbs
- [22:02:21] Reencoding: VID_00031, Pass 1 of 1
- [22:02:34] Video Encode complete
- [22:02:34] Processing audio tracks
- [22:02:34] Multiplexing M2TS
[22:02:38]PHASE ONE complete
[22:02:38]PHASE TWO - Rebuild Started
- [22:02:38] Rebuilding BD file Structure
[22:02:46] - Encode and Rebuild complete
[22:02:46] Writing BD structure to ISO file
- ImgBurn completed successfully
- COLD_PURSUIT folder removed.
- WORKFILES folder removed.
[22:03:56] JOB: COLD_PURSUIT finished.

[Ch3vr0n]

Please put such long logs between the [code] tags

[MrVideo]

By default it will do two pass at high quality. You may be waiting a while.
It is saying pass 1 of 1. Looks like it is going to take over a week. :eek:

[SquallMX]

I'm getting a "Bitstream exception Unknown exception. It does not have to be! Please contact application support team for more information" error msg:

[12/28/19] BD Rebuilder v0.61.01
[13:13:29] Source: GUASON
- Input BD size: 52.45 GB
- Approximate total content: [02:13:01.807]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- MOVIE and MENUS mode enabled
- Quality: Better (Faster), Two Pass
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[13:13:29] PHASE ONE, Encoding
- [13:13:29] Blanking: VID_00000 (1 of 15)
- [13:13:29] Blanking: VID_00001 (2 of 15)
- [13:13:29] Blanking: VID_00002 (3 of 15)
- [13:13:29] Blanking: VID_00003 (4 of 15)
- [13:13:29] Blanking: VID_00004 (5 of 15)
- [13:13:29] Processing: VID_00005 (6 of 15)
- [13:13:29] Extracting A/V streams [VID_00005]
- [13:13:33] Reencoding video [VID_00005]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 6 frames
- Bitrate: 500 Kbs
- [13:13:33] Reencoding: VID_00005, Pass 1 of 2
- [13:13:34] Reencoding: VID_00005, Pass 2 of 2
- [13:13:35] Video Encode complete
- [13:13:36] Processing audio tracks
- [13:13:36] Multiplexing M2TS
- [13:13:39] Blanking: VID_00006 (7 of 15)
- [13:13:39] Blanking: VID_00008 (8 of 15)
- [13:13:39] Blanking: VID_00009 (9 of 15)
- [13:13:39] Blanking: VID_00010 (10 of 15)
- [13:13:39] Processing: VID_00011 (11 of 15)
- [13:13:39] Extracting A/V streams [VID_00011]
- [13:13:43] Reencoding video [VID_00011]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 302 frames
- Bitrate: 17,304 Kbs
- [13:13:43] Reencoding: VID_00011, Pass 1 of 2
- [13:14:03] Reencoding: VID_00011, Pass 2 of 2
- [13:14:21] Video Encode complete
- [13:14:21] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [13:14:21] Multiplexing M2TS
- [13:14:25] Blanking: VID_00013 (12 of 15)
- [13:14:25] Processing: VID_00014 (13 of 15)
- [13:14:25] Extracting A/V streams [VID_00014]
- Extracting video streams [VID_00014]
- Extracting secondary video [VID_00014]
- Extracting audio/subtitle streams [VID_00014]
- [13:22:05] Reencoding video [VID_00014]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 175,243 frames
- Bitrate: 15,299 Kbs
- [13:22:05] Reencoding: VID_00014, Pass 1 of 2
- [16:41:36] Reencoding: VID_00014, Pass 2 of 2
- [19:46:33] Video Encode complete
- [19:46:33] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (eng): Keeping original audio
- Track 4354 (eng): Keeping original audio
- Track 4355 (fra): Keeping original audio
- Track 4356 (spa): Keeping original audio
- [19:46:33] Multiplexing M2TS
- Bitstream exception. Adjusting...
- Error in attempt to multiplex: MUX_00014.meta
- Bitstream exception Unknown exception. It does not have to be! Please contact application support team for more information.
[19:48:26] - Failed to build structure, aborted

[Michi]

Muxing error with 61.02 and old tsmuxer:

[12.28.19] BD Rebuilder v0.61.02
[22:50:56] Source: COLD_PURSUIT
- Input BD size: 78,62 GB
- Approximate total content: [02:04:46.291]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Fastest, BD-25+), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[22:50:56] PHASE ONE, Encoding
- [22:50:56] Processing: VID_00000 (1 of 14)
- [22:50:56] Extracting A/V streams [VID_00000]
- [22:51:01] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 1.046 frames
- Bitrate: 24.020 Kbs
- [22:51:01] Reencoding: VID_00000, Pass 1 of 1
- [22:52:23] Video Encode complete
- [22:52:23] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [22:52:23] Multiplexing M2TS
- [22:52:30] Processing: VID_00001 (2 of 14)
- [22:52:30] Extracting A/V streams [VID_00001]
- [22:52:34] Reencoding video [VID_00001]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 631 frames
- Bitrate: 9.355 Kbs
- [22:52:34] Reencoding: VID_00001, Pass 1 of 1
- [22:53:18] Video Encode complete
- [22:53:18] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [22:53:18] Multiplexing M2TS
- [22:53:22] Processing: VID_00002 (3 of 14)
- [22:53:22] Extracting A/V streams [VID_00002]
- [22:53:45] Reencoding video [VID_00002]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 8.582 frames
- Bitrate: 35.000 Kbs
- [22:53:46] Reencoding: VID_00002, Pass 1 of 1
- [23:03:43] Video Encode complete
- [23:03:43] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [23:03:43] Multiplexing M2TS
- [23:04:39] Processing: VID_00003 (4 of 14)
- [23:04:39] Extracting A/V streams [VID_00003]
- [23:04:43] Reencoding video [VID_00003]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 211 frames
- Bitrate: 35.000 Kbs
- [23:04:43] Reencoding: VID_00003, Pass 1 of 1
- [23:04:58] Video Encode complete
- [23:04:58] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [23:04:58] Multiplexing M2TS
- [23:05:03] Processing: VID_00008 (5 of 14)
- [23:05:03] Extracting A/V streams [VID_00008]
- Extracting video streams [VID_00008]
- Extracting secondary video [VID_00008]
- Extracting audio/subtitle streams [VID_00008]
- [23:23:57] Reencoding video [VID_00008]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 160.215 frames
- Bitrate: 35.000 Kbs
- [23:23:57] Reencoding: VID_00008, Pass 1 of 1
- [02:17:03] Video Encode complete
- [02:17:03] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [02:17:03] Multiplexing M2TS
- [02:33:31] Processing: VID_00020 (6 of 14)
- [02:33:31] Extracting A/V streams [VID_00020]
- [02:33:34] Reencoding video [VID_00020]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 240 frames
- Bitrate: 1.489 Kbs
- [02:33:34] Reencoding: VID_00020, Pass 1 of 1
- [02:33:49] Video Encode complete
- [02:33:49] Processing audio tracks
- [02:33:49] Multiplexing M2TS
- [02:33:52] Processing: VID_00021 (7 of 14)
- [02:33:52] Extracting A/V streams [VID_00021]
- [02:33:56] Reencoding video [VID_00021]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 167 frames
- Bitrate: 1.244 Kbs
- [02:33:56] Reencoding: VID_00021, Pass 1 of 1
- [02:34:06] Video Encode complete
- [02:34:06] Processing audio tracks
- [02:34:06] Multiplexing M2TS
- [02:34:11] Processing: VID_00022 (8 of 14)
- [02:34:11] Extracting A/V streams [VID_00022]
- [02:34:14] Reencoding video [VID_00022]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 168 frames
- Bitrate: 1.339 Kbs
- [02:34:14] Reencoding: VID_00022, Pass 1 of 1
- [02:34:24] Video Encode complete
- [02:34:24] Processing audio tracks
- [02:34:24] Multiplexing M2TS
- [02:34:29] Processing: VID_00025 (9 of 14)
- [02:34:29] Extracting A/V streams [VID_00025]
- [02:34:33] Reencoding video [VID_00025]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 120 frames
- Bitrate: 791 Kbs
- [02:34:33] Reencoding: VID_00025, Pass 1 of 1
- [02:34:40] Video Encode complete
- [02:34:40] Processing audio tracks
- [02:34:40] Multiplexing M2TS
- [02:34:48] UHD_Correct_M2TS() 00005 8102
[04:57:11]PHASE ONE aborted by user request

[Priapismic]

With much mention of tsmuxer; The 1st post in this thread does not specifically state if the user needs to download and install the latest version - in addition to BDRB. A clarification there would perhaps be helpful to all.

[Ch3vr0n]

That's because you don't need to. When you download BDRB all proper versions are included in the zipfile itself (tsmuxer or otherwise). There's nothing to clarify, always has been that way.

[MrVideo]

Not true. There are some programs that need to be separately installed. Those are noted in the first post. Otherwise, the program is included.

[Ch3vr0n]

Not true. There are some programs that need to be separately installed. Those are noted in the first post. Otherwise, the program is included.Yes true, he makes no mention of the other tools. He specifically stated 'tsmuxer' 'install'. That is what I responded to. Nothing else

Though perhaps my 'otherwise' could have been a bit more precise and mention the exact 'subtools' such as mp4box etc. I'll not talking about the lav filters...

Sent from my Pixel 3 XL using Tapatalk

[jdobbs]

With much mention of tsmuxer; The 1st post in this thread does not specifically state if the user needs to download and install the latest version - in addition to BDRB. A clarification there would perhaps be helpful to all.Definitely not. The versions greater than v2.6.12 (the one included with BD-RB for download) are not stable. I am now also including a version called tsmuxer4k.exe -- which is a newer version that I have tested before including and only gets executed for UHD muxing.

If you follow the directions (exactly) as they are outlined in the first post, you should be ok. Any changes to those instructions are done at your own risk and can result in self-inflicted problems. That includes changing versions for any of the helper apps.

[jdobbs]

The log-file of the DV disc Cold PursuitHave you tried v0.61.02 yet?

[Michi]

Have you tried v0.61.02 yet?

Yes, I tried 61.02 and it produces the same error as 60.29.

[12.28.19] BD Rebuilder v0.61.02
[22:50:56] Source: COLD_PURSUIT
- Input BD size: 78,62 GB
- Approximate total content: [02:04:46.291]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Fastest, BD-25+), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[22:50:56] PHASE ONE, Encoding
- [22:50:56] Processing: VID_00000 (1 of 14)
- [22:50:56] Extracting A/V streams [VID_00000]
- [22:51:01] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 1.046 frames
- Bitrate: 24.020 Kbs
- [22:51:01] Reencoding: VID_00000, Pass 1 of 1
- [22:52:23] Video Encode complete
- [22:52:23] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [22:52:23] Multiplexing M2TS
- [22:52:30] Processing: VID_00001 (2 of 14)
- [22:52:30] Extracting A/V streams [VID_00001]
- [22:52:34] Reencoding video [VID_00001]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 631 frames
- Bitrate: 9.355 Kbs
- [22:52:34] Reencoding: VID_00001, Pass 1 of 1
- [22:53:18] Video Encode complete
- [22:53:18] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [22:53:18] Multiplexing M2TS
- [22:53:22] Processing: VID_00002 (3 of 14)
- [22:53:22] Extracting A/V streams [VID_00002]
- [22:53:45] Reencoding video [VID_00002]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 8.582 frames
- Bitrate: 35.000 Kbs
- [22:53:46] Reencoding: VID_00002, Pass 1 of 1
- [23:03:43] Video Encode complete
- [23:03:43] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [23:03:43] Multiplexing M2TS
- [23:04:39] Processing: VID_00003 (4 of 14)
- [23:04:39] Extracting A/V streams [VID_00003]
- [23:04:43] Reencoding video [VID_00003]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 211 frames
- Bitrate: 35.000 Kbs
- [23:04:43] Reencoding: VID_00003, Pass 1 of 1
- [23:04:58] Video Encode complete
- [23:04:58] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [23:04:58] Multiplexing M2TS
- [23:05:03] Processing: VID_00008 (5 of 14)
- [23:05:03] Extracting A/V streams [VID_00008]
- Extracting video streams [VID_00008]
- Extracting secondary video [VID_00008]
- Extracting audio/subtitle streams [VID_00008]
- [23:23:57] Reencoding video [VID_00008]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 160.215 frames
- Bitrate: 35.000 Kbs
- [23:23:57] Reencoding: VID_00008, Pass 1 of 1
- [02:17:03] Video Encode complete
- [02:17:03] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [02:17:03] Multiplexing M2TS
- [02:33:31] Processing: VID_00020 (6 of 14)
- [02:33:31] Extracting A/V streams [VID_00020]
- [02:33:34] Reencoding video [VID_00020]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 240 frames
- Bitrate: 1.489 Kbs
- [02:33:34] Reencoding: VID_00020, Pass 1 of 1
- [02:33:49] Video Encode complete
- [02:33:49] Processing audio tracks
- [02:33:49] Multiplexing M2TS
- [02:33:52] Processing: VID_00021 (7 of 14)
- [02:33:52] Extracting A/V streams [VID_00021]
- [02:33:56] Reencoding video [VID_00021]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 167 frames
- Bitrate: 1.244 Kbs
- [02:33:56] Reencoding: VID_00021, Pass 1 of 1
- [02:34:06] Video Encode complete
- [02:34:06] Processing audio tracks
- [02:34:06] Multiplexing M2TS
- [02:34:11] Processing: VID_00022 (8 of 14)
- [02:34:11] Extracting A/V streams [VID_00022]
- [02:34:14] Reencoding video [VID_00022]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 168 frames
- Bitrate: 1.339 Kbs
- [02:34:14] Reencoding: VID_00022, Pass 1 of 1
- [02:34:24] Video Encode complete
- [02:34:24] Processing audio tracks
- [02:34:24] Multiplexing M2TS
- [02:34:29] Processing: VID_00025 (9 of 14)
- [02:34:29] Extracting A/V streams [VID_00025]
- [02:34:33] Reencoding video [VID_00025]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 120 frames
- Bitrate: 791 Kbs
- [02:34:33] Reencoding: VID_00025, Pass 1 of 1
- [02:34:40] Video Encode complete
- [02:34:40] Processing audio tracks
- [02:34:40] Multiplexing M2TS
- [02:34:48] UHD_Correct_M2TS() 00005 8102
[04:57:11]PHASE ONE aborted by user request

[Priapismic]

Definitely not. The versions greater than v2.6.12 (the one included with BD-RB for download) are not stable. I am now also including a version called tsmuxer4k.exe -- which is a newer version that I have tested before including and only gets executed for UHD muxing.

If you follow the directions (exactly) as they are outlined in the first post, you should be ok. Any changes to those instructions are done at your own risk and can result in self-inflicted problems. That includes changing versions for any of the helper apps.I just wish the post stated that the download includes tsmuxer.

[Ch3vr0n]

If he were to do that and be consistent he'd have to state that it also includes a version of DGIndex, HCEncoder, FRIM, mkvextract, mkvmerge and every other x264/265 version. Can't leave those out can we?

[MrVideo]

Though perhaps my 'otherwise' could have been a bit more precise and mention the exact 'subtools' such as mp4box etc. I'll not talking about the lav filters...
Yes, it is the "otherwise" that tripped my posting.

[Michi]

Deumuxing error on RED2:

BD Rebuilder v0.61.02
[19:19:34] Source: RED_2
- Input BD size: 59,23 GB
- Approximate total content: [03:02:05.879]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Fastest, BD-25+), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[19:19:34] PHASE ONE, Encoding
- [19:19:34] Processing: VID_00000 (1 of 8)
- [19:19:34] Extracting A/V streams [VID_00000]
- [19:27:02] Reencoding video [VID_00000]
- [19:27:02] Keeping original video (no reencode)
- [19:27:02] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [19:27:02] Multiplexing M2TS
- [19:27:59] Processing: VID_00001 (2 of 8)
- [19:27:59] Extracting A/V streams [VID_00001]
- Extracting video streams [VID_00001]
- Extracting audio/subtitle streams [VID_00001]
- Network Optix tsMuxeR. Version 2.6.12. www.networkoptix.com
- Extracting audio streams [VID_00001]
- Error in attempt to extract audio.
- Network Optix tsMuxeR. Version 2.6.12. www.networkoptix.com
- Network Optix tsMuxeR. Version 2.6.12. www.networkoptix.com
[19:30:37] - Failed to retrieve audio, aborted

[zamengo]

Multiplexing error on Joker.


----------------------
[12/29/19] BD Rebuilder v0.61.01
[17:56:19] Source: JOKER
- Input BD size: 53.28 GB
- Approximate total content: [02:13:01.807]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Very Good (Very Fast), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=448
[17:56:19] PHASE ONE, Encoding
- [17:56:19] Processing: VID_00004 (1 of 2)
- [17:56:19] Extracting A/V streams [VID_00004]
- [17:56:34] Reencoding video [VID_00004]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 8,160 frames
- Bitrate: 5,652 Kbs
- [17:56:34] Reencoding: VID_00004, Pass 1 of 1
- [18:18:44] Video Encode complete
- [18:18:44] Processing audio tracks
- [18:18:44] Multiplexing M2TS
- [18:18:49] Processing: VID_00014 (2 of 2)
- [18:18:49] Extracting A/V streams [VID_00014]
- Extracting video streams [VID_00014]
- Extracting secondary video [VID_00014]
- Extracting audio/subtitle streams [VID_00014]
- [18:47:27] Reencoding video [VID_00014]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 175,243 frames
- Bitrate: 20,541 Kbs
- [18:47:27] Reencoding: VID_00014, Pass 1 of 1
- [00:33:14] Video Encode complete
- [00:33:14] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (eng): Keeping original audio
- Track 4354 (eng): Keeping original audio
- Track 4355 (fra): Keeping original audio
- Track 4356 (spa): Keeping original audio
- [00:34:40] Multiplexing M2TS
- Bitstream exception. Adjusting...
- Error in attempt to multiplex: MUX_00014.meta
- Bitstream exception Unknown exception. It does not have to be! Please contact application support team for more information.
[00:44:07] - Failed to build structure, aborted


EDIT: I found the problem.

The problem is the Dolby Vision track, i try to remux with last tsmuxer "w64-nightly-2019-12-30--01-10-40" and give the same error.

When remove the Dolby Vision track, the remux runs fine.

I don't have a Dolby Vision TV, can I keep this without Dolby Vision track? Any way to add a option to avoid Dolby Vision in BDRebuilder?

EDIT2: I found a solution, I replace the dolby vision track in the work folder with the original from full disc and everything works fine.

@Jobbs, you make any change in dolby vision track? I don't understand why the original one work fine.

[cartman0208]

I can confirm the multiplexing error on ALITA_BATTLE_ANGEL
Strangely the encoding of the same disc was working fine with v0.60.29

[zamengo]

I can confirm the multiplexing error on ALITA_BATTLE_ANGEL
Strangely the encoding of the same disc was working fine with v0.60.29

Alita works for me too on v0.60.29.

I think this is a bug in new tsmuxer, I try to make a remux with the cli version from 10 days ago and can't recognize the sequence of m2ts files.

I don't know what the version Jdobbs include on last bdrb version, but with the tsmuxer from 2019-12-28 I can make a remux from Alite without issues.

Already have a new tsmuxer version "w64-nightly-2019-12-30".

[cartman0208]

I just tried with v0.61.02 and the option UHD_TSMUXER=0 ...
that resolved the error

I wouldn't change any of the included versions ... as said many times: that creates more problems as it solves...

[ripem2011]

I just tried with v0.61.02 and the option UHD_TSMUXER=0 ...
that resolved the error

I wouldn't change any of the included versions ... as said many times: that creates more problems as it solves...

where is that option UHD TSMUXER i dont see it in the config file with v0.6.02

[zamengo]

where is that option UHD TSMUXER i dont see it in the config file with v0.6.02

This is a hidden option, add line in your .ini

[Lathe]

It is saying pass 1 of 1. Looks like it is going to take over a week. :eek:

Well, you know what they say...

7 days without BDRB makes one weak...



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

[MrVideo]

@jdobbs
Is there a GUI version of the tsmuxer you are using? And if so, where can one get it?

[MrVideo]

By default it will do two pass at high quality.
Only one pass was done.

[zamengo]

@jdobbs
Is there a GUI version of the tsmuxer you are using? And if so, where can one get it?

In github, send a pm to you.

[Dofin]

Hello, I've been using BD Rebuilder for years but recently it has started to completely freeze my PC. At first, I had thought about a heat issue but it is not as "Core temp" indicated. I've checked used software and everything looked working properly. Any suggestions ? Running Windows 10 PRO on eight core AMD processor. Many thanks.

Note: can not get a log as once PC's frozen, I do not have access to my mouse, programs or whatever was running, including Tasks Management. Only a hard reboot, depressing reset button on PC, works.

[Michi]

@jdobbs
Is there a GUI version of the tsmuxer you are using? And if so, where can one get it?

The latest nightly build with gui:

https://www.videohelp.com/software/tsMuxeR

[MrVideo]

Thanks, I already have it. You gotta be quicker on the draw. :D

[MrVideo]

The rebuild of a UHD blu-ray to BD-50 has completed w/o any errors. Nothing to test it on though. It will be a while before I do.

[cartman0208]

Only one pass was done.

Noticed that, too ...
If set to "Automatic Quality Settings", there's only one pass
You might want to uncheck that and then go to encoder settings again and uncheck any "one pass...", then you get two passes ... which will take even longer :D

@jdobbs: is there a reason for the strange sorting in the encoder quality menu? (Good is below Highest, but it seems to belong to the top?)

[MrVideo]

It took so long with one pass, setting it up for two will be like Rip Van Winkle.

[Lowpro]

I'd love to be able to take a movie that includes shifting aspect ratios and run it through BD Rebuilder having it reencode the video, so that the end result is a fixed aspect ratio.

An example would be a movie in the 2.40:1 aspect ratio where in just a couple scenes the aspect ratio opens up to 1.78:1. Would love to be able to reencode the video so that the entire film is in 2.40:1 instead, the IMAX portions above and below the 2.40:1 portion being replaced with black bars as is the case with the rest of the film.

I watch movies using a front projector and 150" 1.78:1 projector screen. For aspect ratios north or south of 1.78:1 I mask down to the projected image area with black velvet masking. I'm not interested in leaving unused portions of my projector screen unmasked for the entire length of a scope film because for a couple minutes during the film the aspect ratio jumps to 1.78:1.

Curious to learn how feasible such an option might be for BD Rebuilder or if anyone knows, how I might go about accomplishing the same with other tools out there.

@lowpro
BDRB has the possibility to add avisynth scripts. Assuming your source is 1920x1080, try
crop(0,120,-0,-120) #1.78 to 2.40
addborders(0,120,0,120) #letterbox (mask) for for blu-ray compliance

(It works in avisynth, I didn't try to include it in BDRB)

Thanks. I'll give that a try and yes, I own several movies on Blu-ray (1920x1080) that contain multiple aspect ratios. I'd like to create versions of each where the aspect ratio doesn't change. For example, if the main aspect ratio is 2.39:1 I'd like to mask everything above and below that visible area of the frame during times when the aspect ratio has changed. I don't care what content I lose as a result.

This worked beautifully by the way. The first film I tried this on was Mission: Impossible - Fallout (https://www.lowpro.net/phpdvdprofiler/index.php?mediaid=032429309891&action=show). Added the script you provided via "Settings > Setup > Use AVS Filters during encoding", then creating a fresh movie-only backup. Worked like a charm. Was wonderful to be able to watch the film (...my projector screen physically masked down to 2.40:1) without those aerial sequences (1.78:1) being projected on the black velvet masking above and below the 2.40:1 screen area. The IMAX sequences do look great, but it's not worth the trade-off for me.

[Devilman1]

Hello, I've been using BD Rebuilder for years but recently it has started to completely freeze my PC. At first, I had thought about a heat issue but it is not as "Core temp" indicated. I've checked used software and everything looked working properly. Any suggestions ? Running Windows 10 PRO on eight core AMD processor. Many thanks.

Note: can not get a log as once PC's frozen, I do not have access to my mouse, programs or whatever was running, including Tasks Management. Only a hard reboot, depressing reset button on PC, works.

This happened to me in the past when I had a faulty emory stick or a faulty capacitor on the Motherboard or on the Graphic card, but normally it happens also when using other stressing software

[jdobbs]

@jdobbs: is there a reason for the strange sorting in the encoder quality menu? (Good is below Highest, but it seems to belong to the top?)The last couple of encode options got added after the fact... so they are out of sequence. I just didn't feel like having to go back through the code and change the numbering for every reference. Normally "Good" doesn't even show as an option (until you use it by manually setting it in the INI). There's also an "Ultra-High (Extremely Slow)" setting that you can use by manually setting your INI value to 4.

[jdobbs]

Here's a piece of information I discovered that I think is interesting. The HEVC codec, according to UHD-BD spec is meant to be used only with 2160p and 1080p sources and those two resolutions are all that is supposed to be supported. But... the settings in the MPLS and CLPI files include other formats. So I did some experimenting... and low and behold, I can create a disc that uses the HEVC codec on 480/576 and 720p sources -- and my Sony UHD-BD Player accepts it and plays it back just as if it were meant to do so.

That's a big deal if you are trying to backup some old DVDs (like series discs) onto BD, as HEVC is much more efficient (especially at low bitrates) and you can fit a LOT of old episodes on a 50GB disc when using it.

Just thought I'd mention it. If someone else would like to try it... I'd be interested to know if other players accept it as well. You can do it with the new TSMUXER using the --blu-ray-v3 setting. The only thing I noticed that is a little odd is that it seems to always assume a 16:9 aspect ratio (which can be fixed with a little patching).

If it appears to be universal among players, I may add it as an option in BD-RB (with a warning that it isn't actually within spec).

[Emulgator]

Good find ! I shall try this on a UDP-205.
As soon as you have a BD-RB test version ready, please let me know.

Edit:
Now I see, I shall try using tsMuxeR 2.6.15 first so that you can implement it in BD-RB if sucess can be reported.

[jdobbs]

I have updated the first post of this thread with a link to the most recent version of BD-RB (v0.61.03). Changes for this release:- Updated the included TSMUXER4K version to the
most current release that supports UHD. This
should fix dolbyvision problems experienced
in 61.01. If you added UHD_TSMUXER=0 to your
your INI -- it should be removed in order to
enable the new TSMUXER version.
- Corrected an issue in which performing a
build with UHD_TSMUXER=0 could result in a
"Error in attempt to create UHD CLPI" error
- Fixed a rare issue associated with importing
an MPEG-2 source with telecined video.
- Modified alternate build routine so that SRT
files that are kept are limited to those
selected in the SETUP dialog.
- Other minor corrections and cosmetic fixes.

[Michi]

Nothing has changed with the new version. My Sony X800M2 plays DV Rebuilds only in HDR , when DV is off. When I turn DV on the Sony on, the main film is black.

DV remuxes of the main film with the last tsmuxer plays my Sony without problems.

[01.11.20] BD Rebuilder v0.61.03
[15:17:05] Source: COLD_PURSUIT
- Input BD size: 78,62 GB
- Approximate total content: [02:04:46.291]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Fastest, BD-25+), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[15:17:07] PHASE ONE, Encoding
- [15:17:07] Processing: VID_00000 (1 of 14)
- [15:17:07] Extracting A/V streams [VID_00000]
- [15:17:11] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 1.046 frames
- Bitrate: 24.020 Kbs
- [15:17:11] Reencoding: VID_00000, Pass 1 of 1
- [15:19:04] Video Encode complete
- [15:19:04] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [15:19:04] Multiplexing M2TS
- [15:19:08] Processing: VID_00001 (2 of 14)
- [15:19:08] Extracting A/V streams [VID_00001]
- [15:19:12] Reencoding video [VID_00001]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 631 frames
- Bitrate: 9.355 Kbs
- [15:19:12] Reencoding: VID_00001, Pass 1 of 1
- [15:20:04] Video Encode complete
- [15:20:04] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [15:20:04] Multiplexing M2TS
- [15:20:08] Processing: VID_00002 (3 of 14)
- [15:20:08] Extracting A/V streams [VID_00002]
- [15:20:31] Reencoding video [VID_00002]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 8.582 frames
- Bitrate: 35.000 Kbs
- [15:20:31] Reencoding: VID_00002, Pass 1 of 1
- [15:34:37] Video Encode complete
- [15:34:37] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [15:34:37] Multiplexing M2TS
- [15:34:45] Processing: VID_00003 (4 of 14)
- [15:34:45] Extracting A/V streams [VID_00003]
- [15:34:49] Reencoding video [VID_00003]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 211 frames
- Bitrate: 35.000 Kbs
- [15:34:49] Reencoding: VID_00003, Pass 1 of 1
- [15:35:16] Video Encode complete
- [15:35:16] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [15:35:16] Multiplexing M2TS
- [15:35:20] Processing: VID_00008 (5 of 14)
- [15:35:20] Extracting A/V streams [VID_00008]
- Extracting video streams [VID_00008]
- Extracting secondary video [VID_00008]
- Extracting audio/subtitle streams [VID_00008]
- [15:54:17] Reencoding video [VID_00008]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 160.215 frames
- Bitrate: 35.000 Kbs
- [15:54:17] Reencoding: VID_00008, Pass 1 of 1
- [18:57:39] Video Encode complete
- [18:57:39] Processing audio tracks
- Track 4356 (deu): Keeping original audio
- [18:57:39] Multiplexing M2TS
[18:57:44]PHASE ONE aborted by user request
----------------------
[01.11.20] BD Rebuilder v0.61.03
[19:01:31] Source: COLD_PURSUIT
- Input BD size: 78,62 GB
- Approximate total content: [02:04:46.291]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Fastest, BD-25+), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[19:01:32] PHASE ONE, Encoding
- [19:01:32] Processing: VID_00008 (5 of 14)
- [19:02:01] Multiplexing M2TS
- [19:03:17] Processing: VID_00020 (6 of 14)
- [19:03:17] Extracting A/V streams [VID_00020]
- [19:03:21] Reencoding video [VID_00020]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 240 frames
- Bitrate: 1.489 Kbs
- [19:03:21] Reencoding: VID_00020, Pass 1 of 1
- [19:03:35] Video Encode complete
- [19:03:36] Processing audio tracks
- [19:03:36] Multiplexing M2TS
- [19:03:39] Processing: VID_00021 (7 of 14)
- [19:03:39] Extracting A/V streams [VID_00021]
- [19:03:42] Reencoding video [VID_00021]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 167 frames
- Bitrate: 1.244 Kbs
- [19:03:43] Reencoding: VID_00021, Pass 1 of 1
- [19:03:53] Video Encode complete
- [19:03:53] Processing audio tracks
- [19:03:53] Multiplexing M2TS
- [19:03:56] Processing: VID_00022 (8 of 14)
- [19:03:56] Extracting A/V streams [VID_00022]
- [19:04:00] Reencoding video [VID_00022]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 168 frames
- Bitrate: 1.339 Kbs
- [19:04:00] Reencoding: VID_00022, Pass 1 of 1
- [19:04:10] Video Encode complete
- [19:04:10] Processing audio tracks
- [19:04:10] Multiplexing M2TS
- [19:04:13] Processing: VID_00025 (9 of 14)
- [19:04:13] Extracting A/V streams [VID_00025]
- [19:04:17] Reencoding video [VID_00025]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 120 frames
- Bitrate: 791 Kbs
- [19:04:17] Reencoding: VID_00025, Pass 1 of 1
- [19:04:25] Video Encode complete
- [19:04:25] Processing audio tracks
- [19:04:25] Multiplexing M2TS
- [19:04:30] Processing: VID_00026 (10 of 14)
- [19:04:30] Extracting A/V streams [VID_00026]
- [19:04:33] Reencoding video [VID_00026]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 192 frames
- Bitrate: 2.790 Kbs
- [19:04:33] Reencoding: VID_00026, Pass 1 of 1
- [19:04:45] Video Encode complete
- [19:04:45] Processing audio tracks
- [19:04:45] Multiplexing M2TS
- [19:04:48] Processing: VID_00027 (11 of 14)
- [19:04:48] Extracting A/V streams [VID_00027]
- [19:04:52] Reencoding video [VID_00027]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 192 frames
- Bitrate: 1.400 Kbs
- [19:04:52] Reencoding: VID_00027, Pass 1 of 1
- [19:05:03] Video Encode complete
- [19:05:03] Processing audio tracks
- [19:05:03] Multiplexing M2TS
- [19:05:07] Processing: VID_00028 (12 of 14)
- [19:05:07] Extracting A/V streams [VID_00028]
- [19:05:10] Reencoding video [VID_00028]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 120 frames
- Bitrate: 500 Kbs
- [19:05:10] Reencoding: VID_00028, Pass 1 of 1
- [19:05:18] Video Encode complete
- [19:05:18] Processing audio tracks
- [19:05:18] Multiplexing M2TS
- [19:05:21] Processing: VID_00029 (13 of 14)
- [19:05:21] Extracting A/V streams [VID_00029]
- [19:05:26] Reencoding video [VID_00029]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 480 frames
- Bitrate: 29.360 Kbs
- [19:05:26] Reencoding: VID_00029, Pass 1 of 1
- [19:06:12] Video Encode complete
- [19:06:12] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:06:12] Multiplexing M2TS
- [19:06:16] Processing: VID_00031 (14 of 14)
- [19:06:16] Extracting A/V streams [VID_00031]
- [19:06:20] Reencoding video [VID_00031]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 168 frames
- Bitrate: 16.925 Kbs
- [19:06:20] Reencoding: VID_00031, Pass 1 of 1
- [19:06:32] Video Encode complete
- [19:06:32] Processing audio tracks
- [19:06:32] Multiplexing M2TS
[19:06:35]PHASE ONE complete
[19:06:35]PHASE TWO - Rebuild Started
- [19:06:35] Rebuilding BD file Structure
[19:06:44] - Encode and Rebuild complete
[19:06:44] Writing BD structure to ISO file
- ImgBurn completed successfully
- COLD_PURSUIT folder removed.
- WORKFILES folder removed.
[19:07:36] JOB: COLD_PURSUIT finished.

[jdobbs]

Nothing has changed with the new version. My Sony X800M2 plays DV Rebuilds only in HDR , when DV is off. When I turn DV on the Sony on, the main film is black.

DV remuxes of the main film with the last tsmuxer plays my Sony without problems. BD-Rebuilder is using the last TSMUXER... (current as of yesterday), so that isn't the problem. Too bad you deleted the work folder, I'd like to see a couple of the files to see what is up. Can you post your settings so I can look at those?

[Michi]

My bdrebuilder.ini:

[Options]
VERSION=0.61.0.3
MODE=0
ENCODER_MENU=1
ENCODE_QUALITY=5
ONEPASS_ENCODING=2
AUTO_QUALITY=0
AUDIO_TO_KEEP=deu;gem;ger;
SUBS_TO_KEEP=deu;gem;ger;gmh;goh;gsw;
SD_CONVERT=0
OPEN_GOP=1
RESIZE_1080=0
DEINTERLACE=0
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=0
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=0
REMOVE_WORKFILES=1
MOVIE_ONLY_LOOP=1
REMOVE_OUTPUT=1
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=1
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
UNMASK_CHAPTER=0
COMPLETION_BEEP=0
DGDECNV=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=66000
TARGET_SIZE=47366
AUTO_BURN=2
MOVIEONLY_TYPE=40
ALTCRF=18
ARCHIVE_265=1
ARCHIVE_AUDIO=100
ARCHIVE_CRF=16
ARCHIVE_ENABLE=1
ARCHIVE_LIMIT=1
ALT_TARGET=7800
ALTMETHOD=0
ALTAUTOCROP=0
QUICK_EXTRAS=0
OUTPUT_3D=0
RESIZE_1440=0
RESIZE_720=0
NEROAAC=0
SUPTITLE=0
IGNORE_3D=0
OUTPUT_SBS=0
ENCODER_MENU=1
HC_PROFILE=BEST
IMPORT_HEVC_INTACT=1
MIN_M2TS_SIZE=20
NEW_CRF_PREDICTION=1
MULTIPROCESS=0
THREADS=auto
BD5_SIZE=4520
BD9_SIZE=8200
BD25_SIZE=23200
QUALITY_ULTRA=1





FRIMSOURCE=0
ENCODER=0
DGDECIM=1
FRIM_SW_DECODE=1
FRIM_SW_ENCODE=1
PRIORITY_CLASS=1
MENU_BACKGROUND=C:\BD_Rebuilder\misc\menuback.jpg
IMPORT_THRESHOLD=15
QUICK_PLAY_THRESHOLD=10
MENU_AUTO_BACKGROUND=1
MENU_PLAY_SEQUENTIAL=0
MENU_START_WITH_MENU=1
DECODER=0
AUDIO_DRC=0
MENU_AUTO_DVDAUDIO=1
IMPORT_LIMIT_LANG=0
IMPORT_KEEP_PLAYALL=0
ALT_CRF_TARGET=4000
PGSTOSRT=0
UHD_MAXRATE=60000
UHD_VBV_BUFFER=60000
TWEAK_X265=--no-open-gop --no-sao --no-slow-firstpass --no-rskip --subme 4 --weightb

[Paths]
SOURCE_PATH=Y:\
WORKING_PATH=Q:\4K\

[thekiller]

hello, i regularly meet with bdrebuilder problems with the automatically crop black bolders, on harry potter 5 instead of having 1920x800, i have 1516x796, how to fix the good value?
thank you

[jdobbs]

hello, i regularly meet with bdrebuilder problems with the automatically crop black bolders, on harry potter 5 instead of having 1920x800, i have 1516x796, how to fix the good value?
thank youBD-RB should correct it on it's own when it reencodes.

[LowDead]

@jdobbs: Have you recently tried importing mkv's?

I just encountered an error just after the "Scanning for Variable Framerate" step. Something about missing number or filename. I went back to 0.60.29 and it worked again. I'll get you a log ASAP :)

//LD

EDIT:

Well There wasn't much in the log...

----------------------
[01:49:08] Importing MKV: PURE_(2019)_S01E01_-_EPISODE_1
- Preparing MKV for processing...


From the TEMPIMPORT folder:

General
Unique ID : 183007012736287462016813617846879401966 (0x89ADDE5BA9BE000BA56959A4B42A37EE)
Complete name : W:\WORK\TEMPIMPORT\Pure (2019) S01E01 - Episode 1.MKV
Format : Matroska
Format version : Version 2
File size : 2.06 GiB
Duration : 33 min 16 s
Overall bit rate : 8 846 kb/s
Encoded date : UTC 2020-01-13 00:49:08
Writing application : mkvmerge v9.7.1 ('Pandemonium') 32bit
Writing library : libebml v1.3.4 + libmatroska v1.4.5

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L4
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 33 min 16 s
Bit rate : 8 458 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 50.000 FPS
Original frame rate : 25.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan type, store method : Separated fields
Scan order : Top Field First
Bits/(Pixel*Frame) : 0.082
Stream size : 1.97 GiB (96%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 2
Format : AC-3
Format/Info : Audio Coding 3
Codec ID : A_AC3
Duration : 33 min 16 s
Bit rate mode : Constant
Bit rate : 384 kb/s
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 91.4 MiB (4%)
Language : English
Service kind : Complete Main
Default : Yes
Forced : No




LASTCMD only had some command from old encode.

INI:

[Options]
VERSION=0.61.0.3
ENCODER=0
MODE=0
ENCODE_QUALITY=3
ONEPASS_ENCODING=0
AUTO_QUALITY=0
AUDIO_TO_KEEP=deu;eng;ger;swe;
SUBS_TO_KEEP=all
SD_CONVERT=0
OPEN_GOP=1
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=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=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=8250
AUTO_BIAS=3
B_PYRAMID=1
DGDECIM_SW_DECODE=0
ENCODER_MENU=1
FRIM_SW_DECODE=0
FRIM_SW_ENCODE=0
HC_PROFILE=BEST
IMPORT_HEVC_INTACT=1
KEEP_MBTREE=1
PASS_TWO_STATS_UPDATE=1
SHOW_ENCODER=1
DTSX_ENABLE=1
ENABLE_TEST=1
ENABLE_BLANKING=1
DEFAULT_LANG=eng
TARGET_SIZE=8250
MIN_M2TS_SIZE=1

SYS:

[01-13-20] Checking System Settings
- BD-Rebuilder v0.61.03
- Windows Version: 6.2 [9200]
- Working Path Free Space: 64,45GB
- AVISYNTH Version: 2.6.0.5, Ok
- LAVFILTERS: Ok
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[01-13-20] Systems Settings Check complete


//LD

[thekiller]

BD-RB should correct it on it's own when it reencodes.


Hello, thank you for your reply, I went to see the extracted x264 file, it has the right resolution, so there is a problem with the re-encoding because the output file is incorrect ??

Thank

[jdobbs]

Hello, thank you for your reply, I went to see the extracted x264 file, it has the right resolution, so there is a problem with the re-encoding because the output file is incorrect ??

ThankPlease post the contents of AVS file from the working folder and the PINFO.INF file from the PSEUDO folder (in the imported folder). That way I can see how BD-RB attempted to correct the sizing of the file.

[jdobbs]

@LowDead

Yes, I import all the time. But, obviously, there is something wrong with the variable framerate scan (it doesn't get hit that often). I'll look at it and see what I find.

I'll look at what changes I made between v0.60.29 and v0.61.03 to see where I screwed the pooch.

Can you look and see if there is a files called "timecodes.txt" in the working folder?

[zamengo]

BD-Rebuilder is using the last TSMUXER... (current as of yesterday), so that isn't the problem. Too bad you deleted the work folder, I'd like to see a couple of the files to see what is up. Can you post your settings so I can look at those?


I think tsmuxer from justdan96 don't work with DV.

Jcdr428 tell about DV and her tsmuxer, he talk something like "DV only work in my tsmuxer".

I cant't find the post, but I remember this...

https://github.com/jcdr428/tsMuxer

I think this don't have in tsmuxer from justdan:
https://github.com/jcdr428/tsMuxer/pull/23

[jdobbs]

I think tsmuxer from justdan96 don't work with DV.

Jcdr428 tell about DV and her tsmuxer, he talk something like "DV only work in my tsmuxer".

I cant't find the post, but I remember this...

https://github.com/jcdr428/tsMuxer

I think this don't have in tsmuxer from justdan:
https://github.com/jcdr428/tsMuxer/pull/23I was under the impression that all jcdr428's changes has been integrated into the master. I'll ask the question and see if that's the case.

@Michi

Try replacing the TSMUXER4K.EXE file located in the tools folder of v0.61.03 with this version (https://jammernhilftnichts.de/jdobbs/tsmuxer4k.exe) and see if it has an impact on the result. You may also want to try turning off the switch to automatically delete the working folder. That way all you'd have to do is rebuild rather than run the entire process to test this.

[thekiller]

#Created by BD Rebuilder - v0.61.01
DirectshowSource("V:\Video\HP5_PHOENIX\HP5_PHOENIX.Title0.mkv", framecount=198866, ConvertFPS=true, audio=false)
LoadPlugin("C:\Users\Sebastien\Desktop\Videos\BD_Rebuilder\tools\autocrop.dll")
Autocrop(mode=0, hMultOf=4)
ConvertToYV12().AssumeFPS(24000,1001)
SelectRangeEvery(4800,48,4000)

[jdobbs]

#Created by BD Rebuilder - v0.61.01
DirectshowSource("V:\Video\HP5_PHOENIX\HP5_PHOENIX.Title0.mkv", framecount=198866, ConvertFPS=true, audio=false)
LoadPlugin("C:\Users\Sebastien\Desktop\Videos\BD_Rebuilder\tools\autocrop.dll")
Autocrop(mode=0, hMultOf=4)
ConvertToYV12().AssumeFPS(24000,1001)
SelectRangeEvery(4800,48,4000)Sorry. That's the wrong AVS file. That's the AVS used for CRF prediction. I need the one that is titled something similar to "VID_00000.AVS".

[mask0rz]

Hi there,

Is there a possibility of re-encoding a UHD MKV to Blu-ray disc (by example a BD-25 disc) and keeping the HD audio intact. For now i only see the option to import MKV file and then it reencodes the audio to 640 bits.

Kind Regards,

Mask0rz

[Michi]

Yesterday I made several test with this 64bit version of tsmuxer:

https://bintray.com/justdan96/tsMuxer/tsMuxerGUI-Nightly/2020-01-11--01-10-45#files

I remuxed all m2ts-files from BD-Rebuilder manually with this version and 2 DV discs are playing fine on my Sony X800M2, but when I replaced the tsmuxer4k.exe with above version in BD-Rebuilder, DV isn't working.

Today I want testing jdobbs new tsmuxer version.

[thekiller]

Sorry. That's the wrong AVS file. That's the AVS used for CRF prediction. I need the one that is titled something similar to "VID_00000.AVS".


I just did a test directly with the disk directly, same problem, is this file you want?


#Created by BD Rebuilder - v0.61.01
DirectshowSource("G:\BDMV\STREAM\00000.m2ts", fps=23.976, framecount=198868, audio=false)
LoadPlugin("C:\Users\Sebastien\Desktop\Videos\BD_Rebuilder\tools\autocrop.dll")
Autocrop(mode=0, hMultOf=4)
ConvertToYV12().AssumeFPS(24000,1001)

[Michi]

DV isn't working with Jdobbs last tsmuxer.exe version. I have a backup of the workfiles folder.

Manually remuxing of the m2ts-files are working on following DV-discs:

Cold Pursuit
Gladiator
The secret life of pets 2
Mary queen of Scotland

Actually I only tested these DV-discs.

[LowDead]

@LowDead

Yes, I import all the time. But, obviously, there is something wrong with the variable framerate scan (it doesn't get hit that often). I'll look at it and see what I find.

I'll look at what changes I made between v0.60.29 and v0.61.03 to see where I screwed the pooch.

Can you look and see if there is a files called "timecodes.txt" in the working folder?

Yes, here it is..

//LD

[jdobbs]

DV isn't working with Jdobbs last tsmuxer.exe version. I have a backup of the workfiles folder.

Manually remuxing of the m2ts-files are working on following DV-discs:

Cold Pursuit
Gladiator
The secret life of pets 2
Mary queen of Scotland

Actually I only tested these DV-discs.I'm confused. Are you talking about remuxing the original files, or remuxing the reencoded files?

[jdobbs]

Yes, here it is..

//LDThanks. That narrows it down a little as to where the error could have occurred.

[jdobbs]

Yesterday I made several test with this 64bit version of tsmuxer:

https://bintray.com/justdan96/tsMuxer/tsMuxerGUI-Nightly/2020-01-11--01-10-45#files

I remuxed all m2ts-files from BD-Rebuilder manually with this version and 2 DV discs are playing fine on my Sony X800M2, but when I replaced the tsmuxer4k.exe with above version in BD-Rebuilder, DV isn't working.

Today I want testing jdobbs new tsmuxer version. Still a little confused. So... if I understand correctly, the reencoded files that BD-RB created work fine when you remux it manually, but not when BD-RB performs the remux?

Did you try using the the version I linked in the post (https://forum.doom9.org/showthread.php?p=1895664#post1895664) above?

Can you post the META file that is used by BD-RB and the one used when you do it manually so I can see the difference? If you are using the GUI, just cut and paste from the area in the GUI.

I hope I'm understanding you correctly?

[LowDead]

Thanks. That narrows it down a little as to where the error could have occurred.

Also found this in EXTRACT.META:

MUXOPT --no-pcr-on-video-pid --new-audio-pes --demux --vbr --vbv-len=500
- Scanning for Variable Frame Rate...

[jdobbs]

Also found this in EXTRACT.META:

MUXOPT --no-pcr-on-video-pid --new-audio-pes --demux --vbr --vbv-len=500
- Scanning for Variable Frame Rate...
Hmmm... that's not good. Actually that file never gets used except when I set a test flag... but the fact that the text " - Scanning for Variable Frame Rate..." is being written to it makes be wonder how that could even happen.

This may help me put a finger on the problem. Thanks.

[jdobbs]

Hello,

I have a Panasonic DPUB450 player & use imgburn

the movie I tested was gemini man movie only for both tests below

in 60.01 I got the same results as michi the film played ok as hdr10 but when I switch on dolby vision the film was black

in 60.03 the film plays ok with dolby vision turned on but if I turn dolby vision off the film plays in hdr10 as black & white, I also did a second rebuild replacing the tsmuxer4k with the one jdobbs posted earlier with the same results

I hope this helps Thanks. I'll look at it and see if I can see something that might help put a finger on the issue. Weird, though, that it plays as Dolby Vision but not HDR10. My player doesn't support Dolby Vision, but whenever I reencode a DV source it always plays back fine as HDR10. Really odd that it seems to act in the opposite on your player.

[spexman]

Now that TSMuxer has been updated, is it correct to conclude that TSMuxer has now become what TSM2UHD set out to achieve?

[jdobbs]

Now that TSMuxer has been updated, is it correct to conclude that TSMuxer has now become what TSM2UHD set out to achieve?Yes. TSM2UHD is no longer needed.

[spexman]

Much appreciated jdobbs!

[jdobbs]

Also found this in EXTRACT.META:

MUXOPT --no-pcr-on-video-pid --new-audio-pes --demux --vbr --vbv-len=500
- Scanning for Variable Frame Rate...
Hmmm... that's not good. Actually that file never gets used except when I set a test flag... but the fact that the text " - Scanning for Variable Frame Rate..." is being written to it makes be wonder how that could even happen.

This may help me put a finger on the problem. Thanks.I found what was causing this. It was a stupid mistake on my part. I've fixed it for the next release.

[LowDead]

I found what was causing this. It was a stupid mistake on my part. I've fixed it for the next release.

Great, thanks!

//LD

[Michi]

Still a little confused. So... if I understand correctly, the reencoded files that BD-RB created work fine when you remux it manually, but not when BD-RB performs the remux?

Yes, this is correct. I manually remuxed the reencoded files by BD-RB an overwrite it.

you try using the the version I linked in the post (https://forum.doom9.org/showthread.php?p=1895664#post1895664) above?

Yes , I used this version yesterday and it's the same.

you post the META file that is used by BD-RB and the one used when you do it manually so I can see the difference? If you are using the GUI, just cut and paste from the area in the GUI.

META file of the main movie by BD-RB:

MUXOPT --no-pcr-on-video-pid --new-audio-pes --blu-ray-v3 --vbr --auto-chapters=5 --vbv-len=500 --start-time=27000000
V_MPEGH/ISO/HEVC, "Q:\4K\WORKFILES\VID_00008.AVS.hevc", fps=24, insertSEI, contSPS
V_MPEGH/ISO/HEVC, "Q:\4K\WORKFILES\00008.track_4117.hevc", fps=24, secondary, contSPS
A_AC3, "Q:\4K\WORKFILES\00008.track_4356.AC3", lang=deu
S_HDMV/PGS, "Q:\4K\WORKFILES\00008.track_4771.sup",lang=deu


META file by manually remuxing with tsmuxergui:

MUXOPT --no-pcr-on-video-pid --new-audio-pes --vbr --vbv-len=500
V_MPEGH/ISO/HEVC, "Q:\4K\COLD_PURSUIT\BDMV\STREAM\00008.m2ts", track=6912
V_MPEGH/ISO/HEVC, "Q:\4K\COLD_PURSUIT\BDMV\STREAM\00008.m2ts", fps=24, ar=As source, track=4113
A_AC3, "Q:\4K\COLD_PURSUIT\BDMV\STREAM\00008.m2ts", track=4352, lang=deu
S_HDMV/PGS, "Q:\4K\COLD_PURSUIT\BDMV\STREAM\00008.m2ts", fps=24, track=4608, lang=deu

https://forum.doom9.org/attachment.php?attachmentid=17147&stc=1&d=1579014500

[jdobbs]

Yes, this is correct. I manually remuxed the reencoded files by BD-RB an overwrite it.Looking at the what you posted, it doesn't look like you used the files reencoded by BD-RB when you did it manually?

In BD-RB you used "Q:\4K\WORKFILES\VID_00008.AVS.hevc"

In the manual remux you used "Q:\4K\COLD_PURSUIT\BDMV\STREAM\00008.m2ts"

Am I missing something?

[Michi]

In the manual remux you used "Q:\4K\COLD_PURSUIT\BDMV\STREAM\00008.m2ts"


This is the m2ts-file created by BD-RB.

[thekiller]

I just did a test directly with the disk directly, same problem, is this file you want?


#Created by BD Rebuilder - v0.61.01
DirectshowSource("G:\BDMV\STREAM\00000.m2ts", fps=23.976, framecount=198868, audio=false)
LoadPlugin("C:\Users\Sebastien\Desktop\Videos\BD_Rebuilder\tools\autocrop.dll")
Autocrop(mode=0, hMultOf=4)
ConvertToYV12().AssumeFPS(24000,1001)

you have forgotten me??

[jdobbs]

This is the m2ts-file created by BD-RB.Ok. I see.

So you read it from the file BD-RB created and is sees "track=6912"? That's interesting -- and probably the source of the issue!

Thanks!

[jdobbs]

you have forgotten me??From the first post of this thread:Don't push bug resolution or keep asking for a fix. I will get to the reported bugs, but only when I can find the time.It has nothing to do with "forgotten" -- but with priorities. Right now I've prioritized "getting Dolby Vision working" as the thing I need to complete next.

It appears that AUTOCROP is having issues finding the borders on your source. Since AUTOCROP is an external filter (developed by someone else) there's not a lot I can do about it. I'd suggest you just just set autocropping off in the ALTERNATE output dialog.

Alternatively you could read info about autocrop at this link (http://avisynth.nl/index.php/AutoCrop) and possibly add it as a filter (using the SETUP dialog). That way you could experiment with some of its settings (like maybe the "threshold" or "sample" parameters) when you find sources that resize oddly. Remember, though, to disable the filter when you are trying to output to something other than ALTERNATE

[jdobbs]

I have updated the first post of this thread with a link to the most recent version of BD-RB (v0.61.04). Changes for this release:- Corrected an error in which IMPORT_PAL_TO_FILM
was not working for UHD sources.
- Fixed "Error 52" and failure when attempting
to import a source that needed to be scanned
for variable frame rate. Introduced in the
v0.61.xx series.
- Fixed an error in which the wrong PID was
being assigned to Dolby Vision substreams
on full backups, causing it to not playback
correctly on machines supporting it when
enabled.
- Other minor corrections and cosmetic fixes.

@michi -- Let me know if this fixes your Dolby Vision issues.

[thekiller]

From the first post of this thread:Don't push bug resolution or keep asking for a fix. I will get to the reported bugs, but only when I can find the time.It has nothing to do with "forgotten" -- but with priorities. Right now I've prioritized "getting Dolby Vision working" as the thing I need to complete next.

It appears that AUTOCROP is having issues finding the borders on your source. Since AUTOCROP is an external filter (developed by someone else) there's not a lot I can do about it. I'd suggest you just just set autocropping off in the ALTERNATE output dialog.

Alternatively you could read info about autocrop at this link (http://avisynth.nl/index.php/AutoCrop) and possibly add it as a filter (using the SETUP dialog). That way you could experiment with some of its settings (like maybe the "threshold" or "sample" parameters) when you find sources that resize oddly. Remember, though, to disable the filter when you are trying to output to something other than ALTERNATE

ok I understand, for the moment I am doing this to force the correct resolution:

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.

it happens on old movies, if recent movies I don't have the problem

thank

[Michi]

This version is a major release! DV works great on my Sony X800M2.

Great job jdobbs!

[jdobbs]

This version is a major release! DV works great on my Sony X800M2.

Great job jdobbs!Good news. Thanks for helping me put my finger on where the problem was.

[zamengo]

Good news. Thanks for helping me put my finger on where the problem was.

Jcdr428 tsmuxer help with this or you still using justdan version ?

[MrVideo]

- Corrected an error in which IMPORT_PAL_TO_FILM
was not working for UHD sources.
Huh? PAL sources are 625 analog converted to 576i (which is technically no longer PAL). There is no such thing as PAL 4K sources. So, I am confused.

[FilipeAmadeuO]

@jdobbs
Can you please add the possibility to replace the subtitles/audio and change language of subtitles/audio diretly on BDRebuilder GUI ?
Something like right click on subtitle/audio and select file to use for replace…
That would be a nice improvement...
@jdobbs
Before you finish this improvement is there any option on bdrebuilder.ini file that stops processing after all m2ts demux so i can replace subtitles manually and then continue with the remux ?

Also another question. Why is Dolby Vision HEVC file extracted on a 2nd run ? Why can´t it be extracted together with the other video/audio files ?
TsMuxer limitation ?

[jdobbs]

Jcdr428 tsmuxer help with this or you still using justdan version ?Still using the justdan version. (same as last release).

[jdobbs]

@jdobbs
Before you finish this improvement is there any option on bdrebuilder.ini file that stops processing after all m2ts demux so i can replace subtitles manually and then continue with the remux ?

Also another question. Why is Dolby Vision HEVC file extracted on a 2nd run ? Why can´t it be extracted together with the other video/audio files ?
TsMuxer limitation ?BD-RB works with one CLPI/M2TS at a time when doing full backups, so you'd have to stop/replace subtitles one at a time. That could get to be a real challenge on multi-part sources.

Normally the Dolby HEVC file isn't extracted individually. The only time BD-RB extracts streams individually is if it encounters an error when trying to extract all tracks at once.

[FilipeAmadeuO]

BD-RB works with one CLPI/M2TS at a time when doing full backups, so you'd have to stop/replace subtitles one at a time. That could get to be a real challenge on multi-part sources.

I know that :)
Any chance to demux all m2ts at once -> stop -> i replace subtitles manually -> remux all m2ts ?
Or even better implement subtitle/dudio replacement directly on GUI :)

Normally the Dolby HEVC file isn't extracted individually. The only time BD-RB extracts streams individually is if it encounters an error when trying to extract all tracks at once.
Any way to check extraction errors ? On the log there is no error reported

[Michi]

Hello,

test with 61.04, gemini man full backup this time

dolby vision seems to be working fine but hdr10 (when dolby vision is turned off) plays in black & white but when I switch to sdr it plays in colour

just for testing purposes to eliminate any player problem I did a full backup with dvdfab from the same rip & dolby vision, hdr10 & sdr all play ok



HDR10 or HDR10+?

My Sony X800M2 have no problem with HDR10 on UHD-discs made by BD-RB. The Sony can't play HDR10+.

Which player can play HDR10+ discs?

[FilipeAmadeuO]

which player can play hdr10+ discs?
oppo udp-203

[SeeMoreDigital]

Which player can play HDR10+ discs?
A good place to start would be to find which player manufacturer is a member of the HDR10+ ('https://hdr10plus.org/') alliance.

Suffice to say... You'll also need a TV that supports HDR10+ too!


Cheers

[jdobbs]

Hello,

test with 61.04, gemini man full backup this time

dolby vision seems to be working fine but hdr10 (when dolby vision is turned off) plays in black & white but when I switch to sdr it plays in colour

just for testing purposes to eliminate any player problem I did a full backup with dvdfab from the same rip & dolby vision, hdr10 & sdr all play ok

maybe a flag in the hdr10 metadata is not being set ?

ThanksHDR10 is playing fine on my unit. My player doesn't support Dolby Vision -- so SDR and HDR10 are all I can test, and both work fine when I encode a Dolby Vision disc.

[TobiMan]

Probably dumb question... If I donate a Amazon Gift Card in EUR currency, can it be used by jdobbs?

[LowDead]

Now the variable scan works, but another problem occurs with my testfile. After encode and finished job the runtime of the episode is approx half of what it should be. The other episodes doesn't experience this and one thing I can see is that the problem episode is 50fps and the others (working ones) is 25fps.

When I watch the encoded episode in mpc-be it reports correct length but video stops halfway in and audio continues.

When I watch the build bluray in PowerDVD 18 it reports half length and stops altogether at the point.

The pseudo build plays at 2x speed and have half length in PowerDVD 18 while the pseudo file plays at 2x speed and full lenght in mpc-be.

Can one think that the problem comes when BD-RB builds the pseudo disc?
Attached files is the two different clpi and mpls that differ from pseudo and final build and also the DGI file, if that helps in any way.

Interesting to see that DGIndexNV 2053.0.0.119 X32 sees this:

FPS 80000 / 1600

//LD

System check:
[01-16-20] Checking System Settings
- BD-Rebuilder v0.61.04
- Windows Version: 6.2 [9200]
- Working Path Free Space: 68,05GB
- AVISYNTH Version: 2.6.0.5, Ok
- LAVFILTERS: Ok
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[01-16-20] Systems Settings Check complete


Log:
----------------------
[13:54:12] Importing MKV: PURE_(2019)_S01E01_-_EPISODE_1
- Preparing MKV for processing...
- Scanning for Variable Frame Rate...
- Collecting audio/video streams from source...
- Building pseudo-BD source structure...
[13:58:13] Video import completed successfully.
----------------------
[01-16-20] BD Rebuilder v0.61.04
[14:06:14] Source: PURE_(2019)_S01E01_-_EPISODE_1
- Input BD size: 2,18 GB
- Approximate total content: [00:16:38.440]
- Target BD size: 8,25 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[14:06:14] PHASE ONE, Encoding
- [14:06:14] Processing: VID_00000 (1 of 1)
- [14:06:14] Extracting A/V streams [VID_00000]
- [14:06:58] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 50,000fps, 49 922 frames
- Bitrate: 15 000 Kbs
- [14:06:58] Reencoding: VID_00000, Pass 1 of 2
- [14:14:23] Reencoding: VID_00000, Pass 2 of 2
- [14:44:13] Video Encode complete
- [14:44:13] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [14:44:13] Multiplexing M2TS
[14:44:41]PHASE ONE complete
[14:44:41]PHASE TWO - Rebuild Started
- [14:44:41] Rebuilding BD file Structure
[14:44:41] - Encode and Rebuild complete
[14:44:42] JOB: PURE_(2019)_S01E01_-_EPISODE_1 finished.

INF:
[Status]
LABEL=PURE_(2019)_S01E01_-_EPISODE_1
VERSION=v0.61.04
SOURCE_SIZE=2338942220
SOURCE_VIDEO_SIZE=2338922496
TARGET_SIZE=8860467200
REDUCTION=3.78826040245157
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=deu;eng;ger;swe;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=all
BACKUP_MODE=0
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=-1
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
HEVC_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=1
[00000]
AUDIO=1
PGS=1
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=8860447476
RATE=15000
SPLITS=1
NSTART=27000000
NEND=71929800
NSIZE=2061348864
FLINK=0
MLINK=0


META:
MUXOPT --no-pcr-on-video-pid --new-audio-pes --blu-ray --vbr --auto-chapters=5 --vbv-len=500 --start-time=27000000
V_MPEG4/ISO/AVC, "W:\WORK\WORKFILES\VID_00000.AVS.264", fps=50, insertSEI, contSPS
A_AC3, "W:\WORK\WORKFILES\00000.track_4352.AC3", lang=eng
S_HDMV/PGS, "W:\WORK\WORKFILES\00000.track_4608.sup",lang=eng

[LowDead]

Probably dumb question... If I donate a Amazon Gift Card in EUR currency, can it be used by jdobbs?

Yes, that would be no problem at all..

//LD

[SeeMoreDigital]

@michi

Im talking about standard hdr10

my player (Panasonic DPUB450) & tv (Panasonic TX50GX800B) both supports hdr10+ & dolby vision but I havnt tested any hdr10+ discs yet, besides I don't think you don't get any notification of hdr10+ like the nice big dolby vision logo that pops up on the tv

is hdr10+ an extra stream like dolby vision or does it replace the standard hdr10 in the video file ?

I have a few hdr10+ discs if you want me to test

ThanksI'm confused... Given that you have some HDR10+ discs, why haven't you tested any yet?

[Emulgator]

Interesting to see that DGIndexNV 2053.0.0.119 X32 sees this:
FPS 80000 / 1600
LowDead, is your source 50p?
You cannot have 1980x1080x50p on a blu-ray.
If 50p, then 1280x720 only.

[FilipeAmadeuO]

Can anyone try last BdRebuilder version with FF or RW 2x ou more to see if image shutters ?
In my case it shutters at least on Dolby Vision titles.

[Michi]

Muxing error on Angel_Heart:

[01.16.20] BD Rebuilder v0.61.04
[17:19:11] Source: ANGEL_HEART
- Input BD size: 82,08 GB
- Approximate total content: [03:52:38.137]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Fastest, BD-25+), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[17:19:12] PHASE ONE, Encoding
- [17:19:12] Processing: VID_00002 (3 of 15)
- [17:19:14] Reencoding video [VID_00002]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 163.002 frames
- Bitrate: 35.000 Kbs
- [17:19:14] Reencoding: VID_00002, Pass 1 of 1
- [21:38:06] Video Encode complete
- [21:38:06] Processing audio tracks
- Track 4354 (deu): Keeping original audio
- [21:38:06] Multiplexing M2TS
- Bitstream exception. Adjusting...
- Error in attempt to multiplex: MUX_00002.meta
- Bitstream exception std::exception. It does not have to be! Please contact application support team for more information.
[21:40:39] - Failed to build structure, aborted

[LowDead]

LowDead, is your source 50p?
You cannot have 1980x1080x50p on a blu-ray.
If 50p, then 1280x720 only.

It looks like the source is 25i and I'm aiming for a 8.5GB(6 episodes in total) AVCHD disc.

//LD

ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L4
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 33 min 16 s
Bit rate : 8 286 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 25.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan type, store method : Separated fields
Scan order : Top Field First
Bits/(Pixel*Frame) : 0.160
Stream size : 1.93 GiB (94%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

[zamengo]

I know that :)
Any chance to demux all m2ts at once -> stop -> i replace subtitles manually -> remux all m2ts ?
Or even better implement subtitle/dudio replacement directly on GUI :)


Any way to check extraction errors ? On the log there is no error reported

Why you don't use tsmuxer gui?

[LowDead]

Adding to this.. Thought of changing frameserver and this happens...

Anyway, result is the same.

//LD

[Emulgator]

Wrong signalling in .mkv container ?
A sample would tell more, I am guessing blindly here.

[jdobbs]

It looks like the source is 25i and I'm aiming for a 8.5GB(6 episodes in total) AVCHD disc.

//LD

ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L4
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 33 min 16 s
Bit rate : 8 286 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 25.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan type, store method : Separated fields
Scan order : Top Field First
Bits/(Pixel*Frame) : 0.160
Stream size : 1.93 GiB (94%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
I'm confused. The scan for variable bitrate only applies to files that say "Frame rate mode: Variable". Is this a different file? You don't force it by having IMPORT_VFR_SCAN=1 set in your INI, do you?

[LowDead]

I'm confused. The scan for variable bitrate only applies to files that say "Frame rate mode: Variable". Is this a different file? You don't force it by having IMPORT_VFR_SCAN=1 set in your INI, do you?

This is the same file. Used Mediainfo 19.04 (and latest version 19.09) to check it. And I don't have IMPORT_VFR_SCAN at all in my INI.

//LD

[prologic]

Today I did the 4k movie Gemini Man ,
Just rebuilt it, taking some sound and subtitle streams out, without shrinking anything else ..
Report is , DOLBY VISION and (60 FRAME RATE) (DOLBY ATMOS) all worked great ..
This just get`s better , with every new release ..

[TobiMan]

Yes, that would be no problem at all..

//LD

:thanks:

[jdobbs]

This is the same file. Used Mediainfo 19.04 (and latest version 19.09) to check it. And I don't have IMPORT_VFR_SCAN at all in my INI.

//LDDoes it report differently if you use the version of MEDIAINFO that is included in BD-RB's tools folder?

[LowDead]

Does it report differently if you use the version of MEDIAINFO that is included in BD-RB's tools folder?

This is what I get with the included mediainfo (changed filename for ease of use):

General
Unique ID : 0 (0x0)
Complete name : 1.mkv
Format : Matroska
Format version : Version 4 / Version 2
File size : 2.06 GiB
Duration : 33 min 16 s
Overall bit rate : 8 846 kb/s
Encoded date : UTC 2010-02-22 21:41:29
Writing application : no_variable_data
Writing library : no_variable_data

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L4
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 33 min 16 s
Bit rate : 8 286 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 25.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan type, store method : Separated fields
Scan order : Top Field First
Bits/(Pixel*Frame) : 0.160
Stream size : 1.93 GiB (94%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 2
Format : AC-3
Format/Info : Audio Coding 3
Codec ID : A_AC3
Duration : 33 min 16 s
Bit rate mode : Constant
Bit rate : 384 kb/s
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 91.4 MiB (4%)
Language : English
Service kind : Complete Main
Default : Yes
Forced : No

[cartman0208]

Jdobbs: I was wondering ... do you plan on implementing GPU encoding in the future?
I was able to do some testing recently with my new graphics card and the results look awesome.
Additionally the encoding time on a UHD 2hr movie decreased from 30 hours to 40 minutes :eek:

[zamengo]

Jdobbs: I was wondering ... do you plan on implementing GPU encoding in the future?
I was able to do some testing recently with my new graphics card and the results look awesome.
Additionally the encoding time on a UHD 2hr movie decreased from 30 hours to 40 minutes :eek:

Encoding with cuda cores have a issues, the final result is a 2176p file, not 2160p.

[jdobbs]

Jdobbs: I was wondering ... do you plan on implementing GPU encoding in the future?
I was able to do some testing recently with my new graphics card and the results look awesome.
Additionally the encoding time on a UHD 2hr movie decreased from 30 hours to 40 minutes :eek:Encoding with cuda cores have a issues, the final result is a 2176p file, not 2160p.Really? That's disappointing. I was actually thinking about (eventually) buying an NVIDIA card in the Turing family (for B-Frame support) and doing some testing.

Good to know.

[Ch3vr0n]

@jdobbs Thats because it's obsolete. CUDA has been replaced by NVEnc https://avidemux.org/smif/index.php?topic=16389.0, https://steamcommunity.com/app/330070/discussions/0/154644045360096302/, https://en.wikipedia.org/wiki/Nvidia_NVENC

[jdobbs]

@jdobbs Thats because it's obsolete. CUDA has been replaced by NVEnc https://avidemux.org/smif/index.php?topic=16389.0, https://steamcommunity.com/app/330070/discussions/0/154644045360096302/, https://en.wikipedia.org/wiki/Nvidia_NVENCNVENC is what I was taking about... so the issue he mentioned isn't related to NVENC? I guess I didn't understand that CUDA and NVENC were mutually exclusive.

If I understand it correctly, in FFMPEG NVENC and NVDEC are still called CUDA, but, honestly, I have spend a whole lot of time researching it. My (still unresearched) plan was to use FFMPEG for NVENC encoding.

[videoh]

CUDA refers to the GPU multiprocessors (cores) and the infrastructure to utilize them. NVDec (previously called CUVID) and NVEnc are separate engines on the GPU that implement video decoding and encoding, respectively. CUDA is certainly not obsolete. And CUVID was not replaced, merely renamed.

[jdobbs]

CUDA refers to the GPU multiprocessors (cores) and the infrastructure to utilize them. NVDec (previously called CUVID) and NVEnc are separate engines on the GPU that implement video decoding and encoding, respectively. CUDA is certainly not obsolete. And CUVID was not replaced, merely renamed.Thanks for the clarification.

[MrVideo]

Encoding with cuda cores have a issues, the final result is a 2176p file, not 2160p.
References?

[prologic]

References?

I have done around 70% of all 4k uhd releases , using cuda ..
And everyone , still the same
3840 x 2160 pixels..
It takes around 15mins on my geforce gtx 1070 card , to make then fit on a BD50 ..I also use BD Rebuilder , to Alter the build of the disc as well , resulting in resizing a lot less .

[Sharc]

…. My (still unresearched) plan was to use FFMPEG for NVENC encoding.
You may also want to take a look at rigaya's NVEncC. It is continually developed and well documented.
https://github.com/rigaya/NVEnc/releases
https://github.com/rigaya/NVEnc/
https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md

[jdobbs]

You may also want to take a look at rigaya's NVEncC. It is continually developed and well documented.
https://github.com/rigaya/NVEnc/releases
https://github.com/rigaya/NVEnc/
https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.mdThanks! This looks great.

[MrVideo]

I have done around 70% of all 4k uhd releases , using cuda ..
What program?

[zamengo]

References?

https://devtalk.nvidia.com/default/topic/1032118/video-codec-and-optical-flow-sdk/nvenc-hevc-encoding-of-3840x2160-results-in-coded-size-of-3840x2176/

[prologic]

What program?
I use DVDFAB

[zamengo]

I use DVDFAB

Open playlist on tsmuxer, you will figure out 2176p.

This is incompatible with Xbox One S and X player.

[MrVideo]

Based on the reference, it looks like 2176 is it, period. The hardware is only 32x32. Sounds like Xbox needs to get it right. It is the same issue with 1080. It is encoded to 1088 (16x16) and set to display at 1080.

[LowDead]

Yes, tsmuxer reports 2176p, but mediainfo says 2160p... after reading the discussion at nvidia I would trust tsmuxer. BUT it's an old discussion and in the end they say the Turing (for those who don't know: GTX1660, 2060, 2070, 2080 etc...) cards have HW capabilities of 8x8 and 16x16. So off to buy a new gfx card then :)

Anyway, even though an dvdfab encode have 2176p, I believe they have gotten around the problem with green screen on the XB and also works flawlessly for most others. So what I'm saying, not to get too much OT, is that jdobbs can also fix these problems when/if they occur with bdrb.

//LD

[cartman0208]

You may also want to take a look at rigaya's NVEncC. It is continually developed and well documented.
https://github.com/rigaya/NVEnc/releases
https://github.com/rigaya/NVEnc/
https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md

I did my testing with Staxrip, which makes use of NVEncC.

[jdobbs]

I have updated the first post of this thread with a link to the most recent version of BD-RB (v0.61.05). Changes for this release:- Corrected an issue that could result in
blocky or distorted display during FF or
REW on full backups.
- Fixed an issue in which an imported source
(very rarely) might not have its frame rate
detected by MEDIAINFO.
- Added an "*" to the "HEVC" callout of the
stream display for sources that have HDR and
"**" for those that also have Dolby Vision.
- Changed the setting for adjustment/scan of
MKV during import. Should have been off by
default instead of on.
- Updated prediction routines for CRF encodes
to more accurately predict UHD output when
CRF is selected. Still needs testing.
- Updated TSMUXER4K to a more recent nightly
release.
- Other minor corrections and cosmetic fixes.

[FilipeAmadeuO]

@jdobbs
The “Corrected an issue that could result in blocky or distorted display during FF or REW on full backups.”
was a TSmuxer ou BdRebuilder bug ?

Because with this last version the problem is fixed. And now UHD backup is perfect.
But before I had same issue using only Tsmuxer.
Now subtitles/audio in GUI replacement is what I miss :)

[jdobbs]

@jdobbs
The “Corrected an issue that could result in blocky or distorted display during FF or REW on full backups.”
was a TSmuxer ou BdRebuilder bug ?

Because with this last version the problem is fixed. And now UHD backup is perfect.
But before I had same issue using only Tsmuxer.
Now subtitles/audio in GUI replacement is what I miss :)The one mentioned in the log was a BD Rebuilder bug. Not sure if there was another bug fixed in TSMUXER. If so, I wasn't aware of it.

[Michi]

BD-RB encodes 4K import without HDR in HDR. I tested this with a x264 4K mkv file.

Since 61.05 BD-RB uses higher bitrates than 35Mbit on UHD rebuilds. Is this normal?

For me this is a feature and not a bug.

[jdobbs]

BD-RB encodes 4K import without HDR in HDR. I tested this with a x264 4K mkv file.

Since 61.05 BD-RB uses higher bitrates than 35Mbit on UHD rebuilds. Is this normal?

For me this is a feature and not a bug.Yes. I originally left it at the maximum for a standard BD while I was testing it (to be safe). But, after some testing, I've now increased it since a UHD BD-25/50 has a higher maximum bitrate.

Just remember, though, that this is just the maximum bitrate (associated with peaks). The actual bitrate for VBR is typically much lower (unless the source is small enough that it reaches the maximum with the selected target).

[Priapismic]

Done.

[Michi]

The crf encoded files are to big and the second pass crashed:

[01.31.20] BD Rebuilder v0.61.05
[14:14:12] Source: DER_WILDE_PAZIFIK
- Input BD size: 24,30 GB
- Approximate total content: [00:56:24.305]
- Target BD size: 8,01 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), CRF
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[14:14:12] PHASE ONE, Encoding
- [14:14:12] Processing: VID_00002 (1 of 3)
- [14:14:12] Extracting A/V streams [VID_00002]
- [14:14:19] Reencoding video [VID_00002]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 888 frames
- [14:14:19] Performing CRF Prediction...
- Analyzing 20,70 30,95 32,15 31,55 31,25 31,10 31,03 31,06 31,08 31,07 31,07 31,07 31,07 31,07 31,07 31,07 31,07 31,07 31,07 31,07 [31,07]
- [14:17:41] Encoding using constant rate factor.
- [14:20:15] Video Encode complete
- [14:20:15] Processing audio tracks
- Track 4352 (deu): Keeping original audio
- [14:20:15] Multiplexing M2TS
- [14:20:19] Processing: VID_00003 (2 of 3)
- [14:20:19] Extracting A/V streams [VID_00003]
- [14:24:17] Reencoding video [VID_00003]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 75.083 frames
- [14:24:17] Performing CRF Prediction...
- Analyzing 20,70 22,70 21,70 21,20 20,95 20,83 20,76 20,73 20,72 20,72 20,73 20,73 20,73 20,73 20,73 20,73 20,73 20,73 20,73 20,73 20,73 20,73 20,73 20,73 20,73 20,73 20,73 20,73 20,73 [20,73]
- [15:26:16] Encoding using constant rate factor.
- Performing size-correcting second pass...
[20:19:03] - Failed video encode, aborted

[jdobbs]

Wow. I'm really confused as to how it could get caught using the same CRF value that many times during prediction??? I'll look at it.

Can you post your REBUILDER.INI file?

[Michi]

BD-Rebuilder.ini:

[Options]
VERSION=0.61.0.5
MODE=0
ENCODER_MENU=1
ENCODE_QUALITY=5
ONEPASS_ENCODING=2
AUTO_QUALITY=0
AUDIO_TO_KEEP=deu;gem;ger;
SUBS_TO_KEEP=deu;gem;ger;gmh;goh;gsw;
SD_CONVERT=0
OPEN_GOP=1
RESIZE_1080=0
DEINTERLACE=0
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=0
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=0
REMOVE_WORKFILES=1
MOVIE_ONLY_LOOP=1
REMOVE_OUTPUT=1
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=1
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
UNMASK_CHAPTER=0
COMPLETION_BEEP=0
DGDECNV=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=66000
TARGET_SIZE=23200
AUTO_BURN=2
MOVIEONLY_TYPE=40
ALTCRF=18
ARCHIVE_265=1
ARCHIVE_AUDIO=100
ARCHIVE_CRF=16
ARCHIVE_ENABLE=1
ARCHIVE_LIMIT=1
ALT_TARGET=7800
ALTMETHOD=0
ALTAUTOCROP=0
QUICK_EXTRAS=0
OUTPUT_3D=0
RESIZE_1440=0
RESIZE_720=0
NEROAAC=0
SUPTITLE=0
IGNORE_3D=0
OUTPUT_SBS=0
ENCODER_MENU=1
HC_PROFILE=BEST
IMPORT_HEVC_INTACT=1
MIN_M2TS_SIZE=20
NEW_CRF_PREDICTION=1
MULTIPROCESS=0
THREADS=auto
BD5_SIZE=4520
BD9_SIZE=8200
BD25_SIZE=23200
QUALITY_ULTRA=1





FRIMSOURCE=0
ENCODER=0
DGDECIM=1
FRIM_SW_DECODE=1
FRIM_SW_ENCODE=1
PRIORITY_CLASS=1
MENU_BACKGROUND=C:\BD_Rebuilder\misc\menuback.jpg
IMPORT_THRESHOLD=15
QUICK_PLAY_THRESHOLD=10
MENU_AUTO_BACKGROUND=1
MENU_PLAY_SEQUENTIAL=0
MENU_START_WITH_MENU=1
DECODER=0
AUDIO_DRC=0
MENU_AUTO_DVDAUDIO=1
IMPORT_LIMIT_LANG=0
IMPORT_KEEP_PLAYALL=0
ALT_CRF_TARGET=4000
PGSTOSRT=0
UHD_MAXRATE=60000
UHD_VBV_BUFFER=60000
TWEAK_X265=--no-open-gop --no-sao --no-slow-firstpass --no-rskip --subme 4 --weightb --ctu 32

[Paths]
SOURCE_PATH=F:\4K\
WORKING_PATH=Q:\4K\

[jfcarbel]

Updating to latest build and been using NeroAAC in past due to quality, But wondering if this is still case. Is the built in one now just as good if not better?

Also building a new Ryzen 3900X system, is MULTIPROCESS setting even needed anymore as I seem to recall that both x264 and x265 and multi-threaded by default.

[BuddTX]

JDobbs, I would also be interested in a future version of BD Rebuilder with NVEnc/NVEncC or similar nVidia GPU Hardware encoding for 4K/UHD x265 encoding.

I did a test with the evaluation version of CloneBD using x265 and NVEnc and it took about 30 minutes to make a MKV using the highest settings, whereas the same source took over a day using BD 61.05 and x265. this is NOT A COMPLAINT at all, I love BD Rebuilder! I am very appreciative of all you have done!

While I have an older PC (10 years old!), it is still a powerhouse, it is a 6 core Intel Xeon W3680 3.33 Ghz, 12 cores with hyperthreading, 24 gig of triple channel ram, and two SSD hard drives. The video card I have is a NVIDIA GeForce GTX 1050 TI. Still using W7 if that matters.

Thank you!

[jdobbs]

JDobbs, I would also be interested in a future version of BD Rebuilder with NVEnc/NVEncC or similar nVidia GPU Hardware encoding for 4K/UHD x265 encoding.

I did a test with the evaluation version of CloneBD using x265 and NVEnc and it took about 30 minutes to make a MKV using the highest settings, whereas the same source took over a day using BD 61.05 and x265. this is NOT A COMPLAINT at all, I love BD Rebuilder! I am very appreciative of all you have done!

While I have an older PC (10 years old!), it is still a powerhouse, it is a 6 core Intel Xeon W3680 3.33 Ghz, 12 cores with hyperthreading, 24 gig of triple channel ram, and two SSD hard drives. The video card I have is a NVIDIA GeForce GTX 1050 TI. Still using W7 if that matters.

Thank you!In order to build and test it I need to have an Nvidia card that supports it. Right now with donations virtually non-existent I have a hard time justifying the cost to myself. Not trying to jockey for donations, just stating the facts.

[cartman0208]

In order to build and test it I need to have an Nvidia card that supports it. Right now with donations virtually non-existent I have a hard time justifying the cost to myself. Not trying to jockey for donations, just stating the facts.

If you don't mind missing some of the newer features like 8k and B-Frame support and 4k 4:4:4 and lossless support (https://developer.nvidia.com/video-encode-decode-gpu-support-matrix), I could send you my spare GTX960 ...

I just looked up shipping prices to US and its less than I feared :D

[MrVideo]

I think it needs to be a GTX-1050, or better, for HEVC hardware encoding support.

The GTX-1050 has the 2176p issue. AIUI, it needs to be a RTX-20xx to get 2160p support (a turing card).

[MrVideo]

Jdobbs: There is currently an unbranded GTX-1050 on E-bay for $80. I'll be happy to buy it and sent it to you. Just let me know right away before it goes away.

[cartman0208]

I think it needs to be a GTX-1050, or better, for HEVC hardware encoding support.

The GTX-1050 has the 2176p issue. AIUI, it needs to be a RTX-20xx to get 2160p support (a turing card).

Doesn't need to be a RTX... GTX1660 is also Turing (I've got one), but starts around $200 :(

[jdobbs]

Jdobbs: There is currently an unbranded GTX-1050 on E-bay for $80. I'll be happy to buy it and sent it to you. Just let me know right away before it goes away.I appreciate it. But I'll just wait until I can afford a Turing card. I want to be able to encode with B frames.

I'll probably end up buying one soon enough. My will power for frugality is pretty lame.

[jdobbs]

Doesn't need to be a RTX... GTX1660 is also Turing (I've got one), but starts around $200 :(Yeah. I was thinking about a GTX1660 or GTX1660 ti, and that's around the price point I've been seeing too. Have you done any HEVC encoding with it? Opinion?

[MrVideo]

Yeah. I was thinking about a GTX1660 or GTX1660 ti

How about I get you this one: www.ebay.com/itm/EVGA-GeForce-GTX-1660-Ti-XC-6GB-GDDR5-PCI-Express-Graphics-Card-06G-P4-1163-KR/193329468270?epid=22031750613&hash=item2d0355936e:g:rZMAAOSwgiVeN0~T

[MrVideo]

Doesn't need to be a RTX... GTX1660 is also Turing (I've got one), but starts around $200 :(
Thanks for the update.

[cartman0208]

Yeah. I was thinking about a GTX1660 or GTX1660 ti, and that's around the price point I've been seeing too. Have you done any HEVC encoding with it? Opinion?

Yep, I just uploaded some Samples with different CRF, let the video enthusiasts decide ... I can't see much of a difference ... even at a tenth of the original filesize.
The encoding for each file took less than 10 seconds, but the secondary stream from the orignal is lost in the samples
Original.mkv (https://jammernhilftnichts.de/download/Original.mkv) - 270MB
H265Main10High10bitLvl5.1QP14.mkv (https://jammernhilftnichts.de/download/H265Main10High10bitLvl5.1QP14.mkv) - 207MB
H265Main10High10bitLvl5.1QP18.mkv (https://jammernhilftnichts.de/download/H265Main10High10bitLvl5.1QP18.mkv) - 105MB
H265Main10High10bitLvl5.1QP20.mkv (https://jammernhilftnichts.de/download/H265Main10High10bitLvl5.1QP20.mkv) - 75MB
H265Main10High10bitLvl5.1QP22.mkv (https://jammernhilftnichts.de/download/H265Main10High10bitLvl5.1QP22.mkv) - 53MB
H265Main10High10bitLvl5.1QP24.mkv (https://jammernhilftnichts.de/download/H265Main10High10bitLvl5.1QP24.mkv) - 38MB

[jdobbs]

Yep, I just uploaded some Samples with different CRF, let the video enthusiasts decide ... I can't see much of a difference ... even at a tenth of the original filesize.
The encoding for each file took less than 10 seconds, but the secondary stream from the orignal is lost in the samples
Original.mkv (https://jammernhilftnichts.de/download/Original.mkv) - 270MB
H265Main10High10bitLvl5.1QP14.mkv (https://jammernhilftnichts.de/download/H265Main10High10bitLvl5.1QP14.mkv) - 207MB
H265Main10High10bitLvl5.1QP18.mkv (https://jammernhilftnichts.de/download/H265Main10High10bitLvl5.1QP18.mkv) - 105MB
H265Main10High10bitLvl5.1QP20.mkv (https://jammernhilftnichts.de/download/H265Main10High10bitLvl5.1QP20.mkv) - 75MB
H265Main10High10bitLvl5.1QP22.mkv (https://jammernhilftnichts.de/download/H265Main10High10bitLvl5.1QP22.mkv) - 53MB
H265Main10High10bitLvl5.1QP24.mkv (https://jammernhilftnichts.de/download/H265Main10High10bitLvl5.1QP24.mkv) - 38MBThanks!

I'll take a look at these, and I'll also do some PSNR and SSIM comparisons.

[Edit] You're right... you'd never guess by looking that the 38MB file was compressed that much more than the 270MB original.

[gonca]

I think it needs to be a GTX-1050, or better, for HEVC hardware encoding support.

The GTX-1050 has the 2176p issue. AIUI, it needs to be a RTX-20xx to get 2160p support (a turing card).
A GTX-10xx will do 4k, no B frames on HEVC though

[Sharc]

Thanks!

I'll take a look at these, and I'll also do some PSNR and SSIM comparisons.

[Edit] You're right... you'd never guess by looking that the 38MB file was compressed that much more than the 270MB original.
Well, the smoothing (loss of details) is obvious when you step through the frames in interleaved mode. It doesn't mean that the compressed version is not pleasant to view, it just looks like a denoised original and loss of details in low contrast areas.
Comparisons with SSIM, PSNR and VMAF have already been posted in doom9, but one has definitely to make his own tests and optimize encoder settings, like constant quality versus constant quantizer etc. for ffmpeg NVEnc or rigaya's NVEncC.
One 'problem' I see with HW encoding is that BD-RB would have to analyze the user's HW in order to suggest the appropriate encoder settings.

[cartman0208]

Well, the smoothing (loss of details) is obvious when you step through the frames in interleaved mode. It doesn't mean that the compressed version is not pleasant to view, it just looks like a denoised original and loss of details in low contrast areas.
Comparisons with SSIM, PSNR and VMAF have already been posted in doom9, but one has definitely to make his own tests and optimize encoder settings, like constant quality versus constant quantizer etc. for ffmpeg NVEnc or rigaya's NVEncC.
One 'problem' I see with HW encoding is that BD-RB would have to analyze the user's HW in order to suggest the appropriate encoder settings.

I can't repeat it enough: the main reason for HW encoding is speed ... Usually my 4K encodes with medium to high settings run at 1-2 fps ... HW does the same with over 60 fps ;)

[Sharc]

I can't repeat it enough: the main reason for HW encoding is speed ...
Sure, I know. There is little other good reason to prefer HW over SW encoding. Also keep in mind if CPU demanding avisynth scripts get involved the overall speed gain can significantly drop.
I do not at all argue against HW encoding. The speed/quality/compression compromise has always been a personal decision :).

[jdobbs]

Sure, I know. There is little other good reason to prefer HW over SW encoding. Also keep in mind if CPU demanding avisynth scripts get involved the overall speed gain can significantly drop.
I do not at all argue against HW encoding. The speed/quality/compression compromise has always been a personal decision :).Exactly. Right now BD-RB doesn't offer that choice. Hopefully at some point it will.

One other point. There's also the option to choose the fastest speed for X265 in BD-RB. My guess would be that it is similar to hardware encoding in quality -- and is a lot faster than, say, the default "High Quality" mode in BD-RB. Even on my old AMD FX-8350 I can get 5-7 fps with that setting. It still takes 8-10 hours to encode -- but it doesn't require a $200 investment in a new video card.One 'problem' I see with HW encoding is that BD-RB would have to analyze the user's HW in order to suggest the appropriate encoder settings.Does anyone know if the Nvidia API or FFMPEG/NVENC offer ways to report the capabilities of existing Nvidia hardware? That's one problem I foresee with support for HW encoding -- it changes so much that it could become a full-time job just trying to keep up with it. The Nvidia support matrix (https://developer.nvidia.com/video-encode-decode-gpu-support-matrix) shows the variety of cards and capabilities that you might have to support.

[Sharc]

...Does anyone know if the Nvidia API or FFMPEG/NVENC offer ways to report the capabilities of existing Nvidia hardware? That's one problem I foresee with support for HW encoding -- it changes so much that it could become a full-time job just trying to keep up with it. The Nvidia support matrix (https://developer.nvidia.com/video-encode-decode-gpu-support-matrix) shows the variety of cards and capabilities that you might have to support.
I only know for NVEncC:
NVEncC.exe --check-features
I didn't find something similar for ffmpeg.

[jfcarbel]

Is MULTIPROCESS setting even needed anymore as I seem to recall that both x264 and x265 and multi-threaded by default?

Also I noticed that some rebuilds the extras are not using Quicker for extras CRF setting as likely not identified as extras since the file size of some extras can match the episodes/movie due to length. Is there a way to force a CRF per title or mark certain streams as extras?

[jdobbs]

Is MULTIPROCESS setting even needed anymore as I seem to recall that both x264 and x265 and multi-threaded by default?

Also I noticed that some rebuilds the extras are not using Quicker for extras CRF setting as likely not identified as extras since the file size of some extras can match the episodes/movie due to length. Is there a way to force a CRF per title or mark certain streams as extras?MULIPROCESS has outlived its usefulness. I should probably remove it as an option.

Right now there is no easy way to mark streams as extras or force a CRF per title.

[jfcarbel]

MULIPROCESS has outlived its usefulness. I should probably remove it as an option.

Right now there is no easy way to mark streams as extras or force a CRF per title.

Is NeroAAC another that is no longer useful, that is, have other AAC libraries you use now equal or better quality to Nero's AAC?

Also for MULTIPROCESS=4 with my 6 core/12 thread CPU I am seeing CPU utilization pegged at 100% where without the CPU usage never goes above 30%. Seems it would be much faster with the setting. Does the splitting of the parts into 4 per movie add more time than the Multiprocess gains would give?

[Ch3vr0n]

I'm using multi-process=8 on my 9900k, speeds it up quite nicely. Defo not useless.

[Mike-uk]

Is NeroAAC another that is no longer useful, that is, have other AAC libraries you use now equal or better quality to Nero's AAC?

Also for MULTIPROCESS=4 with my 6 core/12 thread CPU I am seeing CPU utilization pegged at 100% where without the CPU usage never goes above 30%. Seems it would be much faster with the setting. Does the splitting of the parts into 4 per movie add more time than the Multiprocess gains would give?

odd I have a 8700K, BDR ver .05 setting very slow 2 pass

no matter what MULTIPROSESS setting I use n, 6, 2, I see no difference in first pass encode, my cpu is working anywhere between 87-100% giving me 6.50X speed ( pass 1 ) no matter the setting

in resorce manager it shows all cores and threads at 87-100 cpu usage

[jdobbs]

Is NeroAAC another that is no longer useful, that is, have other AAC libraries you use now equal or better quality to Nero's AAC?

Also for MULTIPROCESS=4 with my 6 core/12 thread CPU I am seeing CPU utilization pegged at 100% where without the CPU usage never goes above 30%. Seems it would be much faster with the setting. Does the splitting of the parts into 4 per movie add more time than the Multiprocess gains would give?Not sure if other encoders have grown to equal NeroAAC. I know I still use it.

Interesting. No. I don't believe the splitting would add anything more than a negligible amout of time.

Glad you told me. I wasn't sure if anyone was using MULTIPROCESS.

[LowDead]

Could the difference in speed, using MULTIPROCESS, that is reported above be due to the use of different decoders as in BD-RB will choose the older (faster) x264 or the newer (slower) x264?

//LD

[jfcarbel]

I am going to do a test on my 6 core to compare. I had heard that about 4 for MULTIPROCESS does not make that much difference but never really tested that.

I also have a Ryzen 3900X build coming so be interesting to compare the 2 platforms.

[tebasuna51]

Not sure if other encoders have grown to equal NeroAAC.

Maybe qaac is better for low bitrates, but for NeroAAC quality 0.5 is not possible ear differences with same size than qaac.

NeroAACenc.exe can be distributed (or linked) without copyright problems.
qaac need a instalation process (https://sites.google.com/site/qaacpage/home) not easy to override copyright.

If low bitrates are desired maybe the free opus is the best option.

[musiclover]

I installed BD-RB on a new Windows 10 box. After starting the program I got the message "Your Windows 7 system has been succesfully configured to use LAV with BD Rebuilder". Is BD-RB not recognising my Windows 10 system correctly?

[jdobbs]

I installed BD-RB on a new Windows 10 box. After starting the program I got the message "Your Windows 7 system has been succesfully configured to use LAV with BD Rebuilder". Is BD-RB not recognising my Windows 10 system correctly?No. Actually I was surprised at your post and went back and looked... for some reason I made the message box say "Windows 7"... Nothing to worry about, I'll change it.

[terrykuntz]

I just put together a PC with a AMD Ryzen 3900X processor and currently trying to shrink UHD Aladdin to a 50GB disk. Why is my frame rate only 2-3 frames per second? I do have it set to do the highest quality. With this same settings on other Blu ray's I get frame rates around 40 frames per second?

[MrVideo]

Re-encoding UHD video takes a lot longer via software.

[BuddTX]

One other point. There's also the option to choose the fastest speed for X265 in BD-RB. My guess would be that it is similar to hardware encoding in quality -- and is a lot faster than, say, the default "High Quality" mode in BD-RB.

Interesting Observation JDobbs! I will take "your guess" any day!

So are you saying that the hardware encoding will not give as good quality as software encoding?

The whole idea of wanting to go to HW encoding is speed, but I also want good quality.

I don't want to spend hundreds of dollars on a new video card, and find out that the "best" it can do in HW encoding, is similar to the SW encoding "fastest speed for X265".

Even though I have a relatively new, GTX 1050 TI, it sounds like I would need to upgrade again, to take advantage of all the latest HW encoding options.

So am I understanding this correctly, that with HW encoding, there are limited options for video quality?

If that is the case, HW encoding does not interest me as much now. Of course, we all want speed, but quality is very important to me also.

I would not mind a "several hours-half day-similar time" encode, if I could use HW encoding and also use the "ENCODE_QUALITY=4" setting.

Thanks!

[Mike-uk]

I just put together a PC with a AMD Ryzen 3900X processor and currently trying to shrink UHD Aladdin to a 50GB disk. Why is my frame rate only 2-3 frames per second? I do have it set to do the highest quality. With this same settings on other Blu ray's I get frame rates around 40 frames per second?

UHD is 4x the resolution compared to bluray ( 1080 ) and I guess HDR adds some time so Hella al lot more pixels to process

[Mike-uk]

Interesting Observation JDobbs! I will take "your guess" any day!

So are you saying that the hardware encoding will not give as good quality as software encoding?

The whole idea of wanting to go to HW encoding is speed, but I also want good quality.

I don't want to spend hundreds of dollars on a new video card, and find out that the "best" it can do in HW encoding, is similar to the SW encoding "fastest speed for X265".

Even though I have a relatively new, GTX 1050 TI, it sounds like I would need to upgrade again, to take advantage of all the latest HW encoding options.

So am I understanding this correctly, that with HW encoding, there are limited options for video quality?

If that is the case, HW encoding does not interest me as much now. Of course, we all want speed, but quality is very important to me also.

I would not mind a "several hours-half day-similar time" encode, if I could use HW encoding and also use the "ENCODE_QUALITY=4" setting.

Thanks!

taken from another site hardware 265 encoding is coming on hopefully they can get turing cards better, and hopefully the next gpu cards will be equal

Hey mate, depending on what card you have, NVENC can perform as good as Slow on the right bitrate. Pascal and Maxwell cards don't beat x265 Faster. However Turing cards do. Turing cards in H.265 get much closer to Medium and Slow on x265. If you have a Turing card, and you use FFMPEG with some good options like -g 240 and spatial adaptive quantisation, you can basically get anything x265 can get. Some settings will still use CPU for rc-lookahead and the 2-pass preset "slow", but in terms of speed and quality Turing is the way to go now.

[jdobbs]

Given a high enough bitrate -- almost anything can give excellent quality. But at a given bitrate, you'll be hard pressed to find any solution that can beat X265. When backing up a blu-ray the average bitrate is fixed based upon the target size and the length of the source. While I haven't done any testing, I have doubts that a hardware solution could match it.

With that said... the bitrates are typically pretty high in BD backups, and its debatable whether most people would see a difference.

[BuddTX]

Thank you Mike-UK and JDobbs!

Mike-UK, I have a GTX 1050 TI, and that apparently does not have Turing, and am not anxious to upgrade my video card again! My 9 year old PC is still a workhorse, (6 core Xeon processor (12 threads with Hyperthreading), 24 gig RAM, 2 SSD HD, 2 physical HD), and was hoping to wait a few years before upgrading, because no matter what I buy, two years down the road, it is "not the latest and greatest!"
If you have a Turing card, and you use FFMPEG with some good options like -g 240 and spatial adaptive quantisation, you can basically get anything x265 can get. Some settings will still use CPU for rc-lookahead and the 2-pass preset "slow", but in terms of speed and quality Turing is the way to go now.
Mike, I would not know how to apply those command line parameters in the context of using BD Rebuilder, however your comment does make me ask a new question!

On the first post, JDobbs says:
CURRENT VERSION 0.61.05 (January 23rd, 2020)
2. While not required it is recommended you perform either one of the following (2A, preferred, or 2B):

2A. Download and install the LAV Directshow Filters (https://jammernhilftnichts.de/jdobbs/freeware/LAVFilters-0.65.exe). Use only the version linked here -- as other versions may result in out-of-sync audio. While not required for BD-RB to work, LAVFilters will improve functionality and are free. They are required for some functionality associated with HEVC import and processing.

2B. Download and install FFDSHOW (https://jammernhilftnichts.de/jdobbs/freeware/ffdshow_rev4504_20130312_clsid.exe) and the Haali Matroska Splitter (https://jammernhilftnichts.de/jdobbs/freeware/MatroskaSplitter.exe). While they are not required for BD-RB to work, they will improve functionality and are free. After the install, run "Video Decoder Configuration" for FFDSHOW from the "START/Programs" menu, and make sure MPEG2 decoding is enabled. Do the same using "Audio Decoder Configuration" to ensure "Uncompressed" is set to "All Supported".

2C. If you decide to install both 2A and 2B, make sure HAALI/FFDSHOW (2B) is installed first, followed by LAVFilters (2A). This will prevent issues with HEVC splitting.

I have always only done "2A", and BD rebuilder has always been reliable for me. However, in reading this, should I be installing 2B also? I use BD Rebuilder exclusively to make MKV files, and want to only use X265 encoder.

Reason for asking the question is this line (see bolded sentence):

2B. Download and install FFDSHOW (https://jammernhilftnichts.de/jdobbs/freeware/ffdshow_rev4504_20130312_clsid.exe) and the Haali Matroska Splitter (https://jammernhilftnichts.de/jdobbs/freeware/MatroskaSplitter.exe). While they are not required for BD-RB to work, they will improve functionality and are free.

I certainly would like to "improve functionality" to BD Rebuilder! Please advise.

Thanks!

[terrykuntz]

To increase the frame rate I tried 2 things, I added the option MULTIPROCESS=12 because I have the AMD Ryzen 3900X cpu which ended up changing nothing, frame rate still 3 frames per second. Then I changed the encoder settings to High Quality (default) and now the frame rate changes to 6 frames per second. Is there anything else I can change to increase the frame rate other than changing the encoder settings to a lower value?

[Mike-uk]

BuddTX, yes only the 20XX series Nvidia cards have turing chips, as for your other questions I have no idea but im sure there are people on here that can answer them

[MrVideo]

The GTX-1660 is also a turning card.

[terrykuntz]

I was trying to do the movie UHD movie Aladdin. It took 10 hours to build and it failed at the end: Failed to REBUILD, could you please tell me what went wrong???
----------------------
[02/10/20] BD Rebuilder v0.61.05
[09:58:22] Source: ALADDIN_00800
- Input BD size: 58.18 GB
- Approximate total content: [02:07:58.879]
- Target BD size: 46.26 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: High Quality (Default), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[09:58:29] PHASE ONE, Encoding
- [09:58:29] Processing: VID_00055 (1 of 1)
- [09:58:29] Extracting A/V streams [VID_00055]
- [10:16:09] Reencoding video [VID_00055]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 184,109 frames
- Bitrate: 39,694 Kbs
- [10:16:09] Reencoding: VID_00055, Pass 1 of 1
- [18:19:40] Video Encode complete
- [18:19:40] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (eng): Keeping original audio
[18:19:40]PHASE ONE complete
[18:19:40]PHASE TWO - Rebuild Started
- [18:19:40] Rebuilding BD file Structure
- Failed in attempt to multiplex: MUX_MOVIE_ONLY.meta
- Demuxing time: 17 min 37 sec
[18:20:33] - Failed to REBUILD

[Sharc]

The GTX-1660 is also a turning card.
Turning what/where? Towards the next model which is on the horizon? :p

[Mike-uk]

The GTX-1660 is also a turning card.

yes 1660 is ok, but the 1650 does not support B-frames as its using the older chip

[Sharc]

yes 1660 is ok, but the 1650 does not support B-frames as its using the older chip
The 1650 as well as the 1050Ti support B-frames for H.264 (AVC) but not for H.265 (HEVC).

[MrVideo]

Turning what/where? Towards the next model which is on the horizon? :p
Oops, my fingers got carried away.

[SeeMoreDigital]

Yep, I just uploaded some Samples with different CRF, let the video enthusiasts decide ... I can't see much of a difference ... even at a tenth of the original filesize.
The encoding for each file took less than 10 seconds, but the secondary stream from the orignal is lost in the samples
Original.mkv (https://jammernhilftnichts.de/download/Original.mkv) - 270MB
.....................
H265Main10High10bitLvl5.1QP24.mkv (https://jammernhilftnichts.de/download/H265Main10High10bitLvl5.1QP24.mkv) - 38MB

[Edit] You're right... you'd never guess by looking that the 38MB file was compressed that much more than the 270MB original.
Agreed.... I extracted the Dolby Vision stream from the 'original.mkv' file and added it to the 'H265Main10High10bitLvl5.1QP24.mkv' encode using TSmuxer GUI 'open source'. The OPPO plays the new mux in Dolby Vision without any issues and it looks very good indeed. Amazing...

Cheers

[SquallMX]

yes 1660 is ok, but the 1650 does not support B-frames as its using the older chip

The 1650 Super does, is the cheapest one, quality still is crap vs x265

[SquallMX]

CFR mode produces badly undersized results in UHD mode, I think the issue is that the produced test pass has a lot of corrupted frames, and that screw the size prediction.

[jdobbs]

CFR mode produces badly undersized results in UHD mode, I think the issue is that the produced test pass has a lot of corrupted frames, and that screw the size prediction.Yeah. It definitely needs work. AVISYNTH apparently has a hard time locating a keyframe when pulling out encoding samples, and you end up with corrupted frames. I'd suggest using single-pass ABR instead until I can figure out a better way to select samples for prediction.

[sneaker_ger]

It's not really an AviSynth problem. Are you using LAV Filters to seek in HEVC-in-TS? It's a known limitation of LAV Filters to not seek to keyframes, then (because of the container not providing an index as opposed to mkv/mp4). I think with H.264 it at least mitigates the problem a bit by waiting for a keyframe which might be good enough for CRF/bitrate estimation. There's a reason people are more likely to recommend lwlibavvideosource() instead of DirectShowSource() outside of this sub-forum.

[terrykuntz]

I am trying to reduce the Jumanji UHD movie from 54 GB to 46 GB to burn on a 50 GB disk. The re-encode takes over 11 hours then when trying to re-build structure it fails?? Why?? This sucks?

[02/12/20] BD Rebuilder v0.61.05
[09:13:31] Source: JUMANJI_WELCOME_TO_THE_JUNGLE_00822
- Input BD size: 54.11 GB
- Approximate total content: [01:59:03.135]
- Target BD size: 46.26 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: High Quality (Default), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[09:13:33] PHASE ONE, Encoding
- [09:13:33] Processing: VID_00001 (1 of 1)
- [09:13:33] Extracting A/V streams [VID_00001]
- [09:27:15] Reencoding video [VID_00001]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 171,264 frames
- Bitrate: 41,378 Kbs
- [09:27:15] Reencoding: VID_00001, Pass 1 of 1
- [19:59:21] Video Encode complete
- [19:59:21] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (eng): Keeping original audio
- Track 4354 (eng): Keeping original audio
[19:59:21]PHASE ONE complete
[19:59:21]PHASE TWO - Rebuild Started
- [19:59:21] Rebuilding BD file Structure
- Bitstream exception. Adjusting...
- Failed in attempt to multiplex: MUX_MOVIE_ONLY.meta
- Bitstream exception std::exception. It does not have to be! Please contact application support team for more information.
[20:08:22] - Failed to REBUILD

[terrykuntz]

If I re-open of re-rebuilder and have it continue from where it left off, it rebuilds the BD file structure the progress bar on the bottom gets to 100 percent rebuild then the error occurs at very end?

[prologic]

Today .. Dvdfab failed to do a movie only, of
A Shaun the Sheep Movie Farmageddon...
It came up error on disk `message from oppo .

But BdRebuiler did it, no problem ..(with no re-encode) options.
but I also took 2 audio streams out .. Things are getting good.:thanks:

[jdobbs]

If I re-open of re-rebuilder and have it continue from where it left off, it rebuilds the BD file structure the progress bar on the bottom gets to 100 percent rebuild then the error occurs at very end?It's rare -- but I've seen that error a couple of times. It comes from TSMUXER. Sometimes it just gets confused by the source. I'm not sure why yet, but if I can put my finger on the issue, maybe I'll be able to find a workaround.

[toiletglasses]

How is BD-RB so wildly off-size? I have a blu-ray that's only 4.73GB, so I ask it to encode to BD-5 (4.37GB). Result: 3.73GB. This is with highest quality, 2-pass. The entire point of 2-pass is to get exact size. I've repeated this with FULL blu-rays, to BD25. The result is ALWAYS smaller than DVDFAB, thus, lesser quality. It's off by GIGABYTES. Custom size 23.3GB? BD-RB gives me 19-21GB.
BD-RB log (https://pastebin.com/vCqpQ5fx)

[jdobbs]

How is BD-RB so wildly off-size? I have a blu-ray that's only 4.73GB, so I ask it to encode to BD-5 (4.37GB). Result: 3.73GB. This is with highest quality, 2-pass. The entire point of 2-pass is to get exact size. I've repeated this with FULL blu-rays, to BD25. The result is ALWAYS smaller than DVDFAB, thus, lesser quality. It's off by GIGABYTES. Custom size 23.3GB? BD-RB gives me 19-21GB.
BD-RB log (https://pastebin.com/vCqpQ5fx)From your log:

- Bitrate: 15,000 Kbs

You are hitting the maximum bitrate for an AVCHD disc. BD-RB can't make it any larger without risking exceeding the speed that a BD-5 can handle.

So... BD-RB isn't "wildly off-size" -- it is doing exactly what it supposed to do to prevent the disc from skipping and/or failing during playback.

[Mike-uk]

How is BD-RB so wildly off-size? I have a blu-ray that's only 4.73GB, so I ask it to encode to BD-5 (4.37GB). Result: 3.73GB. This is with highest quality, 2-pass. The entire point of 2-pass is to get exact size. I've repeated this with FULL blu-rays, to BD25. The result is ALWAYS smaller than DVDFAB, thus, lesser quality. It's off by GIGABYTES. Custom size 23.3GB? BD-RB gives me 19-21GB.
BD-RB log (https://pastebin.com/vCqpQ5fx)

shamelessly taken from another site


The Max official allowable bitrates for AVCHD are:

1. (BD media) ~24Mbps v+a+sub/pic
2. (DVD media) ~18Mbps v+a+sub/pic (this is supposed to also equal BD-9 spec)

and the new Max AVCHD/3D and AVCHD/60p rates are:
~28Mbps v+a+sub/pic (only BD media is supported)

As you can see, BD/AVCHD titles on DVD media are more limited by the spin/transfer capability of the DVD playback chain than by the spec's limits, so it often depends on the brand/quality of the playback equipment. Realistically speaking, you should set the target bitrate to fall in the 1/4 to 1/3 (possibly/occasionally 1/2) compared to BD rates.

[jdobbs]

And, although you mention it, I want to emphasize... the 18Mbs is the combined total of video, all audio tracks, subtitles, and muxing overhead (which is significant in an M2TS file). That's why BD-RB puts a 15Mbs limit on video.

[terrykuntz]

It does not matter if you select the target output to be 25 gb or 50 gb. Both selections fail. I do have an AMD processor. The final status is Current Progress: 100.00% and Overall Progress: 99.00%

[02/21/20] BD Rebuilder v0.61.05
[16:56:55] Source: JUMANJI_WELCOME_TO_THE_JUNGLE_00001
- Input BD size: 54.11 GB
- Approximate total content: [01:59:03.135]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: High Quality (Default), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[16:56:59] PHASE ONE, Encoding
[16:56:59]PHASE ONE complete
[16:56:59]PHASE TWO - Rebuild Started
- [16:56:59] Rebuilding BD file Structure
- Bitstream exception. Adjusting...
- Failed in attempt to multiplex: MUX_MOVIE_ONLY.meta
- Bitstream exception std::exception. It does not have to be! Please contact application support team for more information.
[17:00:34] - Failed to REBUILD

[Sharc]

One other point. There's also the option to choose the fastest speed for X265 in BD-RB. My guess would be that it is similar to hardware encoding in quality …..
Out of curiosity I made a quality comparison between cartman's QP24 HW encode and a BD-RB x265 'Very Good (Very Fast)' CPU encode at same bitrate (about 7740 kbps).

- cartman's HEVC QP24 GPU encode: VMAF = 95.7191, SSIM = 0.997884, PSNR = 49.1751
- BD-RB x265 'Very Good (Very Fast)' CPU encode: VMAF = 96.3585, SSIM = 0.997893, PSNR = 49.4838 (CPU encoding speed was about 9 fps with my i5-8400 CPU)

No big difference in the quality metrics, both encodes are softening and denoising the picture somewhat.
Visually they look much the same IMO, by far good enough for casual viewing (a very subjective statement of course :) ).
So the GPU HEVC encode has about the same quality as the CPU x265 'Very Good / Very Fast' encode in this test.

[ripem2011]

trying to to compress 4k black panther but keep getting this error DB Rebuilder experienced error 1605 extractaudiosuds 00058 1605
i dont have any problems doing other movies

thanks

[Ch3vr0n]

No such thing as db rebuilder, and as useless as your message unfortunately without the full bdrb log.

Sent from my Pixel 3 XL using Tapatalk

[ripem2011]

No such thing as db rebuilder, and as useless as your message unfortunately without the full bdrb log.

Sent from my Pixel 3 XL using Tapatalk
my bad BD but you know what i was talking about

[ripem2011]

----------------------
[02 22 20] BD Rebuilder v0.61.05
[11:45:21] Source: BLACK_PANTHER_00004
- Input BD size: 56.16 GB
- Approximate total content: [02:14:34.399]
- Target BD size: 4.36 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Very Good (Very Fast), CRF
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[11:45:21] PHASE ONE, Encoding
- [11:45:21] Processing: VID_00045 (1 of 1)
- [11:45:21] Extracting A/V streams [VID_00045]
- Extracting video streams [VID_00045]
- Extracting secondary video [VID_00045]
- Extracting audio/subtitle streams [VID_00045]
- [12:18:30] ExtractAudioSubs() 00058 1605
- Extracting audio streams [VID_00045]
[12:18:41]PHASE ONE aborted by user request
----------------------
[02 22 20] BD Rebuilder v0.61.05
[12:18:51] Source: BLACK_PANTHER_00004
- Input BD size: 56.16 GB
- Approximate total content: [02:14:34.399]
- Target BD size: 4.36 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Very Good (Very Fast), CRF
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[12:18:52] PHASE ONE, Encoding
- [12:18:52] Processing: VID_00045 (1 of 1)
- [12:18:52] Extracting A/V streams [VID_00045]
[02 22 20] Checking System Settings
- BD-Rebuilder v0.61.05
- Windows Version: 6.2 [9200]
- Working Path Free Space: 343.19GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[02 22 20] Systems Settings Check complete
- Extracting video streams [VID_00045]
- Extracting secondary video [VID_00045]
- Extracting audio/subtitle streams [VID_00045]
- [12:51:55] ExtractAudioSubs() 00058 1605
- Extracting audio streams [VID_00045]
[12:55:14]PHASE ONE aborted by user request

[Mike-uk]

----------------------
[02 22 20] BD Rebuilder v0.61.05
[11:45:21] Source: BLACK_PANTHER_00004
- Input BD size: 56.16 GB
- Approximate total content: [02:14:34.399]
- Target BD size: 4.36 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Very Good (Very Fast), CRF
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[11:45:21] PHASE ONE, Encoding
- [11:45:21] Processing: VID_00045 (1 of 1)
- [11:45:21] Extracting A/V streams [VID_00045]
- Extracting video streams [VID_00045]
- Extracting secondary video [VID_00045]
- Extracting audio/subtitle streams [VID_00045]
- [12:18:30] ExtractAudioSubs() 00058 1605
- Extracting audio streams [VID_00045]
[12:18:41]PHASE ONE aborted by user request
----------------------
[02 22 20] BD Rebuilder v0.61.05
[12:18:51] Source: BLACK_PANTHER_00004
- Input BD size: 56.16 GB
- Approximate total content: [02:14:34.399]
- Target BD size: 4.36 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Very Good (Very Fast), CRF
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[12:18:52] PHASE ONE, Encoding
- [12:18:52] Processing: VID_00045 (1 of 1)
- [12:18:52] Extracting A/V streams [VID_00045]
[02 22 20] Checking System Settings
- BD-Rebuilder v0.61.05
- Windows Version: 6.2 [9200]
- Working Path Free Space: 343.19GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[02 22 20] Systems Settings Check complete
- Extracting video streams [VID_00045]
- Extracting secondary video [VID_00045]
- Extracting audio/subtitle streams [VID_00045]
- [12:51:55] ExtractAudioSubs() 00058 1605
- Extracting audio streams [VID_00045]
[12:55:14]PHASE ONE aborted by user request

4K movie to a 4.46 gig DVD ?? youd be better off using a 1080p bluray version, can you even do UHD HDR to DVD ??( I guess so but HDR to SDR and a ton of wasted time to do it, for one the extracting of A/V takes ages compared to 1080p), it would need to convert HDR to SDR, so as said better to use a 1080p source if your wanting DVD, mayby explain more on what your trying to do ?

[Ch3vr0n]

4K movie to a 4.36 gig DVD ?? youd be better off using a 1080p bluray version

Perhaps, but that doesn't clarify the problem nor should it impact EXTRACTING of the streams. The size issue should only come into play during rebuilding (if it would even start rebuilding).

Though on that issue, even if it's possible, it'll look like crap. Even with x264/x265

[ripem2011]

Perhaps, but that doesn't clarify the problem nor should it impact EXTRACTING of the streams. The size issue should only come into play during rebuilding (if it would even start rebuilding).

Though on that issue, even if it's possible, it'll look like crap. Even with x264/x265
i done it with a couple other ones just to see how it looks even with DV it dont look bad at all or my eyes are but then i add atmos to it with tsMuxeR and every thing work good but not with black panther no matter if i do 25 gig still get that error

[Mike-uk]

i done it with a couple other ones just to see how it looks even with DV it dont look bad at all or my eyes are but then i add atmos to it with tsMuxeR and every thing work good but not with black panther no matter if i do 25 gig still get that error

Atmos track on a DVD ?? that's out of spec, are you playing these dvds in a dvd player ??

[SeeMoreDigital]

Atmos track on a DVD ?? that's out of spec, are you playing these dvds in a dvd player ??Perhaps the tracks are being authored to suit the Blu-ray spec but are being burned onto DVD~R's.

[ripem2011]

Atmos track on a DVD ?? that's out of spec, are you playing these dvds in a dvd player ??

copy them on my usb drive play them on my Sony UBP-X700 no problems then store them on my USB hard drive hooked to my 4k bluray player

[SquallMX]

Out of curiosity I made a quality comparison between cartman's QP24 HW encode and a BD-RB x265 'Very Good (Very Fast)' CPU encodes at same bitrate (about 7740 kbps).

- cartman's HEVC QP24 GPU encode: VMAF = 95.7191, SSIM = 0.997884, PSNR = 49.1751
- BD-RB x265 'Very Good (Very Fast)' CPU encode: VMAF = 96.3585, SSIM = 0.997893, PSNR = 49.4838 (CPU encoding speed was about 9 fps with my i5-8400 CPU)

No big difference in the quality metrics, both encodes are softening and denoising the picture somewhat.
Visually they look much the same IMO, by far good enough for casual viewing (a very subjective statement of course :) ).
So the GPU HEVC encode has about the same quality as the CPU x265 'Very Good / Very Fast' encode in this test.

Newer movies are easy to compress, try using an older one (35 mm film), I remember doing some tests with the original Ghostbusters, even at BD50 bitrate, the NVIDIA encoder was awful (http://www.framecompare.com/image-compare/screenshotcomparison/DZLPGNNX), grain retention was particularly bad.

[Sharc]

Newer movies are easy to compress, try using an older one (35 mm film), I remember doing some tests with the original Ghostbusters, even at BD50 bitrate, the NVIDIA encoder was awful (http://www.framecompare.com/image-compare/screenshotcomparison/DZLPGNNX), grain retention was particularly bad.
Agree, but I wouldn't recommend superfast x265 setting for difficult sources and strong compression either.

[Lathe]

The GTX-1660 is also a turning card.

'A Turn of a Friendly Card'...? :D

[Lathe]

Turning what/where? Towards the next model which is on the horizon? :p

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

[Mike-uk]

quicker encode for extras ?? does this affect multi file discs, I have a disc with 4 files that make up the main movie 1 file is 130mb another 430, will quicker mode encode this low file sizes with lesster quality ?

Thanks
Mike

[Tyrell63]

BD Rebuilder 0.61.05
Trying to work on two different 3D videos (BD-50)
Both are stopping with
[13:51:28] Reencoding: VID_00042, Pass 1 of 1
[13:52:29] - Failed video encode, aborted
Trying CloneBD on these mounted disks results in no error

Best
Lutz

[Ch3vr0n]

BD Rebuilder 0.61.05
Trying to work on two different 3D videos (BD-50)
Both are stopping with
[13:51:28] Reencoding: VID_00042, Pass 1 of 1
[13:52:29] - Failed video encode, aborted
Trying CloneBD on these mounted disks results in no error

Best
Lutz

full bdrb log, or nobody can help you, and you need to provide a lot more info. For example, i own and use CloneBD myself and it does NOT support disc-to-disc backups of 3D titles. It only supports them to an alternate output such as mp4, mkv...

[Mike-uk]

full bdrb log, or nobody can help you, and you need to provide a lot more info. For example, i own and use CloneBD myself and it does NOT support disc-to-disc backups of 3D titles. It only supports them to an alternate output such as mp4, mkv...

the "other" cloneBD apparently does full 3D 1:1 backups

[Ch3vr0n]

You mean the [emoji205] monkey? Or ClownBD? Afaik full disc to disc isn't yet supported by elby's CloneBD.

Sent from my Pixel 3 XL using Tapatalk

[Mike-uk]

umm no cloneBD, yes not elby software, no idea if its real or works

[Image Removed by moderator]

[Ch3vr0n]

Looks like someone trying to get some easy money of CloneBD's (elby) name. I wouldn't trust it if they gave it to me for free.

[DrinkLyeAndDie]

Looks like someone trying to get some easy money of CloneBD's (elby) name. I wouldn't trust it if they gave it to me for free.

Likely the same bozos who released a not-the-same-as-Elby-CloneDVD CloneDVD [dot] net software. Compare the fire image to the left of the product names for the knock-off CloneDVD & CloneBD software and they look coincidentally similar as do the websites, as a whole.

[Tyrell63]

full bdrb log, or nobody can help you, and you need to provide a lot more info. For example, i own and use CloneBD myself and it does NOT support disc-to-disc backups of 3D titles. It only supports them to an alternate output such as mp4, mkv...

How can I get a log file? I can reproduce the error. I know that CloneBD can only do 3D when extracting the movie itself (not a 1:1 copy aof all). Thats why I prefer BD Rebuilder

[Mike-uk]

How can I get a log file?


in your working path or output folder you will see BD-REBUILDER.log, just copy and paste the job/s that have problems

[jdobbs]

@Mike-uk

What? Now we're reproducing ads for products and posting them as images in this "Bug Reports Only" thread? I realize I'm not a strict moderator... but come on. I'm removing it.

Please review Forum Rules 3 and 5.

[Mike-uk]

Hi jdobbs, yes sorry, I guess it was off topic, it wasn't ment to be advertising was just a response to previous posts

[Tyrell63]

in your working path or output folder you will see BD-REBUILDER.log, just copy and paste the job/s that have problems

Thank you.
Here is the log to the error:

----------------------
[03.10.20] BD Rebuilder v0.61.05
[10:50:33] Source: READY_PLAYER_ONE
- Input BD size: 46,53 GB
- Approximate total content: [02:30:38.654]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- Quality: Very Good (Very Fast), ABR
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[10:50:33] PHASE ONE, Encoding
- [10:50:33] Processing: VID_00018 (1 of 2)
- [10:50:33] Extracting A/V streams [VID_00018]
- [10:51:06] Reencoding video [VID_00018]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 8.159 frames
- Bitrate: 4.464 Kbs
- Using FRIMEncoder for MVC encoding
- [10:51:06] Reencoding: VID_00018, Pass 1 of 1
- [11:01:11] Video Encode complete
- [11:01:11] Processing audio tracks
- [11:01:11] Multiplexing M2TS
- [11:01:15] Scanning for 3D CLPI info...
- [11:01:17] Processing: VID_00042 (2 of 2)
- [11:01:17] Extracting A/V streams [VID_00042]
- [11:35:05] Reencoding video [VID_00042]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 201.357 frames
- Bitrate: 11.870 Kbs
- Using FRIMEncoder for MVC encoding
- [11:35:05] Reencoding: VID_00042, Pass 1 of 1
[11:36:06] - Failed video encode, aborted

[jdobbs]

'A Turn of a Friendly Card'...? :DAlan Parsons Project, 1980

[cartman0208]

...
- Decoding/Frame serving: FRIMDecode
...
- Using FRIMEncoder for MVC encoding
...
- Using FRIMEncoder for MVC encoding
- [11:35:05] Reencoding: VID_00042, Pass 1 of 1
[11:36:06] - Failed video encode, aborted

try using DirectShowSource as Frameserver

[writersblock29]

Yeah. I was thinking about a GTX1660 or GTX1660 ti, and that's around the price point I've been seeing too. Have you done any HEVC encoding with it? Opinion?

Not sure if you're still wondering about these cards, but I use a GTX1660 via Staxrip for creating files for my Emby server. I'm quite satisfied with it! B-frames work fine, and most certainly do make a difference in regard to file size vs. quality. NVENC isn't as tweakable as x265/x264, but in all honesty both compression standards are so efficient that...

Well, let me paraphrase something a wise man has said several times hereabouts: It's like pissing into the ocean. Sure, it'll raise sea level, but not by a noticeable amount. ;-)

I can confirm that it's capable of outputting set-top-friendly files, since I have used it to create discs from time to time. I'd call it a good choice if you're wanting to tinker with it without having to declare bankruptcy.

[jdobbs]

Not sure if you're still wondering about these cards, but I use a GTX1660 via Staxrip for creating files for my Emby server. I'm quite satisfied with it! B-frames work fine, and most certainly do make a difference in regard to file size vs. quality. NVENC isn't as tweakable as x265/x264, but in all honesty both compression standards are so efficient that...

Well, let me paraphrase something a wise man has said several times hereabouts: It's like pissing into the ocean. Sure, it'll raise sea level, but not by a noticeable amount. ;-)

I can confirm that it's capable of outputting set-top-friendly files, since I have used it to create discs from time to time. I'd call it a good choice if you're wanting to tinker with it without having to declare bankruptcy.Thanks for the feedback.

[Mike-uk]

30xx series nvidia cards are rumoured to be coming out in a few months, mayby h265 has been improved again over the current turing cards

[gonca]

Alan Parsons Project, 1980

You realize that was 40 years ago?
Aging yourself a bit.

Disclosure
Used to have the LP (vinyl), now have the digital version

[MrVideo]

YUsed to have the LP (vinyl),
I still have that LP and ALL of the singles/LPs that I've ever obtained.

[jdobbs]

I still have that LP and ALL of the singles/LPs that I've ever obtained.I do to... and digital versions for almost all of them (mostly FLAC that I ripped from CDs).

[jdobbs]

You realize that was 40 years ago?
Aging yourself a bit.

Disclosure
Used to have the LP (vinyl), now have the digital versionScary. I was working in assembler language back then on a computer assisted radar system that had actual core memory (donut shaped magnets threaded with conductors) and an 18 bit address bus. Debugging consisted of pushing the STOP button and reading a group LEDs to find the current address and the contents of the accumulator, followed by scanning the 4 foot stack of code listings to find out how we got there.

"Old" hardly covers it.

[gonca]

But it is still a good song, along with most of what Alan Parsons Project released

[Tyrell63]

try using DirectShowSource as Frameserver

Direct Show is already set (Default setting)

[jdobbs]

But it is still a good song, along with most of what Alan Parsons Project releasedThat it is. I think I may have every album Alan Parsons released.

[AmigaFuture]

You realize that was 40 years ago?
Aging yourself a bit.

Disclosure
Used to have the LP (vinyl), now have the digital version

I still have that LP and ALL of the singles/LPs that I've ever obtained.

The only LPs I kept were of Rush. The only band progressive enough worth keeping..okay, okay, also AC/DC. But Rush..that's golden, _The Best_ when it comes to music. Neil and Geddy made sure those lyrics where unique and honest. Zero fluff.

I left vinyl when CD's started becoming really well made, when "Remasters" were being created. I don't miss the Pops and Hisses of, Hisses of, Hisses of, Hisses of, LPs..and I was also deeply into how to care for them...and much, much more than I'll post here. One thing I do not support is Apple Digital or any other kind of Digital that does not support Lossless. Without a CD you're missing soooo much. That's what I miss about LPs...Artwork, and correct grammar and punctuation with information contained inside.

I've obtained all my favorites in Digital as well. I've encoded all my (sooo many) CDs with FLAC or APE. I've made sure Artwork is part of it.

Progressive music is much better than 95% of the stuff that's played these days. Auto-Tune = You're unable to sing = Stop!

[MrVideo]

What sucks about CDs is the 44.1 kHz sample rate. At a minimum it should have been 48 kHz. You can find 48/96 kHz material out there, but they are few and far between.

[Sharc]

What sucks about CDs is the 44.1 kHz sample rate. At a minimum it should have been 48 kHz. You can find 48/96 kHz material out there, but they are few and far between.
44.1 kHz sampling rate sucks? Hmmm, 44.1 kHz sampling rate accommodates audio frequencies up to about 20....22 kHz. I have some doubts whether people beyond their 20ies can even hear 20 kHz. Lot of placebos in the audio industry .....

[jdobbs]

44.1 kHz sampling rate sucks? Hmmm, 44.1 kHz sampling rate accommodates audio frequencies up to about 20....22 kHz. I have some doubts whether people beyond their 20ies can even hear 20 kHz. Lot of placebos in the audio industry .....Yep. Anytime your hear the term "HD Audio" you can bet you are being sold a bill of nonsense.

[MrVideo]

The point is that the upper frequencies harmonics are lost.

[Sharc]

The point is that the upper frequencies harmonics are lost.
Harmonics contribute to an instrument's 'timbre', but only with those frequencies which are within a human's hearing range which is normally below about 20kHz for youngsters. (Your avatar may chime in at this point though ;) ).
Now take the highest C of a piano which is about 4186 Hz. Its audible overtones would be 8372, 12558, 16400, 20930Hz which are still covered by the 44.1kHz sampling rate. An 48kHz sampling rate will not even include the next harmonic of 25116Hz for which the minimum sampling rate would have to be about 51kHz.
So I don't see a significant improvement between 44.1kHz sampling rate or 48kHz sampling rate. More important than extending the frequency range is the resolution (quantization) of the samples (true 16bit is fine) and how the samples are processed in the sequel.
Oh well, audio quality can be discussed to death by audiophiles :).

Edit:
Now this makes we wonder why the sampling rate has been increased from 44.1 to 48kHz at all. Technology convenience? Marketing gimmick? Or perhaps a better or simpler design of the anti-aliasing filter with a smoother roll-of and a better transient response? Just guessing.

[MrVideo]

Its audible overtones would be 8372, 12558, 16400, 20930Hz which are still covered by the 44.1kHz sampling rate.
20930 Hz has better sampling at 48 kHz than it does as 44.1 kHz (more data points). I suspect that 44.1 kHz was used on a CD in order to be able to supply more music. That doesn't hold water when existing LPs are redone for CDs, considering that a 48 kHz rate would have let them fit just fine.

In any event, back to our normal programming.

[jdobbs]

I have a question in the hope that one of the X265 experts out there can help me understand something. It's regarding how CRF mode works.

In X264, if I select a CRF value, I can be confident that it actually results in "constant quality". In other words, if I choose "medium" as my encoding preset and set the CRF to 20, I will get approximately the same quality as if I do the same using the "ultrafast" preset. Of course there will be a sacrifice in file size in order to make up the decreased efficiency of the faster mode. Great. Makes perfect sense.

But when I run X265 it seems to be all over the place. For example, I ran a job last night in which I used the exact same command line (with CRF=20) but changed only the preset from "ultrafast" to "medium". The "medium" job resulted in an HEVC file that is 69% larger than the "ultrafast" encode??? Huh? That is the exact opposite of what common sense would dictate. I haven't tested it yet, but I'm certain the ultrafast encode won't look as good... but how is that "constant quality"? I'm confused.

[Sharc]

@jdobbs
You may find this discussion interesting:
https://forum.doom9.org/showthread.php?t=180438
At the end CRF means just constant rate factor and provides a 'constant quality' for a particular encode. It is not an absolute quality measure and hence even for the same CRF the quality differs from source to source and between different encoder settings.
But yes, the behavior for x264 was more logical than it seems to be for x265.

[jdobbs]

@jdobbs
You may find this discussion interesting:
https://forum.doom9.org/showthread.php?t=180438
At the end CRF means just constant rate factor and provides a 'constant quality' for a particular encode. It is not an absolute quality measure and hence even for the same CRF the quality differs from source to source and between different encoder settings.
But yes, the behavior for x264 was more logical than it seems to be for x265.You would think, though, that "constant quality" for the exact same source would have some root in logic. It very definitely doesn't. All I get from all this is that in X265 CRF=20 doesn't equal CRF=20. Now that is crazy.

[Sharc]

You would think, though, that "constant quality" for the exact same source would have some root in logic. It very definitely doesn't. All I get from all this is that in X265 CRF=20 doesn't equal CRF=20. Now that is crazy.
Only when one links CRF with 'constant quality', or (mis)interprets it as a measure for absolute quality. I understand that it has been 'sold' like this to make it popular or easier to understand, but in fact it just means Constant Rate Factor for the encoding process, and nothing else. It aims at providing a 'constant quality' visual experience for that particular encode, but when one changes encoding parameters for the same CRF and same source the quality as well as the files size will change. Apparently this seems to be much more pronounced for x265 than for x264.
When x265 encoder preset is changed from fast to slow and the file size increases (unexpectedly) for the same CRF one would expect in return that the quality has become better, like less blurring, better noise and details retention in low contrast areas etc. But seen from the encoding process it is still the same CRF, but not the same quality.
Whether this could be aligned more logical in the quality/encoder settings/file size context for x265, I really don't know. Perhaps an expert could shed some light on this.

What remains at the end is that for a given set of encoding parameters (preset) and for a given same source the quality becomes worse (@lower file size) for a higher CRF and becomes better (@higher file size) for a lower CRF. So I'd assume that the 1-pass CRF size prediction algo in BD-RB will still be working.

[cartman0208]

Out of curiosity I made a quality comparison between cartman's QP24 HW encode and a BD-RB x265 'Very Good (Very Fast)' CPU encode at same bitrate (about 7740 kbps).

- cartman's HEVC QP24 GPU encode: VMAF = 95.7191, SSIM = 0.997884, PSNR = 49.1751
- BD-RB x265 'Very Good (Very Fast)' CPU encode: VMAF = 96.3585, SSIM = 0.997893, PSNR = 49.4838 (CPU encoding speed was about 9 fps with my i5-8400 CPU)

No big difference in the quality metrics, both encodes are softening and denoising the picture somewhat.
Visually they look much the same IMO, by far good enough for casual viewing (a very subjective statement of course :) ).
So the GPU HEVC encode has about the same quality as the CPU x265 'Very Good / Very Fast' encode in this test.

How can I compare the results myself? Is there some kind of How-to?
I'd like to tweak my settings to see if I can get even more quality ;)

[Sharc]

How can I compare the results myself? Is there some kind of How-to?
I'd like to tweak my settings to see if I can get even more quality ;)
1) Subjectively (my preference actually) using my eyes: Open the script below in a player like MPC-HC and step through the interleaved pictures one by one and spot the difference.
v1=your source filter for videofile 1
v2=your source filter for videofile 2
interleave(v1,v2)

Pay attention to fine details (especially in low contrast areas), blurring, color banding, noise, artefacts etc. Step backward and forward between pairs of pictures. Zoom in as needed.

2) More objective: Using a standardized metric. Google for PSNR, SSIM, VMAF to get an idea how to proceed. And crop the borders for these tests because they would bias the result.

[spotswood]

Hello all, hope everyone is safe and healthy...

Well, like many of us, I'm stuck inside with too much time on my hands. I've come across a puzzling problem and can't figure it out. Using the latest v0.61.05, my BD9 encodes are averaging 1GB-1.5GB under the default target size of 7.84GB when finished.

My latest BD9 encode is Rocky which has a DTS-MA 5.1 track that I choose to re-encode to AC3@640. It finishes w/a file size of 6.30GB, about 1.5GB under the normal default target for a BD9.

So I try a Custom Target Size to increase the finished file size (have done this before many times w/no problems), but when I choose any size over 8499MB, the movie bit rate decreases by half, from 6,199Kbs for BD9, to 3387Kbs for 8500MB? Makes no sense!

I've tried it w/movie and menus and movie only but every time I increase the custom target to 8500MB or more the bit rate and file size gets smaller. Any ideas?

Thanks for any help or suggestions. Hang in there everyone!

[84lion]

Does BD-RB have an option wherein UHD content can be encoded to HD BD compliant structure? For example, under Alternate Movie-Only Output, the Standard Output is to Output a BD or AVCHD Compliant Structure. But this retains the UHD content (2160p). What I am looking for is a way to downrez the movie-only content to 1080p in a format that I could burn to a BR disc. I know I could recode it to MKV at 1080p equivalent, but some players don’t show the subtitles.

[musiclover]

Does BD-RB have an option wherein UHD content can be encoded to HD BD compliant structure? For example, under Alternate Movie-Only Output, the Standard Output is to Output a BD or AVCHD Compliant Structure. But this retains the UHD content (2160p). What I am looking for is a way to downrez the movie-only content to 1080p in a format that I could burn to a BR disc. I know I could recode it to MKV at 1080p equivalent, but some players don’t show the subtitles.

I guess you could import the resulting mkv in BD-RB and go from there.

[jdobbs]

Hello all, hope everyone is safe and healthy...

Well, like many of us, I'm stuck inside with too much time on my hands. I've come across a puzzling problem and can't figure it out. Using the latest v0.61.05, my BD9 encodes are averaging 1GB-1.5GB under the default target size of 7.84GB when finished.

My latest BD9 encode is Rocky which has a DTS-MA 5.1 track that I choose to re-encode to AC3@640. It finishes w/a file size of 6.30GB, about 1.5GB under the normal default target for a BD9.

So I try a Custom Target Size to increase the finished file size (have done this before many times w/no problems), but when I choose any size over 8499MB, the movie bit rate decreases by half, from 6,199Kbs for BD9, to 3387Kbs for 8500MB? Makes no sense!

I've tried it w/movie and menus and movie only but every time I increase the custom target to 8500MB or more the bit rate and file size gets smaller. Any ideas?

Thanks for any help or suggestions. Hang in there everyone!8500 is the cutoff where BD-RB decides it is no longer encoding for DVD-R and removes the restrictions/rules. It is odd, though, that you could undersize by that much on a DVD. How big is the source? Is it hitting possibly the maximum bitrate for DVD-R? I'd have to see a log to know.

[spotswood]

8500 is the cutoff where BD-RB decides it is no longer encoding for DVD-R and removes the restrictions/rules. It is odd, though, that you could undersize by that much on a DVD. How big is the source? Is it hitting possibly the maximum bitrate for DVD-R? I'd have to see a log to know.Here 2 logs from my tests...

Default BD9
----------------------
[03/27/20] BD Rebuilder v0.61.05
[22:16:42] Source: ROCKY
- Input BD size: 31.39 GB
- Approximate total content: [06:16:13.383]
- Target BD size: 7.84 GB
- Windows Version: 6.2 [9200]
- MOVIE and MENUS mode enabled
- Quality: High Quality (Default), Two Pass
- SHUTDOWN at completion enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=1 HD=1 Kbs=640
[22:16:42] PHASE ONE, Encoding
- [22:16:42] Processing: VID_00020 (1 of 99)
- [22:16:42] Extracting A/V streams [VID_00020]
- [22:16:51] Reencoding video [VID_00020]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,740 frames
- Bitrate: 8,694 Kbs
- [22:16:51] Reencoding: VID_00020, Pass 1 of 2
- [22:17:24] Reencoding: VID_00020, Pass 2 of 2
- [22:18:00] Video Encode complete
- [22:18:00] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:18:01] Multiplexing M2TS
- [22:18:05] Blanking: VID_00070 (2 of 99)
- [22:18:05] Blanking: VID_00121 (3 of 99)
- [22:18:05] Blanking: VID_00122 (4 of 99)
- [22:18:05] Blanking: VID_00123 (5 of 99)
- [22:18:05] Blanking: VID_00131 (6 of 99)
- [22:18:05] Blanking: VID_00133 (7 of 99)
- [22:18:05] Blanking: VID_00151 (8 of 99)
- [22:18:05] Blanking: VID_00152 (9 of 99)
- [22:18:05] Blanking: VID_00153 (10 of 99)
- [22:18:05] Blanking: VID_00154 (11 of 99)
- [22:18:05] Blanking: VID_00155 (12 of 99)
- [22:18:05] Blanking: VID_00156 (13 of 99)
- [22:18:05] Blanking: VID_00157 (14 of 99)
- [22:18:05] Blanking: VID_00158 (15 of 99)
- [22:18:05] Blanking: VID_00159 (16 of 99)
- [22:18:05] Blanking: VID_00160 (17 of 99)
- [22:18:05] Blanking: VID_00161 (18 of 99)
- [22:18:05] Blanking: VID_00162 (19 of 99)
- [22:18:05] Blanking: VID_00163 (20 of 99)
- [22:18:05] Blanking: VID_00164 (21 of 99)
- [22:18:05] Blanking: VID_00165 (22 of 99)
- [22:18:05] Blanking: VID_00166 (23 of 99)
- [22:18:05] Blanking: VID_00167 (24 of 99)
- [22:18:05] Blanking: VID_00168 (25 of 99)
- [22:18:05] Blanking: VID_00169 (26 of 99)
- [22:18:05] Blanking: VID_00170 (27 of 99)
- [22:18:05] Blanking: VID_00171 (28 of 99)
- [22:18:05] Blanking: VID_00172 (29 of 99)
- [22:18:05] Blanking: VID_00173 (30 of 99)
- [22:18:05] Blanking: VID_00174 (31 of 99)
- [22:18:05] Blanking: VID_00175 (32 of 99)
- [22:18:05] Blanking: VID_00176 (33 of 99)
- [22:18:05] Blanking: VID_00177 (34 of 99)
- [22:18:05] Blanking: VID_00178 (35 of 99)
- [22:18:05] Blanking: VID_00179 (36 of 99)
- [22:18:06] Blanking: VID_00180 (37 of 99)
- [22:18:06] Blanking: VID_00181 (38 of 99)
- [22:18:06] Blanking: VID_00182 (39 of 99)
- [22:18:06] Blanking: VID_00183 (40 of 99)
- [22:18:06] Blanking: VID_00184 (41 of 99)
- [22:18:06] Blanking: VID_00185 (42 of 99)
- [22:18:06] Blanking: VID_00186 (43 of 99)
- [22:18:06] Blanking: VID_00187 (44 of 99)
- [22:18:06] Blanking: VID_00188 (45 of 99)
- [22:18:06] Blanking: VID_00189 (46 of 99)
- [22:18:06] Blanking: VID_00190 (47 of 99)
- [22:18:06] Blanking: VID_00191 (48 of 99)
- [22:18:06] Processing: VID_00200 (49 of 99)
- [22:18:06] Extracting A/V streams [VID_00200]
- [22:18:10] Reencoding video [VID_00200]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 249 frames
- Bitrate: 4,533 Kbs
- [22:18:10] Reencoding: VID_00200, Pass 1 of 2
- [22:18:14] Reencoding: VID_00200, Pass 2 of 2
- [22:18:17] Video Encode complete
- [22:18:17] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [22:18:18] Multiplexing M2TS
- [22:18:22] Blanking: VID_00220 (50 of 99)
- [22:18:22] Blanking: VID_00234 (51 of 99)
- [22:18:22] Blanking: VID_00370 (52 of 99)
- [22:18:22] Blanking: VID_00371 (53 of 99)
- [22:18:22] Blanking: VID_00372 (54 of 99)
- [22:18:22] Processing: VID_00600 (55 of 99)
- [22:18:22] Extracting A/V streams [VID_00600]
- [22:18:26] Reencoding video [VID_00600]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1 frames
- Bitrate: 9,569 Kbs
- [22:18:26] Reencoding: VID_00600, Pass 1 of 2
- [22:18:26] Reencoding: VID_00600, Pass 2 of 2
- [22:18:26] Video Encode complete
- [22:18:26] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [22:18:26] Multiplexing M2TS
- [22:18:30] Blanking: VID_00601 (56 of 99)
- [22:18:30] Processing: VID_00720 (57 of 99)
- [22:18:30] Extracting A/V streams [VID_00720]
- [22:18:35] Reencoding video [VID_00720]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 430 frames
- Bitrate: 5,307 Kbs
- [22:18:35] Reencoding: VID_00720, Pass 1 of 2
- [22:18:42] Reencoding: VID_00720, Pass 2 of 2
- [22:18:50] Video Encode complete
- [22:18:50] Processing audio tracks
- [22:18:50] Multiplexing M2TS
- [22:18:54] Processing: VID_00800 (58 of 99)
- [22:18:54] Extracting A/V streams [VID_00800]
- [22:24:18] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 172,170 frames
- Bitrate: 6,199 Kbs
- [22:24:18] Reencoding: VID_00800, Pass 1 of 2
- [23:08:53] Reencoding: VID_00800, Pass 2 of 2
- [00:00:44] Video Encode complete
- [00:00:44] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [00:03:14] Multiplexing M2TS
- [00:07:06] Blanking: VID_01288 (59 of 99)
- [00:07:06] Blanking: VID_01289 (60 of 99)
- [00:07:06] Blanking: VID_01290 (61 of 99)
- [00:07:06] Blanking: VID_01291 (62 of 99)
- [00:07:06] Blanking: VID_01292 (63 of 99)
- [00:07:06] Blanking: VID_01293 (64 of 99)
- [00:07:07] Blanking: VID_01294 (65 of 99)
- [00:07:07] Blanking: VID_01295 (66 of 99)
- [00:07:07] Blanking: VID_01296 (67 of 99)
- [00:07:07] Blanking: VID_01297 (68 of 99)
- [00:07:07] Blanking: VID_01298 (69 of 99)
- [00:07:07] Blanking: VID_01299 (70 of 99)
- [00:07:07] Blanking: VID_01300 (71 of 99)
- [00:07:07] Blanking: VID_01301 (72 of 99)
- [00:07:07] Blanking: VID_01302 (73 of 99)
- [00:07:07] Blanking: VID_01303 (74 of 99)
- [00:07:07] Blanking: VID_01304 (75 of 99)
- [00:07:07] Blanking: VID_01305 (76 of 99)
- [00:07:07] Blanking: VID_01306 (77 of 99)
- [00:07:07] Blanking: VID_01307 (78 of 99)
- [00:07:07] Blanking: VID_01308 (79 of 99)
- [00:07:07] Blanking: VID_01309 (80 of 99)
- [00:07:07] Blanking: VID_01310 (81 of 99)
- [00:07:07] Blanking: VID_01311 (82 of 99)
- [00:07:07] Blanking: VID_01312 (83 of 99)
- [00:07:07] Blanking: VID_01313 (84 of 99)
- [00:07:07] Blanking: VID_01314 (85 of 99)
- [00:07:07] Blanking: VID_01315 (86 of 99)
- [00:07:07] Blanking: VID_01316 (87 of 99)
- [00:07:07] Blanking: VID_01317 (88 of 99)
- [00:07:07] Blanking: VID_01318 (89 of 99)
- [00:07:07] Blanking: VID_01319 (90 of 99)
- [00:07:07] Blanking: VID_01320 (91 of 99)
- [00:07:07] Blanking: VID_01321 (92 of 99)
- [00:07:07] Blanking: VID_01525 (93 of 99)
- [00:07:07] Blanking: VID_01526 (94 of 99)
- [00:07:07] Blanking: VID_01527 (95 of 99)
- [00:07:07] Blanking: VID_01528 (96 of 99)
- [00:07:07] Blanking: VID_01529 (97 of 99)
- [00:07:07] Blanking: VID_01530 (98 of 99)
- [00:07:07] Blanking: VID_01531 (99 of 99)
[00:07:07]PHASE ONE complete
[00:07:07]PHASE TWO - Rebuild Started
- [00:07:07] Rebuilding BD file Structure
[00:07:12] - Encode and Rebuild complete
- WORKFILES folder removed.
- Computer SHUTDOWN initiated.

Custom Target 8512MB: Notice how the movie bit rate in bold decreases from 6,199 Kbs to 3,387 Kbs even though the target size is larger...
----------------------
[03/27/20] BD Rebuilder v0.61.05
[19:50:36] Source: ROCKY
- Input BD size: 31.39 GB
- Approximate total content: [06:16:13.383]
- Target BD size: 8.34 GB
- Windows Version: 6.2 [9200]
- MOVIE and MENUS mode enabled
- Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=1 HD=1 Kbs=640
[19:50:38] PHASE ONE, Encoding
- [19:50:38] Blanking: VID_00070 (1 of 97)
- [19:50:38] Blanking: VID_00121 (2 of 97)
- [19:50:38] Blanking: VID_00122 (3 of 97)
- [19:50:38] Blanking: VID_00123 (4 of 97)
- [19:50:38] Blanking: VID_00131 (5 of 97)
- [19:50:38] Blanking: VID_00133 (6 of 97)
- [19:50:39] Blanking: VID_00151 (7 of 97)
- [19:50:39] Blanking: VID_00152 (8 of 97)
- [19:50:39] Blanking: VID_00153 (9 of 97)
- [19:50:39] Blanking: VID_00154 (10 of 97)
- [19:50:39] Blanking: VID_00155 (11 of 97)
- [19:50:39] Blanking: VID_00156 (12 of 97)
- [19:50:39] Blanking: VID_00157 (13 of 97)
- [19:50:39] Blanking: VID_00158 (14 of 97)
- [19:50:39] Blanking: VID_00159 (15 of 97)
- [19:50:39] Blanking: VID_00160 (16 of 97)
- [19:50:39] Blanking: VID_00161 (17 of 97)
- [19:50:39] Blanking: VID_00162 (18 of 97)
- [19:50:39] Blanking: VID_00163 (19 of 97)
- [19:50:39] Blanking: VID_00164 (20 of 97)
- [19:50:39] Blanking: VID_00165 (21 of 97)
- [19:50:39] Blanking: VID_00166 (22 of 97)
- [19:50:39] Blanking: VID_00167 (23 of 97)
- [19:50:39] Blanking: VID_00168 (24 of 97)
- [19:50:39] Blanking: VID_00169 (25 of 97)
- [19:50:39] Blanking: VID_00170 (26 of 97)
- [19:50:39] Blanking: VID_00171 (27 of 97)
- [19:50:39] Blanking: VID_00172 (28 of 97)
- [19:50:39] Blanking: VID_00173 (29 of 97)
- [19:50:39] Blanking: VID_00174 (30 of 97)
- [19:50:39] Blanking: VID_00175 (31 of 97)
- [19:50:39] Blanking: VID_00176 (32 of 97)
- [19:50:39] Blanking: VID_00177 (33 of 97)
- [19:50:39] Blanking: VID_00178 (34 of 97)
- [19:50:39] Blanking: VID_00179 (35 of 97)
- [19:50:39] Blanking: VID_00180 (36 of 97)
- [19:50:39] Blanking: VID_00181 (37 of 97)
- [19:50:39] Blanking: VID_00182 (38 of 97)
- [19:50:39] Blanking: VID_00183 (39 of 97)
- [19:50:39] Blanking: VID_00184 (40 of 97)
- [19:50:39] Blanking: VID_00185 (41 of 97)
- [19:50:39] Blanking: VID_00186 (42 of 97)
- [19:50:39] Blanking: VID_00187 (43 of 97)
- [19:50:39] Blanking: VID_00188 (44 of 97)
- [19:50:39] Blanking: VID_00189 (45 of 97)
- [19:50:39] Blanking: VID_00190 (46 of 97)
- [19:50:39] Blanking: VID_00191 (47 of 97)
- [19:50:39] Processing: VID_00200 (48 of 97)
- [19:50:39] Extracting A/V streams [VID_00200]
- [19:50:44] Reencoding video [VID_00200]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 249 frames
- Bitrate: 1,493 Kbs
- [19:50:44] Reencoding: VID_00200, Pass 1 of 2
- [19:50:47] Reencoding: VID_00200, Pass 2 of 2
- [19:50:51] Video Encode complete
- [19:50:51] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:50:51] Multiplexing M2TS
- [19:50:55] Blanking: VID_00220 (49 of 97)
- [19:50:55] Blanking: VID_00234 (50 of 97)
- [19:50:55] Blanking: VID_00370 (51 of 97)
- [19:50:55] Blanking: VID_00371 (52 of 97)
- [19:50:55] Blanking: VID_00372 (53 of 97)
- [19:50:55] Processing: VID_00600 (54 of 97)
- [19:50:55] Extracting A/V streams [VID_00600]
- [19:50:59] Reencoding video [VID_00600]
- [19:50:59] Keeping original video (no reencode)
- [19:50:59] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:50:59] Multiplexing M2TS
- [19:51:02] Blanking: VID_00601 (55 of 97)
- [19:51:02] Processing: VID_00800 (56 of 97)
- [19:51:03] Extracting A/V streams [VID_00800]
- [19:57:05] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 172,170 frames
- Bitrate: 3,387 Kbs
- [19:57:05] Reencoding: VID_00800, Pass 1 of 2
[19:57:23]PHASE ONE aborted by user requestTIA for any help/suggestions!

[spotswood]

Here's a default BD5 of a movie extras job I just did. This one comes out undersized too. Finished size comes out to 3.73GB, default target is 4.36GB. I tried a Custom Target of 5120GB but the finished size comes out the same at 3.73GB. Very confusing...

[03/30/20] Checking System Settings
- BD-Rebuilder v0.61.05
- Windows Version: 6.2 [9200]
- Working Path Free Space: 284.59GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[03/30/20] Systems Settings Check complete
----------------------
[03/30/20] BD Rebuilder v0.61.05
[09:04:03] Source: JOKER
- Input BD size: 5.13 GB
- Approximate total content: [02:50:29.719]
- Target BD size: 4.36 GB
- Windows Version: 6.2 [9200]
- MOVIE and MENUS mode enabled
- Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[09:04:07] PHASE ONE, Encoding
- [09:04:07] Processing: VID_01007 (1 of 30)
- [09:04:07] Extracting A/V streams [VID_01007]
- [09:04:11] Reencoding video [VID_01007]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 321 frames
- Bitrate: 15,000 Kbs
- [09:04:11] Reencoding: VID_01007, Pass 1 of 2
- [09:04:16] Reencoding: VID_01007, Pass 2 of 2
- [09:04:21] Video Encode complete
- [09:04:21] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:04:21] Multiplexing M2TS
- [09:04:26] Blanking: VID_01063 (2 of 30)
- [09:04:26] Blanking: VID_01065 (3 of 30)
- [09:04:26] Blanking: VID_01066 (4 of 30)
- [09:04:26] Blanking: VID_01067 (5 of 30)
- [09:04:26] Blanking: VID_01068 (6 of 30)
- [09:04:26] Blanking: VID_01069 (7 of 30)
- [09:04:26] Blanking: VID_01070 (8 of 30)
- [09:04:26] Blanking: VID_01071 (9 of 30)
- [09:04:26] Blanking: VID_01072 (10 of 30)
- [09:04:26] Blanking: VID_01073 (11 of 30)
- [09:04:26] Blanking: VID_01074 (12 of 30)
- [09:04:26] Blanking: VID_01075 (13 of 30)
- [09:04:26] Blanking: VID_01076 (14 of 30)
- [09:04:26] Blanking: VID_01086 (15 of 30)
- [09:04:26] Blanking: VID_01206 (16 of 30)
- [09:04:26] Blanking: VID_01218 (17 of 30)
- [09:04:26] Blanking: VID_01223 (18 of 30)
- [09:04:26] Blanking: VID_01224 (19 of 30)
- [09:04:26] Blanking: VID_01225 (20 of 30)
- [09:04:27] Processing: VID_01227 (21 of 30)
- [09:04:27] Extracting A/V streams [VID_01227]
- [09:04:34] Reencoding video [VID_01227]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,052 frames
- Bitrate: 15,000 Kbs
- [09:04:34] Reencoding: VID_01227, Pass 1 of 2
- [09:05:02] Reencoding: VID_01227, Pass 2 of 2
- [09:05:38] Video Encode complete
- [09:05:38] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:05:38] Multiplexing M2TS
- [09:05:44] Processing: VID_01228 (22 of 30)
- [09:05:44] Extracting A/V streams [VID_01228]
- [09:06:41] Reencoding video [VID_01228]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 32,253 frames
- Bitrate: 15,000 Kbs
- [09:06:41] Reencoding: VID_01228, Pass 1 of 2
- [09:14:29] Reencoding: VID_01228, Pass 2 of 2
- [09:24:48] Video Encode complete
- [09:24:48] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:24:48] Multiplexing M2TS
- [09:25:33] Processing: VID_01229 (23 of 30)
- [09:25:33] Extracting A/V streams [VID_01229]
- [09:25:43] Reencoding video [VID_01229]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 3,955 frames
- Bitrate: 15,000 Kbs
- [09:25:43] Reencoding: VID_01229, Pass 1 of 2
- [09:26:34] Reencoding: VID_01229, Pass 2 of 2
- [09:27:40] Video Encode complete
- [09:27:40] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:27:40] Multiplexing M2TS
- [09:27:48] Processing: VID_01230 (24 of 30)
- [09:27:48] Extracting A/V streams [VID_01230]
- [09:28:01] Reencoding video [VID_01230]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 4,425 frames
- Bitrate: 15,000 Kbs
- [09:28:01] Reencoding: VID_01230, Pass 1 of 2
- [09:29:02] Reencoding: VID_01230, Pass 2 of 2
- [09:30:16] Video Encode complete
- [09:30:16] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:30:16] Multiplexing M2TS
- [09:30:26] Processing: VID_01231 (25 of 30)
- [09:30:26] Extracting A/V streams [VID_01231]
- [09:30:30] Reencoding video [VID_01231]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 120 frames
- Bitrate: 10,715 Kbs
- [09:30:30] Reencoding: VID_01231, Pass 1 of 2
- [09:30:31] Reencoding: VID_01231, Pass 2 of 2
- [09:30:33] Video Encode complete
- [09:30:33] Processing audio tracks
- [09:30:33] Multiplexing M2TS
- [09:30:37] Processing: VID_01232 (26 of 30)
- [09:30:37] Extracting A/V streams [VID_01232]
- [09:30:43] Reencoding video [VID_01232]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,500 frames
- Bitrate: 15,000 Kbs
- [09:30:43] Reencoding: VID_01232, Pass 1 of 2
- [09:31:03] Reencoding: VID_01232, Pass 2 of 2
- [09:31:25] Video Encode complete
- [09:31:25] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:31:25] Multiplexing M2TS
- [09:31:30] Processing: VID_01233 (27 of 30)
- [09:31:30] Extracting A/V streams [VID_01233]
- [09:31:36] Reencoding video [VID_01233]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,440 frames
- Bitrate: 15,000 Kbs
- [09:31:36] Reencoding: VID_01233, Pass 1 of 2
- [09:31:55] Reencoding: VID_01233, Pass 2 of 2
- [09:32:16] Video Encode complete
- [09:32:16] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:32:16] Multiplexing M2TS
- [09:32:22] Processing: VID_01234 (28 of 30)
- [09:32:22] Extracting A/V streams [VID_01234]
- [09:32:29] Reencoding video [VID_01234]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,440 frames
- Bitrate: 15,000 Kbs
- [09:32:29] Reencoding: VID_01234, Pass 1 of 2
- [09:32:48] Reencoding: VID_01234, Pass 2 of 2
- [09:33:08] Video Encode complete
- [09:33:08] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:33:08] Multiplexing M2TS
- [09:33:14] Processing: VID_01235 (29 of 30)
- [09:33:14] Extracting A/V streams [VID_01235]
- [09:33:20] Reencoding video [VID_01235]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,440 frames
- Bitrate: 12,503 Kbs
- [09:33:20] Reencoding: VID_01235, Pass 1 of 2
- [09:33:34] Reencoding: VID_01235, Pass 2 of 2
- [09:33:50] Video Encode complete
- [09:33:50] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:33:50] Multiplexing M2TS
- [09:33:55] Processing: VID_01236 (30 of 30)
- [09:33:55] Extracting A/V streams [VID_01236]
- [09:33:59] Reencoding video [VID_01236]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 120 frames
- Bitrate: 10,715 Kbs
- [09:33:59] Reencoding: VID_01236, Pass 1 of 2
- [09:34:00] Reencoding: VID_01236, Pass 2 of 2
- [09:34:02] Video Encode complete
- [09:34:02] Processing audio tracks
- [09:34:02] Multiplexing M2TS
[09:34:06]PHASE ONE complete
[09:34:06]PHASE TWO - Rebuild Started
- [09:34:06] Rebuilding BD file Structure
[09:34:07] - Encode and Rebuild complete
- WORKFILES folder removed.
[09:34:08] JOB: JOKER finished.
Custom Target 5120GB. Finished file size is still 3.73GB even though the target size is larger???
----------------------
[03/30/20] BD Rebuilder v0.61.05
[10:17:20] Source: JOKER
- Input BD size: 5.13 GB
- Approximate total content: [02:50:29.719]
- Target BD size: 5.00 GB
- Windows Version: 6.2 [9200]
- MOVIE and MENUS mode enabled
- Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[10:17:20] PHASE ONE, Encoding
- [10:17:20] Processing: VID_01007 (1 of 30)
- [10:17:20] Extracting A/V streams [VID_01007]
- [10:17:24] Reencoding video [VID_01007]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 321 frames
- Bitrate: 15,000 Kbs
- [10:17:24] Reencoding: VID_01007, Pass 1 of 2
- [10:17:29] Reencoding: VID_01007, Pass 2 of 2
- [10:17:34] Video Encode complete
- [10:17:34] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:17:34] Multiplexing M2TS
- [10:17:38] Blanking: VID_01063 (2 of 30)
- [10:17:38] Blanking: VID_01065 (3 of 30)
- [10:17:38] Blanking: VID_01066 (4 of 30)
- [10:17:38] Blanking: VID_01067 (5 of 30)
- [10:17:38] Blanking: VID_01068 (6 of 30)
- [10:17:38] Blanking: VID_01069 (7 of 30)
- [10:17:38] Blanking: VID_01070 (8 of 30)
- [10:17:38] Blanking: VID_01071 (9 of 30)
- [10:17:38] Blanking: VID_01072 (10 of 30)
- [10:17:38] Blanking: VID_01073 (11 of 30)
- [10:17:38] Blanking: VID_01074 (12 of 30)
- [10:17:38] Blanking: VID_01075 (13 of 30)
- [10:17:38] Blanking: VID_01076 (14 of 30)
- [10:17:38] Blanking: VID_01086 (15 of 30)
- [10:17:38] Blanking: VID_01206 (16 of 30)
- [10:17:38] Blanking: VID_01218 (17 of 30)
- [10:17:38] Blanking: VID_01223 (18 of 30)
- [10:17:38] Blanking: VID_01224 (19 of 30)
- [10:17:38] Blanking: VID_01225 (20 of 30)
- [10:17:38] Processing: VID_01227 (21 of 30)
- [10:17:38] Extracting A/V streams [VID_01227]
- [10:17:45] Reencoding video [VID_01227]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,052 frames
- Bitrate: 15,000 Kbs
- [10:17:45] Reencoding: VID_01227, Pass 1 of 2
- [10:18:12] Reencoding: VID_01227, Pass 2 of 2
- [10:18:48] Video Encode complete
- [10:18:48] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:18:48] Multiplexing M2TS
- [10:18:54] Processing: VID_01228 (22 of 30)
- [10:18:54] Extracting A/V streams [VID_01228]
- [10:19:42] Reencoding video [VID_01228]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 32,253 frames
- Bitrate: 15,000 Kbs
- [10:19:42] Reencoding: VID_01228, Pass 1 of 2
- [10:27:27] Reencoding: VID_01228, Pass 2 of 2
- [10:37:42] Video Encode complete
- [10:37:42] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:37:42] Multiplexing M2TS
- [10:38:23] Processing: VID_01229 (23 of 30)
- [10:38:23] Extracting A/V streams [VID_01229]
- [10:38:33] Reencoding video [VID_01229]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 3,955 frames
- Bitrate: 15,000 Kbs
- [10:38:33] Reencoding: VID_01229, Pass 1 of 2
- [10:39:24] Reencoding: VID_01229, Pass 2 of 2
- [10:40:30] Video Encode complete
- [10:40:30] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:40:30] Multiplexing M2TS
- [10:40:38] Processing: VID_01230 (24 of 30)
- [10:40:38] Extracting A/V streams [VID_01230]
- [10:40:49] Reencoding video [VID_01230]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 4,425 frames
- Bitrate: 15,000 Kbs
- [10:40:49] Reencoding: VID_01230, Pass 1 of 2
- [10:41:50] Reencoding: VID_01230, Pass 2 of 2
- [10:43:05] Video Encode complete
- [10:43:05] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:43:05] Multiplexing M2TS
- [10:43:13] Processing: VID_01231 (25 of 30)
- [10:43:13] Extracting A/V streams [VID_01231]
- [10:43:17] Reencoding video [VID_01231]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 120 frames
- Bitrate: 12,282 Kbs
- [10:43:17] Reencoding: VID_01231, Pass 1 of 2
- [10:43:19] Reencoding: VID_01231, Pass 2 of 2
- [10:43:20] Video Encode complete
- [10:43:20] Processing audio tracks
- [10:43:20] Multiplexing M2TS
- [10:43:24] Processing: VID_01232 (26 of 30)
- [10:43:24] Extracting A/V streams [VID_01232]
- [10:43:31] Reencoding video [VID_01232]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,500 frames
- Bitrate: 15,000 Kbs
- [10:43:31] Reencoding: VID_01232, Pass 1 of 2
- [10:43:50] Reencoding: VID_01232, Pass 2 of 2
- [10:44:12] Video Encode complete
- [10:44:12] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:44:12] Multiplexing M2TS
- [10:44:18] Processing: VID_01233 (27 of 30)
- [10:44:18] Extracting A/V streams [VID_01233]
- [10:44:24] Reencoding video [VID_01233]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,440 frames
- Bitrate: 15,000 Kbs
- [10:44:24] Reencoding: VID_01233, Pass 1 of 2
- [10:44:43] Reencoding: VID_01233, Pass 2 of 2
- [10:45:04] Video Encode complete
- [10:45:04] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:45:04] Multiplexing M2TS
- [10:45:08] Processing: VID_01234 (28 of 30)
- [10:45:08] Extracting A/V streams [VID_01234]
- [10:45:15] Reencoding video [VID_01234]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,440 frames
- Bitrate: 15,000 Kbs
- [10:45:15] Reencoding: VID_01234, Pass 1 of 2
- [10:45:34] Reencoding: VID_01234, Pass 2 of 2
- [10:45:55] Video Encode complete
- [10:45:55] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:45:55] Multiplexing M2TS
- [10:46:00] Processing: VID_01235 (29 of 30)
- [10:46:00] Extracting A/V streams [VID_01235]
- [10:46:05] Reencoding video [VID_01235]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,440 frames
- Bitrate: 14,376 Kbs
- [10:46:05] Reencoding: VID_01235, Pass 1 of 2
- [10:46:19] Reencoding: VID_01235, Pass 2 of 2
- [10:46:35] Video Encode complete
- [10:46:35] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:46:35] Multiplexing M2TS
- [10:46:40] Processing: VID_01236 (30 of 30)
- [10:46:40] Extracting A/V streams [VID_01236]
- [10:46:44] Reencoding video [VID_01236]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 120 frames
- Bitrate: 12,282 Kbs
- [10:46:44] Reencoding: VID_01236, Pass 1 of 2
- [10:46:46] Reencoding: VID_01236, Pass 2 of 2
- [10:46:47] Video Encode complete
- [10:46:47] Processing audio tracks
- [10:46:47] Multiplexing M2TS
[10:46:51]PHASE ONE complete
[10:46:51]PHASE TWO - Rebuild Started
- [10:46:51] Rebuilding BD file Structure
[10:46:52] - Encode and Rebuild complete
- WORKFILES folder removed.
[10:46:52] JOB: JOKER finished.

[Mike-uk]

heres my rocky, but with DTS audio, end result 7.4 gig, video 5.81 gig, audio 1.2gig

also your 31 gig file holds 6 hours of content, wow

03/30/20] BD Rebuilder v0.61.05
[14:26:54] Source: Rocky
- Input BD size: 21.05 GB
- Approximate total content: [01:59:54.353]
- Target BD size: 7.84 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[14:26:56] PHASE ONE, Encoding
- [14:26:56] Processing: VID_00002 (1 of 2)
- [14:26:56] Extracting A/V streams [VID_00002]
- [14:29:57] Reencoding video [VID_00002]
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 172,032 frames
- Bitrate: 6,684 Kbs
- [14:29:57] Reencoding: VID_00002, Pass 1 of 2
- [14:56:43] Reencoding: VID_00002, Pass 2 of 2
- [15:47:10] Video Encode complete
- [15:47:10] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [15:47:10] Multiplexing M2TS
- [15:47:24] Processing: VID_00011 (2 of 2)
- [15:47:24] Extracting A/V streams [VID_00011]
- [15:47:29] Reencoding video [VID_00011]
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 216 frames
- Bitrate: 4,479 Kbs
- [15:47:29] Reencoding: VID_00011, Pass 1 of 2
- [15:47:31] Reencoding: VID_00011, Pass 2 of 2
- [15:47:34] Video Encode complete
- [15:47:34] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [15:47:34] Multiplexing M2TS
[15:47:38]PHASE ONE complete
[15:47:38]PHASE TWO - Rebuild Started
- [15:47:38] Rebuilding BD file Structure
[15:47:38] - Encode and Rebuild complete
[15:47:38] JOB: Rocky finished.

[spotswood]

heres my rocky, but with DTS audio, end result 7.4 gig, video 5.81 gig, audio 1.2gig

also your 31 gig file holds 6 hours of content, wow...Looks like you used Decoding/Frame serving: DGDecNV. I'll try another and keep the DTS core and report back. And yes, the disc has LOTS of extras... :)

[spotswood]

OK, here's another Rocky default BD9 w/DTS and DGDecNV. File size finished at 6.35GB, same as before. Something's weird...

----------------------
[03/30/20] BD Rebuilder v0.61.05
[14:44:18] Source: ROCKY
- Input BD size: 31.39 GB
- Approximate total content: [06:16:13.383]
- Target BD size: 7.84 GB
- Windows Version: 6.2 [9200]
- MOVIE and MENUS mode enabled
- Auto Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: DGDecNV [4-way]
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[14:44:18] PHASE ONE, Encoding
- [14:44:18] Processing: VID_00020 (1 of 99)
- [14:44:18] Extracting A/V streams [VID_00020]
- [14:44:29] Reencoding video [VID_00020]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,740 frames
- Bitrate: 8,694 Kbs
- [14:44:29] Reencoding: VID_00020, Pass 1 of 2
- [14:44:44] Reencoding: VID_00020, Pass 2 of 2
- [14:45:07] Video Encode complete
- [14:45:07] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [14:45:07] Multiplexing M2TS
- [14:45:11] Blanking: VID_00070 (2 of 99)
- [14:45:11] Blanking: VID_00121 (3 of 99)
- [14:45:11] Blanking: VID_00122 (4 of 99)
- [14:45:11] Blanking: VID_00123 (5 of 99)
- [14:45:11] Blanking: VID_00131 (6 of 99)
- [14:45:11] Blanking: VID_00133 (7 of 99)
- [14:45:11] Blanking: VID_00151 (8 of 99)
- [14:45:11] Blanking: VID_00152 (9 of 99)
- [14:45:11] Blanking: VID_00153 (10 of 99)
- [14:45:11] Blanking: VID_00154 (11 of 99)
- [14:45:11] Blanking: VID_00155 (12 of 99)
- [14:45:11] Blanking: VID_00156 (13 of 99)
- [14:45:11] Blanking: VID_00157 (14 of 99)
- [14:45:11] Blanking: VID_00158 (15 of 99)
- [14:45:11] Blanking: VID_00159 (16 of 99)
- [14:45:11] Blanking: VID_00160 (17 of 99)
- [14:45:11] Blanking: VID_00161 (18 of 99)
- [14:45:11] Blanking: VID_00162 (19 of 99)
- [14:45:11] Blanking: VID_00163 (20 of 99)
- [14:45:11] Blanking: VID_00164 (21 of 99)
- [14:45:11] Blanking: VID_00165 (22 of 99)
- [14:45:11] Blanking: VID_00166 (23 of 99)
- [14:45:11] Blanking: VID_00167 (24 of 99)
- [14:45:11] Blanking: VID_00168 (25 of 99)
- [14:45:11] Blanking: VID_00169 (26 of 99)
- [14:45:11] Blanking: VID_00170 (27 of 99)
- [14:45:11] Blanking: VID_00171 (28 of 99)
- [14:45:11] Blanking: VID_00172 (29 of 99)
- [14:45:11] Blanking: VID_00173 (30 of 99)
- [14:45:11] Blanking: VID_00174 (31 of 99)
- [14:45:11] Blanking: VID_00175 (32 of 99)
- [14:45:11] Blanking: VID_00176 (33 of 99)
- [14:45:11] Blanking: VID_00177 (34 of 99)
- [14:45:11] Blanking: VID_00178 (35 of 99)
- [14:45:11] Blanking: VID_00179 (36 of 99)
- [14:45:11] Blanking: VID_00180 (37 of 99)
- [14:45:11] Blanking: VID_00181 (38 of 99)
- [14:45:11] Blanking: VID_00182 (39 of 99)
- [14:45:11] Blanking: VID_00183 (40 of 99)
- [14:45:11] Blanking: VID_00184 (41 of 99)
- [14:45:11] Blanking: VID_00185 (42 of 99)
- [14:45:11] Blanking: VID_00186 (43 of 99)
- [14:45:11] Blanking: VID_00187 (44 of 99)
- [14:45:11] Blanking: VID_00188 (45 of 99)
- [14:45:11] Blanking: VID_00189 (46 of 99)
- [14:45:12] Blanking: VID_00190 (47 of 99)
- [14:45:12] Blanking: VID_00191 (48 of 99)
- [14:45:12] Processing: VID_00200 (49 of 99)
- [14:45:12] Extracting A/V streams [VID_00200]
- [14:45:16] Reencoding video [VID_00200]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 249 frames
- Bitrate: 3,639 Kbs
- [14:45:16] Reencoding: VID_00200, Pass 1 of 2
- [14:45:18] Reencoding: VID_00200, Pass 2 of 2
- [14:45:21] Video Encode complete
- [14:45:21] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [14:45:21] Multiplexing M2TS
- [14:45:25] Blanking: VID_00220 (50 of 99)
- [14:45:25] Blanking: VID_00234 (51 of 99)
- [14:45:25] Blanking: VID_00370 (52 of 99)
- [14:45:25] Blanking: VID_00371 (53 of 99)
- [14:45:25] Blanking: VID_00372 (54 of 99)
- [14:45:25] Processing: VID_00600 (55 of 99)
- [14:45:25] Extracting A/V streams [VID_00600]
- [14:45:29] Reencoding video [VID_00600]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1 frames
- Bitrate: 8,537 Kbs
- [14:45:29] Reencoding: VID_00600, Pass 1 of 2
- [14:45:30] Reencoding: VID_00600, Pass 2 of 2
- [14:45:31] Video Encode complete
- [14:45:31] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [14:45:31] Multiplexing M2TS
- [14:45:34] Blanking: VID_00601 (56 of 99)
- [14:45:34] Processing: VID_00720 (57 of 99)
- [14:45:34] Extracting A/V streams [VID_00720]
- [14:45:39] Reencoding video [VID_00720]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 430 frames
- Bitrate: 5,307 Kbs
- [14:45:39] Reencoding: VID_00720, Pass 1 of 2
- [14:45:44] Reencoding: VID_00720, Pass 2 of 2
- [14:45:52] Video Encode complete
- [14:45:52] Processing audio tracks
- [14:45:52] Multiplexing M2TS
- [14:45:55] Processing: VID_00800 (58 of 99)
- [14:45:55] Extracting A/V streams [VID_00800]
- [14:55:59] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 172,170 frames
- Bitrate: 5,305 Kbs
- [14:55:59] Reencoding: VID_00800, Pass 1 of 2
- [15:12:22] Reencoding: VID_00800, Pass 2 of 2
- [15:45:21] Video Encode complete
- [15:45:21] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [15:45:21] Multiplexing M2TS
- [15:47:12] Blanking: VID_01288 (59 of 99)
- [15:47:12] Blanking: VID_01289 (60 of 99)
- [15:47:12] Blanking: VID_01290 (61 of 99)
- [15:47:12] Blanking: VID_01291 (62 of 99)
- [15:47:12] Blanking: VID_01292 (63 of 99)
- [15:47:12] Blanking: VID_01293 (64 of 99)
- [15:47:12] Blanking: VID_01294 (65 of 99)
- [15:47:12] Blanking: VID_01295 (66 of 99)
- [15:47:12] Blanking: VID_01296 (67 of 99)
- [15:47:12] Blanking: VID_01297 (68 of 99)
- [15:47:12] Blanking: VID_01298 (69 of 99)
- [15:47:12] Blanking: VID_01299 (70 of 99)
- [15:47:12] Blanking: VID_01300 (71 of 99)
- [15:47:12] Blanking: VID_01301 (72 of 99)
- [15:47:12] Blanking: VID_01302 (73 of 99)
- [15:47:12] Blanking: VID_01303 (74 of 99)
- [15:47:12] Blanking: VID_01304 (75 of 99)
- [15:47:12] Blanking: VID_01305 (76 of 99)
- [15:47:12] Blanking: VID_01306 (77 of 99)
- [15:47:12] Blanking: VID_01307 (78 of 99)
- [15:47:12] Blanking: VID_01308 (79 of 99)
- [15:47:12] Blanking: VID_01309 (80 of 99)
- [15:47:12] Blanking: VID_01310 (81 of 99)
- [15:47:12] Blanking: VID_01311 (82 of 99)
- [15:47:12] Blanking: VID_01312 (83 of 99)
- [15:47:12] Blanking: VID_01313 (84 of 99)
- [15:47:13] Blanking: VID_01314 (85 of 99)
- [15:47:13] Blanking: VID_01315 (86 of 99)
- [15:47:13] Blanking: VID_01316 (87 of 99)
- [15:47:13] Blanking: VID_01317 (88 of 99)
- [15:47:13] Blanking: VID_01318 (89 of 99)
- [15:47:13] Blanking: VID_01319 (90 of 99)
- [15:47:13] Blanking: VID_01320 (91 of 99)
- [15:47:13] Blanking: VID_01321 (92 of 99)
- [15:47:13] Blanking: VID_01525 (93 of 99)
- [15:47:13] Blanking: VID_01526 (94 of 99)
- [15:47:13] Blanking: VID_01527 (95 of 99)
- [15:47:13] Blanking: VID_01528 (96 of 99)
- [15:47:13] Blanking: VID_01529 (97 of 99)
- [15:47:13] Blanking: VID_01530 (98 of 99)
- [15:47:13] Blanking: VID_01531 (99 of 99)
[15:47:13]PHASE ONE complete
[15:47:13]PHASE TWO - Rebuild Started
- [15:47:13] Rebuilding BD file Structure
[15:47:17] - Encode and Rebuild complete
- WORKFILES folder removed.
[15:47:17] JOB: ROCKY finished.

[Mike-uk]

what is the file size from the original is vid 00800 ??, maby your source file is of low file size, cos 6 hours on a 31 gig prob means the main movie is of low bitrate and file size to begin with ??

my main file source is vid_00002 is 22 gigs

[Mike-uk]

ohhh whats 4 way ?? - Decoding/Frame serving: DGDecNV [4-way], ive tried enabling multiprossess but I don't see that in my log ?

[spotswood]

what is the file size from the original is vid 00800 ??, maby your source file is of low file size, cos 6 hours on a 31 gig prob means the main movie is of low bitrate and file size to begin with ??

my main file source is vid_00002 is 22 gigsMy VID_00800 is 32GB. DTS-MA 5.1 track, AC3 Mono track, 8 foreign language tracks, 3 commentary tracks. Disc has 12GB of extras. 43.6GB total.

ohhh whats 4 way ?? - Decoding/Frame serving: DGDecNV [4-way], ive tried enabling multiprossess but I don't see that in my log ?From the hiddenopts.txt: MULTIPROCESS=n - Experimental, see http://www.jdobbs.net/freeware/multiprocessing.html

[spotswood]

OK, I decided to start over. Uninstalled BDRB, Avisynth 2.60, LAVFilters 0.65. Re-downloaded and reinstalled everything from the main page.

Here's the last one I did. Movie/Menu's, AC3@640, had to use a custom target of 9472MB (9.25GB) to get a finished file size of 7.67GB which I'm happy with. Still don't understand why everything is coming out so undersized???

----------------------
[03/30/20] BD Rebuilder v0.61.05
[21:33:08] Source: ROCKY
- Input BD size: 31.39 GB
- Approximate total content: [06:16:13.383]
- Target BD size: 9.25 GB
- Windows Version: 6.2 [9200]
- MOVIE and MENUS mode enabled
- Auto Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: DGDecNV [4-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[21:33:08] PHASE ONE, Encoding
- [21:33:08] Blanking: VID_00070 (1 of 97)
- [21:33:08] Blanking: VID_00121 (2 of 97)
- [21:33:08] Blanking: VID_00122 (3 of 97)
- [21:33:08] Blanking: VID_00123 (4 of 97)
- [21:33:08] Blanking: VID_00131 (5 of 97)
- [21:33:08] Blanking: VID_00133 (6 of 97)
- [21:33:08] Blanking: VID_00151 (7 of 97)
- [21:33:08] Blanking: VID_00152 (8 of 97)
- [21:33:08] Blanking: VID_00153 (9 of 97)
- [21:33:09] Blanking: VID_00154 (10 of 97)
- [21:33:09] Blanking: VID_00155 (11 of 97)
- [21:33:09] Blanking: VID_00156 (12 of 97)
- [21:33:09] Blanking: VID_00157 (13 of 97)
- [21:33:09] Blanking: VID_00158 (14 of 97)
- [21:33:09] Blanking: VID_00159 (15 of 97)
- [21:33:09] Blanking: VID_00160 (16 of 97)
- [21:33:09] Blanking: VID_00161 (17 of 97)
- [21:33:09] Blanking: VID_00162 (18 of 97)
- [21:33:09] Blanking: VID_00163 (19 of 97)
- [21:33:09] Blanking: VID_00164 (20 of 97)
- [21:33:09] Blanking: VID_00165 (21 of 97)
- [21:33:09] Blanking: VID_00166 (22 of 97)
- [21:33:09] Blanking: VID_00167 (23 of 97)
- [21:33:09] Blanking: VID_00168 (24 of 97)
- [21:33:09] Blanking: VID_00169 (25 of 97)
- [21:33:09] Blanking: VID_00170 (26 of 97)
- [21:33:09] Blanking: VID_00171 (27 of 97)
- [21:33:09] Blanking: VID_00172 (28 of 97)
- [21:33:09] Blanking: VID_00173 (29 of 97)
- [21:33:09] Blanking: VID_00174 (30 of 97)
- [21:33:09] Blanking: VID_00175 (31 of 97)
- [21:33:09] Blanking: VID_00176 (32 of 97)
- [21:33:09] Blanking: VID_00177 (33 of 97)
- [21:33:09] Blanking: VID_00178 (34 of 97)
- [21:33:09] Blanking: VID_00179 (35 of 97)
- [21:33:09] Blanking: VID_00180 (36 of 97)
- [21:33:09] Blanking: VID_00181 (37 of 97)
- [21:33:09] Blanking: VID_00182 (38 of 97)
- [21:33:09] Blanking: VID_00183 (39 of 97)
- [21:33:09] Blanking: VID_00184 (40 of 97)
- [21:33:09] Blanking: VID_00185 (41 of 97)
- [21:33:09] Blanking: VID_00186 (42 of 97)
- [21:33:09] Blanking: VID_00187 (43 of 97)
- [21:33:09] Blanking: VID_00188 (44 of 97)
- [21:33:09] Blanking: VID_00189 (45 of 97)
- [21:33:09] Blanking: VID_00190 (46 of 97)
- [21:33:09] Blanking: VID_00191 (47 of 97)
- [21:33:09] Processing: VID_00200 (48 of 97)
- [21:33:09] Extracting A/V streams [VID_00200]
- [21:33:14] Reencoding video [VID_00200]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 249 frames
- Bitrate: 5,302 Kbs
- [21:33:14] Reencoding: VID_00200, Pass 1 of 2
- [21:33:16] Reencoding: VID_00200, Pass 2 of 2
- [21:33:19] Video Encode complete
- [21:33:19] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [21:33:20] Multiplexing M2TS
- [21:33:23] Blanking: VID_00220 (49 of 97)
- [21:33:23] Blanking: VID_00234 (50 of 97)
- [21:33:23] Blanking: VID_00370 (51 of 97)
- [21:33:23] Blanking: VID_00371 (52 of 97)
- [21:33:23] Blanking: VID_00372 (53 of 97)
- [21:33:23] Processing: VID_00600 (54 of 97)
- [21:33:23] Extracting A/V streams [VID_00600]
- [21:33:27] Reencoding video [VID_00600]
- [21:33:27] Keeping original video (no reencode)
- [21:33:27] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [21:33:27] Multiplexing M2TS
- [21:33:31] Blanking: VID_00601 (55 of 97)
- [21:33:31] Processing: VID_00800 (56 of 97)
- [21:33:31] Extracting A/V streams [VID_00800]
- [21:39:44] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 172,170 frames
- Bitrate: 7,437 Kbs
- [21:39:44] Reencoding: VID_00800, Pass 1 of 2
- [21:56:46] Reencoding: VID_00800, Pass 2 of 2
- [22:34:27] Video Encode complete
- [22:34:27] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [22:37:01] Multiplexing M2TS
- [22:40:38] Blanking: VID_01288 (57 of 97)
- [22:40:38] Blanking: VID_01289 (58 of 97)
- [22:40:38] Blanking: VID_01290 (59 of 97)
- [22:40:39] Blanking: VID_01291 (60 of 97)
- [22:40:39] Blanking: VID_01292 (61 of 97)
- [22:40:39] Blanking: VID_01293 (62 of 97)
- [22:40:39] Blanking: VID_01294 (63 of 97)
- [22:40:39] Blanking: VID_01295 (64 of 97)
- [22:40:39] Blanking: VID_01296 (65 of 97)
- [22:40:39] Blanking: VID_01297 (66 of 97)
- [22:40:39] Blanking: VID_01298 (67 of 97)
- [22:40:39] Blanking: VID_01299 (68 of 97)
- [22:40:39] Blanking: VID_01300 (69 of 97)
- [22:40:39] Blanking: VID_01301 (70 of 97)
- [22:40:39] Blanking: VID_01302 (71 of 97)
- [22:40:39] Blanking: VID_01303 (72 of 97)
- [22:40:39] Blanking: VID_01304 (73 of 97)
- [22:40:39] Blanking: VID_01305 (74 of 97)
- [22:40:39] Blanking: VID_01306 (75 of 97)
- [22:40:39] Blanking: VID_01307 (76 of 97)
- [22:40:39] Blanking: VID_01308 (77 of 97)
- [22:40:39] Blanking: VID_01309 (78 of 97)
- [22:40:39] Blanking: VID_01310 (79 of 97)
- [22:40:39] Blanking: VID_01311 (80 of 97)
- [22:40:39] Blanking: VID_01312 (81 of 97)
- [22:40:39] Blanking: VID_01313 (82 of 97)
- [22:40:39] Blanking: VID_01314 (83 of 97)
- [22:40:39] Blanking: VID_01315 (84 of 97)
- [22:40:39] Blanking: VID_01316 (85 of 97)
- [22:40:39] Blanking: VID_01317 (86 of 97)
- [22:40:39] Blanking: VID_01318 (87 of 97)
- [22:40:39] Blanking: VID_01319 (88 of 97)
- [22:40:39] Blanking: VID_01320 (89 of 97)
- [22:40:39] Blanking: VID_01321 (90 of 97)
- [22:40:39] Blanking: VID_01525 (91 of 97)
- [22:40:39] Blanking: VID_01526 (92 of 97)
- [22:40:39] Blanking: VID_01527 (93 of 97)
- [22:40:39] Blanking: VID_01528 (94 of 97)
- [22:40:39] Blanking: VID_01529 (95 of 97)
- [22:40:39] Blanking: VID_01530 (96 of 97)
- [22:40:39] Blanking: VID_01531 (97 of 97)
[22:40:39]PHASE ONE complete
[22:40:39]PHASE TWO - Rebuild Started
- [22:40:39] Rebuilding BD file Structure
[22:40:48] - Encode and Rebuild complete
- WORKFILES folder removed.
[22:40:48] JOB: ROCKY finished.

[Mike-uk]

hmm odd not sure whats going on there then at a target size of 7.8 your getting a bitrate of 5.300 yet I get 6.680

I have multiprosess at 1, but don't see the 4 way in my log

[spotswood]

hmm odd not sure whats going on there then at a target size of 7.8 your getting a bitrate of 5.300 yet I get 6.680I don't know, I'm stumped. If jdobbs can come up with anything then great. I'm happy with the last one I did so I'll chalk it up to an anomaly and leave it at that.

I have multiprosess at 1, but don't see the 4 way in my logWith BDRB open, click on File>View/Edit Config file. Copy/paste MULTIPROCESS=1 above [Paths] like this then save. Make sure spelling is correct. You do have a multi-core processor, right?

MULTIPROCESS=1
[Paths]

[Mike-uk]

With BDRB open, click on File>View/Edit Config file. Copy/paste MULTIPROCESS=1 above [Paths] like this then save. Make sure spelling is correct. You do have a multi-core processor, right?

MULTIPROCESS=1
[Paths]

oh wow cheers, hmm ok so just changing the hiddenops.txt doesn't activate multiprosess, you have to add it in bdrebuilder also, hmm not seen that documented anywhere and I spent prob an hour searching 2 way 4 way on the net and only came across a post that said you need to edit the hiddenops to activate it

lol only after do I read the top text "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." DOH, I thought it read the settings from that txt file and thinking I had multithread on, OMG the amount of time I prob could of saved if it was realy on "cry"

[jdobbs]

I don't know, I'm stumped. If jdobbs can come up with anything then great. I'm happy with the last one I did so I'll chalk it up to an anomaly and leave it at that.

With BDRB open, click on File>View/Edit Config file. Copy/paste MULTIPROCESS=1 above [Paths] like this then save. Make sure spelling is correct. You do have a multi-core processor, right?

MULTIPROCESS=1
[Paths]Can you post the contents of your INI so I can see if there is anything that might cause your odd bitrates?

[MrVideo]

oh wow cheers, hmm ok so just changing the hiddenops.txt doesn't activate multiprosess, you have to add it in bdrebuilder also, hmm not seen that documented anywhere
Actually, how hiddenopts.txt works is explained. You just need to go back to the start of this thread and look thru the posts. Also, the first few lines of the file explain it as well.

[Mike-uk]

yes I know now :p

lol only after do I read the top text "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." DOH, I thought it read the settings from that txt file and thinking I had multithread on, OMG the amount of time I prob could of saved if it was realy on "cry"

[spotswood]

Can you post the contents of your INI so I can see if there is anything that might cause your odd bitrates?Here ya go...

[Options]
VERSION=0.61.0.5
ENCODER=0
MODE=1
ENCODE_QUALITY=2
ONEPASS_ENCODING=0
AUTO_QUALITY=1
TARGET_SIZE=8032
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=3
AVCHD=0
REMOVE_WORKFILES=1
REMOVE_OUTPUT=1
USE_FILTERS=0
BDMV_CERT_ONLY=1
IVTC_PULLDOWN=0
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=9472
MOVIE_ONLY_LOOP=0
ENABLE_TEST=1
ENABLE_BLANKING=1
BLANK_THRESHOLD=1800
MULTIPROCESS=1
AUTO_BIAS=2
AUTO_TWOPASSONLY=1
BEEP_SOUNDFILE=C:\Windows\Media\tada.wav
[Paths]
SOURCE_PATH=M:\
WORKING_PATH=I:\ROCKY_BD9\
DGIndexNV=C:\Users\eM3\Downloads\dgdecnv2053\x32 Binaries\DGIndexNV.exe
DGDecNV=C:\Users\eM3\Downloads\dgdecnv2053\x32 Binaries\DGDecodeNV.dll

[jdobbs]

@spotswood

I've been looking at your log in this post (https://forum.doom9.org/showthread.php?p=1905723#post1905723). It looks like the reason your bitrate is dropping on "Rocky" is because you'd set a target size that is greater than 8500. When BD-RB sees that, it assumes you are writing to something larger than a DVD-R. So, it removes the restrictions. One of the restrictions is that large audio streams are reencoded to AC3. You'll notice that in the first log you see this: - [22:18:17] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...for your first encode, while you see this: - [19:50:51] Processing audio tracks
- Track 4352 (eng): Keeping original audio in your second log. The bitrate is dropping because you have your audio settings set to not reencode to AC3. When outputting to DVD-R, the audio is always reencoded because of output disc size. Setting the target above 8500 tells BD-RB you aren't using DVD-R.


In your second example (https://forum.doom9.org/showthread.php?p=1905724#post1905724) (outputting to DVD-5) you are undersizing because BD-RB reached the maximum bitrate that can be used on a DVD-R: - [09:04:34] Reencoding video [VID_01227]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,052 frames
- Bitrate: 15,000 Kbs There's nothing BD-RB can do about that, because increasing the bitrate would very likely make the disc unplayable by violating the DVD-R's maximum bitrate standard.

[FilipeAmadeuO]

Hi jdobbs
Any chance to add a hidden option in order for BDRebuilder to Extract A/V streams from all M2TS (and when finished) then Multiplexing all M2TS file instead of doing Extracting A/V streams (M2TS_1) -> Multiplexing M2TS file (M2TS_1) -> Extracting A/V streams (M2TS_2) -> Multiplexing M2TS file (M2TS_2) ?
I am replacing subtitles sup files from others with different languague and it would help (or else i have to do Multiplexing M2TS file twice)

[spotswood]

@spotswood

I've been looking at your log in this post (https://forum.doom9.org/showthread.php?p=1905723#post1905723). It looks like the reason your bitrate is dropping on "Rocky" is because you'd set a target size that is greater than 8500. When BD-RB sees that, it assumes you are writing to something larger than a DVD-R. So, it removes the restrictions. One of the restrictions is that large audio streams are reencoded to AC3. You'll notice that in the first log you see this: - [22:18:17] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...

Yes, in my first log (default BD9) I chose to re-encode to AC3 because the main track is DTS-MA 5.1 (way overkill for this title, even at BD25). This came out undersized at 6.35GB. This was the main point of my first post, why was the default BD9 setting coming out so undersized, and why I tried to increase the target size in the second one.

...while you see this in your second log: - [19:50:51] Processing audio tracks
- Track 4352 (eng): Keeping original audio The bitrate is dropping because you have your audio settings set to not reencode to AC3. When outputting to DVD-R, the audio is always reencoded because of output disc size. Setting the target above 8500 tells BD-RB you aren't using DVD-R.

I understand that the audio is reencoded or the core is used for BD5/9 for either Dolby or DTS due to size restrictions. In the second log I chose to keep the DTS core which is why it's "keeping original audio". I also switched to Decoding/Frame serving: DGDecNV hoping for a different outcome, not knowing at the time what happens over 8500. If the restrictions are removed at 8500 the bitrate should increase in my way of thinking. If I'm using a custom target over 8500 there should be no restrictions, but BDRB still thinks I'm using DVD-R/+R and decreases the bitrate?

In your second example (https://forum.doom9.org/showthread.php?p=1905724#post1905724) (outputting to DVD-5) you are undersizing because BD-RB reached the maximum bitrate that can be used on a DVD-R: - [09:04:34] Reencoding video [VID_01227]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,052 frames
- Bitrate: 15,000 Kbs There's nothing BD-RB can do about that, because increasing the bitrate would very likely make the disc unplayable by violating the DVD-R's maximum bitrate standard.With an - Input BD size: 5.09 GB and a - Target BD5 size: 4.36 GB I wouldn't expect BDRB to max out the bitrate at 15,000 Kbs, but I guess this job required it. I'll see what happens with my next job and report back. Thanks for your help...

[spotswood]

Here's the Media Info for my Rocky disc from MPC-HC. I didn't include all the foreign language stuff, just the main movie and DTS-MA 5.1 track. Have a look if that will help troubleshoot the weirdness on this disc. Don't mean to be a PITA or question your software (I've donated a couple times) just trying to figure out why this title comes out so undersized at BD9...

General
Complete name : M:\BDMV\PLAYLIST\00800.mpls
Format : Blu-ray Playlist
File size : 1.37 KiB
Duration : 1 h 59 min
Overall bit rate mode : Variable
Overall bit rate : 2 b/s

Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings, CABAC : Yes
Format settings, RefFrames : 4 frames
Codec ID : 27
Duration : 1 h 59 min
Bit rate mode : Variable
Maximum bit rate : 30.0 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
format_identifier : HDMV
Source : 00800.m2ts

Audio #1
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : DTS
Format/Info : Digital Theater Systems
Format profile : MA / Core
Mode : 16
Format settings, Endianness : Big
Muxing mode : Stream extension
Codec ID : 134
Duration : 1 h 59 min
Bit rate mode : Variable / Constant
Bit rate : Unknown / 1 509 kb/s
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossless / Lossy
Language : English
Source : 00800.m2ts

[Mike-uk]

obviously how you want to encode video and where you store it is your choice, but why are you wanting to squish BD sources onto a DVD in BD format ?? id understand if you were converting BD to DVD (VOB) , 25gig blurays are well cheap

[Emulgator]

spotswood, maybe AUTO_QUALITY=1 was responsible ?

[spotswood]

obviously how you want to encode video and where you store it is your choice, but why are you wanting to squish BD sources onto a DVD in BD format ?? id understand if you were converting BD to DVD (VOB) , 25gig blurays are well cheapBecause I don't burn to disc, I save all my encodes on hard disks, which I access on my computer w/Kodi/MadVR etc. Encoding to BD9 w/lossy audio (for most titles) saves a ton of space without sacrificing picture quality, which is the main point of BDRB. It does an absolutely fantastic job doing this, and I've been using it since it's inception. I also use BD9 just in case I have the need to burn, and those DVD+R DL discs will play on my older Sony Blu-ray player ;^). Of course I use BD25 for newer titles w/7.1 lossless audio (the John Wick series for example) and those encodes are indistinguishable from the originals.

You did Rocky as a BD9 here https://forum.doom9.org/showthread.php?p=1905725#post1905725. Was this just a test or do you encode to BD9 as well?

[Mike-uk]

You did Rocky as a BD9 here https://forum.doom9.org/showthread.php?p=1905725#post1905725. Was this just a test or do you encode to BD9 as well?

ah ok cool, everyone has there preferred method

yes it was just a test as ive never encoded to that size so was just to see what file size I ended up with, I encode to BD25 keeping audio as is, as BD50 discs are horrendously expensive here ( UK ) and I only use verbatim

[jdobbs]

I understand that the audio is reencoded or the core is used for BD5/9 for either Dolby or DTS due to size restrictions. In the second log I chose to keep the DTS core which is why it's "keeping original audio". I also switched to Decoding/Frame serving: DGDecNV hoping for a different outcome, not knowing at the time what happens over 8500. If the restrictions are removed at 8500 the bitrate should increase in my way of thinking. If I'm using a custom target over 8500 there should be no restrictions, but BDRB still thinks I'm using DVD-R/+R and decreases the bitrate? The bitrate is lower because the DTS audio is much, much larger. It has to lower the bitrate to make room for the larger audio.

[Mike-uk]

AS Emulgator said in your ini you have AUTO_QUALITY=1

also you have a few other options that I don't have

ENABLE_TEST=1
AUTO_BIAS=2
AUTO_TWOPASSONLY=1

so not sure if any of thouse options are messing with it

if you did a fresh install of bdrebuilder then I guess thouse options shouldn't be there ??

heres my ini

[Options]
VERSION=0.61.0.5
ENCODER=0
MODE=0
ENCODE_QUALITY=2
ONEPASS_ENCODING=0
AUTO_QUALITY=0
TARGET_SIZE=8032
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=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=3
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=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23500
MOVIEONLY_TYPE=0
ALTCRF=23
ALT_TARGET=1024
ALT_CRF_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
PRIORITY_CLASS=1
QUICK_EXTRAS=0
MULTIPROCESS=2

[Ch3vr0n]

multi-process is a "testing" feature, you need to have that enable_test in there for it to work.

[Mike-uk]

multi-process is a "testing" feature, you need to have that enable_test in there for it to work.

oh ??? I don't have enable test, and I see 2 x264 prosesses with multiprosess 2 ?? also enable_test isn't listed in the hidden ops txt file ?? and even the multiprocess webpage don't mention enable_test, it just says set multiprocess to 1, 2 or 4

[MrVideo]

Because I don't burn to disc, I save all my encodes on hard disks
So why not make MKV files instead? Then you won't have any bitrate issues.

[Mike-uk]

I guess he wants to preserve menues, which ovs MKV wont do

[spotswood]

AS Emulgator said in your ini you have AUTO_QUALITY=1

also you have a few other options that I don't have

ENABLE_TEST=1
AUTO_BIAS=2
AUTO_TWOPASSONLY=1

so not sure if any of thouse options are messing with it. if you did a fresh install of bdrebuilder then I guess thouse options shouldn't be there ??Yes, I did a fresh install of everything, but came out with the same result (undersized BD9), so I added my preferred options back in (and came out with the same result again).

AUTO_QUALITY=1: This is not a hidden option that you add to your .ini. BDRB changes this setting when you enable/disable Auto Quality settings. 0=disabled, 1=enabled. I had Auto Quality enabled in this instance.

ENABLE_TEST=1: https://forum.doom9.org/showthread.php?p=1526277#post1526277. This enables the Movie and Menu's mode and blanking feature allowing you to remove things you don't want like special features etc. Works independently from the MULTIPROCESS setting.

AUTO_BIAS=2: This is explained here (thanks for the link jdobbs... ;^)) https://forum.doom9.org/showthread.php?p=1449851#post1449851

AUTO_TWOPASSONLY=1: This should force two-pass encoding which I prefer and should result in better picture quality. Takes a little longer but my 2700x processor doesn't mind... ;^)
multi-process is a "testing" feature, you need to have that enable_test in there for it to work.MULTIPROCESS takes advantage of multi-core processors, allowing more than one instance of x264 (up to 4) when using DGDecNV or DirectshowSource which significantly speeds up the encoding process. Works independently of the ENABLE_TEST setting. See http://www.jdobbs.net/freeware/multiprocessing.html.

oh ??? I don't have enable test, and I see 2 x264 prosesses with multiprosess 2 ?? also enable_test isn't listed in the hidden ops txt file ?? and even the multiprocess webpage don't mention enable_test, it just says set multiprocess to 1, 2 or 4Actually, you don't need to add ENABLE_TEST for MULTIPROCESS to work. See above...

So why not make MKV files instead? Then you won't have any bitrate issues.What Mike-uk says below... ;^)

I guess he wants to preserve menues, which ovs MKV wont doExactly!

Thanks for chiming in everyone. If any of my explanations/understandings are incorrect, let me know!

[spotswood]

@spotswood

I've been looking at your log in this post (https://forum.doom9.org/showthread.php?p=1905723#post1905723). It looks like the reason your bitrate is dropping on "Rocky" is because you'd set a target size that is greater than 8500. When BD-RB sees that, it assumes you are writing to something larger than a DVD-R. So, it removes the restrictions. One of the restrictions is that large audio streams are reencoded to AC3. You'll notice that in the first log you see this: - [22:18:17] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...for your first encode, while you see this: - [19:50:51] Processing audio tracks
- Track 4352 (eng): Keeping original audio in your second log. The bitrate is dropping because you have your audio settings set to not reencode to AC3. When outputting to DVD-R, the audio is always reencoded because of output disc size. Setting the target above 8500 tells BD-RB you aren't using DVD-R.OK, I've figured it out. It wasn't the audio setting set to not reencode to AC3 that was mucking things up, it was the setting to Keep HD audio for BD25 intact. I normally keep this enabled since it's overridden when encoding to BD5/9, and I don't have to remember to enable it when encoding to BD25. My problem came about when adjusting a custom target size over 8500 MB to compensate for the undersizing I was experiencing (and not understanding what happens over that). I got it now...

As you explain, at 8501 MB the BD5/9 restrictions are lifted and BDRB assumes I am writing to BD25 and keeps the DTS-MA track (or TrueHD/Atmos), rather than reencoding to AC3 like I'm used to, resulting in the very low video bitrates. So my bad everyone. Sorry for taking you on a wild goose chase. I now return you to your regular scheduled "programming".

Stay safe and healthy...

[jdobbs]

OK, I've figured it out. It wasn't the audio setting set to not reencode to AC3 that was mucking things up, it was the setting to Keep HD audio for BD25 intact. I normally keep this enabled since it's overridden when encoding to BD5/9, and I don't have to remember to enable it when encoding to BD25. My problem came about when adjusting a custom target size over 8500 MB to compensate for the undersizing I was experiencing (and not understanding what happens over that). I got it now...

As you explain, at 8501 MB the BD5/9 restrictions are lifted and BDRB assumes I am writing to BD25 and keeps the DTS-MA track (or TrueHD/Atmos), rather than reencoding to AC3 like I'm used to, resulting in the very low video bitrates. So my bad everyone. Sorry for taking you on a wild goose chase. I now return you to your regular scheduled "programming".

Stay safe and healthy...Yeah. The way BD-RB works with audio isn't as obvious as I wish it could be. This post (https://forum.doom9.org/showthread.php?p=1447836#post1447836) goes into depth as to how BD-RB works with the different settings when outputting to DVD-R and BD-R.

[spotswood]

Yeah. The way BD-RB works with audio isn't as obvious as I wish it could be. This post (https://forum.doom9.org/showthread.php?p=1447836#post1447836) goes into depth as to how BD-RB works with the different settings when outputting to DVD-R and BD-R.Thanks for the link. I understand AUTO_BIAS better now too. I've always used High Quality as my default, at the expense of a little more time. I normally start a job (sometimes two) right before I go to bed anyway, setting shutdown after rebuild, and it's all done in the morning. Thanks again!

[AmigaFuture]

Hello,

I noticed what seems like a bug. Select the BD, then export to MKV all lossless. I've repeated this several times and the same result happens. The video is altered or...something is altered in the process. When MKV is made from ripped BD..it looks great, and smooth. After importing the MKV and that is successful I checked IMPORT directory and the resulting BD. That's where the glitch that isn't in the original shows.

There is a video glitch that is not present all the way through the movie. It's like frame are corrupted. JD, I could send you a PM with a link to 2 5MB files so you may check the differences. Audio and subs looks good.

Any thoughts? Suggestions? Shall I send you the link?

----------------------
[04/09/20] BD Rebuilder v0.61.05
[15:55:49] Source: HELLRAISER_JUDGMENT_00000
- Input BD size: 16.38 GB
- Approximate total content: [01:21:09.906]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV, Intact Video, Intact Audio
- Quality: Good (Fastest, BD-25+)
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[15:55:50] PHASE ONE, Encoding
- [15:55:50] Processing: VID_00031 (1 of 1)
- [15:55:50] Extracting A/V streams [VID_00031]
- [16:02:11] Reencoding video [VID_00031]
- [16:02:11] Keeping original video (no reencode)
- [16:02:11] Processing audio tracks
- Track 4352 (eng): Keeping original audio
[16:02:11]PHASE ONE complete
[16:02:11]PHASE TWO - Rebuild Started
- [16:02:11] Building ALTERNATE OUTPUT Structure
[16:10:38] - Encode and Rebuild complete
[16:10:38] JOB: HELLRAISER_JUDGMENT finished.
----------------------
[16:17:59] Importing MKV: HELLRAISER_JUDGMENT
- Collecting audio/video streams from source...
- Building pseudo-BD source structure...
[16:29:01] Video import completed successfully.

[Mike-uk]

have you tried with another source file ?? have you tried the failing file with a different frame server ?

[AmigaFuture]

Yup, X264's internal LAVF and DGDecNV. Both have same results. I have used other BDs, and noticed it. I was making MKV USB HD and then decided to rerender it smaller so I was prepping for DVD-9 to use less space when I checked it. I've not "gone that route" before so I was surprised to see that. My Windows 7 Pro is also also a pretty fresh install.. I installed AviSynth 2.60 but I doubt that's it.

Update: I'll remove it and used 2.58.. That didn't help. Heh.

[jdobbs]

Hello,

I noticed what seems like a bug. Select the BD, then export to MKV all lossless. I've repeated this several times and the same result happens. The video is altered or...something is altered in the process. When MKV is made from ripped BD..it looks great, and smooth. After importing the MKV and that is successful I checked IMPORT directory and the resulting BD. That's where the glitch that isn't in the original shows.

There is a video glitch that is not present all the way through the movie. It's like frame are corrupted. JD, I could send you a PM with a link to 2 5MB files so you may check the differences. Audio and subs looks good.

Any thoughts? Suggestions? Shall I send you the link?I can't imagine how that could even happen. The problem is presented in the imported BD folder after importing an MKV that BD-RB created? Please send me the link -- and also post the contents of your INI so I can see if there is anything that might help identify the cause.

[AmigaFuture]

I can't imagine how that could even happen. The problem is presented in the imported BD folder after importing an MKV that BD-RB created? Please send me the link -- and also post the contents of your INI so I can see if there is anything that might help identify the cause.

I'mmmmm as surprised as you! Okay, was holding on to link until you agreed.

BD to MKV. Nope.
MKV to Import - Yes.

[Options]
VERSION=0.61.0.5
ENCODER=0
MODE=3
ENCODE_QUALITY=5
ENABLE_TEST=1
FORCE_ENCODE=1
MULTIPROCESS=0
IVTC_SELECTION=1
ONEPASS_ENCODING=2
AUTO_QUALITY=0
ENABLE_BLANKING=0
QUICK_EXTRAS=0
TARGET_SIZE=8032
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=all
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=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=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23500
MOVIEONLY_TYPE=28
ALTCRF=23
ALT_TARGET=1024
ALT_CRF_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
[Paths]
WORKING_PATH=O:\OUTPUT\
SOURCE_PATH=O:\OUTPUT\IMPORTS\HELLRAISER_JUDGMENT\
DGIndexNV=C:\Users\User\Desktop\BD_Rebuilder\nVidia\2053\DGIndexNV.exe
DGDecNV=C:\Users\User\Desktop\BD_Rebuilder\nVidia\2053\DGDecodeNV.dll

[musiclover]

Track does not show-up in the stream window
I want to replace the audio track in 00006.m2ts from the bluray 'Script For A Jesters Tear'. But the problem is that BD_RB does not show this track in the stream window. Further problem is that this track has no stand alone playlist. It shares a playlist with 00004.m2ts, 00005.m2ts and 00007.m2ts. Only 00004.m2ts shows up in BD_RB's stream window. I tried composing the track with tsMuxer and replacing it in the STREAM directory but that did not work. How do I get 00006.m2ts to show-up in the stream window so BD_RB can work on it and I can replace the audio track?

I have 'BLANK_THRESHOLD=0' set in the .ini file but 00006.m2ts, 00005.m2ts and 00007.m2ts do not show. The files are 312, 343 and 395 Mb in size.

What do I overlook? How can I get it to work?

[CraigWally]

try the following

MIN_M2TS_SIZE=0
MIN_PLAYLIST_MINS=0

[musiclover]

try the following

MIN_M2TS_SIZE=0
MIN_PLAYLIST_MINS=0

Thanks CraigWally for your reaction.
But that did not work either.

[Mike-uk]

demux 0006.m2ts with tsmuxer, demux the file with the track you want, then remux vid from 0006 and the audio from the file you want the audio back to m2ts ??

[musiclover]

demux 0006.m2ts with tsmuxer, demux the file with the track you want, then remux vid from 0006 and the audio from the file you want the audio back to m2ts ??

I tried that already. It does not work because there are more tracks on the same playlist.

I am hoping on a hidden option to show all the streams

[MrVideo]

I tried that already. It does not work because there are more tracks on the same playlist.
Then place 0006 in the muxer and remove an audio track from the list. Add the wanted track and place it in the sequence from which you deleted the audio. Now, when you mux that you'll have the correct number of audio streams. Be sure to keep any and all sub-title streams.

[musiclover]

Then place 0006 in the muxer and remove an audio track from the list. Add the wanted track and place it in the sequence from which you deleted the audio. Now, when you mux that you'll have the correct number of audio streams. Be sure to keep any and all sub-title streams.

That does not work. When I play the updated bluray it skips the track I messed with. Because of that I wanted to make the audio switch in BD_RB so BD_RB could repair the playlist.

Is there a hidden option to make BD_RB list all the tracks in the stream window? Just as it shows all the tracks when I setup for a small target size?

[MrVideo]

That is what the two options that CraigWally posted are supposed to do. No idea why they didn't work.

[SquallMX]

That does not work. When I play the updated bluray it skips the track I messed with. Because of that I wanted to make the audio switch in BD_RB so BD_RB could repair the playlist.

Is there a hidden option to make BD_RB list all the tracks in the stream window? Just as it shows all the tracks when I setup for a small target size?

You need to replace the .clpi files too and fix any discrepancy using BDEdit.

[musiclover]

You need to replace the .clpi files too and fix any discrepancy using BDEdit.

I did replace the .clpi file and there is no discrepancy between the old and new audio file, only a sync difference. And I don't know what must be done with BDEdit. I find that program very difficult to use. Because of that I tried to solve it with BD_RB.

[Domell1]

Hello
sorry for my English
I have a problem with converting to MKV so stubbornly the application forces bdrebuilder settings for blu-ray despite the fact that I do not want to

log
----------------------
[04.27.20] BD Rebuilder v0.61.04
[12:34:50] Source: 07_ZGLOS_SIE_DISC_8_00000
- Input BD size: 22,45 GB
- Approximate total content: [01:43:08.000]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1920x1080, 640Kbs DD5.1
- Quality: Ultra-High (Extremely Slow)
- Automatic cropping of borders enabled
- X264 Tweak(s) enabled
- Decoding/Frame serving: DGDecNV [4-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[12:34:52] PHASE ONE, Encoding
- [12:34:52] Processing: VID_00001 (1 of 1)
- [12:34:52] Extracting A/V streams [VID_00001]
- [12:38:39] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 25,000fps, 154 700 frames
- [12:38:39] Reencoding: VID_00001, Pass 1 of 1
- Analyzing 11,00 30,50 26,31 23,87 23,28 [23,29]

bdrebuilder.ini

[Options]
VERSION=0.61.0.4
ENCODER=0
MODE=3
ENCODE_QUALITY=4
ONEPASS_ENCODING=0
AUTO_QUALITY=0
TARGET_SIZE=24250
MULTIPROCESS=1
AUDIO_TO_KEEP=eng;pol;
SUBS_TO_KEEP=eng;pol;
SD_CONVERT=0
ALTERNATE_BLURAY=1
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=3
AVCHD=0
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=24250
TWEAK_PASS_TWO= --deblock -3:-3 --bframes 9 --b-pyramid strict --ref 5 --no-mbtree --rc-lookahead 60 --aq-mode 2 --merange 32 --me umh --direct auto --subme 9 --partitions all --trellis 2 --psy-rd 1.0:0.05 --no-fast-pskip --mvrange 512
MOVIEONLY_TYPE=10
ALTCRF=23
ALT_TARGET=1024
ALT_CRF_TARGET=6750
ALTMETHOD=3
ALTAUTOCROP=1
[Paths]
SOURCE_PATH=\\NASTS328HOSSA\DOWNLOAD\07 ZGŁOŚ SIĘ (1976-1987) - REKONSTRUKCJA CYFROWA D08\B2507ZGL8SE6688750\07_ZGLOS_SIE_DISC_8\
WORKING_PATH=C:\TEMP\
DGIndexNV=C:\BD\BD_Rebuilder\Tools\x32 Binaries\DGIndexNV.exe
DGDecNV=C:\BD\BD_Rebuilder\Tools\x32 Binaries\DGDecodeNV.dll

and mediainfo output file:

Wideo
Format : AVC
Format/Informacja : Advanced Video Codec
Profil formatu : High@L4.1
Ustawienia formatu : CABAC / 4 Ref Frames
Ustawienia formatu, CABAC : Tak
Ustawienia formatu, poklatkowy : 4 klatki
Rodzaj przepływności : Zmienna
Przwpływność maksymalna : 15,0 Mb/s
Szerokość : 1.508 pikseli
Wysokość : 1.080 pikseli
Proporcje obrazu : 1,396
Szybkość wyświetlania klatek : 25,000 kl/s
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bitów
Rodzaj skanu : Progresywny
Biblioteka zapisująca : x264 core 158 r2984 3759fcb
Ustawienia kodowania : cabac=1 / ref=5 / deblock=1:-3:-3 / analyse=0x3:0x133 / me=umh / subme=9 / psy=1 / psy_rd=1.00:0.05 / mixed_ref=1 / me_range=32 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-3 / threads=24 / lookahead_threads=2 / sliced_threads=0 / slices=4 / nr=0 / decimate=1 / interlaced=fake / bluray_compat=1 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=1 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=1 / keyint=48 / keyint_min=1 / scenecut=40 / intra_refresh=0 / rc_lookahead=48 / rc=crf / mbtree=0 / crf=23.3 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=15000 / vbv_bufsize=15000 / crf_max=0.0 / nal_hrd=vbr / filler=0 / ip_ratio=1.10 / pb_ratio=1.10 / aq=2:1.00

its possible to disable bluray-compat?

even though I set it in x264, twak 0 makes compatible blurk mkv anyway

[jdobbs]

Hello
sorry for my English
I have a problem with converting to MKV so stubbornly the application forces bdrebuilder settings for blu-ray despite the fact that I do not want to

its possible to disable bluray-compat?

even though I set it in x264, twak 0 makes compatible blurk mkv anywayFrom HIDDENOPTS.TXT:
ALTERNATE_BLURAY=n n = 0/1 Default "1", if set to "0" --bluray-compat setting not used for ALTERNATE encodes

[MrVideo]

its possible to disable bluray-compat?
There really is no need. Having the H.264 file with that compile flag will not make the file play any differently than if it was not there.

[Domell1]

From HIDDENOPTS.TXT:
ALTERNATE_BLURAY=n n = 0/1 Default "1", if set to "0" --bluray-compat setting not used for ALTERNATE encodes

thank you for your reply, unfortunately, despite adding the entry to bdrebuilder.ini still doing restrictions (due to the bluray-compat option enabled) and both vbv-bufsize and vbv-maxrate sets rigidly to 15000 and bframes to 3

ps

after removing bdrebuilder.ini from the disk and adding exactly the same options to the newly created bdrebuilder.ini, the bluray-compat option has finally turned off, but still after CRF it introduces restrictions as for AVCHD i.e. vbv-maxrate and vbv-bufsize 15000 and bframes 3 knot that in the case of CRF if there is a dynamic scene, these restrictions reduce the quality of the scenes themselves (instead of e.g. 35Mbps it is only 15Mbps)
adding manually in tweak as if bdrebuilder skips


Ogólne
Pełna ścieżka : C:\Temp\WORKFILES\VID_00000.AVS.3.264
Format : AVC
Format/Informacja : Advanced Video Codec
Rozmiar pliku : 34,2 MiB
Rodzaj całkowitej przepływności bitów : Zmienna
Biblioteka zapisująca : x264 core 158 r2984 3759fcb
Ustawienia kodowania : cabac=1 / ref=4 / deblock=1:-3:-3 / analyse=0x3:0x133 / me=umh / subme=9 / psy=1 / psy_rd=1.00:0.05 /
mixed_ref=1 / me_range=32 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-3 / threads=24 /
lookahead_threads=2 / sliced_threads=0 / slices=4 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 /
b_pyramid=1 / b_adapt=1 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=1 / keyint=48 / keyint_min=1 / scenecut=40 / intra_refresh=0 /
rc_lookahead=48 / rc=crf / mbtree=0 / crf=19.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=15000 / vbv_bufsize=15000 /
crf_max=0.0 / nal_hrd=vbr / filler=0 / ip_ratio=1.10 / pb_ratio=1.10 / aq=1:1.00

do you have any idea?

PS2
to make it more interesting the temp that bdreuiblder uses to find the right CRF for the given size, say that it normally encodes

Ogólne
Pełna ścieżka : C:\Temp\WORKFILES\TEMP.264
Format : AVC
Format/Informacja : Advanced Video Codec
Rozmiar pliku : 65,2 MiB
Rodzaj całkowitej przepływności bitów : Zmienna
Biblioteka zapisująca : x264 core 158 r2984 3759fcb
Ustawienia kodowania : cabac=1 / ref=4 / deblock=1:-3:-3 / analyse=0x3:0x133 / me=umh / subme=9 / psy=1 / psy_rd=1.00:0.05 / mixed_ref=1 / me_range=32 /
chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-3 / threads=24 / lookahead_threads=2 / sliced_threads=0 / slices=4 / nr=0 /
decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=1 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=1 / keyint=24 /
keyint_min=1 / scenecut=40 / intra_refresh=0 / rc_lookahead=24 / rc=crf / mbtree=0 / crf=19.1 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=35000 / vbv_bufsize=30000 /
crf_max=0.0 / nal_hrd=vbr / filler=0 / ip_ratio=1.10 / pb_ratio=1.10 / aq=1:1.00

he understands nothing more

[MrVideo]

thank you for your reply, unfortunately, despite adding the entry to bdrebuilder.ini still doing restrictions (due to the bluray-compat option enabled) and both vbv-bufsize and vbv-maxrate sets rigidly to 15000 and bframes to 3
Why do you care? Are you having issues playing the MKV files?

[Domell1]

Why do you care? Are you having issues playing the MKV files?

I have no problem with playback only as it comes out, for example CRF set 16 on bdrebuilder theoretically uses bitrate up to 15 Mbps (vbv-bufsize and vbv-maxrate ) and at dynamic scenes you should bitrate up to 40Mbps
Temp CRF is ok vbv-bufsize=30000 and vbv-maxrate=35000 (30 and 35Mbps - standard bluray?) but finished encode set vbv-bufsize=15000 and vbv-maxrate=15000 a large discrepancy in encoding

[gg72]

Has FRIMSource and FRIM Encode ("Intel Quicksync") some disadvantages in the quality of the encoded material over the another options as LAVF and FRIMSource?

[panzerdivision1]

I have a problem with importing MKV - I make BD25 from Remux MKV:
If there is an audio delay (1 sec) to the video (I check in mediainfo), after building pseudo-BD structure, the audio will be delayed with 1 sec.
The BD-RB does not take into account the delay time or what is the problem?

I observed the importing procedure step-by-step:
1. Copy the source file to Tempimport folder, there is a few Mb's difference. Why need this? Less compatibility problems during playback?
2. Demux into video, audio, subs.
3. Building pseudo-BD structure
It takes approx. 1 hour.
With TSMuxerGui it takes approx. 20 mins (I think it performs only the 3. step?)
What is the main difference? I just want to know how it's works...

The resulting BD structure cannot be played on my BD player due to blocking, and other playback problems (the MKV compressing method is the problem I think)
I always recompress with BD-RB. Sometimes the pseudo-BD file size will be smaller than the BD25, and the source image bit rate will be larger than it was after rebuilding with BD-RB. This is interesting.

[MrVideo]

The resulting BD structure cannot be played on my BD player due to blocking, and other playback problems (the MKV compressing method is the problem I think)
MKV is a wrapper. It does not do compressing of any sort.

I have no clue as to why the BDRB recoded video won't play correctly on your BD player. If the H.264 video is not recoded, then it might not play correctly. Not all H.264 video provided within MKV files are necessarily recoded correctly, i.e., not Blu-ray compliant.

[gamete]

One question

Is it possible to read a guide for every option ?
Because bdrebuilder is a wonderful software but i have fear that i dont use it in the best way because i dont know the effects if a set all the option on or off

Thanks guys

[MrVideo]

Is it possible to read a guide for every option?
No. Only what is written within the hidden options text file and this thread.

[panzerdivision1]

My wording was bad. Not compress -> only encode to other bitrate.
The MKV is a wrapper as the M2TS.
As you said the Blu-ray compatibility will be the key.

Returning to the other question, I adjusted the audio delay (1 sec) to the movie in directly the TSMuxerGui.
I get the same result with TsMuxerGui as in the BD-RB import function in 1/3 time.
Played in PC I think is OK, but I would still be wondering if the BD-RB does anything else extra, thinking from the longer processing time?

[Emulgator]

pd1:
Your BD_RB log would be helpful to see if BD_RB did demux -> remux or demux -> decode -> reencode -> remux.

[MrVideo]

My wording was bad. Not compress -> only encode to other bitrate.
Encoding is the same thing as compressing, especially if you take the higher bitrate of a Blu-ray file and recode to a lower bitrate, you are definitely compressing.

[ChuckUFarley]

Has "OUTPUT_FOLDER=" been removed as an option in the Config or is it now "OUTPUT_PATH=" like SOURCE_PATH and WORKING_PATH?
I have OUTPUT_FOLDER set and the folder exists, but the final disc still gets dropped in the working folder.

[Ch3vr0n]

Not that i know of, but the output folder needs to exist PRIOR to beginning the encode. BDRB checks for valid paths before encoding.

[ChuckUFarley]

As I said, the folder does exist. It's just ignored.

[AmigaFuture]

One question

Is it possible to read a guide for every option ?
Because bdrebuilder is a wonderful software but i have fear that i dont use it in the best way because i dont know the effects if a set all the option on or off

Thanks guys

Yup, this is it..we're it. Along with DJ commenting. Don't have fear when using it, just practice. :) Depends what you want to do. Most times I don't rerender my BDs to BD25 anymore, I'm keeping backups on Hard Drives. There isn't really a "best way". Sometimes with some discs that only have the movie, I copy them to portable Hard Drives...then I'm able to use my TV, BD Player, or whatever..in Lossless quality. Which beats the digital junk (haha) they offer with my originals.
Practice, play around, report bugs. Ask...but don't forget logs.

Has "OUTPUT_FOLDER=" been removed as an option in the Config or is it now "OUTPUT_PATH=" like SOURCE_PATH and WORKING_PATH?
I have OUTPUT_FOLDER set and the folder exists, but the final disc still gets dropped in the working folder.

How does a program "drop" it in a folder? Haha!
"OUTPUT_FOLDER=p p = Path to a folder to be used for output. e.g. OUTPUT_FOLDER=D:\OUTPUT (it must exist)"
I don't recall it being removed or disabled.

[MrVideo]

in Lossless quality
Sorry, but all blu-ray and UHD video releases are lossy.

[Tyrell63]

v0.61.05

Trying to "rebuild" a whole BD-50 to a BD-25

Here is the error:

[05.21.20] BD Rebuilder v0.61.05
[14:42:16] Source: UNDERWATER
- Input BD size: 39,63 GB
- Approximate total content: [03:02:06.073]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Very Good (Very Fast), ABR
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[14:42:20] PHASE ONE, Encoding
- [14:42:20] Processing: VID_00800 (1 of 14)
- [14:42:20] Extracting A/V streams [VID_00800]
- Extracting video streams [VID_00800]
- Bitstream exception Unknown exception. It does not have to be! Please contact application support team for more information.
- Error in attempt to extract video.
- Bitstream exception Unknown exception. It does not have to be! Please contact application support team for more information.
- Bitstream exception Unknown exception. It does not have to be! Please contact application support team for more information.
[14:42:27] - Failed to retrieve audio, aborted

[MrVideo]

The disc has been decrypted, right?

[ChuckUFarley]

I pulled out a backup INI file and discovered that the "OUTPUT_FOLDER=" needs to be in the [Options] section not [Paths]. I'll test that later tonight.

Is there a setting for imported video files to have subtitles on by default?

[jdobbs]

I pulled out a backup INI file and discovered that the "OUTPUT_FOLDER=" needs to be in the [Options] section not [Paths]. I'll test that later tonight.

Is there a setting for imported video files to have subtitles on by default?You can right click on it after an import and default a subtitle on when you do the encode and/or build.

[ChuckUFarley]

You can right click on it after an import and default a subtitle on when you do the encode and/or build.

That's weird. I kept trying that and it wasn't working. Now it is. I feel stupid.

And yes, "OUTPUT_FOLDER=" needs to be in the [Options] section. That worked fine.

[AmigaFuture]

Sorry, but all blu-ray and UHD video releases are lossy.

This has all been discussed for many years now. Blu-ray/UHD are made with lossy quality, they are compressed (lossy). When you're making a backup of a BD and not reencoding anything, you're making a Lossless copy...just getting rid of extras you don't want.

[TheIceman]

I hope there's an easy answer to this question. And no, I didn't read all 1471 pages in this forum to try and find it.
How do I enable video card (CUDA) acceleration in BDRB? I'm currently using v0.61.05, Win10.

Yes, my PC can handle 4K. Yes, my CUDA acceleration works with other programs like Adobe & FAB. So, what setting do I need to modify in BDRB or its' supporting programs to get this performance advantage???
Using a 2hr 4K file, and encoding to a high quality 25G output: FAB takes about 90mins, BDRB takes 19hrs. I really like BDRB, but the encoding time difference is Huge.

Any advice would be appreciated. Thanks in advance!!

[SquallMX]

I hope there's an easy answer to this question. And no, I didn't read all 1471 pages in this forum to try and find it.
How do I enable video card (CUDA) acceleration in BDRB? I'm currently using v0.61.05, Win10.

Yes, my PC can handle 4K. Yes, my CUDA acceleration works with other programs like Adobe & FAB. So, what setting do I need to modify in BDRB or its' supporting programs to get this performance advantage???
Using a 2hr 4K file, and encoding to a high quality 25G output: FAB takes about 90mins, BDRB takes 19hrs. I really like BDRB, but the encoding time difference is Huge.

Any advice would be appreciated. Thanks in advance!!

BD Rebuilder does not uses CUDA Hardware Acceleration, software encoding provides better quality but is always slower.

[Ch3vr0n]

BDRB doesn't no, because it's basically just a GUI for the command line tools like x264/x265 which DO use the CUDA/NVENC cores

[MrVideo]

BDRB doesn't no, because it's basically just a GUI for the command line tools like x264/x265 which DO use the CUDA/NVENC cores
I've never seen the x264 encoder use my nVidia CUDA GPU. I need a newer card for H.265 encoding.

[jdobbs]

BDRB doesn't no, because it's basically just a GUI for the command line tools like x264/x265 which DO use the CUDA/NVENC coresThat is absolutely false. BD-RB is much, much more than that. But the actual encoding itself is done by X264/X265/FRIM.

[jdobbs]

I've never seen the x264 encoder use my nVidia CUDA GPU. I need a newer card for H.265 encoding. The decoding may (if set properly) uses the CUDA core, but not encoding.

I still have NVIDIA's NVENC on my "to do" list.

[Ch3vr0n]

That is absolutely false. BD-RB is much, much more than that. But the actual encoding itself is done by X264/X265/FRIM.Oh I know it is. No offense meant, I was just simplifying it. That's all. It does a everything but encoding [emoji6]

Sent from my Pixel 3 XL using Tapatalk

[MrVideo]

The decoding may (if set properly) uses the CUDA core, but not encoding.
Yep, it does indeed. The discussion was about encoding. Plus x264 isn't used for decoding.

[Ch3vr0n]

This isn't meant as advertising by any means. Just as a reference, i have many tools in my video processing library (BDRB still being used, before this one even was released, my alternative (Elaborate Byte's "CloneBD" does full hw acc decoding and encoding. Shrinking a full size BD50 to BD25 on my GTX1080 takes me under 15 minutes with it. Though for my 3D discs, nothin beats BDRB (yet :))

@jdobbs if you believe this post is violating your topic in any way. Feel free to edit/remove it.

[DoctorM]

BD RB could encode a disc in 15 minutes if you used the fastest settings. Is CloneBD any good or just fast?

[Michi]

Error "Jaws UHD":

[06.06.20] BD Rebuilder v0.61.05
[12:22:31] Source: JAWS
- Input BD size: 92,75 GB
- Approximate total content: [06:47:49.242]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), CRF
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[12:22:33] PHASE ONE, Encoding
- [12:22:33] Processing: VID_00480 (4 of 18)
- [12:22:33] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00480.meta
- HEVC manual defined fps doesn't equal to stream fps. Change HEVC fps from 59.97 to 59.9401
[12:22:37] - Failed to build structure, aborted

[Ch3vr0n]

BD RB could encode a disc in 15 minutes if you used the fastest settings. Is CloneBD any good or just fast?

For me 15 minutes is on "best quality" with my 1080A. If i select fastest option it's done in around 8 minutes. It's very good, and has an easy to use interface. Though offers less configuration options than BRDB.

Which is why i still use both :)

[Mark_Venture]

Just jumping in late on the NVENC/CUDA discussion... I too have other tools that support it for Decoding/Encoding. They are definitely faster than BD-RB.

With my older Nvidia cards, GPU Accelerated encoding (be it Cuda/NVENC/Qsync/whatever), was faster but didn't look as good. It seemed softer and not as clear. And the bitrates were less even when trying to use the same CRF values, etc.

With my GTX1660ti (newest gen Nvidia hardware encoder) using hardware accelerated in the other tools (like FAB) is definitely faster and for all intents and purposes the output looks as good on my TV as BD-RB. (ok, I never looked frame by frame, blew them up side by side, etc... just talking about what my eyes see on my TV and my tablets)

That being said, I still use BD-RB as my primary app for making "Movie Only" MKV's for Bluray and UHD discs. (I use FAB for the occasional DVD) I just trust it, and its UI and settings are better (more configuration + very nicely laid out). Plus it always works and always gives me great quality which is the most important to me.

Having GPU Accelerated encoding would be a plus, I can certainly understand why some want it. But I'm fine without it if BD-RB keeps working as well as it does!

[MrVideo]

Error "Jaws UHD":

[06.06.20] - HEVC manual defined fps doesn't equal to stream fps. Change HEVC fps from 59.97 to 59.9401

Huh? This movie was shot on film @ 24fps. The frame rate should either be 24 or 23.976. It is hard to get 60fps video from 24fps film and not use 3-2 pulldown. Doing so gains nothing for 24fps movies on Blu-ray and/or UHD

[DoctorM]

I've been away from this forum for a while and I'm seeing discussion of BD RB working with 4k discs, but searching the thread back for the past year, the first post and jdobb's website, I can't figure out what BD RB can and can't do.

Are people converting 4k discs to standard BD format? Can Atmos and other higher type audio tracks be passed to a standard BD?
Can BD RB re-encode 4k discs to a smaller size and output a burnable/playable UHD BD structure?
What happens to HDR in either of these cases?

Sorry if this has been answered, but there doesn't seem to be a resource explaining this. I don't see a setting for an x265 encoder, so I have to assume the output isn't UHD.

Edit: OOOooooh. tsMuxer was actually updated to support UHD structure, HDR, etc. I had no idea there was any development going on.
I had to dig back into the end of 2018 to find out that BD RB can actually shrink a UHD disc. Beautiful... but it would be nice if that info were somewhere like the first post.
Can anyone comment on standalone hardware support for UHD BD25 and BD50? I didn't think that was possible. It would be nice to know what brands/models support it.

[AmigaFuture]

JDobbs, have you found a solution for the imported video becoming corrupted? I've recorded all 8 episodes of "The Secret of Skinwalker Ranch" (not related to the movie) Season 1, after removing commercials I've saved to MKV. There are 8 episodes. A few import fine, but the rest have glitches at chapter points. The MKVs before import are clear, and play through everything well. During Import v0.61.05, I've checked the TEMP directory and also made a copy when it's just about done..and checked with MPC-HC and the video is clean and smooth just like the MKV. It's when it's being added to the BD structure that some videos are altered.

Since I love the new actual evidence presented in this show I decided to make a BD. Which reminded me of the problem previously. I figured I'd check into it more, and I found that if Chapters are included or if not..and BD Rebuilder makes then, some videos are altered. Those are my findings so far. The episodes are in 720p 59.94 FPS.

[DoctorM]

@AmigaFuture - If your source recordings are mpeg2, you might want to try running mpeg2repair on them first.

And a question: Is "Quicker Encode for Extras" supposed to still work even if "force_noencode" is set to 1? Someone gave that advice once as a way to leave the movie untouched and encode the extras to fit the remaining space. It doesn't work for me. All video is left un-re-encoded. (I did make sure not to use x264's LAVF because that can't 1-pass.)

[BuddTX]

Just jumping in late on the NVENC/CUDA discussion...
Having GPU Accelerated encoding would be a plus, I can certainly understand why some want it. But I'm fine without it if BD-RB keeps working as well as it does!


I also was interested in GPU Accelerated encoding, but when JDobbs and other explained that there are fewer "quality" settings, compared to sw encoding, and the "best quality" BD-RB software settings gives a better final video, I am no longer interested in GPU Accelerated encoding.

I have two unused, older i7 pc's, attached to a KVM switch, and let BD-RB crank away at the highest possible settings making MKV files. So it takes 3 days or longer to make 1 MKV file using x265. The results are great, and "my" computer is left to do other things.

Now if they ever come out with GPU Accelerated encoding that offered "insane" High Quality video settings, I might be interested, but that might cost several hundred dollars for a video card, I probably would not be in a huge rush to buy such a graphics card, to get the same results I get now, with just waiting several days. Thanks everyone and JDobbs for explaing this!

[Sharc]

Now if they ever come out with GPU Accelerated encoding that offered "insane" High Quality video settings, I might be interested, but that might cost several hundred dollars for a video card, I probably would not be in a huge rush to buy such a graphics card, to get the same results I get now, with just waiting several days.
... and electric power is so cheap :D

[AmigaFuture]

@AmigaFuture - If your source recordings are mpeg2, you might want to try running mpeg2repair on them first.

A question: Is "Quicker Encode for Extras" supposed to still work even if "force_noencode" is set to 1? Someone gave that advice once as a way to leave the movie untouched and encode the extras to fit the remaining space. It doesn't work for me. All video is left un-re-encoded. (I did make sure not to use x264's LAVF because that can't 1-pass.)

Comcast is transmitting MPEG-4 for HD channels. I have Quick-Encode for Extras enabled almost constantly. Functions very well with BD backups. Imported MKV's from that source aren't being reencoded. I'm now noticing, ahhhh...been a while attempting to "debug" this. That if I rencode some 59.94 files to 29.97 then..imports are great. So, there seems to be a problem that gets by (VideoReDo) TVSuite AND BD-RB (tsMuxer).
Which then also means some movies might not be rendered correctly, or mastering errors (?). I gave JD 2 files a while back, but I know he's been active with other stuff.
HandBreak is a nice replacement for now for encoding then since if I change the Framerate ONLY (to 29.97), and disable all Deinterlacing then it looks really good and plays smooth..and Imports sweetly. I just prefer JD's method because I'm not into all the math for getting MB output size right.

Appreciate the reply.

"x264's LAVF because that can't 1-pass." - It should, or DirectShow. I use these..often. Hmm..

[ChuckUFarley]

Let me correct myself. CRF is disabled with X264's internal LAVF, but ABR is still an option. Since quicker-encode seems to use a CRF value, I would think a different decoder is needed.
I'd just like to know if that's a bug or a feature with force_noencode & quicker encode.

As far as your issue AmigaFuture... dude, I have no idea what you are even trying to do anymore. I figured you were capping OTA content. Since it's Comcast, I have to assume it's not QAM, and by MPEG-4, I'll assume you mean AVC video.

I don't know of a way to clean possible broadcast or encoding bugs under those conditions. I'm not sure there is. It could be a bug in the software you are using to cut the commercials.

[Lathe]

Oh GEEZ...

Sorry guys, but I am like 3 frigg'n MONTHS behind checking this thread, my humble and lowly apologies. My poor ol' PC finally passed on to the Great Beyond and I had to build another one. The good news is that since it has been over 8 years since my last one, this new one now, although I'm sure no where NEAR some of your guys' cutting edge systems, is a HELL of a lot faster and better :) So, I'm looking forward to seeing how long encoding times take now. I've done little snippets, like Conan shows, and using the x264 CMD LN it used to take about 6 minutes to re-encode a file of say 400 Megs to a size of about 60 Megs, and now it takes like 1 1/2 minutes, so that's a good sign :D

I know it isn't as super duper as your guys's stuff, but I now have a nice AMD Ryzen 5 3600, 16 Gigs of RAM, and My Goodness, I thought okay I'll try to get maybe an older generation but used to be cutting edge video card. DAMN! The thing was like half the size of a bloody shoe box! I'd never seen anything so huge (well... except of course in my case... *cough...) I was bloody terrified trying to install it, but fortunately I didn't seem to screw anything up. It is an older Raedon 590x Fat Boy. Oh, and if was just easier to get a new SDD drive, I guess one of the newer M2 generation ones that plugs directly into the MB with the W10 OS on it. That is rather nice too!

Anyway, sorry to go on... So, I went to the first post on this thread to DL all the versions of Avisynth and stuff we need to do, and WTF! The Avisynth links, both of them do not work now...??? I suppose I can just find the Avisynth site, etc., but I thought that was kind of weird. Did some monumental changes occur here since I was gone...? Like...

Is JD doing okay...?

Is Mr. Video still being as anal as ever...?

Is gonca still lusting after the moose of the Great North...?

Any updates that I should know about?

Thanks! http://lathe-of-heaven.com/tiphat.gif

[Lathe]

I guess it was all right, no big deal...

I already had the versions DL'd anyway, so I just used them, it started up fine.

I need to go back over the last 3 months and see what the HELL all of you guys have been up to!

[Lathe]

Hmmm, interesting...

Although definitely running faster on all accounts, the CPU utilization is only about maybe from about 17-19% Weird... It used to use a fair amount of my old CPU, like easily from 80-95%...

[MrVideo]

Is Mr. Video still being as anal as ever...?
Somebody has to. :eek:

[AmigaFuture]

Oh GEEZ...

Sorry guys, but I am like 3 frigg'n MONTHS behind checking this thread, my humble and lowly apologies.

This part where you're so Lowly is still very funny to me.

I know it isn't as super duper as your guys's stuff, but I now have a nice AMD Ryzen 5 3600, 16 Gigs of RAM [...]with the W10 OS on it. That is rather nice too!

I'm looking at the same setup. I'm still enjoying my older ASUS 10+ year system..and it's doing really well, but I want faster speeds with USB, and more. You got your parts around the same time I was considering buying..then..I delayed, so I'm awaiting stock to refill.

Screw OS 10..I won't go there. It's much too ugly a UI. I found plenty of ways to get Window 7 to function. That rocks!

JD doing okay...

I wondered that also, sent a PM..got a reply. :)

Somebody has to. :eek:

Ohhh.. So many comments...


Anyway..

I've found some bugs I'm confirming for 720p.. They all are related to TsMuxer.. Advanced warning. :)

[DoctorM]

@Lathe - Are you using your SSD while encoding? It might wear it out faster, but a spinning platter drive could be a limiting factor. Also, what are you using to decode? On my previous system (FX-8350) I got a 10% bump in performance using x264's internal LAVF versus my vid card. The reason is the internal LAVF is the only way to take advantage of a 64-bit pipe in BD RB. I have to assume a Ryzen 5 would be even better.

@AmigaFuture - Oh, God. I'm glad someone else said it. I'm running two drives with two OS's right now that I swap between. I'm TRYING to ease myself into Win10 and I hate it. It's ugly, bloated and clunky. It'll take forever to root out all the M$ crap and tweak it to function smoothly like Win7.

[gonca]

well... except of course in my case... *cough...
You realize that you were looking in a trick mirror stumpy

[jdobbs]

Is JD doing okay...?Still breathing. I haven't spent as much time on BD-RB as I'd like. My dream is to get a GTX1660 so I can work on NVENC encoding, but the wife seems to think we should concentrate on things like food, fuel, clothing and a roof over our head instead. Women. They just don't understand geek economics, do they?

[gonca]

Women. They just don't understand geek economics, do they?
Careful, you never know who is reading ;)

[DoctorM]

Since force_noencode & quicker encode don't seem to work together, no matter what I fiddle with, is it possible to override the 15000 Kbs max bitrate cap for discs sized under 25GB?
I'm manually re-encoding the extras to a DVD5 and because it's under 25 minutes of content, all the extras are hitting the cap and the disc is undersized.

Edit: Would this work (and is it right)?
TWEAK_PASS_ONE=--vbv-bufsize 30000 --vbv-maxrate 40000
TWEAK_PASS_TWO=--vbv-bufsize 30000 --vbv-maxrate 40000

[jdobbs]

Careful, you never know who is reading ;)Good point. I apologize if I insulted any female geeks.

[LowDead]

Since force_noencode & quicker encode don't seem to work together, no matter what I fiddle with, is it possible to override the 15000 Kbs max bitrate cap for discs sized under 25GB?
I'm manually re-encoding the extras to a DVD5 and because it's under 25 minutes of content, all the extras are hitting the cap and the disc is undersized.

Edit: Would this work (and is it right)?
TWEAK_PASS_ONE=--vbv-bufsize 30000 --vbv-maxrate 40000
TWEAK_PASS_TWO=--vbv-bufsize 30000 --vbv-maxrate 40000

If you go above 15000 Kbs and play on standalone it will most likely stutter. And with 25 minutes of content and the disc resulting in undersizing it probably means the encoder max out the quality anyway so you get the best it can do with these settings.

//LD

Edit: Sorry I misunderstood the first time... Ofcourse the final disc have the movie+extras, and you want to have more bitrat added to the movie? isnt it better to apply the extra bitrate to the extras if the movie already looks good? too avoid any compability issues? It will be fitted to a BD25 in the end so the DVD5 caps doesn't need to be applied.

[laserfan]

Oh GEEZ...

Sorry guys, but I am like 3 frigg'n MONTHS behind checking this thread, my humble and lowly apologies. My poor ol' PC finally passed on to the Great Beyond and I had to build another one. The good news is that since it has been over 8 years since my last one, this new one now, although I'm sure no where NEAR some of your guys' cutting edge systems, is a HELL of a lot faster and better :)

Thanks for posting your tale. In my case its been over FOUR YEARS since my video PC has worked! Loaded with drives of course, and since we moved houses/locations the mobo has refused to come alive. This used to happen when I'd leave it for months in the summer, and it would sometimes balk when re-firing the thing for winter, but now it remains quiet.

I have dreaded the work associated with building a new PC but maybe your experience will inspire me! In the Fall! :)

[musiclover]

@AmigaFuture - If your source recordings are mpeg2, you might want to try running mpeg2repair on them first.

And a question: Is "Quicker Encode for Extras" supposed to still work even if "force_noencode" is set to 1? Someone gave that advice once as a way to leave the movie untouched and encode the extras to fit the remaining space. It doesn't work for me. All video is left un-re-encoded. (I did make sure not to use x264's LAVF because that can't 1-pass.)

See your own post at https://forum.doom9.org/showthread.php?p=1678011

[jdobbs]

Since force_noencode & quicker encode don't seem to work together, no matter what I fiddle with, is it possible to override the 15000 Kbs max bitrate cap for discs sized under 25GB?
I'm manually re-encoding the extras to a DVD5 and because it's under 25 minutes of content, all the extras are hitting the cap and the disc is undersized.

Edit: Would this work (and is it right)?
TWEAK_PASS_ONE=--vbv-bufsize 30000 --vbv-maxrate 40000
TWEAK_PASS_TWO=--vbv-bufsize 30000 --vbv-maxrate 40000The max is based on the maximum transfer rate for a DVD. Trying to increase it will just cause stutter or other issues during playback.

Those tweaks won't work. There are some settings that BD-RB won't allow you to change (to prevent self-inflicted issues).

[DoctorM]

I know what I was doing. It's just that gonca mentioned there was an easier method a while back, and as far as doing separate processing and manually rebuilding the disc, jdobbs did mention he was planning to add a hidden opt. to allow removal the VBV restriction from the pass tweaks. He did add a maxbitrate option for UHD.

My post is 6 years old, musiclover, and 6 years later, neither of these alternatives work, it still has to be done manually.

I tried gonca's method only once back when he originally posted it and I didn't aggressively try adjusting options to see if I could make it work until this week. I don't know if the original intent WAS for that method to work or not, but many updates to BDRB later, I didn't know what to expect.

I'd just like to see the ability to right-click a stream and select 'don't encode'. So maybe someone doesn't want to re-encode the movie like me, or someone else might not want to re-encode a specific bonus feature that's they lover or is already bitrate starved.
It sounds useful to me.

Edit: Again, to be clear, this isn't an attack on anyone. It's just I haven't worked with BD-RB in a while and I'm trying to understand what changes have been made in that time.

[vanille]

hello. i've tried to shrink the BD which i recorded again and again.
but everytime this error message is displayed and i have no choice
but to abort the process.
"BD Rebuilder experienced an error 2008 correctEPData() 00006 2008"
i tried the latest and some old versions on Windows 7(32bit) and Windows 10(64bit).
but i always got the same error message.
could you tell me what i need to do to solve this problem please?

----------------------
[06/06/20] BD Rebuilder v0.61.05
[03:21:59] Source: GONZOU
- Input BD size: 25.96 GB
- Approximate total content: [07:36:56.756]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), CRF
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[03:22:00] PHASE ONE, Encoding
- [03:22:00] Processing: VID_00000 (1 of 1)
- [03:22:00] Extracting A/V streams [VID_00000]
- [03:24:39] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1440x1080
- Rate/Length: 29.970fps, 821,653 frames
- [03:24:39] Performing CRF Prediction...
- Analyzing 17.90 [17.95]
- [03:26:25] Encoding using constant rate factor.
- [05:46:28] Video Encode complete
- [05:46:28] Processing audio tracks
- Track 4352 (und): Keeping original audio
- [05:46:28] Multiplexing M2TS
- [05:49:09] CorrectEPData() 00006 2008
[05:51:51]PHASE ONE aborted by user request

----------------------
[06/09/20] BD Rebuilder v0.61.05
[14:34:59] Source: BD
- Input BD size: 23.82 GB
- Approximate total content: [07:06:25.192]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), CRF
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[14:34:59] PHASE ONE, Encoding
- [14:34:59] Processing: VID_00000 (1 of 1)
- [14:34:59] Extracting A/V streams [VID_00000]
- [14:42:46] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1440x1080
- Rate/Length: 29.970fps, 766,761 frames
- [14:42:46] Performing CRF Prediction...
- Analyzing 17.60 19.50 20.15 [20.15]
- [14:47:50] Encoding using constant rate factor.
- [16:57:44] Video Encode complete
- [16:57:44] Processing audio tracks
- Track 4352 (und): Keeping original audio
- [16:57:44] Multiplexing M2TS
- [17:00:40] CorrectEPData() 00006 2008
[17:53:55]PHASE ONE aborted by user request

[AmigaFuture]

@Lathe - Are you using your SSD while encoding? It might wear it out faster, but a spinning platter drive could be a limiting factor. Also, what are you using to decode? On my previous system (FX-8350) I got a 10% bump in performance using x264's internal LAVF versus my vid card. The reason is the internal LAVF is the only way to take advantage of a 64-bit pipe in BD RB. I have to assume a Ryzen 5 would be even better.

@AmigaFuture - Oh, God. I'm glad someone else said it. I'm running two drives with two OS's right now that I swap between. I'm TRYING to ease myself into Win10 and I hate it. It's ugly, bloated and clunky. It'll take forever to root out all the M$ crap and tweak it to function smoothly like Win7.

Those are some valid points to what I was considering. I'll check Ryzen 5 some..

Oh, Enki, indeed! I do tech stuff for family & others & 10 is not a joy. I don't "hate" but the "Blleech!" is very strong. I've installed it on my system, multiple OS installs..as you, but there isn't any way I'm going to say "Okay." to it. The GUI is my stopper. It's made for Keyboard commandos (not the PEOPLE THAT TYPE LIKE THIS ALL THE TIME). My Son at Intel really doesn't enjoy it either, and he's very much keyboard commando (as little mouse use as possible).

I've heard they've finally removed a lot of bloat. Okay, well, the make it "Look cool again." so I'm not going any time soon. Besides, you're not able to pick updates; like Windows 7. Make a product and then treat customers as products - bad business idea. "Epic Fail!" as the buzz-word jargon says.

Anyway, very interested to know more about how well Ryzen does with BD-RB. I'm think the cores and threads will help a lot. I'd probably not use my GPU as much then, with LAVF handling better. Hmm... I have a couple Samsung SSDs and they're not operating at near full speeds with this ASUS motherboard. So, I'm thinking that'll really be helpful with BD-RB. I don't get into heavy gaming, but sometimes it's fun. Nothing like the "gamers" of today though...many other things to do than sit for 5 to 8+ hours playing video games. Yikes, haha! So a good mix... Hmm.

Good point. I apologize if I insulted any female geeks.

I'm sure the lowly wretch, Lathe, wasn't offended. :D

[vanille]

hello. i've tried to shrink the BD which i recorded again and again.
but everytime this error message is displayed and i have no choice
but to abort the process.
"BD Rebuilder experienced an error 2008 correctEPData() 00006 2008"
i tried the latest and some old versions on Windows 7(32bit) and Windows 10(64bit).
but i always got the same error message.
could you tell me what i need to do to solve this problem please?

----------------------
[06/06/20] BD Rebuilder v0.61.05
[03:21:59] Source: GONZOU
- Input BD size: 25.96 GB
- Approximate total content: [07:36:56.756]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), CRF
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[03:22:00] PHASE ONE, Encoding
- [03:22:00] Processing: VID_00000 (1 of 1)
- [03:22:00] Extracting A/V streams [VID_00000]
- [03:24:39] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1440x1080
- Rate/Length: 29.970fps, 821,653 frames
- [03:24:39] Performing CRF Prediction...
- Analyzing 17.90 [17.95]
- [03:26:25] Encoding using constant rate factor.
- [05:46:28] Video Encode complete
- [05:46:28] Processing audio tracks
- Track 4352 (und): Keeping original audio
- [05:46:28] Multiplexing M2TS
- [05:49:09] CorrectEPData() 00006 2008
[05:51:51]PHASE ONE aborted by user request

----------------------
[06/09/20] BD Rebuilder v0.61.05
[14:34:59] Source: BD
- Input BD size: 23.82 GB
- Approximate total content: [07:06:25.192]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), CRF
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[14:34:59] PHASE ONE, Encoding
- [14:34:59] Processing: VID_00000 (1 of 1)
- [14:34:59] Extracting A/V streams [VID_00000]
- [14:42:46] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1440x1080
- Rate/Length: 29.970fps, 766,761 frames
- [14:42:46] Performing CRF Prediction...
- Analyzing 17.60 19.50 20.15 [20.15]
- [14:47:50] Encoding using constant rate factor.
- [16:57:44] Video Encode complete
- [16:57:44] Processing audio tracks
- Track 4352 (und): Keeping original audio
- [16:57:44] Multiplexing M2TS
- [17:00:40] CorrectEPData() 00006 2008
[17:53:55]PHASE ONE aborted by user request

[gonca]

I know what I was doing. It's just that gonca mentioned there was an easier method a while back, and as far as doing separate processing and manually rebuilding the disc, jdobbs did mention he was planning to add a hidden opt. to allow removal the VBV restriction from the pass tweaks. He did add a maxbitrate option for UHD.

My post is 6 years old, musiclover, and 6 years later, neither of these alternatives work, it still has to be done manually.

I tried gonca's method only once back when he originally posted it and I didn't aggressively try adjusting options to see if I could make it work until this week. I don't know if the original intent WAS for that method to work or not, but many updates to BDRB later, I didn't know what to expect.

I'd just like to see the ability to right-click a stream and select 'don't encode'. So maybe someone doesn't want to re-encode the movie like me, or someone else might not want to re-encode a specific bonus feature that's they lover or is already bitrate starved.
It sounds useful to me.

Edit: Again, to be clear, this isn't an attack on anyone. It's just I haven't worked with BD-RB in a while and I'm trying to understand what changes have been made in that time.

It has been a while, so I am not sure if I meant to use both options together or FORCE_NOENCODE=1 to first strip out unwanted stuff and then Quick Encode extras on the result.
OR one or the other, been a long time

[AmigaFuture]

Update about 720p 59.94 videos.. I've been able to use HandBrake to convert the Secret of Skinwalker Ranch episodes to 23.96 without any filters being used. Just change it to constant framerate and force 23.97 vs 29.97, Pass AC-3 through.. When done making MKV, use MKVToolNix GUI and add SRT (and remove Substation if you don't clear subtitles)...then import into BD-RB and tsMuxer doesn't change anything. Playback of all videos and subs are smooth as can be from sources. Since there isn't an ability, yet, for BD-RB to change framerate this way, none that will complete anyway.. I thought it was a bug with BD-RB, but it's TsMuxer doing it as I downloaded newer and older versions of that to make singe BDs of each episode.

[jdobbs]

I've decided I'm going to buy an NVIDIA card that supports encoding so I can include NVENC support in BD-RB. I'm thinking about a GTX 1660 because it supports B-FRAMES in HEVC encoding and is in the $200~ price range. I was wondering if anyone had experience with this or other cards and could make some recommendations. Any estimates on encoding speeds for AVC and HEVC (including UHD) would be helpful. Thanks in advance.

[Mark_Venture]

I've decided I'm going to buy an NVIDIA card that supports encoding so I can include NVENC support in BD-RB. I'm thinking about a GTX 1660 because it supports B-FRAMES in HEVC encoding and is in the $200~ price range. I was wondering if anyone had experience with this or other cards and could make some recommendations. Any estimates on encoding speeds for AVC and HEVC (including UHD) would be helpful. Thanks in advance.
While not a 1660, I have an EVGA 1660ti https://www.evga.com/products/product.aspx?pn=06G-P4-1267-KR

It works. Using it with FAB, set as “cuda” it is way faster than “software” mode. (When converting a Blu-ray ripped to Hard drive can be converted MKV with Fab & Cuda with CRF20 in about 15 minutes vs BD-RB as Alt-movie only CRF20 in about 45-50 min). And it’s faster than using the intel u630 with my i7-8700k.

I haven’t done UHD to MKV in a while.

Over the next few days I can run some tests and comparisons if you help me understand what would be the best way.

[MrVideo]

Why are you dealing with 720p when 1080p23.976 is available? Especially why are you just converting the frame rate instead of doing a true IVTC? With BDRB, you can pass an AVIsynth script to do the IVTC. Me, I prefer 1080p. But that is me.

[BuddTX]

... and electric power is so cheap :D
My two "extra" pc's are Dell SFF and SSFF (small and extra small) so they really don't use a lot of electricity, except for the i7.

[Mike-uk]

I've decided I'm going to buy an NVIDIA card that supports encoding so I can include NVENC support in BD-RB. I'm thinking about a GTX 1660 because it supports B-FRAMES in HEVC encoding and is in the $200~ price range. I was wondering if anyone had experience with this or other cards and could make some recommendations. Any estimates on encoding speeds for AVC and HEVC (including UHD) would be helpful. Thanks in advance.
Thats realy nice of you, mayby post a link to your donations page and im sure you will not have to bare the full cost of a new card

i have a RTX 2070 super, if you need any tests done just ask and ill try and do them

[jdobbs]

Thats realy nice of you, mayby post a link to your donations page and im sure you will not have to bare the full cost of a new card

i have a RTX 2070 super, if you need any tests done just ask and ill try and do themWent to Amazon and not a single GTX 1660 (of several they sell) is in stock. Looking elsewhere.

[AmigaFuture]

Why are you dealing with 720p when 1080p23.976 is available? Especially why are you just converting the frame rate instead of doing a true IVTC? With BDRB, you can pass an AVIsynth script to do the IVTC. Me, I prefer 1080p. But that is me.

Because BD-RB doesn't reencode the 720p 59.94 to 1080p 23.976. Each attempt, combination I've used always aborts in the attempt. IVTC produces (in WORKFILES) a 720p 59.97/29.97 video stream that's too fast. 2-passes are aborted on 1st pass. If I use CBR it finishes, but this relies on tsMuxeR not altering the video from Import.

HandBrake won't upscale past 720p. I also don't know a script to use to force it to work. BD-RB's upscale aborts immediately after starting.

I don't have a script for the AVS Filter in BD-RB.

Went to Amazon and not a single GTX 1660 (of several they sell) is in stock. Looking elsewhere.

Try https://www.amazon.com/MSI-GeForce-GTX-1660-OC/dp/B07PBLDV3D/ref=sr_1_2?dchild=1&keywords=GTX+1660&qid=1592529742&sr=8-2 then Available from these sellers. I see a lot listed.

[Mike-uk]

jdobbs your donation link just takes me to amazon gift cards, but its not filling in the email address ? what are your donation details ?

[jdobbs]

jdobbs your donation link just takes me to amazon gift cards, but its not filling in the email address ? what are your donation details ?dvd-rb@jdobbs.net

Thanks for thinking about me. Anything helps. I haven't been able to figure out how to automatically fill in the e-mail address in the link.

[jdobbs]

Try https://www.amazon.com/MSI-GeForce-GTX-1660-OC/dp/B07PBLDV3D/ref=sr_1_2?dchild=1&keywords=GTX+1660&qid=1592529742&sr=8-2 then Available from these sellers. I see a lot listed. There's a Microcenter about 1 1/2 hours from where I live that has an MSI GTX-1660 for $219. I'm going to drive up there today and check it out.

[Mike-uk]

do you not have payapl or some other donation where you can get cash out, if you were getting it from amazon then yeh gift card, otherwise the donation is locked to amazon ?

[AmigaFuture]

There's a Microcenter about 1 1/2 hours from where I live that has an MSI GTX-1660 for $219. I'm going to drive up there today and check it out.

Sweet!

do you not have payapl or some other donation where you can get cash out, if you were getting it from amazon then yeh gift card, otherwise the donation is locked to amazon ?

PayPal wouldn't / didn't / couldn't understand BD-RB isn't decrypting discs. He left PayPal because of that.

[Mike-uk]

PayPal wouldn't / didn't / couldn't understand BD-RB isn't decrypting discs. He left PayPal because of that.[/QUOTE]

oh ok :( ill donate a gift card then

and anyone else if BD-rebuilder has helped you, help jdobbs continue to develop and add new features :)

[vanille]

Hello again.
could anybody give me advice please?

hello. i've tried to shrink the BD which i recorded again and again.
but everytime this error message is displayed and i have no choice
but to abort the process.
"BD Rebuilder experienced an error 2008 correctEPData() 00006 2008"
i tried the latest and some old versions on Windows 7(32bit) and Windows 10(64bit).
but i always got the same error message.
could you tell me what i need to do to solve this problem please?

----------------------
[06/06/20] BD Rebuilder v0.61.05
[03:21:59] Source: GONZOU
- Input BD size: 25.96 GB
- Approximate total content: [07:36:56.756]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), CRF
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[03:22:00] PHASE ONE, Encoding
- [03:22:00] Processing: VID_00000 (1 of 1)
- [03:22:00] Extracting A/V streams [VID_00000]
- [03:24:39] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1440x1080
- Rate/Length: 29.970fps, 821,653 frames
- [03:24:39] Performing CRF Prediction...
- Analyzing 17.90 [17.95]
- [03:26:25] Encoding using constant rate factor.
- [05:46:28] Video Encode complete
- [05:46:28] Processing audio tracks
- Track 4352 (und): Keeping original audio
- [05:46:28] Multiplexing M2TS
- [05:49:09] CorrectEPData() 00006 2008
[05:51:51]PHASE ONE aborted by user request

----------------------
[06/09/20] BD Rebuilder v0.61.05
[14:34:59] Source: BD
- Input BD size: 23.82 GB
- Approximate total content: [07:06:25.192]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), CRF
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[14:34:59] PHASE ONE, Encoding
- [14:34:59] Processing: VID_00000 (1 of 1)
- [14:34:59] Extracting A/V streams [VID_00000]
- [14:42:46] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1440x1080
- Rate/Length: 29.970fps, 766,761 frames
- [14:42:46] Performing CRF Prediction...
- Analyzing 17.60 19.50 20.15 [20.15]
- [14:47:50] Encoding using constant rate factor.
- [16:57:44] Video Encode complete
- [16:57:44] Processing audio tracks
- Track 4352 (und): Keeping original audio
- [16:57:44] Multiplexing M2TS
- [17:00:40] CorrectEPData() 00006 2008
[17:53:55]PHASE ONE aborted by user request

[Mark_Venture]

Went to Amazon and not a single GTX 1660 (of several they sell) is in stock. Looking elsewhere.
Yeah, video cards seem to be out of stock, or very very low stock the past couple of months. :(

[DoctorM]

I was just reading an article about ARC over HDMI and that the original version, although limited to S/PDIF specs, can still pass Atmos & DTS:X embedded in Dolby Digital Plus audio tracks. This is apparently something streaming services use.

That got me thinking, since lossless is pretty much a waste of disc space, could BD RB create a DD+/Atmos track? Not for ARC use, but just for compression reasons.

[CV91913]

Hello again.
could anybody give me advice please?

When you say the source is a BD that you recorded, exactly how was it recorded? The errors could be from a corrupt source.

[MrVideo]

Because BD-RB doesn't reencode the 720p 59.94 to 1080p 23.976. Each attempt, combination I've used always aborts in the attempt. IVTC produces (in WORKFILES) a 720p 59.97/29.97 video stream that's too fast. 2-passes are aborted on 1st pass. If I use CBR it finishes, but this relies on tsMuxeR not altering the video from Import.
I should have been a little more specific. I wasn't implying that you upconvert to 1080. I was saying that a much better source of the show is available in 1080p23.976.

Did you try adding your own AVIsynth script instead:
telecide(guide=1)
decimate()
That should get you 720p23.976.

Still, obtaining the show at 1080p23.976 would be much better than trying to do all the work yourself. They even come with subtitles.

Oh, and no bugs or snipes.

[jdobbs]

Yeah, video cards seem to be out of stock, or very very low stock the past couple of months. :(Picked one up at Microcenter and installed it today. Now comes the part where I try to figure out NVENC encoding.

[AmigaFuture]

I should have been a little more specific. I wasn't implying that you upconvert to 1080. I was saying that a much better source of the show is available in 1080p23.976.

OOohhhh, okay! I checked with upscaling though with 1 program and it looked good, but there was still a jitter so some frames were left. HandBrake so far is the only processor that's getting videos to smooth 23.976 at 720p. I'd prefer high quality 1080p, but my TiVo Roamio doesn't record at that. I know there are other ways..but I prefer from the subscription I have been maintaining.

Did you try adding your own AVIsynth script instead:
telecide(guide=1)
decimate()
That should get you 720p23.976.

I'll add that to BD-RB's AVS Filter and check between CRF, ABR, and 2-pass combinations. Below is the result of putting that into AVS Filter.

I haven't made an AVS script outside of BD-RB in a long time. I wasn't very good at it..and so I stopped for a while. Ignore the stuff after the date & channel..it's my own comment about affects after importing from this source. The output size doesn't seem to matter, so I was trying to reencode each episode.

[06/19/20] BD Rebuilder v0.61.05
[13:57:58] Source: THE_SECRET_OF_SKINWALKER_RANCH_S1_E04_-_''HIGH_STRANGENESS''_(RECORDED_MAY_05,_2020,_HISTHD-W)_(1)_BAD_AT_5TH_CHAP
- Input BD size: 1.09 GB
- Approximate total content: [00:40:07.555]
- Target BD size: 4.36 GB
- Windows Version: 6.1 [7601]
- AVS Filtering is enabled
- Quality: Good (Fastest, BD-25+), CRF
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[13:58:01] PHASE ONE, Encoding
- [13:58:01] Processing: VID_00000 (1 of 1)
- [13:58:01] Extracting A/V streams [VID_00000]
- [13:58:49] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1280x720
- Rate/Length: 59.940fps, 144,309 frames
- Inverse Telecining in effect (IVTC)
- [13:58:49] Performing CRF Prediction...
- Analyzing 13.65 - Encode failed. Aborting.
- BD-Rebuilder v0.61.05
- Windows Version: 6.1 [7601]
- Working Path Free Space: 88.92GB
- AVISYNTH Version: 2.5.8.0, Ok
- LAVFILTERS: Ok
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[13:58:49] - Failed video encode, aborted


Still, obtaining the show at 1080p23.976 would be much better than trying to do all the work yourself. They even come with subtitles.

I understand. Yeah, lack of subs (sync) is one of the reasons I stopped that. Normally, though, all video stuff has been going very well and smooth...until I noticed these errors.

Edit 1: I'm wondering this what's causing the problem in VID_00000.DGI:

SIZ 1280 x 720
FPS 60000 / 1001
CODED 144309
PLAYBACK 144309
0.00% FILM
ORDER 0

[MrVideo]

OOohhhh, okay! I checked with upscaling though with 1 program and it looked good, but there was still a jitter so some frames were left. HandBrake so far is the only processor that's getting videos to smooth 23.976 at 720p. I'd prefer high quality 1080p, but my TiVo Roamio doesn't record at that. I know there are other ways..but I prefer from the subscription I have been maintaining.
AFAIK, The History Channel is 720p. The only way you are going to get 1080p23.976 is via other means.
I'll add that to BD-RB's AVS Filter and check between CRF, ABR, and 2-pass combinations. Below is the result of putting that into AVS Filter.[/quote[
Reset any BDRB options that would try IVTC. Don't want conflicting IVTC operations.
[quote]I haven't made an AVS script outside of BD-RB in a long time. I wasn't very good at it..and so I stopped for a while. Ignore the stuff after the date & channel..it's my own comment about affects after importing from this source. The output size doesn't seem to matter, so I was trying to reencode each episode.
[06/19/20] BD Rebuilder v0.61.05
[13:57:58] Source: BAD_AT_5TH_CHAP
- Decoding/Frame serving: DGDecNV
- Inverse Telecining in effect (IVTC)

I use the same decoder when I do my own recoding with IVTC. With BDRB saying that IVTC is in effect is telling me that you have a flag set for trying to do that. BDRB shouldn't detect that IVTC is in effect when using a personal AVS script. What is wrong in the 5th chapter?
[CODE]0.00% FILM
Not used by anything. Pretty much all of the 1080i video that I decoded had that indication, even though it was 2:3 pulldown video.

It would probably help if I had a sample of what you have to look at.

[AmigaFuture]

I did that but same error. I'll go rename my BD-RB INI and let it create a new one. I'm uploading a sample. I'll PM when done. I figured the FILM part in that file wasn't any big deal, but..

"With BDRB saying that IVTC is in effect is telling me that you have a flag set for trying to do that. BDRB shouldn't detect that IVTC is in effect when using a personal AVS script."

I didn't think about that until well after. Oops!

"What is wrong in the 5th chapter?"

The audio is out of sync after importing.. Right at the chapter point.

[AmigaFuture]

Let BD-RB make a new INI and added...

telecide(guide=1)
decimate()

to AVS Filter after disabling IVTC from Setup. Still aborts..

[15:57:49] Source: S1_E01-BAD_THINGS_HAPPEN_WHEN_YOU_DIG_TEST
- Input BD size: 1.10 GB
- Approximate total content: [00:40:33.764]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- AVS Filtering is enabled
- Quality: Good (Fastest, BD-25+), CRF
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[15:57:50] PHASE ONE, Encoding
- [15:57:50] Processing: VID_00000 (1 of 1)
- [15:57:50] Extracting A/V streams [VID_00000]
- [15:58:41] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1280x720
- Rate/Length: 59.940fps, 145,880 frames
- [15:58:41] Performing CRF Prediction...
- Analyzing 1.00 - Encode failed. Aborting.
- BD-Rebuilder v0.61.05
- Windows Version: 6.1 [7601]
- Working Path Free Space: 83.69GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[15:58:42] - Failed video encode, aborted


It doesn't matter which episode I use to test, or if I rename the files. A few moments ago I realize the filename is pretty long. For normal stuff, like playing that's okay, but not for importing.

Hmm.. I'm going to go through the list of encoders again...since I hadn't renamed my INI. I think my INI isn't the problem. I'm still thinking tsMuxeR is it.

[AmigaFuture]

Update: I forgot about IVTC_METHOD=1. In conjunction to IVTC_SELECTION=1 then select video stream from list with RMB and enable IVTC. This allowed to 720p to be converted to 23.976. Arrgh! However, this does not help Convert 720 to 1080 from Setup. That always renders the video playing too fast even though it's noticed as 23.976. I'm now running a test with MKV output, for now, leaving at CRF. Rerendering to 1080 leaving audio alone.

Different episodes are resulting in different output. Not consistent as HandBrake was doing. Some, as I preview from WORKFILES live, show 59.94 but display at 23.976 speeds. At some chapter points the Alt MKV IS 1080p @ 23.976 but the audio is out of sync.

I'll have BD-RB process all 8 episodes at 720p with these settings and check what results.

[Mark_Venture]

Picked one up at Microcenter and installed it today. Now comes the part where I try to figure out NVENC encoding.Very nice!!

If you ever need help testing, I'd be happy to help.

[Mike-uk]

Picked one up at Microcenter and installed it today. Now comes the part where I try to figure out NVENC encoding.
im sure you already came across this

If you are looking to make use of the dedicated decoding/encoding hardware on your GPU in an existing application you can leverage the integration already available in the FFmpeg/libav. FFmpeg/libav should be used for evaluation or quick integration, but it may not provide control over every encoder parameter. NVDECODE and NVENCODE APIs should be used for low-level granular control over various encode/decode parameters and if you want to directly tap into the hardware decoder/encoder. This access is available through the Video Codec SDK.

https://developer.nvidia.com/nvidia-video-codec-sdk/download

[Ch3vr0n]

Ooh great to hear jdobbs. hw acc bdrb, maybe it'll be possible to use it on 3D discs instead of the frim method that creates artifacts with hw acc. Unless you found a fix to that. I did rememer reading a while back that an updated frim version might fix that?

[vanille]

Hello. Thank you so much for replying to me.
I recorded TV shows and then cut commercials on TMPGEnc Authoring Works.

When you say the source is a BD that you recorded, exactly how was it recorded? The errors could be from a corrupt source.

[CV91913]

Hello. Thank you so much for replying to me.
I recorded TV shows and then cut commercials on TMPGEnc Authoring Works.

It could be an issue with the source file. I have used TAW a lot. If you are importing an edited mp4 into BDRB with output to BD structure, why don't you just use TAW to do that. It will make BDs.

[AmigaFuture]

Hello again.
could anybody give me advice please?

Is there enough hard drive space available? It passes the rendering process and aborted during the multiplexing. Seems storage related...?

[AmigaFuture]

AFAIK, The History Channel is 720p. The only way you are going to get 1080p23.976 is via other means.
I'll add that to BD-RB's AVS Filter and check between CRF, ABR, and 2-pass combinations. Below is the result of putting that into AVS Filter.
Reset any BDRB options that would try IVTC. Don't want conflicting IVTC operations.

I use the same decoder when I do my own recoding with IVTC. With BDRB saying that IVTC is in effect is telling me that you have a flag set for trying to do that. BDRB shouldn't detect that IVTC is in effect when using a personal AVS script. What is wrong in the 5th chapter?

Not used by anything. Pretty much all of the 1080i video that I decoded had that indication, even though it was 2:3 pulldown video.

It would probably help if I had a sample of what you have to look at.

Maybe you'll do better with it than I have? Luck isn't any kind of truth, so I won't use any references towards that.

Update: My System has become slow as I've done many tests with BD-RB with this file and some others that didn't Import well. Where Sync was lost after the 2nd "chapter" which is where commercials were cut from. By slow, which I've not encountered before, I mean..slow responses to Shut down, or Icon clicks. Even Right click on Quick Launch to get the menu for Task Manager. Without so many tests with BD-RB (TsMuxeR) my System is pretty quick in response. Which means a memory leak somewhere in the Processing of video.

Yesterday I thought it odd, late night when I noticed it at first.

Other than that, anything from you about the video, results?

[jdobbs]

Does anyone here know how or if you can do 2 pass encoding with NVENCC? I've looked at it and FFMPEG, and I like it better (more control and faster). But I can't seem to see a way to do 2 pass encoding with it.

[Added] By the way -- I am really impressed with the speed and quality of the NVIDIA GTX-1660's encoding. All I can say is "Wow".

[Added] Never mind. I did some reading and realize now that true 2 pass isn't an option in NVENC. It has it's own "2-pass" methodology that uses a lookahead scheme.

[vanille]

Hello. Thank you so much for replying to me again.
Yes. I can make BDs with only TMPGEnc Authoring Works.
But when the video is fully rendered, it's not smooth.
Of course, it's not always jerky, it depends on player.
I'd like to make BDs which I can watch on any player.

It could be an issue with the source file. I have used TAW a lot. If you are importing an edited mp4 into BDRB with output to BD structure, why don't you just use TAW to do that. It will make BDs.

[vanille]

Hello. Thank you so much for replying to me.
I think there's enough space, almost 400GB.

Is there enough hard drive space available? It passes the rendering process and aborted during the multiplexing. Seems storage related...?

[AmigaFuture]

Hello. Thank you so much for replying to me again.
Yes. I can make BDs with only TMPGEnc Authoring Works.
But when the video is fully rendered, it's not smooth.
Of course, it's not always jerky, it depends on player.
I'd like to make BDs which I can watch on any player.

I had that problem when I checked the demo. It doesn't IVTC, or use a method BD-RB uses, nor HandBrake. It leaves "ghost" affects, and isn't smooth in motion video.

Hello. Thank you so much for replying to me.
I think there's enough space, almost 400GB.

You didn't include storage space free, so I wondered. :)

[Mike-uk]

Does anyone here know how or if you can do 2 pass encoding with NVENCC? I've looked at it and FFMPEG, and I like it better (more control and faster). But I can't seem to see a way to do 2 pass encoding with it.

[Added] By the way -- I am really impressed with the speed and quality of the NVIDIA GTX-1660's encoding. All I can say is "Wow".

[Added] Never mind. I did some reading and realize now that true 2 pass isn't an option in NVENC. It has it's own "2-pass" methodology that uses a lookahead scheme.
found this

You can do 2-pass in a few popular encoding programs, but the .stats file that is created is blank. The only way I've found to actually get a true 2-Pass is to run the first pass on the CPU, save the stats file and then use that during a second pass using NVENC which is a cumbersome process. Every other way I've encountered is no different than a 1-pass encode.

mayby have the option of first pass cpu, or both passes gpu, even with first pass cpu i guess the total time verses all cpu will be less

[Sharc]

Does anyone here know how or if you can do 2 pass encoding with NVENCC? I've looked at it and FFMPEG, and I like it better (more control and faster). But I can't seem to see a way to do 2 pass encoding with it.

[Added] By the way -- I am really impressed with the speed and quality of the NVIDIA GTX-1660's encoding. All I can say is "Wow".

[Added] Never mind. I did some reading and realize now that true 2 pass isn't an option in NVENC. It has it's own "2-pass" methodology that uses a lookahead scheme.
You may also want to try both its constant quantizer and its constant quality mode (both 1-pass)

Edit:
ooops - these modes may apply for AVC only. Don't know if similar exist for HEVC.

[MrVideo]

Other than that, anything from you about the video, results?
The main thing I wanted to look at was the pulldown cadence. Was it 3-2? Well it isn't and is at the same time. The problem is that many times when it is supposed to have a three frame count, it is only two. It'll be 3-2-2. Then a few 3-2 sequences before doing another 3-2-2.

I'm now going to see if it will do a nice IVTC via the way I normally do it, i.e., using x264 to recode with AVIsynth tools to do the IVTC work.

[MrVideo]

Well, you are not going to like the results I achieved. The IVTC recode came out great. No audio issues either. The video was smooth. That means that IVTC can be accomplished. How to get BDRB to accomplish it is another story.

My steps were to use VideoReDo to separate the audio and video. x264 was used to recode the video, fed the video stream via AVISynth tools that did the IVTC. mkvmerge was then used to put the new video and audio back together,

[AmigaFuture]

Why would I not like that? I'm cool with separating the streams with my VideoReDo. You've left away what tools you used to do the IVTC.

[MrVideo]

The tool is a Zshell and doit script that I run under cygwin. They won't do you any good if you do not use cygwin, i.e. Linux for M$.

[AmigaFuture]

I completely spaced the abilities of MeGUI. It's doing a great job of reencoding the 720p 59.94 to 23.976 (zero frames left, and totally smooth playback and IN sync). Once I found that Analysis has some memory leaks, and made a copy of the AVS script I've been able to paste it..and use it skipping the Analysis..and zero memory problems (I thought using TIVTC.dll was the problem?). Which was causing my system to become very slow (Full RAM).

On another note, I'm attempting to use the script (MeGUI), though slightly modified, for BD-RB..and so far, it's not going well for final product BUT...is now rendering every time). For now, though, I'm able to finish my encodes of these episodes with the help of MKMERGE GUI..and should be able to make a sweet BD with BD-RB. Aaahhhh... Haha. I appreciate the look-see, MrVideo. That Cygwin looks interesting. I'll look into this more with BD-RB..perhaps a bug..still and not only with TsMuxeR?

[MrVideo]

Great that you got things going. Keep in mind that cygwin is mainly command line.

[cartman0208]

Anyway, sorry to go on... So, I went to the first post on this thread to DL all the versions of Avisynth and stuff we need to do, and WTF! The Avisynth links, both of them do not work now...??? I suppose I can just find the Avisynth site, etc., but I thought that was kind of weird. Did some monumental changes occur here since I was gone...? Like...


Sorry, the last Apache update made the webserver case sensitive (again :mad: ) ... Since the link points to Avisynth_260.exe but the file is named AviSynth_260.exe you got a 404 :(

I just renamed the file, link should be working now.

[MrVideo]

Sorry, the last Apache update made the webserver case sensitive (again :mad: )
1: Updating the apache code is not supposed to change any local configuration files. Never has for me.
2: So, just fix the config file and restart apache.

[cartman0208]

1: Updating the apache code is not supposed to change any local configuration files. Never has for me.
2: So, just fix the config file and restart apache.

Well ... the server is a NAS appliance ... Apache is an app on it ... I DID change the config file, but the update of the app resets it to default

[MrVideo]

That sucks. That would mean keeping a copy and putting it back after an update.

[jdobbs]

Sorry, the last Apache update made the webserver case sensitive (again :mad: ) ... Since the link points to Avisynth_260.exe but the file is named AviSynth_260.exe you got a 404 :(

I just renamed the file, link should be working now.Wow. When was that posted... I must have missed it completely.

[Edit] Ok, I see. It was part of the "3 frigg'n MONTHS behind" post. I guess I just missed that part.

[jdobbs]

Does anyone out there have some suggestions for a command line (for NVEncC.exe) that will create an .hevc file that is compatible with UHD blu-ray? I can create one that will compile and play (in UHD and HDR), but any attempts to fast forward/rewind or chapter skip will result in a blank screen (sound only). I've been beating my head against the wall for a couple days now -- and any help would be appreciated.

Thanks.

[Mike-uk]

Does anyone out there have some suggestions for a command line (for NVEncC.exe) that will create an .hevc file that is compatible with UHD blu-ray? I can create one that will compile and play (in UHD and HDR), but any attempts to fast forward/rewind or chapter skip will result in a blank screen (sound only). I've been beating my head against the wall for a couple days now -- and any help would be appreciated.

Thanks.

mayby post the question on his blog ??

https://rigaya34589.blog.fc2.com/

[jdobbs]

mayby post the question on his blog ??

https://rigaya34589.blog.fc2.com/Can you post in English in a thread that is in Japanese and has to be interpreted by Google translate?

I was under the impression that people have actually done UHD-BD encodes with this encoder. I'm hoping they can provide me with something that points out what I'm missing.

With this specific behavior I thought that maybe it wasn't creating I frames at the right distances/places, but I brought the resulting HEVC stream up with an HEVC browser and it looks like they are at the right places. I'm thinking now that maybe it's missing some of the supplementary information, but I'm not really sure? I guess I can do some comparisons to X265 output and see. But even if that is it -- I'd still need some way to add it.

[Sharc]

Can you post in English in a thread that is in Japanese and has to be interpreted by Google translate?

You may want to report it as an issue here (in English):
https://github.com/rigaya/NVEnc/issues

[gonca]

Does anyone out there have some suggestions for a command line (for NVEncC.exe) that will create an .hevc file that is compatible with UHD blu-ray? I can create one that will compile and play (in UHD and HDR), but any attempts to fast forward/rewind or chapter skip will result in a blank screen (sound only). I've been beating my head against the wall for a couple days now -- and any help would be appreciated.

Thanks.

I tried a barebones command line and I get the same symptoms. Plays fine start to finish, HDR and UHD recognized but ff, rw or chapter select I get black screen

[cartman0208]

Does anyone out there have some suggestions for a command line (for NVEncC.exe) that will create an .hevc file that is compatible with UHD blu-ray? I can create one that will compile and play (in UHD and HDR), but any attempts to fast forward/rewind or chapter skip will result in a blank screen (sound only). I've been beating my head against the wall for a couple days now -- and any help would be appreciated.

Thanks.

Maybe it's something with the CU-Size ... I noticed that some months ago when I did some 4K testing with nvenc ...
Mediainfo doesn't show it (to me) ... can only be seen in VLC Player:
Video Resolution: 3840x2160
Buffer dimensions: 3840x2176

With CU Size set to 32 and 2160 isn't divisible by 32, result is set to 2176 which could end up in UHD incompatibility ...

In the original mt2s the values are identical.

So .. 2 possibilities ... setting CU size to 16x16 (if possible) or crop away 16 pix vertically and hope its still compatible :D

Just an idea ...

[jdobbs]

I tried a barebones command line and I get the same symptoms. Plays fine start to finish, HDR and UHD recognized but ff, rw or chapter select I get black screenThanks for confirming it. My guess is there is some supplementary header information missing in the i-frame since that is what is used for FF/REW & CHAP jumps. I'm looking to see if I can find anything and possibly fix it myself. I can't find anything in the command line options that might change it significantly. Of course BD-RB fixing it would mean that after an encode I'd have to scan and rewrite the .hevc file (which can add some time to the process). I posted and error report on the site Sharc listed, hopefully someone will actually see it and respond -- but it looks like there are quite a bit of other reports there as well.

[jdobbs]

Maybe it's something with the CU-Size ... I noticed that some months ago when I did some 4K testing with nvenc ...
Mediainfo doesn't show it (to me) ... can only be seen in VLC Player:
Video Resolution: 3840x2160
Buffer dimensions: 3840x2176

With CU Size set to 32 and 2160 isn't divisible by 32, result is set to 2176 which could end up in UHD incompatibility ...

In the original mt2s the values are identical.

So .. 2 possibilities ... setting CU size to 16x16 (if possible) or crop away 16 pix vertically and hope its still compatible :D

Just an idea ...Interesting. If I look at the Sequence Parameter Set (NAL_SPS) it also tells me 3840x2176 for the picture height/width in luma samples, while in X265 it correctly says 3840x2160. But it plays when I insert the disc -- which makes me wonder what the significance of it is. You'd think an incorrect resolution would cause it to fail.

There's a discussion on this topic at this link. (https://forums.developer.nvidia.com/t/nvenc-hevc-encoding-of-3840x2160-results-in-coded-size-of-3840x2176/60107) I'm not sure if there is a solution in the works...

[Edit]@cartman0208

The encoder allows me to set the CU to 16 (--cu-max 16) - but it seems to have no affect on the SPS value (as it still says 3840x2176 with a bottom offset of 8). The Blu-Ray spec specifically states that these values aren't allowed -- but my guess is that the player's hardware allows it (per the H.265 standard), and that's why the video is playing back. For right now I'm going to pretend this isn't the issue -- but I'll investigate further.

[MrVideo]

There's a discussion on this topic at this link. (https://forums.developer.nvidia.com/t/nvenc-hevc-encoding-of-3840x2160-results-in-coded-size-of-3840x2176/60107) I'm not sure if there is a solution in the works...
From what I read in the discussion is that nVidia is telling all the decoder manufactures that do not display 2176 as 2160 (by cropping bottom 16) to get with the spec and go screw yourself.

[cartman0208]

[Edit]@cartman0208

The encoder allows me to set the CU to 16 (--cu-max 16) - but it seems to have no affect on the SPS value (as it still says 3840x2176 with a bottom offset of 8). The Blu-Ray spec specifically states that these values aren't allowed -- but my guess is that the player's hardware allows it (per the H.265 standard), and that's why the video is playing back. For right now I'm going to pretend this isn't the issue -- but I'll investigate further.

Yep, tried that too with the same result.
What I didn't try was my second suggestion ... initially crop away 16 pixel to a height of 2144, which is divisibly by 32...
Too small should be less of a problem then too big... or does the BluRay standard say EXACTLY 2160px in height?

I'm still wild guessing here, but maybe the screen can't display the oversize and stays blank ...

[gonca]

I cropped 280 top and bottom, script for a mkv file, and it behaved exactly the same
I know that is an illegal res for BD but the player didn't mind it.

[Sharc]

Interesting. If I look at the Sequence Parameter Set (NAL_SPS) it also tells me 3840x2176 for the picture height/width in luma samples, while in X265 it correctly says 3840x2160. But it plays when I insert the disc -- which makes me wonder what the significance of it is. You'd think an incorrect resolution would cause it to fail.

There's a discussion on this topic at this link. (https://forums.developer.nvidia.com/t/nvenc-hevc-encoding-of-3840x2160-results-in-coded-size-of-3840x2176/60107) I'm not sure if there is a solution in the works...

[Edit]@cartman0208

The encoder allows me to set the CU to 16 (--cu-max 16) - but it seems to have no affect on the SPS value (as it still says 3840x2176 with a bottom offset of 8). The Blu-Ray spec specifically states that these values aren't allowed -- but my guess is that the player's hardware allows it (per the H.265 standard), and that's why the video is playing back. For right now I'm going to pretend this isn't the issue -- but I'll investigate further.
Isn't this much the same as with x264 AVC: The coded size has always been 1920x1088 while the display size is 1920x1080?

[MrVideo]

Isn't this much the same as with x264 AVC: The coded size has always been 1920x1088 while the display size is 1920x1080?
Yep, that be the case.

[jdobbs]

Looking at the output from NVENCC, I'm guessing (but only guessing) that this may be the issue:

According to "White Paper Blu-ray Disc Read-Only Format Coding constraints on HEVC video streams for BD-ROM Version 3.0", page 6, each GOP (Group of Pictures) of the HEVC stream must start with an IDR (of course) -- and will contain one SPS (Sequence Parameter Set), one VPS (Video Parameter Set), and at least one PPS (Picture Parameter Set), and no more than 30 PPSs.

In dumping out the HEVC stream I'm finding that only the first GOP (the first IDR frame and following P/B frames in the file) meets this requirement. All the others IDR frames (start of GOP) I've looked at only have an AUD (Access Unit Delimeter) and a couple SEI's (Supplemental Enhancement Information) preceding the IDR slice.

I'll have to do some finagling with the stream to find out if this is truly the issue -- but it could make sense and explain why the stream can start playing from the beginning (the IDR that has the required information) but can't step into any of the others (FF/REW and CHAPTER SKIPS).

You never know, this may not be the problem at all... but I guess I'm going to have to find out somehow. In X265 you create a stream that contains the SPS/VPS/PPS in every GOP by using the --repeat-headers command line option. I'm hoping the same thing can be done in NVENCC.

I've added this information to my Issue Report at GITHUB. Hopefully someone with a little more HEVC/UHD-BD knowledge than me can confirm or deny this as the cause of the issue I'm seeing.

[Edit] In the meantime, I'm going to see how hard it would be for me to to scan and insert the headers via a software routine -- or if it is even possible. Unfortunately that would require me to read through the entire HEVC file and write a new one -- which requires significant processing time. In the end I may find out it isn't even the problem! :scared:

[jdobbs]

Looking at the output from NVENCC, I'm guessing (but only guessing) that this may be the issue:

According to "White Paper Blu-ray Disc Read-Only Format Coding constraints on HEVC video streams for BD-ROM Version 3.0", page 6, each GOP (Group of Pictures) of the HEVC stream must start with an IDR (of course) -- and will contain one SPS (Sequence Parameter Set), one VPS (Video Parameter Set), and at least one PPS (Picture Parameter Set), and no more than 30 PPSs.

In dumping out the HEVC stream I'm finding that only the first GOP (the first IDR frame and following P/B frames in the file) meets this requirement. All the others IDR frames (start of GOP) I've looked at only have an AUD (Access Unit Delimeter) and a couple SEI's (Supplemental Enhancement Information) preceding the IDR slice.

I'll have to do some finagling with the stream to find out if this is truly the issue -- but it could make sense and explain why the stream can start playing from the beginning (the IDR that has the required information) but can't step into any of the others (FF/REW and CHAPTER SKIPS).

You never know, this may not be the problem at all... but I guess I'm going to have to find out somehow. In X265 you create a stream that contains the SPS/VPS/PPS in every GOP by using the --repeat-headers command line option. I'm hoping the same thing can be done in NVENCC.

I've added this information to my Issue Report at GITHUB. Hopefully someone with a little more HEVC/UHD-BD knowledge than me can confirm or deny this as the cause of the issue I'm seeing.

[Edit] In the meantime, I'm going to see how hard it would be for me to to scan and insert the headers via a software routine -- or if it is even possible. Unfortunately that would require me to read through the entire HEVC file and write a new one -- which requires significant processing time. In the end I may find out it isn't even the problem! :scared:Well... even a broken clock is right twice a day.

That was it. I wrote some code to insert the SPS/VPS/PPS headers into the IDR of each GOP and... it fixed the issue. Fast Forward, Rewind and Chapter jumps now work.

I'll add code into BD-RB to correct the HEVC stream after encoding. It looks like it will add about 15 minutes or so to a job. But that's not bad considering how much time is saved using the NVENCC encoder. I just ran a complete job on a 2 hour and 22 minute UHD/HDR movie and it finished the encoding portion in less than 30 minutes (using the fastest setting).

I have to add supporting code for several subroutines before BD-RB is ready for a testing release -- expect it in the next week or so.

I will also update my issue information on GITHUB and hopefully all the will have to do is add a "--repeat-headers" command line function and make my workaround unneeded.

[Sharc]

I will also update my issue information on GITHUB and hopefully all the will have to do is add a "--repeat-headers" command line function and make my workaround unneeded.
Now let's hope that rigaya takes action :cool:

[Ch3vr0n]

2h22m compared to what for you @jdobbs? 16hrs? ^^

[Mike-uk]

i guess this blank issue is only present on a bluray player, was playing the file on a pc ok ??

[jdobbs]

i guess this blank issue is only present on a bluray player, was playing the file on a pc ok ??Yes. It was only an issue when authored into BD format and played on a Blu-Ray player. On a PC it had worked fine. I didn't test it, but I would assume an MKV or MP4 would probably have played even on the BD unit. The issue (needing the headers in each GOP) is related to the container type used in an authored BD.

[jdobbs]

2h22m compared to what for you @jdobbs? 16hrs? ^^2h22m was the length of the movie. The actual job only about 45 minutes start-to-finish (before correcting the HEVC stream). And, yes, using X265 it would have probably taken somewhere in the neighborhood of 16 hours.

[cartman0208]

Can't wait to do some alpha tesing ;)

[Ch3vr0n]

I don't suppose this will be of benefit for 3D encoding would it. Last time i tried hw acc FRIM it resulted in severe artifacts for software based players.

[jdobbs]

I don't suppose this will be of benefit for 3D encoding would it. Last time i tried hw acc FRIM it resulted in severe artifacts for software based players.Sorry, no.

I haven't looked at FRIM or 3D in a while, but I seem to remember that problem as being related to drivers.

[Ch3vr0n]

I believe a while back someone said there was an updated FRIM build that supposedly fixed that problem. I just have no idea where to get it.

Sent from my Pixel 3 XL using Tapatalk

[musiclover]

I believe a while back someone said there was an updated FRIM build that supposedly fixed that problem. I just have no idea where to get it.

Sent from my Pixel 3 XL using Tapatalk

https://www.videohelp.com/software/FRIM and https://forum.doom9.org/showthread.php?t=169651

[Ch3vr0n]

Which one would i need for BDRB, the 32bit version? My cpu is a 9900K

[gonca]

32 bit

[Mike-uk]

bdrebuilder uses frim 1.25, there has been 5 updates and now 1.31

[jdobbs]

Anybody else experiencing this?

I can start NVENCC with a fixed command line.

When I start the job it seems to be slower than I'd expected -- about 125fps. So I stop the job and restart it. Suddenly I'm getting 420fps... with the exact same command line. Try it again... and it's random. I might get either of the two speeds. Weird.

Now THAT's confusing.

[MrVideo]

Well... even a broken clock is right twice a day.
Not if it is a digital clock and the display goes dark/blank. :eek:

[Sharc]

Anybody else experiencing this?

I can start NVENCC with a fixed command line.

When I start the job it seems to be slower than I'd expected -- about 125fps. So I stop the job and restart it. Suddenly I'm getting 420fps... with the exact same command line. Try it again... and it's random. I might get either of the two speeds. Weird.

Now THAT's confusing.
Strange. Did you check the GPU load and temperature (e.g. using GPU-Z)? Is the speed limited by the GPU or by the bus transfers/memory access? Are you using HDD or SSD? Virus scanner interference, or some other background process interfering?
What I noticed here (NVEncC x264 1050Ti) is an initial speed increase during the first few (say 10) seconds which then settles to a steady value.

[Emulgator]

When I start the job it seems to be slower than I'd expected -- about 125fps. So I stop the job and restart it. Suddenly I'm getting 420fps... with the exact same command line. Try it again... and it's random. I might get either of the two speeds. Weird.

Now THAT's confusing.

An app being quicker on second run is no mystery, happens with sore more SW.
Its just that these date are still kept in RAM.
Like with tsMuxeR, muxing time went from 9..10 min first run
down to 1,5 minutes for the same 10GB test stream on second and third run.
(Magnetic platter HDDs used, with SSD maybe unnoticeable)
I just extensively tested for one particular stream losing packets at the end.
(solved since the 2020-06-27 build for me, BTW)

Would fit the available 32GB RAM. (Did not run RAMMap though to confirm)
Why it would be slower on third run, I cannot comment.
But if I close the app and allow the RAM to be flushed, then it may take the full first running time again.

[cartman0208]

Anybody else experiencing this?

I can start NVENCC with a fixed command line.

When I start the job it seems to be slower than I'd expected -- about 125fps. So I stop the job and restart it. Suddenly I'm getting 420fps... with the exact same command line. Try it again... and it's random. I might get either of the two speeds. Weird.

Now THAT's confusing.

Can you post that commandline?

[Mike-uk]

ohhh looks like nvencc has fixed/added the repeat issue :)

[Mike-uk]

Anybody else experiencing this?

I can start NVENCC with a fixed command line.

When I start the job it seems to be slower than I'd expected -- about 125fps. So I stop the job and restart it. Suddenly I'm getting 420fps... with the exact same command line. Try it again... and it's random. I might get either of the two speeds. Weird.

Now THAT's confusing.

hmm im only get 66 FPS regardless how many time i restart, just a note 400 fps sounds too quick, gpu encoding doesnt give same quality as cpu, so id be happy for gpu to be spitting out the best quality it can do "--preset quality" even if that means less fps, im sure gpu at max quality will be a lot quicker than cpu, will be nice to have the option of HW excelearion, will you be including 264 hw exceleration also ?

in using a RTX 2070 Super

NVEncC (x64) 5.06 (r1569) by rigaya, Jun 16 2020 13:25:14 (VC 1916/Win/avx2)
[NVENC API v9.1, CUDA 10.1]
reader: raw, y4m, avi, avs, vpy, avsw, avhw [H.264/AVC, H.265/HEVC, MPEG2, VP8, VP9, VC-1, MPEG1, MPEG4]

Environment Info
OS : Windows 10 x64 (19041)
CPU: Intel Core i7-8700K @ 3.70GHz [TB: 4.30GHz] (6C/12T)
RAM: Used 7414 MB, Total 16311 MB

#0: GeForce RTX 2070 SUPER (2560 cores, 1800 MHz)[PCIe3x16][451.48]
NVEnc features
Codec: H.264/AVC
Max Bframes 4
B Ref Mode yes
RC Modes 63
Field Encoding no
MonoChrome no
FMO no
Quater-Pel MV yes
B Direct Mode yes
CABAC yes
Adaptive Transform yes
Max Temporal Layers 0
Hierarchial P Frames no
Hierarchial B Frames no
Max Level 62
Min Level 10
4:4:4 yes
Min Width 145
Max Width 4096
Min Height 49
Max Height 4096
Multiple Refs yes
Max LTR Frames 8
Dynamic Resolution Change yes
Dynamic Bitrate Change yes
Forced constant QP yes
Dynamic RC Mode Change no
Subframe Readback yes
Constrained Encoding yes
Intra Refresh yes
Custom VBV Bufsize yes
Dynamic Slice Mode yes
Ref Pic Invalidiation yes
PreProcess no
Async Encoding yes
Max MBs 65536
Lossless yes
SAO no
Me Only Mode yes
Lookahead yes
AQ (temporal) yes
Weighted Prediction yes
10bit depth no

Codec: H.265/HEVC
Max Bframes 5
B Ref Mode yes
RC Modes 63
Field Encoding no
MonoChrome no
Quater-Pel MV yes
B Direct Mode no
Max Temporal Layers 0
Hierarchial P Frames no
Hierarchial B Frames no
Max Level 186
Min Level 30
4:4:4 yes
Min Width 129
Max Width 8192
Min Height 33
Max Height 8192
Multiple Refs yes
Max LTR Frames 7
Dynamic Resolution Change yes
Dynamic Bitrate Change yes
Forced constant QP yes
Dynamic RC Mode Change no
Subframe Readback yes
Constrained Encoding yes
Intra Refresh yes
Custom VBV Bufsize yes
Dynamic Slice Mode yes
Ref Pic Invalidiation yes
PreProcess no
Async Encoding yes
Max MBs 262144
Lossless yes
SAO yes
Me Only Mode yes
Lookahead yes
AQ (temporal) yes
Weighted Prediction yes
10bit depth yes


NVDec features
H.264/AVC: nv12, yv12
H.265/HEVC: nv12, yv12, yv12(9bit), yv12(10bit), yv12(12bit), yuv444, yuv444(9bit), yuv444(10bit), yuv444(12bit)
MPEG1: nv12, yv12
MPEG2: nv12, yv12
MPEG4: nv12, yv12
VP8: nv12, yv12
VP9: nv12, yv12, yv12(9bit), yv12(10bit), yv12(12bit)
VC-1: nv12, yv12

[Ch3vr0n]

i'll experiment with the updated version. I'll have to go into the bios to enable the iGPU. That's a job for upcoming weekend.

[jdobbs]

Can you post that commandline?I've deleted it. Right now I'm in the middle of system backups, but I'll post an example later.

Thanks.

[jdobbs]

ohhh looks like nvencc has fixed/added the repeat issue :)Wow. That's are really quick response! I just downloaded it and will do some testing after my backups finish. I added code to BD-RB yesterday to scan/add the headers -- but I'm very happy to remove it! I'd much rather have the encoder do it!

[MrVideo]

[...] will be nice to have the option of HW excelearion, will you be including 264 hw exceleration also?
I think you mean acceleration. Also, when posting long lists like that, please CODE wrap them.

[Mike-uk]

I think you mean acceleration. Also, when posting long lists like that, please CODE wrap them.

:p yes acceleration, code wrap done

[jdobbs]

Can you post that commandline?"D:\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "N:\BD\SOURCE\BDMV\STREAM\00500.m2ts" --codec h264 --preset quality --bluray --qp-min 0 --vbr 22429 --keyfile "D:\WORKING4\WORKFILES\VID_00500.CHP" --sar 1:1 --aud --pic-struct --vbv-bufsize 30000 --max-bitrate 35000 --gop-len 24 -o "D:\WORKING4\WORKFILES\VID_00500.AVS.264"
hmm im only get 66 FPS regardless how many time i restart, just a note 400 fps sounds too quick, gpu encoding doesnt give same quality as cpu, so id be happy for gpu to be spitting out the best quality it can do "--preset quality" even if that means less fps, im sure gpu at max quality will be a lot quicker than cpu, will be nice to have the option of HW excelearion, will you be including 264 hw exceleration also ?I'm guessing you are talking about a 2160p source. The one in which I was getting the goofy numbers was a h264 stream at 1080p.

[Mike-uk]

"
I'm guessing you are talking about a 2160p source. The one in which I was getting the goofy numbers was a h264 stream at 1080p.

yes was 2160p

[jdobbs]

Just a head's up. I tested the new version of NVENCC yesterday, and the new option to include headers results an encoding failure with a "Cannot allocate memory" message. Removing the new option from the command line makes the encoding error goes away. But, then, of course you're back to having the FF/REW/CHAP issues. I posted an issue report on GITHUB. It appears that the new option creates a memory leak (as can be observed by watching the process under the Windows 10 task manager). On the 32 bit version of NCENCC it hits the memory limitation pretty quickly (you have to use the 32 bit version to remain compatible with AVISYNTH 2.60 -- which must be used under certain circumstances).

So the options right now are to wait and see if it gets another quick fix, or to go ahead and implement the code that adds the headers within BD-RB. I'd prefer the first option, as that's a cleaner way to go. So I'm going to wait for a bit and see what happens.

[Mike-uk]

Id wait a while and see if it gets fixed, i can also conform its eating memory, at frame 69522 it consumed 1.6 gig of memory and then errored, im running 16 gig but according to task manager i was only at 50% mem ussage ?

[gonca]

I think the wait is over
5.08 is out

[Mike-uk]

I think the wait is over
5.08 is out

unfortunatly not :( not good news :(

Please try with x64 build of NVEnc 5.08, it should not require nppc64_10.dll now.

It might be a memory leak but it's difficult to fix, as "--repeat-headers" only sets a parameter provided by NVENC SDK, there is little I can do here.

[gonca]

Yes, but issue 246 seemed to develop with 5.07 has been resolved
Running a quick test, to see if it finishes

[gonca]

Update 1
80000 frames out of 188855
RAM usage is steady 582.5 MB
x265 is using 6.7 GB

Update 2
110000 frames

Completed fine

[2020-07-01][12:02:46] Simple x264 Launcher (Build #1208), built 2020-06-25
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] Job started at 2020-07-01, 12:02:46.
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] Source file : I:\PACIFIC RIM.vpy
[2020-07-01][12:02:46] Output file : T:\\PACIFIC RIM.hevc
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] --- SYSTEMINFO ---
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] Binary Path : C:\Users\LUIS\Desktop\x264_launcher.2020-06-25
[2020-07-01][12:02:46] Avisynth : Yes
[2020-07-01][12:02:46] VapourSynth : Yes
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] --- SETTINGS ---
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] Encoder : NVEncC, 64-Bit (x64), HEVC
[2020-07-01][12:02:46] Source : VapourSynth (vpy)
[2020-07-01][12:02:46] RC Mode : CQP
[2020-07-01][12:02:46] Preset : performance
[2020-07-01][12:02:46] Tuning : <None>
[2020-07-01][12:02:46] Profile : main10
[2020-07-01][12:02:46] Custom :
--master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50)"
--max-cll "2465,823" --frames 188855 --chromaloc 2 --colormatrix bt2020nc --colorprim bt2020
--transfer smpte2084 --repeat-headers

[2020-07-01][12:02:46]
[2020-07-01][12:02:46] --- CHECK VERSION ---
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] Detect video encoder version:
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] Creating process:
[2020-07-01][12:02:46] C:\Users\LUIS\Desktop\x264_launcher.2020-06-25\toolset\x64\nvencc\nvencc64.exe --version
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] NVEncC (x64) 5.08 (r1585) by rigaya, Jul 1 2020 15:17:08 (VC 1916/Win/avx2)
[2020-07-01][12:02:46] [NVENC API v9.1, CUDA 10.1]
[2020-07-01][12:02:46] reader: raw, y4m, avi, avs, vpy, avsw, avhw [H.264/AVC, H.265/HEVC, MPEG2, VP8, VP9, VC-1, MPEG1, MPEG4]
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] WARNING: Your version of NVEncC is newer than the latest tested version, take care!
[2020-07-01][12:02:46] This application works best with NVEncC version 5.6. Newer versions may work or not.
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] Detect video source version:
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] Creating process:
[2020-07-01][12:02:46] "C:\Program Files\VapourSynth\core\vspipe.exe" --version
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] VapourSynth Video Processing Library
[2020-07-01][12:02:46] Copyright (c) 2012-2020 Fredrik Mellbin
[2020-07-01][12:02:46] Core R50
[2020-07-01][12:02:46] API R3.6
[2020-07-01][12:02:46] Options: -
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] > NVEncC version: 5.80 [rev #1585]
[2020-07-01][12:02:46] > VapourSynth version: r50 (API r3)
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] --- GET SOURCE INFO ---
[2020-07-01][12:02:46]
[2020-07-01][12:02:46] Creating process:
[2020-07-01][12:02:46] "C:\Program Files\VapourSynth\core\vspipe.exe" --info "I:\\pacific rim.vpy" -
[2020-07-01][12:02:46]
[2020-07-01][12:02:47] Width: 3840
[2020-07-01][12:02:47] Height: 2160
[2020-07-01][12:02:47] Frames: 188855
[2020-07-01][12:02:47] FPS: 24000/1001 (23.976 fps)
[2020-07-01][12:02:47] Format Name: YUV420P10
[2020-07-01][12:02:47] Color Family: YUV
[2020-07-01][12:02:47] Alpha: No
[2020-07-01][12:02:47] Sample Type: Integer
[2020-07-01][12:02:47] Bits: 10
[2020-07-01][12:02:47] SubSampling W: 1
[2020-07-01][12:02:47] SubSampling H: 1
[2020-07-01][12:02:47]
[2020-07-01][12:02:47] Resolution: 3840 x 2160
[2020-07-01][12:02:47] Frame Rate: 24000/1001
[2020-07-01][12:02:47] No. Frames: 188855
[2020-07-01][12:02:47]
[2020-07-01][12:02:47] --- ENCODING VIDEO ---
[2020-07-01][12:02:47]
[2020-07-01][12:02:47] Creating input process:
[2020-07-01][12:02:47] "C:\Program Files\VapourSynth\core\vspipe.exe" --y4m "I:\\pacific rim.vpy" -
[2020-07-01][12:02:47]
[2020-07-01][12:02:47] WARNING: Custom parameter "--frames" will be ignored in Pipe'd mode!
[2020-07-01][12:02:47]
[2020-07-01][12:02:47] Creating encoder process:
[2020-07-01][12:02:47] C:\Users\LUIS\Desktop\x264_launcher.2020-06-25\toolset\x64\nvencc\nvencc64.exe
--codec hevc --preset performance --cqp 30 --profile main10
--master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50)
--max-cll 2465,823
--chromaloc 2 --colormatrix bt2020nc --colorprim bt2020 --transfer smpte2084 --repeat-headers
--output "T:\\PACIFIC RIM.hevc" --y4m --input -

[2020-07-01][12:02:47]
[2020-07-01][12:02:50] --------------------------------------------------------------------------------
[2020-07-01][12:02:50] T:\\PACIFIC RIM.hevc
[2020-07-01][12:02:50] --------------------------------------------------------------------------------
[2020-07-01][12:02:50] Max B frames are 0 frames.
[2020-07-01][12:02:50] NVEncC (x64) 5.08 (r1585) by rigaya, Jul 1 2020 15:17:08 (VC 1916/Win/avx2)
[2020-07-01][12:02:50] OS Version Windows 10 x64 (14393)
[2020-07-01][12:02:50] CPU Intel Core i7-6900K @ 3.20GHz [TB: 3.50GHz] (8C/16T)
[2020-07-01][12:02:50] GPU #0: GeForce GTX 1080 Ti (3584 cores, 1670 MHz)[PCIe3x16][445.87]
[2020-07-01][12:02:50] NVENC / CUDA NVENC API 9.1, CUDA 11.0, schedule mode: auto
[2020-07-01][12:02:50] Input Buffers CUDA, 13 frames
[2020-07-01][12:02:50] Input Info y4m(yv12(10bit))->p010 [AVX2], 3840x2160, 24000/1001 fps
[2020-07-01][12:02:50] Vpp Filters copyHtoD
[2020-07-01][12:02:50] Output Info H.265/HEVC main10 @ Level auto
[2020-07-01][12:02:50] 3840x2160p 1:1 23.976fps (24000/1001fps)
[2020-07-01][12:02:50] Encoder Preset performance
[2020-07-01][12:02:50] Rate Control CQP I:30 P:30 B:30
[2020-07-01][12:02:50] Lookahead off
[2020-07-01][12:02:50] GOP length 240 frames
[2020-07-01][12:02:50] B frames 0 frames [ref mode: disabled]
[2020-07-01][12:02:50] Ref frames 3 frames
[2020-07-01][12:02:50] AQ off
[2020-07-01][12:02:50] CU max / min auto / auto
[2020-07-01][12:02:50] VUI matrix:bt2020nc,colorprim:bt2020,transfer:smpte2084,chromaloc:topleft
[2020-07-01][12:02:50] MasteringDisp G(0.265000 0.690000) B(0.150000 0.060000) R(0.680000 0.320000)
[2020-07-01][12:02:50] WP(0.312700 0.329000) L(4000.000000 0.005000)
[2020-07-01][12:02:50] MaxCLL/MaxFALL 2465/823
[2020-07-01][12:02:50] Others mv:auto repeat-headers
[2020-07-01][12:48:45] encoded 188855 frames, 68.51 fps, 4745.73 kbps, 4456.20 MB
[2020-07-01][12:48:45] encode time 0:45:56, CPU: 8.4, GPU: 35.4, VE: 32.4, VD: 39.3, GPUClock: 1936MHz, VEClock: 1645MHz
[2020-07-01][12:48:45] frame type IDR 787
[2020-07-01][12:48:45] frame type I 787, total size 40.78 MB
[2020-07-01][12:48:45] frame type P 188068, total size 4415.41 MB
[2020-07-01][12:48:45] vpyp [info]: Output 188855 frames in 2757.37 seconds (68.49 fps)
[2020-07-01][12:48:45] Final file size is 4.35 GB bytes.
[2020-07-01][12:48:45]
[2020-07-01][12:48:45] --- COMPLETED ---
[2020-07-01][12:48:45]
[2020-07-01][12:48:45] Job finished at 2020-07-01, 12:48:45. Process took 45 minutes, 59 seconds.

[gonca]

Finished a remux and it seems to work
FF, REW and CHP skips

[jdobbs]

I think the wait is over
5.08 is outThe issue is still there. It will probably have to be fixed by NVIDIA.

It's very obvious. Try this:

1. Run NVENCC with the --repeat-headers parameter
2. Open up Windows Task Manager and click on "Details"
3. Watch the memory usage for NVENCC.EXE.

The application's memory usage will continually rise (pretty quickly) until it eventually runs out and the app crashes. It's just more obvious on the 32 bit version because of 32 memory limitations.

[jdobbs]

Finished a remux and it seems to work
FF, REW and CHP skips
Even if you use the 64 bit version, the memory usage keeps growing (at least on my system). But the application is less likely to crash since 64 bit apps have much more memory available. I can use the --repeat-headers on the 64 bit version with a 2 1/2 hour movie and it will complete. But... the application is using about 600 Megabytes when it starts then slowly increases to point at which it is using over 2 GigaBytes when it finishes.

Who knows? It may act differently on your card and/or drivers.

[gonca]

Maybe a driver related issue, memory usage is constant at about 582 MB on my GTX1080ti
Driver is 445.87

[cartman0208]

I don't see a lot of memory growth, even on the 32bit version ... starts at 750MB and finishes with 850MB used by nvencc.exe

What I also noticed ... no matter what preset or rate factor ... the processing speed stays the same for a given resolution ... 4K is always around 75fps for me :cool:

Graphics driver was updated yesterday (451.48), but I'm not on Win10 May 2020 update yet, if that helps.

PS C:\WINDOWS\system32> U:\Temp\nvenc\NVEncC.exe --cqp 25 --codec h265 --preset quality --profile main10 --level 5.1 --output-depth 10 --max-bitrate 30000 --aq --aq-temporal --output-buf 128 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --colormatrix bt2020nc --colorprim bt2020 --transfer smpte2084 --max-cll "1000,0" --chromaloc 2 --output "U:\Temp\ALITA_BATTLE_ANGEL_temp\ALITA_BATTLE_ANGEL.hevc" --input "U:\Temp\ALITA_BATTLE_ANGEL_temp\ALITA_BATTLE_ANGEL.h265" --repeat-headers

--------------------------------------------------------------------------------
U:\Temp\ALITA_BATTLE_ANGEL_temp\ALITA_BATTLE_ANGEL.hevc
--------------------------------------------------------------------------------
NVEncC (x86) 5.08 (r1585) by rigaya, Jul 1 2020 14:48:28 (VC 1900/Win/avx2)
OS Version Windows 10 x64 (18363)
CPU Intel Core i7-6800K @ 3.40GHz [TB: 3.80GHz] (6C/12T)
GPU #0: GeForce GTX 1660 Ti (1536 cores, 1770 MHz)[2147483.64]
NVENC / CUDA NVENC API 9.1, CUDA 11.0, schedule mode: auto
Input Buffers CUDA, 16 frames
Input Info avcuvid: H.265/HEVC, 3840x2160, 24000/1001 fps
Vpp Filters copyDtoD
Output Info H.265/HEVC main10 @ Level 5.1
3840x2160p 1:1 23.976fps (24000/1001fps)
Encoder Preset quality
Rate Control CQP I:25 P:25 B:25
Lookahead off
GOP length 240 frames
B frames 3 frames [ref mode: disabled]
Ref frames 3 frames, MultiRef L0:auto L1:auto
AQ on
CU max / min auto / auto
VUI matrix:bt2020nc,colorprim:bt2020,transfer:smpte2084,chromaloc:topleft
MasteringDisp G(0.265000 0.690000) B(0.150000 0.060000) R(0.680000 0.320000)
WP(0.312700 0.329000) L(999.999975 0.000100)
MaxCLL/MaxFALL 1000/0
Others mv:auto repeat-headers

encoded 175440 frames, 76.88 fps, 7280.96 kbps, 6351.12 MB
encode time 0:38:02, CPU: 9.8%, GPU: 7.4%, VE: 99.2%, VD: 20.6%
frame type IDR 731
frame type I 731, total size 70.98 MB
frame type P 43860, total size 2313.22 MB
frame type B 130849, total size 3966.92 MB

Edit: 1080p runs at 175fps stable with above settings, no big memory increase either...

[Mike-uk]

I don't see a lot of memory growth, even on the 32bit version ... starts at 750MB and finishes with 850MB used by nvencc.exe

What I also noticed ... no matter what preset or rate factor ... the processing speed stays the same for a given resolution ... 4K is always around 75fps for me :cool:

Graphics driver was updated yesterday (451.48), but I'm not on Win10 May 2020 update yet, if that helps.


[CODE]
--------------------------------------------------------------------------------
U:\Temp\ALITA_BATTLE_ANGEL_temp\ALITA_BATTLE_ANGEL.hevc
--------------------------------------------------------------------------------


where is your --avhw to enable fully hardware encode ?

[cartman0208]

Forgot about it ...
Maybe it was auto detected?

from the help text...
--avhw use libavformat + hw decode for input

Does it matter what is used for decoding?
Just started another run ... not much of a difference in speed

[jdobbs]

Maybe a driver related issue, memory usage is constant at about 582 MB on my GTX1080ti
Driver is 445.87I'm using Driver 451.48, dated June 24th, 2020 on a GTX1660

[jdobbs]

I don't see a lot of memory growth, even on the 32bit version ... starts at 750MB and finishes with 850MB used by nvencc.exe

What I also noticed ... no matter what preset or rate factor ... the processing speed stays the same for a given resolution ... 4K is always around 75fps for me :cool:

Graphics driver was updated yesterday (451.48), but I'm not on Win10 May 2020 update yet, if that helps.



--------------------------------------------------------------------------------
U:\Temp\ALITA_BATTLE_ANGEL_temp\ALITA_BATTLE_ANGEL.hevc
--------------------------------------------------------------------------------
NVEncC (x86) 5.08 (r1585) by rigaya, Jul 1 2020 14:48:28 (VC 1900/Win/avx2)
OS Version Windows 10 x64 (18363)
CPU Intel Core i7-6800K @ 3.40GHz [TB: 3.80GHz] (6C/12T)
GPU #0: GeForce GTX 1660 Ti (1536 cores, 1770 MHz)[2147483.64]
NVENC / CUDA NVENC API 9.1, CUDA 11.0, schedule mode: auto
Input Buffers CUDA, 16 frames
Input Info avcuvid: H.265/HEVC, 3840x2160, 24000/1001 fps
Vpp Filters copyDtoD
Output Info H.265/HEVC main10 @ Level 5.1
3840x2160p 1:1 23.976fps (24000/1001fps)
Encoder Preset quality
Rate Control CQP I:25 P:25 B:25
Lookahead off
GOP length 240 frames
B frames 3 frames [ref mode: disabled]
Ref frames 3 frames, MultiRef L0:auto L1:auto
AQ on
CU max / min auto / auto
VUI matrix:bt2020nc,colorprim:bt2020,transfer:smpte2084,chromaloc:topleft
MasteringDisp G(0.265000 0.690000) B(0.150000 0.060000) R(0.680000 0.320000)
WP(0.312700 0.329000) L(999.999975 0.000100)
MaxCLL/MaxFALL 1000/0
Others mv:auto repeat-headers

encoded 175440 frames, 76.88 fps, 7280.96 kbps, 6351.12 MB
encode time 0:38:02, CPU: 9.8%, GPU: 7.4%, VE: 99.2%, VD: 20.6%
frame type IDR 731
frame type I 731, total size 70.98 MB
frame type P 43860, total size 2313.22 MB
frame type B 130849, total size 3966.92 MB

Edit: 1080p runs at 175fps stable with above settings, no big memory increase either...Part of that might be because you are using GOPs of 240 frames. That's 10 times larger than what it would need to be for a UHD-BD encode. The --repeat-headers would not be activated as often and would probably not hit the routine that causes the memory leak as often. Try adding --gop-len 24 and see what happens.

[Edit] Yeah. I just set the GOP length to 240 frames and it is barely growing at all... but, of course, that encode would fail to meet the UHD-BD standard. I would assume that it would also mean that as you attempt to fast forward, each picture step would jump 10 seconds instead of 1. The table used for these actions only logs IDR positions.

Finished a remux and it seems to work FF, REW and CHP skips
I just went back and looked at your post again as well... and you are also using the default 240 frame GOP. That's probably why you're not seeing the issue as well. You are only having to insert the SPS/VPS/PPS once every 10 seconds instead of once per second. The headers are only inserted on the IDR frame that begins a GOP.

[jdobbs]

Here's a look at memory usage at the start of an encode and then after 35,000 frames. Considering that a 2 hour movie would be 172,627 frames, you can see how this can become an issue.

[Mike-uk]

am i right in seeing nvencc uses SDK version 9.1, i think there is a version 10 now ??, unfortunatly that would mean we need to wait for nvencc to compile sdk 10 versions

mayby ask him if he intends to compile a SDK 10 verstion ? mayby that will solve the memory leak

What's new in Video Codec SDK 10
New H.264 NVENC presets for improved flexibility and granularity
Finer control of rate control modes
Use-case Setting (also referred to as Tuning information)
NVDEC Support for GA100

[jdobbs]

I think the bottom line for now is that I am going to have to insert the headers myself from within BD-RB, which will increase the overall job time by about 10 or 15 minutes. It's a shame, but based on the last response I saw, I have doubts that the issue is going to be addressed. Apparently no one except me is even attempting to create a UHD-BD that is standards compliant (at least with NVENCC), or the --repeat-headers issue would have been brought up long ago.

[gonca]

I should have checked the cmd line a little better
Still, 45 min encode and 15 min clean up for 4K movie isn't bad
By the way, username eddie haskell
Leave it to Beaver fan?

[Mike-uk]

how do you view if repeat headers worked ?? i tried another encoder that uses nvencc and added --repeat-headers and it started off allocating 1,2 gig of memory and stayed around there but no idea if headers are repeated

[jdobbs]

I should have checked the cmd line a little better
Still, 45 min encode and 15 min clean up for 4K movie isn't bad
By the way, username eddie haskell
Leave it to Beaver fan?I watched it after school when I was a kid. Eddie Haskell was quite a character -- I've been using that name for one thing or another for years. If you look hard enough you might even find the name "Haskell Industries" buried somewhere in the BD Rebuilder code...

[jdobbs]

how do you view if repeat headers worked ?? i tried another encoder that uses nvencc and added --repeat-headers and it started off allocating 1,2 gig of memory and stayed around there but no idea if headers are repeatedIt's not easy without the right tools. I have an HEVC browser.

If you're good with a hex editor, you can find the delimiters between headers, slices etc by searching for the start code delimiter (00 00 00 01) -- it is prohibited from appearing anywhere else in the elementary stream. But even if you find the delimiters you'll need to reference the H265 standard (T-REC-H.265-201802-I) to find the format of all the segments that might follow a delimeter (see page 68). The standard is available for free download as a PDF.

The best way to see if the headers are there is to use TSMUXER to create a UHD-BD structure and play it back on a UHD compatible BD player. If FF/REW works... it's probably safe to assume the headers are repeated.

Just out of curiosity... what is the other encoder? It would likely be random luck if it would use the same command line parameter. I think NVENCC uses it because I suggested it (so it would match the parameter in X265).

[GreasyGreedo]

Hello,

I tried searching to see if this problem has been reported otherwise, but didn't see it.

When I author a UHD disc with multiple movie files (quick reauthored import), the subtitles are lost from the final disc. I have not had this problem with HD discs. Is there some difference that prevents the subtitles from being present on a UHD disc of this type?

[cartman0208]

[Edit] Yeah. I just set the GOP length to 240 frames and it is barely growing at all... but, of course, that encode would fail to meet the UHD-BD standard. I would assume that it would also mean that as you attempt to fast forward, each picture step would jump 10 seconds instead of 1. The table used for these actions only logs IDR positions.



Ok, so that's why I saw blocky artifacts for several seconds when jumping to random positions in the SW Player...
So I started a new run with gop-len 24 and the memory increase is actually higher ... started out at around 600 and went up to 1500MB after 180000 frames.
Maybe with a 3hr movie file the 2GB mark would have cracked ... maybe...

Then I tried your commandline and an 1080p video ... stable at around 300MB, no increase at all
The only difference ... I didn't use the keyfile-parameter
.\NVEncC.exe --avhw -i U:\Temp\Spectre_temp\Spectre.h264 --codec h264 --preset quality --bluray --qp-min 0 --vbr 22429 --sar 1:1 --aud --pic-struct --vbv-bufsize 30000 --max-bitrate 35000 --gop-len 24 -o U:\Temp\Spectre_temp\Spectre.264 --repeat-headers
--------------------------------------------------------------------------------
U:\Temp\Spectre_temp\Spectre.264
--------------------------------------------------------------------------------
NVEncC (x86) 5.08 (r1585) by rigaya, Jul 1 2020 14:48:28 (VC 1900/Win/avx2)
OS Version Windows 10 x64 (18363)
CPU Intel Core i7-6800K @ 3.40GHz [TB: 3.80GHz] (6C/12T)
GPU #0: GeForce GTX 1660 Ti (1536 cores, 1770 MHz)[2147483.64]
NVENC / CUDA NVENC API 9.1, CUDA 11.0, schedule mode: auto
Input Buffers CUDA, 20 frames
Input Info avcuvid: H.264/AVC, 1920x1080, 24000/1001 fps
Vpp Filters copyDtoD
Output Info H.264/AVC high @ Level auto
1920x1080p 1:1 23.976fps (24000/1001fps)
Encoder Preset quality
Rate Control VBR
Bitrate 22429 kbps (Max: 35000 kbps)
Target Quality auto
Initial QP I:20 P:23 B:25
QP range I:0-51 P:0-51 B:0-51
VBV buf size 30000 kbit
Lookahead off
GOP length 24 frames
B frames 3 frames [ref mode: disabled]
Ref frames 3 frames, MultiRef L0:auto L1:auto
AQ off
Others mv:auto cabac deblock adapt-transform:auto bdirect:auto aud pic-struct repeat-headers

encoded 213072 frames, 412.48 fps, 21838.53 kbps, 23135.71 MB
encode time 0:08:36, CPU: 9.5%, GPU: 7.1%, VE: 96.2%, VD: 78.7%
frame type IDR 8878
frame type I 8878, total size 1702.42 MB
frame type P 53268, total size 8475.27 MB
frame type B 150926, total size 12958.02 MB

Apparently I cannot reproduce the error ... only a memory increase :o

[jdobbs]

@cartman0208

I removed the keyfile parameter and the memory leak persists for me. Not sure how my test differs from yours. As for the encode failure... I think the problem would also depend on the source you are using. So it will happen, it's just a matter of time. You actually need the keyfile to make sure there is an IDR frame at each chapter point.

But... I have good news. If you change the output format from an elementary stream (.hevc) to a container (e.g. .m2ts)... the problem seems to go away. That provides a good workaround that won't require BD-RB to have to rewrite the entire HEVC stream! I should be able to use the .m2ts as an input file for the TSMUXER muxing. It'll require some code changes -- but I don't think it should be anything too extreme.

My thanks to jkiku101 for experimenting with encodes and finding this potential workaround!

[jdobbs]

Hello,

I tried searching to see if this problem has been reported otherwise, but didn't see it.

When I author a UHD disc with multiple movie files (quick reauthored import), the subtitles are lost from the final disc. I have not had this problem with HD discs. Is there some difference that prevents the subtitles from being present on a UHD disc of this type?I can't think of a difference. But I'll look and see.

[cartman0208]

@cartman0208

I removed the keyfile parameter and the memory leak persists for me. Not sure how my test differs from yours. As for the encode failure... I think the problem would also depend on the source you are using. So it will happen, it's just a matter of time. You actually need the keyfile to make sure there is an IDR frame at each chapter point.

But... I have good news. If you change the output format from an elementary stream (.hevc) to a container (e.g. .m2ts)... the problem seems to go away. That provides a good workaround that won't require BD-RB to have to rewrite the entire HEVC stream! I should be able to use the .m2ts as an input file for the TSMUXER muxing. It'll require some code changes -- but I don't think it should be anything too extreme.

My thanks to jkiku101 for experimenting with encodes and finding this potential workaround!

Ok, then maybe it's really my 1909 Win10 Build for which I did not receive an update yet ... and 2004 is messed up with memory leak ...

Doesn't matter ... good to have a solution for this ... now to find the best settings for awesome quality :D

[Mike-uk]

Doesn't matter ... good to have a solution for this ... now to find the best settings for awesome quality :D

yes being hardware encoding and to contend with x265/264 we need to get the best possible settings dialed in, but will be nice to have the option of considerably faster encodes but slightly less quality with HW, or still the SW/cpu at 16Hrs for absolute best :/

[jdobbs]

yes being hardware encoding and to contend with x265/264 we need to get the best possible settings dialed in, but will be nice to have the option of considerably faster encodes but slightly less quality with HW, or still the SW/cpu at 16Hrs for absolute best :/Yep. It's all about choice.

[gonca]

NVEncC 5.09 is out
Supposed to fix memory leak

[Mike-uk]

NVEncC 5.09 is out
Supposed to fix memory leak

darn you beat me too it :(

[gonca]

Presently testing 5.09, looking promising

[gonca]

Completed fine but have to repeat test
Forgot --repeat-headers in cmd line

[gonca]

cmd line
nvencc64.exe --codec hevc --preset quality --cqp 22 --profile main10 --master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50) --max-cll 902,182 --chromaloc 2 --colormatrix bt2020nc --colorprim bt2020 --transfer smpte2084 --gop-len 24 --lookahead 32 --sar 1:1 --repeat-headers
tested only on software player
no memory leak during encode
appears ok but requires more testing

[gonca]

Burned to disc and played on stand alone player (Sony)
Seems fine

[Mike-uk]

Burned to disc and played on stand alone player (Sony)
Seems fine

nice :),

[Mike-uk]

cmd line

tested only on software player
no memory leak during encode
appears ok but requires more testing

yep can confirm it seems fixed stayed arounf 700 Mb, not tested on a disc as not got any RWs

--avhw --vpp-pad 0,276,0,278 -i F:\Movies\uhd2019\BDMV\STREAM\00014.m2ts --codec hevc --preset quality --profile main10 --output-depth 10 --repeat-headers --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1) --qp-min 0 --vbrhq 0 --vbr-quality 25 --sar 1:1 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 --slices 4 -o "D:\test\VID_00000.hevc

RTX 2070 Super

encoded 175243 frames, 62.57 fps, 12390.37 kbps, 10795.88 MB
encode time 0:46:40, CPU: 7.2%, GPU: 6.3%, VE: 99.2%, VD: 18.1%
frame type IDR 7302
frame type I 7302, total size 1246.97 MB
frame type P 43811, total size 4712.77 MB
frame type B 124130, total size 4836.14 MB

[jdobbs]

Good to hear... I wasn't expecting that one to get fixed so fast. I'll test it tomorrow. Sigh... now I need to go back through my code and remove all the changes I made for outputting to .m2ts. It resulted in a lot more changes than I'd expected, and I was still testing it and finding stuff. Two steps forward and one step back. :)

[cartman0208]

yep can confirm it seems fixed stayed arounf 700 Mb, not tested on a disc as not got any RWs

--avhw --vpp-pad 0,276,0,278 -i F:\Movies\uhd2019\BDMV\STREAM\00014.m2ts --codec hevc --preset quality --profile main10 --output-depth 10 --repeat-headers --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1) --qp-min 0 --vbrhq 0 --vbr-quality 25 --sar 1:1 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 --slices 4 -o "D:\test\VID_00000.hevc

RTX 2070 Super

encoded 175243 frames, 62.57 fps, 12390.37 kbps, 10795.88 MB
encode time 0:46:40, CPU: 7.2%, GPU: 6.3%, VE: 99.2%, VD: 18.1%
frame type IDR 7302
frame type I 7302, total size 1246.97 MB
frame type P 43811, total size 4712.77 MB
frame type B 124130, total size 4836.14 MB

I can also confirm, that there is a stable RAM usage.

And the best part ... it doesn't seem to matter which turing chip ... i tried with Mike's settings and got around 61 fps on my 1660ti, while the card costs about half ;)
Maybe a Titan would make a difference ... but people could buy a decent car in that price range :eek:

BTW: I think with your settings you actually add some height to the video ( pad: [3840x2160]->[3840x2714] (right=0, left=0, top=276, bottom=278) ) ... forgot some dashes? :)

@jdobbs: why not use the code from 0.61.0.5 and start over?

[Mike-uk]

I can also confirm, that there is a stable RAM usage.

And the best part ... it doesn't seem to matter which turing chip ... i tried with Mike's settings and got around 61 fps on my 1660ti, while the card costs about half ;)
Maybe a Titan would make a difference ... but people could buy a decent car in that price range :eek:

hmm yeh interesting encoding fps is the same :confused:

[gonca]

Dedicated encoding hardware is probably the same

[jdobbs]

@jdobbs: why not use the code from 0.61.0.5 and start over? You underestimate how much code it took to integrate it in. I also have implemented a host of other changes since that version. Anyway, I've already reversed most of the code I'd written for it.

[Mike-uk]

Dedicated encoding hardware is probably the same

hmm yeh quite possibly found this on a forum

Turing NVENC is slower at higher quality settings than Pascal NVENC. The NVIDIA application note for NVENC states that at highest quality you should expect no more than 130fps at 1080p (or around 33fps at 4K).

[gonca]

Extra switches (cmd line options) available
NVenc is on a dedicated chip, same chip across the "line" (family) of cards
https://developer.nvidia.com/video-encode-decode-gpu-support-matrix
Chip number and number of encoding chips per card

[MrVideo]

You underestimate how much code it took to integrate it in. I also have implemented a host of other changes since that version. Anyway, I've already reversed most of the code I'd written for it.
Don't you use Revision Control Software? Programs like Git, CVS and SVN (subversion, which I've managed at a work place) would have allowed you to back out those changes. But, as you've pointed out, a little late now.

[jdobbs]

Don't you use Revision Control Software? Programs like Git, CVS and SVN (subversion, which I've managed at a work place) would have allowed you to back out those changes. But, as you've pointed out, a little late now.I am my revision control software.

[cartman0208]

...
Turing NVENC is slower at higher quality settings than Pascal NVENC. ....

I assume, that's because of the B-Frame capability of Turing ... which I don't want to miss, because there is the bitrate saving ...

[jdobbs]

I assume, that's because of the B-Frame capability of Turing ... which I don't want to miss, because there is the bitrate saving ...I'm with you. I want the B-Frame efficiency.

[Mike-uk]

jdobbs do you think you'll add true CPU first pass, then GPU second pass ?? seems the only way to get true 2 pass or maybe add it as an option so people can choose what they want,

maybe get some comparisons of CPU first pass and the lookahead feature to see if theres any quality difference

[MrVideo]

I am my revision control software.
:scared:

[Mike-uk]

Nvidia 3xx series rumoured to be released in aug, wonder if they have improved NVenc, and x266 being developed ohhhh its like xmas

[Mark_Venture]

...
And the best part ... it doesn't seem to matter which turing chip ... i tried with Mike's settings and got around 61 fps on my 1660ti, while the card costs about half ;)
Maybe a Titan would make a difference ... but people could buy a decent car in that price range :eek: So are you saying that as long as its card with a Turing chip, the Cuda cores, clock, etc. doesn't really impact the FPS much when using NVEncC? They're all about the same?

[cartman0208]

So are you saying that as long as its card with a Turing chip, the Cuda cores, clock, etc. doesn't really impact the FPS much when using NVEncC? They're all about the same?

I was wondering, too ...
But i used the same settings as Mike-uk, only a different source (with the same dimensions)
I could try different sources, but my experience so far was an almost unnoticable FPS change, even when changing presets.
We need someone with RTX 2060 / 2080 to verify :rolleyes:

[jdobbs]

I was wondering, too ...
But i used the same settings as Mike-uk, only a different source (with the same dimensions)
I could try different sources, but my experience so far was an almost unnoticable FPS change, even when changing presets.
We need someone with RTX 2060 / 2080 to verify :rolleyes:I'm seeing quite a bit of difference between presets when running against the same source. The "performance" preset, for example, is running much faster than "default" or "quality". It can also change based on whether I am using --vbr or --vbrhq.

For example, on a specific UHD source I'm using for testing with preset "performance" and "--vbr" I am getting 127.49 fps -- the same source with "quality" and "--vbrhq" it is doing 77.67 fps (with an otherwise identical command line).

I am also seeing fluctuations depending upon the size (on disc) of the source. An imported 10GB source M2TS encodes faster than a full 60GB untouched source.

The largest factor to speed I've seen (as you might expect) is whether I am using --avs as the input type as opposed to --avhw or --avsw.

[cartman0208]

Ok, I didn't do extended tests ... only constant QP on a small source file ... I wanted to check out resulting file sizes

[Mark_Venture]

I'm seeing quite a bit of difference between presets when running against the same source. The "performance" preset, for example, is running much faster than "default" or "quality". It can also change based on whether I am using --vbr or --vbrhq.

For example, on a specific UHD source I'm using for testing with preset "performance" and "--vbr" I am getting 127.49 fps -- the same source with "quality" and "--vbrhq" it is doing 77.67 fps (with an otherwise identical command line).

I am also seeing fluctuations depending upon the size (on disc) of the source. An imported 10GB source M2TS encodes faster than a full 60GB untouched source.

The largest factor to speed I've seen (as you might expect) is whether I am using --avs as the input type as opposed to --avhw or --avsw.you mention different presets. I was wondering about using the same source, with the same preset, across different cards.

cartman0208 indicated using the same command line that Mike-uk posted, resulted in similar FPS using different video cards (GTX1660ti vs RTX 2070 Super) based on their posts. And using the same string Mike-uk posted on a UHD rip on my PC also came out with the same FPS (using GTX1660ti here).

When all is said and done, it will be interesting to compare results if we could each run tests on our respective systems using the SAME pre-sets and (if possible) the same source.

[gonca]

you mention different presets. I was wondering about using the same source, with the same preset, across different cards.

cartman0208 indicated using the same command line that Mike-uk posted, resulted in similar FPS using different video cards (GTX1660ti vs RTX 2070 Super) based on their posts. And using the same string Mike-uk posted on a UHD rip on my PC also came out with the same FPS (using GTX1660ti here).

When all is said and done, it will be interesting to compare results if we could each run tests on our respective systems using the SAME pre-sets and (if possible) the same source.
https://forum.doom9.org/showthread.php?p=1917767#post1917767

[deadfrog]

I just downloaded NVEncC 5.09 64 bit. I have a Ryzen 3900 with 128gb ram and a RTX2060. If someone could give me the command line they would like tested I can run it against Avengers endgame and see what kind of frames/sec I get.

[Mike-uk]

I just downloaded NVEncC 5.09 64 bit. I have a Ryzen 3900 with 128gb ram and a RTX2060. If someone could give me the command line they would like tested I can run it against Avengers endgame and see what kind of frames/sec I get.

--avhw --vpp-pad 0,276,0,278 -i F:\Movies\uhd2019\BDMV\STREAM\00014.m2ts --codec hevc --preset quality --profile main10 --output-depth 10 --repeat-headers --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1) --qp-min 0 --vbrhq 0 --vbr-quality 25 --sar 1:1 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 --slices 4 -o "D:\test\VID_00000.hevc

[cartman0208]

I had to do some small corrections to make it work (with powershell):
"C:\path\to\nvenc\nvencc64.exe" --avhw --vpp-pad 0,276,0,278 -i "X:\path\to\input.file" --codec hevc --preset quality --profile main10 --output-depth 10 --repeat-headers --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --qp-min 0 --vbrhq 0 --vbr-quality 25 --sar 1:1 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 --slices 4 -o "X:\path\to\output.file"

Also I coudn't make out any difference in encoding speed between 32bit and 64bit version.

[jdobbs]

Also I coudn't make out any difference in encoding speed between 32bit and 64bit version.I also see no difference in speed between 32 bit and 64 bit. That makes sense, since the actual encoding is being done by hardware anyway.

The one thing I did notice is that (like x264 and x265) you can't use the 64 bit version with a standard (not "+" version) of AVISYNTH. So in BD-Rebuilder I will only be including the 32 bit version of NCEncc in the TOOLS folder.

I have NVENCC working reliably within BD Rebuilder. I'm now working on the function of sizing predictions for constant quality mode (CQM). Since prediction (X264/x265 CRF) never really worked well with HEVC sources in the past, I'm also fixing that in the prediction algorithm. There are a few other minor support functions that will have to be adjusted as well.

All-in-all I'm pretty pleased with what I'm seeing (especially for UHD sources). The only real disadvantage of NVENC is the lack of a true 2-pass mode. But I don't think that's ever likely with a HW encoder.
"C:\path\to\nvenc\nvencc64.exe" --avhw --vpp-pad 0,276,0,278 -i "X:\path\to\input.file" --codec hevc --preset quality --profile main10 --output-depth 10 --repeat-headers --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --qp-min 0 --vbrhq 0 --vbr-quality 25 --sar 1:1 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 --slices 4 -o "X:\path\to\output.file"By the way, the only reason "--vpp-pad 0,276,0,278" was a part of that command line is because the file I was using was imported from an MKV and the black padding had been removed in the original MKV file. So, during import, BD-RB sensed the sizing irregularity and inserted the necessary padding to make it UHD-BD compliant. Some of the other portions of the command line (e.g. --master-display) can also be specific to a source (UHD-BD keeps track of it, and BD-RB pulls the information to make sure the reencode matches). With recent changes to NVENCC you would also want to add the "--repeat-headers" parameter to it if the output is targeted at a UHD-BD disc.

[Mike-uk]

The only real disadvantage of NVENC is the lack of a true 2-pass mode. But I don't think that's ever likely with a HW encoder.


can you not do a CPU true first pass ??
ou can do 2-pass in a few popular encoding programs, but the .stats file that is created is blank. The only way I've found to actually get a true 2-Pass is to run the first pass on the CPU, save the stats file and then use that during a second pass using NVENC which is a cumbersome process. Every other way I've encountered is no different than a 1-pass encode.

[jdobbs]

can you not do a CPU true first pass ??
ou can do 2-pass in a few popular encoding programs, but the .stats file that is created is blank. The only way I've found to actually get a true 2-Pass is to run the first pass on the CPU, save the stats file and then use that during a second pass using NVENC which is a cumbersome process. Every other way I've encountered is no different than a 1-pass encode.How can you get NVENC to read a stats file? I must have missed that parameter.

But, even if it could, running the first pass on the CPU kinda' defeats the purpose (speed) of NVENCC.

Right now all NVENCC can do is a 2-pass within a short range of frames... which isn't really a 2 pass. Honestly, though, I'm pretty satisfied with the output quality of 1 pass anyhow, and the CQM output looks really good.

[cartman0208]

How do you make sure, you hit the requested target size?
I imagine thats pretty hard with CQM ...

[Sharc]

How do you make sure, you hit the requested target size?
I imagine thats pretty hard with CQM ...
Possibly using the same (or similar) prediction algorithm which has been available since long for CPU based x264 CRF encodes?

[jdobbs]

Possibly using the same (or similar) prediction algorithm which has been available since long for CPU based x264 CRF encodes?Yeah. I built a prediction algorithm for BD Rebuilder so it could do targeted sizing using CRF in X264/X265. So for NVENC, I just had to do a large group of sample encodes in order to build its prediction tables.

I've done several tests and it seems to be working well enough. I also modified the way in which HEVC sources are sampled -- AVISYNTH's SelectRangeEvery() was getting terrible picture glitches with hevc, and I couldn't use if for UHD-BD anyway, because it didn't support HDR.

[cartman0208]

Yeah. I built a prediction algorithm for BD Rebuilder so it could do targeted sizing using CRF in X264/X265. So for NVENC, I just had to do a large group of sample encodes in order to build its prediction tables.


You mean like: take a sample of 24 frames from every minute of the movie ? :)

Oh, and what I just noticed ... is BD-RB cabable of HDR10+ ?
(sorry if that topic came up already)
because MediaInfo shows me on very few movies
HDR format : SMPTE ST 2094 App 4, Version 1, HDR10+ Profile A compatible
and after the BD-RB conversion:
HDR format : SMPTE ST 2086, HDR10 compatible

Or did I miss a secret switch? :eek:

[jdobbs]

You mean like: take a sample of 24 frames from every minute of the movie ? :)

Oh, and what I just noticed ... is BD-RB cabable of HDR10+ ?
(sorry if that topic came up already)
because MediaInfo shows me on very few movies

and after the BD-RB conversion:


Or did I miss a secret switch? :eek:The AVISYNTH sampling is configurable. See HIDDENOPTS.TXT: SAMPLE_GROUP=n n = Number of frames in each sample group for CRF estimation
SAMPLE_SIZE=n n = Number of frames in each sample for CRF estimation (size/group = sample percentage)The default values change depending upon on source framerates. But typically they are a 1% sample (e.g. 24fps uses a 48 frame sample [SAMPLE_SIZE] for every 4800 frames [SAMPLE_GROUP]).

On an HEVC source (in the upcoming version) a sample M2TS is created which consists of a 1% sample across multiple locations within the source.

BD-RB supports HDR10 and Dolby Vision. I don't think I've looked at HDR10+ yet (it's been a while), but frankly I am skeptical of all of these "extensions" to HDR10 as I think they are getting ridiculous and may in the same category as "HD Audio" (which is nothing beyond a marketing gimmick that has been proven scientifically as nonsense). Of course that comment will likely result in responses from people with "magic ears" who will say how they can tell the difference (even though what they actually hear is increased baseline volume that the marketeers have implemented in HD audio to try and make it appear as if there is an actual difference). Double blind tests show that (other than the additional channels available available in HD formats) Dolby Digital 5.1 at 640Kbs is indistinguishable from an lossless original audio source. Okay, time to step down off my soapbox.

I suppose I will have to look at HDR10+ just to keep the wolves at bay. But my guess is it will soon be replaced by HDR10++ or HDR10+ super-duper-excellent or some such thing. Marketeers have no boundaries (or ethics).

[cartman0208]

thanks for the description.

From my limited knowlege ... HDR10+, almost like DolbyVision, adds dynamic metadata to adjust brightness scene-by-scene, while HDR10 only uses static metadata

[Sharc]

NVEncC v5.10 is out. Supporting multipass ... (didn't try yet)

[jdobbs]

NVEncC v5.10 is out. Supporting multipass ... (didn't try yet)What???

And I was close to posting a test version of BD-RB...

I think I'll test multipass first...

[jdobbs]

I set it to --multipass 2pass-full and it shows it as set while it is running... but the speed seems identical and it appears to only do one pass. I think this may be a mode I read about previously (somewhere), where it does two passes on a limited subset of frames (the lookahead, maybe?). It wouldn't be considered as really two pass.

True two-pass encoding requires a look at the entire stream so bits can be allocated with the entire set of frames under consideration.

With that said, I'll do some testing and see if --multipass results in any noticable improvements.

[Edit] Curiouser and curiouser... you can even set --multipass 2pass-full when using CQM mode. How does that work?
And it appears that two-pass is ON no matter what settings you use. The encode shows 2pass-full mode even when I set --multipass none or --multipass 2pass-quater [SIC] It even says it is on if you leave the --multipass option off completely.

v5.10 is running a little slower than v5.09 and the output size with the same setting is a little larger with v5.10 (with the same CQM value)... so something has changed. I'm just not sure what. Maybe it's because 2 pass is stuck on no matter the setting? No idea.

So....

:confused:

[Sharc]

it requires nvidia driver 445.87 or later (SDK API 10.0).
Can't test it as I am away from home ....

Edit:
Perhaps this explains it
https://github.com/rigaya/NVEnc/issues/248

Edit2:
NVIDIA's multipass description / definition:
https://docs.nvidia.com/video-technologies/video-codec-sdk/nvenc-video-encoder-api-prog-guide/index.html#multi-pass-frame-phencoding

[jdobbs]

it requires nvidia driver 445.87 or later (SDK API 10.0).
Can't test it as I am away from home ....

Edit:
Perhaps this explains it
https://github.com/rigaya/NVEnc/issues/248I'm currently using nvidia driver 451.48... so that's not it.

[Sharc]

NVIDIA's multipass explanation from their doc:
https://docs.nvidia.com/video-technologies/video-codec-sdk/nvenc-video-encoder-api-prog-guide/index.html#multi-pass-frame-phencoding

Multi pass frame encoding
When determining the QP to use for encoding a frame, it is beneficial if NVENC knows the overall complexity of the frame to distribute the available bit budget in the most optimal manner. In some situations, multi-pass encoding may also help catch larger motion between frames. For this purpose, NVENC supports the following types of multi-pass frame encoding modes:

1-pass per frame encoding (NV_ENC_MULTI_PASS_DISABLED)
2-passes per frame, with first pass in quarter resolution and second pass in full resolution (NV_ENC_TWO_PASS_QUARTER_RESOLUTION)
2-passes per frame, with both passes in full resolution (NV_ENC_TWO_PASS_FULL_RESOLUION).
In 1-pass rate control modes, NVENC estimates the required QP for the macroblock and immediately encodes the macroblock. In 2-pass rate control modes, NVENC estimates the complexity of the frame to be encoded and determines bit distribution across the frame in the first pass. In the second pass, NVENC encodes macroblocks in the frame using the distribution determined in the first pass. As a result, with 2-pass rate control modes, NVENC can distribute the bits more optimally within the frame and can reach closer to the target bitrate, especially for CBR encoding. Note, however, that everything else being the same, performance of 2-pass rate control mode is lower than that of 1-pass rate control mode. The client application should choose an appropriate multi-pass rate control mode after evaluating various modes, as each of the modes has its own advantages and disadvantages. NV_ENC_TWO_PASS_FULL_RESOLUION generates better statistics for the second pass, whereas NV_ENC_TWO_PASS_QUARTER_RESOLUTION results in larger motion vectors being caught and fed as hints to second pass.

[jdobbs]

Thanks for that. That make sense. So it isn't really 2 pass encoding in the traditional sense at all -- it's just 2 passes on a single frame during that frame's encoding.

It looks to me like the new version of NVENCC keeps it in 2-pass-full no matter what setting you specify. I'm sure that's a bug... but probably not a bad one, since 2pass-full is likely the best option in most cases anyhow.

[Edit] I submitted a bug report on GITHUB related to the mode always staying 2pass-full. (or, at least, always reporting 2pass-full)

Interestingly, the encode seems to actually be faster on a UHD source on v5.10 vs. v5.09 -- even with 2pass-full always selected. I'm not sure that that might mean.

[jdobbs]

thanks for the description.

From my limited knowlege ... HDR10+, almost like DolbyVision, adds dynamic metadata to adjust brightness scene-by-scene, while HDR10 only uses static metadataJust an interesting aside on this subject. NVENCC has an option built in in which the additional information associated with HDR10+ can be copied from the original file automatically during encoding.

[cartman0208]

Just an interesting aside on this subject. NVENCC has an option built in in which the additional information associated with HDR10+ can be copied from the original file automatically during encoding.

Yep, found that, too ;)
Actually a lot of parameters can just be copied ... like colormatrix, master-display and so on, even the audio...
https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md

Doesn't that make your job a lot easier?

[jdobbs]

Yep, found that, too ;)
Actually a lot of parameters can just be copied ... like colormatrix, master-display and so on, even the audio...
https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md

Doesn't that make your job a lot easier?Yes, for NVEncC -- but I'll also have to make it work for X265 encoding. That means I'll probably have to create a JSON file from the extracted HEVC file, so it can be referenced from the command line -- which will add about 6-10 minutes to each job.

As for the other settings that can be copied... they are readily available in a BD structure and BD-RB already has the code to extract it and use it. My attention-to-detail tendencies also make me want to have control over things like that rather than "trust" other software.

Just a note on that. In my testing, I'm finding (as you might expect) that X265 is significantly more efficient than the NVIDIA hardware encoder. For example, if you encode some sources with a CQM of 25 using the hardware encoder you will get a file that is twice as large as one created by X265 with a CRF of 25. Of course you also have to factor in that the hardware encode is about 20-40x faster...

[Sharc]

Just a note on that. In my testing, I'm finding (as you might expect) that X265 is significantly more efficient than the NVIDIA hardware encoder. For example, if you encode some sources with a CQM of 25 using the hardware encoder you will get a file that is twice as large as one created by X265 with a CRF of 25. Of course you also have to factor in that the hardware encode is about 20-40x faster...
Would you say that the quality (in terms of metrics or by visual comparison) is about the same for the CQM=25 (HW, h.265) and and CRF=25 (SW, x265) encodes?

[jdobbs]

Would you say that the quality (in terms of metrics or by visual comparison) is about the same for the CQM=25 (HW, h.265) and and CRF=25 (SW, x265) encodes? I'm not sure. I don't like doing subjective comparisons, so I'll have to use AVISYNTH and do some SSIM testing.

More on the "--multipass" thing: It turns out that setting --vbrhq mode automatically sets the encoder to do 2 pass-full. So I'm not sure that there is actually any additional capability associated with that parameter other than it may provide a bit of granularity (with the ability to set 2pass-quarter).

[Mike-uk]

I'm not sure. I don't like doing subjective comparisons, so I'll have to use AVISYNTH and do some SSIM testing.

More on the "--multipass" thing: It turns out that setting --vbrhq mode automatically sets the encoder to do 2 pass-full. So I'm not sure that there is actually any additional capability associated with that parameter other than it may provide a bit of granularity (with the ability to set 2pass-quarter).

well yess compressing around 80 gig to 25 will have its tradeoff in quality, i think for h264 max quality, is like x264 medium not sure with 265

[Mike-uk]

hmm i wonder if the AMD Ryzen Threadripper 3970X Processor (32 Core / 64 Threads , 128 MB Cache, 4.5 GHz Boost) would bring x265 times down ? its only 1.8k for the chip :P

[laserfan]

The discussion of quality settings makes me smile. My first BD backup/conversion, in Oct 2008 before BD-RB was born iirc, was Live Free or Die Hard which as you all know is action-packed. Yet when compressed to less than 4GB DVD-size it looked flippin' awesome the couple times I played it. I will have to break it out sometime and see how it holds-up 12 years later!

:)

[jdobbs]

I've created a test release (v0.61.06) of BD Rebuilder for anyone who would like to experiment and report any issues they see with the new support for NVIDIA/NVENC support.

Please note that in order to use the new capability you must run BD-RB on a system that has an NVIDIA card installed that supports NVENC. You can find out more about which cards can be used at this link (https://developer.nvidia.com/video-encode-decode-gpu-support-matrix). BD-RB does a check when you attempt to select the NVENC encoder (under the SETTINGS menu).

There were a considerable number of changes to this release, so this version should be considered "for testing purposes only", so I'm not updating the first post of this thread -- please try it and let me know your experiences and report any bugs you find.

BD-RB v0.61.06 (https://jammernhilftnichts.de/jdobbs/BD-RBV06106.zip)

Thanks.

[Mark_Venture]

I've created a test release (v0.61.06) of BD Rebuilder for anyone who would like to experiment and report any issues they see with the new support for NVIDIA/NVENC support.

Please note that in order to use the new capability you must run BD-RB on a system that has an NVIDIA card installed that supports NVENC. You can find out more about which cards can be used at this link (https://developer.nvidia.com/video-encode-decode-gpu-support-matrix). BD-RB does a check when you attempt to select the NVENC encoder (under the SETTINGS menu).

There were a considerable number of changes to this release, so this version should be considered "for testing purposes only", so I'm not updating the first post of this thread -- please try it and let me know your experiences and report any bugs you find.

BD-RB v0.61.06 (https://jammernhilftnichts.de/jdobbs/BD-RBV06106.zip)

Thanks.Can I just say, I hate Norton... gives issues on the NVEncC.exe included with BD-RB (says RISK:WS.Reputation.1). didn't have issues with one I downloaded separately.

(had to restore and exclude this)

[cartman0208]

First encode looks pretty awesome, but I wanted to compare more closely, so I tried AviSynth interleave (first time for me) on the m2ts files

Immediately I noticed random artifacts on the reencoded file.

a=DirectShowSource("U:\FullDisc\OLYMPUS_HAS_FALLEN\BDMV\STREAM\00021.m2ts").Subtitle("O", align=2, size=30, text_color=$ffffff)
b=DirectShowSource("U:\BD-Output\OLYMPUS_HAS_FALLEN\BDMV\STREAM\00021.m2ts").Subtitle("NV", align=2, size=30, text_color=$ffffff)
return interleave(a, b)

Playing the resulting file alone is without artifacts...
Any Hints from the AviSynth pro's?

[Mark_Venture]

First encode of ALT-Movie Only (MKV Container, HEVC, NO_Resize, Intact Audio) of Avengers Endgame was quick. ABout 1hr 21 min.
[07/17/20] BD Rebuilder v0.61.06
[12:35:56] Source: AVENGERS_ENDGAME-4K_00004
- Input BD size: 59.49 GB
- Approximate total content: [03:01:11.527]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, HEVC, NO_RESIZE, Intact Audio
- Quality: High Quality (Default)
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[12:35:59] PHASE ONE, Encoding
- [12:35:59] Processing: VID_00055 (1 of 1)
- [12:35:59] Extracting A/V streams [VID_00055]
- [12:56:49] Reencoding video [VID_00055]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 260,656 frames
- [12:56:49] Reencoding: VID_00055, Pass 1 of 1
- [13:45:26] Video Encode complete
- [13:45:26] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (eng): Keeping original audio
[13:45:26]PHASE ONE complete
[13:45:26]PHASE TWO - Rebuild Started
- [13:45:26] Building ALTERNATE OUTPUT Structure
[13:56:22] - Encode and Rebuild complete
[13:56:22] JOB: AVENGERS_ENDGAME-4K finished.



using the following ini...
[Options]
VERSION=0.61.0.6
ENCODER=1
MODE=3
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=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
DECODER=3
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=1
NEROAAC=0
SUPTITLE=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23500
PRIORITY_CLASS=0
TARGET_SIZE=23500
MOVIEONLY_TYPE=40
ALTCRF=19
ALT_TARGET=8096
ALTMETHOD=0
ALTAUTOCROP=0
QUICK_EXTRAS=1
AUDIO_DRC=0
PGSTOSRT=0
ALT_CRF_TARGET=1024
FRIM_SW_DECODE=0
FRIM_SW_ENCODE=0
NVENC_CAPABLE=1

[Paths]
SupTitlePath=C:\Program Files (x86)\AviSynth\plugins\SupTitle.dll
SOURCE_PATH=H:\BLURAY\AVENGERS_ENDGAME-4K\
WORKING_PATH=F:\BLURAY-WORKING\
DGIndexNV=D:\BD_Rebuilder\dgdecnv\DGIndexNV.exe
DGDecNV=D:\BD_Rebuilder\dgdecnv\DGDecodeNV.dll
General
Unique ID : 220642287505551334163210721554557699978 (0xA5FE28AA6D37327D898374BC265A078A)
Complete name : F:\BluRay-Working\AVENGERS_ENDGAME-4K.mkv
Format : Matroska
Format version : Version 2
File size : 27.7 GiB
Duration : 3 h 1 min
Overall bit rate mode : Variable
Overall bit rate : 21.9 Mb/s
Encoded date : UTC 2020-07-17 17:45:32
Writing application : mkvmerge v9.7.1 ('Pandemonium') 32bit
Writing library : libebml v1.3.4 + libmatroska v1.4.5

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 3 h 1 min
Bit rate : 16.1 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (23976/1000) FPS
Original frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.081
Stream size : 20.3 GiB (73%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2

Audio #1
ID : 2
Format : MLP FBA 16-ch
Format/Info : Meridian Lossless Packing FBA with 16-channel presentation
Commercial name : Dolby TrueHD with Dolby Atmos
Codec ID : A_TRUEHD
Duration : 3 h 1 min
Bit rate mode : Variable
Bit rate : 4 777 kb/s
Maximum bit rate : 8 430 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 1 200.000 FPS (40 SPF)
Compression mode : Lossless
Delay relative to video : 1 ms
Stream size : 6.05 GiB (22%)
Language : English
Default : Yes
Forced : No
Number of dynamic objects : 13
Bed channel count : 1 channel
Bed channel configuration : LFE

Audio #2
ID : 3
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Duration : 3 h 1 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 829 MiB (3%)
Service kind : Complete Main
Default : No
Forced : No

Audio #3
ID : 4
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Duration : 3 h 1 min
Bit rate mode : Constant
Bit rate : 320 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 415 MiB (1%)
Language : English
Service kind : Complete Main
Default : No
Forced : No

Text
ID : 5
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 3 h 0 min
Bit rate : 11.5 kb/s
Count of elements : 5266
Stream size : 14.9 MiB (0%)
Language : English
Default : No
Forced : No

Menu
00:00:00.000 : en:00:00:00.000
00:08:06.068 : en:00:08:06.068
00:20:01.867 : en:00:20:01.867
00:26:15.448 : en:00:26:15.448
00:36:57.340 : en:00:36:57.340
00:43:20.764 : en:00:43:20.764
00:48:44.338 : en:00:48:44.338
00:57:36.911 : en:00:57:36.911
01:07:12.778 : en:01:07:12.778
01:16:02.683 : en:01:16:02.683
01:26:25.597 : en:01:26:25.597
01:32:20.284 : en:01:32:20.284
01:38:55.971 : en:01:38:55.971
01:48:12.527 : en:01:48:12.527
01:57:27.081 : en:01:57:27.081
02:05:00.409 : en:02:05:00.409
02:15:06.598 : en:02:15:06.598
02:25:50.616 : en:02:25:50.616
02:34:38.102 : en:02:34:38.102
02:43:04.065 : en:02:43:04.065
02:49:05.510 : en:02:49:05.510
03:01:11.277 : en:03:01:11.277

Original M2TS on disc 59.4 GB, resulting file from BD-RB is 27.6GB, so a nice reduction in size.

Playback on my 1080p monitor looked good. Will check on my 4K TV as soon as I get a chance to step away from my desk.

I also just started a Full Backup to BD-25.. Will post results in a little bit.


NOTE: my graphics card is an EVGA GTX 1660ti XC Ultra Gaming 06G-P4-1267-KR (full PC spec's HERE (https://forum.doom9.org/showpost.php?p=1918386&postcount=45) )

[Sharc]

First encode looks pretty awesome, but I wanted to compare more closely, so I tried AviSynth interleave (first time for me) on the m2ts files

Immediately I noticed random artifacts on the reencoded file.

a=DirectShowSource("U:\FullDisc\OLYMPUS_HAS_FALLEN\BDMV\STREAM\00021.m2ts").Subtitle("O", align=2, size=30, text_color=$ffffff)
b=DirectShowSource("U:\BD-Output\OLYMPUS_HAS_FALLEN\BDMV\STREAM\00021.m2ts").Subtitle("NV", align=2, size=30, text_color=$ffffff)
return interleave(a, b)

Playing the resulting file alone is without artifacts...
Any Hints from the AviSynth pro's?
Don't use DirectShowSource. Make .dgi index files of the 2 files (original and encoded) instead.

[cartman0208]

Don't use DirectShowSource. Make .dgi index files of the 2 files (original and encoded) instead.

.dgi sounds like DGDecNV ... Oh well, seems I have to invest that money ..:p

[Sharc]

BD-RB does a check when you attempt to select the NVENC encoder (under the SETTINGS menu).

Encoding a HD BD 1920x1080 source with NVEnc is done with h264 (AVC) only. I can't select h265 (HEVC). Is this because my 1050ti does not support B-frames for HEVC?
Not that it matters, it's just a question.

[cartman0208]

Encoding a HD BD 1920x1080 source with NVEnc is done with h264 (AVC) only. I can't select h265 (HEVC). Is this because my 1050ti does not support B-frames for HEVC?
Not that it matters, it's just a question.

HEVC is for UHD-BD only ... wouldn't be compliant with (Full-HD) BD
I think BD-RB has always been like that (also with x264/x265) to be compliant with disc standards.

Seems to work for Alternate Encoding though :cool:

[jdobbs]

Encoding a HD BD 1920x1080 source with NVEnc is done with h264 (AVC) only. I can't select h265 (HEVC). Is this because my 1050ti does not support B-frames for HEVC?
Not that it matters, it's just a question.It follows the same rules as X265/X264. The only way to force a 1920x1080 source to HEVC would be with ALTERNATE output.

I am working on that ability -- to create a 1080p HEVC (UHD format) disc -- but I disabled that code for this release because I haven't tested it very well.HEVC is for UHD-BD only ... wouldn't be compliant with (Full-HD) BD
I think BD-RB has always been like that (also with x264/x265) to be compliant with disc standards.

Seems to work for Alternate Encoding though :cool:The UHD standard also allows 1080p using HEVC. So that part should be available soon. See the table below from the Part 3 Whitepaper.

But, just as an aside... I have tried other formats (720p and 480p) using HEVC and UHD (V3) disc output and they also play on my Sony player -- so I might put a hidden option that allows HEVC there as well. It would be a great non-standard-but-working capability for creating series discs, since HEVC looks a lot better at lower bitrates. I'm usually hesitant to step out of the standard -- but I'd bet that most UHD players will accept it since the format/type tables have settings for it.

[cartman0208]

I am working on that ability -- to create a 1080p HEVC (UHD format) disc -- but I disabled that code for this release because I haven't tested it very well.

Can you implement that as Alternate Output setting for HEVC with AC3, too?
Would be a nice addition, because my SamsungTV can't play DTS and some older SmartTV models had trouble playing AAC ...

AC3 just plays everywhere :)

[jdobbs]

Can you implement that as Alternate Output setting for HEVC with AC3, too?
Would be a nice addition, because my SamsungTV can't play DTS and some older SmartTV models had trouble playing AAC ...

AC3 just plays everywhere :)You can easily create a preset that uses AC3 by editing the ALTERNATE.TXT file in the Misc folder. The comment area at the beginning of the file explains the settings. Here's an example you could try:

[00041]
caption=MKV Container, HEVC, NO_RESIZE, Auto-AC3
vEncoder=1
vBitrate=1500
vKeyint=Auto
aBitrate=*
aType=0
vFormat=7
cType=1

I used [00041] because the default ALTERNATE.TXT file has 40 entries in it. Just adjust if yours has more or fewer. You could also replace one of the existing presets if you'd like that better.

Honestly I thought I'd put one in there. I'm surprised that I didn't.

[cartman0208]

You can easily create a preset that uses AC3 by editing the ALTERNATE.TXT file in the Misc folder.

Wow, I've never noticed that file ... :thanks:

[jdobbs]

Encoding a HD BD 1920x1080 source with NVEnc is done with h264 (AVC) only. I can't select h265 (HEVC). Is this because my 1050ti does not support B-frames for HEVC?
Not that it matters, it's just a question.It follows the same rules as X265/X264. The only way to force a 1920x1080 source to HEVC would be with ALTERNATE output.

I am working on that ability -- to create a 1080p HEVC (UHD format) disc -- but I disabled that code for this release because I haven't tested it very well.The UHD standard also allows 1080p using HEVC. So that part should be available soon.If you'd like to experiment with the capability to output 1080p to disc using HEVC into a UHD format, try adding:

UHD_V3_MODE=1

...to your INI file. I haven't tested it much, but I'm pretty sure it would only work in movie-only mode right now. Don't forget to reset it to 0 after playing with it -- as it will try to make normal BD backups into UHD format.

[Edit] Nope... sorry. I just ran a test on a 1080p source and, while it played, BD-RB failed to add the "--repeat-headers" parameter in the encode and FF/REW/CHAP isn't working (for 1080p output). I fixed it for the next release.

[prologic]

Tested BD-RB v0.61.06
With Movie LE_MANS_66 UHD 60gig to BD50 using geforce gtx 1070 card.
Worked a treat .Took about 1 hour to do .Very pleased with the result , on my oppo 203 Player , with all the menus and such .
Here is the log:
[07-18-20] BD Rebuilder v0.61.06
[12:27:33] Source: LE_MANS_66
- Input BD size: 60.18 GB
- Approximate total content: [02:43:59.496]
- Target BD size: 46.26 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Very Good (Very Fast), ABR
- X264 Tweak(s) enabled
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=1 DTS=1 HD=1 Kbs=640
[12:27:33] PHASE ONE, Encoding
- [12:27:33] Processing: VID_00006 (1 of 1)
- [12:27:33] Extracting A/V streams [VID_00006]
- Extracting video streams [VID_00006]
- Extracting audio/subtitle streams [VID_00006]
- [12:33:35] Reencoding video [VID_00006]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 219,511 frames
- Bitrate: 31,380 Kbs
- [12:33:35] Reencoding: VID_00006, Pass 1 of 1
- [13:21:57] Video Encode complete
- [13:21:57] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [13:21:57] Multiplexing M2TS
[13:26:07]PHASE ONE complete
[13:26:07]PHASE TWO - Rebuild Started
- [13:26:07] Rebuilding BD file Structure
[13:26:17] - Encode and Rebuild complete
[13:26:17] JOB: LE_MANS_66 finished.

[cartman0208]

I'm having trouble converting UHD BDs in CQM Mode ... each one I tried so far fails on CQM prediction
[07.18.20] BD Rebuilder v0.61.06
[21:57:28] Source: COLD_PURSUIT
- Input BD size: 78,62 GB
- Approximate total content: [02:04:46.291]
- Target BD size: 47,85 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), CQM
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[21:57:33] PHASE ONE, Encoding
- [21:57:33] Processing: VID_00000 (1 of 14)
- [21:57:33] Extracting A/V streams [VID_00000]
- [21:57:38] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 1.046 frames
- [21:57:38] Performing CQM Prediction...
- Analyzing 17,35 [21:57:42] - Failed video encode, aborted


VBR runs fine

Which one would you suggest for quality?

[jdobbs]

I'm having trouble converting UHD BDs in CQM Mode ... each one I tried so far failes on CQM prediction


VBR runs fine

Which one would you suggest for quality? I think it may be too early to call for quality -- but I suspect it might be CQM. I wouldn't make a wager on that though until a lot more testing is done.

Can you -- right after the encode fails:

1. Copy the content of LASTCMD.TXT (in the BD-RB folder) and post it here.

2. Cut and paste the command line from that file into a DOS prompt window and try to run it, and see what error it gets.

Hmm... I wonder if the routine is inserting a "," instead of a "." when specifying the CQM value on the command line because of European notation for the decimal place?

Thanks.

[jdobbs]

Tested BD-RB v0.61.06
With Movie LE_MANS_66 UHD 60gig to BD50 using geforce gtx 1070 card.
Worked a treat .Took about 1 hour to do .Very pleased with the result , on my oppo 203 Player , with all the menus and such.Thanks for testing and posting the result. Appreciated.

One thing I see... since X264 isn't being used, I guess the message saying "tweaks enabled" isn't applicable and shouldn't be logged.

[cartman0208]

"U:\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "U:\BD-OUTPUT\WORKFILES\00008.AVS.SMPL.m2ts" --codec hevc --preset quality --profile main10 --output-depth 10 --repeat-headers --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1) --qp-min 0 --vbr 0 --vbr-quality 1 --aq-temporal --keyfile "U:\BD-OUTPUT\WORKFILES\VID_00008.CHP" --sar 1:1 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 -o "U:\BD-OUTPUT\WORKFILES\TEMP.265"


and the result from command line:


--------------------------------------------------------------------------------
U:\BD-OUTPUT\WORKFILES\TEMP.265
--------------------------------------------------------------------------------
avcuvid: size of input file "U:\BD-OUTPUT\WORKFILES\00008.AVS.SMPL.m2ts" is 0
failed to initialize file reader(s).
Failed to open input file.

[jdobbs]

and the result from command line:Ok... I see. It looks like the input file is too short for BD-RB to create a sample. I guess I never thought about that possibility when I added the new sampling method for HEVC.

There's only 1 frame in that file? I'm surprise it is even in the list to be encoded... you must have set the minimum encode length to 0, maybe?

Would you mind posting the contents of your BDREBUILDER.INI file?

[cartman0208]

Ok... I see. It looks like the input file is too short for BD-RB to create a sample. I guess I never thought about that possibility when I added the new sampling method for HEVC.

There's only 1 frame in that file? I'm surprise it is even in the list to be encoded... you must have set the minimum encode length to 0, maybe?

Would you mind posting the contents of your BDREBUILDER.INI file?

The input file should have 160k frames

[22:37:53] PHASE ONE, Encoding
- [22:37:53] Processing: VID_00008 (5 of 14)
- [22:38:24] Reencoding video [VID_00008]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 160.215 frames
- [22:38:24] Performing CQM Prediction...
- Analyzing 1,00 [22:38:28] - Failed video encode, aborted[/QUOTE]

[QUOTE][Options]
AC3_192=0
AC3_640=1
AC3_REENCODE=0
ALTAUTOCROP=1
ALTCRF=20
ALTMETHOD=0
ALT_CRF_TARGET=1024
ALT_TARGET=1024
ASSUME_DVD_PAL=0
AUDIO_DRC=0
AUDIO_TO_KEEP=deu;eng;ger;
AUDIO_TRACK_LIMIT=1
AUTO_BURN=2
AUTO_QUALITY=0
AVCHD=1
BD25_SIZE=24500
BD50_SIZE=49000
BDMV_CERT_ONLY=0
COMPLETION_BEEP=0
CONVERT_WIDE=0
CUSTOM_TARGET_SIZE=23500
DECODER=0
DEINTERLACE=0
DTS_REENCODE=0
ENCODER=1
ENCODE_QUALITY=3
FRIMSOURCE=0
IGNORE_3D=0
IVTC_PULLDOWN=0
KEEP_HD_AUDIO=0
MODE=0
MOVIEONLY_TYPE=4
NEROAAC=0
NVENC_CAPABLE=1
ONEPASS_ENCODING=2
OPEN_GOP=0
OUTPUT_SBS=0
PGSTOSRT=0
REMOVE_OUTPUT=0
REMOVE_WORKFILES=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
SD_CONVERT=0
SD_TO_1080=0
SUBS_TO_KEEP=all
SUBTITLE_TRACK_LIMIT=1
SUPTITLE=0
TARGET_SIZE=49000
USE_FILTERS=0
VERSION=0.61.0.6
MENU_BACKGROUND=U:\BD_Rebuilder\misc\menuback.jpg
MENU_AUDIO=U:\BD_Rebuilder\tools\blankclip\blank.ac3
IMPORT_THRESHOLD=1
QUICK_PLAY_THRESHOLD=1
MENU_AUTO_BACKGROUND=1
MENU_AUTO_DVDAUDIO=1
MENU_PLAY_SEQUENTIAL=0
MENU_START_WITH_MENU=1
IMPORT_LIMIT_LANG=0
IMPORT_KEEP_PLAYALL=0
IMPORT_PREPARE_MKV=0
[Paths]
SOURCE_PATH=U:\FULLDISC\COLD_PURSUIT\
WORKING_PATH=U:\BD-OUTPUT\
DGIndexNV=U:\Tools\dgdecnv2053\x32 Binaries\DGIndexNV.exe
DGDecNV=U:\Tools\dgdecnv2053\x32 Binaries\DGDecodeNV.dll

[jdobbs]

The input file should have 160k framesNot in the log that you posted:

[21:57:33] PHASE ONE, Encoding
- [21:57:33] Processing: VID_00000 (1 of 14)
- [21:57:33] Extracting A/V streams [VID_00000]
- [21:57:38] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160

The 160 frames is for an entirely different M2TS (VID_00008). (5 of 14)

- [22:37:53] Processing: VID_00008 (5 of 14)
- [22:38:24] Reencoding video [VID_00008]
- Source Video: HEVC, 3840x2160


Looking back at it now, though, it looks like even that one had over 1000 frames (I got confused by the use of "." rather than ",")

[cartman0208]

Sorry, that was the same movie, I just wanted some progress while waiting ;)
I did the 1st vid ... when that failed, I posted that and switched to VBR
When you asked for that command line, I was on the 5th vid of that movie, switched back to CQM, and posted the log...
Sorry again for the confusion :rolleyes:

Should I switch regional settings on my OS?

[cartman0208]

Hmm... I wonder if the routine is inserting a "," instead of a "." when specifying the CQM value on the command line because of European notation for the decimal place?


Good hint ... and guess what?

Should I switch regional settings on my OS?

That worked!
I set decimal separator to "." and digit grouping to "," (like here (https://www.officetooltips.com/office_2016/tips/how_to_change_decimal_symbol_and_digit_grouping_symbol_in_windows_10.html) ) and now the encode runs fine in CQM mode...

But I'd rather have my settings back to normal :scared:

[jdobbs]

Good hint ... and guess what?



That worked!
I set decimal separator to "." and digit grouping to "," (like here (https://www.officetooltips.com/office_2016/tips/how_to_change_decimal_symbol_and_digit_grouping_symbol_in_windows_10.html) ) and now the encode runs fine in CQM mode...

But I'd rather have my settings back to normal :scared:Try this version and let me know if it fixes your issue:

BD-RB v0.61.07 (https://jammernhilftnichts.de/jdobbs/BD-RBV06107.zip)

It also adds the --repeat-headers fix when using UHD_V3_MODE=1

Also, I did some testing yesterday to compare CQM and VBR modes with NVENCC. At the same files size (bitrate) it seems that CQM gives a better SSIM. But... since the CQM prediction isn't perfect, its possible that you might have a lower file size and the better SSIM might not hold true. I'm looking at possible ways to improve prediction, or, since it's so fast -- maybe do a second CQM pass (using the first pass as the ultimate "prediction" sample).

[Sharc]

Also, I did some testing yesterday to compare CQM and VBR modes with NVENCC. At the same files size (bitrate) it seems that CQM gives a better SSIM.
Some time ago I found to my surprise that leaving --aq 'off' gave the best SSIM and VMAF values in CQM mode (adjusted for nearly same filesize) using NVEncC (AVC, h.264). Maybe it was specific to the source I tested and/or the --aq algo may have improved since, so don't quote me on that.....

[GreasyGreedo]

Have you had a chance to look into the issue where subtitles are lost from a UHD disc containing multiple movie files? Just checking, no rush or anything.

[Michi]

CQM fails on 61.07, too:

[07.19.20] BD Rebuilder v0.61.07
[19:50:44] Source: UHD_GENTLEMEN
- Input BD size: 60,94 GB
- Approximate total content: [01:56:59.095]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), CQM
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[19:50:46] PHASE ONE, Encoding
- [19:50:46] Processing: VID_00000 (1 of 2)
- [19:50:46] Extracting A/V streams [VID_00000]
- [19:50:50] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 610 frames
- [19:50:50] Performing CQM Prediction...
- Analyzing 1,00 [19:51:01] - Failed video encode, aborted


Nvenc VBR works without error, but the quality on UHDs with grain isn't good enough for me.

I used a GTX 1660 for all tests.

[Sharc]

CQM fails on 61.07, too:


- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 610 frames
- [19:50:50] Performing CQM Prediction...
- Analyzing 1,00 [19:51:01] - Failed video encode, aborted


The blue seems not right to me ....
If size is not that important to you, you may want to try with a fix quality factor rather than running the prediction, or you could try with the old prediction algo perhaps (NEW_CRF_PREDICTION=0 in the .ini). I didn't try it though.

[jdobbs]

CQM fails on 61.07, too:

[07.19.20] BD Rebuilder v0.61.07
[19:50:44] Source: UHD_GENTLEMEN
- Input BD size: 60,94 GB
- Approximate total content: [01:56:59.095]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), CQM
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[19:50:46] PHASE ONE, Encoding
- [19:50:46] Processing: VID_00000 (1 of 2)
- [19:50:46] Extracting A/V streams [VID_00000]
- [19:50:50] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 610 frames
- [19:50:50] Performing CQM Prediction...
- Analyzing 1,00 [19:51:01] - Failed video encode, aborted


Nvenc VBR works without error, but the quality on UHDs with grain isn't good enough for me.

I used a GTX 1660 for all tests.I'll take another look at it.

Can you post the contents of LASTCMD.TXT (in the BD-RB folder) right after it fails? If possible, then copy the command to a DOS window and try and run it so we can see what error is occurring.

[Michi]

LASTCMD.TXT;

"C:\BD_Rebuilder UHD\tools\nvenc\nvencc.exe" --avhw -i "Q:\4K\WORKFILES\00000.AVS.SMPL.m2ts" --codec hevc --preset
quality --profile main10 --output-depth 10 --repeat-headers --chromaloc 2 --colorprim bt2020 --transfer smpte2084
--colormatrix bt2020nc --master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)
--qp-min 0 --vbr 0 --vbr-quality 1 --aq-temporal --sar 1:1 --aud --pic-struct --vbv-bufsize 60000 --max-bitrate 60000
--gop-len 24 -o "Q:\4K\WORKFILES\TEMP.265"

[jdobbs]

@Michi

Thanks. It looks exactly like what cartman0208 saw. I'm going through sources trying to find one that causes it for me so I can point out exactly why the sample is created with a zero length.

[cartman0208]

I reseted my regionals back to normal and the Prediction fails on 61.07...
[23:03:26] PHASE ONE, Encoding
- [23:03:26] Processing: VID_00000 (1 of 14)
- [23:03:26] Extracting A/V streams [VID_00000]
- [23:03:31] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 1.046 frames
- [23:03:31] Performing CQM Prediction...
- Analyzing 17,35 [23:03:35] - Failed video encode, aborted


Set it to "US" type:
[23:06:53] PHASE ONE, Encoding
- [23:06:53] Processing: VID_00000 (1 of 14)
- [23:06:53] Extracting A/V streams [VID_00000]
- [23:06:57] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24.000fps, 1,046 frames
- [23:06:57] Performing CQM Prediction...
- Analyzing 17.35 9.18 5.09 3.04 2.02 1.51 1.26 1.13 1.06 1.03 1.02 1.01 [1.01]
- [23:07:31] Encoding using constant quality mode.


Unfortunately thats not all ... on a later vid of that BD the prediction fails with an error Popup
[22:42:06] PHASE ONE, Encoding
- [22:42:06] Processing: VID_00020 (6 of 14)
- [22:42:06] Reencoding video [VID_00020]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 240 frames
- [22:42:06] Performing CQM Prediction...
- [22:42:06] PredictAndEncode() 00006 2810
[22:42:17] - Aborted by user request

LASTCMD.TXT still holds the command from the previous vid.

What I noticed ... VID_00020 only shows the copyright warning, still frame with no motion at all

[jdobbs]

Yeah. Definitely some work to be done on that HEVC prediction routine.

[Moviewatcher666]

I've created a test release (v0.61.06) of BD Rebuilder for anyone who would like to experiment and report any issues they see with the new support for NVIDIA/NVENC support.

Please note that in order to use the new capability you must run BD-RB on a system that has an NVIDIA card installed that supports NVENC. You can find out more about which cards can be used at this link (https://developer.nvidia.com/video-encode-decode-gpu-support-matrix). BD-RB does a check when you attempt to select the NVENC encoder (under the SETTINGS menu).

There were a considerable number of changes to this release, so this version should be considered "for testing purposes only", so I'm not updating the first post of this thread -- please try it and let me know your experiences and report any bugs you find.

BD-RB v0.61.06 (https://jammernhilftnichts.de/jdobbs/BD-RBV06106.zip)

Thanks.

HOLY CRAP! Are you kidding me??

Just did an whole disk 4K encode on my Empire Strike Back disk.

Previous whole disk encodes shrinking to BD50 using FFMPEG frame serving would take 2 days (that's right, 48 HOURS).

Using this version of BD-RB using NVENC frame serving....2 HOURS! And the quality is amazing on my LG 65" OLED TV.

Can there be that much of a difference!? I am truly blown away at the speed difference.

Good work, jdobbs and thank you!

[jdobbs]

HOLY CRAP! Are you kidding me??

Just did an whole disk 4K encode on my Empire Strike Back disk.

Previous whole disk encodes shrinking to BD50 using FFMPEG frame serving would take 2 days (that's right, 48 HOURS).

Using this version of BD-RB using NVENC frame serving....2 HOURS! And the quality is amazing on my LG 65" OLED TV.

Can there be that much of a difference!? I am truly blown away at the speed difference.

Good work, jdobbs and thank you!Good to hear.

[musiclover]

Yeah. Definitely some work to be done on that HEVC prediction routine.

I guess the AVC prediction routine also needs work. With software compression BDRB uses the same bitrate as with hardware compression. But NVENCC compresses the video much more than x264 does. Therefore the resulting BD's are much smaller. So I think NVENCC needs to use a higher bitrate.

But maybe at the moment most of the work must be done on making UHD work properly

[geekzapoppin]

Just tried out the latest beta version using NVENC as the encoder. As a previous post mentioned, it's like BD-Rebuilder got a nitrous injection. I didn't encounter any errors and the results are as good as I've come to expect over the years. Great work!

[cartman0208]

It also adds the --repeat-headers fix when using UHD_V3_MODE=1


First run looks good, no issues.
So basically we get an UHD compliant (HEVC, 10bit) disc with 1080p from a standard BD ... NICE! :D

Can't wait to compare the results on the big screen...

[geekzapoppin]

Spoke a little too soon, I'm afraid. I'm running into a situation where HD audio is not converting to AC3 properly. I don't encounter any errors during the process, but when I test out the final result, there is no audio. I took a look into the WORKFILES folder and noticed that, before the remuxing stage, the AC3 files are 1KB. The intermediate files look to be the correct size, it's like it just gets to the AC3 encoding stage and then either skips encoding or starts long enough to create a tiny dummy file, but then moves on to remuxing when there isn't an actual AC3 file to include. I'm using v0.61.06, but I noticed this happening on older versions as well.

What kind of info do I need to post that would be helpful to you? Just let me know. Your work over the years has been much-appreciated.

[musiclover]

Spoke a little too soon, I'm afraid. I'm running into a situation where HD audio is not converting to AC3 properly. I don't encounter any errors during the process, but when I test out the final result, there is no audio. I took a look into the WORKFILES folder and noticed that, before the remuxing stage, the AC3 files are 1KB. The intermediate files look to be the correct size, it's like it just gets to the AC3 encoding stage and then either skips encoding or starts long enough to create a tiny dummy file, but then moves on to remuxing when there isn't an actual AC3 file to include. I'm using v0.61.06, but I noticed this happening on older versions as well.

What kind of info do I need to post that would be helpful to you? Just let me know. Your work over the years has been much-appreciated.

You need to install the helper apps from the first page again. That usually helps me in this situation

[geekzapoppin]

You need to install the helper apps from the first page again. That usually helps me in this situation

I'll give that a try. Thanks!

[MrVideo]

But I'd rather have my settings back to normal :scared:
Normal is in the eye of the beholder. :D

[jdobbs]

Update: Still working on the CQM/CRF prediction for HEVC sources. I think I've fixed the error issues -- but I'm now trying to try and make it a little more accurate -- and to add an automatic second pass if it oversizes.

[AmigaFuture]

Wow, I've never noticed that file ... :thanks:

What? Okay, reading through the thread.. I'm a _little_ surprised. The current supplier of the BD-RB files..missed that. Smiling.

[cartman0208]

What? Okay, reading through the thread.. I'm a _little_ surprised. The current supplier of the BD-RB files..missed that. Smiling.

Well, true :o
I never used the Alternate Output feature much, there are other solutions, which are actually a wee bit handier ... but I do now, because of NVENC :rolleyes:

And I have a question: Is it possible to burn in subtitles in Alternate Output?
Because with Plex the whole movie gets reencoded, when you turn on subtitles ... and the Atom Processor of the NAS then has some trouble on 4K sources :scared:

I tried "Turn Subtitle ON" but it's not burnt in...

[Sharc]

Well, true :o
I never used the Alternate Output feature much, there are other solutions, which are actually a wee bit handier ... but I do now, because of NVENC :rolleyes:

And I have a question: Is it possible to burn in subtitles in Alternate Output?
Because with Plex the whole movie gets reencoded, when you turn on subtitles ... and the Atom Processor of the NAS then has some trouble on 4K sources :scared:

I tried "Turn Subtitle ON" but it's not burnt in...
Instead of burning you could try with .srt subtitles which you can download free from opensubtitles.org, for example. Text subtitles are widely supported.

[cartman0208]

Instead of burning you could try with .srt subtitles which you can download free from opensubtitles.org, for example. Text subtitles are widely supported.

That might work, but I'd have to maintain the extra subtitle files
plus...
The Subtitles I'm after (foreign language) are not always available

BUT ... I think I found the answer
In the Setup options I found "Use SupTitle for Alternate Forced Subs"
That transforms the selectable Subtitle into something that Plex doesn't need to transcode (Text?) ... and its still selectable, thats even better than burnt in... :)

[ggtop]

thats even better than burnt in... :)
SupTitle is an AviSynth plugin and burn-in is exactely what it's supposed to do :D

ggtop

[cartman0208]

SupTitle is an AviSynth plugin and burn-in is exactely what it's supposed to do :D

ggtop

Burn-in, as I understand it, is a subtitle encoded in the video stream

But the resulting MKV has no burned-in subtitles ... I can switch between different languages

Never mind ... subtitles are fine for me :)

[ggtop]

Burn-in, as I understand it, is a subtitle encoded in the video stream

YES


But the resulting MKV has no burned-in subtitles ... I can switch between different languages

Never mind ... subtitles are fine for me :)

If subs are fine I suggest to uncheck "Use Suptitle..." again as it will burn-in subs into the encoded videostream. Look into the AVS file(s) holding the AviSynth script. By default BD-RB searches for forced subs having language codes defined in your .INI in that order. Example:
FORCED_SUB_LANG=deu;ger;
As I don't use MKV I'm not 100% it works the same way like it does for MP4, but I'm pretty sure it does. BD-RB muxes subs into MKV container. That's why they are present for you using PLEX are other video players. In any case "Use Suptitle..." is not what you want.
There are a lot of sources without forced subs. In case you can enable sub streams by right-clicking them in the streams' pane. Very likely your current source is such an example.

ggtop

[cartman0208]

Thanks for the explanation, that helps a lot.
And as long as Plex can play subtitles without reencoding, any method is fine for me ;)

@jdobbs: you might want to reconsider copying the color information ... there are a few UHD-BDs where (some) extras are in BT.709 ...

[jdobbs]

Thanks for the explanation, that helps a lot.
And as long as Plex can play subtitles without reencoding, any method is fine for me ;)

@jdobbs: you might want to reconsider copying the color information ... there are a few UHD-BDs where (some) extras are in BT.709 ...It should be keeping the current configuration -- including BT.709. Are you saying it isn't?

[jdobbs]

Okay, everyone, let's try this release and see if it gets rid of the errors. It should also do better prediction (although it can never be perfect). It will also do a self-correcting second CQM pass if the output is too large (you may see that a lot on very small files).

BD-RB v0.61.08 (https://jammernhilftnichts.de/jdobbs/BD-RBV06108.zip)

Please let me know what you find and provide any suggestions you think might make it better.

[cartman0208]

It should be keeping the current configuration -- including BT.709. Are you saying it isn't?

Source files are BT.709 with 4K resolution, after BDRB conversion it's BT.2020

[cartman0208]

Unfortunately the issue with european punctuation still exists

- [20:02:14] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 128.721 frames
- [20:02:14] Performing CQM Prediction...
- Analyzing 1,00 [20:02:23] - Failed video encode, aborted

Changeing punctuation works

- [20:10:04] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 128,721 frames
- [20:10:04] Performing CQM Prediction...
- Analyzing 1.00 [1.00]
- [20:10:53] Encoding using constant quality mode.

[Sharc]

@jdobbs/cartman:
Just wondering: Is the initial value of 1.0 for the prediction intentional or is it possibly a bug?
It looks like the 128,721 frames are interpreted as 128 frames (a thousands separator issue, I think). Hence it selects the rate factor 1.0.

Edit: Here the frame numbers show with the usual high comma like 175'243 frames and the initial rate factor is 14.5. All ok......

[cartman0208]

@jdobbs/cartman:
Just wondering: Is the initial value of 1.0 for the prediction intentional or is it possibly a bug?
It looks like the 128,721 frames are interpreted as 128 frames (a thousands separator issue, I think). Hence it selects the rate factor 1.0.

Edit: Here the frame numbers show with the usual high comma like 175'243 frames and the initial rate factor is 14.5. All ok......

Good thinking ... If I set both the 1000s separator and decimal separator to "." (which usually is nowhere the case) the logging in the GUI stops completely, where the separator should be
- [21:58:02] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 128

BDREBUILDER.LOG:
- [21:58:02] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 128 721 frames
- [21:58:02] Performing CQM Prediction...
- Analyzing 1.00 [1.00]
- [21:58:51] Encoding using constant quality mode.

But even when the separators are set to " ' " and "." ... the initial (and only) number is 1.00 ... I will check the output size

[Sharc]

Something is odd with your settings.
The thousands grouping is a space char rather than ' in your system.
The decimal separator looks ok.
Hence BD RB still assumes a very short file and sets the ratefactor to 1.0 accordingly.
Try to change the thousands separator in your local windows settings.

[jdobbs]

Source files are BT.709 with 4K resolution, after BDRB conversion it's BT.2020Are they being imported, or are they from a UHD disc?

[jdobbs]

Unfortunately the issue with european punctuation still exists



Changeing punctuation worksI am really confused. BD-RB scans the string and replaces any "," with a "."


I'll look at it again.

Can you look at the command line (LASTCMD.TXT) and see if the "," is still there?

[jdobbs]

Something is odd with your settings.
The thousands grouping is a space char rather than ' in your system.
The decimal separator looks ok.
Hence BD RB still assumes a very short file and sets the ratefactor to 1.0 accordingly.
Try to change the thousands separator in your local windows settings.Is there a standard somewhere in which a ' is used instead of . or , in the thousands separator? I don't think I was aware of that.

So 1 million could be: 1,000,000.00 or 1.000.000,00 or 1'000'000,00?

[Sharc]

I am really confused. BD-RB scans the string and replaces any "," with a "."


I'll look at it again.

Can you look at the command line (LASTCMD.TXT) and see if the "," is still there?
I think cartman's problem is the 1000s grouping character (which should be '), not the decimal point.

[Sharc]

Is there a standard somewhere in which a ' is used instead of . or , in the thousands separator? I don't think I was aware of that.

So 1 million could be: 1,000,000.00 or 1.000.000,00 or 1'000'000,00?
I think the notation is a local (national) habit rather than a strict standard. It can therefore be customized in Windows how the numbers should be presented.

[jdobbs]

I think the notation is a local (national) habit rather than a strict standard. It can therefore be customized in Windows how the numbers should be presented.Still confused as to how that value could be misinterpreted. BD-RB calculates the framecount. I can understand how a string being interpreted as a number could be an issue, or how a number being represented on the screen could show the wrong values because of local representations. But how can a number be misinterpreted when is doesn't change from a number (the actual framecount used in calculations)???

I guess I'm going to have to change my system to a European style locality setting and trace it to find out how this happens.

[Sharc]

Still confused as to how that value could be misinterpreted. BD-RB calculates the framecount. I can understand how a string being interpreted as a number could be an issue, or how a number being represented on the screen could show the wrong values because of local representations. But how can a number be misinterpreted when is doesn't change from a number (the actual framecount used in calculations)???

I guess I'm going to have to change my system to a European style locality setting and trace it to find out how this happens.
No idea. Somewhere happening a conversion numbers <-> strings?
Windows secrets?

[jdobbs]

I just set my system so that the thousands separator is . and the decimal is , -- and it seems to be working properly. So I'm not sure why cartman0208 is getting an error.

@cartman0208

Can you give me some hints on settings that cause an issue? Ignore what is showing on the screen -- that doesn't matter right now. Are you getting errors when the encode is running? Can you show me the command line being used?

The new NVENC subroutine is structured after the original ones that did X265 encodes. I'm confused why it would be acting differently.

[Edit] I have to correct myself. There is an error -- I just realized the sample file was empty -- and OMG I was using a special system format call to create the string used for a seek command that tells it where to start! I must have been in lala land when I wrote that code. And why was it so hard for me to see when I reviewed it 10 times?

v061.09 should be coming in a little while. I just want to test it with the regional settings first.

[cartman0208]

Are they being imported, or are they from a UHD disc?

I'll upload a sample ... could take a while

[cartman0208]

This is default in Germany
https://jammernhilftnichts.de/download/format.png

lastcmd is
"U:\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "U:\FULLDISC\LUCYUHD\BDMV\STREAM\00000.m2ts" --codec hevc --preset quality --profile main10 --output-depth 10 --repeat-headers --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,50) --max-cll 1000,400 --qp-min 0 --vbr 0 --vbr-quality 1 --aq-temporal --keyfile "U:\BD-OUTPUT\WORKFILES\VID_00000.CHP" --sar 1:1 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 -o "U:\BD-OUTPUT\WORKFILES\VID_00000.AVS.hevc"

[cartman0208]

[Edit] I have to correct myself. There is an error -- I just realized the sample file was empty -- and OMG I was using a special system format call to create the string used for a seek command that tells it where to start! I must have been in lala land when I wrote that code. And why was it so hard for me to see when I reviewed it 10 times?

v061.09 should be coming in a little while. I just want to test it with the regional settings first.

Good thing you sorted it out... I was beginning to believe that I messed up my system :D

[jdobbs]

I'm hoping this version fixes the regional issues reported:

BD-RB v0.61.09 (https://jammernhilftnichts.de/jdobbs/BD-RBV06109.zip)

@cartman0208

Can you confirm this is working on your system? Thanks.

Meanwhile I'm going to look at the BT.709 thing and how hard it would be to include HDR10+ in a future version.

One question: Was the BT.709 source an imported file, or was it BT.709 on an original UHD disc? That way I can know if it is the reencoding or the import that causes the mixup.

[cartman0208]

One question: Was the BT.709 source an imported file, or was it BT.709 on an original UHD disc? That way I can know if it is the reencoding or the import that causes the mixup.

It's an original BD rip... the main movie is fine, also most of the extras

[Edit]
I did two rebuilds and both ran fine, but I still only get - Analyzing 1,00 [1,00] in the log .. at least for the main movie ... is that intended?
[Edit2]
Ok, the former applies only on some sources

[CraigWally]

I'm loving the speed gains on this latest version,
However
Is the "Quicker encode for extras" still working right

I've just tried to The Great Escape BluRay 1080,
and the extras have come out larger than the original with the main movie being compressed more than necessary

I'm just doing some further test, I'll post settings/ini etc later if necessary

EDIT: Hmmm, somethings not right here
If I choose "movie and menus / auto blank extras" - it chooses all the extras, rather than blanking them - seems to be just this disc?!

[jdobbs]

It's an original BD rip... the main movie is fine, also most of the extras

[Edit]
I did two rebuilds and both ran fine, but I still only get - Analyzing 1,00 [1,00] in the log .. at least for the main movie ... is that intended?
[Edit2]
Ok, the former applies only on some sourcesOn the one where you get "Analyzing 1,00", can you look at the sample file and see its size? It would be named after the M2TS being sampled, so if the M2TS was 00058 it would be named 00058.AVS.SMPL.m2ts.

I would think the only time you would see a 1,00 would be when the source file was already extremely small. That would be unusual for a feature, you might see it for an extra (like something that hold several still pictures). I've run numerous jobs and I don't think I've ever seen it. It makes me think the sample file still has a length of zero.

Could you post the log from that job? Also, could you post the contents of the INF file for that job?

[jdobbs]

I'm loving the speed gains on this latest version,
However
Is the "Quicker encode for extras" still working right

I've just tried to The Great Escape BluRay 1080,
and the extras have come out larger than the original with the main movie being compressed more than necessary

I'm just doing some further test, I'll post settings/ini etc later if necessary

EDIT: Hmmm, somethings not right here
If I choose "movie and menus / auto blank extras" - it chooses all the extras, rather than blanking them - seems to be just this disc?!When "quick for extras" is checked, no sizing checks are done on the extras. They are just encoded at a fixed CRF rate and the feature is adjusted based on their total end sizing. The whole point is to get them done quickly because they don't (typically) add up to much anyway. The normal CRF (or CQM) used varies based on the target -- on a BD-25 CRF is 20. Normally that would make them smaller than the originals -- but if the originals were encoded at a very low bitrate it could, possibly, make them larger. If you think they are taking too much space, you can adjust the CRF/CQM value by adding QUICK_CRF=nn (nn being the new target CRF) to the BDREBUILDER.INI file (see the explanation in HIDDENOPTS.TXT). If you choose a value larger than the default they will get smaller and show less quality.

[cartman0208]

Here's the log
[07.24.20] BD Rebuilder v0.61.09
[09:09:06] Source: LUCYUHD
- Input BD size: 58,50 GB
- Approximate total content: [01:42:30.060]
- Target BD size: 47,85 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), CQM
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[09:09:09] PHASE ONE, Encoding
- [09:09:09] Processing: VID_00000 (1 of 3)
- [09:09:09] Extracting A/V streams [VID_00000]
- Extracting video streams [VID_00000]
- Extracting audio/subtitle streams [VID_00000]
- [09:15:57] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 128.721 frames
- [09:15:57] Performing CQM Prediction...
- Analyzing 1,00 [1,00]
- [09:16:50] Encoding using constant quality mode.
- [10:08:10] Video Encode complete
- [10:08:10] Processing audio tracks
- Track 4353 (eng): Keeping original audio
- Track 4354 (deu): Keeping original audio
- [10:08:11] Multiplexing M2TS
- [10:10:00] Processing: VID_00003 (2 of 3)
- [10:10:00] Extracting A/V streams [VID_00003]
- [10:10:04] Reencoding video [VID_00003]
- [10:10:04] Keeping original video (no reencode)
- [10:10:04] Processing audio tracks
- [10:10:04] Multiplexing M2TS
- [10:10:08] Processing: VID_00004 (3 of 3)
- [10:10:08] Extracting A/V streams [VID_00004]
- [10:10:12] Reencoding video [VID_00004]
- [10:10:12] Keeping original video (no reencode)
- [10:10:12] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:10:12] Multiplexing M2TS
[10:10:16]PHASE ONE complete
[10:10:16]PHASE TWO - Rebuild Started
- [10:10:16] Rebuilding BD file Structure
[10:10:22] - Encode and Rebuild complete
[10:10:22] Writing BD structure to ISO file
- ImgBurn completed successfully
[10:13:00] JOB: LUCYUHD finished.
[/QUOTE]

and the .inf
[QUOTE][Status]
LABEL=LUCYUHD
VERSION=v0.61.09
SOURCE_SIZE=62817573023
SOURCE_VIDEO_SIZE=62142130176
TARGET_SIZE=51380224000
REDUCTION=.815948552284787
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=deu;eng;ger;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=all
BACKUP_MODE=0
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=-1
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
UHD_V3_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=3
REBUILD_COMPLETE=1
[00000]
AUDIO=011
PGS=111111111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=50587878624
NSTART=26999955
NEND=268593181
NSIZE=36097812480
FLINK=0
MLINK=0
[00003]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=10026
USE_ORIGINAL=1
NSTART=27000000
NEND=27011261
NSIZE=12288
FLINK=0
MLINK=0
[00004]
USE_ORIGINAL=1
AUDIO=1
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=116892502
NSTART=27000000
NEND=28081080
NSIZE=143271936
FLINK=0
MLINK=0


Another thing I noticed ...
currently CQM is set, but LASTCMD states "--vbr 0 --vbr-quality <cqm-prediction-result>" ... shouldn't that be "--cqp <cqm-prediction-result>" ?

[jdobbs]

Another thing I noticed ...
currently CQM is set, but LASTCMD states "--vbr 0 --vbr-quality <cqm-prediction-result>" ... shouldn't that be "--cqp <cqm-prediction-result>" ?No. cqp would set a constant quantizer value (or set of quantizer values for I, P, and B frames). Constant Quality Mode (CQM) would use "--vbr 0 --vbr-quality <float>"

I guess it's possible that shrinking the original by such a low factor might result in a value of 1.00, especially if the original was purposely oversized to force the need for a dual-layer disc -- but I would think that would be extremely rare (although I have seen it before).

What happens if you select a 25GB target size?

Did you get a chance to look at the size of the sample file?

[cartman0208]

Did you get a chance to look at the size of the sample file?

I'm currently on another encode (where everything looks fine, several numbers on prediction, the sample file is around 750MB) but will retry the one in question after
I should mention, the one I posted, was way undersized ... around 35GB

[jdobbs]

I'm currently on another encode (where everything looks fine, several numbers on prediction, the sample file is around 750MB) but will retry the one in question afterThanks.

In your INF file it looks like the output M2TS size is actually smaller than the target size, even with a CQM value of 1.00. That makes me wonder if the original actually was purposefully oversized. I've even seen M2TS files that were padded with zeros to make them larger. The one here is a pretty short film (about 90 minutes). Weird.

I would have thought, though, that BD-RB would have noticed (after extracting the HEVC elementary stream) that no reencoding was needed and would have kept the original (unless "force_encode" was asserted). It is probably possible to pad an elementary stream too, I guess (you just wouldn't use zeros). Curious.

[cartman0208]

But would a CQM value of 1.00 not result in a HUGE output file, since its almost lossless?

[edit]
Mediainfo Output on the sample file
General
ID : 1 (0x1)
Complete name : U:\BD-Output\WORKFILES\00000.AVS.SMPL.m2ts
Format : MPEG-TS
File size : 604 MiB
Duration : 1 s 1 ms
Overall bit rate mode : Variable
Overall bit rate : 4 956 Mb/s
FileExtension_Invalid : ts m2t m2s m4t m4s tmf ts tp trp ty

Video
ID : 256 (0x100)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 2 s 2 ms
Bit rate : 4 711 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 23.690
Stream size : 1.10 GiB
Writing library : ATEME Titan KFE 3.7.3 (4.7.3.1003)
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1000 cd/m2
Maximum Frame-Average Light Level : 400 cd/m2

Menu
ID : 4096 (0x1000)
Menu ID : 1 (0x1)
Duration : 1 s 1 ms
List : 256 (0x100) (HEVC)
Service name : Service01
Service provider : FFmpeg
Service type : digital television

That's one big Bits/(Pixel*Frame) value :eek:

[jdobbs]

But would a CQM value of 1.00 not result in a HUGE output file, since its almost lossless?You would think so.

By the way, the sample file is nothing more than sets of frames pulled intact from the original stream. So what you are seeing there is the original information.

The only way to know is to look at the command line in LASTCMD.TXT (before the next encode starts) and see if it was actually used for the encode.

[cartman0208]

You would think so.

The only way to know is to look at the command line in LASTCMD.TXT (before the next encode starts) and see if it was actually used for the encode.


... --max-cll 1000,400 --qp-min 0 --vbr 0 --vbr-quality 1 --aq-temporal --keyfile "U:\BD-OUTPUT\WORKFILES\VID_00000.CHP"...
:scared:

[edit]
Well well ... on target-size BD25 I get:
- [15:29:49] Performing CQM Prediction...
- Analyzing 18,05 20,00 20,50 [20,50]

[Sharc]

That's one big Bits/(Pixel*Frame) value :eek:
No wonder when you look at the bitrate:
Bit rate : 4 711 Mb/s

[jdobbs]

No wonder when you look at the bitrate:Wow. That is an illegally high bitrate, even for a UHD/BD. I have to believe MEDIAINFO is reporting it incorrectly. It could be due to the way in which BD-RB creates the sample file by pulling sets of frames in small groups and throwing them together as an M2TS for sample reencoding. The PTS values might look a little crazy to it, as they start over again with each I frame at the start of a grouping. It won't affect the decoding/reencoding for sampling -- but might look goofy as a whole when trying to analyze it.

[cartman0208]

Sorry to be annoying, but I found another thing:
On Alternate Output the Cropping-Borders-Feature seems broken:

"U:\BD_Rebuilder\tools\nvenc\nvencc.exe" --avs -i "U:\BD-OUTPUT\WORKFILES\VID_00002.AVS" --codec hevc --preset performance --profile main10 --output-depth 10 --repeat-headers --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1) --max-cll 435,289 --qp-min 0 --vbr 0 --vbr-quality 25 --aq-temporal --keyfile "U:\BD-OUTPUT\WORKFILES\VID_00002.CHP" --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 -o "U:\BD-OUTPUT\WORKFILES\VID_00002.AVS.hevc"
--------------------------------------------------------------------------------
U:\BD-OUTPUT\WORKFILES\VID_00002.AVS.hevc
--------------------------------------------------------------------------------
avs: invalid clip.
avs: DirectShowSource: RenderFile, the filter graph manager won't talk to me
avs: (U:\BD-OUTPUT\WORKFILES\VID_00002.AVS, line 2)
failed to initialize file reader(s).
Failed to open input file.

[00003]
caption=MKV, HEVC, 1080p, Auto-AC3
aBitrate=640
aType=0
cType=1
vEncoder=1
vFormat=5
vKeyint=Auto
vBitrate=0


#Created by BD Rebuilder - v0.61.09
DirectshowSource("U:\FULLDISC\UHD_ASTERIX\BDMV\STREAM\00002.m2ts", fps=23.976, framecount=123617, audio=false)
Spline16Resize(1920,1080)
LoadPlugin("U:\BD_Rebuilder\tools\autocrop.dll")
Autocrop(mode=0, hMultOf=4)
ConvertToYV12().AssumeFPS(24000,1001)


[edit]
I made a list of different scenarios, where autocrop is working or not:
Source: h264 1080p, Target: h264 1080p, Decoder: DShow, Encoder: x26x - working
Source: h264 1080p, Target: h264 1080p, Decoder: DShow, Encoder: NVenc - failed
Source: h264 1080p, Target: h264 1080p, Decoder: DGdecNV, Encoder: x26x - failed
Source: h264 1080p, Target: h264 1080p, Decoder: DGdecNV, Encoder: NVenc - failed
Source: h264 1080p, Target: hevc 1080p, Decoder: DShow, Encoder: x26x - hanging
Source: h264 1080p, Target: hevc 1080p, Decoder: DShow, Encoder: NVenc - working
Source: h264 1080p, Target: hevc 1080p, Decoder: DGdecNV, Encoder: x26x - hanging
Source: h264 1080p, Target: hevc 1080p, Decoder: DGdecNV, Encoder: NVenc - failed
Source: hevc 2160p, Target: h264 1080p, Decoder: DShow, Encoder: x26x - failed
Source: hevc 2160p, Target: h264 1080p, Decoder: DShow, Encoder: NVenc - failed
Source: hevc 2160p, Target: h264 1080p, Decoder: DGdecNV, Encoder: x26x - failed
Source: hevc 2160p, Target: h264 1080p, Decoder: DGdecNV, Encoder: NVenc - failed
Source: hevc 2160p, Target: hevc 1080p, Decoder: DShow, Encoder: x26x - working
Source: hevc 2160p, Target: hevc 1080p, Decoder: DShow, Encoder: NVenc - failed
Source: hevc 2160p, Target: hevc 1080p, Decoder: DGdecNV, Encoder: x26x - working
Source: hevc 2160p, Target: hevc 1080p, Decoder: DGdecNV, Encoder: NVenc - failed
Source: hevc 2160p, Target: h264 2160p, Decoder: DShow, Encoder: x26x - failed
Source: hevc 2160p, Target: h264 2160p, Decoder: DShow, Encoder: NVenc - failed
Source: hevc 2160p, Target: h264 2160p, Decoder: DGdecNV, Encoder: x26x - failed
Source: hevc 2160p, Target: h264 2160p, Decoder: DGdecNV, Encoder: NVenc - failed
Source: hevc 2160p, Target: hevc 2160p, Decoder: DShow, Encoder: x26x - working
Source: hevc 2160p, Target: hevc 2160p, Decoder: DShow, Encoder: NVenc - failed
Source: hevc 2160p, Target: hevc 2160p, Decoder: DGdecNV, Encoder: x26x - working
Source: hevc 2160p, Target: hevc 2160p, Decoder: DGdecNV, Encoder: NVenc - failed

[MrVideo]

@cartman0208: Please use code wrapping instead of quote wrapping for data lists. That way long lists will get scrollbars and use the correct font. Thanks.

[cartman0208]

@cartman0208: Please use code wrapping instead of quote wrapping for data lists. That way long lists will get scrollbars and use the correct font. Thanks.

Yep, I know ... but as you can see, no horizontal scrollbars ... at least not in the post itself, but in the browser ... and that kind of messes up the thread, imho.

For the next long list I'll use CODE, but else I would rather use QUOTE, if that is OK?

[MrVideo]

Yep, I know ... but as you can see, no horizontal scrollbars.
I get around the long lines by adding CRs to those long lines, making two, or more, shorter lines. They do not have to stay long.

[BuddTX]

Sorry to be annoying, but I found another thing:
On Alternate Output the Cropping-Borders-Feature seems broken:[/CODE]

Thank you for finding this issue Cartman, as this has been happening to me also.

I have just been testing each "session" with "UHD_LIMIT_ENCODE=1" before I create the full length MKV, so that I dont waste 2-4 days processing a video that will fail.

Oh, btw, I am only doing software encoding at this time, if that matters.

On the videos that fail, I create the MKV file with "cropping borders" unchecked, but with all other videos, I like having this feature checked.

[jdobbs]

Unfortunately AUTOCROP is simply an AVISYNTH PlugIn that I added to the BD-RB package. BD-RB just adds it to the AVISYNTH file when the box is checked. If it has an issue... there's really not much I can do other than maybe removing it as an option.

If you run into this problem, pretty much all I can recommend is to just use AVISYNTH filters to do the cropping manually.

[BuddTX]

Unfortunately AUTOCROP is simply an AVISYNTH PlugIn that I added to the BD-RB package. BD-RB just adds it to the AVISYNTH file when the box is checked. If it has an issue... there's really not much I can do other than maybe removing it as an option.

If you run into this problem, pretty much all I can recommend is to just use AVISYNTH filters to do the cropping manually.

Thanks JDobbs. I have not had this problem of a job failing with Autocrop selected, but the job successfully completed when unchecking the AutoCrop button until relatively recently.

I also have been playing with newer versions of Avisynth. (Currently using AviSynthPlus 3.6.1)

Wonder if this plugin would work "better" or "more reliably"?
RoboCrop

https://forum.doom9.org/showthread.php?t=168053&highlight=autocrop.dll

Version 1.13 has a release date of 2-7-2020

However, I do not see any place to download this dll.

In post 95 of the above link, "hello_hello" wrote "RoboCropped.avsi" and posted a link.

from the link above:
Plugin's for both Avisynth v2.5 and v2.6.

RoboCrop is an automatic cropping solution to crop black borders from video clips, loosely based on (but using no code from)
Autocrop by Glenn Bussell.

For the most part, you can just call it with RoboCrop(clip) and not bother with any other arguements, it is intended to be pretty
much autonomous in its decisions. You might however want to alter eg WMod and HMod if your encoder has special requirements, and
perhaps Laced if your source is likely to be fully progressive.

Borders are detected by sampling at Samples frames, at scanlines (h/v) using AverageLuma (RGB is converted to Luma Y at either TV or
PC levels, See Matrix). This sampling is done on all 4 sides of the frame.
If a scanline Average luma is below or equal to Thresh, then is considered possible black border, above considered possible image,
if Baffle [default=4] adjacent scanlines above Thresh, then it IS image.


Thanks JDobbs!

[BuddTX]

Also, maybe I should try using your "officially recommended" avisynth version, or maybe go back to 2.5.7 and see if that "fixes" the problem, the next time I find a video that fails with the autocrop selected, but is sucessful with autocrop unchecked.

[cartman0208]

I've dug a little further...
Looking at the software-only results
Source: h264 1080p, Target: h264 1080p, Decoder: DShow, Encoder: x26x - working
Source: h264 1080p, Target: hevc 1080p, Decoder: DShow, Encoder: x26x - hanging
Source: hevc 2160p, Target: h264 1080p, Decoder: DShow, Encoder: x26x - failed
Source: hevc 2160p, Target: hevc 1080p, Decoder: DShow, Encoder: x26x - working
Source: hevc 2160p, Target: h264 2160p, Decoder: DShow, Encoder: x26x - failed
Source: hevc 2160p, Target: hevc 2160p, Decoder: DShow, Encoder: x26x - working
that's not an issue of Avisynth or the Autocrop plugin ... the conversions between x264 and x265 content (and vice versa) seem to cause trouble ... the above results are the same with or without Autocrop.

[jdobbs]

I've dug a little further...
Looking at the software-only results
Source: h264 1080p, Target: h264 1080p, Decoder: DShow, Encoder: x26x - working
Source: h264 1080p, Target: hevc 1080p, Decoder: DShow, Encoder: x26x - hanging
Source: hevc 2160p, Target: h264 1080p, Decoder: DShow, Encoder: x26x - failed
Source: hevc 2160p, Target: hevc 1080p, Decoder: DShow, Encoder: x26x - working
Source: hevc 2160p, Target: h264 2160p, Decoder: DShow, Encoder: x26x - failed
Source: hevc 2160p, Target: hevc 2160p, Decoder: DShow, Encoder: x26x - working
that's not an issue of Avisynth or the Autocrop plugin ... the conversions between x264 and x265 content (and vice versa) seem to cause trouble ... the above results are the same with or without Autocrop.I don't think I understand what you are saying. Can you provide an description of what you are doing that results in a hang of a failure? A log maybe?

[jedihyte]

Is there a way to make a movie only MKV backup with MVC 3D? All my full 3D BD-25 Blu-ray backups using BDRebuilder always come out pixelated when using Powerdvd playback but fine if burn and use a hardware player, never can figure out how to get around this, so I want to try a 3D MVC MKV option.

[Sharc]

Is there a way to make a movie only MKV backup with MVC 3D? All my full 3D BD-25 Blu-ray backups using BDRebuilder always come out pixelated when using Powerdvd playback but fine if burn and use a hardware player, never can figure out how to get around this, so I want to try a 3D MVC MKV option.
There is no '3D MVC mkv' option AFAIK. However, the Alternate Movie-only output includes a few options for SBS 3D mkv.

[cartman0208]

I don't think I understand what you are saying. Can you provide an description of what you are doing that results in a hang of a failure? A log maybe?

I think, the log won't help much
[07.27.20] BD Rebuilder v0.61.09
[11:05:18] Source: SPECTRE_00800
- Input BD size: 37,52 GB
- Approximate total content: [02:28:06.878]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV, HEVC, NO_RESIZE, Auto-AC3
- Quality: Good (Fastest, BD-25+)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[11:05:20] PHASE ONE, Encoding
- [11:05:20] Processing: VID_02211 (1 of 1)
- [11:05:20] Extracting A/V streams [VID_02211]
- [11:14:02] Reencoding video [VID_02211]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 213.072 frames
- [11:14:02] Reencoding: VID_02211, Pass 1 of 1

No Progress, no CPU usage...
Running the contents of LASTCMD returns nothing.
"V:\BD_Rebuilder2\tools\x265-64.exe" - --preset ultrafast --slow-firstpass --qpfile "V:\OUTPUT\WORKFILES\VID_02211.CHP" --keyint 240 --crf 25 --y4m --stats "V:\OUTPUT\WORKFILES\VID_02211.AVS.hevc.stats" --output "V:\OUTPUT\WORKFILES\VID_02211.AVS.hevc"

when I break the command with CTRL+C, I get:
x265 [error]: unable to open input file <->

[jdobbs]

I think, the log won't help much
[07.27.20] BD Rebuilder v0.61.09
[11:05:18] Source: SPECTRE_00800
- Input BD size: 37,52 GB
- Approximate total content: [02:28:06.878]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV, HEVC, NO_RESIZE, Auto-AC3
- Quality: Good (Fastest, BD-25+)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[11:05:20] PHASE ONE, Encoding
- [11:05:20] Processing: VID_02211 (1 of 1)
- [11:05:20] Extracting A/V streams [VID_02211]
- [11:14:02] Reencoding video [VID_02211]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 213.072 frames
- [11:14:02] Reencoding: VID_02211, Pass 1 of 1

No Progress, no CPU usage...
Running the contents of LASTCMD returns nothing.

when I break the command with CTRL+C, I get:
x265 [error]: unable to open input file <->I can see the issue. X265 is trying to encode using a pipe as input, but nothing is being fed to the pipe. Unfortunately, though, I've tried several times and I can't repeat the issue. Can you please send (or post) a copy of your BDREBUILDER.INI and ALTERNATE.TXT files? I need to try with your exact settings.

[cartman0208]

[Options]
VERSION=0.61.0.7
ENCODER=0
MODE=3
ENCODE_QUALITY=5
ONEPASS_ENCODING=0
AUTO_QUALITY=0
MOVIEONLY_TYPE=1
ALTCRF=25
ALT_TARGET=1024
ALT_CRF_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
AUDIO_TO_KEEP=deu;eng;ger;
SUBS_TO_KEEP=all
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=0
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=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=1
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23500
[Paths]
SOURCE_PATH=V:\FULLDISC\SPECTRE\
WORKING_PATH=V:\OUTPUT\

# 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=MKV, HEVC, NO_RESIZE, Auto-AC3
aBitrate=640
aType=0
cType=1
vEncoder=1
vFormat=7
vKeyint=Auto
vBitrate=0
[00002]
caption=MP4, HEVC, NO_RESIZE, Auto-AC3
aBitrate=640
aType=0
cType=5
vEncoder=1
vFormat=7
vKeyint=Auto
vBitrate=0
[00003]
caption=MKV, HEVC, 1080p, Auto-AC3
aBitrate=640
aType=0
cType=1
vEncoder=1
vFormat=5
vKeyint=Auto
vBitrate=0
[00004]
caption=MP4, HEVC, 1080p, Auto-AC3
aBitrate=640
aType=0
cType=5
vEncoder=1
vFormat=5
vKeyint=Auto
[00005]
caption=MKV, H264, NO_RESIZE, Auto-AC3
aBitrate=640
aType=0
cType=1
vEncoder=0
vFormat=7
vKeyint=Auto
vBitrate=0
[00006]
caption=MP4, H264, NO_RESIZE, Auto-AC3
aBitrate=640
aType=0
cType=5
vEncoder=0
vFormat=7
vKeyint=Auto
vBitrate=0
[00007]
caption=MKV, H264, 1080p, Auto-AC3
aBitrate=640
aType=0
cType=1
vEncoder=0
vFormat=5
vKeyint=Auto
vBitrate=0
[00008]
caption=MP4, H264, 1080p, Auto-AC3
aBitrate=640
aType=0
cType=5
vEncoder=0
vFormat=5
vKeyint=Auto


An Inspect returns
[07.27.20] Checking System Settings
- BD-Rebuilder v0.61.09
- Windows Version: 6.2 [9200]
- Working Path Free Space: 632,36GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- X264: Ok
- X265: Wrong version found
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[07.27.20] Systems Settings Check complete


But I only use encoders, that come with BDRB, nothing was changed.

[jdobbs]

I updated x265 and forgot to update the checksum. I'll fix that for the next release.


[Edit] Yep. I used your INI and ALTERNATE settings and I got the same error. I'll have to trace it now and see why.

[cartman0208]

I updated x265 and forgot to update the checksum. I'll fix that for the next release.


[Edit] Yep. I used your INI and ALTERNATE settings and I got the same error. I'll have to trace it now and see why.

That INI should be quite fresh ... I deleted it some days ago and let BDRB create a new one ...
I made no manual changes since then ... only Settings and Setup menu

[jdobbs]

That INI should be quite fresh ... I deleted it some days ago and let BDRB create a new one ...
I made no manual changes since then ... only Settings and Setup menuYeah. I found it. It wasn't repeating because of a setting I had set in my INI.

It turns out I had commented out a line when I was working on the X265 call subroutine (I don't even remember doing it) and failed to enable it again.

[jdobbs]

Well that explains the X265 output issue. Now I need to look at the hevc input issues.

[cartman0208]

"V:\BD_Rebuilder2\tools\x264.exe" "V:\OUTPUT\WORKFILES\VID_00000.AVS" --preset ultrafast --bluray-compat --cabac --bframes 3 --b-pyramid none --weightp 1 --slow-firstpass --qpmin=0 --crf 25 --level 4.0 --qpfile "V:\OUTPUT\WORKFILES\VID_00000.CHP" --aud --nal-hrd vbr --pic-struct --vbv-bufsize 15000 --keyint 24 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 15000 --threads auto --thread-input --stats "V:\OUTPUT\WORKFILES\VID_00000.AVS.264.stats" --output "V:\OUTPUT\WORKFILES\VID_00000.AVS.264"
clpi_parse.c:138: failed signature match expected (HDMV0200) got (HDMV0300)
avs [info]: 3840x2160p 0:0 @ 24000/1001 fps (cfr)
x264 [warning]: frame MB size (240x135) > level limit (8192)
x264 [warning]: DPB size (2 frames, 64800 mbs) > level limit (1 frames, 32768 mbs)
x264 [warning]: MB rate (776823) > level limit (245760)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x264 [info]: profile Main, level 4.0, 4:2:0, 8-bit
x264 [error]: malloc of size 25876352 failed
x264 [error]: x264_encoder_encode failed

aborted at input frame 33, output frame 0

That machine has 32GBs of RAM, about 8GB are in use

[jdobbs]

That machine has 32GBs of RAM, about 8GB are in useYeah. But that's a 32 bit version of X264 (it has to be to work with AVISYNTH) -- and it has a reduced memory limit. With that said, though, 25MB isn't really that much. Something must have gotten it close to the limit before that happened (the large frame size, maybe?)

This part bothers me:clpi_parse.c:138: failed signature match expected (HDMV0200) got (HDMV0300)I'm not asking it to parse the CLPI, I'm asking it to do an encode of an M2TS, and it seems to have decided it knows what I want more than I do.

[jdobbs]

That machine has 32GBs of RAM, about 8GB are in useI've tried a couple encodes of 3840x2160 to an ALTERNATE output using X264 (with your settings) and so far it has worked fine. I'll try some more...

[cartman0208]

I've tried a couple encodes of 3840x2160 to an ALTERNATE output using X264 (with your settings) and so far it has worked fine. I'll try some more...

I tried 3 so far ... output error is exactly the same everytime, except for the aborting frame in the last line, that differs slightly

I cant't think of anything wrong ... :(
Maybe someone else can do some tests?

[Mark_Venture]

I know you've been looking at NVENCC lately, and I love it.. especially since my one drive crashed and I have begun to re-rip a bunch of discs to Alt Movie Only... Its been working great, NVENCC and all...

Unfortunately today I ran into an issue with Avatar Extended Collector's Edition 3 disc set. Disc 1 has Three versions of the movie on it. Theatrical, Special Edition Re-Release, and Collector's Extended Cut. BR-RB seems to not see anything by 800.MPLS, even when selecting "other movie". Apparently the correct play lists are 850, 851 and 852 respectively, and it uses branching? (based on google searches).

I tried looking back in the thread to see if this was discussed, and couldn't find it (used "Search this thread..." and did just AVATAR as the search term. Found plenty on the RED_BIRD_2D disc which is the standard theatrical only disc, subtitle questions, and 3D, but not this).

Does anyone remember anything about this, or how to possibly get around it?

[jdobbs]

I tried 3 so far ... output error is exactly the same everytime, except for the aborting frame in the last line, that differs slightly

I cant't think of anything wrong ... :(
Maybe someone else can do some tests?I've tried several more -- and none have gotten an error.

Does it crash right away, or after running for some period? Do you have enough time to bring up the task manager and see how much memory it is using?

Which ALTERNATE preset are you using?

Can you post the contents of the AVS file right after it fails so I can see if that may have an impact?

[cartman0208]

Does it crash right away, or after running for some period? Do you have enough time to bring up the task manager and see how much memory it is using?

Which ALTERNATE preset are you using?

Can you post the contents of the AVS file right after it fails so I can see if that may have an impact?

It takes about 3 seconds where the used memory goes quickly up from 8.5 to 10.5 GB and then drops immediately back to 8.5GB after the error message.

Preset is 00005

The AVS file is pretty short:
#Created by BD Rebuilder - v0.61.09
DirectshowSource("V:\FULLDISC\JUSTICE_LEAGUE\BDMV\STREAM\00015.m2ts", fps=23.976, framecount=172689, audio=false)
ConvertToYV12().AssumeFPS(24000,1001)

[BuddTX]

It seems to me, that most of my encodes work with "Automatically crop black borders", just a relatively few of my encodes do not fail, but when I find an encode that fails, it will consistently fail. When I use the "UHD_LIMIT_ENCODE=n", if the encode is going to fail, will still fail with only 10 minutes of data, so that is how I can tell that an encode will fail without spending several days processing the encode (I also turn down all the quality settings). Next encode that fails, I will post the details of both the successful and failed logs. Thanks JDobbs!

[cartman0208]

What preset(s) do you use?
And are your sources UHDs or *normal* BDs?

[jdobbs]

It takes about 3 seconds where the used memory goes quickly up from 8.5 to 10.5 GB and then drops immediately back to 8.5GB after the error message.

Preset is 00005

The AVS file is pretty short:
#Created by BD Rebuilder - v0.61.09
DirectshowSource("V:\FULLDISC\JUSTICE_LEAGUE\BDMV\STREAM\00015.m2ts", fps=23.976, framecount=172689, audio=false)
ConvertToYV12().AssumeFPS(24000,1001)
Just as a test, try downloading a newer version of X264 (32 bit version) and replace the one included with BD-RB, and see if it makes a difference. For that matter, maybe trying an older (smaller) version might be a good idea as well.

[cartman0208]

Just as a test, try downloading a newer version of X264 (32 bit version) and replace the one included with BD-RB, and see if it makes a difference. For that matter, maybe trying an older (smaller) version might be a good idea as well.

Tried it but no success... error message is the same
BUT ... when I delete "--bframes 3" from the string, it works ...
The failed signature message is still there but no malloc error ... and I see progress

Is there anything more I can do to localize the issue?

[jdobbs]

Tried it but no success... error message is the same
BUT ... when I delete "--bframes 3" from the string, it works ...
The failed signature message is still there but no malloc error ... and I see progress

Is there anything more I can do to localize the issue? The signature thing is no big deal -- it just bothers me that they do it without asking or being told to do so.

The weird thing is that adding the "--bframes 3" is actually redundant. The default value is 3. I only use it in the command line because I like to be explicit on values that are outlined in the standard.

While it is running, can you open up Task Manager, click on "Details", and then on CPU (so it orders by CPU usage) and see how much memory X264.exe is using?

[cartman0208]

While it is running, can you open up Task Manager, click on "Details", and then on CPU (so it orders by CPU usage) and see how much memory X264.exe is using?

The H.264 Process uses roughly 3GB

Meanwhile I installed BDRB freshly on a VM and there I have no issues on the same settings (I didn't try more, as that one is really slow) and the process uses around 800MB. Autocrop is also working...

So my encoding machine seems to be messed up somehow :(
Sorry for all the trouble...

[jdobbs]

The H.264 Process uses roughly 3GB

Meanwhile I installed BDRB freshly on a VM and there I have no issues on the same settings (I didn't try more, as that one is really slow) and the process uses around 800MB. Autocrop is also working...

So my encoding machine seems to be messed up somehow :(
Sorry for all the trouble...Interesting. On my system it is using about 2.5GB when it is executing an x264 reencode of a 2160p source. That is on a system that has a total memory amount of 8GB.

I wonder what is causing the difference? I have to guess that x264 is allocating memory based on what is available -- and somehow it might be making a mistake or pushing it to a "too much" point. The other possibility might be an issue with your memory. I've see it happen before where glitches go away by simply removing and reseating the memory modules (I've experienced that one personally). But, you'd think that would show somewhere else as well (unless other apps are never needing that much memory and the "glitch" point is never being reached).

[meadrocks]

I'm having a problem with Howls Moving Castle. Options are Alternative Output, h265, auto-aac, mkv. Notice the Duration in the 4 sections.


$ mediainfo HOWLS_MOVING_CASTLE.mkv
General
Unique ID : 210199344552902314261481553146180215470 (0x9E22EBD388AAA84F99D8BF2B39BF22AE)
Complete name : HOWLS_MOVING_CASTLE.mkv
Format : Matroska
Format version : Version 2
File size : 2.43 GiB
Duration : 3 h 53 min
Overall bit rate : 1 490 kb/s
Encoded date : UTC 2020-07-26 21:09:42
Writing application : mkvmerge v9.7.1 ('Pandemonium') 32bit
Writing library : libebml v1.3.4 + libmatroska v1.4.5

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 59 min
Bit rate : 2 600 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (23976/1000) FPS
Original frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.052
Stream size : 2.17 GiB (89%)
Writing library : x265 3.1.2+1-76650bab70f9:[Windows][GCC 9.1.1][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=3 / numa-pools=8 / wpp /
no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=1920x1080 /
interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=3 /
no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-hrd / info / hash=0 /
no-temporal-layers / open-gop / min-keyint=23 / keyint=240 / gop-lookahead=0 / bframes=4 /
b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=20 / lookahead-slices=6 / scenecut=40 /
radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp /
max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 /
dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 /
no-constrained-intra / strong-intra-smoothing / max-merge=3 / limit-refs=1 /
no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / weightp /
no-weightb / no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock / rd=3 /
early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / b-intra / no-splitrd-skip /
rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 /
crqpoffs=0 / rc=crf / crf=23.7 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 /
ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 /
no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=0 /
overscan=0 / videoformat=5 / range=0 / colorprim=2 / transfer=2 / colormatrix=2 /
chromaloc=0 / display-window=0cll=0,0 / min-luma=0 / max-luma=1023 /
log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps /
no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp /
no-aq-motion / no-hdr / no-hdr-opt / no-dhdr10-opt / no-idr-recovery-sei /
analysis-reuse-level=5 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=0 /
refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 /
copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq /
no-svt / no-field / qp-adaptation-range=1.00
Default : Yes
Forced : No

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : A_AAC-2
Duration : 1 h 59 min
Bit rate : 277 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 237 MiB (10%)
Language : English
Default : Yes
Forced : No

Text #1
ID : 3
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 3 h 49 min
Bit rate : 10.8 kb/s
Count of elements : 2845
Stream size : 17.7 MiB (1%)
Language : English
Default : No
Forced : No

Text #2
ID : 4
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 3 h 53 min
Bit rate : 7 807 b/s
Count of elements : 2062
Stream size : 13.0 MiB (1%)
Language : English
Default : No
Forced : No

Menu
00:00:00.000 : en:00:00:00.000
00:01:09.069 : en:00:01:09.069
00:05:03.302 : en:00:05:03.302
00:12:27.037 : en:00:12:27.037
00:18:27.397 : en:00:18:27.397
00:23:21.691 : en:00:23:21.691
00:28:56.025 : en:00:28:56.025
00:33:18.287 : en:00:33:18.287
00:40:14.703 : en:00:40:14.703
00:45:35.023 : en:00:45:35.023
00:49:20.248 : en:00:49:20.248
00:55:30.618 : en:00:55:30.618
00:58:36.804 : en:00:58:36.804
01:04:58.185 : en:01:04:58.185
01:10:58.545 : en:01:10:58.545
01:15:28.815 : en:01:15:28.815
01:20:30.116 : en:01:20:30.116
01:25:26.412 : en:01:25:26.412
01:32:35.841 : en:01:32:35.841
01:38:39.204 : en:01:38:39.204
01:44:26.551 : en:01:44:26.551
01:48:27.792 : en:01:48:27.792
01:52:24.028 : en:01:52:24.028
01:54:43.209 : en:01:54:43.209
01:59:27.201 : en:01:59:27.201



The movie is only 1:59, but in General its 3:53, its like its doubling the time the Text Durations, then using the longest time from Video, Audio & Text for the General Duration. This was made with BD-61.05.

Ive deleted the temp files but if necessary & can run it again & include them.

Thanks.

[meadrocks]

Here's a mediainfo on the BD source.


C:\BD_Rebuilder61.05\Tools>MediaInfo.exe c:\dvdrip\HOWLS_MOVING_CASTLE
General
Complete name : c:\dvdrip\HOWLS_MOVING_CASTLE
Format : Blu-ray movie
Format profile : BD-Java
Duration : 1 h 59 min
Overall bit rate : 1 b/s

Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : 27
Duration : 1 h 59 min
Bit rate mode : Constant
Bit rate : 3 178 kb/s
Nominal bit rate : 3 000 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Stream size : 2.65 GiB
format_identifier : HDMV
Source : 00008.m2ts

Audio #1
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Codec ID : 129
Duration : 1 h 59 min
Bit rate mode : Constant
Bit rate : 448 kb/s
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 382 MiB
Language : English
Service kind : Complete Main
bsid : 6
dialnorm : -27
dialnorm : -27 dB
compr : -0.28
compr : -0.28 dB
acmod : 7
lfeon : 1
dialnorm_Average : -27
dialnorm_Average : -27 dB
dialnorm_Minimum : -27
dialnorm_Minimum : -27 dB
dialnorm_Maximum : -27
dialnorm_Maximum : -27 dB
dialnorm_Count : 1877
compr_Average : 2.71
compr_Average : 2.71 dB
compr_Minimum : -9.27
compr_Minimum : -9.27 dB
compr_Maximum : 6.02
compr_Maximum : 6.02 dB
compr_Count : 1772
format_identifier : AC-3
Source : 00008.m2ts

Audio #2
ID : 4353 (0x1101)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Codec ID : 129
Duration : 1 h 59 min
Bit rate mode : Constant
Bit rate : 448 kb/s
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 382 MiB
Language : Japanese
Service kind : Complete Main
bsid : 6
dialnorm : -27
dialnorm : -27 dB
compr : -0.28
compr : -0.28 dB
acmod : 7
lfeon : 1
dialnorm_Average : -27
dialnorm_Average : -27 dB
dialnorm_Minimum : -27
dialnorm_Minimum : -27 dB
dialnorm_Maximum : -27
dialnorm_Maximum : -27 dB
dialnorm_Count : 1877
compr_Average : 2.91
compr_Average : 2.91 dB
compr_Minimum : -8.89
compr_Minimum : -8.89 dB
compr_Maximum : 6.02
compr_Maximum : 6.02 dB
compr_Count : 1841
format_identifier : AC-3
Source : 00008.m2ts

Audio #3
ID : 4354 (0x1102)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Codec ID : 129
Duration : 1 h 59 min
Bit rate mode : Constant
Bit rate : 448 kb/s
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 382 MiB
Language : French
Service kind : Complete Main
bsid : 6
dialnorm : -27
dialnorm : -27 dB
compr : -0.28
compr : -0.28 dB
acmod : 7
lfeon : 1
dialnorm_Average : -27
dialnorm_Average : -27 dB
dialnorm_Minimum : -27
dialnorm_Minimum : -27 dB
dialnorm_Maximum : -27
dialnorm_Maximum : -27 dB
dialnorm_Count : 1877
compr_Average : 2.75
compr_Average : 2.75 dB
compr_Minimum : -8.52
compr_Minimum : -8.52 dB
compr_Maximum : 6.02
compr_Maximum : 6.02 dB
compr_Count : 1812
format_identifier : AC-3
Source : 00008.m2ts

Text #1
ID : 4608 (0x1200)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144
Duration : 1 h 59 min
Delay relative to video : 22 s 105 ms
Language : English
Source : 00008.m2ts

Text #2
ID : 4609 (0x1201)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144
Duration : 1 h 58 min
Delay relative to video : 11 s 178 ms
Language : English
Source : 00008.m2ts

Text #3
ID : 4610 (0x1202)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144
Duration : 1 h 58 min
Delay relative to video : 11 s 178 ms
Language : French
Source : 00008.m2ts

Menu
00:00:00.000 : Chapter 1
00:01:08.276 : Chapter 2
00:05:02.927 : Chapter 3
00:12:26.829 : Chapter 4
00:18:27.272 : Chapter 5
00:23:20.774 : Chapter 6
00:28:55.942 : Chapter 7
00:33:17.787 : Chapter 8
00:40:14.995 : Chapter 9
00:45:34.398 : Chapter 10
00:49:19.873 : Chapter 11
00:55:30.368 : Chapter 12
00:58:36.930 : Chapter 13
01:04:58.311 : Chapter 14
01:10:58.796 : Chapter 15
01:15:28.023 : Chapter 16
01:20:29.491 : Chapter 17
01:25:25.578 : Chapter 18
01:32:34.882 : Chapter 19
01:38:39.455 : Chapter 20
01:44:26.426 : Chapter 21
01:48:27.792 : Chapter 22
01:52:23.486 : Chapter 23
01:54:43.042 : Chapter 24
01:59:12.228 : Chapter 25

General
Complete name : c:\dvdrip\HOWLS_MOVING_CASTLE\CERTIFICATE\app.discroot.crt
File size : 766 Bytes

General
Complete name : c:\dvdrip\HOWLS_MOVING_CASTLE\CERTIFICATE\BACKUP\app.discroot.crt
File size : 766 Bytes

General
Complete name : c:\dvdrip\HOWLS_MOVING_CASTLE\CERTIFICATE\BACKUP\bu.discroot.crt
File size : 766 Bytes

General
Complete name : c:\dvdrip\HOWLS_MOVING_CASTLE\CERTIFICATE\BACKUP\id.bdmv
File size : 104 Bytes

General
Complete name : c:\dvdrip\HOWLS_MOVING_CASTLE\CERTIFICATE\bu.discroot.crt
File size : 766 Bytes

General
Complete name : c:\dvdrip\HOWLS_MOVING_CASTLE\CERTIFICATE\id.bdmv
File size : 104 Bytes

General
Complete name : c:\dvdrip\HOWLS_MOVING_CASTLE\disc.inf
File size : 219 Bytes

[jdobbs]

I'm having a problem with Howls Moving Castle. Options are Alternative Output, h265, auto-aac, mkv. Notice the Duration in the 4 sections.


The movie is only 1:59, but in General its 3:53, its like its doubling the time the Text Durations, then using the longest time from Video, Audio & Text for the General Duration. This was made with BD-61.05.

Ive deleted the temp files but if necessary & can run it again & include them.

Thanks.That is a really weird one. The only explanation I can see is that somehow either: 1) The PGS files have something off within them (either in the original or created by TSMUXER during demux). or 2) MKVMERGE is somehow misreading the timestamps in the PGS file when it is creating the MKV.

[Lathe]

@Lathe - Are you using your SSD while encoding? It might wear it out faster, but a spinning platter drive could be a limiting factor. Also, what are you using to decode? On my previous system (FX-8350) I got a 10% bump in performance using x264's internal LAVF versus my vid card. The reason is the internal LAVF is the only way to take advantage of a 64-bit pipe in BD RB. I have to assume a Ryzen 5 would be even better.

@AmigaFuture - Oh, God. I'm glad someone else said it. I'm running two drives with two OS's right now that I swap between. I'm TRYING to ease myself into Win10 and I hate it. It's ugly, bloated and clunky. It'll take forever to root out all the M$ crap and tweak it to function smoothly like Win7.

Hey Bro, sorry to reply so late (Doom9 has NEVER sent prompts of replies) Yeah, I am using my new M2 SSD which I believe plugs directly into the MOBO. Supposed to be pretty fast. Interestingly, since this last comment a month or more ago when I use the x264 CMD line it does seem to utilize the CPU more. I'll hafta go back now and figure out WTH I was talking about :)

[Lathe]

Still breathing. I haven't spent as much time on BD-RB as I'd like. My dream is to get a GTX1660 so I can work on NVENC encoding, but the wife seems to think we should concentrate on things like food, fuel, clothing and a roof over our head instead. Women. They just don't understand geek economics, do they?

Sorry, just seeing this now, that's great :D

Food... SO overrated... http://lathe-of-heaven.com/no.gif

[Lathe]

Thanks for posting your tale. In my case its been over FOUR YEARS since my video PC has worked! Loaded with drives of course, and since we moved houses/locations the mobo has refused to come alive. This used to happen when I'd leave it for months in the summer, and it would sometimes balk when re-firing the thing for winter, but now it remains quiet.

I have dreaded the work associated with building a new PC but maybe your experience will inspire me! In the Fall! :)

Well, I can't really take any credit. There is this shop with these guys who have been here nearby forever who work on computers. So, I gave one of them a quick call, gave them my sad story, basically stated what I wanted hardware wise and what I had, ran the actual parts by him to get his opinion, bought them from Amazon, had him build it.

@AmigaFuture I know, I know about W10, believe me. But, it was just the simplest option for the fellow building it. Otherwise we would be talking about 'ghosting' my old SSD drive and the old OS, etc., etc... It was just WAY more simple to buy the new faster M2 SSD drive from him with W10 already installed and used as the primary OS drive. He didn't even charge me for the OS. It's been fine though. It is really a no-brainer simply using Classic Start easily to get it to look like W7. And, it is just faster. I've never used the 'tiles' and all that crap since W8 anyway. There ARE a few little quirks here and there, but overall it is much faster and sleeker (of course the new generation SSD drive helps I'm sure :))

[Lathe]

Sorry, the last Apache update made the webserver case sensitive (again :mad: ) ... Since the link points to Avisynth_260.exe but the file is named AviSynth_260.exe you got a 404 :(

I just renamed the file, link should be working now.

Hey, sorry about the late reply, but thanks Bro, appreciate it! :D

[Lathe]

Wow. When was that posted... I must have missed it completely.

[Edit] Ok, I see. It was part of the "3 frigg'n MONTHS behind" post. I guess I just missed that part.

Sorry Boss... http://lathe-of-heaven.com/rolleyes2.gif

[Lathe]

but frankly I am skeptical of all of these "extensions" to HDR10 as I think they are getting ridiculous and may in the same category as "HD Audio" (which is nothing beyond a marketing gimmick that has been proven scientifically as nonsense). Of course that comment will likely result in responses from people with "magic ears" who will say how they can tell the difference (even though what they actually hear is increased baseline volume that the marketeers have implemented in HD audio to try and make it appear as if there is an actual difference). Double blind tests show that (other than the additional channels available available in HD formats) Dolby Digital 5.1 at 640Kbs is indistinguishable from an lossless original audio source. Okay, time to step down off my soapbox.

Poor JD... All those tours in 'Nam around those big guns... http://lathe-of-heaven.com/no.gif

[meadrocks]

That is a really weird one. The only explanation I can see is that somehow either: 1) The PGS files have something off within them (either in the original or created by TSMUXER during demux). or 2) MKVMERGE is somehow misreading the timestamps in the PGS file when it is creating the MKV.

What can I do to help you with this?

[Lathe]

Normal is in the eye of the beholder. :D



You got that right, just ask @gonca...




http://lathe-of-heaven.com/Groucho eyeroll1.gif

[cartman0208]

FOUND IT!

There is a similar problem here (https://forum.doom9.org/showthread.php?t=163825) which put me to the right direction.
The commandline states "--threads auto" ... that might do for 99% of the systems. But I build that machine mainly for encoding, with 2 Xeon 2699v3, that sum up (with hyperthreading) to 72 threads total.
Every thread of x264 uses a certain amount of RAM, which breaks the memory limitation of 32bit apps

I guess disabling hyperthreading ("--threads 36" is working with 2.8 GB RAM used) will solve the problem for me, but if someone builds a similar system or uses one of the mean AMD Threadrippers, they will also run into that Problem.
[edit] Read a little more: "--threads auto" creates 1.5 times CPU cores threads for encoding... So even with Hyperthreading switched off the encode would fail on my machine

[Lathe]

Uh, I kinda feel bad asking this amongst the more serious cutting edge stuff that you've been working on here (which I've just been catching up on and is truly amazing guys!) But, it's been a while since I used BDRB and I THOUGHT that I remembered that if you input a file that was not BR compliant, say an MKV file with the dimensions of 1920x800, that BDRB would automatically see that and using AVS would add borders to bring it up to compliance. BUT... maybe once you take that MKV file and put it through TSMuxer to put it into a BDMV folder format and THEN input that into BDRB, apparently it does not seem to do that but even setting the output size slightly smaller (to force re-encoding) the dimensions of the resulting m2ts file are unchanged...???

So, is that the deal then, whatever is INSIDE the BDMV folder is left untouched when inputted into BDRB, and borders are not automatically added?

I'm doing it over now and I simply added the AVS script to add borders, and of course in checking the processing .264 file it is now going to be compliant when it is done. I guess I had always thought that BDRB did that automatically with anything out of specification.

[BuddTX]

What preset(s) do you use?
And are your sources UHDs or *normal* BDs?

I cant recall if any DVD's imported into BD-RBD ever failed the "auto crop black borders", I think, from memory, maybe there were a few.

However, I mainly do 1080P Blu-ray sources, using X265 to process the encode.

I rough guess would be about 1 in 10 Blu-ray sources fail when "auto crop black borders" is selected.

Again, "from memory" I think I tested one encode with X264 when one encode failed using X265, and I believe it also failed, so both X265 and X264 failed with "auto crop black borders" selected for that encode.

Next encode that fails, I will try both x264 and x265.

[jdobbs]

FOUND IT!

There is a similar problem here (https://forum.doom9.org/showthread.php?t=163825) which put me to the right direction.
The commandline states "--threads auto" ... that might do for 99% of the systems. But I build that machine mainly for encoding, with 2 Xeon 2699v3, that sum up (with hyperthreading) to 72 threads total.
Every thread of x264 uses a certain amount of RAM, which breaks the memory limitation of 32bit apps

I guess disabling hyperthreading ("--threads 36" is working with 2.8 GB RAM used) will solve the problem for me, but if someone builds a similar system or uses one of the mean AMD Threadrippers, they will also run into that Problem.
[edit] Read a little more: "--threads auto" creates 1.5 times CPU cores threads for encoding... So even with Hyperthreading switched off the encode would fail on my machineI'll recheck and see if that option is actually necessary. If not I'll remove it, otherwise I'll create a hidden option to remove it.

[Edit] Actually that won't work because the default value is "auto". But... there is a HIDDEN option in BD-RB that will set the number of threads you want to use:

THREADS=n

n is the number of threads to use. The limit is 16. I may have to look at increasing that limit. X264 has a limit of 128, but they say "realistically you should never set it this high".

[jdobbs]

Uh, I kinda feel bad asking this amongst the more serious cutting edge stuff that you've been working on here (which I've just been catching up on and is truly amazing guys!) But, it's been a while since I used BDRB and I THOUGHT that I remembered that if you input a file that was not BR compliant, say an MKV file with the dimensions of 1920x800, that BDRB would automatically see that and using AVS would add borders to bring it up to compliance. BUT... maybe once you take that MKV file and put it through TSMuxer to put it into a BDMV folder format and THEN input that into BDRB, apparently it does not seem to do that but even setting the output size slightly smaller (to force re-encoding) the dimensions of the resulting m2ts file are unchanged...???

So, is that the deal then, whatever is INSIDE the BDMV folder is left untouched when inputted into BDRB, and borders are not automatically added?

I'm doing it over now and I simply added the AVS script to add borders, and of course in checking the processing .264 file it is now going to be compliant when it is done. I guess I had always thought that BDRB did that automatically with anything out of specification.It is not automatically resized or padded during import. So you can have a pseudo-BD structure (thus the name) that contains a video stream that is not resized to be compliant.

But... when you run a job against that structure, the resizing occurs during reencoding and the output is compliant.

[jedihyte]

There is no '3D MVC mkv' option AFAIK. However, the Alternate Movie-only output includes a few options for SBS 3D mkv.

Ok thanks for the info.

Does anyone know how to get around the issue when making BD-25 Full backups of 3D movies without the pixelization/artifacts that show up every second of the playback using software players? (I have not seen the issue using a hardware player). But searching the forum I can see it happens to others, but not sure if there ever was a workaround found?

[gonca]

@AmigaFuture It is really a no-brainer :))
It is about your speed

[gonca]

You got that right, just ask @gonca...

This from a guy that plays with dolls

[jdobbs]

Ok thanks for the info.

Does anyone know how to get around the issue when making BD-25 Full backups of 3D movies without the pixelization/artifacts that show up every second of the playback using software players? (I have not seen the issue using a hardware player). But searching the forum I can see it happens to others, but not sure if there ever was a workaround found?If it only happens on a software player and never on a hardware player, it would lead to to believe that the software player is at fault, not the encode.

[meadrocks]

What can I do to help you with this?

I also have the same issue with Porco Rosso, Princess Mononoke, and The Iron Giant.


$ mediainfo IRON_GIANT.mkv
General
Unique ID : 249929721907896038595676073595108680533 (0xBC06B6AAA7854E4A9BA9125D1FA56355)
Complete name : IRON_GIANT.mkv
Format : Matroska
Format version : Version 2
File size : 1.76 GiB
Duration : 2 h 55 min
Overall bit rate : 1 438 kb/s
Encoded date : UTC 2019-08-01 09:29:38
Writing application : mkvmerge v9.7.1 ('Pandemonium') 32bit
Writing library : libebml v1.3.4 + libmatroska v1.4.5

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 26 min
Bit rate : 2 608 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (23976/1000) FPS
Original frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.052
Stream size : 1.58 GiB (90%)
Writing library : x265 2.8+69-856f056d392e:[Windows][GCC 8.2.0][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=3 / numa-pools=8 /
wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=1920x1080 / interlace=0 /
total-frames=0 / level-idc=0 /
high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-hrd /
info / hash=0 / no-temporal-layers / open-gop / min-keyint=23 / keyint=240 / gop-lookahead=0 / bframes=4 /
b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=20 / lookahead-slices=6 / scenecut=40 / radl=0 /
no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 /
imit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 /
no-constrained-intra / strong-intra-smoothing / max-merge=2 / limit-refs=3 / no-limit-modes / me=1 / subme=2 /
merange=57 / temporal-mvp / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock /
rd=3 / no-early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / no-b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 /
psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=20.0 / qcomp=0.60 / qpstep=4 / stats-write=0 /
stats-read=0 / ipratio=1.40 / pbratio=1.30 / aq-mode=1 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 /
no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=0 / overscan=0 / videoformat=5 / range=0 / colorprim=2 /
transfer=2 / colormatrix=2 / chromaloc=0 / display-window=0 / max-cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 /
vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / n
o-opt-cu-delta-qp / no-aq-motion / no-hdr / no-hdr-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=5 /
scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-mv-type=0 / c
opy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei
Default : Yes
Forced : No

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : A_AAC-2
Duration : 1 h 26 min
Bit rate : 288 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 176 MiB (10%)
Language : English
Default : Yes
Forced : No

Text
ID : 3
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 2 h 54 min
Bit rate : 5 781 b/s
Count of elements : 2448
Stream size : 7.22 MiB (0%)
Language : English
Default : No
Forced : No

Menu
00:00:00.000 : en:00:00:00.000
00:02:26.896 : en:00:02:26.896
00:06:11.537 : en:00:06:11.537
00:08:58.454 : en:00:08:58.454
00:10:31.339 : en:00:10:31.339
00:12:47.558 : en:00:12:47.558
00:14:53.934 : en:00:14:53.934
00:16:23.899 : en:00:16:23.899
00:18:17.054 : en:00:18:17.054
00:20:36.401 : en:00:20:36.401
00:23:53.682 : en:00:23:53.682
00:25:47.504 : en:00:25:47.504
00:27:55.465 : en:00:27:55.465
00:29:57.045 : en:00:29:57.045
00:32:19.979 : en:00:32:19.979
00:33:42.395 : en:00:33:42.395
00:36:11.711 : en:00:36:11.711
00:37:54.188 : en:00:37:54.188
00:40:22.711 : en:00:40:22.711
00:44:04.808 : en:00:44:04.808
00:45:51.415 : en:00:45:51.415
00:48:07.968 : en:00:48:07.968
00:50:33.405 : en:00:50:33.405
00:52:33.108 : en:00:52:33.108
00:54:04.366 : en:00:54:04.366
00:58:31.132 : en:00:58:31.132
01:01:27.517 : en:01:01:27.517
01:03:42.443 : en:01:03:42.443
01:05:36.140 : en:01:05:36.140
01:09:03.347 : en:01:09:03.347
01:10:19.256 : en:01:10:19.256
01:14:00.394 : en:01:14:00.394
01:16:40.762 : en:01:16:40.762
01:19:28.513 : en:01:19:28.513
01:26:38.818 : en:01:26:38.818

[gonca]

Can you retry without the subtitles
and if possible post a before and after subtitle file

[cartman0208]

I'll recheck and see if that option is actually necessary. If not I'll remove it, otherwise I'll create a hidden option to remove it.

[Edit] Actually that won't work because the default value is "auto". But... there is a HIDDEN option in BD-RB that will set the number of threads you want to use:

THREADS=n

n is the number of threads to use. The limit is 16. I may have to look at increasing that limit. X264 has a limit of 128, but they say "realistically you should never set it this high".

I set it to 16, but the CPU utilization is now around 20% at the most.
Changing values of MULTIPROCESS doesn't make it faster.
Even 36 threads don't use more CPU

Guess I'll have to go with that

[BuddTX]

I cant recall if any DVD's imported into BD-RBD ever failed the "auto crop black borders", I think, from memory, maybe there were a few.

However, I mainly do 1080P Blu-ray sources, using X265 to process the encode.

I rough guess would be about 1 in 10 Blu-ray sources fail when "auto crop black borders" is selected.

Again, "from memory" I think I tested one encode with X264 when one encode failed using X265, and I believe it also failed, so both X265 and X264 failed with "auto crop black borders" selected for that encode.

Next encode that fails, I will try both x264 and x265.

Forgot to add, that I create, almost exclusively, MKV Files.

[Lathe]

It is not automatically resized or padded during import. So you can have a pseudo-BD structure (thus the name) that contains a video stream that is not resized to be compliant.

But... when you run a job against that structure, the resizing occurs during reencoding and the output is compliant.

Thanks kindly for the answer JD, but I must not be understanding you correctly because I THOUGHT that is exactly what I just did. I used the non-compliant BDMV folder (containing the TSMuxer muxed MKV file still at 1920x800) and BDRB did re-encode it, but the resulting BDMV folder and thus the m2ts file inside it STILL was the non-compliant AR of 1920x800, nothing changed.

What am I missing here...?

[Lathe]

This from a guy that plays with dolls

Well, at least I am procreating within my species... :D

[Lathe]

Just in addition...

So, what I ended up doing was re-running the exact same job with BDRB, but this time adding the AVS code for 'add borders', so yes this time the borders were added to the re-encode just fine. BUT... I had thought that BDRB detected that automatically and that you didn't need to add the AVS code.

[meadrocks]

What can I do to help you with this?

In alternate.txt I copied my MKV entry to the end, 00041, changed ctype from 1 to 5,
ran it, but it still created a mkv file and mediainfo reports the General->Format to be Matroska. I was curious to see if the mp4 container fixed the Duration problems that the mkv seems to have.

[cartman0208]

In alternate.txt I copied my MKV entry to the end, 00041, changed ctype from 1 to 5,
ran it, but it still created a mkv file and mediainfo reports the General->Format to be Matroska. I was curious to see if the mp4 container fixed the Duration problems that the mkv seems to have.

Did you try Subtitle Edit (https://github.com/SubtitleEdit/subtitleedit/releases) to check out the Subtitles?

I can confirm that x265 only results in MKVs, even if MP4 is requested as container.
x264 seems to output the correct container.

[meadrocks]

Did you try Subtitle Edit (https://github.com/SubtitleEdit/subtitleedit/releases) to check out the Subtitles?

I can confirm that x265 only results in MKVs, even if MP4 is requested as container.
x264 seems to output the correct container.

I'll check it out Sunday, as Im out of town.

[AmigaFuture]

You got that right, just ask @gonca...

Just ask at-gonca?? That's like saying "I want to use the ATM machine." since ATM is an acronym for Automatic Teller Machine.

"Ur funny."

More fun poking.."But, it's been a while since I used BDRB..." "It is been a while..", are you sure it IS been a while? Though MrVideo and I aren't related, it's fun to catch stuff.

Well, at least I am procreating within my species... :D

Yet, you speak...and type. Are you "Possessed"??

FOUND IT!

There is a similar problem here (https://forum.doom9.org/showthread.php?t=163825) which put me to the right direction.
The commandline states "--threads auto" ... that might do for 99% of the systems. But I build that machine mainly for encoding, with 2 Xeon 2699v3, that sum up (with hyperthreading) to 72 threads total.
Every thread of x264 uses a certain amount of RAM, which breaks the memory limitation of 32bit apps

I guess disabling hyperthreading ("--threads 36" is working with 2.8 GB RAM used) will solve the problem for me, but if someone builds a similar system or uses one of the mean AMD Threadrippers, they will also run into that Problem.
[edit] Read a little more: "--threads auto" creates 1.5 times CPU cores threads for encoding... So even with Hyperthreading switched off the encode would fail on my machine

Thhhhhhat is interesting!! I'll check that with my new budget Ryzen build. Still using Windows 7, ahhhhhhhhh...it's sweet.

[Lathe]

Just ask at-gonca?? That's like saying "I want to use the ATM machine." since ATM is an acronym for Automatic Teller Machine.

"Ur funny."

More fun poking.."But, it's been a while since I used BDRB..." "It is been a while..", are you sure it IS been a while? Though MrVideo and I aren't related, it's fun to catch stuff.



Yet, you speak...and type. Are you "Possessed"??



I think BOTH you and Mr. Video should be severely beaten...

And, BTW... "it's" is also a proper contraction for "it has" Mr. WeeWeeHead...



http://lathe-of-heaven.com/Suspicious Cat.gif

[jdobbs]

I set it to 16, but the CPU utilization is now around 20% at the most.
Changing values of MULTIPROCESS doesn't make it faster.
Even 36 threads don't use more CPU

Guess I'll have to go with thatI've changed the limits on THREADS=n for the next release. It can be set up to 128 (the limit for X264).

[jdobbs]

I can confirm that x265 only results in MKVs, even if MP4 is requested as container.
x264 seems to output the correct container. Actually I'd forgotten about that. Earlier versions of MP4BOX (like the 2012 one included with BD-RB) didn't support HEVC -- so BD-RB only allowed MKV for writing an HEVC stream.

I'm testing a version with HEVC support that is a good balance of size/capability to include with BD-RB in the next release.

[Edit] Completed. You will be able to output HEVC to an MP4 in the next release.

[jdobbs]

Thanks kindly for the answer JD, but I must not be understanding you correctly because I THOUGHT that is exactly what I just did. I used the non-compliant BDMV folder (containing the TSMuxer muxed MKV file still at 1920x800) and BDRB did re-encode it, but the resulting BDMV folder and thus the m2ts file inside it STILL was the non-compliant AR of 1920x800, nothing changed.

What am I missing here...?One thing that might cause that: Did you import the file before NVENCC was implemented in BD-RB and then use NVENCC for the encode? If so, the NVENCC adjustments wouldn't be found in the PSEUDO.INF file (created during import) and the resizing and/or padding wouldn't occur.

Just throwing out possibilities.

[cartman0208]

I've changed the limits on THREADS=n for the next release. It can be set up to 128 (the limit for X264).

:thanks:

and

Completed. You will be able to output HEVC to an MP4 in the next release.

:thanks:

Was anyone able to do a successful Autocrop with HEVC (UHD) content?
The AVS file is running, there is just no cropping done.

[jdobbs]

Was anyone able to do a successful Autocrop with HEVC (UHD) content?
The AVS file is running, there is just no cropping done.I'll do some testing.

Were you using NVENCC or X265 for your output?

[jdobbs]

Was anyone able to do a successful Autocrop with HEVC (UHD) content?
The AVS file is running, there is just no cropping done.I'll do some testing.

Were you using NVENCC or X265 for your output?I just tried it with an HEVC 2160p source... and it didn't work. The AVS file looks okay, but when I play it back (even directly with no reencoding) it isn't cropping. It's almost as if the AutoCrop() call isn't even there -- but it is.


[Edit] Just tried it with RoboCrop (another auto cropping plugin) as suggested by BuddTX (https://forum.doom9.org/showthread.php?p=1919471#post1919471) and got the same results.

[gonca]

Quick question
Do AutoCrop or RoboCrop work with 10 bit video?

[jdobbs]

Quick question
Do AutoCrop or RoboCrop work with 10 bit video?That could be an issue, yes. AVISYNTH only works in 8 bit. But I would have assumed that the conversion takes place during decoding, otherwise AVISYNTH shouldn't work at all with the source.

[cartman0208]

I just tried it with an HEVC 2160p source... and it didn't work. The AVS file looks okay, but when I play it back (even directly with no reencoding) it isn't cropping. It's almost as if the AutoCrop() call isn't even there -- but it is.


Can confirm that ... I did a conversion with x265, but also just played the AVS file in MPC-HC.
I'm afraid, in 2005, when AutoCrop was last updated, 10bit and 4K was far away :(

[Mike-uk]

@jdobbs are you using multipass ??

Multi pass frame encoding
When determining the QP to use for encoding a frame, it is beneficial if NVENC knows the overall complexity of the frame to distribute the available bit budget in the most optimal manner. In some situations, multi-pass encoding may also help catch larger motion between frames. For this purpose, NVENC supports the following types of multi-pass frame encoding modes:

1-pass per frame encoding (NV_ENC_MULTI_PASS_DISABLED)
2-passes per frame, with first pass in quarter resolution and second pass in full resolution (NV_ENC_TWO_PASS_QUARTER_RESOLUTION)
2-passes per frame, with both passes in full resolution (NV_ENC_TWO_PASS_FULL_RESOLUION).
In 1-pass rate control modes, NVENC estimates the required QP for the macroblock and immediately encodes the macroblock. In 2-pass rate control modes, NVENC estimates the complexity of the frame to be encoded and determines bit distribution across the frame in the first pass. In the second pass, NVENC encodes macroblocks in the frame using the distribution determined in the first pass. As a result, with 2-pass rate control modes, NVENC can distribute the bits more optimally within the frame and can reach closer to the target bitrate, especially for CBR encoding. Note, however, that everything else being the same, performance of 2-pass rate control mode is lower than that of 1-pass rate control mode. The client application should choose an appropriate multi-pass rate control mode after evaluating various modes, as each of the modes has its own advantages and disadvantages. NV_ENC_TWO_PASS_FULL_RESOLUION generates better statistics for the second pass, whereas NV_ENC_TWO_PASS_QUARTER_RESOLUTION results in larger motion vectors being caught and fed as hints to second pass.

and from nvencc

--multipass <string>
Multi pass mode. Available only for --vbr and --cbr. [API v10.0]

none
2pass-quarter
2pass-full

[Sharc]

History repeats ..... ;)

https://forum.doom9.org/showpost.php?p=1918354&postcount=29626

From rigaya's release notes of Release 5.10:
Options below will be mapped to each other depending on the NVENC API version used.

SDK API 9.0, 9.1: --vbrhq
SDK API 10.0: --vbr --multipass 2pass-full

The 2 are currently equivalent.
He also wrote that in future the --vbrhq of API 9.0, 9.1 may be dropped and and only the syntax of API 10.0 will be supported.

[Mike-uk]

History repeats ..... ;)

https://forum.doom9.org/showpost.php?p=1918354&postcount=29626

lol didnt see your post :P

[Sharc]

No problem. Double-stitching has its benefits :D

[SquallMX]

CRF Prediction is broken for x265.

----------------------
[08/02/20] BD Rebuilder v0.61.09
[14:41:06] Source: THE_FAST_AND_THE_FURIOUS_2001
- Input BD size: 57.81 GB
- Approximate total content: [02:36:40.348]
- Target BD size: 24.41 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), CRF
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[14:41:08] PHASE ONE, Encoding
- [14:41:08] Processing: VID_00165 (1 of 4)
- [14:41:08] Extracting A/V streams [VID_00165]
- [14:41:14] Reencoding video [VID_00165]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 576 frames
- [14:41:14] Performing CRF Prediction...
- Analyzing 16.00 14.40 15.45 14.70 15.25 14.85 15.15 [15.15]
- [14:42:22] Encoding using constant rate factor.
- Performing size-correcting second pass...
- [14:45:07] Video Encode complete
- [14:45:07] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [14:45:07] Multiplexing M2TS
- [14:45:11] Blanking: VID_00252 (2 of 4)
- [14:45:11] Blanking: VID_00253 (3 of 4)
- [14:45:11] Processing: VID_00294 (4 of 4)
- [14:45:11] Extracting A/V streams [VID_00294]
- [14:54:27] Reencoding video [VID_00294]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 153,721 frames
- [14:54:27] Performing CRF Prediction...
- Analyzing 16.30 2.00 [2.00]
- [14:55:03] Encoding using constant rate factor.
[14:56:53] - Aborted by user request

CRF 2 is insanely low, I loaded the prediction AVS script / M2TS on VDub, seems to be broken at I frames, so its mainly static frames, which explains the low CRF value.

This is the sample file:
https://mega.nz/file/ATpg3Q6J#XK09Bq7i5cyL5eE1nU24ddgXb2Q7UKhTTZVPpz4w9Es

[cartman0208]

CRF Prediction is broken for x265.



CRF 2 is insanely low, I loaded the prediction AVS script / M2TS on VDub, seems to be broken at I frames, so its mainly static frames, which explains the low CRF value.

This is the sample file:
https://mega.nz/file/ATpg3Q6J#XK09Bq7i5cyL5eE1nU24ddgXb2Q7UKhTTZVPpz4w9Es

Did you try a complete encode?
I had CRF Values of 1.00 but the output was not oversized ...

[SquallMX]

Did you try a complete encode?
I had CRF Values of 1.00 but the output was not oversized ...

It's almost impossible for a 35mm live action film to get those CRF values for a 4K BD-25, for reference when using nVidia HW Accelerated encoding I got a value of 22.15.

[meadrocks]

Actually I'd forgotten about that. Earlier versions of MP4BOX (like the 2012 one included with BD-RB) didn't support HEVC -- so BD-RB only allowed MKV for writing an HEVC stream.

I'm testing a version with HEVC support that is a good balance of size/capability to include with BD-RB in the next release.

[Edit] Completed. You will be able to output HEVC to an MP4 in the next release.

I'll wait for the next release & try both container types.

[Lathe]

One thing that might cause that: Did you import the file before NVENCC was implemented in BD-RB and then use NVENCC for the encode? If so, the NVENCC adjustments wouldn't be found in the PSEUDO.INF file (created during import) and the resizing and/or padding wouldn't occur.

Just throwing out possibilities.

Hmmm, thanks for the thought, but no... I just simply took the MKV file, used TSMuxer to convert it to a BDMV/CERT format, then used that as the source like I would any ripped Blu-ray for BDRB. I then set the size output slightly smaller so that it would force a re-encode (the original size of the BDMV folder was around 18 Gigs. I used the LAV internal encoder as usual. I didn't change anything that I normally would do.

No biggie really, as long as I know now that BDRB will not automatically detect the improper AR within the BDMV folder, I will just add the AVS script from now on if I have to do that. I don't do that very often, only when I have a pretty high resolution file that has the lossless audio (I know, I know... :)) but I want to convert the video to a playable Blu-ray format.

It just occurred to me too that maybe if I just simply imported the original MKV file into BDRB and let IT created the pseudo BDMV folder, then perhaps it would detect the non-compliant AR in the MKV file. I guess I was just trying to skip having BDRB do that step.

[cartman0208]

It's almost impossible for a 35mm live action film to get those CRF values for a 4K BD-25, for reference when using nVidia HW Accelerated encoding I got a value of 22.15.

Sure, but did you actually complete the encode (in your log it was aborted)?
Might be a display issue and an other value is used ... just see, what output size you get...

[jdobbs]

Status update: Got pretty much everything reported in bug reports fixed. Currently working on HDR10+ support. I'll probably be releasing the next version in a day or two.

[jdobbs]

CRF Prediction is broken for x265.



CRF 2 is insanely low, I loaded the prediction AVS script / M2TS on VDub, seems to be broken at I frames, so its mainly static frames, which explains the low CRF value.

This is the sample file:
https://mega.nz/file/ATpg3Q6J#XK09Bq7i5cyL5eE1nU24ddgXb2Q7UKhTTZVPpz4w9EsThe AVS isn't used for HEVC prediction because the SelectRangeEvery() filter just doesn't seem to be able to find keyframes on HEVC. You also can't look at the M2TS used as input because a player (but not an encoder) will have trouble with the crazy DTS/PTS values.

You pretty much have to look at the output of the prediction to actually see how it went.

[Lathe]

Status update: Got pretty much everything reported in bug reports fixed. Currently working on HDR10+ support. I'll probably be releasing the next version in a day or two.

Thanks Boss! http://lathe-of-heaven.com/tiphat.gif

[Lathe]

On a side note, with my new build everything works really well, except when I try to utilize more of the CPU. I wonder if the Ryzen 5's are known easily to over heat? It's ONLY when I try to do an encode which of course tries to utilize most of the CPU. If it is running full out at 90%+ it gradually gets hotter and hotter until it reaches about 90 degrees and shuts the computer off. The case I got has FIVE bloody fans in it too for Goodness sake! With a huge one on the side to draw in cooler air. I'm taking it back in to where they built it, and as an added help I bought an after market CPU cooler. But, it really shouldn't be doing that anyway.

The only work around I could come up with is when I did an encode using x264 either with or without BDRB, the only way I can keep the CPU from overheating is to deselect the cores/threads in the 'Affinity' setting when you right-click the x264 process in TM. So, if I only use 1/4 of the 'cores' or whatever they are and the CPU is only running at 25%, I can just BARELY keep it under the redline temperature. Sure is frustrating. Still is a lot faster than my old one, but it would be kind of nice to be able to use the entire potential of the CPU.

I'm HOPING that he will find what exactly is causing that (hopefully NOT a bad CPU!) because just adding the after market cooler alone will not fix that. I guess I'll just hafta see what happens...

[cartman0208]

On a side note, with my new build everything works really well, except when I try to utilize more of the CPU. I wonder if the Ryzen 5's are known easily to over heat? It's ONLY when I try to do an encode which of course tries to utilize most of the CPU. If it is running full out at 90%+ it gradually gets hotter and hotter until it reaches about 90 degrees and shuts the computer off. The case I got has FIVE bloody fans in it too for Goodness sake! With a huge one on the side to draw in cooler air. I'm taking it back in to where they built it, and as an added help I bought an after market CPU cooler. But, it really shouldn't be doing that anyway.


It's like cars with a lot of power and crappy tires ... can't get the power on the street ;)
One hint I can give: thermal conductive paste, not too little, not too much...
If the heat from the CPU cant get to the heat spreader you can have the best cooling solution ever but it won't cool.

I, personally, use AIO watercoolers ... easy setup, lots of space left in the case, way cooler than all the aircoolers I had and not even that expensive...

[gonca]

@Lathe
The coolers supplied by Intel and AMD with their CPUs are not the greatest, to be kind.
Like cartman0208 said, get an AIO watercooler
I like Corsair, and don't get one with a small radiator

[MrVideo]

@Lathe
The coolers supplied by Intel and AMD with their CPUs are not the greatest, to be kind.
Like cartman0208 said, get an AIO watercooler
I like Corsair, and don't get one with a small radiator
You still got to get the paste correct.

[BuddTX]

You still got to get the paste correct.

Check out this IC Graphite Pad, supposed to work just as good as the best thermal pastes, but with no drying out or installation errors:
https://youtu.be/YpphKzmDiJM
https://www.amazon.com/dp/B07CKVW18G

[SquallMX]

Did you try a complete encode?
I had CRF Values of 1.00 but the output was not oversized ...

Yes I did:

[08/03/20] BD Rebuilder v0.61.09
[21:37:28] Source: THE_FAST_AND_THE_FURIOUS_2001
- Input BD size: 57.81 GB
- Approximate total content: [02:36:40.348]
- Target BD size: 24.41 GB
- Windows Version: 6.2 [9200]
- Quality: Better (Faster), CRF
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[21:37:32] PHASE ONE, Encoding
- [21:37:32] Processing: VID_00165 (1 of 4)
- [21:37:32] Extracting A/V streams [VID_00165]
- [21:37:37] Reencoding video [VID_00165]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 576 frames
- [21:37:37] Performing CRF Prediction...
- Analyzing 15.80 15.30 14.95 [14.95]
- [21:37:53] Encoding using constant rate factor.
- [21:38:40] Video Encode complete
- [21:38:40] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [21:38:40] Multiplexing M2TS
- [21:38:44] Blanking: VID_00252 (2 of 4)
- [21:38:44] Blanking: VID_00253 (3 of 4)
- [21:38:44] Processing: VID_00294 (4 of 4)
- [21:38:44] Extracting A/V streams [VID_00294]
- [21:48:00] Reencoding video [VID_00294]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 153,721 frames
- [21:48:00] Performing CRF Prediction...
- Analyzing 15.90 8.45 4.72 2.86 1.93 1.46 1.23 1.11 1.06 1.03 1.02 1.01 [1.01]
- [21:49:38] Encoding using constant rate factor.
- Performing size-correcting second pass...
- [09:34:24] Video Encode complete
- [09:34:24] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4354 (spa): Keeping original audio
- Track 4357 (eng): Keeping original audio
- [09:34:24] Multiplexing M2TS
[09:35:24]PHASE ONE complete
[09:35:24]PHASE TWO - Rebuild Started
- [09:35:24] Rebuilding BD file Structure
[09:35:44] - Encode and Rebuild complete

[Status]
LABEL=THE_FAST_AND_THE_FURIOUS_2001
VERSION=v0.61.09
SOURCE_SIZE=62073708041
SOURCE_VIDEO_SIZE=60550053888
TARGET_SIZE=26214400000
REDUCTION=.407774134977166
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=0
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
UHD_V3_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=4
REBUILD_COMPLETE=1
[00165]
AUDIO=1
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=78560708
NSTART=27000000
NEND=28081079
NSIZE=80283648
FLINK=0
MLINK=0
[00294]
AUDIO=101001
PGS=1111111111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=24612185139
NSTART=27000000
NEND=315515101
NSIZE=23796996096
FLINK=0
MLINK=0


After creating an enormous 40+ GBs .hevc file, BD-RB did a 2-pass which resulted in a properly fit 23 GB output but pretty much regates the point of a CRF mode, which is getting similar quality than 2 pass mode on 1 pass, in fact, because 2-pass mode uses a "fast" 1 pass the encoding time was longer (8 Hours [Normal 2-Pass mode] vs 12 Hours [CRF mode + size-correcting second pass]).

So software encoding CRF prediction is definitely buggy, at least in version 61.09. Looks like its using FFMPEG for getting the sample data but the results are static images (crazy DTS/PTS values?) so the prediction calculates a very low CRF value:

"D:\Archivos de Programa\BD Rebuilder UHD\tools\ffmpeg.exe" -ss 5998.7456 -i
"L:\BLU-RAYS\4K\THE FAST AND THE FURIOUS 2001\BDMV\STREAM\00294.m2ts"
-frames 48 -an -sn -codec copy -f mpegts - >> "C:\TEMP\WORKFILES\00294.AVS.SMPL.m2ts"

[MrVideo]

Please code wrap, do not quote wrap output text.

[MrVideo]

Check out this IC Graphite Pad, supposed to work just as good as the best thermal pastes, but with no drying out or installation errors:
https://www.amazon.com/dp/B07CKVW18G
Neat stuff. Thanks for the tip. I ordered one from ebay. 50 cents more, but free shipping.

[jdobbs]

Hmmm, thanks for the thought, but no... I just simply took the MKV file, used TSMuxer to convert it to a BDMV/CERT format, then used that as the source like I would any ripped Blu-ray for BDRB. I then set the size output slightly smaller so that it would force a re-encode (the original size of the BDMV folder was around 18 Gigs. I used the LAV internal encoder as usual. I didn't change anything that I normally would do.

No biggie really, as long as I know now that BDRB will not automatically detect the improper AR within the BDMV folder, I will just add the AVS script from now on if I have to do that. I don't do that very often, only when I have a pretty high resolution file that has the lossless audio (I know, I know... :)) but I want to convert the video to a playable Blu-ray format.

It just occurred to me too that maybe if I just simply imported the original MKV file into BDRB and let IT created the pseudo BDMV folder, then perhaps it would detect the non-compliant AR in the MKV file. I guess I was just trying to skip having BDRB do that step.Yes. That would be the problem. If you create the source manually (using TSMUXER) then BD-RB has no way of knowing the AR is noncompliant and noting it for adjustment. TSMUXER will set the CLPI's flags to the nearest compliant resolution. Since there is no PSEUDO.INI file, BD-RB thinks it's a standard BD and assumes the CLPI is correct.

[jdobbs]

After creating an enormous 40+ GBs .hevc file, BD-RB did a 2-pass which resulted in a properly fit 23 GB output but pretty much regates the point of a CRF mode, which is getting similar quality than 2 pass mode on 1 pass, in fact, because 2-pass mode uses a "fast" 1 pass the encoding time was longer (8 Hours [Normal 2-Pass mode] vs 12 Hours [CRF mode + size-correcting second pass]).

So software encoding CRF prediction is definitely buggy, at least in version 61.09. Looks like its using FFMPEG for getting the sample data but the results are static images (crazy DTS/PTS values?) so the prediction calculates a very low CRF value:Yes. It needs work -- that's the purpose of releasing a test version, so I can get feedback. But as I said before -- the "static images" you mention AREN'T a problem when encoding for prediction... that is an issue with whatever you are using in playback.

The reason I think it is important to get CQM & CRF working well ISN'T just speed. My testing shows that you get BETTER QUALITY at the same size using CQM/CRF than you do with one-pass VBR bitrate encoding. NVENCC has no true two-pass option and X265 is so slow on UHD that you want to try and avoid two-pass. So the time comparison shouldn't be between one-pass and CQM/CRF -- but between CQM/CRF and a two pass encode (averaging across multiple discs -- not just one). A second pass in CQM/CRF mode only occurs when the final target size is exceeded to a point where it won't fit on the target disc.

It's also important to point out that the reason BD-RB has to create an alternate prediction method for HEVC is because AVISYNTH doesn't handle HEVC well. The problems stem from the fact that when trying to seek (SelectRangeEvery) with AVISYNTH on an HEVC source you don't seem to land on (or adjust from) i-frames and you get garbage output -- making the method used for AVC prediction (upon which I spent a considerable amount of time) is a non-starter. Part of the purpose of the "test" releases is to figure out a good way to predict without using AVISYNTH. So the new method (for HEVC) uses FFMPEG to pull out sections of the source M2TS and combines them into an M2TS to use as the prediction source.

With all that said... I'm working on trying to make the initial CQM/CRF value more accurate. But it ain't easy... and that's why you don't see CQM/CRF prediction algorithms laying around waiting for someone to pick one up to use.

[jdobbs]

Unless I've missed something in testing, I think the latest version is very close to release for public consumption. Please download and do some testing on this release:

BD Rebuilder v0.61.10 (https://jammernhilftnichts.de/jdobbs/BD-RBV06110.zip)

Summary of changes:- Added support for NVIDIA NVENC encoding.
- Corrected an error that could cause BD-RB
to exit in failure when attempting a size-
correcting second pass in CRF mode while
doing a UHD backup.
- Added code that will update the HDR flags
in the MPLS file for sources in which HDR
was not established until after reencoding
on full backups.
- Fixed an error in which MPEG2 sources may
not make video adjustments detected during
import when reencoding. This could result
in stretched or compressed images.
- Created a workaround for a problem with
converting PAL to NTSC flags during import
which could confuse TSMUXER's recognition
of video resolution.
- Added code to adapt to UHD sources that are
not sized to either 3840(h) or 2160(v).
- Corrected an issue in which video sources
that are an odd size during import might
use the wrong resizing when HEVC encoding
is enabled.
- Fixed a bug in which large audio offsets
detected during import were not being
interpreted correctly.
- Fixed a bug that could cause undersizing
when an AC3 stream is kept intact because
the original is smaller than the selected
reencoder bitrate. This typically only
happens on DVD imports.
- Fixed an error that could result in wrong
aspect ratio on imported sources that are
being resized.
- Corrected an issue in which some command
line settings were not being set when a
non-UHD source is output as V3.
- Added a routine to ensure formatting of
CRF values consistent.
- Updated CQM prediction routines.
- Fixed an issue that can cause the CQM/CRF
sample file to have a zero length when
used in other-than-US regions.
- Modified NVENCC options to eliminate vbrhq
from the command line, as it is targeted
to be deprecated. Replaced by "vbr" and
manually enabling "--multipass 2pass-full"
(the newer equivalent of vbrhq).
- Rewrote the "Bitstream Exception" TSMUXER
error workaround routine so it now uses
a more efficient method -- and better
adjusts audio sync. It also now adjusts
for Dolby Vision exception errors.
- Fixed an issue in which BT709 sources were
not being encoded with proper settings.
- Increased the accepted value of the THREADS
hidden option from 16 to 128. Note: While
128 is accepted for x264 -- realistically
you should never set it that high.
- Added support for HDR10+ A JSON file is
created concurrently with video extraction.
HDR10+ streams are now identified in the
streams list by a "+" next to "HEVC". Note
that "*" indicates Dolby Vision. "*+"=both.
- Changed the ALTERNATE settings so creating
a preset that outputs HEVC to MP4 is now
allowed.
- Updated the included version of MP4BOX to
support HEVC.
- Updated the included versions of X265 to a
newer (v3.2.1) release.
- Other minor corrections and cosmetic fixes.

[SquallMX]

Yes. It needs work -- that's the purpose of releasing a test version, so I can get feedback. But as I said before -- the "static images" you mention AREN'T a problem when encoding for prediction... that is an issue with whatever you are using in playback.


I have to disagree, the prediction file generated by BD-RB is also only 48 frames, here a direct feed from LASTCMD.TXT:

C:\Windows\System32>"D:\Archivos de Programa\BD Rebuilder UHD\tools\ffmpeg.exe" -probesize 100MB -i "C:\TEMP\WORKFILES\00294.AVS.SMPL.m2ts" -frames 48 -an -pix_fmt yuv420p10le -f yuv4mpegpipe -strict -1 - | "D:\Archivos de Programa\BD Rebuilder UHD\tools\x265-64.exe" - --preset faster --profile main10 --uhd-bd --repeat-headers --vbv-bufsize 45000 --vbv-maxrate 48000 --hdr --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,50)" --max-cll "1000,221" --fps 23.976 --slow-firstpass --pass 1 --sar 1:1 --qpfile "C:\TEMP\WORKFILES\VID_00294.CHP" --keyint 24 --crf 2.86 --y4m --no-strong-intra-smoothing --no-sao --stats "C:\TEMP\WORKFILES\TEMP.265.stats" --output "C:\TEMP\WORKFILES\TEMP.265"
ffmpeg version 3.4 Copyright (c) 2000-2017 the FFmpeg developers
built with gcc 7.2.0 (GCC)
configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-cuda --enable-cuvid --enable-d3d11va --enable-nvenc --enable-dxva2 --enable-avisynth --enable-libmfx
libavutil 55. 78.100 / 55. 78.100
libavcodec 57.107.100 / 57.107.100
libavformat 57. 83.100 / 57. 83.100
libavdevice 57. 10.100 / 57. 10.100
libavfilter 6.107.100 / 6.107.100
libswscale 4. 8.100 / 4. 8.100
libswresample 2. 9.100 / 2. 9.100
libpostproc 54. 7.100 / 54. 7.100
Input #0, mpegts, from 'C:\TEMP\WORKFILES\00294.AVS.SMPL.m2ts':
Duration: 00:00:02.00, start: 1.525122, bitrate: 4537470 kb/s
Program 1
Metadata:
service_name : Service01
service_provider: FFmpeg
Stream #0:0[0x100]: Video: hevc (Main 10) ([36][0][0][0] / 0x0024), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 3840x2160 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn, 23.98 tbc
Stream mapping:
Stream #0:0 -> #0:0 (hevc (native) -> wrapped_avframe (native))
Press [q] to stop, [?] for help
[hevc @ 00000207dc1208e0] First slice in a frame missing.
Last message repeated 6 times
[hevc @ 00000207dcd200a0] First slice in a frame missing.
Last message repeated 6 times
[yuv4mpegpipe @ 00000207e22d2020] Warning: generating non standard YUV stream. Mjpegtools will not work.
Output #0, yuv4mpegpipe, to 'pipe:':
Metadata:
encoder : Lavf57.83.100
Stream #0:0: Video: wrapped_avframe, yuv420p10le, 3840x2160 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 23.98 fps, 23.98 tbn, 23.98 tbc
Metadata:
encoder : Lavc57.107.100 wrapped_avframe
y4m [info]: 3840x2160 fps 23976/1000 i420p10 sar 1:1 unknown frame count
raw [info]: output file: C:\TEMP\WORKFILES\TEMP.265
x265 [info]: HEVC encoder version 3.2.1+3-b4b2ecac21f6
x265 [info]: build info [Windows][GCC 9.2.0][64 bit] 10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x265 [warning]: uhd-bd: Turning off open GOP
x265 [warning]: uhd-bd: keyframeMin is always 1
x265 [info]: Main 10 profile, Level-5.1 (High tier)
x265 [info]: Thread pool created using 24 threads
x265 [info]: Slices : 1
x265 [info]: frame threads / pool features : 4 / wpp(34 rows)
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : hex / 57 / 2 / 2
x265 [info]: Keyframe min / max / scenecut / bias: 1 / 24 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt : 15 / 4 / 0
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 2 / on / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 2 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : CRF-2.9 / 0.60
x265 [info]: VBV/HRD buffer / max-rate / init : 45000 / 48000 / 0.900
x265 [info]: tools: rd=2 psy-rd=2.00 early-skip rskip signhide tmvp fast-intra
x265 [info]: tools: lslices=8 deblock stats-write
frame= 48 fps= 13 q=-0.0 Lsize= 1166400kB time=00:00:02.00 bitrate=4772803.0kbits/s dup=1 drop=0 speed=0.532x
video:25kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 4712628.500000%
x265 [info]: frame I: 4, Avg QP:8.74 kb/s: 113388.31
x265 [info]: frame P: 10, Avg QP:8.47 kb/s: 77779.35
x265 [info]: frame B: 34, Avg QP:11.63 kb/s: 42043.62
x265 [info]: Weighted P-Frames: Y:90.0% UV:90.0%
x265 [info]: consecutive B-frames: 35.7% 0.0% 7.1% 0.0% 57.1%

encoded 48 frames in 6.38s (7.53 fps), 55433.96 kb/s, Avg QP:10.73

C:\Windows\System32>

And here the output file from that preddiction pass:

https://mega.nz/file/NXpgmSJb#LPjgIryl4uhVVoKklJ8nZFQrIjcv60bdzKUTdTOTmog

Looks like even FFMPEG is incapable of properly read the "00294.AVS.SMPL.m2ts" file created for CRF prediction, and that is the reason for the ultra low values that results in a oversized file.

With all that said... I'm working on trying to make the initial CQM/CRF value more accurate. But it ain't easy... and that's why you don't see CQM/CRF prediction algorithms laying around waiting for someone to pick one up to use.

Thanks for your hard work, is what makes a difference from lesser quality bloatware (cough, cough, DVDFa... cough, cough).

EDIT: I Think I found the culprit, "-frames 48" removing it from lastcmd.txt creates a proper output file!!!

Looks like FFMPEG is actually capable of properly decoding the prediction file, but for some reason, BD-RB is parsing a incorrect parameter for "-frames" that cut the prediction file to early.

EDIT 2: Still present in 0.61.10 (obviously).

[cartman0208]

Unless I've missed something in testing, I think the latest version is very close to release for public consumption. Please download and do some testing on this release:

BD Rebuilder v0.61.10 (https://jammernhilftnichts.de/jdobbs/BD-RBV06110.zip)


Long list of changes ... thanks a lot for the hard work ... testing ... :)

[jdobbs]

@SquallMX

The "-frames 48" is a bit confusing. I'll have a look at it. If it were taken from the command line that is creating the SAMPLE it would make more sense.

The sample file is created using groups of 48 frames (about 2 seconds each), each starting with an iframe (the start of which is pulled from the CLPI's EP_map table). FFMPEG is run multiple times outputting 48 frames with each iteration giving an approximate 1% of the entire source file (by default, it is adjustable with HIDDENOPTS and it can be a larger percentage sample on smaller files).

Why it is in the command line used to encode the sample makes me think there has to be a bug somewhere. The question is "why is it not happening to me?" I assume the source being encoded is larger than 4800 frames?

Can you send me (or post) your settings (the contents of BDREBUILDER.INI). Maybe something in the settings is triggering the glitch.

[Edit] Never mind. I found it.

It was a mistake in coding and you were absolutely right. No wonder the prediction was so far off. It appears to be left over from a test I was doing to compare encoding 48 frames at a time as opposed to extracting them with FFMPEG beforehand and then encoding the group. Since most of my recent testing has been using NVENCC (the logic flow of which was copied from the X265 routine) -- I guess I just outright failed to switch it back from the test code in the X265 routine.

Thanks for the help in identifying that bug.

I'll put in a fix, test it, and get another version up. I'm also working on improving the prediction algorithm on small streams -- so it will probably be a day or two (at the most).

[jedihyte]

If it only happens on a software player and never on a hardware player, it would lead to to believe that the software player is at fault, not the encode.

Thanks for the reply. Ya its something I've just had to deal with for several years, but just trying to find out if there were any new developments. BTW, It only happens if it goes through BD-Rebuilder first, as the software player (PowerDVD) plays the original 3D discs fine without artifacts. I know 3D is not a priority and is dying :(, but I'm still a huge 3D fan. Thanks for all the cool BD Rebuilder developments over the years :).

[jdobbs]

Thanks for the reply. Ya its something I've just had to deal with for several years, but just trying to find out if there were any new developments. BTW, It only happens if it goes through BD-Rebuilder first, as the software player (PowerDVD) plays the original 3D discs fine without artifacts. I know 3D is not a priority and is dying :(, but I'm still a huge 3D fan. Thanks for all the cool BD Rebuilder developments over the years :).Sorry I wasn't more help. Maybe someone else in the forum has experienced the same issue and found a solution -- anyone?

[Ch3vr0n]

@jedihyte

Sorry I wasn't more help. Maybe someone else in the forum has experienced the same issue and found a solution -- anyone?

i have asked that before and supposedly using a newer version of FRIM than the one that currently comes with BDRB fixes that issue. I have it downloaded, i just havent had the time to test it. https://www.videohelp.com/software/FRIM

[jdobbs]

@jedihyte



i have asked that before and supposedly using a newer version of FRIM than the one that currently comes with BDRB fixes that issue. I have it downloaded, i just havent had the time to test it. https://www.videohelp.com/software/FRIMI'll download it and test to see if it causes any interface issues.

[meadrocks]

It failed on making alternative output; mp4, x265, auto-aac. version is 61.10


----------------------
[08/06/20] BD Rebuilder v0.61.10
[17:10:20] Source: HOWLS_MOVING_CASTLE_00200
- Input BD size: 32.77 GB
- Approximate total content: [01:59:27.243]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MP4 Container, HEVC 1920x1080, Auto-AAC
- Quality: High Quality (Default)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[17:10:20] PHASE ONE, Encoding
- [17:10:20] Processing: VID_00100 (1 of 3)
- [17:10:20] Extracting A/V streams [VID_00100]
- [17:15:44] Reencoding video [VID_00100]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 17,911 frames
- [17:15:44] Reencoding: VID_00100, Pass 1 of 1
- Analyzing 21.50 23.70 [23.70]
- [17:30:53] Video Encode complete
- [17:30:53] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AAC...
- [17:38:06] Processing: VID_00102 (2 of 3)
- [17:38:06] Extracting A/V streams [VID_00102]
- [17:46:32] Reencoding video [VID_00102]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 147,121 frames
- [17:46:32] Reencoding: VID_00102, Pass 1 of 1
- Analyzing 21.50 21.80 [21.85]
- [20:12:38] Video Encode complete
- [20:12:38] Processing: VID_00103 (3 of 3)
- [20:12:38] Extracting A/V streams [VID_00103]
- [20:13:01] Reencoding video [VID_00103]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 6,810 frames
- [20:13:01] Reencoding: VID_00103, Pass 1 of 1
- Analyzing 21.45 18.50 17.95 17.70 [17.70]
- [20:18:48] Video Encode complete
[20:18:48]PHASE ONE complete
[20:18:48]PHASE TWO - Rebuild Started
- [20:18:48] Building ALTERNATE OUTPUT Structure
- ERROR in attempt to mux (MP4BOX)
[20:19:10] - Failed to REBUILD
-----------------------
[20:19:10] PROCESSING BATCH FILE [2]




[00041]
caption=MP4 Container, HEVC 1920x1080, Auto-AAC
vEncoder=1
vBitrate=2000
vKeyint=Auto
aBitrate=*
aType=1
vFormat=5
cType=5

[MrVideo]

but when I changed your blocking from CODE to QUOTE (so I could get line wrapping and better read the command line) and saw what was actually happening I realized I was zigging when I should have been zagging.
Keep it code wrapped, but manually cut long lines with returns. Especially useful when the included text is really long. Long quotes are very annoying.

[BuddTX]

Status update: Got pretty much everything reported in bug reports fixed. Currently working on HDR10+ support. I'll probably be releasing the next version in a day or two. NICE! Thank you!:thanks:

[cartman0208]

More of a feature request:

Is it possible to turn quality up even more?
like:
--preset quality --multipass 2pass-full

I just tried the commandline ... encoding speed drops by another 25% but that wouldn't matter for me ... still around 20x faster than CPU

Or is that already covered by the QUALITY_ULTRA hidden switch?

:thanks:

[jdobbs]

More of a feature request:

Is it possible to turn quality up even more?
like:
--preset quality --multipass 2pass-full

I just tried the commandline ... encoding speed drops by another 25% but that wouldn't matter for me ... still around 20x faster than CPU

Or is that already covered by the QUALITY_ULTRA hidden switch?

:thanks:Funny you should ask. Yes, you can get that with a hidden switch. But I left that one off the non-hidden list purposely.

Note, however: QUALITY_ULTRA doesn't apply to NVENCC, only X264 & X265.

I ran numerous tests on numerous sources using that setting. Even though the encode slowed down significantly (making you think it does more), the SSIM results were worse than the next lower setting (quality, without multipass). All the existing settings position in the quality list were based on SSIM values first and encode speed second.

My results could be wrong... but it would have to be wrong on every source I tried.

If you want, though, you can still use that setting by editing the INI file and changing ENCODE_QUALITY to a value of 4. But I wouldn't recommend it.

Just as an aside: Have you tested the HDR10+ capability I added to v0.61.10? My player doesn't support HDR10+ so I could only do limited testing (header and value checks, etc.).

[jdobbs]

Update:

I'm currently still working on CQM/CRF encode prediction improvements. In testing, I'm finding that maybe my current prediction tables for HEVC/2160p sources using X265 may need to be adjusted. Unfortunately the means encoding multiple sources at every possible CRF value so I can calculate the relationship of each value to all the rest. It's just taking forever to do that at 4-7fps.

I'm also tuning the actual encode routine to prevent some of the anomalies that have been reported.

[jdobbs]

@meadrocks

Can you post the ALTERNATE preset you used for HEVC/MP4 output? I tested it on different sources and it worked for me.

I notice you are using a multipart source. Try it on a single part source and see if that's related to the problem. I'd do it but my system is bogged down doing prediction table encodes.

[meadrocks]

@meadrocks

Can you post the ALTERNATE preset you used for HEVC/MP4 output?


Sorry, where do I find that info?
Do you mean this?
[00041]
caption=MP4 Container, HEVC 1920x1080, Auto-AAC
vEncoder=1
vBitrate=2000
vKeyint=Auto
aBitrate=*
aType=1
vFormat=5
cType=5

[Sharc]

I ran numerous tests on numerous sources using that setting. Even though the encode slowed down significantly (making you think it does more), the SSIM results were worse than the next lower setting (quality, without multipass). All the existing settings position in the quality list were based on SSIM values first and encode speed second.

My results could be wrong... but it would have to be wrong on every source I tried.
I have some doubt whether NVIDIA's 2pass method contributes much to quality in the sense of best match with the original or highest SSIM. They write:
As a result, with 2-pass rate control modes, NVENC can distribute the bits more optimally within the frame and can reach closer to the target bitrate, especially for CBR encoding. Note, however, that everything else being the same, performance of 2-pass rate control mode is lower than that of 1-pass rate control mode. The client application should choose an appropriate multi-pass rate control mode after evaluating various modes, as each of the modes has its own advantages and disadvantages.
In earlier tests I found that disabling -aq resulted in better SSIM than using it. The explanation is probably that -aq is to some extent a psychovisual optimization which conflicts with PSNR -- and possibly also with SSIM --optimization.
From NVIDIA on Spatial AQ:
Spatial AQ mode adjusts the QP values based on spatial characteristics of the frame. Since the low complexity flat regions are visually more perceptible to quality differences than high complexity detailed regions, extra bits are allocated to flat regions of the frame at the cost of the regions having high spatial detail. Although spatial AQ improves the perceptible visual quality of the encoded video, the required bit redistribution results in PSNR drop in most of the cases. Therefore, during PSNR-based evaluation, this feature should be turned off.
Perhaps we see a similar effect with the 2pass modes?

[cartman0208]

I ran numerous tests on numerous sources using that setting. Even though the encode slowed down significantly (making you think it does more), the SSIM results were worse than the next lower setting (quality, without multipass). All the existing settings position in the quality list were based on SSIM values first and encode speed second.



I have some doubt whether NVIDIA's 2pass method contributes much to quality in the sense of best match with the original or highest SSIM. They write:
Quote:
As a result, with 2-pass rate control modes, NVENC can distribute the bits more optimally within the frame and can reach closer to the target bitrate, especially for CBR encoding. Note, however, that everything else being the same, performance of 2-pass rate control mode is lower than that of 1-pass rate control mode. The client application should choose an appropriate multi-pass rate control mode after evaluating various modes, as each of the modes has its own advantages and disadvantages.


Well that is surprising ... and I though 2pass gives the ultimate quality ...
Do you see the same on the other quality settings, where 2pass is involved?


Just as an aside: Have you tested the HDR10+ capability I added to v0.61.10? My player doesn't support HDR10+ so I could only do limited testing (header and value checks, etc.).

Actually my player also doesn't support HDR10+ while my TV does :o
I'm still in the process of evaluating players ... (any suggestions?)
I was hoping to get the meta information in an alternate output.

[edit]
Tried an encode of a HDR10+ disk... all fine up to the point where the source resolution (or compression) changes:
---------------------
[08.08.20] BD Rebuilder v0.61.10
[09:59:02] Source: HOBBS_AND_SHAW
- Input BD size: 87,50 GB
- Approximate total content: [04:37:04.228]
- Target BD size: 47,36 GB
- Windows Version: 6.2 [9200]
- Quality: Ultra-High (Extremely Slow), CQM
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[09:59:05] PHASE ONE, Encoding
- [09:59:05] Processing: VID_00165 (1 of 63)
- [09:59:05] Extracting A/V streams [VID_00165]
- [09:59:10] Reencoding video [VID_00165]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 576 frames
- [09:59:10] Performing CQM Prediction...
- Analyzing 18,40 21,55 22,00 [22,08]
- [09:59:32] Encoding using constant quality mode.
- [09:59:51] Video Encode complete
- [09:59:51] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:59:51] Multiplexing M2TS
- [09:59:56] Processing: VID_00294 (2 of 63)
- [09:59:56] Extracting A/V streams [VID_00294]
- [10:05:08] Reencoding video [VID_00294]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 195.520 frames
- [10:05:08] Performing CQM Prediction...
- Analyzing 18,90 21,45 21,75 [21,75]
- [10:10:56] Encoding using constant quality mode.
- [11:49:51] Video Encode complete
- [11:49:51] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (deu): Keeping original audio
- [11:49:51] Multiplexing M2TS
- [11:51:52] Processing: VID_00368 (3 of 63)
- [11:51:52] Extracting A/V streams [VID_00368]
- [11:52:10] Reencoding video [VID_00368]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 14.728 frames
- [11:52:10] Performing CQM Prediction...
- Analyzing 20,15 23,20 24,60 24,90 [24,90]
- [11:52:38] Encoding using constant quality mode.
- [12:00:04] Video Encode complete
- [12:00:04] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [12:00:04] Multiplexing M2TS
- [12:00:09] Processing: VID_00369 (4 of 63)
- [12:00:09] Extracting A/V streams [VID_00369]
- [12:00:16] Reencoding video [VID_00369]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 5.241 frames
- [12:00:16] Performing CQM Prediction...
- Analyzing 16,35 [12:00:17] - Failed video encode, aborted


Also tried an alternate output that fails if autocrop is enabled. Without ... went fine, but the MKV output file flickers when played directly on my TV, like the brightness meta info is switched on and off every half a second ...

[Ch3vr0n]

I tried the new FRIM, decode worked, encode process was stuck at , FPS (yes just a comma, that's not a typo) on my 9900k, then just failed on the newer one. Encoding wouldn't even start (after enabling dual GPU in the bios and installing the proper drivers and rebooting). Could be because the newer 1.30 zip contains a whole lot more files than the default 1.27. I just copied over the same 4 files and renamed the new FRIMDecode32.exe etc to FRIMDecode.exe

Tried the default one. Only copied the audio track for some reason. 26GB down to under 3GB for the main title including HD audio, yeah that aint right

oh and that is with the 61.05 version (i'll wait for the newer one until it gets updated with a newer frim)

[jdobbs]

Also tried an alternate output that fails if autocrop is enabled. Without ... went fine, but the MKV output file flickers when played directly on my TV, like the brightness meta info is switched on and off every half a second ...Interesting. That would make sense, since the metadata is inserted into i-frames (about every half second).

[cartman0208]

In the alternate output with intact video there's no such issues ... does that mean the metadata only fits to the original P, B and I-Frame sequence (or at least I-Frame interval)?
I guess, it's pretty hard to synchronize that in a reencode :eek:

[jdobbs]

In the alternate output with intact video there's no such issues ... does that mean the metadata only fits to the original P, B and I-Frame sequence (or at least I-Frame interval)?
I guess, it's pretty hard to synchronize that in a reencode :eek:It should be by scene, and a scene should always start with an i-frame. So my belief is that the sequence within that GOP (P & B frames) shouldn't matter.

In order to make sure the metadata matches the original i-frame positioning, BD-RB grabs the frame numbers of all i-frames in the original and uses them to force i-frames at the same position in the reencode (in the .CHP file).

That takes place for sure when creating a new BD structure. It's possible that I may be losing that when doing ALTERNATE output. It may be affected by the ability to create much longer GOP sequences in ALTERNATE files. For example, in a BD there is a limit as to how long a GOP can be (typically it's every 24 frames for a film source). But in ALTERNATE output you often (very often) see it expanded to 240 frames. That might play havoc with positioning of the metadata (just speculating)

The actual placement of the metadata in the newly encoded stream is done by X265 or NVENCC using a JSON file that was created from the original source.

This is all speculation until I look at the code and do some testing. I'll take a look and see what I can find. Unfortunately I'm no expert on HDR10+ and/or exactly how JSON files are applied. BD-RB uses 3rd party software to create the JSON and X265/NVENCC to apply it.

The downside is that the reason most people use GOP lengths of 240 is for encoding efficiency. If you have to keep the original i-frame positions, that goes out the window. Generally an encoder senses scene changes and inserts an i-frame when it changes -- that makes it even more complex. I believe the .CHP file overrides that, since it explicitly forces i-frames at certain points.

[Edit] Oh, and by the way, the --multipass option does seem to give better SSIM values in all the other modes. It's just in QUALITY mode that I saw that anomaly.

[Edit - again] I just scanned a JSON file, and there seems to be an entry in the file for every frame in the source. That would seem to imply that the scene change information would be kept correctly even if I didn't use the .CHP to force i-frames. Any experts out there want to chime in?

[cartman0208]

That takes place for sure when creating a new BD structure. It's possible that I may be losing that when doing ALTERNATE output. It may be affected by the ability to create much longer GOP sequences in ALTERNATE files. For example, in a BD there is a limit as to how long a GOP can be (typically it's every 24 frames for a film source). But in ALTERNATE output you often (very often) see it expanded to 240 frames. That might play havoc with positioning of the metadata (just speculating)


So just removing vKeyint=Auto from the alternate.txt could solve the problem?
I didn't know what to set and left it on all presets to Auto, since it's usually a good choice :D

[jdobbs]

So just removing vKeyint=Auto from the alternate.txt could solve the problem?
I didn't know what to set and left it on all presets to Auto, since it's usually a good choice :DAfter my last edit comment on my post, I'm not so sure. Since the JSON file contains data on every frame, it implies that the encoder can put a keyframe anywhere it wants -- but it can force one at the point where the metadata changes (a new scene) in the JSON file and add an SEI to the i-frame [keyframe] implementing the new metadata.

So that kinda' puts the theory of the GOP length as the cause as less likely.

[cartman0208]

After my last edit comment on my post, I'm not so sure. Since the JSON file contains data on every frame, it implies that the encoder can put a keyframe anywhere it wants -- but it can force one at the point where the metadata changes (a new scene) in the JSON file and add an SEI to the i-frame [keyframe] implementing the new metadata.

So that kinda' puts the theory of the GOP length as the cause as less likely.

OK, as you said... I had a look at source and output and the Keyframes match .. so that should not be the issue ...
I'll do some more testing on other sources
If that is fruitless, maybe we could join in here (https://forum.doom9.org/showthread.php?t=175947)

[edit]
I ran several encodes with NVEnc ... all the same flickering while playing.
Then I decided to make a SW encode and despite the fact that Mediainfo is almost identical, the SW encoded file with HDR10+ Metadata looked very good on my TV

[Sharc]

[Edit] Oh, and by the way, the --multipass option does seem to give better SSIM values in all the other modes. It's just in QUALITY mode that I saw that anomaly.

I am not aware of a document which explains what the presets or modes actually do in terms of setting or tuning the encoding parameters, and whether presets overwrite possibly conflicting commandline options. Or what is at the end just double stitching.
Maybe I am just missing something.

[meadrocks]

@meadrocks

Can you post the ALTERNATE preset you used for HEVC/MP4 output? I tested it on different sources and it worked for me.

I notice you are using a multipart source. Try it on a single part source and see if that's related to the problem. I'd do it but my system is bogged down doing prediction table encodes.

Watchmen Directors Cut Bluray also has the same problem with the English subtitles, they look correct duration in the source, but come out double length in the mkv. It also fails making a mp4 file. Its a multi part source. I cant find any single part source disks that have this problem.

[jdobbs]

I am not aware of a document which explains what the presets or modes actually do in terms of setting or tuning the encoding parameters, and whether presets overwrite possibly conflicting commandline options. Or what is at the end just double stitching.
Maybe I am just missing something.Neither am I. One of the reasons it took so long to implement NVENC was all the testing I had to do to determine things like which settings actually improved SSIM values (so I could decide which settings would represent the different BD-RB quality presets).

[jdobbs]

OK, as you said... I had a look at source and output and the Keyframes match .. so that should not be the issue ...
I'll do some more testing on other sources
If that is fruitless, maybe we could join in here (https://forum.doom9.org/showthread.php?t=175947)

[edit]
I ran several encodes with NVEnc ... all the same flickering while playing.
Then I decided to make a SW encode and despite the fact that Mediainfo is almost identical, the SW encoded file with HDR10+ Metadata looked very good on my TVBy SW encode, do you mean using "--avsw" in the command line instead of "--avhw"?

Have you tried using --avhw but changing the use of the JSON file to "--dhdr10-info copy"?

[jdobbs]

Watchmen Directors Cut Bluray also has the same problem with the English subtitles, they look correct duration in the source, but come out double length in the mkv. It also fails making a mp4 file. Its a multi part source. I cant find any single part source disks that have this problem.Thanks. I'll look at the code and see how it might be impacted by multi-part sources.

[jdobbs]

Also tried an alternate output that fails if autocrop is enabled. Without ... went fine, but the MKV output file flickers when played directly on my TV, like the brightness meta info is switched on and off every half a second ...I forgot to mention on this one -- if you use AUTOCROP it would force use of an AVS, which in turn causes you to lose HDR. Of course it shouldn't fail, and I'll look at that.

[cartman0208]

By SW encode, do you mean using "--avsw" in the command line instead of "--avhw"?

No ... I switched the encoder from nvencc to x264 & x265


Have you tried using --avhw but changing the use of the JSON file to "--dhdr10-info copy"?

Tried that, no change

I forgot to mention on this one -- if you use AUTOCROP it would force use of an AVS, which in turn causes you to lose HDR. Of course it shouldn't fail, and I'll look at that.

I read in other forums, that crop or resize don't get along with HDR10+, so I'll stick with the original resolution for those cases.

The currently used autocrop version had other issues, as we found out earlier in the thread...

[jdobbs]

I read in other forums, that crop or resize don't get along with HDR10+, so I'll stick with the original resolution for those cases.

The currently used autocrop version had other issues, as we found out earlier in the thread...Yeah, that makes sense. The HDR10+ metadata adjusts for things like the average brightness of the picture, etc., and then when you crop the black portion suddenly it changes the picture dramatically and it's unlikely that the calculated values used in HDR10+ apply anymore.

So... the JSON works with X265, but fails with NVENCC. And if you remove it (replaced by "copy") it still doesn't work... that means it isn't the JSON (or the use of it). It sure sounds like the problem is within NVENCC (or at least the way BD-RB is using it).

Anybody else out there done any testing of HDR10+? Your experiences?

[cartman0208]

Ok, I went and had a look at a competitive product (Staxrip) and guess what ... there's no issues with the file ... my TV shows that HDR10+ is played
Here's the commandline used:
U:\Tools\Staxrip\Apps\Encoders\NVEnc\NVEncC64.exe --avhw --vbrhq 0 --codec h265 --preset performance --profile main10 --level 5.1 --output-depth 10 --max-bitrate 30000 --vbr-quality 0 --aq --aq-temporal --bref-mode each --strict-gop --output-buf 128 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,50)" --dhdr10-info U:\Output\WORKFILES\VID_00685.JSON --colormatrix bt2020nc --colorprim bt2020 --transfer smpte2084 --colorrange auto --max-cll "1000,0" --chromaloc 2 --aud -i U:\Temp\BOHEMIAN_RHAPSODY_temp\BOHEMIAN_RHAPSODY.h265 -o U:\Temp\BOHEMIAN_RHAPSODY_temp\BOHEMIAN_RHAPSODY_temp_out.h265

(I used the JSON that was extracted by BDRB)

Now I have to figure out what causes the issues ... any clues?

[edit]
Here the BDRB Command line
"U:\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "U:\FULLDISC\BOHEMIAN_RHAPSODY\BDMV\STREAM\00685.m2ts" --codec hevc --preset performance --profile main10 --output-depth 10 --repeat-headers --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,50) --dhdr10-info "U:\OUTPUT\WORKFILES\VID_00685.JSON" --qp-min 0 --vbr 0 --vbr-quality 25 --aq-temporal --keyfile "U:\OUTPUT\WORKFILES\VID_00685.CHP" --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 48 -o "U:\OUTPUT\WORKFILES\VID_00685.AVS.hevc"

[gonca]

@cartman0208
Can you compare the two command lines to see if there are any differences?

[cartman0208]

@cartman0208
Can you compare the two command lines to see if there are any differences?

Posted above ... some quality differences ... could --strict-gop be the culprit ?

[gonca]

Had some issues getting back on Doom9
Here are the differences between the two command lines, all common switches removed
Don't have HDR10+ capability so you gonna have to test

Staxrip
--vbrhq 0 --level 5.1 --max-bitrate 30000 --vbr-quality 0 --aq --bref-mode each --strict-gop --output-buf 128
--colorrange auto --max-cll "1000,0"

BDRB
--repeat-headers --qp-min 0 --vbr 0 --vbr-quality 25 --keyfile "U:\OUTPUT\WORKFILES\VID_00685.CHP" --pic-struct
--vbv-bufsize 45000 --max-bitrate 48000 --gop-len 48

Use the command line , I would try removing the --keyfile entry and changing --gop-len to 24 on the BDRB line

[jdobbs]

Working on a recent bug report by cartman0208, and guess what... I found a bug that apparently has been there since at least 2012 (see this post (https://forum.doom9.org/showthread.php?p=1596646#post1596646)). That has to be a record for time-from-report-to-fix.

[Edit] Nope. It wasn't a record. I found a reference to that error dating back to 2009! It was a really obscure error that can only happen under very rare certain circumstances and only then if there is secondary video.

[jdobbs]

Ok, I went and had a look at a competitive product (Staxrip) and guess what ... there's no issues with the file ... my TV shows that HDR10+ is played
Here's the commandline used:

(I used the JSON that was extracted by BDRB)

Now I have to figure out what causes the issues ... any clues?

[edit]
Here the BDRB Command line
Posted above ... some quality differences ... could --strict-gop be the culprit ?Had some issues getting back on Doom9
Here are the differences between the two command lines, all common switches removed
Don't have HDR10+ capability so you gonna have to test

Staxrip
--vbrhq 0 --level 5.1 --max-bitrate 30000 --vbr-quality 0 --aq --bref-mode each --strict-gop --output-buf 128
--colorrange auto --max-cll "1000,0"

BDRB
--repeat-headers --qp-min 0 --vbr 0 --vbr-quality 25 --keyfile "U:\OUTPUT\WORKFILES\VID_00685.CHP" --pic-struct
--vbv-bufsize 45000 --max-bitrate 48000 --gop-len 48

Use the command line , I would try removing the --keyfile entry and changing --gop-len to 24 on the BDRB lineInteresting. Please let me know what you find.

[jdobbs]

Its a multi part source. I cant find any single part source disks that have this problem.This turned out to be a TSMUXER issue. I'd updated the version used for 4k adjustments to try and keep up with the improvements. The new one uses a new naming convention when concatenating files.

I hope there aren't more surprises like that.

[meadrocks]

This turned out to be a TSMUXER issue. I'd updated the version used for 4k adjustments to try and keep up with the improvements. The new one uses a new naming convention when concatenating files.

I hope there aren't more surprises like that.

I'll rerun Howls & Watchmen with the next release & give you feedback.

Thanks!

[cartman0208]

Interesting. Please let me know what you find.

OK, after 2 days of testing, gradually removing paramters from the stax-string and then adding the parameters from the BDRB string (which I should have done the other way around, because I found it on the second-to-last parameter :mad:) the cause for the flickering is found ...
If the --pic-struct is removed from the command line string, the file plays fine.

But I also noticed, some scenes are WAY to dark on my TV.
A file with intact video (vFormat=8 in the alternate.txt) on the other hand is bright in the same scenes.
I'll do some more testing to find the cause for that...

[Michi]

Bug on HEVC/V3 BluRays and x264/LAVF frameserving:

[08.12.20] BD Rebuilder v0.61.10
[20:38:07] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:38:09] PHASE ONE, Encoding
- [20:38:09] Processing: VID_00001 (2 of 4)
- [20:38:09] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00001.meta
- Can't open file: Q:\4K\WORKFILES\VID_00001.AVS.hevc
[20:38:13] - Failed to build structure, aborted
----------------------
[08.12.20] BD Rebuilder v0.61.10
[20:39:11] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:39:12] PHASE ONE, Encoding
- [20:39:12] Processing: VID_00001 (2 of 4)
- [20:39:12] Multiplexing M2TS
- [20:39:17] Processing: VID_00002 (3 of 4)
- [20:39:17] Extracting A/V streams [VID_00002]
- [20:39:21] Reencoding video [VID_00002]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 557 frames
- Bitrate: 1.424 Kbs
- [20:39:21] Reencoding: VID_00002, Pass 1 of 2
- [20:40:12] Reencoding: VID_00002, Pass 2 of 2
- [20:40:49] Video Encode complete
- [20:40:49] PredictAndEncode() 00053 2809
[20:40:56] - Aborted by user request
----------------------
[08.12.20] BD Rebuilder v0.61.10
[20:40:59] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:41:01] PHASE ONE, Encoding
- [20:41:01] Processing: VID_00002 (3 of 4)
- [20:41:01] Processing audio tracks
- [20:41:01] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00002.meta
- Can't open file: Q:\4K\WORKFILES\VID_00002.AVS.hevc
[20:41:05] - Failed to build structure, aborted
----------------------
[08.12.20] BD Rebuilder v0.61.10
[20:41:22] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:41:23] PHASE ONE, Encoding
- [20:41:23] Processing: VID_00002 (3 of 4)
- [20:41:23] Multiplexing M2TS
- [20:41:27] Processing: VID_00003 (4 of 4)
- [20:41:27] Extracting A/V streams [VID_00003]
- [20:41:31] Reencoding video [VID_00003]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 279 frames
- Bitrate: 2.160 Kbs
- [20:41:31] Reencoding: VID_00003, Pass 1 of 2
- [20:42:27] Reencoding: VID_00003, Pass 2 of 2
- [20:43:18] Video Encode complete
- [20:43:18] PredictAndEncode() 00053 2809
[20:43:21] - Aborted by user request
----------------------
[08.12.20] BD Rebuilder v0.61.10
[20:43:30] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:43:31] PHASE ONE, Encoding
- [20:43:31] Processing: VID_00003 (4 of 4)
- [20:43:31] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [20:43:32] Multiplexing M2TS
[20:43:35]PHASE ONE complete
[20:43:35]PHASE TWO - Rebuild Started
- [20:43:35] Rebuilding BD file Structure
[20:43:36] - Encode and Rebuild complete
[20:43:36] Writing BD structure to ISO file
- ImgBurn completed successfully
- SONNTAG_IN_NEW_YORK_1963_1080P folder removed.
- WORKFILES folder removed.
[20:43:47] JOB: SONNTAG_IN_NEW_YORK_1963_1080P finished.

The name of the encoded file is false. When I rename the file manually, BDRB works correct.

With directshow no problems.

[jdobbs]

OK, after 2 days of testing, gradually removing paramters from the stax-string and then adding the parameters from the BDRB string (which I should have done the other way around, because I found it on the second-to-last parameter :mad:) the cause for the flickering is found ...
If the --pic-struct is removed from the command line string, the file plays fine.

But I also noticed, some scenes are WAY to dark on my TV.
A file with intact video (vFormat=8 in the alternate.txt) on the other hand is bright in the same scenes.
I'll do some more testing to find the cause for that...Thanks! Your help is very much appreciated -- I had no way of testing it myself.

[Edit] I went back through requirements of the BD standard information that I have to see when the pic-structure is needed, and I think removing that parameter will be ok.

[jdobbs]

Bug on HEVC/V3 BluRays and x264/LAVF frameserving:

[08.12.20] BD Rebuilder v0.61.10
[20:38:07] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:38:09] PHASE ONE, Encoding
- [20:38:09] Processing: VID_00001 (2 of 4)
- [20:38:09] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00001.meta
- Can't open file: Q:\4K\WORKFILES\VID_00001.AVS.hevc
[20:38:13] - Failed to build structure, aborted
----------------------
[08.12.20] BD Rebuilder v0.61.10
[20:39:11] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:39:12] PHASE ONE, Encoding
- [20:39:12] Processing: VID_00001 (2 of 4)
- [20:39:12] Multiplexing M2TS
- [20:39:17] Processing: VID_00002 (3 of 4)
- [20:39:17] Extracting A/V streams [VID_00002]
- [20:39:21] Reencoding video [VID_00002]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 557 frames
- Bitrate: 1.424 Kbs
- [20:39:21] Reencoding: VID_00002, Pass 1 of 2
- [20:40:12] Reencoding: VID_00002, Pass 2 of 2
- [20:40:49] Video Encode complete
- [20:40:49] PredictAndEncode() 00053 2809
[20:40:56] - Aborted by user request
----------------------
[08.12.20] BD Rebuilder v0.61.10
[20:40:59] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:41:01] PHASE ONE, Encoding
- [20:41:01] Processing: VID_00002 (3 of 4)
- [20:41:01] Processing audio tracks
- [20:41:01] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00002.meta
- Can't open file: Q:\4K\WORKFILES\VID_00002.AVS.hevc
[20:41:05] - Failed to build structure, aborted
----------------------
[08.12.20] BD Rebuilder v0.61.10
[20:41:22] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:41:23] PHASE ONE, Encoding
- [20:41:23] Processing: VID_00002 (3 of 4)
- [20:41:23] Multiplexing M2TS
- [20:41:27] Processing: VID_00003 (4 of 4)
- [20:41:27] Extracting A/V streams [VID_00003]
- [20:41:31] Reencoding video [VID_00003]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 279 frames
- Bitrate: 2.160 Kbs
- [20:41:31] Reencoding: VID_00003, Pass 1 of 2
- [20:42:27] Reencoding: VID_00003, Pass 2 of 2
- [20:43:18] Video Encode complete
- [20:43:18] PredictAndEncode() 00053 2809
[20:43:21] - Aborted by user request
----------------------
[08.12.20] BD Rebuilder v0.61.10
[20:43:30] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:43:31] PHASE ONE, Encoding
- [20:43:31] Processing: VID_00003 (4 of 4)
- [20:43:31] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [20:43:32] Multiplexing M2TS
[20:43:35]PHASE ONE complete
[20:43:35]PHASE TWO - Rebuild Started
- [20:43:35] Rebuilding BD file Structure
[20:43:36] - Encode and Rebuild complete
[20:43:36] Writing BD structure to ISO file
- ImgBurn completed successfully
- SONNTAG_IN_NEW_YORK_1963_1080P folder removed.
- WORKFILES folder removed.
[20:43:47] JOB: SONNTAG_IN_NEW_YORK_1963_1080P finished.

The name of the encoded file is false. When I rename the file manually, BDRB works correct.

With directshow no problems.I don't think UHD_V3_MODE is ready for full backups yet. It's definitely only experimental -- and it should probably only be used experimentally for MOVIE-ONLY backups.

With that said -- I'll do some testing to see why the filename issue is popping up.

[gonca]

OK, after 2 days of testing, gradually removing paramters from the stax-string and then adding the parameters from the BDRB string (which I should have done the other way around, because I found it on the second-to-last parameter :mad:) the cause for the flickering is found ...
If the --pic-struct is removed from the command line string, the file plays fine.

But I also noticed, some scenes are WAY to dark on my TV.
A file with intact video (vFormat=8 in the alternate.txt) on the other hand is bright in the same scenes.
I'll do some more testing to find the cause for that...

Well done

[cartman0208]

Thanks! Your help is very much appreciated -- I had no way of testing it myself.

[Edit] I went back through requirements of the BD standard information that I have to see when the pic-structure is needed, and I think removing that parameter will be ok.

I'll try to get my hands on a HDR10+ capable player, to see if the flicker is there when played from disk...
If not, then it might be enough if the parameter is removed in alternate output only.

What does this parameter do anyway? I read something about shutter timings :confused:

[gonca]

--pic-struct <integer>

Set the picture structure and emits it in the picture timing SEI message. Values in the range 0..12. See D.3.3 of the HEVC spec. for a detailed explanation. Required for HLG (Hybrid Log Gamma) signalling. Not signalled by default.
Not required for HDR10+

[jdobbs]

Not required for HDR10+I went through the spec -- and there are three conditions where it has to be used... none of which really apply to HEVC/UHD.

[gonca]

I was referring to x265 (HEVC)

[cartman0208]

After some more testing I'm pretty sure, that's an encoder thing ...

My TV is showing the HDR10+ logo when playing the intact file, which is bright, also the file encoded with x265 and metadata.

Same brightness on an encoded file, either x265 and nvenc (surprisingly), without HDR10+ metadata, TV then shows a HDR-Logo

A file encoded with nvencc plus metadata also shows the HDR10+ logo, but dark scenes are much too dark, barely visible... where in the same scene on the other files everything was distinguishable...

I tried playing with maxcll values, but that doesn't help either ... plus - I don't want to mess up the original settings

I even tried to set my TV to max backlight and brightness, still too dark

Any ideas what else I could try?

[jdobbs]

After some more testing I'm pretty sure, that's an encoder thing ...

My TV is showing the HDR10+ logo when playing the intact file, which is bright, also the file encoded with x265 and metadata.

Same brightness on an encoded file, either x265 and nvenc (surprisingly), without HDR10+ metadata, TV then shows a HDR-Logo

A file encoded with nvencc plus metadata also shows the HDR10+ logo, but dark scenes are much too dark, barely visible... where in the same scene on the other files everything was distinguishable...

I tried playing with maxcll values, but that doesn't help either ... plus - I don't want to mess up the original settings

I even tried to set my TV to max backlight and brightness, still too dark

Any ideas what else I could try?Does it look the same if you use the "copy" feature in the command line (with NVENCC) instead of the JSON reference?

I wish I could help, but I have no equipment that has the ability to playback HDR10+.

[cartman0208]

Does it look the same if you use the "copy" feature in the command line (with NVENCC) instead of the JSON reference?

I wish I could help, but I have no equipment that has the ability to playback HDR10+.


Yep, "copy" or using the JSON file gives the same negative result...

The file is extracted with
ffmpeg -i "input.m2ts" -c:v copy -vbsf hevc_mp4toannexb -f hevc - | hdr10plus_parser.exe -o metadata.json -

Correct?

Problem might be, that rigaya does not have the equipment either. I think I'll post an issue on his github page.

I suggest to disable the feature by default and only enable it optional... until the root cause is found.

[jdobbs]

Yep, "copy" or using the JSON file gives the same negative result...

The file is extracted with
ffmpeg -i "input.m2ts" -c:v copy -vbsf hevc_mp4toannexb -f hevc - | hdr10plus_parser.exe -o metadata.json -

Correct?

Problem might be, that rigaya does not have the equipment either. I think I'll post an issue on his github page.

I suggest to disable the feature by default and only enable it optional... until the root cause is found.Yes. The JSON file is extracted with that command line -- it actually comes from the hdr10plus_parser.exe documentation (https://github.com/quietvoid/hdr10plus_parser).

Yeah. I'll do that.

The NVENCC documentation does say the "copy" option is "experimental". Interestingly it doesn't say that about --dhdr10-info with the JSON file.

You mentioned that x265 looks ok without the metadata. Have you tried an X265 encode using the JSON file?

[cartman0208]

Yes. The JSON file is extracted with that command line -- it actually comes from the hdr10plus_parser.exe documentation (https://github.com/quietvoid/hdr10plus_parser).

Yeah. I'll do that.

The NVENCC documentation does say the "copy" option is "experimental". Interestingly it doesn't say that about --dhdr10-info with the JSON file.

You mentioned that x265 looks ok without the metadata. Have you tried an X265 encode using the JSON file?

Yes, that works well with BDRB:
"V:\BD_Rebuilder\tools\ffmpeg.exe" -probesize 100MB -i "V:\FULLDISC\BOHEMIAN_RHAPSODY\BDMV\STREAM\00685.m2ts" -an -pix_fmt yuv420p10le -f yuv4mpegpipe -strict -1 - | "V:\BD_Rebuilder\tools\x265-64.exe" - --preset ultrafast --profile main10 --uhd-bd --repeat-headers --vbv-bufsize 45000 --vbv-maxrate 48000 --hdr --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,50)" --dhdr10-info "V:\OUTPUT\WORKFILES\VID_00685.JSON" --fps 23.976 --slow-firstpass --qpfile "V:\OUTPUT\WORKFILES\VID_00685.CHP" --keyint 24 --crf 30 --y4m --stats "V:\OUTPUT\WORKFILES\VID_00685.AVS.hevc.stats" --output "V:\OUTPUT\WORKFILES\VID_00685.AVS.hevc"


That one is unaltered from LASTCMD, brightness is right and also comes without flicker.

[jdobbs]

Yes, that works well with BDRB:


That one is unaltered from LASTCMD, brightness is right and also comes without flicker.Ahh so that makes it clear that the issue is within NVENCC.

Thanks.

I'll do a couple encodes with each encoder and then look at the SEI extension data in the HEVC files to see what differences I can find.

I think if I can get past that one, I'm ready for a new release (a real one rather than test version).

[MrVideo]

This is a capability question. As you know, I've created BDs with 1080p H.264 videos, with menus. Can 1080p HEVC videos be used in the same way to create UHD formatted BDs with menus? The video is not to be upscale recoded to 4K, but left as 1080p.

[jdobbs]

This is a capability question. As you know, I've created BDs with 1080p H.264 videos, with menus. Can 1080p HEVC videos be used in the same way to create UHD formatted BDs with menus? The video is not to be upscale recoded to 4K, but left as 1080p.I'm working on that. Right now my plan is for the menus themselves to stay H.264/1080p, but the videos accessed via the menu would be HEVC at 1080p.

I will include a hidden switch that would allow 720p and SD to be encoded to HEVC as well. That wouldn't be inline with the BD specification -- but I think most if not all UHD players will handle it (mine does). It would make it nice for creating disc backups of things like SD series. It could give the better quality of HEVC at low bitrates when you put a large number of episodes on a single disc.

[MrVideo]

I'm working on that.
I look forward to it. Thanks.

[jdobbs]

I look forward to it. Thanks.Well... a new glitch thrown into the mix. The way I'd tested this previously was by muxing with the old version of TSMUXER and then correcting the stream from within BD-RB. Slow as molasses.

I had assumed that the new UHD capable version of TSMUXER would mux a 1080p source correctly -- easy peasy.

Well, I've done two attempts so far today (both using NVENCC) and TSMUXER has failed to mux them. No error message, no warning, no failure indicator. It just stops.

Honestly this whole thing is getting tiresome. I've had to write code for so many "exceptions" in the helper apps that BD-RB has more code dedicated to bypassing mistakes or implementing workarounds than it has actually doing its job.

I'm trying an encode using X265 now to see if it fares any better.

[MrVideo]

Well, I've done two attempts so far today (both using NVENCC) and TSMUXER has failed to mux them. No error message, no warning, no failure indicator. It just stops.
I don't have the right card to take advantage of NVENCC. I'm waiting for the newest series to be released, for better I/P/B frame support.
I'm trying an encode using X265 now to see if it fares any better.
I'm hoping that the HEVC in the MKV files will pass muster and be usable without recoding. But, my luck normally means... nope.

[jdobbs]

I don't have the right card to take advantage of NVENCC. I'm waiting for the newest series to be released, for better I/P/B frame support.

I'm hoping that the HEVC in the MKV files will pass muster and be usable without recoding. But, my luck normally means... nope.Yeah. It's rare that an MKV doesn't have a huge (240 frame or so) GOP.

[jdobbs]

I don't have the right card to take advantage of NVENCC. I'm waiting for the newest series to be released, for better I/P/B frame support.

I'm hoping that the HEVC in the MKV files will pass muster and be usable without recoding. But, my luck normally means... nope.Ok. I found out that X265 was working fine on the 1080p source. So I did some checking with my HEVC browser. It turns out that the issue was caused by the removal of the "--pic-struct" command line parameter in response to a bug report by cartman0208 related to HDR10+. Without that parameter the new UHD TSMUXER got totally confused and bailed on a 1080p source.

I went back in and made changes so the parameter was removed only for HDR10+ sources. But given the other reported issues with NVENCC and HDR10+, I may have to just remove HDR10+ support completely for NVENCC until it is fixed anyway.

[cartman0208]

I opened an issue at the NVENCC Github page regarding dark scenes.
Should I address the --pic-struct issue also? Could be related...

[jdobbs]

I opened an issue at the NVENCC Github page regarding dark scenes.
Should I address the --pic-struct issue also? Could be related...You might want to mention it. There seems to be a connection -- and it might help put a finger on the problem.

[cartman0208]

You might want to mention it. There seems to be a connection -- and it might help put a finger on the problem.

Did that ... I also added some captures I did with my mobile phone to see the differences

[jdobbs]

Did that ... I also added some captures I did with my mobile phone to see the differencesIn browsing the HEVC streams from X265 and NVENCC -- there is one thing that stands out:

1. In the X265 encoded HEVC file there are two SEI prefixes added:

One SEI that contains the content light level
One SEI that contains the display mastering information

2. In the NVENCC there is only one SEI prefix that contains:

Content light level, followed by display mastering information.

3. In the original (from the authored disc) there are also two SEI prefixes present:

One SEI that contains the content light level
One SEI that contains the display mastering information

4. It also appears that both X265 and the original add the two SEIs to every IDR frame (even if they don't change) -- while NVENCC doesn't (I assume it only changes it at what it thinks are scene changes... but I'm not sure).


Since both the original and X265 streams seem to be working... I suspect that the problem is centered around the attempt to combine both types of information into a single SEI.

I'm nowhere near an expert on how these SEIs should be implemented -- but this information might be helpful to add to your bug report.

[cartman0208]

I'm nowhere near an expert on how these SEIs should be implemented -- but this information might be helpful to add to your bug report.

Well, since I'm even farther away ... feel free to add it :)

[MrVideo]

Yeah. It's rare that an MKV doesn't have a huge (240 frame or so) GOP.
That isn't the fault of MKV, but with the person who set the encoding options.

For one show, a quick glance showed 250 frames from one IDR to the next. Another show wasn't as bad, but still normally more than 50.

To be UHD disc compliant, what should the maximum be?

[jdobbs]

That isn't the fault of MKV, but with the person who set the encoding options.

For one show, a quick glance showed 250 frames from one IDR to the next. Another show wasn't as bad, but still normally more than 50.

To be UHD disc compliant, what should the maximum be?From the UHD Part 3, v3.1 Whitepaper:

[cartman0208]

jdobbs: do you have plans to change the "browse for folder" interfaces (behind the "Browse" buttons in the main interface) so they look like the one for "import file" ?

I'd love to sort the folders by age when browsing :)

[jdobbs]

jdobbs: do you have plans to change the "browse for folder" interfaces (behind the "Browse" buttons in the main interface) so they look like the one for "import file" ?

I'd love to sort the folders by age when browsing :)No plans right now. Browsing for a file and browsing for a folder involve two different system calls in Windows. But I'll look at it and see if it's possible.

[jdobbs]

I opened an issue at the NVENCC Github page regarding dark scenes.
Should I address the --pic-struct issue also? Could be related...I was hoping this might be a quick fix, especially after I noted the differences... but it doesn't look like it is getting any attention at all.

I could probably write code to make this fix myself, but I'd hesitated since the last time I did that a fix was made a couple days later. Another reason for hesitating is that it will add time (since I'd have to scan and rewrite the entire HEVC file after the encode is done).

[cartman0208]

I was hoping this might be a quick fix, especially after I noted the differences... but it doesn't look like it is getting any attention at all.

I could probably write code to make this fix myself, but I'd hesitated since the last time I did that a fix was made a couple days later. Another reason for hesitating is that it will add time (since I'd have to scan and rewrite the entire HEVC file after the encode is done).

I would wait ... several days with no contribution or blog activity ... maybe rigaya is on vacation ?

[jdobbs]

I have updated the first post of this thread with a link to the latest version (v0.61.12) of BD Rebuilder. Cumulative changes for this release (since the last public release):- This list includes changes made since the
last public release (v0.61.05).
- Added support for NVIDIA NVENC encoding.
- Corrected an error that could cause BD-RB
to exit in failure when attempting a size-
correcting second pass in CRF mode while
doing a UHD backup.
- Added code that will update the HDR flags
in the MPLS file for sources in which HDR
was not established until after reencoding
on full backups.
- Fixed an error in which MPEG2 sources may
not make video adjustments detected during
import when reencoding. This could result
in stretched or compressed images.
- Created a workaround for a problem with
converting PAL to NTSC flags during import
which could confuse TSMUXER's recognition
of video resolution.
- Added code to adapt to UHD sources that are
not sized to either 3840(h) or 2160(v).
- Corrected an issue in which video sources
that are an odd size during import might
use the wrong resizing when HEVC encoding
is enabled.
- Fixed a bug in which large audio offsets
detected during import were not being
interpreted correctly.
- Fixed a bug that could cause undersizing
when an AC3 stream is kept intact because
the original is smaller than the selected
reencoder bitrate. This typically only
happens on DVD imports.
- Fixed an error that could result in wrong
aspect ratio on imported sources that are
being resized.
- Corrected an issue in which some command
line settings were not being set when a
non-UHD source is output as V3.
- Added a routine to ensure formatting of
CRF values consistent.
- Updated CQM prediction routines.
- Fixed an issue that can cause the CQM/CRF
sample file to have a zero length when
used in other-than-US regions.
- Modified NVENCC options to eliminate vbrhq
from the command line, as it is targeted
to be deprecated. Replaced by "vbr" and
manually enabling "--multipass 2pass-full"
(the newer equivalent of vbrhq).
- Rewrote the "Bitstream Exception" TSMUXER
error workaround routine so it now uses
a more efficient method -- and better
adjusts audio sync. It also now adjusts
for Dolby Vision exception errors.
- Fixed an issue in which BT709 sources were
not being encoded with proper settings.
- Increased the accepted value of the THREADS
hidden option from 16 to 128. Note: While
128 is accepted for x264 -- realistically
you should never set it that high.
- Added support for HDR10+ in X265 encoding
and experimental (needs testing) support
for NVENCC. A JSON file is created con-
currently with video extraction. HDR10+
streams are now identified in the streams
list by a "+" next to "HEVC". Note that "*"
indicates Dolby Vision. "*+"=both. To enable
experimental support in NVENCC, as the
hidden value NVENC_ENABLE_10PLUS=1 to your
BDREBUILDER.INI file.
- Corrected an error that would result in
only 48 frames being encoded during CRF
prediction when using X265.
- Changed the ALTERNATE settings so creating
a preset that outputs HEVC to MP4 is now
allowed.
- Fixed an issue that could result in an
error "ExtractAudioSubs() 00058 1605".
- Fixed a problem that could cause multipart
sources to fail during rebuild when
outputting to ALTERNATE choices.
- Implemented a method by which a different
background image could be used for multpage
menus. Menu pages 2-x can be changed by
adding additional file(s) into the same
folder as the initial background image.
Example: If the background image is called
"BACKGROUND.JPG". You can us another
image for page 2 by creating an image called
"BACKGROUND_2.JPG" (page 3=BACKGROUND_3.JPG)
etc.
- Updated the included version of MP4BOX to
support HEVC.
- Updated the included versions of X265 to a
newer (v3.2.1) release.
- Other minor corrections and cosmetic fixes.

[meadrocks]

Ran Howls Moving Castle w/ the new version, same problem. I'll try with a mp4 container.


$ mediainfo HOWLS_MOVING_CASTLE.mkv
General
Unique ID : 221294904985475506127951980034512522439 (0xA67BD931150DAFE18584E1C6A43E0CC7)
Complete name : HOWLS_MOVING_CASTLE.mkv
Format : Matroska
Format version : Version 2
File size : 2.44 GiB
Duration : 3 h 53 min
Overall bit rate : 1 495 kb/s
Encoded date : UTC 2020-08-21 06:17:34
Writing application : mkvmerge v9.7.1 ('Pandemonium') 32bit
Writing library : libebml v1.3.4 + libmatroska v1.4.5

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 59 min
Bit rate : 2 611 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (23976/1000) FPS
Original frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.053
Stream size : 2.18 GiB (89%)
Writing library : x265 3.2.1+3-b4b2ecac21f6:[Windows][GCC 9.2.0][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=3 / numa-pools=8 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 /
input-res=1920x1080 / interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud /
no-hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=23 / keyint=240 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 /
rc-lookahead=20 / lookahead-slices=6 / scenecut=40 / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 /
tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra /
strong-intra-smoothing / max-merge=3 / limit-refs=1 / no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / no-hme / weightp / no-weightb /
no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock / rd=3 / selective-sao=4 / early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless /
b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=23.7 / qcomp=0.60 /
qpstep=4 / stats-write=0 / stats-read=0 / ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 /
no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=0 / overscan=0 / videoformat=5 / range=0 / colorprim=2 / transfer=2 / colormatrix=2 / chromaloc=0 /
display-window=0 / cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps /
no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / no-hdr / no-hdr-opt / no-dhdr10-opt /
no-idr-recovery-sei / analysis-reuse-level=5 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao /
ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt /
no-field / qp-adaptation-range=1.00
Default : Yes
Forced : No

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : A_AAC-2
Duration : 1 h 59 min
Bit rate : 277 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 237 MiB (9%)
Language : English
Default : Yes
Forced : No

Text #1
ID : 3
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 3 h 49 min
Bit rate : 10.8 kb/s
Count of elements : 2845
Stream size : 17.7 MiB (1%)
Language : English
Default : No
Forced : No

Text #2
ID : 4
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 3 h 53 min
Bit rate : 7 807 b/s
Count of elements : 2062
Stream size : 13.0 MiB (1%)
Language : English
Default : No
Forced : No

Menu
00:00:00.000 : en:00:00:00.000
00:01:09.069 : en:00:01:09.069
00:05:03.302 : en:00:05:03.302
00:12:27.037 : en:00:12:27.037
00:18:27.397 : en:00:18:27.397
00:23:21.691 : en:00:23:21.691
00:28:56.025 : en:00:28:56.025
00:33:18.287 : en:00:33:18.287
00:40:14.703 : en:00:40:14.703
00:45:35.023 : en:00:45:35.023
00:49:20.248 : en:00:49:20.248
00:55:30.618 : en:00:55:30.618
00:58:36.804 : en:00:58:36.804
01:04:58.185 : en:01:04:58.185
01:10:58.545 : en:01:10:58.545
01:15:28.815 : en:01:15:28.815
01:20:30.116 : en:01:20:30.116
01:25:26.412 : en:01:25:26.412
01:32:35.841 : en:01:32:35.841
01:38:39.204 : en:01:38:39.204
01:44:26.551 : en:01:44:26.551
01:48:27.792 : en:01:48:27.792
01:52:24.028 : en:01:52:24.028
01:54:43.209 : en:01:54:43.209
01:59:27.201 : en:01:59:27.201

[MrVideo]

I have updated the first post of this thread with a link to the latest version (v0.61.12) of BD Rebuilder. Cumulative changes for this release (since the last public release):
- Implemented a method by which a different
background image could be used for multpage
menus. Menu pages 2-x can be changed by
adding additional file(s) into the same
folder as the initial background image.
Example: If the background image is called
"BACKGROUND.JPG". You can us another
image for page 2 by creating an image called
"BACKGROUND_2.JPG" (page 3=BACKGROUND_3.JPG)
etc.
Somehow I missed that new feature. I like it and will be using it. Thanks.

[jdobbs]

@meadrocks

I notice that the source is 1920x1080. Was it imported into BD-RB, or was it from a BD disc?

[meadrocks]

@meadrocks

I notice that the source is 1920x1080. Was it imported into BD-RB, or was it from a BD disc?

The source is a BD disk.

When making a mp4 I get an "ERROR in attempt to mux (MP4BOX)"

Trying Watchmen DC disk now.

[jdobbs]

The source is a BD disk.

When making a mp4 I get an "ERROR in attempt to mux (MP4BOX)"

Trying Watchmen DC disk now.Are you sure you are using the new version -- including the helper files that are included with the new version?

I didn't make any changes to affect the subtitles -- but I did multiple tests with MP4BOX without error.

By "Watchmen DC" are you referring to the Directors Cut (DC)?

[jdobbs]

Updated the first post of this thread with a new version (v0.61.13) of BD Rebuilder. Changes for this release:

This is nothing more than a recompile of v0.61.12. Apparently some antivirus software was (incorrectly) flagging BD-RB.EXE. Changing the version number seems to have "fixed" it. Just another antivirus false positive. Go figure.

I've also updated the v0.61.12 zip file so it downloads v0.61.13. The last thing I need is people driving me crazy with reports of false positives from antivirus mistakes.

[meadrocks]

Are you sure you are using the new version -- including the helper files that are included with the new version?

I didn't make any changes to affect the subtitles -- but I did multiple tests with MP4BOX without error.

By "Watchmen DC" are you referring to the Directors Cut (DC)?

Yes Watchmen Dir Cut. its 186 minutes long. Both of these BD disks (Howls Moving Castle & Watchmen Dir Cut) are multi part.

[meadrocks]

Yes Watchmen Dir Cut. its 186 minutes long. Both of these BD disks (Howls Moving Castle & Watchmen Dir Cut) are multi part.

Heres the Input file.


[Status]
LABEL=WATCHMEN
VERSION=v0.61.12
SOURCE_SIZE=35145842688
SOURCE_VIDEO_SIZE=35145842688
TARGET_SIZE=4686086144
REDUCTION=.133332587458487
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=0
SUBS_TO_KEEP=all
BACKUP_MODE=1
MOVIEONLY_TYPE=41
USE_LAVF=0
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
UHD_V3_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=25
REBUILD_COMPLETE=0
[00500]
AUDIO=100
PGS=100010
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=268696
NSIZE=0
FLINK=-1
MLINK=0
[00501]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=15032236
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00502]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=57589438
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00503]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=78818887
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00504]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=378957342
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00505]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=69512008
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00506]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=574395251
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00507]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=65900995
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00508]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=134614287
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00509]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=45525147
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00510]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=94264817
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00511]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=65805968
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00512]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=597088602
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00513]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=56924251
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00514]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=802112735
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00515]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=93446440
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00516]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=473949605
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00517]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=69221194
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00518]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=334745366
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00519]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=69143370
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00520]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=87712073
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00521]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=64320767
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00522]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=366298316
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00523]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=90352339
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00524]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=86016
AUDIO=100
NSIZE=0
FLINK=0
MLINK=0



Heres the output file.


----------------------
[08/21/20] BD Rebuilder v0.61.12
[08:05:09] Source: WATCHMEN_00100
- Input BD size: 32.73 GB
- Approximate total content: [03:06:28.385]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MP4 Container, HEVC 1920x1080, Auto-AAC
- Quality: High Quality (Default)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[08:05:09] PHASE ONE, Encoding
- [08:05:09] Processing: VID_00500 (1 of 25)
- [08:05:09] Extracting A/V streams [VID_00500]
[08:05:40]PHASE ONE aborted by user request
----------------------
[08/21/20] BD Rebuilder v0.61.12
[08:06:43] Source: WATCHMEN_00100
- Input BD size: 32.73 GB
- Approximate total content: [03:06:28.385]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MP4 Container, HEVC 1920x1080, Auto-AAC
- Quality: High Quality (Default)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[08:06:46] PHASE ONE, Encoding
- [08:06:46] Processing: VID_00500 (1 of 25)
- [08:06:46] Extracting A/V streams [VID_00500]
- [08:11:41] Reencoding video [VID_00500]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23.976fps, 96 frames
- [08:11:41] Reencoding: VID_00500, Pass 1 of 1
- Analyzing 43.95 24.40 1.00 [1.00]
- [08:11:51] Video Encode complete
- [08:11:51] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AAC...

snip

- [14:51:53] Processing: VID_00524 (25 of 25)
- [14:51:53] Extracting A/V streams [VID_00524]
- [14:51:57] Reencoding video [VID_00524]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23.976fps, 29 frames
- [14:51:57] Reencoding: VID_00524, Pass 1 of 1
- Analyzing 42.60 25.00 14.60 1.00 [1.00]
- [14:52:05] Video Encode complete
[14:52:05]PHASE ONE complete
[14:52:05]PHASE TWO - Rebuild Started
- [14:52:05] Building ALTERNATE OUTPUT Structure
- ERROR in attempt to mux (MP4BOX)
[14:54:35] - Failed to REBUILD

[Ch3vr0n]

Just a quick question. I don't see a mentioning of updated FRIM. Is it still the "old" one or the new one that supposedly fixes pixellation issues on 3D for software players?

[jdobbs]

Just a quick question. I don't see a mentioning of updated FRIM. Is it still the "old" one or the new one that supposedly fixes pixellation issues on 3D for software players?Sorry, but I haven't updated it yet. I haven't had time to test it. By testing I mean making sure that it still works the same and doesn't cause other issues. I can't test the pixellation issue since it doesn't happen to me.

[Ch3vr0n]

Yeah no worries, I'll see it updated when it gets updated. Was just a question

Sent from my Pixel 3 XL using Tapatalk

[jdobbs]

Weird. Yesterday someone indicated that their antivirus software was give a hit on BD-RB. This wasn't the first time I'd gotten a false negative in a new release. I ran a scan with AVG (the AV software I use) and it also showed it. So I recompiled and what I assume was a false negative went away. I packed the new compile into a ZIP file and posted it for download. I even downloaded it and ran the test again. No problem.

Now today that user told me he got it again, and sure enough, AVG showed it too -- and it also found something else in the FRIMSource.dll. Huh? There'd been a virus database update earlier. I scanned my entire system -- nothing found. But I've blocked the downloads until I do some more in-depth checking.

A long time ago I put special code in BD-RB that performs a checksum at startup and it exits with a warning if the EXE has been modified. It also is protected via EXE compression (from reverse engineering) so it would be very hard for malware to "attach" itself to it. So I have to assume another false negative, FRIMSource.dll hasn't changed in years. But it is getting annoying.

The two hits were with AVG and AVAST -- can someone scan the new version of BD-RB with another A/V checker and see if it gets an all-clear?

[musiclover]

All files in the BD_Rebuilder v0.61.13 folder are getting the all-clear from Malwarebytes

[MajorEvent]

All clear with Malwarebytes and Windows Defender both .zip and extracted with BD-RBV06112

[jdobbs]

Thanks. Yeah, the odds are high that it's another false positive. It's happened before. Sometimes A/V software can be just as bad as the things they are designed to protect you against.

Anyone else?

[prologic]

can not download from the main site, re-direction .. not working here .

[raul124]

first page redirected me to this
https://jammernhilftnichts.de/jdobbs/BD-RBV06113.zip

[jdobbs]

Sorry, I blocked it until it could be tested by a few different packages. Try this link (https://jammernhilftnichts.de/jdobbs/BD-RBV06113-keep.zip).

Thanks,

[Ch3vr0n]

Running avast premier security here, BDRB opens fine but i manually scanned the archive. The culprit for my manual scan seems to be FRIMSource.dll on the initial .13 archive.

[jdobbs]

Running avast premier security here, BDRB opens fine but i manually scanned the archive. The culprit for my manual scan seems to be FRIMSource.dll on the initial .13 archive.Yeah, I got that too with AVG -- but that file is the same one (unchanged) that has been there for years. I compared it to the older archives and it is still identical. I'm guessing that the problem is that somewhere in that file is a string of bytes that matches something else they are trying to catch.

Not sure which is worse, the viruses or the software that is designed to deal with them.

[LowDead]

Bitdefender have nothing to report with BD_Rebuilder v0.61.13

//LD

[jdobbs]

Thanks all. I've submitted a request to whitelist BDRB.EXE to both AVAST and AVG.

[jdobbs]

I would wait ... several days with no contribution or blog activity ... maybe rigaya is on vacation ?Rigaya has posted a link to a version that should (likely) fix the HDR10+ issues. Have you had a chance to try it?

[cartman0208]

Rigaya has posted a link to a version that should (likely) fix the HDR10+ issues. Have you had a chance to try it?

I did one encode, but it's still too dark.
I want to do more tests, but I will be away from my PC for several weeks.
Did you have a chance to check SEI information?

[ggtop]

Hi jdobbs,

thank you for the new version. Just downloaded it and wanted to perform a first encode when I immediately received an error:ExtractAudioSubs() 00053 1604
After some research I found that I copied the wrong paths for DGIndexNV and DGDecNV to my INI file.
Maybe you could implement a basic "FILE EXISTS" check for entries under [Paths] in BDREBUILDER.INI?

ggtop

[Lathe]

It's like cars with a lot of power and crappy tires ... can't get the power on the street ;)
One hint I can give: thermal conductive paste, not too little, not too much...
If the heat from the CPU cant get to the heat spreader you can have the best cooling solution ever but it won't cool.

I, personally, use AIO watercoolers ... easy setup, lots of space left in the case, way cooler than all the aircoolers I had and not even that expensive...

Thanks!

[Lathe]

@Lathe
The coolers supplied by Intel and AMD with their CPUs are not the greatest, to be kind.
Like cartman0208 said, get an AIO watercooler
I like Corsair, and don't get one with a small radiator

Thanks Bro! Yeah, I read a lot where people said that the stock cooler that comes with it isn't that great (although it LOOKS pretty good sized) Just seems weird that you can't just simply utilize the entire CPU without it overheating in like 1 minute.

What I'm doing now since I'm not re-encoding a lot of Blu-rays at the moment, I just defeat about 3/4 of the 'cores/threads' so that I am only using 3 out of 12 and at that 25% I can BARELY keep the heat just below redlining. Doesn't seem like it should be that way.

I guess down the road I will hafta get one of the water coolers you guys are talking about. Appreciate the input!

[Lathe]

You still got to get the paste correct.

Yeah, the guy honestly SEEMS like he is pretty sharp about this, but he could always take a look at it to see if he can narrow down exactly why it is getting so hot when more fully utilized. I guess I can wait until I get the water cooler so that he can install it at the same time I suppose...

[Lathe]

Check out this IC Graphite Pad, supposed to work just as good as the best thermal pastes, but with no drying out or installation errors:
https://youtu.be/YpphKzmDiJM
https://www.amazon.com/dp/B07CKVW18G

Good to know, I will mention it to the guy if I ever get around to taking it in, thanks!

[Lathe]

Yes. That would be the problem. If you create the source manually (using TSMUXER) then BD-RB has no way of knowing the AR is noncompliant and noting it for adjustment. TSMUXER will set the CLPI's flags to the nearest compliant resolution. Since there is no PSEUDO.INI file, BD-RB thinks it's a standard BD and assumes the CLPI is correct.

Yeah, that is what I figured. Thanks JD!

[Lathe]

Especially useful when the included text is really long. Long quotes are very annoying.

Sounds like someone is suffering from some serious Long Quote Envy to me...

[Lathe]

Um, the latest version on page one seems to direct to a site in Germany with really slow speeds. Is that where it usually goes...?

https://jammernhilftnichts.de/jdobbs/BD-RBV06113.zip

[Mike-uk]

Um, the latest version on page one seems to direct to a site in Germany with really slow speeds. Is that where it usually goes...?

https://jammernhilftnichts.de/jdobbs/BD-RBV06113.zip

whining doesn't help, lol :P

[cartman0208]

Um, the latest version on page one seems to direct to a site in Germany with really slow speeds. Is that where it usually goes...?

https://jammernhilftnichts.de/jdobbs/BD-RBV06113.zip

How slow?
Can't do much about it but reboot the Server.
Usually I get at least 100mbit/s

[jdobbs]

Um, the latest version on page one seems to direct to a site in Germany with really slow speeds. Is that where it usually goes...?

https://jammernhilftnichts.de/jdobbs/BD-RBV06113.zipYes. That's where it usually goes. I can upload it to my server too... but you may be stuck downloading at 5Mbs is you use that one.

[meadrocks]

Running this BD as a .mp4 container fails, Input & Output files are in a previous post. Running this as a .mkv completes successfully, but it still has the wrong length. Notice that the Audio & Video sections report the Time Duration as 3h 6min, that is the correct length of the movie. The subtitles are an incorrect Duration causing the General->Duration time to be incorrect.

I have the mediainfo on the BD source, but its too long to add as CODE.
How can I get the data in here?


$ mediainfo WATCHMEN_DC.mkv
General
Unique ID : 190735447712007644297711488837758782096 (0x8F7E4F9F098A76D0BCE8F305B0C88A90)
Complete name : WATCHMEN_DC.mkv
Format : Matroska
Format version : Version 2
File size : 5.25 GiB
Duration : 6 h 12 min
Overall bit rate : 2 015 kb/s
Encoded date : UTC 2020-08-25 03:48:42
Writing application : mkvmerge v9.7.1 ('Pandemonium') 32bit
Writing library : libebml v1.3.4 + libmatroska v1.4.5

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 3 h 6 min
Bit rate : 3 731 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (23976/1000) FPS
Original frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.075
Stream size : 4.86 GiB (93%)
Writing library : x265 3.2.1+3-b4b2ecac21f6:[Windows][GCC 9.2.0][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=3 / numa-pools=8 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2
/ input-csp=1 / input-res=1920x1080 / interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance
/ no-repeat-headers / annexb / no-aud / no-hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=23 / keyint=240 / gop-lookahead=0
/ bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=20 / lookahead-slices=6 / scenecut=40 / radl=0 / no-splice / no-intra-refresh
/ ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00
/ no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=3 / limit-refs=1 / no-limit-modes
/ me=1 / subme=2 / merange=57 / temporal-mvp / no-hme / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock
/ rd=3 / selective-sao=4 / early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00
/ psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=1.0 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0
/ ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69
/ qpmin=0 / no-const-vbv / sar=0 / overscan=0 / videoformat=5 / range=0 / colorprim=2 / transfer=2 / colormatrix=2 / chromaloc=0
/ display-window=0 / cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps
/ no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / no-hdr / no-hdr-opt / no-dhdr10-opt
/ no-idr-recovery-sei / analysis-reuse-level=5 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao
/ ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq
/ no-svt / no-field / qp-adaptation-range=1.00
Default : Yes
Forced : No

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : A_AAC-2
Duration : 3 h 6 min
Bit rate : 265 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 351 MiB (7%)
Language : English
Default : Yes
Forced : No

Text #1
ID : 3
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 6 h 12 min
Bit rate : 6 485 b/s
Count of elements : 4072
Stream size : 17.3 MiB (0%)
Language : English
Default : No
Forced : No

Text #2
ID : 4
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 6 h 12 min
Bit rate : 8 679 b/s
Count of elements : 4758
Stream size : 23.1 MiB (0%)
Language : English
Default : No
Forced : No

Menu
00:00:00.000 : en:00:00:00.000
00:05:41.674 : en:00:05:41.674
00:11:16.133 : en:00:11:16.133
00:16:05.339 : en:00:16:05.339
00:19:05.561 : en:00:19:05.561
00:23:48.802 : en:00:23:48.802
00:26:39.514 : en:00:26:39.514
00:31:37.979 : en:00:31:37.979
00:36:26.892 : en:00:36:26.892
00:41:01.417 : en:00:41:01.417
00:44:58.654 : en:00:44:58.654
00:47:27.344 : en:00:47:27.344
00:51:40.597 : en:00:51:40.597
00:56:10.241 : en:00:56:10.241
00:58:17.910 : en:00:58:17.910
01:00:58.946 : en:01:00:58.946
01:04:13.265 : en:01:04:13.265
01:11:22.778 : en:01:11:22.778
01:13:14.264 : en:01:13:14.264
01:16:45.892 : en:01:16:45.892
01:18:47.264 : en:01:18:47.264
01:21:47.527 : en:01:21:47.527
01:26:52.081 : en:01:26:52.081
01:31:17.972 : en:01:31:17.972
01:37:09.490 : en:01:37:09.490
01:41:10.355 : en:01:41:10.355
01:46:57.410 : en:01:46:57.410
01:53:50.698 : en:01:53:50.698
01:57:18.739 : en:01:57:18.739
02:03:03.167 : en:02:03:03.167
02:06:07.309 : en:02:06:07.309
02:10:23.774 : en:02:10:23.774
02:15:18.777 : en:02:15:18.777
02:19:31.988 : en:02:19:31.988
02:22:13.524 : en:02:22:13.524
02:27:11.030 : en:02:27:11.030
02:33:54.933 : en:02:33:54.933
02:36:37.679 : en:02:36:37.679
02:41:03.069 : en:02:41:03.069
02:44:25.897 : en:02:44:25.897
02:47:31.833 : en:02:47:31.833
02:51:02.293 : en:02:51:02.293
02:55:06.996 : en:02:55:06.996
02:59:45.983 : en:02:59:45.983
03:06:27.843 : en:03:06:27.843



Input file...


[Status]
LABEL=WATCHMEN
VERSION=v0.61.12
SOURCE_SIZE=35145842688
SOURCE_VIDEO_SIZE=35145842688
TARGET_SIZE=4686086144
REDUCTION=.133332587458487
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=0
SUBS_TO_KEEP=eng;
BACKUP_MODE=1
MOVIEONLY_TYPE=33
USE_LAVF=0
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
UHD_V3_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=25
REBUILD_COMPLETE=1
[00500]
AUDIO=100
PGS=100010
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=268696
NSIZE=0
FLINK=-1
MLINK=0
[00501]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=15032236
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00502]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=57589438
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00503]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=78818887
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00504]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=378957342
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00505]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=69512008
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00506]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=574395251
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00507]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=65900995
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00508]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=134614287
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00509]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=45525147
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00510]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=94264817
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00511]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=65805968
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00512]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=597088602
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00513]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=56924251
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00514]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=802112735
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00515]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=93446440
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00516]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=473949605
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00517]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=69221194
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00518]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=334745366
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00519]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=69143370
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00520]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=87712073
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00521]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=64320767
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00522]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=366298316
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00523]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=90352339
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00524]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=86016
AUDIO=100
NSIZE=0
FLINK=0
MLINK=0



Output File...


[08/24/20] BD Rebuilder v0.61.12
[13:54:12] Source: WATCHMEN_00100
- Input BD size: 32.73 GB
- Approximate total content: [03:06:28.385]
- Windows Version: 6.2 [9200]
- 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
[13:54:12] PHASE ONE, Encoding
- [13:54:12] Processing: VID_00500 (1 of 25)
- [13:54:12] Extracting A/V streams [VID_00500]
- [13:59:32] Reencoding video [VID_00500]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23.976fps, 96 frames
- [13:59:32] Reencoding: VID_00500, Pass 1 of 1
- Analyzing 43.45 23.75 1.00 [1.00]
- [13:59:44] Video Encode complete
- [13:59:44] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AAC...

<snip>

- [20:39:34] Processing: VID_00523 (24 of 25)
- [20:39:34] Extracting A/V streams [VID_00523]
- [20:39:47] Reencoding video [VID_00523]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23.976fps, 10,006 frames
- [20:39:47] Reencoding: VID_00523, Pass 1 of 1
- Analyzing 26.35 21.85 22.20 [22.20]
- [20:45:59] Video Encode complete
- [20:45:59] Processing: VID_00524 (25 of 25)
- [20:45:59] Extracting A/V streams [VID_00524]
- [20:46:03] Reencoding video [VID_00524]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23.976fps, 29 frames
- [20:46:03] Reencoding: VID_00524, Pass 1 of 1
- Analyzing 42.15 24.35 11.45 1.00 [1.00]
- [20:46:10] Video Encode complete
[20:46:10]PHASE ONE complete
[20:46:10]PHASE TWO - Rebuild Started
- [20:46:11] Building ALTERNATE OUTPUT Structure
[20:51:32] - Encode and Rebuild complete
[20:51:32] JOB: WATCHMEN finished.

[Ch3vr0n]

This fails making a mp4

What exactly is "this" supposed to mean? What BDRB version? Where's the conversion log?...

[meadrocks]

What exactly is "this" supposed to mean? What BDRB version? Where's the conversion log?...

I updated the previous post with the input & output files.

[jdobbs]

@meadrocks

Have you tried multipart sources other than those two? I don't have either of those discs. But I just did another test of a multipart source output to MKV and it worked fine. It was AVC... but I'll try redoing it in HEVC to see if it changes (I can't imagine why it would since that shouldn't affect a PGS stream).

[Edit] Completed the HEVC encode -- no issue with the subtitles. I'll try MP4 output next.

[Edit] Yes, the MP4 worked as well.

[ggtop]

IIRC I have an European version of Watchmen DC. Let me find it and do some testing.

[Edit] Unfortunately it's not DC. It's the 165 min version and it's not multi part.

ggtop

[LowDead]

Bitdefender have nothing to report with BD_Rebuilder v0.61.13

//LD

I may have jumped the gun on this one...

When doing an ordinary bluray encode my Bitdefender acted up on bdrb.exe halfway into the encode claiming it to be ransomware and that it had infected two files. One nvidia file(don't remember wich one) and lastcmd.txt. Bitdefender autorestored them and I had to exclude bdrb.exe to be able to continue.

//LD

[jdobbs]

I may have jumped the gun on this one...

When doing an ordinary bluray encode my Bitdefender acted up on bdrb.exe halfway into the encode claiming it to be ransomware and that it had infected two files. One nvidia file(don't remember wich one) and lastcmd.txt. Bitdefender autorestored them and I had to exclude bdrb.exe to be able to continue.

//LDI submitted the file to AVAST! and they tested it, verified it, and excluded it from their list. I also submitted it to AVG -- but they haven't responded yet.

BD-RB definitely modifies LASTCMD.TXT -- it always updates it with the last encode command (for debugging). It's silly to think that a text file could be "infected", though. It makes no changes to any NVIDIA files, not sure what that is about.

[LowDead]

I submitted the file to AVAST! and they tested it, verified it, and excluded it from their list. I also submitted it to AVG -- but they haven't responded yet.

BD-RB definitely modifies LASTCMD.TXT -- it always updates it with the last encode command (for debugging). It's silly to think that a text file could be "infected", though. It makes no changes to any NVIDIA files, not sure what that is about.

yes, super strange... I will see if Bitdefender can verify also.

//LD

[Mike-uk]

malware bytes flagged up version 09( i know were on 13 but i was having a problem creating a bd struture from a mkv import so wanted to see if and earlier version worked) as a threat

Malwarebytes

-Log Details-
Protection Event Date: 31/08/2020
Protection Event Time: 10:32
Log File: e7d454dc-eb6c-11ea-b3eb-0c9d9279b63b.json

-Software Information-
Version: 4.2.0.82
Components Version: 1.0.1025
Update Package Version: 1.0.29253
Licence: Trial

-System Information-
OS: Windows 10 (Build 19041.450)
CPU: x64
File System: NTFS
User: System

-Blocked Malware Details-
File: 1
MachineLearning/Anomalous.100%, C:\Users\xxxx\Desktop\BD_Rebuilder09\BDRB.exe, Quarantined, 0, 392687, 1.0.29253, , shuriken, , 447C0F9C095C02880FE9B16AB91499AD, 4865F0F4278C7D6775CA460B67EB320810F00AA07583541D5B8B2859AD8EB3C4


(end)

[jdobbs]

This is getting crazy. It seems that A/V software is becoming almost as intrusive and harming as the viruses they are meant to protect us from.

[Mike-uk]

and version 10 its flagging up the same, but 13 seems ok so far

[Ch3vr0n]

WOOHOO Just watched the Geforce special event. RTX 3090 CONFIRMED, goodbye GTX 1080, hello 3090. BDRB nvenc is gonna FLYYYYYYYYYYYYY on that thing right out along to say hi to tesla's speedster in space :D

[SquallMX]

Output video created by BD-RB with nvEnc gets reported as 3840x2176 by TsMuxerGUI and eac3to. Is that right?

command line: "D:\Archivos de Programa\EAC32AC3\eac3to.exe" "D:\Temp\Sherlock Holmes UHD\BDMV\STREAM\00004.m2ts" 4: "D:\Temp\Sherlock Holmes UHD\BDMV\STREAM\00004.m2ts_4eng.ac3" 5: "D:\Temp\Sherlock Holmes UHD\BDMV\STREAM\00004.m2ts_5spa.ac3" 6: "D:\Temp\Sherlock Holmes UHD\BDMV\STREAM\00004.m2ts_6spa.ac3" 7: "D:\Temp\Sherlock Holmes UHD\BDMV\STREAM\00004.m2ts_7jap.ac3" -progressnumbers -log="D:\Archivos de Programa\EAC32AC3\UsEac3To.log"
------------------------------------------------------------------------------
M2TS, 1 video track, 5 audio tracks, 29 subtitle tracks, 2:08:30, 23.978i
1: Chapters, 30 chapters
2: h265/HEVC, 3840x2176 48i /1.001 (30:17), 10 bits
3: DTS Master Audio, English, 5.1 channels, 16 bits, 48kHz
(core: DTS, 5.1 channels, 1509kbps, 48kHz)
4: AC3, English, 5.1 channels, 448kbps, 48kHz, dialnorm: -27dB, 4671ms
5: AC3, Spanish, 5.1 channels, 448kbps, 48kHz, dialnorm: -27dB, 4671ms
6: AC3, Spanish, 5.1 channels, 448kbps, 48kHz, dialnorm: -27dB, 4671ms
7: AC3, Japanese, 5.1 channels, 448kbps, 48kHz, dialnorm: -27dB, 4671ms
...

[MrVideo]

WOOHOO Just watched the Geforce special event. RTX 3090 CONFIRMED, goodbye GTX 1080, hello 3090. BDRB nvenc is gonna FLYYYYYYYYYYYYY on that thing right out along to say hi to tesla's speedster in space :D
At $1.5k and 3 slots, it is outta my range. The 3070 is more in my price range and slot usage and should be just fine with BDRB as well.

But, they do not give OS requirements. If the driver does not work under Win7-64, then I will have to look at something that does.

[LowDead]

Output video created by BD-RB with nvEnc gets reported as 3840x2176 by TsMuxerGUI and eac3to. Is that right?

Short answer: Yes, it's a hardware thing... Nothing to worry about though.

Longer technical answer: nVidia Developer Forums (https://forums.developer.nvidia.com/t/nvenc-hevc-encoding-of-3840x2160-results-in-coded-size-of-3840x2176/60107)

//LD

[jdobbs]

WOOHOO Just watched the Geforce special event. RTX 3090 CONFIRMED, goodbye GTX 1080, hello 3090. BDRB nvenc is gonna FLYYYYYYYYYYYYY on that thing right out along to say hi to tesla's speedster in space :DAt $1.5k...
:eek:

I want to be just like Ch3vr0n when I grow up!

[videoh]

Gonna have to get a PCIe 4 motherboard to take full advantage of it for CUDA filtering.

[MrVideo]

Oh crap, a PCIe v4 MB?

[videoh]

Oh crap, a PCIe v4 MB? Only if you want the doubled bandwidth. :p

[gonca]

Oh crap, a PCIe v4 MB?
And that means an AMD cpu, for the Intel fans

[Mike-uk]

ddr5 and pcie 5 in 2021 for intel, looks like intel are making a good decision to almost skip pcie 4 since it was serverly delayed and jump straight to 5 in 2021

[MrVideo]

And that means an AMD cpu, for the Intel fans
I only do AMD. Intel only shows up in the laptops.

[Ch3vr0n]

Actually intel just anounced the 11th gen mobile CPU's. Native pcie gen 4 support, "more in 2021" and by more they probably mean 11th gen desktop CPU's. current announced cpu models won't support DDR5, but future ones will.

[BuddTX]

And that means an AMD cpu, for the Intel fansI dont follow the AMD-Intel Wars like I used to, but for most of the AMD-Intel wars, AMD offered great value, but if you really wanted the best of the best, you choose Intel, however, I believe that currently, the "Best of the best" is a top of the line AMD processor, and I even think that, price point to price point, AMD beats out Intel. Please correct me, or point me to a link where this is discussed in depth.

[LowDead]

Anyone tried Aladdin (animated, 1992) UHD to 25GB UHD? I lost the subs for some reason. Unfortunately happened to delete the log too, so will have to recreate. Bummer since I did software encode with 2-pass very good quality. And wow the result really popped :) except for the subs..

//LD

[SquallMX]

Anyone tried Aladdin (animated, 1992) UHD to 25GB UHD? I lost the subs for some reason. Unfortunately happened to delete the log too, so will have to recreate. Bummer since I did software encode with 2-pass very good quality. And wow the result really popped :) except for the subs..

//LD

It's not only that disc, I have the same issue with several disks, BDInfo shows subtitle streams as hidden / not referenced, and my standalone won't show them, but MPC-HC does, here is the BDInfo log:


Total Video
Title Codec Length Movie Size Disc Size Bitrate Bitrate Main Audio Track Secondary Audio Track
----- ------ ------- -------------- -------------- ------- ------- ------------------ ---------------------
00800.MPLS HEVC 1:32:05 23,444,624,448 23,958,754,514 33.94 26.58 Dolby Atmos 7.1 3757Kbps (48kHz/24-bit)




DISC INFO:

Disc Title: Beetlejuice
Disc Label: Beetlejuice UHD
Disc Size: 23,958,754,514 bytes
Protection: AACS2
Extras: Ultra HD, BD-Java
BDInfo: 0.7.5.5

PLAYLIST REPORT:

Name: 00800.MPLS
Length: 1:32:05.436 (h:m:s.ms)
Size: 23,444,624,448 bytes
Total Bitrate: 33.94 Mbps

(*) Indicates included stream hidden by this playlist.

VIDEO:

Codec Bitrate Description
----- ------- -----------
MPEG-H HEVC Video 26575 kbps 2160p / 23.976 fps / 16:9 / Mastering display color primaries: Display P3 / Mastering display luminance: min: 0.0000 cd/m2, max: 4000 cd/m2 / Maximum Content Light Level: 3941 cd / m2 / Maximum Frame-Average Light Level: 129 cd/m2 /

AUDIO:

Codec Language Bitrate Description
----- -------- ------- -----------
Dolby TrueHD/Atmos Audio English 3757 kbps 7.1 / 48 kHz / 3117 kbps / 24-bit (AC3 Embedded: 5.1-EX / 48 kHz / 640 kbps / DN -31dB)
Dolby Digital Audio Spanish 192 kbps 2.0 / 48 kHz / 192 kbps
Dolby Digital Audio Spanish 192 kbps 2.0 / 48 kHz / 192 kbps
* Dolby Digital Audio Japanese 192 kbps 2.0 / 48 kHz / 192 kbps

SUBTITLES:

Codec Language Bitrate Description
----- -------- ------- -----------
* Presentation Graphics Japanese 25.001 kbps
* Presentation Graphics English 38.004 kbps
* Presentation Graphics French 28.175 kbps
* Presentation Graphics German 33.634 kbps
* Presentation Graphics Spanish 29.555 kbps
* Presentation Graphics Dutch 28.504 kbps
* Presentation Graphics Chinese 28.782 kbps
* Presentation Graphics Chinese 28.185 kbps
* Presentation Graphics Korean 24.446 kbps
* Presentation Graphics Spanish 29.420 kbps
* Presentation Graphics Czech 30.117 kbps
* Presentation Graphics Thai 30.276 kbps
* Presentation Graphics Japanese 1.175 kbps
* Presentation Graphics Italian 34.181 kbps
* Presentation Graphics Danish 26.654 kbps
* Presentation Graphics Finnish 24.970 kbps
* Presentation Graphics Norwegian 26.325 kbps
* Presentation Graphics Swedish 24.274 kbps
* Presentation Graphics French 0.220 kbps
* Presentation Graphics German 0.419 kbps
* Presentation Graphics Italian 0.373 kbps
* Presentation Graphics Spanish 0.308 kbps
* Presentation Graphics Spanish 0.049 kbps
* Presentation Graphics French 0.220 kbps

FILES:

Name Time In Length Size Total Bitrate
---- ------- ------ ---- -------------
00061.M2TS 0:00:00.000 1:32:05.436 23,444,624,448 33,945

...

STREAM DIAGNOSTICS:

File PID Type Codec Language Seconds Bitrate Bytes Packets
---- --- ---- ----- -------- -------------- -------------- ------------- -----
00061.M2TS 4113 (0x1011) 0x24 HEVC 5525.228 26,576 18,354,894,944 99,832,043
00061.M2TS 4352 (0x1100) 0x83 Atmos eng (English) 5525.228 3,757 2,594,940,474 17,433,490
00061.M2TS 4353 (0x1101) 0x81 AC3 spa (Spanish) 5525.228 192 132,610,560 863,350
00061.M2TS 4354 (0x1102) 0x81 AC3 spa (Spanish) 5525.228 192 132,610,560 863,350
00061.M2TS 4355 (0x1103) 0x81 AC3 jpn (Japanese) 5525.228 192 132,610,560 863,350
00061.M2TS 4768 (0x12A0) 0x90 PGS jpn (Japanese) 5525.228 25 17,267,507 101,971
00061.M2TS 4769 (0x12A1) 0x90 PGS eng (English) 5525.228 38 26,248,149 151,393
00061.M2TS 4770 (0x12A2) 0x90 PGS fra (French) 5525.228 28 19,459,419 112,945
00061.M2TS 4771 (0x12A3) 0x90 PGS deu (German) 5525.228 34 23,230,355 134,957
00061.M2TS 4772 (0x12A4) 0x90 PGS spa (Spanish) 5525.228 30 20,412,790 118,159
00061.M2TS 4773 (0x12A5) 0x90 PGS nld (Dutch) 5525.228 29 19,686,968 114,037
00061.M2TS 4774 (0x12A6) 0x90 PGS zho (Chinese) 5525.228 29 19,879,049 115,378
00061.M2TS 4775 (0x12A7) 0x90 PGS zho (Chinese) 5525.228 28 19,466,453 113,175
00061.M2TS 4776 (0x12A8) 0x90 PGS kor (Korean) 5525.228 24 16,884,302 99,147
00061.M2TS 4777 (0x12A9) 0x90 PGS spa (Spanish) 5525.228 29 20,319,567 117,786
00061.M2TS 4778 (0x12AA) 0x90 PGS ces (Czech) 5525.228 30 20,801,150 120,409
00061.M2TS 4779 (0x12AB) 0x90 PGS tha (Thai) 5525.228 30 20,911,152 121,000
00061.M2TS 4780 (0x12AC) 0x90 PGS jpn (Japanese) 5525.228 1 811,880 4,790
00061.M2TS 4781 (0x12AD) 0x90 PGS ita (Italian) 5525.228 34 23,608,271 137,364
00061.M2TS 4782 (0x12AE) 0x90 PGS dan (Danish) 5525.228 27 18,409,086 107,185
00061.M2TS 4783 (0x12AF) 0x90 PGS fin (Finnish) 5525.228 25 17,246,052 100,547
00061.M2TS 4784 (0x12B0) 0x90 PGS nor (Norwegian) 5525.228 26 18,182,226 106,048
00061.M2TS 4785 (0x12B1) 0x90 PGS swe (Swedish) 5525.228 24 16,765,596 98,101
00061.M2TS 4786 (0x12B2) 0x90 PGS fra (French) 5525.228 0 151,636 898
00061.M2TS 4787 (0x12B3) 0x90 PGS deu (German) 5525.228 0 289,499 1,703
00061.M2TS 4788 (0x12B4) 0x90 PGS ita (Italian) 5525.228 0 257,748 1,529
00061.M2TS 4789 (0x12B5) 0x90 PGS spa (Spanish) 5525.228 0 212,813 1,250
00061.M2TS 4790 (0x12B6) 0x90 PGS spa (Spanish) 5525.228 0 33,567 197
00061.M2TS 4791 (0x12B7) 0x90 PGS fra (French) 5525.228 0 151,636 898



I found the reason!!! subtitles mPID should be 12A0 and so on... but BD-RB is moving them to 1200 (like a normal BD) in the mpls files. I don't know if that is compliant with BD Specs, but you can fix it with BDEdit manually.

Additionally, files processed by NvEnc generates ginormous BDInfo reports with the legend ¨Mastering display color primaries: Display P3 / Mastering display luminance: min: 0.0000 cd/m2, max: 4000 cd/m2 / Maximum Content Light Level: 3941 cd / m2 / Maximum Frame-Average Light Level: 129 cd/m2 /¨ repeated ad-nausem.

[LowDead]

@SquallMX: Great! Thanks for the info! Time to get the latest BDedit..

//LD

[Mike-uk]

bye bye RTX 2070 super :( , the 3 week wait for my RTX 3080 will be sad :(, but hopefully they have made more improvements to nvenc, although noting has been said about the encode and decode cores so possibly the same, but getting the new card mainly for games as im unable to hit 144fps at 1440p with the old card and new one should :)

[LowDead]

@Mike-uk: Keep us posted :)

[jdobbs]

I found the reason!!! subtitles mPID should be 12A0 and so on... but BD-RB is moving them to 1200 (like a normal BD) in the mpls files. I don't know if that is compliant with BD Specs, but you can fix it with BDEdit manually. I think I might know what could be causing that. I'm pretty sure is was caused by changes made in TSMUXER (I upgraded the version). I'll get it fixed for the next release.

[LowDead]

I think I might know what could be causing that. I'm pretty sure is was caused by changes made in TSMUXER (I upgraded the version). I'll get it fixed for the next release.

Would that mean that, if above fix works, I could be lazy and just set output size larger than UHD50 in BDRB and re-run it and it will automagically fix itself? :)

//LD

[BuddTX]

WOOHOO Just watched the Geforce special event. RTX 3090 CONFIRMED, goodbye GTX 1080, hello 3090. BDRB nvenc is gonna FLYYYYYYYYYYYYY on that thing right out along to say hi to tesla's speedster in space :D

Now I see what all the excitement is about!

NVIDIA just made EVERYTHING ELSE obsolete! Linus Tech Tips (https://youtu.be/ucutmH2KvSQ)

[Ch3vr0n]

Meh, the special event was better but not just that. I'm only 37 and have owned my own pc for over 20years. NEVER have I ever owned the top of the line GPU in all that time. Now that I have a way of affording one, I'm getting one.

Sent from my Pixel 3 XL using Tapatalk

[sneaker_ger]

bye bye RTX 2070 super :( , the 3 week wait for my RTX 3080 will be sad :(, but hopefully they have made more improvements to nvenc
Nvidia has said encoding hardware is the same as turing. Only decoding is improved (added AV1 decoding).

Q: Will there be any improvements to the RTX encoder in the Ampere series cards, similar to what we saw for the Turing Release? I did see info on the Broadcast software, but I'm thinking more along the lines of improvements in overall image quality at same bitrate.

For RTX 30 Series, we decided to focus improvements on the video decode side of things and added AV1 decode support. On the encode side, RTX 30 Series has the same great encoder as our RTX 20 Series GPU. We have also recently updated our NVIDIA Encoder SDK. In the coming months, livestream applications will be updating to this new version of the SDK, unlocking new performance options for streamers.
https://www.nvidia.com/en-us/geforce/news/rtx-30-series-community-qa/
https://www.reddit.com/r/nvidia/comments/iko4u7/geforce_rtx_30series_community_qa_submit_your/g3mixss?utm_source=share&utm_medium=web2x&context=3

[jdobbs]

Would that mean that, if above fix works, I could be lazy and just set output size larger than UHD50 in BDRB and re-run it and it will automagically fix itself? :)

//LDYes. That would likely work -- if you mean running BD-RB against the output of your last run.

The subtitles were working when BD-RB used the previous version of TSMUXER (4k) with the PID set starting at 0x1200. In the meantime a change was made that sets them for HDR to an address starting at 0x12A0. Since I missed that note in the change log -- the CLPI and M2TS created by the new version of TSMUXER (on full backups) has a different PID than the MPLS (which is updated by BD-RB to account for languages that may not have been kept). The problem doesn't exist in movie-only backups.

I've fixed it and will kick out a new version in the next couple of days.

[LowDead]

Yes. That would likely work -- if you mean running BD-RB against the output of your last run.

The subtitles were working when BD-RB used the previous version of TSMUXER (4k) with the PID set starting at 0x1200. In the meantime a change was made that sets them for HDR to an address starting at 0x12A0. Since I missed that note in the change log -- the CLPI and M2TS created by the new version of TSMUXER (on full backups) has a different PID than the MPLS (which is updated by BD-RB to account for languages that may not have been kept). The problem doesn't exist in movie-only backups.

I've fixed it and will kick out a new version in the next couple of days.

That was exactly what I meant :)

Great, thanks!

//LD

[MrVideo]

Looks like I'll have to wait until the RTX-3090 is released to find out if the driver for the RTX-30xx series still supports win7-64.

[Mike-uk]

Hi

trying to convert a 2160p mkv to a 25 gig bluray but it keeps failing :( where am i going wrong ??

[14:30:30] Importing MKV: test
- Collecting audio/video streams from source...
- Converting audio, Track #2, EAC3 to AC3...
- Building pseudo-BD source structure...
- Source issue found, attempting correction...
- Building pseudo-BD source structure...
[14:32:15]ERROR: Failed to build BD structure. Aborted.

thanks
mike

[MrVideo]

trying to convert a 2160p mkv to a 25 gig bluray but it keeps failing
H.264 or H.265 source? Looking Blu-ray standard or UHD standard?

JDobbs is working on h.265 to UHD.

A note to JDobbs: When doing the h.265/UHD version, do not convert EAC3 to AC3. While my 4k BD player refuses to play EAC3 files, it will play EAC3 when on a UHD disc. I did a test using TSmuxer to create a BD ISO and that disc played just fine. The Sony player even said that it was a UHD disc, which surprised me. I didn't expect TSmuxer to create a UHD disc.

[Mike-uk]

H.264 or H.265 source? Looking Blu-ray standard or UHD standard?

JDobbs is working on h.265 to UHD.

A note to JDobbs: When doing the h.265/UHD version, do not convert EAC3 to AC3. While my 4k BD player refuses to play EAC3 files, it will play EAC3 when on a UHD disc. I did a test using TSmuxer to create a BD ISO and that disc played just fine. The Sony player even said that it was a UHD disc, which surprised me. I didn't expect TSmuxer to create a UHD disc.

yes its a h265 source and im wanting it to a 25 gig bluray standard

[jdobbs]

- Source issue found, attempting correction...Odds are this is the issue... bad source.

[MrVideo]

yes its a h265 source and im wanting it to a 25 gig bluray standard
Any chance you can find an H.264 MKV source?

[Mike-uk]

Any chance you can find an H.264 MKV source?

yes had to resort to a 264 at half the file size :(, but i guess after re encoding a 265 to 264 ill end up with similar quality anyway

[alex74.744]

have a nice day. sorry for my english i use a translator. noticed such a problem. after deleting unnecessary audio tracks and playing in DUNE HD, the sound on the main movie does not work. When playing a movie with a menu (full menu), there is sound in the menu, additional materials, but there is no sound in the movie itself. When played without a menu (lite), there is sound in the movie. And so on any reassembled film. If you rebuild the movie with the multiAVCHD program, the sound works in the main movie, and in the menu, and in additional materials.

[BuddTX]

Looks like I'll have to wait until the RTX-3090 is released to find out if the driver for the RTX-30xx series still supports win7-64.

I made the jump to W10 this month, upgraded my 10+YO Dell T3500 to W10. It was a rough few days, but I am loving it now!

I made a backup boot HD with my W7, and I had to use it a few times. I have a 2.5/3.5 HD "cassette" that I installed into my PC, so I can mount hard drives without having to open up my computer. I also installed a usb 3.1 card, and a SATA3 controller

I have not even applied any "De-Bloat" "De-Crapifier" etc., W10 Privacy settings yet. I will make a backup image b4 I start applying those "tools".

So, just saying that as a fellow "W7 forever" person, go ahead and make the jump! look up on youtube and google how to most probably be able to still use your W7 activation code to work with W10.

I have a nVidia 1050ti installed, as much as I would like to play with a new GPU, unless the turing NVidia cards get real cheap, (or I win a lottery!), I will be keeping the 1050ti for a while. I know my GPU does not support "HEVC B Frame". So unless a 1660 or better nVidia card gets real cheap (come on Black Friday!), I will be keeping my 1050ti.

Also, if I read the last few pages here correctly, there are no more "new" encoding features on the new nVidia cards, just much faster processing, and other playback and decoding improvements.

One of the many reasons why I like BD-Rebuilder so much, is that I can apply all the "insane" "over kill" super slow video encoding settings in x265 to my MKV files!

Oh, I have to say, check out "Open Shell", it will turn your W10 into the W7 look and feel you love! "Open shell" used to be called "Classic Shell", and the original developer stopped developing "Classic Shell", so a new person took over development of the same program. https://open-shell.github.io/Open-Shell-Menu/

[MrVideo]

No Win10 for me. If need be, I'll get the latest nVidia turning card that still works with Win7-64.

[cartman0208]

Back from holidays I just did the first encode with BDRB 0.61.13 and I swapped the nvenc files with the newest ones (version 5.15 ... which apparently was released just some hours ago) and now HDR10+ works and looks awesome on alternate encodes. :)

I used the hidden switch mentioned in the last release notes.
Will do some more sources to confirm the results.

[jdobbs]

Back from holidays I just did the first encode with BDRB 0.61.13 and I swapped the nvenc files with the newest ones (version 5.15 ... which apparently was released just some hours ago) and now HDR10+ works and looks awesome on alternate encodes. :)

I used the hidden switch mentioned in the last release notes.
Will do some more sources to confirm the results.Great! I noticed the changes had been added to the latest NVENCC release. I'm adding it to BD-RB for the next release.

[jdobbs]

I posted and then removed v0.61.15 -- there's something that I forgot to test and I suspect it may have an issue.

If you downloaded it -- please don't upgrade/use it until I know it is working properly.

[cartman0208]

This might have been reported already?

If BDRB is set to NVENC, the encode stops on some sources with error, when the size-correcting second pass should be performed:

...
- [20:00:21] Processing: VID_00004 (5 of 21)
- [20:00:21] Extracting A/V streams [VID_00004]
- [20:00:26] Reencoding video [VID_00004]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 2.520 frames
- [20:00:26] Performing CQM Prediction...
- Analyzing 14,50 19,15 20,10 [20,12]
- [20:00:36] Encoding using constant quality mode.
- Performing size-correcting second pass...
- [20:00:55] PredictAndEncode() 00011 2994

When I then switch the encoder to x264/x265, I can resume and continue

[Michi]

All my UHDs encoding with NVENCC are in 2176p. I use a GTX1660.

I thought this bug was fixed with turion, but it isn't fixed.

[jdobbs]

I have updated the first post of this thread with a link to the most recent version of BD-RB (v0.61.16). Changes for this release:- Handling of HDR10+ in NVENCC has now been
enabled by default, the hidden option
NVENC_ENABLE_10PLUS is no longer needed or
supported.
- Corrected an issue in which SD imports may
not be reencoded with the correct aspect
ratio under some (rare) circumstances.
- Fixed an issue associated with incorrect
subtitle PID values on UHD/HDR sources.
- Added parameter to MKV creation that makes
odd subtitle characters less likely.
- Updated the version of NVENCC included with
BD-RB to v5.15 -- enabling corrected HDR10+
support.
- Other minor corrections and cosmetic fixes.

[LowDead]

All my UHDs encoding with NVENCC are in 2176p. I use a GTX1660.

I thought this bug was fixed with turion, but it isn't fixed.

That is a hardware limitation. It has nothing to do with BD-RB. Anyway you have nothing to worry about as the decoder on your player corrects this and output it as intended per the specs.

This is my understandings, anyone feel free to correct me if i'm wrong.

//LD

[jdobbs]

That is a hardware limitation. It has nothing to do with BD-RB. Anyway you have nothing to worry about as the decoder on your player corrects this and output it as intended per the specs.

This is my understandings, anyone feel free to correct me if i'm wrong.

//LDThat is also my understanding. From what I've read, the way it is used is in sync with industry standards, and if any player has an issue with it -- it is the player that has a "bug", not the encode.

[MrVideo]

It is the same thing with 1080 video. In case you didn't know, 1080 is encoded at 1088, as it too needs to be a multiple of 16. In the early days of OTA HD, my local NBC affiliate had their encoder screwed up such that the 1088 was actually displayed as 1088. The VideoReDo software had to add a "feature" where this was detected and fixed so that I could edit 1080 material with this screwed up 1088 material.

[mikeonecl]

any setup for processing a 3d movie with nvenc enabled?
i mean 3d encoding with nvenc

[Ch3vr0n]

no. 3D requires FRIM and even with nvenc, when bdrb detects 3D afaik it will override the decoder/encoder and default to FRIM

[BuddTX]

I have an install question, and I apologize in advance if it has been answered before, or if the answer is obvious, but obviously it is confusing to me:stupid::

The instructions say:
=================================
2. While not required it is recommended you perform either one of the following (2A, preferred, or 2B):

2A. Download and install the LAV Directshow Filters. Use only the version linked here -- as other versions may result in out-of-sync audio. While not required for BD-RB to work, LAVFilters will improve functionality and are free. They are required for some functionality associated with HEVC import and processing.

2B. Download and install FFDSHOW and the Haali Matroska Splitter. While they are not required for BD-RB to work, they will improve functionality and are free. After the install, run "Video Decoder Configuration" for FFDSHOW from the "START/Programs" menu, and make sure MPEG2 decoding is enabled. Do the same using "Audio Decoder Configuration" to ensure "Uncompressed" is set to "All Supported".

2C. If you decide to install both 2A and 2B, make sure HAALI/FFDSHOW (2B) is installed first, followed by LAVFilters (2A). This will prevent issues with HEVC splitting.
=================================

So the first line says "2A, preferred". OK that makes sense, I always want to do what the author recommends, right!

But then in 2B it says:
=======
While they are not required for BD-RB to work, they will improve functionality and are free.
=======

So, does this mean I SHOULD ALSO install 2B?

After all, who would not want "improved functionality". I am assuming that BD Rebuilder will work better if both 2A and 2B are installed, based on this statement, but the first statement says that 2A is preferred.

Thanks in advance!

[LowDead]

Just wanted to say that subtitles works now for me with full backup UHD with HDR and I could feed the old encode to "fix" it without doing a new encode.

Thanks ALOT for the fix!! :D

//LD

[jdobbs]

I have an install question, and I apologize in advance if it has been answered before, or if the answer is obvious, but obviously it is confusing to me:stupid::

The instructions say:
=================================
2. While not required it is recommended you perform either one of the following (2A, preferred, or 2B):

2A. Download and install the LAV Directshow Filters. Use only the version linked here -- as other versions may result in out-of-sync audio. While not required for BD-RB to work, LAVFilters will improve functionality and are free. They are required for some functionality associated with HEVC import and processing.

2B. Download and install FFDSHOW and the Haali Matroska Splitter. While they are not required for BD-RB to work, they will improve functionality and are free. After the install, run "Video Decoder Configuration" for FFDSHOW from the "START/Programs" menu, and make sure MPEG2 decoding is enabled. Do the same using "Audio Decoder Configuration" to ensure "Uncompressed" is set to "All Supported".

2C. If you decide to install both 2A and 2B, make sure HAALI/FFDSHOW (2B) is installed first, followed by LAVFilters (2A). This will prevent issues with HEVC splitting.
=================================

So the first line says "2A, preferred". OK that makes sense, I always want to do what the author recommends, right!

But then in 2B it says:
=======
While they are not required for BD-RB to work, they will improve functionality and are free.
=======

So, does this mean I SHOULD ALSO install 2B?

After all, who would not want "improved functionality". I am assuming that BD Rebuilder will work better if both 2A and 2B are installed, based on this statement, but the first statement says that 2A is preferred.

Thanks in advance!No. Sorry, that's badly worded. It means that BD-RB will run without either of them (LAV or FFDSHOW) -- but installing one or the other will improve functionality. Using 2A is preferable.

[jdobbs]

Just wanted to say that subtitles works now for me with full backup UHD with HDR and I could feed the old encode to "fix" it without doing a new encode.

Thanks ALOT for the fix!! :D

//LDGlad to be of help. :)

[BuddTX]

No. Sorry, that's badly worded. It means that BD-RB will run without either of them (LAV or FFDSHOW) -- but installing one or the other will improve functionality. Using 2A is preferable.

As always, Thank you JDobbs!

[LowDead]

I got this error with UHD The Natural. Did it before with previous version of BD-RB without fail, but as I got a bit of an undersize + the sub bug I decided to redo it comletely with the new version.

----------------------
[09-17-20] BD Rebuilder v0.61.16
[02:28:54] Source: NATURAL__THE_
- Input BD size: 84,78 GB
- Approximate total content: [03:25:27.987]
- Target BD size: 49,02 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[02:28:54] PHASE ONE, Encoding
- [02:28:54] Processing: VID_00001 (1 of 43)
- [02:28:54] Extracting A/V streams [VID_00001]
- [02:28:57] Reencoding video [VID_00001]
- [02:28:57] Keeping original video (no reencode)
- [02:28:57] Processing audio tracks
- [02:28:57] Multiplexing M2TS
- [02:29:01] Processing: VID_00080 (2 of 43)
- [02:29:01] Extracting A/V streams [VID_00080]
- [02:29:05] Reencoding video [VID_00080]
- [02:29:05] Keeping original video (no reencode)
- [02:29:05] Processing audio tracks
- [02:29:05] Multiplexing M2TS
- [02:29:08] Processing: VID_00081 (3 of 43)
- [02:29:08] Extracting A/V streams [VID_00081]
- [02:29:12] Reencoding video [VID_00081]
- [02:29:12] Keeping original video (no reencode)
- [02:29:12] Processing audio tracks
- [02:29:12] Multiplexing M2TS
- [02:29:15] Processing: VID_00082 (4 of 43)
- [02:29:15] Extracting A/V streams [VID_00082]
- [02:29:19] Reencoding video [VID_00082]
- [02:29:19] Keeping original video (no reencode)
- [02:29:19] Processing audio tracks
- [02:29:19] Multiplexing M2TS
- [02:29:22] Processing: VID_00100 (5 of 43)
- [02:29:22] Extracting A/V streams [VID_00100]
- [02:29:28] Reencoding video [VID_00100]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 346 frames
- Bitrate: 11 918 Kbs
- [02:29:28] Reencoding: VID_00100, Pass 1 of 2
- [02:31:59] Reencoding: VID_00100, Pass 2 of 2
- [02:34:58] Video Encode complete
- [02:34:58] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [02:34:58] Multiplexing M2TS
- [02:35:02] Processing: VID_00102 (6 of 43)
- [02:35:02] Extracting A/V streams [VID_00102]
- [02:35:06] Reencoding video [VID_00102]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 5 200 frames
- Bitrate: 500 Kbs
- [02:35:06] Reencoding: VID_00102, Pass 1 of 2
- [02:46:37] Reencoding: VID_00102, Pass 2 of 2
- [02:54:01] Video Encode complete
- [02:54:01] Processing audio tracks
- [02:54:01] Multiplexing M2TS
- [02:54:05] Processing: VID_00104 (7 of 43)
- [02:54:05] Extracting A/V streams [VID_00104]
- [02:54:10] Reencoding video [VID_00104]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 1 frames
- Bitrate: 48 000 Kbs
- [02:54:10] Reencoding: VID_00104, Pass 1 of 2
- [02:54:11] Reencoding: VID_00104, Pass 2 of 2
- [02:54:13] Video Encode complete
- [02:54:13] Processing audio tracks
- [02:54:13] Multiplexing M2TS
- [02:54:17] Processing: VID_00116 (8 of 43)
- [02:54:17] Extracting A/V streams [VID_00116]
- [02:54:21] Reencoding video [VID_00116]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 271 frames
- Bitrate: 4 292 Kbs
- [02:54:21] Reencoding: VID_00116, Pass 1 of 2
- [02:55:35] Reencoding: VID_00116, Pass 2 of 2
- [02:56:53] Video Encode complete
- [02:56:53] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [02:56:53] Multiplexing M2TS
- [02:56:57] Processing: VID_00208 (9 of 43)
- [02:56:57] Extracting A/V streams [VID_00208]
- [02:57:01] Reencoding video [VID_00208]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 262 frames
- Bitrate: 3 863 Kbs
- [02:57:01] Reencoding: VID_00208, Pass 1 of 2
- [02:58:02] Reencoding: VID_00208, Pass 2 of 2
- [02:59:00] Video Encode complete
- [02:59:00] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [02:59:00] Multiplexing M2TS
- [02:59:04] Processing: VID_00336 (10 of 43)
- [02:59:04] Extracting A/V streams [VID_00336]
- [02:59:08] Reencoding video [VID_00336]
- [02:59:08] Keeping original video (no reencode)
- [02:59:08] Processing audio tracks
- [02:59:08] Multiplexing M2TS
- [02:59:11] Processing: VID_00337 (11 of 43)
- [02:59:11] Extracting A/V streams [VID_00337]
- [02:59:46] Reencoding video [VID_00337]
- Source Video: HEVC, 3840x2160
- Rate/Length: 59,940fps, 7 728 frames
- Bitrate: 22 256 Kbs
- [02:59:46] Reencoding: VID_00337, Pass 1 of 2
- [04:20:04] Reencoding: VID_00337, Pass 2 of 2
- [05:38:56] Video Encode complete
- [05:38:56] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [05:38:56] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00337.meta
- HEVC manual defined fps doesn't equal to stream fps. Change HEVC fps from 59.97 to 59.9401
[05:39:02] - Failed to build structure, aborted

[Status]
LABEL=NATURAL__THE_
VERSION=v0.61.16
SOURCE_SIZE=91036714291
SOURCE_VIDEO_SIZE=90696757248
TARGET_SIZE=52638515200
REDUCTION=.576630959517059
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=0
INSTANCES=1
DGDECNV=-1
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
UHD_V3_MODE=0
QUICK=0
ENCODE_STEP=4
COMPLETED=10
[00001]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=325939
USE_ORIGINAL=1
NSTART=27000000
NEND=28351349
NSIZE=589824
FLINK=0
MLINK=0
[00080]
AUDIO=
PGS=1
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=109827
USE_ORIGINAL=1
NSTART=27000000
NEND=27450449
NSIZE=196608
FLINK=0
MLINK=0
[00081]
AUDIO=
PGS=1
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=109827
USE_ORIGINAL=1
NSTART=27000000
NEND=27450449
NSIZE=196608
FLINK=0
MLINK=0
[00082]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=109827
USE_ORIGINAL=1
NSTART=27000000
NEND=27450449
NSIZE=196608
FLINK=0
MLINK=0
[00100]
AUDIO=1
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=24643860
RATE=11918
NSTART=27000000
NEND=27649398
NSIZE=24084480
FLINK=0
MLINK=0
[00102]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=4439154
RATE=500
NSTART=27000000
NEND=36759749
NSIZE=8294400
FLINK=0
MLINK=0
[00104]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=276340
RATE=48000
NSTART=27000000
NEND=27001876
NSIZE=430080
FLINK=0
MLINK=0
[00116]
AUDIO=1
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=6940386
RATE=4292
NSTART=27000000
NEND=27508632
NSIZE=6782976
FLINK=0
MLINK=0
[00208]
AUDIO=1
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=6079480
RATE=3863
NSTART=27000000
NEND=27491740
NSIZE=6070272
FLINK=0
MLINK=0
[00336]
AUDIO=
PGS=1
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=109827
USE_ORIGINAL=1
NSTART=27000000
NEND=27450449
NSIZE=196608
FLINK=0
MLINK=0
[00337]
AUDIO=1
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=390557002
RATE=22256

"C:\vidsoft\BD_Rebuilder\tools\ffmpeg.exe" -probesize 100MB -i "A:\UHDBD\THE NATURAL\BDMV\STREAM\00337.m2ts" -an -pix_fmt yuv420p10le -f yuv4mpegpipe -strict -1 - | "C:\vidsoft\BD_Rebuilder\tools\x265-64.exe" - --preset slow --profile main10 --uhd-bd --repeat-headers --vbv-bufsize 45000 --vbv-maxrate 48000 --hdr --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50)" --fps 59.97 --sar 1:1 --qpfile "B:\WORK\WORKFILES\VID_00337.CHP" --keyint 60 --bitrate 22256 --y4m --stats "B:\WORK\WORKFILES\VID_00337.AVS.hevc.stats" --pass 2 --output "B:\WORK\WORKFILES\VID_00337.AVS.hevc"

[09-17-20] Checking System Settings
- BD-Rebuilder v0.61.16
- Windows Version: 6.2 [9200]
- Working Path Free Space: 604,51GB
- AVISYNTH Version: 2.6.0.5, Ok
- LAVFILTERS: Ok
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[09-17-20] Systems Settings Check complete

//LD

[Ch3vr0n]

@Jdobbs if you're interested, the Nvidia 3000 series whitepaper is now available. https://www.nvidia.com/en-us/geforce/news/rtx-30-series-ampere-architecture-whitepaper-download/

Sent from my Pixel 3 XL using Tapatalk

[gonca]

NVEnc hasn't changed, NVDec has been improved

[varekai]

@jdobbs
Thanks for the update! Much appreciated!

[jdobbs]

This might have been reported already?

If BDRB is set to NVENC, the encode stops on some sources with error, when the size-correcting second pass should be performed:

...
- [20:00:21] Processing: VID_00004 (5 of 21)
- [20:00:21] Extracting A/V streams [VID_00004]
- [20:00:26] Reencoding video [VID_00004]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 2.520 frames
- [20:00:26] Performing CQM Prediction...
- Analyzing 14,50 19,15 20,10 [20,12]
- [20:00:36] Encoding using constant quality mode.
- Performing size-correcting second pass...
- [20:00:55] PredictAndEncode() 00011 2994

When I then switch the encoder to x264/x265, I can resume and continueI fixed this one. Thanks for your help. It was a silly mistake on my part (the code was looking for a wrong filename when collecting the file size -- resulting in a divide-by-zero error). I'm looking at one other bug I'd like to fix, and then I'll release a new version.

[LowDead]

- [05:38:56] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00337.meta
- HEVC manual defined fps doesn't equal to stream fps. Change HEVC fps from 59.97 to 59.9401
[05:39:02] - Failed to build structure, aborted

Update to my issue:

Made a new encode switching to NVEnc encoder instead and then it did get past that muxing error point. Will test another new x265 encode to see if it was something temporary.

//LD

UPDATE: I did another encode with x265 and managed to reproduce the error. So maybe a bug in x265? Can I download a newer version of x265 from somewhere to test if the bug is fixed?

UPDATE 2: Noticed that the error wasn't exactly the same as before..

- [23:46:01] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00337.meta
- Muxing time: 3 sec
[23:46:10] - Failed to build structure, aborted

After restarting and letting it continue with the backup the muxing went on fine and the disc continued with the encode.

[jdobbs]

Update to my issue:

Made a new encode switching to NVEnc encoder instead and then it did get past that muxing error point. Will test another new x265 encode to see if it was something temporary.

//LD

UPDATE: I did another encode with x265 and managed to reproduce the error. So maybe a bug in x265? Can I download a newer version of x265 from somewhere to test if the bug is fixed?

UPDATE 2: Noticed that the error wasn't exactly the same as before..



After restarting and letting it continue with the backup the muxing went on fine and the disc continued with the encode.It's more likely an error in TSMUXER. Try using TSMUXER4K.EXE for the mux and you may find it works. There were multiple bugs fixed with the new release of TSMUXER (v2.6.16). Unfortunately there are also some changes that can create issues... and I'm working on BD-RB to adjust for those changes. In the end I'm hoping to use the newer version as a complete replacement (it is currently only used for UHD muxing).

[LowDead]

It's more likely an error in TSMUXER. Try using TSMUXER4K.EXE for the mux and you may find it works. There were multiple bugs fixed with the new release of TSMUXER (v2.6.16). Unfortunately there are also some changes that can create issues... and I'm working on BD-RB to adjust for those changes. In the end I'm hoping to use the newer version as a complete replacement (it is currently only used for UHD muxing).

Well then, thats the one that is used as it is a UHD disc...

//LD

[jdobbs]

Well then, thats the one that is used as it is a UHD disc...

//LDUghhh...

[LowDead]

ughhh...

?

//ld

[cartman0208]

Time for your own muxer implementation? ;)

[jdobbs]

?

//ldI was just commenting that it means it is likely a bug that I will have to hunt down and destroy.

[LowDead]

I was just commenting that it means it is likely a bug that I will have to hunt down and destroy.

Ahh, I see. Will post some info on the file that behaves strange as soon as the encode is finished that I'm on now. It's still The Natural.. The movie is divided into Theatrical and Extended versions with seamless branching. It's a pain with all the small segments as it takes like 5-6 days to complete (2-pass very good x265). ohhh I like that sweet sweet quality ;)

//LD

[jdobbs]

I've noticed an anomaly with NVENCC and I wonder if anyone else is experiencing the same thing.

When encoding a 1920x1080 source I typically get about 320 or so frames per second. But I notice that sometimes it encodes at 150 fps. When it does that, if I stop the encode and restart it -- it goes right back up to 320 fps and stays there for the remainder of the encode. I haven't done any extensive testing -- but it seems that I see it when there is more than one encode -- and one is starting right after the other (like in a multipart encode).

Not sure how or why it does that. Anyone else have any insight?

[ggtop]

Hi jdobbs,

I feel a little bit guilty that a lot of people ask for help and you in return get no response...
Actually I'm running a NVEncC encode the very first time now. I only have a Feforce GT730 running under Win10 using MS drivers, but as far as I'm informed it should work with x264.
It's only running with 100 FPS so I'm not even sure if faster than CPU.
When I look into e.g. taskmanager I see 1 process called "NVEncC.exe". Don't know how it is designed but if the host is running something like a service it could be that an orphaned or not correctly quitted task gets re-activated when a new one is started. Do you see more than one process? Or NVEnc is running multi-threaded which it doesn't on my ancient card?

BTW Will compare speed later.

Edit: Speed in nearly equal on my system:
Source: Avengers Endgame, Full backup to BD-25
NVEnC: 102 FPS, full GPU load on encoding/decoding, CPU: 20%
SW: 96 FPS, full CPU load, 75% GPU load while decoding using DGDecNV

While the SW encode is still running I'm very pleased with the visual result.

ggtop

[jdobbs]

Hi jdobbs,

I feel a little bit guilty that a lot of people ask for help and you in return get no response...
Actually I'm running a NVEncC encode the very first time now. I only have a Feforce GT730 running under Win10 using MS drivers, but as far as I'm informed it should work with x264.
It's only running with 100 FPS so I'm not even sure if faster than CPU.
When I look into e.g. taskmanager I see 1 process called "NVEncC.exe". Don't know how it is designed but if the host is running something like a service it could be that an orphaned or not correctly quitted task gets re-activated when a new one is started. Do you see more than one process? Or NVEnc is running multi-threaded which it doesn't on my ancient card?

BTW Will compare speed later.

Edit: Speed in nearly equal on my system:
Source: Avengers Endgame, Full backup to BD-25
NVEnC: 102 FPS, full GPU load on encoding/decoding, CPU: 20%
SW: 96 FPS, full CPU load, 75% GPU load while decoding using DGDecNV

While the SW encode is still running I'm very pleased with the visual result.

ggtopThanks.

[gonca]

As I understand you get slow downs when running consecutive encodes
Ran a simple test with consecutive encodes (x64>x64>x86>x86)
Input was the same for all encodes (vpy script using DGIndexNV)
computer was in use at this time on another encode

Results
\nvencc64.exe" --codec avc --cqp 22 --output T:\\00246.264 --y4m --input
fps 309.29
fps 300.48

\nvencc.exe" --codec avc --cqp 22 --output "T:\\00246 (2).264" --y4m --input
fps 284.18
fps 284.34

[LowDead]

Got a reply from Bitdefender regarding the whole ransomware farce.

"Thank you for your patience.

First of all, please accept my apologies for the severely delayed response. It was by no means intended, just that we are currently receiving a higher number of requests than usual and it takes longer for us to reply. We are working around the clock in order to improve our response time and I am sure that in the future you will notice a significant improvement.

The file was analyzed and it is currently not detected from our end. However, if the .exe file is taking actions in specific locations similar to what real ransomware would do, you will have to add a local exception.

Open Bitdefender, click on the Protection tab and then go to Ransomware Remediation, click on the Add an Exception button, and add the file in question.

If the situation persists, please send us a screenshot with the detection."

..So it shouldn't be detected anymore in bitdefender and IF it still does, one has to manually add BD-RB to exceptions.

//LD

[Ch3vr0n]

I got a GTX 1080 (placed my order in for a 3090 on wednesday lol), i'll see if can reproduce this fps issue

**edit** Pretty consistent so far on my end

Source: Pacific Rim Uprising
Decoder: NVDec (GPU load 45-55%)
Encoder: NVEnc (GPU load 30-35%, Memory use: 320-330MB)
Max FPS: 230-235 with peak of around 250-260 at the 80% complete mark for the main title. Smaller clips cap out at around 350-360 (maybe my 3090 will increase that count :D)
CPU load: 10-13%
Start to fish: around 20min

[LowDead]

I got a GTX 1080 (placed my order in for a 3090 on wednesday lol), i'll see if can reproduce this fps issue

**edit** Pretty consistent so far on my end

Source: Pacific Rim Uprising
Decoder: NVDec (GPU load 45-55%)
Encoder: NVEnc (GPU load 30-35%, Memory use: 320-330MB)
Max FPS: 230-235 with peak of around 250-260 at the 80% complete mark for the main title. Smaller clips cap out at around 350-360 (maybe my 3090 will increase that count :D)
CPU load: 10-13%
Start to fish: around 20min

Please do come with an comparison with the 3090 when it arrives :)

//LD

[Ch3vr0n]

you bet. That'll probably be a while though. In case ya wanna know which one. Picked the ROG STRIX RTX3090 024G Gaming (aka the highest overclocked model ^^). Dollar to Euro, snapped a CUSTOM card up for UNDER nvidia MSRP for a founders edition. Lol € 1390, 110€ cheaper than founders edition.