Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
17th July 2021, 22:34 | #30742 | Link |
Registered User
Join Date: Mar 2009
Posts: 129
|
I redid The Good, Bad & Ugly. here are the results. Success!
.ini: (Do not reencode AC3 checked)... Code:
[Options] VERSION=0.61.0.22 ENCODER=1 MODE=3 ENCODE_QUALITY=2 ONEPASS_ENCODING=2 AUTO_QUALITY=0 NVENC_CAPABLE=1 TARGET_SIZE=23500 AUDIO_TO_KEEP=eng; SUBS_TO_KEEP=eng; SD_CONVERT=0 OPEN_GOP=0 RESIZE_1080=0 RESIZE_1440=0 RESIZE_720=0 DEINTERLACE=1 SD_TO_1080=0 IGNORE_3D=0 CONVERT_WIDE=0 DTS_REENCODE=1 AC3_REENCODE=0 AC3_640=1 AC3_192=0 KEEP_HD_AUDIO=0 AUDIO_DRC=0 DECODER=3 AVCHD=0 REMOVE_WORKFILES=0 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=0 SUPTITLE=0 PGSTOSRT=0 AUDIO_TRACK_LIMIT=1 SUBTITLE_TRACK_LIMIT=0 CUSTOM_TARGET_SIZE=20480 MOVIE_ONLY_LOOP=0 ENABLE_TEST=1 ENABLE_BLANKING=1 BLANK_THRESHOLD=1800 MULTIPROCESS=1 BEEP_SOUNDFILE=C:\Windows\Media\tada.wav UHD_CONVERT_ENABLE=1 UHD_ALL_MODE=1 MOVIEONLY_TYPE=0 UHD_V3_MODE=1 FORCE_NOENCODE=0 [Paths] DGIndexNV=C:\Users\eM-SSD\Downloads\dgdecnv2053v228\x32 Binaries\DGIndexNV.exe DGDecNV=C:\Users\eM-SSD\Downloads\dgdecnv2053v228\x32 Binaries\DGDecodeNV.dll SOURCE_PATH=N:\ WORKING_PATH=C:\USERS\EM-SSD\VIDEOS\1080P_HEVC\ Code:
[07/17/21] BD Rebuilder v0.61.22 [08:30:45] Source: THE_GOOD_THE_BAD_AND_THE_UGLY_00800 - Input BD size: 39.98 GB - Approximate total content: [02:58:36.622] - Target BD size: 22.95 GB - Windows Version: 6.2 [9200] - MOVIE-ONLY mode enabled - Quality: High Quality (Default), 1-Pass VBR - Decoding/Frame serving: NVENCC - Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640 [08:30:45] PHASE ONE, Encoding - [08:30:45] Processing: VID_01559 (1 of 1) - [08:30:45] Extracting A/V streams [VID_01559] - [08:38:46] Reencoding video [VID_01559] - Source Video: MPEG-4 (AVC), 1920x1080 - Rate/Length: 23.976fps, 256,942 frames - Bitrate: 15,731 Kbs - [08:38:46] Reencoding: VID_01559, Pass 1 of 1 - [09:01:30] Video Encode complete - [09:01:30] Processing audio tracks - Track 4352 (eng): Reencoding audio to AC3... [09:05:26]PHASE ONE complete [09:05:26]PHASE TWO - Rebuild Started - [09:05:26] Rebuilding BD file Structure [09:06:03] - Encode and Rebuild complete [09:06:03] JOB: THE_GOOD_THE_BAD_AND_THE_UGLY finished. Code:
Audio ID : 4352 (0x1100) Menu ID : 1 (0x1) Format : AC-3 Format/Info : Audio Coding 3 Commercial name : Dolby Digital Codec ID : 129 Duration : 2 h 58 min Bit rate mode : Constant Bit rate : 640 kb/s Channel(s) : 6 channels Channel layout : L R C LFE Ls Rs Sampling rate : 48.0 kHz Frame rate : 31.250 FPS (1536 SPF) Compression mode : Lossy Stream size : 818 MiB Language : English Service kind : Complete Main bsid : 8 Dialog Normalization : -31 Dialog Normalization : -31 dB acmod : 7 lfeon : 1 dialnorm_Average : -31 dialnorm_Average : -31 dB dialnorm_Minimum : -31 dialnorm_Minimum : -31 dB dialnorm_Maximum : -31 dialnorm_Maximum : -31 dB dialnorm_Count : 2242 format_identifier : AC-3 Source : 00000.m2ts / 00000.m2ts |
17th July 2021, 22:41 | #30743 | Link |
Registered User
Join Date: Mar 2009
Posts: 129
|
Me too!!! "If at first you don't succeed, keep on suckin' till you do suck seed!"
-Curley Howard... https://youtu.be/SZSGvu8foRE Last edited by spotswood; 20th July 2021 at 01:24. Reason: link to video... |
19th July 2021, 23:08 | #30746 | Link | |
Registered User
Join Date: Aug 2005
Posts: 1,100
|
Quote:
|
|
19th July 2021, 23:19 | #30747 | Link |
Registered User
Join Date: Aug 2005
Posts: 1,100
|
Okay, now that the compulsive silliness is outta the way...
I am currently reencoding a Blu-ray that is about 31 Gigs. Since it is a bit bigger than most, I'm using Default 2 Pass with some x264 tweaks that I normally use in a case like this. Since you, JD, had said that the difference in the x264-64.exe and the x264L-64.exe is the non 'L' is the current version or an updated version that will run better with the DirectShow frame server as opposed to the internal LAV one. So, I switched to using the DirectShow figuring I'm using the newest, fasted version of x264, right? However, I checked my TM during the first pass, and it is showing just the x264.exe being used and NOT the x264-64.exe...??? Why? I am not currently using any Avisynth. Why is BDRB using the NON-64 version? Thanks! |
20th July 2021, 09:23 | #30749 | Link | |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,890
|
Quote:
__________________
BeHappy, AviSynth audio transcoder. |
|
20th July 2021, 15:45 | #30750 | Link |
Moderator
Join Date: Oct 2001
Posts: 20,973
|
Well... NVENCC was updated to version 5.20 in that release, so I guess there could be some compile issue (although I haven't had any other reports of issues). In looking up the reported error, this is what I got:
Code:
cudaErrorUnsupportedPtxVersion = 222 This indicates that the provided PTX was compiled with an unsupported toolchain. The most common reason for this, is the PTX was generated by a compiler newer than what is supported by the CUDA driver and PTX JIT compiler. I don't think I understand the issue with the post.... why was it hidden, and why would it require approval? Last edited by jdobbs; 20th July 2021 at 15:52. |
20th July 2021, 23:11 | #30751 | Link | |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,890
|
Quote:
__________________
BeHappy, AviSynth audio transcoder. |
|
22nd July 2021, 13:20 | #30752 | Link |
Registered User
Join Date: Nov 2013
Posts: 38
|
OK here's an issue I would like some help with
I have a Blu-Ray (30GB) with 4 audio tracks (all Eng) : Music 192-24 PCM Stereo 48-24 PCM Stereo 192-24 DTS HD-MA 5.1 48-24 Dolby Atmos Now if I choose to keep HD Audio, it can't shrink enough to fit a BD25 If I re-encode to AC3 I get a 8GB disc What I would like to do is some where inbetween, say, keep 1 of the HD tracks and re-encode the other 3 How would I go about this? TIA Wally |
22nd July 2021, 13:33 | #30753 | Link | |
Life's clearer in 4K UHD
Join Date: Jun 2003
Location: Notts, UK
Posts: 12,219
|
Quote:
__________________
| I've been testing hardware media playback devices and software A/V encoders and decoders since 2001 | My Network Layout & A/V Gear |
|
|
24th July 2021, 10:31 | #30756 | Link |
Life's clearer in 4K UHD
Join Date: Jun 2003
Location: Notts, UK
Posts: 12,219
|
Hmmm... I don't think I have any Blu-ray audio discs with multi-channel DTS-HD MA audio encoded at 192KHz/24-bit. I do have some encoded with Dolby TrueHD and PCM though...
__________________
| I've been testing hardware media playback devices and software A/V encoders and decoders since 2001 | My Network Layout & A/V Gear |
Last edited by SeeMoreDigital; 24th July 2021 at 10:52. |
30th July 2021, 02:28 | #30758 | Link | |
Registered User
Join Date: Jun 2021
Posts: 10
|
Thanks jdobbs,
So I tried the link. I used the 32 bit version of nvencc. No joy, same error. I took the nvencc version from 61.21, and put it in the 61.22 folder, and it works. So, I'm guessing that those of us using windows 8.1, are pretty much out of luck on this? What are my options really? My daily driver is fedora linux, but I did compile ffmpeg a few years ago to be able to take advantage of some features I wanted specifically for my htpc, but I don't have that VM that I used to cross compile any longer. I guess another option is to use the older version of nvencc, but the encode seemed to have some artifact issues compared to the cpu encode I did of the same movie. Lastly, I suppose, I would be forced to use the cpu for encoding otherwise right? Anything I'm not looking at? Any options I'm not seeing? I suppose I could ask on github, but honestly, most devs now are into removing support of older systems, for a myriad of reasons. Thanks again, and hopefully the admins get this posting thing resolved so I don't have to go through the approval process to post anything any longer. Lastly, I suppose, I would be forced to use the cpu for encoding otherwise right? Anything I'm not looking at? Any options I'm not seeing? I suppose I could ask on github Quote:
Last edited by user404; 30th July 2021 at 02:49. Reason: I had a quote twice in it, |
|
30th July 2021, 07:09 | #30759 | Link |
Registered User
Join Date: Jun 2021
Posts: 10
|
Good news,
I realized although it isn't listed, the windows 7 and windows 8 driver for the 1660 are essentially the same. Although Windows update won't go past a really old version for 8.1, you can manually update. Of course I'm still stuck on API 11 though, but it is something. So now, I have nvidia 471 driver installed. After I updated, I reran 61.22 with the latest nvencc (the one provided on the link since it was already in place). This failed, but I got a different and strange error. So, I looked up and ran the last command. After playing around a bit, I discovered that if I removed --avs, it not only ran, but it was smoking my GPU, pegging it at 90% for a majority of the encode while leaving my cpu pretty low, between 15 and 30% usage. I went back to playing with the BDRB settings. Once I unselect "use X264's internal LAVF for frame serving" and choose "Use directShowSource for frameserving" it worked, BDRB 61.22 would correctly run and status. The backup started and completed. However, After seeing how when I run it manually, it pegs my GPU to >90%, I don't think this was correctly using my GPU. In fact, most of the time running from the BDRB GUI the CPU was pegged at 100% and my GPU was around 30-40%. I then went back to the original nvencc and files that go with 61.22 natively, and everything was the same. As long as my decoding frame server stayed on DirectShowSource it worked fine. However, the CPU usage was high for the entire encode, and GPU usage was very low, so I'm wondering if it is actually using my GPU. Plus, to be honest, on the encodes I was doing previously, I had a lot of artifacts while using "nvencc" on v61.21. The newest one looked really good, which makes me believe it might be doing a CPU encode. Anyone have any ideas? |
30th July 2021, 13:15 | #30760 | Link |
Moderator
Join Date: Oct 2001
Posts: 20,973
|
@user404
When encoding, there are times when you have to use AVISYNTH to modify the source in order to make it compliant (--avs). There are also some settings available in SETUP that require it. When I implemented NVENCC I added checks so that whenever possible it would use the GPU to perform those functions (eliminating the AVISYNTH requirement). But AVISYNTH is very powerful, and sometimes there is no choice except to use it (performing functions that aren't available on the GPU). When that is the case, you'll see the GPU usage drop and the CPU usage go up. If I read your posts correctly, it looks like you're running BD-RB on a VM under Linux, is that right? If so, I have to say that running software that works closely with hardware (like NVENCC) can run into issues when implemented on a virtual machine. That makes compatibility a little hard to ensure, and very difficult to debug. You never know when an issue is related to the software or the VM environment. If you're not running it on a VM, then ignore this paragraph. Last edited by jdobbs; 30th July 2021 at 13:27. |
Thread Tools | Search this Thread |
Display Modes | |
|
|