Hardware-forbrug - lav %

[SoNic67]

Jeg prøver den nyeste prøveversion, og jeg har et spørgsmål om den generelle brug.
Ved konvertering af en wtv-fil til mp4 ved hjælp af Nvidia-hardwarekoderen ser det ikke ud til, at den bruger den med maksimal kapacitet. Er det normalt?
Mere præcist er forbruget:
CPU 10-33%
GPU 12% - Video Encode (nvenc)
GPU 6% - CUDA-kerner
Netværk 5,6 Mbps (fra 1 Gbps)

[Will_Tschumy]

Hvilken codec konverterer du til? Jeg tror, du går fra h264 til h264…

[SoNic67]

Jeg tror, at WTV er MPEG2 (HD på FIOS kabel-tv) til H264. Det er standard WTV-profilen.

[SoNic67]

Jeg har muligvis gjort noget forkert. Hvis jeg vælger ikke at fjerne reklamerne, bliver de resulterende filer større end originalerne. Det ser ud til, at “kvaliteten” for h264-koderen er 10… hmmm

2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] job configuration:
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] * source
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + D:\Temp\working0\Airplane!_BBCAHD_2019_06_07_18_59_00.ts
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + title 1, chapter(s) 1 to 1
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] * destination
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + D:\Temp\working0\Airplane!_BBCAHD_2019_06_07_18_59_00-converted.mp4
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + container: MPEG-4 (libavformat)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] * video track
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + decoder: mpeg2video
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + bitrate 200 kbps
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + filters
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + Decomb (mode=7)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + Denoise (hqdn3d) (y-spatial=3:cb-spatial=2:cr-spatial=2:y-temporal=2:cb-temporal=3:cr-temporal=3)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + Output geometry
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + storage dimensions: 1920 x 1080
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + pixel aspect ratio: 1 : 1
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + display dimensions: 1920 x 1080
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + encoder: H.264 (NVEnc)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + quality: 10.00 (CQ)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + color profile: 1-1-1
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] * audio track 1
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + decoder: English (AC3) (5.1 ch) (384 kbps) (track 1, id 0x100)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + bitrate: 384 kbps, samplerate: 48000 Hz
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + mixdown: 5.1 Channels
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + dynamic range compression: 2.500000
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + dither: triangular
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + encoder: AC3 (libavcodec)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] + bitrate: 384 kbps, samplerate: 48000 Hz
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] file is MPEG Transport Stream with 188 byte packets offset 0 bytes
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] sync: expecting 218380 video frames
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] thread 24 started (“Audio Synchronization”)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] encavcodecInit: H.264 (Nvidia NVENC)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] encavcodec: encoding at rc=vbr 10.00
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] encavcodec: encoding with stored aspect 1/1
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → Encoding: task 1 of 1, 0.00 %[19:15:35] Writing Metadata to output file…
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] thread 25 started (“Muxer”)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] thread 26 started (“Reader”)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] thread 27 started (“Audio decoder (libavcodec)”)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] thread 28 started (“Video decoder (libavcodec)”)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] thread 29 started (“Video Synchronization”)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] thread 2a started (“AVCodec Audio encoder (libavcodec)”)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] thread 2b started (“FFMPEG encoder (libavcodec)”)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] thread 2c started (“Muxer”)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] thread 2d started (“Decomb”)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [19:15:35] thread 2e started (“Denoise (hqdn3d)”)
2019-12-21T19:15:35 MCEBuddy.AppWrapper.Handbrake → [mpeg2video @ 000000000770cb00] Application has requested 17 threads. Using a thread count greater than 16 is not recommended.

[SoNic67]

Filstørrelsen er relateret til kvalitetsindstillingerne, så det er ikke relateret til trådomfanget selv.

Så… hvorfor er GPU- og CPU-forbruget så lavt under videokonverteringsfasen?

[Goose]

Afhænger af de videofiltre, der bruges i profilen, og hardwarens kapaciteter. Ikke al hardware understøtter alle filtre, så det ender med at bruge CPU’en til disse behandlingsaktiviteter. Fjern alle filtre fra profilen, hvis du vil bruge mere hardware (på bekostning af kvalitet). Se disse emner:

Not sure if hardware encoding is working or not

It depends on what options and filters are being used in the profile you’re using. Not all adapters support all options. For example if the profile is using a denoise filter to clean up artifacts and if you’re hardware doesn’t support it then it’ll use the CPU to do that part. If you want to use only the GPU then you’ll have to build a custom profile specific to your GPU capabilities only and remove all other options. MCEBuddy uses hardware acceleration to assist and speed up encoding without c…

Video conversion performance question

That sounds about right, the performance can depend on what filters your profile is using to process the video. Maybe @Will_Tschumy @techpro2004 can share their experiences

[SoNic67]

Nå, OK, jeg kan godt se, hvordan filtre kan påvirke det, da de ikke behandles af GPU. Jeg har ikke nogen filtre, jeg kender til, men jeg er nødt til at undersøge det nærmere; jeg har valgt standardprofilen for “Convert to MP4” i WTV-container.

Hvis CPU’en alligevel var flaskehalsen, hvorfor udnyttes den så ikke til 100 %? Jeg har flere kerner end de fleste computere (16 fysiske, 32 virtuelle med HT); er det en skaleringsproblematik? Er softwaren begrænset til et bestemt antal kerner?