BD Rebuilder Beta - Bug Reports Only

[musiclover]

That's really weird. I can't repeat that. I changed the code so I can set to one or the other (regardless of whether the GPU exists) and the correct command line is generated.

After some more testing I come to the conclusion that switching from GPU after a job leads to GPUENCC using the previous GPU or giving an error message. For the right outcome after switching from GPU I have to restart GPUENCC and then all works well.

[jdobbs]

After some more testing I come to the conclusion that switching from GPU after a job leads to GPUENCC using the previous GPU or giving an error message. For the right outcome after switching from GPU I have to restart GPUENCC and then all works well.I found some issues with switching from one to the other as well. A couple of settings that are meant for NVIDIA weren't being reset when I reselected the INTEL option a second time. I've fixed it and will create a new release soon. I'm going to do some more testing before I do.

[jdobbs]

After some more testing I come to the conclusion that switching from GPU after a job leads to GPUENCC using the previous GPU or giving an error message. For the right outcome after switching from GPU I have to restart GPUENCC and then all works well.Could you try replacing GPUENCC.exe with the one in this zip file (https://jammernhilftnichts.de/jdobbs/GPUENCC0114.zip) and see if it fixes your issue?

[musiclover]

Could you try replacing GPUENCC.exe with the one in this zip file (https://jammernhilftnichts.de/jdobbs/GPUENCC0114.zip) and see if it fixes your issue?

With this version NVIDIA GPU is working fine, but INTEL GPU is not completing the jobs. It failed mostly before 10% of the job was done. The longest it worked was 70% of the job. Even restarting the program had no effect.


[06.24.24] GPU Reencoder v0.01.14
----------------------
[22.26.39]Start Job [1 of 1]
- Reencoding "House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"
-- Using NVIDIA GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x960, 23.976fps
-- Vid: H264 (AVC), 1280x720, Keep fps, CQ 20
-- Aud: Intact (Keep Original), no reencode
-- Remuxing output with MKVMERGE
[22.30.11]Job Completed [1 of 1]
----------------------
[06.24.24] GPU Reencoder v0.01.14
----------------------
[22.30.51]Start Job [1 of 1]
- Reencoding "House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"
-- Using INTEL GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x960, 23.976fps
-- Vid: H264 (AVC), 1280x720, Keep fps, CQ 20
-- Aud: Intact (Keep Original), no reencode
- ERROR -- Encode failed. Job aborted.

"C:\BD Rebuilder\BD_Rebuilder\tools\qsvenc\qsvencc.exe" --avhw --output-res 1280x720 -i "E:\House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv" --codec h264 --quality balanced --colorprim bt709 --transfer bt709 --colormatrix bt709 --qp-min 0 --icq 20 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 --audio-copy 1 --sub-source "E:\House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.srt" --sub-copy 17,1,2 --chapter-copy -o "D:\WORK\House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"

[jdobbs]

With this version NVIDIA GPU is working fine, but INTEL GPU is not completing the jobs. It failed mostly before 10% of the job was done. The longest it worked was 70% of the job. Even restarting the program had no effect.


[06.24.24] GPU Reencoder v0.01.14
----------------------
[22.26.39]Start Job [1 of 1]
- Reencoding "House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"
-- Using NVIDIA GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x960, 23.976fps
-- Vid: H264 (AVC), 1280x720, Keep fps, CQ 20
-- Aud: Intact (Keep Original), no reencode
-- Remuxing output with MKVMERGE
[22.30.11]Job Completed [1 of 1]
----------------------
[06.24.24] GPU Reencoder v0.01.14
----------------------
[22.30.51]Start Job [1 of 1]
- Reencoding "House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"
-- Using INTEL GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x960, 23.976fps
-- Vid: H264 (AVC), 1280x720, Keep fps, CQ 20
-- Aud: Intact (Keep Original), no reencode
- ERROR -- Encode failed. Job aborted.

"C:\BD Rebuilder\BD_Rebuilder\tools\qsvenc\qsvencc.exe" --avhw --output-res 1280x720 -i "E:\House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv" --codec h264 --quality balanced --colorprim bt709 --transfer bt709 --colormatrix bt709 --qp-min 0 --icq 20 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 --audio-copy 1 --sub-source "E:\House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.srt" --sub-copy 17,1,2 --chapter-copy -o "D:\WORK\House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"Thanks for the feedback. Can you run the command from a COMMAND prompt and see what error you are getting? I haven't had any problems with encoding...

I do see a possible unrelated issue, though. The input isn't 16:9, but the resizing is outputting it to 1280x720 with no padding. That's probably true on both encodes.

The previous version succeeded in encoding (but having to restart it)?

[jellyhead1]

The resizing error was in BD Rebuilder, or GPUENCCE? Can you post the command line that was used for the encode?

This was encoding to alternate output "MKV Container, 1920x1080, 640kbs DD5.1" which is what I normally use. I was using NVEnc or software before upgrading to an i9-10900K without experiencing this. I have encoded many videos using the software encoder and i9 with v0.61.29 without an issue.

LASTCMD.TXT:
"C:\Video Editing\BDRebuilder\tools\qsvenc\qsvencc.exe" --avs -i "G:\VIDEO RECORDING\MOVIES\HD\BLU-RAY\BDREBUILDER\WORKFILES\TEMP.AVS" --quality balanced --qp-min 0 --icq 17 --sar 1:1 --aud --pic-struct --vbv-bufsize 30000 --max-bitrate 35000 --no-b-adapt --gop-len 24 -o "G:\VIDEO RECORDING\MOVIES\HD\BLU-RAY\BDREBUILDER\WORKFILES\TEMP.264"

I don't see a "GPULASTCMD.TXT", just the usual "BD-REBUILDER.LOG" and "MOVIE_NAME.inf"

This is the MOVIE_NAME.inf:
[Status]
LABEL=MOVIE_NAME
VERSION=v0.62.02
SOURCE_SIZE=8568563712
SOURCE_VIDEO_SIZE=8568563712
TARGET_SIZE=24641536000
REDUCTION=2.87580705801257
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=eng;
BACKUP_MODE=1
MOVIEONLY_TYPE=10
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=1
REBUILD_COMPLETE=1
[00000]
AUDIO=1
PGS=1000
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=24641536000
NSIZE=0
FLINK=0
MLINK=0

This is the BD-REBUILDER.LOG:
[06/24/24] BD Rebuilder v0.62.02
[19:12:07] Source: MOVIE_NAME_00000
- Input BD size: 7.98 GB
- Approximate total content: [02:28:11.757]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1920x1080, 640Kbs DD5.1
- Quality: High Quality (Default)
- Decoding/Frame serving: QSVENCC
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[19:12:11] PHASE ONE, Encoding
- [19:12:11] Processing: VID_00000 (1 of 1)
- [19:12:11] Extracting A/V streams [VID_00000]
- [19:12:31] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 213,189 frames
- [19:12:31] Reencoding: VID_00000, Pass 1 of 1
- Analyzing 17.00 19.00 [19.00]
- [19:33:55] Video Encode complete
- [19:33:55] Processing audio tracks
- Track 4352 (eng): Keeping original audio
[19:33:57]PHASE ONE complete
[19:33:57]PHASE TWO - Rebuild Started
- [19:33:57] Building ALTERNATE OUTPUT Structure
[19:34:34] - Encode and Rebuild complete
- WORKFILES folder removed.
[19:34:35] JOB: MOVIE_NAME finished.

[musiclover]

Thanks for the feedback. Can you run the command from a COMMAND prompt and see what error you are getting? I haven't had any problems with encoding...

I do see a possible unrelated issue, though. The input isn't 16:9, but the resizing is outputting it to 1280x720 with no padding. That's probably true on both encodes.

The previous version succeeded in encoding (but having to restart it)?

A strange thing happened today. After starting my computer this morning GPUENCC v0.01.14 worked perfectly. No problems with changing the GPU's. I wonder what happened yesterday though. There was certainly something wrong going on but I cannot make that happen today although I performed the same job. I hate it when that happens. Don't you?

----------------------
[06.25.24] GPU Reencoder v0.01.14
----------------------
[09.29.34]Start Job [1 of 1]
- Reencoding "House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"
-- Using INTEL GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x960, 23.976fps
-- Vid: H264 (AVC), 1280x720, Keep fps, CQ 20
-- Aud: Intact (Keep Original), no reencode
-- Remuxing output with MKVMERGE
[09.35.48]Job Completed [1 of 1]
----------------------
[06.25.24] GPU Reencoder v0.01.14
----------------------
[09.47.10]Start Job [1 of 1]
- Reencoding "House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"
-- Using NVIDIA GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x960, 23.976fps
-- Vid: H264 (AVC), 1280x720, Keep fps, CQ 20
-- Aud: Intact (Keep Original), no reencode
-- Remuxing output with MKVMERGE
[09.50.55]Job Completed [1 of 1]
----------------------
[06.25.24] GPU Reencoder v0.01.14
----------------------
[09.54.36]Start Job [1 of 1]
- Reencoding "House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"
-- Using INTEL GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x960, 23.976fps
-- Vid: H264 (AVC), 1280x720, Keep fps, CQ 20
-- Aud: Intact (Keep Original), no reencode
-- Remuxing output with MKVMERGE
[10.00.52]Job Completed [1 of 1]
----------------------
[06.25.24] GPU Reencoder v0.01.14
----------------------
[10.03.11]Start Job [1 of 1]
- Reencoding "House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"
-- Using NVIDIA GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x960, 23.976fps
-- Vid: H264 (AVC), 1280x720, Keep fps, CQ 20
-- Aud: Intact (Keep Original), no reencode
-- Remuxing output with MKVMERGE
[10.06.59]Job Completed [1 of 1]
----------------------
[06.25.24] GPU Reencoder v0.01.14
----------------------
[10.18.26]Start Job [1 of 1]
- Reencoding "House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"
-- Using INTEL GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x960, 23.976fps
-- Vid: H264 (AVC), 1280x720, Keep fps, CQ 20
-- Aud: Intact (Keep Original), no reencode
-- Remuxing output with MKVMERGE
[10.25.51]Job Completed [1 of 1]

As you can see the NVIDIA GPU is quicker handling the job but the INTEL GPU has a much better size ratio. But the difference is huge. I don't trust it.
The size of the source file was 5.005.060 kb. NVIDIA GPU made that 3.254.475 kb and INTEL GPU came to 1.151.442 kb.
The padding is an issue with both GPU's.

[musiclover]

Tonight I tried again with the same job with both GPU's. Both jobs completed OK. But.... I didn't change a thing in the settings and still the outcome was different from this morning. The end size of the NVIDIA GPU job was 2.180.806 kb and that of the INTEL GPU job was 901.306 kb. It struck me to see that though I set the highest constant quality this morning and also tonight at CQ23 GPUENCC used this morning constantly CQ20 but tonight it used CQ23.

----------------------
[06.25.24] GPU Reencoder v0.01.14
----------------------
[20.23.25]Start Job [1 of 1]
- Reencoding "House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"
-- Using NVIDIA GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x960, 23.976fps
-- Vid: H264 (AVC), 1280x720, Keep fps, CQ 23
-- Aud: Intact (Keep Original), no reencode
-- Remuxing output with MKVMERGE
[20.26.56]Job Completed [1 of 1]
----------------------
[06.25.24] GPU Reencoder v0.01.14
----------------------
[20.28.07]Start Job [1 of 1]
- Reencoding "House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"
-- Using INTEL GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x960, 23.976fps
-- Vid: H264 (AVC), 1280x720, Keep fps, CQ 23
-- Aud: Intact (Keep Original), no reencode
-- Remuxing output with MKVMERGE
[20.35.31]Job Completed [1 of 1]

Last command of this morning
"C:\BD Rebuilder\BD_Rebuilder\tools\qsvenc\qsvencc.exe" --avhw --output-res 1280x720 -i "E:\House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv" --codec h264 --quality balanced --colorprim bt709 --transfer bt709 --colormatrix bt709 --qp-min 0 --icq 20 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 --audio-copy 1 --sub-source "E:\House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.srt" --sub-copy 17,1,2 --chapter-copy -o "D:\WORK\House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"

Last command of tonight
"C:\BD Rebuilder\BD_Rebuilder\tools\qsvenc\qsvencc.exe" --avhw --output-res 1280x720 -i "E:\House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv" --codec h264 --quality balanced --colorprim bt709 --transfer bt709 --colormatrix bt709 --qp-min 0 --icq 23 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 --audio-copy 1 --sub-source "E:\House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.srt" --sub-copy 17,1,2 --chapter-copy -o "D:\WORK\House.of.the.Dragon.S02E02.1080p.REPACK.AMZN.WEB-DL.DDP5.1.H.264-NTb.mkv"

I hope you can get to the bottom of this.

[jdobbs]

So you're saying it changed to CQ23 on its own?

[jdobbs]

As you can see the NVIDIA GPU is quicker handling the job but the INTEL GPU has a much better size ratio. But the difference is huge. I don't trust it.
The size of the source file was 5.005.060 kb. NVIDIA GPU made that 3.254.475 kb and INTEL GPU came to 1.151.442 kb.
The padding is an issue with both GPU's. I don't think the CQ values of the two encoders are equivalent, or the algorithm for ICQ (Intel) and VBR-Quality (NVIDIA) are significantly different. I'm going to have to do some encode quality testing (PSNR/SSIM) to see what numbers/results are approximately equal.

[dietachi]

I don't think the CQ values of the two encoders are equivalent, or the algorithm for ICQ (Intel) and VBR-Quality (NVIDIA) are significantly different. I'm going to have to do some encode quality testing (PSNR/SSIM) to see what numbers/results are approximately equal.

Intel ICQ: Requires more processing power because it’s constantly adjusting to maintain quality.

Nvidia VBR Quality: Requires less processing power because it balances data use without frequent adjustments.


In ICQ (Intelligent Constant Quality), the file size depends on the video’s complexity because it adjusts the bitrate to maintain consistent quality throughout. Complex scenes use more data, resulting in larger file sizes, whereas simpler scenes use less. This means ICQ can sometimes produce smaller files with better quality because it efficiently allocates data based on scene requirements.

In VBR (Variable Bitrate), the file size is more predictable but can vary because it aims for an average bitrate. While it balances quality and file size, some scenes might get less data than needed, resulting in lower quality compared to ICQ's more targeted data allocation.

ICQ can still look better even with a smaller file size compared to VBR. This happens because ICQ focuses on maintaining consistent quality by efficiently allocating data to more complex scenes while using less for simpler ones.

VBR, aiming for an average bitrate, might allocate data less efficiently, resulting in larger files but not necessarily better quality.

Thus, a 1GB ICQ-encoded video can appear better than a 5GB VBR-encoded video because ICQ prioritizes quality over size.

[jdobbs]

VBR-Quality isn't simple VBR. Newer versions of NVENCC use the parameter --qvbr (same thing). It also set's a quality target and adjusts based upon video complexity. It is the NVENCC equivalent to QSVENCC's ICQ and X264/X265's CRF.

You can see other NVENCC options and read about qvbr at at this link (https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md#--crop-intintintint).

[dietachi]

VBR-Quality isn't simple VBR. Newer versions of NVENCC use the parameter --qvbr (same thing). It also set's a quality target and adjusts based upon video complexity. It is the NVENCC equivalent to QSVENCC's ICQ and X264/X265's CRF.

You can see other NVENCC options and read about qvbr at at this link (https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md#--crop-intintintint).

While the core concept and goals of ICQ and QVBR are aligned, real-world outcomes can still exhibit variations due to the unique approaches and optimizations each company employs in their encoding solutions.

You may want to run some test encodes with both engines and compare them, that's what I did.

[jdobbs]

While the core concept and goals of ICQ and QVBR are aligned, real-world outcomes can still exhibit variations due to the unique approaches and optimizations each company employs in their encoding solutions.

You may want to run some test encodes with both engines and compare them, that's what I did.I think I have a pretty good understanding of how these things work. For example, here are some results (https://forum.doom9.org/showthread.php?p=1929974#post1929974) that compares the NVIDIA (CQM, qvbr) settings to X264 (CRF) using SSIM (Structural Similarity Index Measure). A few posts down you'll see a similar test in which I used PSNR (Peak Signal to Noise Ratio) and came to an almost identical conclusion.

One of the weaknesses I see in QSVENCC (Intel) is that you have to choose the quality factor as an integer, while X264 and NVENCC both use a floating values (note, however, that NVENCC quality output only changes at roughly .5 increments).

[dietachi]

I think I have a pretty good understanding of how these things work. For example, here are some results (https://forum.doom9.org/showthread.php?p=1929974#post1929974) that compares the NVIDIA (CQM, qvbr) settings to X264 (CRF)


My apologies.

I was referring to the QSVEnc vs NVEnc.

In the test that I conducted the ICQ on Intel was slower compared to the QVBR on NVIDIA.
But ICQ had better results.
I also run CQP on QSVEnc but that is very hard to control as it is a lot affected by the video, grain etc.that one needs additional settings.

I tested with the Arc 750, Arc 770, RTX 2060 and RTX 3080. As well with Intel UHD 770 and Intel Iris.

[dietachi]

I try to run some tests this weekend if you'd like on the Arcs.

[jdobbs]

I try to run some tests this weekend if you'd like on the Arcs.I'd be interested to see the results.

[musiclover]

So you're saying it changed to CQ23 on its own?

Yes, that's what I'm saying. GPUENCC has 3 settings. 32 (Good Quality), 28 (High Quality) and 23 (Highest Quality). I used 23 (Highest Quality). So how did it get to 20?

update:
Oh, now I see. The NVIDIA GPU settings are different from the INTEL GPU settings. The above numbers are fore the NVIDIA GPU. The highest quality setting with the INTEL GPU is 20. It needed to change between the NVIDIA and INTEL jobs but it didn't.

[jdobbs]

Yes, that's what I'm saying. GPUENCC has 3 settings. 32 (Good Quality), 28 (High Quality) and 23 (Highest Quality). I used 23 (Highest Quality). So how did it get to 20?

update:
Oh, now I see. The NVIDIA GPU settings are different from the INTEL GPU settings. The above numbers are fore the NVIDIA GPU. The highest quality setting with the INTEL GPU is 20. It needed to change between the NVIDIA and INTEL jobs but it didn't. I should have mentioned that. The numbers aren't equivalent between encoders, so they change.

After I do some SSIM and PSNR testing I'll probably change the defaults for the Intel GPU.

Just as a reference, you can set what you want the values to be with on the menu with an option in the GPUENCC.INI file. For example:


NV_HEVC_Q_VALUES=32,28,23
QSV_HEVC_Q_VALUES=28,23,20

NV_AVC_Q_VALUES=32,28,23
QSV_AVC_Q_VALUES=28,23,20

The example values above are the defaults if they aren't explicitly set.

[musiclover]

I should have mentioned that. The numbers aren't equivalent between encoders, so they change.

But they didn't change. This behaviour must be amended.

[jdobbs]

But they didn't change. This behaviour must be amended.When you select between them you aren't selecting the number as much as the quality/size level (Good, High, and Highest). The highest setting creates a result that has better quality -- at the expense of a larger size. They change to a value that should be roughly equivalent between the two encoders. A value of 20 in one encoder may be equal to a value of 23 in another (in terms of size and quality). For example, from my previous testing I know that a value of 23 in X264 is equivalent to a value of 28 in the NVIDIA encoder.

But... like I said, I need to do some tests to determine what values are equivalent between INTEL and NVIDIA.

[musiclover]

Originally Posted by jdobbs
So you're saying it changed to CQ23 on its own?

I was just saying that when I change from GPU the CQ doesn't change with it. It stays on 20 or 23 for the highest quality just what is was when I started GPUENCC. That needs to be rectified. See the logs in my earlier posts.
You wrote before that a couple of settings that are meant for NVIDIA weren't being reset when you reselected the INTEL option. This is one of them.

[jdobbs]

I was just saying that when I change from GPU the CQ doesn't change with it. It stays on 20 or 23 for the highest quality just what is was when I started GPUENCC. That needs to be rectified. See the logs in my earlier posts.
You wrote before that a couple of settings that are meant for NVIDIA weren't being reset when you reselected the INTEL option. This is one of them.Yep. I checked and that is definitely the case. I've fixed it for the next release.

[jdobbs]

I've started my SSIM comparisons of NVENCC and QSVENCC. I'll have completed the HEVC tests later tonight and will do AVC tomorrow. From what it looks like so far with the HEVC testing, the Intel (QSVENCC) encoder is giving the the same objectively measured quality at a significantly smaller file size (using --qvbr for NVENCC vs --icq for QSVENCC). Impressive. More to come...

[jdobbs]

So below is what I found in my comparison of HEVC encoding for NVIDIA and INTEL using NVENCC and QSVENCC.

The SSIM values were based upon 11 sources that varied in type, complexity, and cinematography. Samples (using the BD-RB size estimation algorithm) were made from all 11 and were combined into a source for encode. It was then encoded using whole constant quality values ranging from 11 to 40 (rarely would you use anything higher or lower). The default quality values were used ("default" in NVENCC and "balanced" in GPUENCC). The original file size was 2830849344. The SSIM values were gathered using FFMPEG's SSIM calculator.

It's mainly meant for informational/planning purposes. So, for example, if you like encoding with a CQM (NVIDIA) value of 28 you would use an ICQ (Intel) value of 27 for approximately equivalent quality and your file would be 87.57% of the output size.

Of course there would be variability based upon the source... but this provides a rough guideline. Also, this isn't meant to be a comparison of the two encoders. I'd have to get a lot more scientific for that. Frankly they are both incredibly fast and provide high quality. It's really meant to provide me with a basis for the default values I use in BD-RB and GPUENCC so I can add Intel support to them.


nvidia ssim file size intel ssim file size size diff

nv_hevc_11 0.99469 2735438211 qsv_hevc_11 0.99492 2370988385 86.68 %
nv_hevc_12 0.99448 2552227295
nv_hevc_13 0.99401 2328739840 qsv_hevc_12 0.99420 2151610991 92.39 %
nv_hevc_14 0.99338 2122928050 qsv_hevc_13 0.99337 1919639622 90.42 %
nv_hevc_15 0.99244 1900798214 qsv_hevc_14 0.99236 1686108802 88.71 %
nv_hevc_16 0.99132 1688757477 qsv_hevc_15 0.99134 1486820316 88.04 %
nv_hevc_17 0.99009 1492524278 qsv_hevc_16 0.99005 1289467174 86.40 %
nv_hevc_18 0.98871 1310176603 qsv_hevc_17 0.98864 1116438300 85.21 %
nv_hevc_19 0.98728 1148904500 qsv_hevc_18 0.98702 960051106 83.56 %
nv_hevc_20 0.98584 1009198253 qsv_hevc_19 0.98533 821968709 81.45 %
nv_hevc_21 0.98436 885250807
nv_hevc_22 0.98282 772522049 qsv_hevc_20 0.98337 690590341 89.39 %
nv_hevc_23 0.98117 666817944 qsv_hevc_21 0.98144 583298263 87.47 %
nv_hevc_24 0.97950 573435830 qsv_hevc_22 0.97931 481562861 83.98 %
nv_hevc_25 0.97791 493929976 qsv_hevc_23 0.97716 394645310 79.90 %
nv_hevc_26 0.97634 423749808 qsv_hevc_24 0.97651 370217079 87.37 %
qsv_hevc_25 0.97589 349571314
nv_hevc_27 0.97472 360136885 qsv_hevc_26 0.97526 331796120 92.13 %
nv_hevc_28 0.97322 307347661 qsv_hevc_27 0.97312 269137749 87.57 %
nv_hevc_29 0.97173 261407806 qsv_hevc_28 0.97105 218090181 83.43 %
nv_hevc_30 0.97027 222447802
nv_hevc_31 0.96877 187941863 qsv_hevc_29 0.96899 174132836 92.65 %
nv_hevc_32 0.96730 158906997 qsv_hevc_30 0.96703 141389351 88.98 %
nv_hevc_33 0.96580 134505532
nv_hevc_34 0.96434 114609022 qsv_hevc_31 0.96489 112962058 98.56 %
nv_hevc_35 0.96279 97577670 qsv_hevc_32 0.96299 92046174 94.33 %
nv_hevc_36 0.96118 83653349 qsv_hevc_33 0.96143 79951128 95.57 %
nv_hevc_37 0.95954 72067442 qsv_hevc_34 0.95938 67142107 93.17 %
nv_hevc_38 0.95776 62530064 qsv_hevc_35 0.95721 57324572 91.68 %
nv_hevc_39 0.95583 54649663 qsv_hevc_36 0.95506 49657159 90.86 %
nv_hevc_40 0.95368 47941203 qsv_hevc_37 0.95286 43762369 91.28 %
qsv_hevc_38 0.95107 41276063
qsv_hevc_39 0.94866 36743861
qsv_hevc_40 0.94613 33191208

[giavra]

please can the developer of the program add the target size up BD100?

[jdobbs]

please can the developer of the program add the target size up BD100?You can do that with the hidden option:

CUSTOM_TARGET_SIZE=nnnnn

Replace the "nnnnn" with the size you want. It is measured in one megabyte units ( 1MB=1048576 bytes). For example, if you wanted to set it to the default for BD-50:

CUSTOM_TARGET_SIZE=47366

[jdobbs]

Below are my results for AVC using the same method as described previously. Quite a difference in results when comparing AVC vs HEVC. So in this example, if you normally use a 28 for your NVIDIA AVC encoding (equivalent to a 23 in X264), you would want to use a 24 with the Intel encoder to get similar quality/size.

Again, these result are based upon my NVIDIA GPU and INTEL GPU. Results for others may vary -- but it is, at least, a guideline.
nvidia ssim file size intel ssim file size qs/nv
------ ---- --------- ----- ---- --------- -----
nv_avc_11 0.99518 2948116978
nv_avc_12 0.99497 2761225255
nv_avc_13 0.99444 2512675762
nv_avc_14 0.99379 2286065628
nv_avc_15 0.99287 2046803154
nv_avc_16 0.99175 1815499678 qsv_avc_11 0.99153 1893426489 104.29 %
nv_avc_17 0.99051 1604944659 qsv_avc_12 0.99010 1603360551 99.90 %
nv_avc_18 0.98914 1414594099 qsv_avc_13 0.98906 1433470502 101.31 %
nv_avc_19 0.98765 1246257654 qsv_avc_14 0.98823 1346877145 108.07 %
qsv_avc_15 0.98682 1194170603
nv_avc_20 0.98609 1100816582 qsv_avc_16 0.98555 1067648837 96.99 %
nv_avc_21 0.98438 968974715 qsv_avc_17 0.98399 919960017 94.94 %
nv_avc_22 0.98256 846555035
nv_avc_23 0.98065 734747056 qsv_avc_18 0.98138 783519276 106.64 %
qsv_avc_19 0.98004 682129810
nv_avc_24 0.97876 636552082 qsv_avc_20 0.97896 633512936 99.52 %
qsv_avc_21 0.97807 594858870
nv_avc_25 0.97689 550045786 qsv_avc_22 0.97634 517590569 94.10 %
nv_avc_26 0.97507 474855796 qsv_avc_23 0.97427 435570699 91.73 %
nv_avc_27 0.97320 406958743
nv_avc_28 0.97144 349505495 qsv_avc_24 0.97225 369357022 105.68 %
nv_avc_29 0.96967 298829575 qsv_avc_25 0.97013 315503691 105.58 %
nv_avc_30 0.96796 255814282 qsv_avc_26 0.96832 267564075 104.59 %
nv_avc_31 0.96628 218977265 qsv_avc_27 0.96627 222208146 101.48 %
nv_avc_32 0.96461 187703741 qsv_avc_28 0.96446 188119186 100.22 %
nv_avc_33 0.96292 161102530 qsv_avc_29 0.96336 174831668 108.52 %
qsv_avc_30 0.96221 151929585
nv_avc_34 0.96124 139469378 qsv_avc_31 0.96033 128760419 92.32 %
nv_avc_35 0.95942 120404165
qsv_avc_32 0.95846 110359080
nv_avc_36 0.95754 104934340
qsv_avc_33 0.95654 94901002
nv_avc_37 0.95549 91922125
qsv_avc_34 0.95467 81918195
nv_avc_38 0.95329 81313119 qsv_avc_35 0.95271 72491981 89.15 %
nv_avc_39 0.95088 72668211 qsv_avc_36 0.95078 65106093 89.59 %
nv_avc_40 0.94814 65427077 qsv_avc_37 0.94804 56929912 81.01 %
qsv_avc_38 0.94534 50436225
qsv_avc_39 0.94264 45691280
qsv_avc_40 0.94040 42331347

[jdobbs]

I have updated the first post of this thread with a link to the latest release of BD Rebuilder (v0.62.04). Changes for this release:- Corrected an error in which UHD-BD encoding
while using the INTEL GPU could fail.
- Corrected an error in GPUENCC in which
changing GPUs might cause an encode to fail
due to incorrect mode values in the command
line.
- Updated the INTEL GPU prediction tables to
make them more accurate when using ICQ.
- Fixed an issue in GPUENCC in which default
constant quality settings were not being
adjusted when changing the selected encoder.
- Added an informational line to the log in
GPUENCC the identifies which GPU is being
used for an encode.
- Other minor corrections and cosmetic fixes.

[dietachi]

I'd be interested to see the results.

I tried to run some tests with the latest version of BD Rebuilder.


Metric Result 1 (QSVEnc) Result 2 (QSVEncC) Result 3 (NVENC)
SSIM 0.997954 0.997589 0.998094
PSNR (dB) 52.822 51.719 52.565
File Size Avg (bytes) 988,297,957 887,747,613 1,415,654,002
File Size % Difference - -10.18% +43.17%




Encoding Speed
ARC A770: AVG 450 fps (normal), 400 fps (--bframes 16 --ref 8 --scenario-info archive)
RTX 2060 (NVENC): AVG 330 fps
Both were encoding from one NVMe to another.

Additional Notes:
- Buffer adjustments to increase encoding speed were not used for QSVEnc testing.
- AVSW can sometimes offer faster de/encoding, particularly in specific CPU/GPU configurations or when handling input file decode errors.


Based on my previous tests, CQP encoding appears to yield better SSIM and PSNR values compared to ICQ.
However, ICQ may offer advantages when precise control over file size is crucial, especially for media destined for formats like CD, DVD, or BD, where strict size limitations apply for what BD Rebuilder is intended.


Some questions:

When transitioning from encoding via GPUENCC to BDRB with HEVC selected in GPUENCC, it defaults to using HEVC for Blu-ray in BD Rebuilder. Shouldn't it default to AVC instead and switch to HEVC only for Ultra HD?


Is there a specific reason why higher b-frames, reference frames, scenario information, etc., for QSVenc, are not utilised when converting to MKV? Or is that in the planning for future versions?

[jdobbs]

I tried to run some tests with the latest version of BD Rebuilder.


Metric Result 1 (QSVEnc) Result 2 (QSVEncC) Result 3 (NVENC)
SSIM 0.997954 0.997589 0.998094
PSNR (dB) 52.822 51.719 52.565
File Size Avg (bytes) 988,297,957 887,747,613 1,415,654,002
File Size % Difference - -10.18% +43.17%




Encoding Speed
ARC A770: AVG 450 fps (normal), 400 fps (--bframes 16 --ref 8 --scenario-info archive)
RTX 2060 (NVENC): AVG 330 fps
Both were encoding from one NVMe to another.

Additional Notes:
- Buffer adjustments to increase encoding speed were not used for QSVEnc testing.
- AVSW can sometimes offer faster de/encoding, particularly in specific CPU/GPU configurations or when handling input file decode errors.


Based on my previous tests, CQP encoding appears to yield better SSIM and PSNR values compared to ICQ.
However, ICQ may offer advantages when precise control over file size is crucial, especially for media destined for formats like CD, DVD, or BD, where strict size limitations apply for what BD Rebuilder is intended.


Some questions:

When transitioning from encoding via GPUENCC to BDRB with HEVC selected in GPUENCC, it defaults to using HEVC for Blu-ray in BD Rebuilder. Shouldn't it default to AVC instead and switch to HEVC only for Ultra HD?


Is there a specific reason why higher b-frames, reference frames, scenario information, etc., for QSVenc, are not utilised when converting to MKV? Or is that in the planning for future versions?There is no connection between GPUENCC and BD-RB. So selecting something in GPUENCC would have no effect. The only way BD-RB will ever use HEVC is if you are creating a UHD-BD. That means the ource is UHD or "Convert BD to UHD" is selected under SETTINGS/OUTPUT OPTIONS.

GPUENCC uses a set of default settings -- I could probably make it possible to change them. You can also use the hidden option ENC_CUSTOM (do a search of this thread) to change some of the defaults.

[dietachi]

There is no connection between GPUENCC and BD-RB. So selecting something in GPUENCC would have no effect. The only way BD-RB will ever use HEVC is if you are creating a UHD-BD. That means the ource is UHD or "Convert BD to UHD" is selected under SETTINGS/OUTPUT OPTIONS.

GPUENCC uses a set of default settings -- I could probably make it possible to change them. You can also use the hidden option ENC_CUSTOM (do a search of this thread) to change some of the defaults.


Roger that.
I'll check the BDRB settings.

For the ENC_CUSTOM, I'll test that as well. Thank you.

I noticed that NVEnc now supports SDR to HDR on Turing GPUs as well as NVIDIA VSR (Video Super Resolution) resize, but only on x64.
I'll gonna give that a try.

[musiclover]

I do see a possible unrelated issue, though. The input isn't 16:9, but the resizing is outputting it to 1280x720 with no padding. That's probably true on both encodes.



The padding is an issue with both GPU's.

It seems the padding issue is not resolved yet.

[musiclover]

In GPUENCC the QC setting meant for INTEL wasn't reset when reselecting NVIDIA after INTEL errored out. In INTEL CQ 18 (highest quality) was selected. After changing to NVIDIA it should have changed to 23. But it didn't.

GPUREENCODE.LOG
----------------------
[06.30.24] GPU Reencoder v0.01.15
----------------------
[17.11.03]Start Job [1 of 1]
- Reencoding "Keane Glastonbury 2160p 2024-06-29 .mp4"
-- Using INTEL GPU for Video Encode
-- Collecting input file information...
-- Input : HEVC, 3840x2160, 50fps
-- Vid: H264 (AVC), 1920x1080, 25 fps, CQ 18
-- Aud: Intact (Keep Original), no reencode
- ERROR -- Encode failed. Job aborted.
----------------------
[06.30.24] GPU Reencoder v0.01.15
----------------------
[17.24.15]Start Job [1 of 1]
- Reencoding "Keane Glastonbury 2160p 2024-06-29 .mp4"
-- Using NVIDIA GPU for Video Encode
-- Collecting input file information...
-- Input : HEVC, 3840x2160, 50fps
-- Vid: H264 (AVC), 1920x1080, 25 fps, CQ 18
-- Aud: Intact (Keep Original), no reencode
[18.42.45]Job Completed [1 of 1]

GPULASTCMD.TXT
"C:\BD Rebuilder\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw --fps 25 --output-res 1920x1080 -i "E:\Keane Glastonbury 2160p 2024-06-29 .mp4" --codec h264 --preset default --colorprim bt709 --transfer bt709 --colormatrix bt709 --qp-min 0 --multipass 2pass-full --vbr 0 --vbr-quality 18 --aq --aq-temporal --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --lookahead 24 --no-b-adapt --gop-len 24 --audio-copy 1 --chapter-copy -o "D:\WORK\Keane Glastonbury 2160p 2024-06-29 .mp4"

[DrinkLyeAndDie]

Can someone please remind me how to import one or more HEVC MKV files and output a Bluray (AVC) disc? I am positive I've done it before but I can't remember how and I'm having no luck finding an actual answer when sifting through a lot of search results. No matter what I do I wind up with a HEVC encoded Bluray output.

[jdobbs]

Can someone please remind me how to import one or more HEVC MKV files and output a Bluray (AVC) disc? I am positive I've done it before but I can't remember how and I'm having no luck finding an actual answer when sifting through a lot of search results. No matter what I do I wind up with a HEVC encoded Bluray output.That shouldn't be an issue.

Do you have UHD_CONVERT_ENABLE=1 and UHD_V3_MODE=1 in your INI file? The first one makes the option "Convert BD to UHD..." available on the SETTINGS/OUTPUT OPTIONS menu. The second one gets set when you actually select it.

That should be the only way it will create HEVC Blu-Ray output from a 1080p source (or smaller).

If you are importing a 2160p HEVC source, that is different, as it has to be HEVC.

[DrinkLyeAndDie]

That shouldn't be an issue.

Do you have UHD_CONVERT_ENABLE=1 and UHD_V3_MODE=1 in your INI file? The first one makes the option "Convert BD to UHD..." available on the SETTINGS/OUTPUT OPTIONS menu. The second one gets set when you actually select it.

That should be the only way it will create HEVC Blu-Ray output from a 1080p source (or smaller).

If you are importing a 2160p HEVC source, that is different, as it has to be HEVC.

Thanks for the reply jdobbs. The source[s] are anywhere from 480 to 1080p. No 2160p sources. Neither of the settings you mentioned is enabled. I actually deleted my regular BDREBUILDER.INI file and let BD-RB create a new one.

I feel like I'm doing something very stupid and causing the issue but I really can't figure out what.

Here's my INI:

[Options]
VERSION=0.62.0.4
ENCODER=0
MODE=0
ENCODE_QUALITY=5
ONEPASS_ENCODING=1
AUTO_QUALITY=0
AUDIO_TO_KEEP=eng;
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=1
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=3
AVCHD=1
REMOVE_WORKFILES=1
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=1
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=1
OUTPUT_SBS=0
NEROAAC=1
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=22450
TARGET_SIZE=22450
NVENC_CAPABLE=1
MENU_BACKGROUND=C:\BD_Rebuilder\misc\menuback.jpg
MENU_AUDIO=C:\BD_Rebuilder\tools\blankclip\blank.ac3
IMPORT_THRESHOLD=15
QUICK_PLAY_THRESHOLD=10
MENU_AUTO_BACKGROUND=1
MENU_AUTO_DVDAUDIO=1
MENU_PLAY_SEQUENTIAL=0
MENU_START_WITH_MENU=1
IMPORT_LIMIT_LANG=0
IMPORT_KEEP_PLAYALL=0
IMPORT_PREPARE_MKV=1
MOVIEONLY_TYPE=0
ALTCRF=23
ALT_TARGET=1024
ALT_CRF_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
[Paths]
NeroAACPath=C:\Program Files (x86)\NeroACC\neroAacEnc.exe
SupTitlePath=C:\Program Files (x86)\SupTitle\SupTitle.dll
DGIndexNV=C:\Program Files (x86)\DGDecNV\DGIndexNV.exe
DGDecNV=C:\Program Files (x86)\DGDecNV\DGDecodeNV.dll
SOURCE_PATH=E:\_TEMP\BD-RB\IMPORTS\S01E01_-_PILOT\
TesseractPath=C:\Program Files (x86)\Tesseract-OCR\tesseract.exe
WORKING_PATH=E:\_TEMP\BD-RB\

[jdobbs]

Thanks for the reply jdobbs. The source[s] are anywhere from 480 to 1080p. No 2160p sources. Neither of the settings you mentioned is enabled. I actually deleted my regular BDREBUILDER.INI file and let BD-RB create a new one.

I feel like I'm doing something very stupid and causing the issue but I really can't figure out what.

Here's my INI:

[Options]
VERSION=0.62.0.4
ENCODER=0
MODE=0
ENCODE_QUALITY=5
ONEPASS_ENCODING=1
AUTO_QUALITY=0
AUDIO_TO_KEEP=eng;
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=1
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=3
AVCHD=1
REMOVE_WORKFILES=1
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=1
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=1
OUTPUT_SBS=0
NEROAAC=1
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=22450
TARGET_SIZE=22450
NVENC_CAPABLE=1
MENU_BACKGROUND=C:\BD_Rebuilder\misc\menuback.jpg
MENU_AUDIO=C:\BD_Rebuilder\tools\blankclip\blank.ac3
IMPORT_THRESHOLD=15
QUICK_PLAY_THRESHOLD=10
MENU_AUTO_BACKGROUND=1
MENU_AUTO_DVDAUDIO=1
MENU_PLAY_SEQUENTIAL=0
MENU_START_WITH_MENU=1
IMPORT_LIMIT_LANG=0
IMPORT_KEEP_PLAYALL=0
IMPORT_PREPARE_MKV=1
MOVIEONLY_TYPE=0
ALTCRF=23
ALT_TARGET=1024
ALT_CRF_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
[Paths]
NeroAACPath=C:\Program Files (x86)\NeroACC\neroAacEnc.exe
SupTitlePath=C:\Program Files (x86)\SupTitle\SupTitle.dll
DGIndexNV=C:\Program Files (x86)\DGDecNV\DGIndexNV.exe
DGDecNV=C:\Program Files (x86)\DGDecNV\DGDecodeNV.dll
SOURCE_PATH=E:\_TEMP\BD-RB\IMPORTS\S01E01_-_PILOT\
TesseractPath=C:\Program Files (x86)\Tesseract-OCR\tesseract.exe
WORKING_PATH=E:\_TEMP\BD-RB\
Nope. It's not you. I just imported an HEVC 1080p file and it did the same thing.

How the hell did I screw that up?

On the plus side, it's actually creating a legal (UHD) blu-ray when I run it... on the minus side, IT'S NOT SUPPOSED TO!

Well... it's not a new bug. I just tried v0.61.29 from a year ago -- and it does the same thing. It looks like it is something in the IMPORT routines, because afer the import BD-RB identifies the source as a UHD-BD.

[DrinkLyeAndDie]

Nope. It's not you. I just imported an HEVC 1080p file and it did the same thing.

How the hell did I screw that up?

On the plus side, it's actually creating a legal (UHD) blu-ray when I run it... on the minus side, IT'S NOT SUPPOSED TO!

Well... it's not a new bug. I just tried v0.61.29 from a year ago -- and it does the same thing. It looks like it is something in the IMPORT routines, because afer the import BD-RB identifies the source as a UHD-BD.

I was really beginning to think I was just a complete idiot. Glad that I'm not although that, unfortunately, means more work for you. :eek: I guess it's been quite awhile since I tried doing this. It also means no one else uses this ability very often, too, or they haven't noticed that it isn't working properly.

Thanks for looking into it and letting me know, jdobbs. Much appreciated.

[jdobbs]

I was really beginning to think I was just a complete idiot. Glad that I'm not although that, unfortunately, means more work for you. :eek: I guess it's been quite awhile since I tried doing this. It also means no one else uses this ability very often, too, or they haven't noticed that it isn't working properly.

Thanks for looking into it and letting me know, jdobbs. Much appreciated.Turns out this has been the case since V0.61.17 (Sept of 2020).

If you enter the line below in the "[Options]" area of your INI it should fix the issue. In the meantime I will create a more permanent solution for the next release.

ENABLE_NEW_TSMUXER=0

[Lathe]

Nope. It's not you. I just imported an HEVC 1080p file and it did the same thing.

How the hell did I screw that up?



Uh oh... Looks like it's time for a Regime change... https://lh3.googleusercontent.com/pw/AP1GczNuSHXicvIvdYEl-wb99oyNaE1gavkEGTT7HSnVqz5pGPEXLyXQvQ8LiOllw7D6hYjqX6y71aZ09-magBjY5mcW2zU5pSdDprOC1jGadqQHhzSQ_RRGV4lBT_9ydGbj80uWSk895V-CwIUn5x2BXCXrtg=w15-h15-s-no-gm?authuser=0

[Lathe]

Can someone please remind me how to import one or more HEVC MKV files and output a Bluray (AVC) disc? I am positive I've done it before but I can't remember how and I'm having no luck finding an actual answer when sifting through a lot of search results. No matter what I do I wind up with a HEVC encoded Bluray output.

So, if I am understanding correctly, this is to import say a HEVC MKV file for example, and you want to convert it either to an AVC MKV file or a fully playable 1080 Blu-ray, right?

I would also like to know how to do this because many times I do want to convert an HEVC MKV file to an x264 encoded file or Blu-ray. I THINK one way I did it was to set the output for 'Archive' and that is already set to AVC/AC3. That would also do the same, wouldn't it, or am I misremembering...?

[DrinkLyeAndDie]

Turns out this has been the case since V0.61.17 (Sept of 2020).

If you enter the line below in the "[Options]" area of your INI it should fix the issue. In the meantime I will create a more permanent solution for the next release.

ENABLE_NEW_TSMUXER=0

Thank you! Just did a quick test on my system and success!

[jdobbs]

Thank you! Just did a quick test on my system and success!So it worked? That means I was right one time in a row!

Nothing to be proud of, I guess. Even a broken clock is right twice a day.

[DrinkLyeAndDie]

So it worked? That means I was right one time in a row!

Nothing to be proud of, I guess. Even a broken clock is right twice a day.

Yes, it worked. I did a quick test where I imported 2 HEVC encoded TV episodes and created a Bluray from them. When it was done I checked and they were AVC encoded in the backup disc.

Would it be possible in the log window to indicate whether the output is being encoded as HEVC or AVC during the actual process. I might have noticed the issue earlier had this been indicated somewhere.

I had already wiped the test info but I redid it again but just with a single small file each way. Before adding ENABLE_NEW_TSMUXER=0 and after. I used Mediainfo to check the main m2ts file when the process was done.

Before:

General
ID : 1 (0x1)
Complete name : E:\_Work\_BD-RB\_OUTPUT\TEST\BDMV\STREAM\00000.m2ts
Format : BDAV
Format/Info : Blu-ray Video
File size : 1.80 GiB
Duration : 43 min 43 s
Overall bit rate mode : Variable
Overall bit rate : 5 891 kb/s
Maximum Overall bit rate : 35.5 Mb/s
Frame rate : 29.970 FPS

Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4.1@High
Codec ID : 36
Duration : 43 min 42 s
Bit rate : 5 424 kb/s
Width : 720 pixels
Height : 480 pixels
Display aspect ratio : 4:3
Frame rate : 29.970 (30000/1001) FPS
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.524
Stream size : 1.66 GiB (92%)
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 43 min 43 s
Bit rate mode : Constant
Bit rate : 224 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
Delay relative to video : 27 ms
Stream size : 70.0 MiB (4%)
Service kind : Complete Main
Dialog Normalization : -31 dB
dialnorm_Average : -31 dB
dialnorm_Minimum : -31 dB
dialnorm_Maximum : -31 dB

After:

General
ID : 1 (0x1)
Complete name : E:\_Work\_BD-RB\_OUTPUT\TEST\BDMV\STREAM\00000.m2ts
Format : BDAV
Format/Info : Blu-ray Video
File size : 4.39 GiB
Duration : 43 min 43 s
Overall bit rate mode : Variable
Overall bit rate : 14.4 Mb/s
Maximum Overall bit rate : 35.5 Mb/s
Frame rate : 29.970 FPS

Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
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=30
Codec ID : 27
Duration : 43 min 43 s
Bit rate mode : Variable
Bit rate : 13.6 Mb/s
Maximum bit rate : 35.0 Mb/s
Width : 720 pixels
Height : 480 pixels
Display aspect ratio : 4:3
Frame rate : 29.970 (30000/1001) FPS
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 1.311
Stream size : 4.15 GiB (94%)

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 43 min 43 s
Bit rate mode : Constant
Bit rate : 224 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
Delay relative to video : 27 ms
Stream size : 70.0 MiB (2%)
Service kind : Complete Main
Dialog Normalization : -31 dB
dialnorm_Average : -31 dB
dialnorm_Minimum : -31 dB
dialnorm_Maximum : -31 dB

[DrinkLyeAndDie]

So, if I am understanding correctly, this is to import say a HEVC MKV file for example, and you want to convert it either to an AVC MKV file or a fully playable 1080 Blu-ray, right?

I want to take HEVC MKVs that I created from my disc library and then create a playable Blu-ray disc output to be burned to disc. I want to do this all in a single flow where I import the files directly into BD-RB and let it do the conversion and Bluray output without my having to first convert from HEVC to AVC and then import to create the Bluray output. I want a single one-step set it and forget it rather than two steps. This is doable and removing the bug this is easily doable again. :)

I would also like to know how to do this because many times I do want to convert an HEVC MKV file to an x264 encoded file or Blu-ray. I THINK one way I did it was to set the output for 'Archive' and that is already set to AVC/AC3. That would also do the same, wouldn't it, or am I misremembering...?

To just convert an HEVC MKV to an AVC MKV under Mode pick Movie-Only Backup, then select Alternate Movie-Only Output. From there select the sizing, audio, etc. If you don't want the output to remain as HEVC then make sure not to select one that is HEVC or has Intact Video in the name. Pick the one applicable to what you want or create your own alternate output selection which can be added to the alternate.txt which contains the preset options. Then import the files and off you go.

For making a standard Bluray disc it should be as simple selecting Full Backup under mode, selecting the encoder, size, etc, importing the HEVC MKVs, and off you go. Unless you explicitly tell it to create UHD (HEVC) content then I believe it used and should have continued to by default output as standard Bluray (AVC). With the added INI file option jdobbs posted this is working again.

[Lathe]

I want to take HEVC MKVs that I created from my disc library and then create a playable Blu-ray disc output to be burned to disc. I want to do this all in a single flow where I import the files directly into BD-RB and let it do the conversion and Bluray output without my having to first convert from HEVC to AVC and then import to create the Bluray output. I want a single one-step set it and forget it rather than two steps. This is doable and removing the bug this is easily doable again. :)



To just convert an HEVC MKV to an AVC MKV under Mode pick Movie-Only Backup, then select Alternate Movie-Only Output. From there select the sizing, audio, etc. If you don't want the output to remain as HEVC then make sure not to select one that is HEVC or has Intact Video in the name. Pick the one applicable to what you want or create your own alternate output selection which can be added to the alternate.txt which contains the preset options. Then import the files and off you go.

For making a standard Bluray disc it should be as simple selecting Full Backup under mode, selecting the encoder, size, etc, importing the HEVC MKVs, and off you go. Unless you explicitly tell it to create UHD (HEVC) content then I believe it used and should have continued to by default output as standard Bluray (AVC). With the added INI file option jdobbs posted this is working again.

Yeah, that is pretty much what I thought... Thanks for the reply. I believe I have also done that with alternate movie-only output too. I would suppose that if you wanted that final step to convert to a playable Blu-ray, you could just simply mux it through TSMuxer to create the Blu-ray folder and burn if you wished to do so.

[MrVideo]

Even a broken clock is right twice a day.
An old mechanical clock, maybe. But a newer digital clock; not so much. :eek:

[giavra]

You can do that with the hidden option:

CUSTOM_TARGET_SIZE=nnnnn

Replace the "nnnnn" with the size you want. It is measured in one megabyte units ( 1MB=1048576 bytes). For example, if you wanted to set it to the default for BD-50:

CUSTOM_TARGET_SIZE=47366

Thank You Very Much

[Blurayhd]

Hi all, Jdobbs mention

Added support for GPU encoding using Intel GPUs (Quick Sync). Note that your GPU must be advanced enough,

So I have an Nvidia GTX 1080 TI 11gb its enough or will crash?