Log in

View Full Version : BD Rebuilder Beta - Bug Reports Only


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 [642] 643 644 645 646 647 648

MrVideo
6th December 2024, 12:34
This used to work, but now it doesn't.

It is doing "converting source to compliant formt..." and ends up taking the 23.976 video and converting it into 59.94. WTF! According to MediaInfo it is indeed 23.976:
General
Unique ID : 242358087752017892526571231757600846667
(0xB6547847DDF69826113125406230734B)
Complete name : E:\BD-Rebuilder\Last_Resort\EDIT\1. Captain.mkv
Format : Matroska
Format version : Version 4
File size : 1.00 GiB
Duration : 44 min 0 s
Overall bit rate : 3 256 kb/s
Writing application : VideoReDo (Lavf58.29.100)
Writing library : VideoReDo (Lavf58.29.100)
ErrorDetectionType : Per level 1

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Codec ID : V_MPEGH/ISO/HEVC
Duration : 44 min 0 s
Bit rate : 2 743 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 FPS
Bits/(Pixel*Frame) : 0.055
Stream size : 863 MiB (84%)
Default : No
Forced : No

Audio
ID : 2
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Duration : 44 min 0 s
Bit rate mode : Constant
Bit rate : 448 kb/s
Channel(s) : 6 channels
ChannelLayout_Original : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 141 MiB (14%)
Language : English
Service kind : Complete Main
Default : Yes
Forced : No

Menu
00:00:00.000 : :Chapter 1
00:17:01.019 : :Chapter 2
00:25:28.776 : :Chapter 3
00:30:09.097 : :Chapter 4
00:37:01.509 : :Chapter 5
00:43:25.058 : :Chapter 6
00:43:59.217 : :Chapter 7
Here is the EPR file:
[Options]
VERSION=0.62.0.11
ENCODER=1
MODE=0
TARGET_SIZE=23500
CUSTOM_TARGET_SIZE=24500
AUTO_BURN=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=0
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AUDIO_DRC=0
DECODER=0
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
MENU_BACKGROUND=E:\BD-Rebuilder\Last_Resort\Last.Resort-bkg.jpg
MENU_AUDIO=C:\BD_Rebuilder-0.62.11\tools\blankclip\blank.ac3
IMPORT_THRESHOLD=0
QUICK_PLAY_THRESHOLD=0
MIN_PLAYLIST_MINS=0
MENU_AUTO_BACKGROUND=0
MENU_AUTO_DVDAUDIO=1
MENU_FORCE_QUICK=1
MENU_PLAY_SEQUENTIAL=0
MENU_START_WITH_MENU=1
IMPORT_LIMIT_LANG=0
IMPORT_KEEP_PLAYALL=0
IMPORT_VFR_SCAN=0
FORCE_NOENCODE=1
MENU_FONT=Century Gothic
MENU_FONT_BOLD=1
MENU_FONT_ITALIC=0
MENU_VERTICAL=300
MENU_HORIZONTAL=1100
MENU_ACTIVE_COLOR=0xd9ba00
MENU_CUSTOM_COLOR=
MENU_INACTIVE_COLOR=0xd98200
MENU_BACKDROP_OPACITY=0
MENU_ROLLOVER=1
MENU_ITEMS_PAGE=14
ENCODE_QUALITY=2
ONEPASS_ENCODING=0
AUTO_QUALITY=0
IMPORT_VFR_FILM=0
AVSFilter01=selectevery(2,0)
IMPORT_PREPARE_MKV=0
MOVIEONLY_TYPE=28
ALTCRF=23
ALT_TARGET=1024
ALT_CRF_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
NVENC_CAPABLE=1
UHD_CONVERT_ENABLE=0
UHD_V3_MODE=1
[Paths]
WORKING_PATH=E:\BD-REBUILDER\WORK\
SOURCE_PATH=E:\BD-REBUILDER\WORK\IMPORTS\EDIT\
DGIndexNV=C:\Program Files (x86)\DGAVCDecNV\DGIndexNV.exe
DGDecNV=C:\Program Files (x86)
\DGAVCDecNV\DGDecodeNV.dll
[Batch]
MAIN_MPLS=.MPLS
MAIN_MPLS_ANGLE=0
FORCED_SUB=0
FORCED_AUD=0
AUDIO=
SUBS=
Log file:
[04:58:29] Importing: EDIT
- [04:59:06] Importing video file: (1 of 14)
- Collecting audio/video streams from source...
- Correcting MKV format inconsistencies...
- Scanning for Variable Frame Rate...
- Collecting audio/video streams from source...
- Converting source to compliant format...
- Integrating into pseudo-BD structure...
- [05:07:20] Importing video file: (2 of 14)
- Collecting audio/video streams from source...
- Correcting MKV format inconsistencies...
- Scanning for Variable Frame Rate...
- Collecting audio/video streams from source...
- Converting source to compliant format...
[05:08:01]ERROR: Failed VFR conversion. Aborted.
----------------------
[05:13:59] Importing: EDIT
- [05:14:37] Importing video file: (1 of 14)
- Collecting audio/video streams from source...
- Correcting MKV format inconsistencies...
- Scanning for Variable Frame Rate...
- Collecting audio/video streams from source...
- Converting source to compliant format...
[05:15:13]ERROR: Failed VFR conversion. Aborted.
Aborted because I hit cancel.

There is zero reason to convert the frame rate. The EPR file was taken from a previous job that worked just fine. Only the paths are changed and FORCE_NOENCODE=1 (it was 0, but didn't make a difference).

Even 0.61.29 gets it wrong.

UPDATE: It just dawned on me what the issue probably is. BDs don't handle HEVC video. I set UHD_CONVERT_ENABLE to 1, but it didn't make a difference. How do I get BDRB to author a UHD disc with 1080p HEVC content? BTW, I don't want to use the standalone program to upconvert to 2160p because the program doesn't use the chapter locations to create I-frames at those locations. AIUI, you want I-frames at chapter marks.

MrVideo
6th December 2024, 13:04
Whenever I restart a job, the contents of titles.inf is ignored. Here is the content of the file:
[Titles]
Title=
Threshold=0
00001=1. Captain
00002=2. Blue on Blue
00003=3. Eight Bells
00004=4. Voluntold
00005=5. Skeleton Crew
00006=6. Another Fine Navy Day
00007=7. Nuke It Out
00008=8. Big Chicken Dinner
00009=9. Cinderella Liberty
00010=10. Blue Water
00011=11. Damn the Torpedoes
00012=12. The Pointy End of the Spear
00013=13. Controlled Flight Into Terrain
00014=Last Resor: Declassified
[Position]
00001=1
00002=2
00003=0
00004=0
00005=0
00006=0
00007=0
00008=0
00009=0
00010=0
00011=0
00012=0
00013=0
00014=3
[Selected]
00001=-1
00002=-1
00003=0
00004=0
00005=0
00006=0
00007=0
00008=0
00009=0
00010=0
00011=0
00012=0
00013=0
00014=-1
This is what it looks like when I do the import: http://vidiot.com/video/BDRB-LR-titles.jpg

The file is completely ignored. It is like it was doing this for the first time.

gonca
7th December 2024, 02:09
@Lathe
Don't think avisynth 2.606 can do 10 bit video, which your input is (main10)
Might have to update to avisynth+ to do these type of files

Lathe
7th December 2024, 02:16
@Lathe
Don't think avisynth 2.606 can do 10 bit video, which your input is (main10)
Might have to update to avisynth+ to do these type of files

Thanks Bro! I knew we kept you up there in the Canadian Outback for a reason... :D

Lathe
7th December 2024, 04:06
Well, I went ahead and ran the Shout Factory Blu-ray through BDRB to shrink it to fit a BD, and burned it to Blu-ray and it played perfectly fine on my OPPO. As an experiment I also had tried the HEVC file (which I got in trouble for :)) and VLC played both the file and the resulting M2ts file from BDRB exactly the same with with exaggerated contrast and super grainy. So, it simply must just be something about VLC rending this movie that way for some mysterious reason. But, as long as I have the Blu-ray backed up and burned to disc and it plays fine on my OPPO then everything is okay... :D

Lathe
7th December 2024, 06:42
Okay, it's official...

I'm an idiot...

Yep, that's about it, pure and simple... I felt my penance should at least be coming back here and telling everyone, NOT that it would especially be a particularly big surprise... :rolleyes:

Okay, here goes... and, I'm telling you this is not going to be easy. *sigh... I checked and for some TOTALLY bizarre reason, the VLC visual effects filter had the 'Sharpen' setting checked and it was cranked way up... I know, unbelievable. No F'n wonder nobody knew what the hell I was talking about. I swear, it is shocking that I can even get through the day without serious damage to myself.

Okay, uh... next time hopefully BEFORE I go spouting off to everyone, I will, uh *cough... check the damn settings first. I'm going to go and hide under some rock now...

However, be that as it may... (and yes, I KNOW gonca, you are laughing your fool head off...) I still would like to know WHY BDRB did not accept and process that HEVC file when I tried to import it. When it started to reencode the video, that's when it threw an error. I put all the BDRB information in my very first post about all this above.

My head hurts...

https://lh3.googleusercontent.com/pw/AP1GczO4WuQqNqCi0sM-JtVCbI3NzckNWLzG_SkE4qnJK1-EXZETNqWwvMuUAZJACKPJSiniGtfFMCLa_44wu-RxTjLlv_WehWt-yjXwEbzh9x0uRG36eJ6ONE9HIsvIv6p-A_SWv3kLWXsYPKem7rHHOO7cXQ=w244-h244-s-no-gm?authuser=0

MrVideo
7th December 2024, 09:36
@lathe Instead of using BDRB to recode H265 to H264, why not use the GPUENCC standalone program? No fuss, no muss. A couple of simple settings and the recoding is done in no time at all (if hardware encoding is used).

Lathe
7th December 2024, 10:02
@lathe Instead of using BDRB to recode H265 to H264, why not use the GPUENCC standalone program? No fuss, no muss. A couple of simple settings and the recoding is done in no time at all (if hardware encoding is used).

I'll look into that, thanks for the suggestion!

I would like just to use a simply CMD line, but there are certain settings I think in order to get the frame rate right or something that I'm not sure of. And, I don't know if my GPU will work with that, I'm not familiar with that whole side of the GPU used for encoding.

gonca
7th December 2024, 11:59
Thanks Bro! I knew we kept you up there in the Canadian Outback for a reason... :D

It's not an Outback, it's a Wilderness
Outback is in Australia

gonca
7th December 2024, 12:01
Okay, it's official...

I'm an idiot...



As long as you know it

During import TsMuxer is doing the demux/remux.
It can handle 10 bit video.
For encoding, avisynth is used, and the version you are on can not.
That is why import was good and processing failed.

Edit
I am not laughing my head off, I have come to expect it of you!

Lathe
7th December 2024, 23:07
As long as you know it

During import TsMuxer is doing the demux/remux.
It can handle 10 bit video.
For encoding, avisynth is used, and the version you are on can not.
That is why import was good and processing failed.

Edit
I am not laughing my head off, I have come to expect it of you!

Ah, I see... Thanks for the explanation. I was curious why BDRB was rejecting it, that's good to know.

I'm glad your expectations have been met... :D

BTW, how's the Moose Stew...?

MrVideo
8th December 2024, 04:05
I would like just to use a simply CMD line, but there are certain settings I think in order to get the frame rate right or something that I'm not sure of. And, I don't know if my GPU will work with that, I'm not familiar with that whole side of the GPU used for encoding.
It can be run via a command line, but because of the numerous options, best to run it from the GUI. There's lots of previous discussion about the newer GPUENCC program. Dig back thru the thread.

MrVideo
8th December 2024, 04:13
UPDATE: It just dawned on me what the issue probably is. BDs don't handle HEVC video. I set UHD_CONVERT_ENABLE to 1, but it didn't make a difference. How do I get BDRB to author a UHD disc with 1080p HEVC content? BTW, I don't want to use the standalone program to upconvert to 2160p because the program doesn't use the chapter locations to create I-frames at those locations. AIUI, you want I-frames at chapter marks.
I went back to the original HEVC videos and recoded them to AVC (via GPUENCC). Because I had to edit them at the commercial breaks to remove some of the black and to create I-frames at those locations, I didn't have to start from scratch as I was able to use the VideoReDo project files to do the editing again, but on AVC files this time. The BD was created just fine.

While I was able to get around the issue this time, I still want to be able to create a UHD with 1080p HEVC videos, in order to avoid a recoding. Each recoding introduces minor artifacts, etc. The less recoding, the better.

varekai
8th December 2024, 11:22
(via GPUENCC).
Where can i find this GUI - GPUENCC program? I can't find it with google.

musiclover
8th December 2024, 12:39
Where can i find this GUI - GPUENCC program? I can't find it with google.

In the BD_Rebuilder directory

Lathe
9th December 2024, 00:35
In the BD_Rebuilder directory

Soooooo, you can just run it by itself somehow...?

gonca
9th December 2024, 01:14
Soooooo, you can just run it by itself somehow...?

Yes, it has a gui just for you.:D

Lathe
9th December 2024, 01:22
Yes, it has a gui just for you.:D

Lovely... I have NO bloody idea what it does (except doesn't it have something to do with using your GPU to do the encoding? I don't know if I have the right kind. Raedon I think) but, I'll check it out.

If that is the case, I wonder what the benefit is rather then just using the CPU as usual? I've been pretty happy with the speed of the encodes now that I have a faster CPU and more memory, so I don't get why there is some whole other way to do it...?

gonca
9th December 2024, 02:11
It has to be a Nvidia gpu, radeon would be amd.

Lathe
9th December 2024, 02:47
It has to be a Nvidia gpu, radeon would be amd.

Yep, thought so...

MrVideo
9th December 2024, 03:37
It has to be a Nvidia gpu, radeon would be amd.
Or the Intel.

MrVideo
9th December 2024, 03:39
If that is the case, I wonder what the benefit is rather then just using the CPU as usual?
It is many times faster than using software (CPU) encoding.

Lathe
9th December 2024, 04:20
It is many times faster than using software (CPU) encoding.

Kinda figured that too... So, does it use the exact same parameters and yield the exact same quality as you would get using x264 settings and the CPU? Would the only different factor then just be the time of encoding?

varekai
9th December 2024, 09:05
In the BD_Rebuilder directory
Thanks!

varekai
9th December 2024, 09:06
Kinda figured that too... So, does it use the exact same parameters and yield the exact same quality as you would get using x264 settings and the CPU? Would the only different factor then just be the time of encoding?

From Google... maybe accurate?

In terms of bitrate efficiency, which encoding is better, software or hardware encoding?
For the best bitrate efficiency (quality per bitrate), software encoding tends to be superior due to its flexibility and ability to use advanced encoding techniques.
14 okt. 2024

Is it better to encode with GPU or CPU?
You almost always want to do GPU encoding for recordings if you have access to it because it minimizes CPU overhead.
However, CPU encoding technically produces more efficient compression (better quality at a given bitrate or lower bitrate at given quality).
19 dec. 2023

Is software or GPU rendering better?
The main attraction to software rendering is capability.
While hardware in GPU rendering is generally limited to its present capabilities, software rendering is developed with fully customizable programming, can perform any algorithm, and can scale across many CPU cores across several servers.

MrVideo
9th December 2024, 12:03
So, does it use the exact same parameters and yield the exact same quality as you would get using x264 settings and the CPU?
Different parameters. As indicated by varekai's posting, overall, software gives you more control. But takes a lot longer. Depending on the job, I'll do some x264 encoding, but it takes a lot longer. I'm not even set up to do x265 software encoding.

Lathe
9th December 2024, 23:42
From Google... maybe accurate?

In terms of bitrate efficiency, which encoding is better, software or hardware encoding?
For the best bitrate efficiency (quality per bitrate), software encoding tends to be superior due to its flexibility and ability to use advanced encoding techniques.
14 okt. 2024

Is it better to encode with GPU or CPU?
You almost always want to do GPU encoding for recordings if you have access to it because it minimizes CPU overhead.
However, CPU encoding technically produces more efficient compression (better quality at a given bitrate or lower bitrate at given quality).
19 dec. 2023

Is software or GPU rendering better?
The main attraction to software rendering is capability.
While hardware in GPU rendering is generally limited to its present capabilities, software rendering is developed with fully customizable programming, can perform any algorithm, and can scale across many CPU cores across several servers.

Thanks mate!

iambryanknowles
10th December 2024, 10:21
When encoding x264 720p 60fps, BDRB defaults to keyint=30, and with extended_gop goes up to keyint=60. Should't it be 60 and 120?

jdobbs
10th December 2024, 17:00
From Google... maybe accurate?

In terms of bitrate efficiency, which encoding is better, software or hardware encoding?
For the best bitrate efficiency (quality per bitrate), software encoding tends to be superior due to its flexibility and ability to use advanced encoding techniques.
14 okt. 2024

Is it better to encode with GPU or CPU?
You almost always want to do GPU encoding for recordings if you have access to it because it minimizes CPU overhead.
However, CPU encoding technically produces more efficient compression (better quality at a given bitrate or lower bitrate at given quality).
19 dec. 2023

Is software or GPU rendering better?
The main attraction to software rendering is capability.
While hardware in GPU rendering is generally limited to its present capabilities, software rendering is developed with fully customizable programming, can perform any algorithm, and can scale across many CPU cores across several servers.If I can give my humble opinion... yes, CPU encoding technically produces more efficient compression. That's mainly due to its ability to do multi-pass encoding. But even then the difference is minimal -- a few percentage points in output size savings at a comparable quality level.

I personally use the GPU to do all my encoding and use constant quality mode (CRF [x264/5], QVBR [Nvidia], or ICQ [Intel]). That way I know exactly what quality level I will get. The only down side to it is that the size isn't easy to predict as it depends on the quality you choose and the complexity of the source. But in BD-RB that is taken care of by the program with sampling and size prediction.

And, as mentioned earlier by MrVideo -- GPU encoding is many, many times faster than using the CPU.

varekai
11th December 2024, 11:56
If I can give my humble opinion...
That's interesting! Thanks for the info! Can I ask what NVIDIA GPU you use?
I have this Geforce RTX 4060 8GB and never tried encoding with it, next project I will try it with your settings.

jdobbs
11th December 2024, 22:13
That's interesting! Thanks for the info! Can I ask what NVIDIA GPU you use?
I have this Geforce RTX 4060 8GB and never tried encoding with it, next project I will try it with your settings.I have a GeForce GTX 1660.

If you look at this link (https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new) you'll see that your card has more capability than mine (like AV1 encoding). I would guess it is faster too.

MrVideo
12th December 2024, 05:43
I have this Geforce RTX 4060 8GB and never tried encoding with it, next project I will try it with your settings.
Nice card, but I can't get one. The driver is Win10/11.

Give the software a run and see what you think of the results.

varekai
13th December 2024, 09:43
@jdobbs
@MrVideo
Thanks for the link and info, will test with GPU on the next project.
Will run one encode with GPU and one with software/CPU and compare them.

SquallMX
16th December 2024, 01:48
Be aware GPU encoding is awful for grainy content. You should use software encoding with that kind of content.

Lathe
16th December 2024, 03:21
Be aware GPU encoding is awful for grainy content. You should use software encoding with that kind of content.

That's interesting... Although I don't have the right GPU to do it, it seems odd that whatever you are using to do the mechanics of encoding, I don't understand why whether the GPU does it or the CPU, aren't the math and computations exactly the same? Why are there different results...? Just curious...

musiclover
16th December 2024, 10:55
For a project I had to convert a music video clip from PAL to NTSC. I used GPUENCC with INTEL GPU. The resulting video was fine but the audio was out of sync and kept getting further out of sync. Then I changed GPUENCC to reencoding with NVIDIA GPU and the audio in the result was completely in sync but the video was somewhat stammering or stuttering. The length of the original file was 3:32 minutes. The INTEL GPU changed that to 3:41 minutes while the NVIDIA GPU kept the 3:32 intact.

----------------------
[12.16.24] GPU Reencoder v0.01.17
----------------------
[10.36.20]Start Job [1 of 1]
- Reencoding "6. David Gilmour with Romany Gilmour - Yes, I Have Ghosts (Official Music Video).mp4"
-- Using INTEL GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x1080, 25fps
-- Vid: H264 (AVC), No Resize, 23.976 fps, CQ 18
-- Aud: Intact (Keep Original), no reencode
-- Remuxing output with MKVMERGE
[10.36.56]Job Completed [1 of 1]
----------------------
[12.16.24] GPU Reencoder v0.01.17
----------------------
[10.49.52]Start Job [1 of 1]
- Reencoding "6. David Gilmour with Romany Gilmour - Yes, I Have Ghosts (Official Music Video).mp4"
-- Using NVIDIA GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x1080, 25fps
-- Vid: H264 (AVC), No Resize, 23.976 fps, CQ 18
-- Aud: Intact (Keep Original), no reencode
-- Remuxing output with MKVMERGE
[10.50.21]Job Completed [1 of 1]

jdobbs
16th December 2024, 16:22
Be aware GPU encoding is awful for grainy content. You should use software encoding with that kind of content.Interesting. I personally haven't had any issues with that any kind of content using GPU.

SquallMX
17th December 2024, 05:45
That's interesting... Although I don't have the right GPU to do it, it seems odd that whatever you are using to do the mechanics of encoding, I don't understand why whether the GPU does it or the CPU, aren't the math and computations exactly the same? Why are there different results...? Just curious...

No, software encoding is slower but can use more advanced/complex ways to save bits.

Interesting. I personally haven't had any issues with that any kind of content using GPU.

Try something like Ghostbusters (the original one), even at BD50 bitrate the output created by NVEnc looks denoised and has this pulsating effect, the one encoded with x265 is superior in every way.

Lathe
17th December 2024, 05:50
No, software encoding is slower but can use more advanced/complex ways to save bits.



Try something like Ghostbusters (the original one), even at BD50 bitrate the output created by NVEnc looks denoised and has this pulsating effect, the one encoded with x265 is superior in every way.

Ah, good to know, thanks! Now I don't feel like I'm missing out so much... :) For me, re-encoding to a BD25 (movie only) even with very strong but compatible settings might take the better part of two hours. A film that is smaller and doesn't need quite so high settings may take about 45 minutes, so that is fine with me.

jdobbs
17th December 2024, 18:05
For a project I had to convert a music video clip from PAL to NTSC. I used GPUENCC with INTEL GPU. The resulting video was fine but the audio was out of sync and kept getting further out of sync. Then I changed GPUENCC to reencoding with NVIDIA GPU and the audio in the result was completely in sync but the video was somewhat stammering or stuttering. The length of the original file was 3:32 minutes. The INTEL GPU changed that to 3:41 minutes while the NVIDIA GPU kept the 3:32 intact.

----------------------
[12.16.24] GPU Reencoder v0.01.17
----------------------
[10.36.20]Start Job [1 of 1]
- Reencoding "6. David Gilmour with Romany Gilmour - Yes, I Have Ghosts (Official Music Video).mp4"
-- Using INTEL GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x1080, 25fps
-- Vid: H264 (AVC), No Resize, 23.976 fps, CQ 18
-- Aud: Intact (Keep Original), no reencode
-- Remuxing output with MKVMERGE
[10.36.56]Job Completed [1 of 1]
----------------------
[12.16.24] GPU Reencoder v0.01.17
----------------------
[10.49.52]Start Job [1 of 1]
- Reencoding "6. David Gilmour with Romany Gilmour - Yes, I Have Ghosts (Official Music Video).mp4"
-- Using NVIDIA GPU for Video Encode
-- Collecting input file information...
-- Input : AVC, 1920x1080, 25fps
-- Vid: H264 (AVC), No Resize, 23.976 fps, CQ 18
-- Aud: Intact (Keep Original), no reencode
-- Remuxing output with MKVMERGE
[10.50.21]Job Completed [1 of 1]Unfortunately the resizing and syncing, etc, is done by NVENCC and QSVENCC (I think they use the FFMPEG libraries). You might want to try downloading a newer version of those and see if you have better luck.

musiclover
18th December 2024, 17:07
Unfortunately the resizing and syncing, etc, is done by NVENCC and QSVENCC (I think they use the FFMPEG libraries). You might want to try downloading a newer version of those and see if you have better luck.

The newer versions didn't do it for me. So I used the video from the INTEL GPU and combined that with the audio that I stretched with 104,27%. It gave a good result. It's a pity that I couldn't get GPUENCC to do it. But I understand that is up to QSVENCC. And the choppy video was the fault of NVENCC.

UPDATE

I found an other way to get it done. Using BD_RB with the hidden option IMPORT_PAL_TO_FILM=1. It gave an excellent result. And BD_RB did the stretching for me.

DeathStalker77
26th December 2024, 18:04
Hello!

I have tried the last 3 versions & the current beta version, with & without the add-ons, different versions of AVISynth, and using different encoders, but I still get the error message - PredictAndEncode() 00006 2803

Thank you for any assistance!!!

--- DS

musiclover
26th December 2024, 18:23
Hello!

I have tried the last 3 versions & the current beta version, with & without the add-ons, different versions of AVISynth, and using different encoders, but I still get the error message - PredictAndEncode() 00006 2803

Thank you for any assistance!!!

--- DS

You get this error when the source stream was encoded at a framerate that is not allowed in Blu-ray. Acceptable framerates are: 23.976, 24, 25, 29.97, 50, 59.94 -- even then some are only compliant with certain frame sizes.

DeathStalker77
26th December 2024, 18:55
You get this error when the source stream was encoded at a framerate that is not allowed in Blu-ray. Acceptable framerates are: 23.976, 24, 25, 29.97, 50, 59.94 -- even then some are only compliant with certain frame sizes.

So how can I fix it? I am just shy of being able to just burn it -- 24,963MiB vs disc size of 23,866MiB. Can that much be done with Overburn?

--- DS

jdobbs
26th December 2024, 21:46
Hello!

I have tried the last 3 versions & the current beta version, with & without the add-ons, different versions of AVISynth, and using different encoders, but I still get the error message - PredictAndEncode() 00006 2803

Thank you for any assistance!!!

--- DSI can tell you that it is an overflow error, and that it is probably happening while trying to calculate space requirements (based on the 2803 error locator code). But that's about it.

DeathStalker77
26th December 2024, 22:07
I can tell you that it is an overflow error, and that it is probably happening while trying to calculate space requirements (based on the 2803 error locator code). But that's about it.

There is more than enough space on the drive (over 100gb). It gets to ~93% Overall Progress. This was using FRIMSOURCE for Frame Serving (I've tried all the others except DGDecNV, as I do not have that exe). I have also tried AUTOMATIC QUALITY -


UPDATE: DoH! It was a bad file in the mix :-(

--- DS

Mark_Venture
29th December 2024, 20:02
Sorry if I missed it, but is it expected that GPUENCC/NVEncC removes DV/DoVi profile 7.6 (dvhe.07.06) when re-encoding video? Thankfully it does at least leave the HDR10 there.

Input file (ripped from disc using MakeMKV):

Video
ID : 1
ID in the original source medium : 4113 (0x1011)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, Profile 7.6, dvhe.07.06, BL+EL+RPU, no metadata compression, Blu-ray compatible / SMPTE ST 2086, Version HDR10, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 2 h 45 min
Bit rate : 65.2 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.328
Stream size : 75.1 GiB (90%)
Language : English
Default : No
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Original source medium : Blu-ray
Output file:
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 2 h 45 min
Bit rate : 38.0 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.191
Stream size : 43.9 GiB (84%)
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2

GPULASTCMD.TXT
"D:\BD-RBV06212\tools\nvenc\nvencc.exe" --avhw -i "C:\ReEncode\Transformers Age of Extinction\Transformers Age of Extinction {edition-4K Disc}.mkv" --codec h265 --preset default --profile main10 --output-depth 10 --chromaloc auto --colorprim auto --transfer auto --colormatrix auto --master-display copy --max-cll copy --qp-min 0 --multipass 2pass-full --vbr 0 --vbr-quality 21 --aq --aq-temporal --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --lookahead 24 --no-b-adapt --gop-len 24 --audio-copy 1 --audio-copy 2 --audio-copy 3 --audio-copy 4 --audio-copy 5 --sub-copy 1,2,3 --chapter-copy -o "C:\REENCODE\WORKING\Transformers Age of Extinction {edition-4K Disc}.mkv"

GPUREENC.LOG
----------------------
[12/29/24] GPU Reencoder v0.01.17
----------------------
[12:24:01]Start Job [1 of 1]
- Reencoding "Transformers Age of Extinction {edition-4K Disc}.mkv"
-- Using NVIDIA GPU for Video Encode
-- Collecting input file information...
-- Input : HEVC, 3840x2160, 23.976fps
-- Vid: H265 (HEVC), No Resize, Keep fps, CQ 21
-- Aud: Intact (Keep Original), no reencode
-- Remuxing output with MKVMERGE
[13:15:12]Job Completed [1 of 1]

iambryanknowles
31st December 2024, 10:20
The program hangs on trying to convert Opus audio.

MrVideo
4th January 2025, 12:05
I want BDRB to read in a disc and not re-encode any of the videos it will end up keeping. The following is in the config:
FORCE_NOENCODE=1
FORCE-ENCODE=0
Yet, BDRB goes ahead and encodes anyway. Is there something else that needs to be set?

gonca
4th January 2025, 13:11
FORCE_NOENCODE=1
FORCE-ENCODE=0


Try FORCE_ENCODE=0
If this doesn't work then post the log