BD Rebuilder Beta - Bug Reports Only

[Alleycat]

You have to rename it to "tsmuxer4k.exe" and then copy it to the BD-RB TOOLS folder. I gave it that name to distinguish it from the older version of TSMUXER (v2.6.12) which is still present in the TOOLS folder.

Thanks, all now understood. I went ahead and tried the newest version, but it still produces m2ts files with missing or corrupted audio when played directly in Windows with VLC or J.River media centre etc. With the old 2.6.12 version, all played perfectly.

After doing some further experiments, I may have found something of use.

Using TsmuxerGUI, I noticed a difference in the meta files produced by the old and new versions. The new Tsmuxer has the extra parameter, "--hdmv-descriptors" included in the first line.
E.g. "MUXOPT --no-pcr-on-video-pid --new-audio-pes --hdmv-descriptors --blu-ray --vbr --auto-chapters=5 --vbv-len=500".

Next I used the command line TsMuxer (newest) to produce muxes using .meta files both with and without --hdmv-descriptors. The one without had the sound issues previously mentioned, but the one with it played perfectly. I tried this test again with the old Tsmuxer but this time both were fine. I expected this, as the help info only mentions this new parameter in the newest versions.

Looking in the BDRB Workfiles folder, the Mux_000xx.meta does not contain the --hdmv-descriptors entry, even though 2.6.16 was enabled.

[jdobbs]

Thanks, all now understood. I went ahead and tried the newest version, but it still produces m2ts files with missing or corrupted audio when played directly in Windows with VLC or J.River media centre etc. With the old 2.6.12 version, all played perfectly.

After doing some further experiments, I may have found something of use.

Using TsmuxerGUI, I noticed a difference in the meta files produced by the old and new versions. The new Tsmuxer has the extra parameter, "--hdmv-descriptors" included in the first line.
E.g. "MUXOPT --no-pcr-on-video-pid --new-audio-pes --hdmv-descriptors --blu-ray --vbr --auto-chapters=5 --vbv-len=500".

Next I used the command line TsMuxer (newest) to produce muxes using .meta files both with and without --hdmv-descriptors. The one without had the sound issues previously mentioned, but the one with it played perfectly. I tried this test again with the old Tsmuxer but this time both were fine. I expected this, as the help info only mentions this new parameter in the newest versions.

Looking in the BDRB Workfiles folder, the Mux_000xx.meta does not contain the --hdmv-descriptors entry, even though 2.6.16 was enabled.Interesting. I'll do some research on that parameter and, if appropriate, I'll add it in the next release.

Thanks for the info!

[Edit] Couldn't find any discussion as to why that parameter was added, or why it was needed. It's easy to add, and the old TSMUXER version seems to not care if it is there. But I don't want to just add it until I know the consequences. Does anyone have any background on this parameter?

[Edit] Ok, I found some discussion in the TSMUXER Open Source thread and some of the change notes. I'll add that parameter to the next release.

[LowDead]

Update:

Working -

"C:\vidsoft\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "L:\UHDBD\FLASH_GORDON_-_4K_UHD\BDMV\STREAM\02001.m2ts" --codec h264 --preset performance --bluray --qp-min 0 --multipass 2pass-full --vbr 0 --vbr-quality 20 --aq-temporal --keyfile "E:\WORK\FIXEDCRF\WORKFILES\VID_02001.CHP" --sar 1:1 --aud --pic-struct --vbv-bufsize 30000 --max-bitrate 35000 --gop-len 24 -o "E:\WORK\FIXEDCRF\WORKFILES\VID_02001.AVS.264"

Not working -

"C:\vidsoft\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "L:\UHDBD\FLASH_GORDON_-_4K_UHD\BDMV\STREAM\02001.m2ts" --codec h264 --preset quality --bluray --qp-min 0 --vbr 11056 --aq-temporal --keyfile "B:\WORK\DG\WORKFILES\VID_02001.CHP" --sar 1:1 --aud --pic-struct --vbv-bufsize 30000 --max-bitrate 35000 --gop-len 24 -o "B:\WORK\DG\WORKFILES\VID_02001.AVS.264"

Difference: EDIT: NEVER MIND Just remembered I encoded the working one with Very fast setting so that is of course the difference with the preset. --preset quality vs. performance - Strange if this is it as the quality parameter should be better.

--multipass 2pass-full is absent in the non working one. Should it be there?

Otherwise the only difference I can see is the constant quality mode switch witch shouldn't have anything to do with it.

//LD

[Sharc]

.....One thing I noticed was that my test extras clip had a bitrate of ~7000kbit instead of ~4000 kbit.

"C:\vidsoft\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "L:\UHDBD\FLASH_GORDON_-_4K_UHD\BDMV\STREAM\02001.m2ts" --codec h264 --preset performance --bluray --qp-min 0 --multipass 2pass-full --vbr 0 --vbr-quality 20 --aq-temporal --keyfile "E:\WORK\FIXEDCRF\WORKFILES\VID_02001.CHP" --sar 1:1 --aud --pic-struct --vbv-bufsize 30000 --max-bitrate 35000 --gop-len 24 -o "E:\WORK\FIXEDCRF\WORKFILES\VID_02001.AVS.264"


Yes, of course. According to your commandline (marked red) you encoded it with a CQM of 20 rather than about 23 as before. Hence the bitrate increased from about 4000 to 7000kbps.
And you shouldn't worry much about the --multipass 2pass-full. Slower presets include it silently and it is actually no longer needed explicitly. If it is still there it does no harm though. It's a legacy. Maybe you should update your NVIDIA drivers.

Edit: And btw. your "Not working" was a bitrate (--vbr 1105) rather than a quality based (--vbr 0 --vbr-quality 20) encode.

[zamengo]

Does it have a forced Portuguese subtitle? It only works to select from the list of subs that actually contain forced subs within them.

If you want a set of subtitle to be turned on by default (as opposed to selecting from forced subs) you can right click on a sub in the streams list and set it to default on.

Nops.

The MKV have only the audio tracks.

This sub come from a ".srt" on same folder of MKV when I import MKV.

Ok, not a problem mux with MKV merge and set "por" on sub...

But, I will make a tv show with 30 mkvs where .srt files will be on the same folder.

Any way to set this external sub as portuguese?

Maybe make .sup files? bdrebuilder import .sup files like .srt on the same folder?

[ggtop]

Hi zamengo,

according to <HIDDENOPTS.txt> there's a setting
IMPORT_SRT_LANG=s s = language code, sets default language for independently imported SRT files Default=eng
I suggest to paste IMPORT_SRT_LANG=por (or IMPORT_SRT_LANG=pt) into your BDREBUILDER.INI and try that.

ggtop

[jdobbs]

I have updated the first post of this thread with a link to the most recent version of BD-RB (v0.61.18). Changes for this release:- Corrected an issue in which ALTERNATE 3D
SBS sources could not be encoded in NVENCC
mode.
- Added TWEAK_ALTERNATE_NV as a new hidden
option. See HIDDENOPTS.TXT.
- Added mBitrate option to ALTERNATE.TXT.
This allows you to set a maximum bitrate
and VBV buffer size for ALTERNATE encode
presets specified in ALTERNATE.TXT. Only
applies to cTypes 1 (MKV) and 5 (MP4).
- Added the --hdmv-descriptors to the TSMUXER
meta file when appropriate to correct for
issues associated with the new version of
TSMUXER.
- Other minor corrections and cosmetic fixes.

[zamengo]

Hi zamengo,

according to <HIDDENOPTS.txt> there's a setting
IMPORT_SRT_LANG=s s = language code, sets default language for independently imported SRT files Default=eng
I suggest to paste IMPORT_SRT_LANG=por (or IMPORT_SRT_LANG=pt) into your BDREBUILDER.INI and try that.

ggtop

Nice one! Thanks!

https://i.imgur.com/VQITjMF.png

:thanks:

[Alleycat]

Interesting. I'll do some research on that parameter and, if appropriate, I'll add it in the next release.

Thanks for the info!

[Edit] Couldn't find any discussion as to why that parameter was added, or why it was needed. It's easy to add, and the old TSMUXER version seems to not care if it is there. But I don't want to just add it until I know the consequences. Does anyone have any background on this parameter?

[Edit] Ok, I found some discussion in the TSMUXER Open Source thread and some of the change notes. I'll add that parameter to the next release.

That's great. I've download the new BDRB and can confirm that all audio tracks are now playing just fine in the various PC players.
I found a little more about the new hdmv descriptors parameter from the help info within TSmuxer itself. It states the following:

"--hdmv-descriptors" "Use HDMV descriptors instead of ITU-T H.222.0 | ISO/IEC 13818-1 descriptors. Activated automatically for BD muxing." (My bold)

Clearly it wasn't activated automatically in the non GUI TsMuxer. When that parameter was not specified, PCM and Dolby TrueHD soundtracks would fail to play in most PC media players.
Many thanks for the quick update of BDRB. :)

[Glarioo]

- Added TWEAK_ALTERNATE_NV as a new hidden
option. See HIDDENOPTS.TXT.

jdobbs, I added this in the BDREBUILDER.INI file:
TWEAK_ALTERNATE_NV=--vbv-maxrate 50000 --vbv-bufsize 50000
The video failed to encode.

----------------------
[14:41:17] Importing MKV: UNCUT_GEMS
- Collecting audio/video streams from source...
- Building pseudo-BD source structure...
[14:47:50] Video import completed successfully.
----------------------
[10/20/20] BD Rebuilder v0.61.18
[14:57:41] Source: UNCUT_GEMS_00000
- Input BD size: 38,81 GB
- Approximate total content: [02:15:08.141]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1920x1080, 640Kbs DD5.1
- Quality: Highest (Very Slow)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[14:57:41] PHASE ONE, Encoding
- [14:57:41] Processing: VID_00000 (1 of 1)
- [14:57:41] Extracting A/V streams [VID_00000]
- [15:00:36] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 194 401 frames
- [15:00:36] Reencoding: VID_00000, Pass 1 of 1
[15:00:36] - Failed video encode, aborted

LASTCMD: "C:\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "G:\BDRB_WORK\IMPORTS\UNCUT_GEMS\BDMV\STREAM\00000.m2ts" --codec h264 --preset quality --bluray --vbr 0 --vbr-quality 20 --aq-temporal --keyfile "G:\BDRB_WORK\WORKFILES\VID_00000.CHP" --aud --pic-struct --vbv-bufsize 15000 --max-bitrate 15000 --gop-len 48 --vbv-maxrate 50000 --vbv-bufsize 50000 -o "G:\BDRB_WORK\WORKFILES\VID_00000.AVS.264"

What am I doing wrong here?

[jdobbs]

@Glarioo

What error do you get if you run that command line from a CMD window?

[Glarioo]

I deleted the line TWEAK_ALTERNATE_NV=--vbv-maxrate 50000 --vbv-bufsize 50000 in the .INI file
and added mBitrate=50000 in the ALTERNATE.TXT
It looks like this:
[00010]
caption=MKV Container, 1920x1080, 640Kbs DD5.1
vBitrate=1941
aBitrate=640
aType=0
vFormat=5
cType=1
mBitrate=50000

BDRebuilder works now, so it was my mistake.

But the max bitrate output, after encoding, was 40000.
So 40000 is the maximum value for NVEnc encodings, I guess.

General
Unique ID : 221187679920445539249478065391758479108 (0xA66732967E11292A8F44EFAAC7500F04)
Complete name : G:\BDRB_Work\UNCUT_GEMS.mkv
Format : Matroska
Format version : Version 2
File size : 15.2 GiB
Duration : 2 h 15 min
Overall bit rate mode : Variable
Overall bit rate : 16.1 Mb/s
Encoded date : UTC 2020-10-20 13:45:50
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 : High@L4.1
Format settings : CABAC / 3 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 3 frames
Format settings, GOP : M=4, N=24
Codec ID : V_MPEG4/ISO/AVC
Duration : 2 h 15 min
Bit rate mode : Variable
Bit rate : 15.4 Mb/s
Maximum bit rate : 40.0 Mb/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 : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.310
Stream size : 14.6 GiB (96%)
Default : Yes
Forced : No

[Glarioo]

@Glarioo

What error do you get if you run that command line from a CMD window?

Excuse me, jdobbs. I read your message too late.
BDRebuilder didn't really give an CMD window error.
Just: "Failed video encode, aborted"

I changed in the ALTERNATE.TXT file mBitrate to 40000. Alright for you?

[00010]
caption=MKV Container, 1920x1080, 640Kbs DD5.1
vBitrate=1941
aBitrate=640
aType=0
vFormat=5
cType=1
mBitrate=40000

[jdobbs]

Excuse me, jdobbs. I read your message too late.
BDRebuilder didn't really give an CMD window error.
Just: "Failed video encode, aborted"

I changed in the ALTERNATE.TXT file mBitrate to 40000. Alright for you?

[00010]
caption=MKV Container, 1920x1080, 640Kbs DD5.1
vBitrate=1941
aBitrate=640
aType=0
vFormat=5
cType=1
mBitrate=40000The window is hidden when BD-RB runs it. But you can open a CMD window (after it fails) and cut/paste the contents of LASTCMD into it (and push ENTER). Then you would be able to see the whatever error message occurs.

Not sure why it got limited to 40Mbs. Is that what is showing in LASTCMD? I thought that maybe the Level 4.1 had done it -- but I looked it up and it has a limit of 50Mbs. It's possible, I guess, that I missed something in the code.

[Glarioo]

The window is hidden when BD-RB runs it. But you can open a CMD window (after it fails) and cut/paste the contents of LASTCMD into it (and push ENTER). Then you would be able to see the whatever error message occurs.

Not sure why it got limited to 40Mbs. Is that what is showing in LASTCMD? I thought that maybe the Level 4.1 had done it -- but I looked it up and it has a limit of 50Mbs. It's possible, I guess, that I missed something in the code.


LASTCMD which worked, but it had, according to MediaInfo, a max bitrate of 40000. 40000 I can live with that.
"C:\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "G:\BDRB_WORK\IMPORTS\UNCUT_GEMS\BDMV\STREAM\00000.m2ts" --codec h264 --preset quality --bluray --vbr 0 --vbr-quality 20 --aq-temporal --keyfile "G:\BDRB_WORK\WORKFILES\VID_00000.CHP" --aud --pic-struct --vbv-bufsize 50000 --max-bitrate 50000 --gop-len 24 -o "G:\BDRB_WORK\WORKFILES\VID_00000.AVS.264"

LASTCMD which did not work. I think there is something wrong with this one. Twice vbv-bufsize (15000 and 50000) and twice max-rate (15000 and 50000)
"C:\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "G:\BDRB_WORK\IMPORTS\UNCUT_GEMS\BDMV\STREAM\00000.m2ts" --codec h264 --preset quality --bluray --vbr 0 --vbr-quality 20 --aq-temporal --keyfile "G:\BDRB_WORK\WORKFILES\VID_00000.CHP" --aud --pic-struct --vbv-bufsize 15000 --max-bitrate 15000 --gop-len 48 --vbv-maxrate 50000 --vbv-bufsize 50000 -o "G:\BDRB_WORK\WORKFILES\VID_00000.AVS.264"

My conclusion: do not add "TWEAK_ALTERNATE_NV=--vbv-maxrate 50000 --vbv-bufsize 50000" in the BDREBUILDER.INI. Add "mBitrate=50000" in the ALTERNATE.TXT
Am I correct?

[gonca]

Can the 40 Mbs be caused by --vbr-quality 20

[jdobbs]

Can the 40 Mbs be caused by --vbr-quality 20I guess its possible -- but I can't imagine why.

[Sharc]

LASTCMD which worked, but it had, according to MediaInfo, a max bitrate of 40000. 40000 I can live with that.
"C:\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "G:\BDRB_WORK\IMPORTS\UNCUT_GEMS\BDMV\STREAM\00000.m2ts" --codec h264 --preset quality --bluray --vbr 0 --vbr-quality 20 --aq-temporal --keyfile "G:\BDRB_WORK\WORKFILES\VID_00000.CHP" --aud --pic-struct --vbv-bufsize 50000 --max-bitrate 50000 --gop-len 24 -o "G:\BDRB_WORK\WORKFILES\VID_00000.AVS.264"

LASTCMD which did not work. I think there is something wrong with this one. Twice vbv-bufsize (15000 and 50000) and twice max-rate (15000 and 50000)
"C:\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "G:\BDRB_WORK\IMPORTS\UNCUT_GEMS\BDMV\STREAM\00000.m2ts" --codec h264 --preset quality --bluray --vbr 0 --vbr-quality 20 --aq-temporal --keyfile "G:\BDRB_WORK\WORKFILES\VID_00000.CHP" --aud --pic-struct --vbv-bufsize 15000 --max-bitrate 15000 --gop-len 48 --vbv-maxrate 50000 --vbv-bufsize 50000 -o "G:\BDRB_WORK\WORKFILES\VID_00000.AVS.264"

My conclusion: do not add "TWEAK_ALTERNATE_NV=--vbv-maxrate 50000 --vbv-bufsize 50000" in the BDREBUILDER.INI. Add "mBitrate=50000" in the ALTERNATE.TXT
Am I correct?
Unlike x264, NVEncC doesn't support '--vbv-maxrate' as I understand.
It's '--max-bitrate' only for NVEncC.

One should however not have to worry about the duplication of parameters. The last ones just overrule the former ones AFAIK.

[jdobbs]

Unlike x264, NVEncC doesn't support '--vbv-maxrate' as I understand.
It's '--max-bitrate' only for NVEncC.

One should however not have to worry about the duplication of parameters. The last ones just overrule the former ones AFAIK.Wow. Good catch. When I read that post I missed that completely. That's the reason his "TWEAK_ALTERNATE_NV" settings didn't take hold (and probably why the command line failed).

[Glarioo]

Can the 40 Mbs be caused by --vbr-quality 20

Did it with CRF 18 now. Same result. max bitrate of 40000
mBitrate=50000 in de alterternate.txt file.
No TWEAK_ALTERNATE_NV in the BDREBUILDER.ini file.

LASTCMD.TEXT: "C:\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "G:\BDRB_WORK\IMPORTS\UNCUT_GEMS\BDMV\STREAM\00000.m2ts" --codec h264 --preset quality --bluray --vbr 0 --vbr-quality 18 --aq-temporal --keyfile "G:\BDRB_WORK\WORKFILES\VID_00000.CHP" --aud --pic-struct --vbv-bufsize 50000 --max-bitrate 50000 --gop-len 24 -o "G:\BDRB_WORK\WORKFILES\VID_00000.AVS.264"

[Glarioo]

Still no max bitrate 50000.
CRF 18
mBitrate=50000 in de alterternate.txt file.
Add TWEAK_ALTERNATE_NV=--max-bitrate 50000 --vbv-bufsize 50000 in the BDREBUILDER.ini file.

LASTCMD.TEXT: "C:\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "G:\BDRB_WORK\IMPORTS\UNCUT_GEMS\BDMV\STREAM\00000.m2ts" --codec h264 --preset quality --bluray --vbr 0 --vbr-quality 18 --aq-temporal --keyfile "G:\BDRB_WORK\WORKFILES\VID_00000.CHP" --aud --pic-struct --vbv-bufsize 50000 --max-bitrate 50000 --gop-len 24 --max-bitrate 50000 --vbv-bufsize 50000 -o "G:\BDRB_WORK\WORKFILES\VID_00000.AVS.264"

[jdobbs]

Did it with CRF 18 now. Same result. max bitrate of 40000
mBitrate=50000 in de alterternate.txt file.
No TWEAK_ALTERNATE_NV in the BDREBUILDER.ini file.

LASTCMD.TEXT: "C:\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "G:\BDRB_WORK\IMPORTS\UNCUT_GEMS\BDMV\STREAM\00000.m2ts" --codec h264 --preset quality --bluray --vbr 0 --vbr-quality 18 --aq-temporal --keyfile "G:\BDRB_WORK\WORKFILES\VID_00000.CHP" --aud --pic-struct --vbv-bufsize 50000 --max-bitrate 50000 --gop-len 24 -o "G:\BDRB_WORK\WORKFILES\VID_00000.AVS.264"It has to be a limitation of NVENCC... but I haven't seen it documented anywhere.

[Sharc]

It has to be a limitation of NVENCC... but I haven't seen it documented anywhere.
Could these 40000 kbps be due to '--bluray' in the commandline?

[jdobbs]

Could these 40000 kbps be due to '--bluray' in the commandline?You're probably right. It makes complete sense since the maximum video bitrate for bluray (HD) actually is 40Mbs, with the combined audio/video being 48Mbs. I would have thought, though, that a later command line callout would override it.

[Glarioo]

You're probably right. It makes complete sense since the maximum video bitrate for bluray (HD) actually is 40Mbs, with the combined audio/video being 48Mbs. I would have thought, though, that a later command line callout would override it, though.

Did a test with CloneBD and it also had a max bitrate of 40 Mbs.
So jdobbs, no worries, 40000 is okay for me.

[Finch]

Not sure if this qualifies as a bug but in newer versions of Windows 10 there is a setting called "Use Unicode UTF-8 for worldwide language support" (it's in Control Panel -> Region -> Change system locale). When it is enabled BDRB gives a "2501 Source Check() 00009 2501" and "Select Source is not BD format" errors when opening a BD source.

[jdobbs]

Not sure if this qualifies as a bug but in newer versions of Windows 10 there is a setting called "Use Unicode UTF-8 for worldwide language support" (it's in Control Panel -> Region -> Change system locale). When it is enabled BDRB gives a "2501 Source Check() 00009 2501" and "Select Source is not BD format" errors when opening a BD source.On my system it says that setting is in beta status. My guess (hope?) is that it will be fixed at some point before going final.

In the meantime I will look at that error, try to repeat it, and see if I can track down why it is happening.

[abogard]

Hello everyone. I'm completely new here. First of all many thanks to jdobbs for a wonderful piece of software, you're the best. Now then, I think I've read a lot of the thread and I'm not sure if what I'm going to report has been reported already but here goes. Yesterday I tried to encode a BD from BD50 to BD25 with Nvenc and it so happens that this BD had secondary video. Nvenc couldn't deal with that. The original .264 file for the secondary video was 9 Mb and the resulting file was 2 Gb, more importantly the bitrate for the main video was drastically reduced because of it.

I don't know if I'm making myself clear, english is not my native language so please bear with me, if you need anymore details I'll be happy to provide them if I can.

Thanks again

[ggtop]

.... if you need anymore details I'll be happy to provide them if I can.

More details would be nice indeed. If you want help you should give much as possible information to understand and (maybe even) reproduce the issue you have.
The full processing log (look into the WORKING folder) would be a good starting point.

BTW Sure you have a 9 MB secondary video? Sounds short :-) There is no (Blu-Ray) compatible bitrate that could inflate it into a 2 GB file... Mediainfo report of that file / playlist could be helpful as well.

ggtop

[abogard]

More details would be nice indeed. If you want help you should give much as possible information to understand and (maybe even) reproduce the issue you have.
The full processing log (look into the WORKING folder) would be a good starting point.

BTW Sure you have a 9 MB secondary video? Sounds short :-) There is no (Blu-Ray) compatible bitrate that could inflate it into a 2 GB file... Mediainfo report of that file / playlist could be helpful as well.

ggtop

Of course I understand and you're right, but before I go and do all that (which I'm more than happy to do) I would first like to ask:

Has anybody here encoded a BD, with secondary video, with nvenc, without any problems?

And yes, it was very strange to me too to see a file so big come out of something so small but it happened so I'm a believer now.

[abogard]

I decided to try and get the info needed to illustrate my problem, it wasn't as hard as I thought it would be. Here it is.

First, the BD-RB log, I stopped it of course because it's pointless to let it finish. Of interest here is to look at the encoding bitrate for the file VID_0045 after the secondary video is encoded:

----------------------
[10/29/20] BD Rebuilder v0.61.18
[17:32:10] Source: TRUE.DETECTIVE.S01.DISC2
- Input BD size: 43,12 GB
- Approximate total content: [03:20:26.464]
- Target BD size: 23,44 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Very Good (Very Fast), ABR
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[17:32:10] PHASE ONE, Encoding
- [17:32:10] Processing: VID_00017 (1 of 11)
- [17:32:10] Extracting A/V streams [VID_00017]
- [17:32:17] Reencoding video [VID_00017]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 336 frames
- Bitrate: 1 894 Kbs
- [17:32:17] Reencoding: VID_00017, Pass 1 of 1
- [17:32:23] Video Encode complete
- [17:32:23] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:32:23] Multiplexing M2TS
- [17:32:27] Processing: VID_00018 (2 of 11)
- [17:32:27] Extracting A/V streams [VID_00018]
- [17:32:34] Reencoding video [VID_00018]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 5 876 frames
- Bitrate: 1 952 Kbs
- [17:32:34] Reencoding: VID_00018, Pass 1 of 1
- [17:32:49] Video Encode complete
- [17:32:49] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:32:49] Multiplexing M2TS
- [17:32:53] Processing: VID_00045 (3 of 11)
- [17:32:53] Extracting A/V streams [VID_00045]
- [17:38:01] Reencoding video [VID_00045]
- [17:38:01] Reencoding secondary video [TRK_02]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 82 090 frames
- Bitrate: 7 936 Kbs
- [17:41:36] Reencoding: VID_00045, Pass 1 of 1


Next is the mediainfo of the secondary video file in its original form:

General
Complete name : D:\temp\WORKFILES\00045.track_6912.264
Format : AVC
Format/Info : Advanced Video Codec
File size : 9.08 MiB
Overall bit rate mode : Constant

Video
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L3.2
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference fra : 4 frames
Format settings, GOP : M=3, N=12
Bit rate mode : Constant
Bit rate : 1 000 kb/s
Width : 720 pixels
Height : 480 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
Bits/(Pixel*Frame) : 0.121



As you can see it's 9 Mb in size. Next the resulting file after encoding:

General
Complete name : D:\temp\WORKFILES\VID_00045_2.AVS.264
Format : AVC
Format/Info : Advanced Video Codec
File size : 2.34 GiB
Overall bit rate mode : Variable

Video
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings : CABAC / 3 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference fra : 3 frames
Format settings, GOP : M=4, N=24
Bit rate mode : Variable
Maximum bit rate : 7 000 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 2.2:1
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive



As you can see, 2.3 Gb in size. And here I noticed something very strange, as I played both files the original file is like a black screen, I don't know its purpose but it's not the traditional secondary video where you can see interviews and whatnot, must be some stupid uninteresting thing, but the fact remains that is there. When I play the encoded video I can see the movie playing but with like a different aspect ratio, as a matter of fact the original is 720x480 and the encoded is 1920x1080, it's very strange. One could say that this is a problematic title if it wasn't for the fact that x264 has no problems with the encode. I'll show right away.

First the BD-RB log, notice the encoding bitrate for the file VID_0045 this time around, it's practically doubled:


[10/29/20] BD Rebuilder v0.61.18
[17:55:53] Source: TRUE.DETECTIVE.S01.DISC2
- Input BD size: 43,12 GB
- Approximate total content: [03:20:26.464]
- Target BD size: 23,44 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Very Good (Very Fast), ABR
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[17:55:56] PHASE ONE, Encoding
- [17:55:56] Processing: VID_00017 (1 of 11)
- [17:55:56] Extracting A/V streams [VID_00017]
- [17:56:01] Reencoding video [VID_00017]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 336 frames
- Bitrate: 1 894 Kbs
- [17:56:01] Reencoding: VID_00017, Pass 1 of 1
- [17:56:03] Video Encode complete
- [17:56:03] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:56:03] Multiplexing M2TS
- [17:56:07] Processing: VID_00018 (2 of 11)
- [17:56:07] Extracting A/V streams [VID_00018]
- [17:56:13] Reencoding video [VID_00018]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 5 876 frames
- Bitrate: 1 952 Kbs
- [17:56:13] Reencoding: VID_00018, Pass 1 of 1
- [17:56:42] Video Encode complete
- [17:56:42] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:56:42] Multiplexing M2TS
- [17:56:47] Processing: VID_00045 (3 of 11)
- [17:56:47] Extracting A/V streams [VID_00045]
- [17:58:48] Reencoding video [VID_00045]
- [17:58:48] Reencoding secondary video [TRK_02]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 82 090 frames
- Bitrate: 13 651 Kbs
- [18:00:18] Reencoding: VID_00045, Pass 1 of 1


Now the mediainfo for the resulting file this time around:

General
Complete name : D:\temp\WORKFILES\VID_00045_2.AVS.264
Format : AVC
Format/Info : Advanced Video Codec
File size : 3.33 MiB
Overall bit rate mode : Variable
Writing library : x264 core 158 r2984 3759fcb
Encoding settings : cabac=1 / ref=1 / deblock=0:0:0 / analyse=0:0 / me=dia / subme=0 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=0 / me_range=16 / chroma_me=1 / trellis=0 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=0 / threads=6 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=0 / b_adapt=0 / b_bias=0 / direct=1 / weightb=0 / open_gop=0 / weightp=0 / keyint=24 / keyint_min=1 / scenecut=0 / intra_refresh=0 / rc_lookahead=0 / rc=crf / mbtree=0 / crf=25.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=7000 / vbv_bufsize=12000 / crf_max=0.0 / nal_hrd=vbr / filler=0 / ip_ratio=1.10 / pb_ratio=1.10 / aq=0

Video
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L3.2
Format settings : CABAC / 2 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference fra : 2 frames
Format settings, GOP : M=4, N=24
Bit rate mode : Variable
Maximum bit rate : 7 000 kb/s
Width : 720 pixels
Height : 480 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
Writing library : x264 core 158 r2984 3759fcb
Encoding settings : cabac=1 / ref=1 / deblock=0:0:0 / analyse=0:0 / me=dia / subme=0 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=0 / me_range=16 / chroma_me=1 / trellis=0 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=0 / threads=6 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=0 / b_adapt=0 / b_bias=0 / direct=1 / weightb=0 / open_gop=0 / weightp=0 / keyint=24 / keyint_min=1 / scenecut=0 / intra_refresh=0 / rc_lookahead=0 / rc=crf / mbtree=0 / crf=25.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=7000 / vbv_bufsize=12000 / crf_max=0.0 / nal_hrd=vbr / filler=0 / ip_ratio=1.10 / pb_ratio=1.10 / aq=0



As you can see, 3.3 Mb in size and it's displaying a black screen like the original and it's 720x480 like the original.

To me it seems like a problem with the encoder, not the file itself, but these are my two cents, I hope it helps and if there really is a problem that it can be solved. I appreciate the help.

[abogard]

Well, I made a long post documenting my findings but I guess it was too long or something because the moderator didn't see fit to publish it, so I wasted my time there. Instead I'm going to try and document an interesting finding. It seems the problem lies in the command line. While doing the encode I went to the LASTCMD.TXT file and found this:

"D:\1\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "E:\TRUE.DETECTIVE.S01.DISC2\BDMV\STREAM\00045.m2ts" --codec h264 --preset performance --bluray --qp-min 0 --multipass 2pass-full --vbr 0 --vbr-quality 25 --aq-temporal --sar 40:33 --aud --pic-struct --vbv-bufsize 12000 --max-bitrate 7000 --gop-len 24 -o "D:\TEMP\WORKFILES\VID_00045_2.AVS.264"


In other words, it's encoding the wrong file. It's supposed to be encoding the file 00045.track_6912.264 and instead it's being directed to the .m2ts without any indication to the secondary video except in the end. So what happens is that the software encodes the main movie only with a different set of commands, that explains the file size. I'm not the expert here but maybe there's the problem.

[Mike-uk]

Well, I made a long post documenting my findings but I guess it was too long or something because the moderator didn't see fit to publish it,.

posts are not moderated ( upon posting) (but afterwards yes) , try again, tip if your writing large amounts, either copy your txt before you submit so if it goes wrong you can paste your work or compose it in notepad

also if your posting long bits of log and data you need to wrap them in "code" to encase it in a smaller window thats scrollable

[abogard]

posts are not moderated ( upon posting) (but afterwards yes) , try again, tip if your writing large amounts, either copy your txt before you submit so if it goes wrong you can paste your work or compose it in notepad

also if your posting long bits of log and data you need to wrap them in "code" to encase it in a smaller window thats scrollable

Yes, I did all that. And as a matter of fact I have it in a txt just in case, but I'm mentioning a moderator because when I posted it I got a message saying that the post would be reviewed by a moderator beforehand and that I would not be able to view it right away, which stroke me as funny but like I said I'm new here. As time has passed already I am led to believe it's not going to be posted

[MrVideo]

A lot of forums limit posts by new users, in that a moderator needs to review them. Then, after a certain number of posts, moderation is no longer done.

[CV91913]

Yes, I did all that. And as a matter of fact I have it in a txt just in case, but I'm mentioning a moderator because when I posted it I got a message saying that the post would be reviewed by a moderator beforehand and that I would not be able to view it right away, which stroke me as funny but like I said I'm new here. As time has passed already I am led to believe it's not going to be posted

Looking at the code snippet you posted, the file name in the path does not look like a BD. Is the source from a BD50 disk or a download?

[abogard]

Looking at the code snippet you posted, the file name in the path does not look like a BD. Is the source from a BD50 disk or a download?

It's from a BD50 disk. I ripped everything to the HDD to do the backup

[Ch3vr0n]

It's from a BD50 disk. I ripped everything to the HDD to do the backup

I find that extremely doubtful. No retail disc ever uses a volume name such as "TRUE.DETECTIVE.S01.DISC2". That is a naming scheme typically used with "the warez scene" and illegal downloads.

[abogard]

I find that extremely doubtful. No retail disc ever uses a volume name such as "TRUE.DETECTIVE.S01.DISC2". That is a naming scheme typically used with "the warez scene" and illegal downloads.

Let me see if I understand. So I come in here reporting a problem with the software and I all I get is somebody calling me a liar. What do you know about me, who are you anyway? I doubt you're the authority here and you're already making assumptions. And let's not even go to your superior intellect saying that your clue is indisputable. So if the naming of the folder is not to your liking that means it's an illegal download, wow, you must be the top detective in your town. And let's also not go as to how you know that's a "typically used" scheme, it seems to me you're the one visiting the "warez scene".

The nerve of some people. For your information I name all my rips in the same manner whether you like it or not. If you're not gonna help or won't gonna help, or worst of all can't help then spare me your comments.

And yes, I'm upset because you have no right to be making assumptions about me. At least show some sign that you have a clue about the problem, all you have done is question me without even trying to help so what's the deal here?

Anyway it doesn't matter. It's obvious that this is not a support forum but more like a fan club, only members of the "gang" get help here with their questions. It's been days and not a soul has a clue as to the problem, or even worse they're saying nothing because I'm not in the "circle". If the source has secondary video I'll just use x264 and problem solved. Have a good day.

[Ch3vr0n]

Regarding the "visiting", ever heard of the torrentfreak new site? Nobody here is explicitly saying you're lying, or anything like it. All we're saying is that (based on multiple other posters here) everyone that used a source rip named like that as a volume label, every single one of them had problems. Every single one of them used a pirated rip, which in turn had been pre-processed by other tools (non-bdrb) which then cause problems for processing with bdrb.

And no, i havent done anything but question you. The other guy was CV91913, that guy aint me.

[AmigaFuture]

I have helped friends who've donated to BD-RB through me that don't trust online...and hope I won't get fraud, and I showed them my naming scheme. I've also watched / helped them decide how to handle seasonal discs. Many discs have wonky names, but not once I saw yours, or others that come here with that filename with the periods between. I use a different method so I can see differences right away when I look later between processed and original, and tests processes. So...it does LOOK a bit suspect. You're also coming across really heated and that's usually a sign of distraction away from what the caught person is doing. I've come across that many times in my life, with different people and situations and almost always that's what's happening. In magic it's called distraction away from what's happening...so the illusion can be preformed. Does pretty well with living energy, but not so well in text with people whom are good at context & comprehension. As someone we know types, IF the truth doesn't do it...[attempt to] dazzle them with B.S.. Haha!

[videoh]

I doubt you're [Ch3vr0n] the authority here While not the authority (as if there is one), Ch3vr0n is definitely a respected authority here, with a long history of valuable contributions to the forum. You could hope to do as well...if you lose the entitled attitude.

[jdobbs]

Well, I made a long post documenting my findings but I guess it was too long or something because the moderator didn't see fit to publish it, so I wasted my time there. Instead I'm going to try and document an interesting finding. It seems the problem lies in the command line. While doing the encode I went to the LASTCMD.TXT file and found this:



In other words, it's encoding the wrong file. It's supposed to be encoding the file 00045.track_6912.264 and instead it's being directed to the .m2ts without any indication to the secondary video except in the end. So what happens is that the software encodes the main movie only with a different set of commands, that explains the file size. I'm not the expert here but maybe there's the problem.I'll take a look at the code and see if I can figure out why it is selecting the wrong track.

[varekai]

@abogard
I'm not moralizing but your indignation is tiresome... :|
Proper BD title
True Detective Season 1 Disc 2 (3 Episodes)
[TRUE_DETECTIVE_DISC2]

[RoyGBiv-inRI]

Can someone help with a re encode speed issue? I have a computer that's about two years old with an Intel i5 7600K CPU with 4 cores. Recently I did a clean re install of Win10, and for some reason video encoding is now much slower. Prior to the re install, the video recode speed would be at about 0.95 or so, and the recode would take about the length of the movie. For reasons I don't understand, I am now getting recode speed about 0.6. I have not changed any settings in BD RB or in any of the supporting programs. Using CPUID HWMonitor I can see that all four cores are being utilized to between 95-100%. I don't imagine there would be any throttling, as the core tests are in the mid 60's C.

Here is my BD Rebuilder INI file if that helps:

[Options]
VERSION=0.61.0.18
ENCODER=0
MODE=3
ENCODE_QUALITY=2
ONEPASS_ENCODING=2
AUTO_QUALITY=0
TARGET_SIZE=23500
AUTO_BURN=2
PRIORITY_CLASS=0
[Paths]
SOURCE_PATH=G:\*********\
WORKING_PATH=G:\*********\NEW FOLDER\

Thanks for any help.

Your Obedient Servant
SMK

[jdobbs]

I'll Well, I made a long post documenting my findings but I guess it was too long or something because the moderator didn't see fit to publish it, so I wasted my time there. Instead I'm going to try and document an interesting finding. It seems the problem lies in the command line. While doing the encode I went to the LASTCMD.TXT file and found this:



In other words, it's encoding the wrong file. It's supposed to be encoding the file 00045.track_6912.264 and instead it's being directed to the .m2ts without any indication to the secondary video except in the end. So what happens is that the software encodes the main movie only with a different set of commands, that explains the file size. I'm not the expert here but maybe there's the problem.I'll take a look at the code and see if I can figure out why it is selecting the wrong track.I just looked at the code... and yes, there is a bug when reencoding using NVENCC on secondary video tracks. It's related to BD-RBs preference to use NVIDIA's internal hardware decoding (rather than an AVS) when possible. It failed to account for secondary video. I'll fix it for the next release.

[abogard]

I just looked at the code... and yes, there is a bug when reencoding using NVENCC on secondary video tracks. It's related to BD-RBs preference to use NVIDIA's internal hardware decoding (rather than an AVS) when possible. It failed to account for secondary video. I'll fix it for the next release.

Thank you very much, I really appreciate it. As I said before, you're the man.

[LowDead]

Yes, of course. According to your commandline (marked red) you encoded it with a CQM of 20 rather than about 23 as before. Hence the bitrate increased from about 4000 to 7000kbps.
And you shouldn't worry much about the --multipass 2pass-full. Slower presets include it silently and it is actually no longer needed explicitly. If it is still there it does no harm though. It's a legacy. Maybe you should update your NVIDIA drivers.

Edit: And btw. your "Not working" was a bitrate (--vbr 1105) rather than a quality based (--vbr 0 --vbr-quality 20) encode.

Sorry for the super late answer. I have been very busy. But I did get some tests done. Unfortunately no positive results. I was tinkering with NVencC encoding parameters and manually inserted the encoded file to see if I got any results, and while I did get a somewhat clearer picture the artifacts was still there.

And yes I double checked the Nvidia drivers were up to date. There's also new drivers out now but there's no difference with them.

On another note I have tried the disc on both DVDFab and CloneBD and both is working for me without pixelation, so something different is done there in the process.

@jdobbs btw.. NVEncC 5.19 is out with a bugfix related to --repeat-headers

//LD

[AmigaFuture]

JDobbs, I haven't noticed any speedups with NVECNCC but the my board is a GeForce GTX so I don't expect it to be fast as your "WOW!!!" was after getting your new board. :) However, I also notice MULTIPROCESS still is still disabled. Not a big deal as the older BD-RB functions well for that.

[Max1984]

jdobbs,

i m try to encoding (Back.to.the.Future.Part.II.1989.2160P.UHD.FULL DISC ) BD25 to. getting some error! how to fix it, plzz help, THANX.

Error :

https://imgur.com/rA6EsDK