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. |
21st January 2017, 13:51 | #82 | Link | |
Registered User
Join Date: Mar 2008
Posts: 448
|
Quote:
The copy-back operation shouldn't be that taxing. EDIT: If you have intel integrated GPU enabled (plus using windows 8/10)....you can select "QSVEncC (Intel)" as decoder. It turned out QSVENCC decoder supports MPEG2, H264, VC1 too. Note: Intel hardware decoder is the fastest compared to Nvidia and AMD. ~Using Intel IGPU decoder to pipe the decoded video to Nvidia Nvenc for encoding.~ Last edited by JohnLai; 21st January 2017 at 14:00. |
|
21st January 2017, 17:22 | #83 | Link | |||
Registered User
Join Date: Apr 2002
Location: Germany
Posts: 4,926
|
The TS Parser that Rigaya uses by default in Nvenc 3.02 makes me crazy.
it fails with Complete name : F:\hevc\10bit\fail wip\Samsung_UHD_Ride_on_Board.ts Format : MPEG-TS File size : 992 MiB Duration : 2 min 41 s Overall bit rate mode : Constant Overall bit rate : 51.6 Mb/s Video ID : 257 (0x101) Menu ID : 1 (0x1) Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main 10@L5.1@High Codec ID : 36 Duration : 2 min 40 s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate : 59.940 (60000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 10 bits Writing library : ATEME Titan KFE 3.6.2 (4.6.1.9) Audio ID : 258 (0x102) Menu ID : 1 (0x1) Format : AAC Format/Info : Advanced Audio Codec Format version : Version 4 Format profile : LC Muxing mode : ADTS Codec ID : 15 Duration : 2 min 40 s Channel(s) : 2 channels Channel positions : Front: L R Sampling rate : 48.0 kHz Frame rate : 46.875 FPS (1024 spf) Compression mode : Lossy Result on the mux side: Quote:
also ProRes seems not supported @ all Lets see if it works on 3.05 now by default uhhh Rigaya updated to Video Codec SDK 7.1.9 since 7.01 it seems seems 375.63 stopped working now and now 375.95 is minimum Glimpse of 8.0 coming ? Quote:
Quote:
Most important improvements where introduced already with 7.01
__________________
all my compares are riddles so please try to decipher them yourselves :) It is about Time Join the Revolution NOW before it is to Late ! http://forum.doom9.org/showthread.php?t=168004 Last edited by CruNcher; 21st January 2017 at 18:28. |
|||
21st January 2017, 18:20 | #84 | Link |
Registered User
Join Date: Mar 2008
Posts: 448
|
[@CruNcher]
Muxer error = Seem like there is a problem with the audio. If ffmpeg is being used...then -ar 48000 is used. In case of NVENCC, maybe --audio-samplerate 48000 ? NVENC SDK 7.1 requires NVIDIA Windows display driver 375.95 or newer. Last edited by JohnLai; 21st January 2017 at 18:33. |
21st January 2017, 18:33 | #85 | Link |
Registered User
Join Date: Apr 2002
Location: Germany
Posts: 4,926
|
Every muxer for Rigayas Nvenc TS input shows the same problem, very unreliable standalone and ProRes fails Decoding completely.
__________________
all my compares are riddles so please try to decipher them yourselves :) It is about Time Join the Revolution NOW before it is to Late ! http://forum.doom9.org/showthread.php?t=168004 Last edited by CruNcher; 21st January 2017 at 18:35. |
21st January 2017, 18:46 | #86 | Link |
Registered User
Join Date: Mar 2008
Posts: 448
|
Well....you could contact rigaya or create a ticket https://github.com/rigaya/NVEnc/issues about the parser issue.
|
21st January 2017, 19:37 | #87 | Link | |
Registered User
Join Date: Apr 2002
Location: Germany
Posts: 4,926
|
I'll do it when im sure 3.05 has still the same issue it looks like it copying the new ffmpeg library components to the 3.02 binary but i dunno how both are internally working together and before i can test 3.05 i need to change the driver and im very picky with driver changing overall (especially Nvidia Drivers since some strategy updates), even if it looks basically like a very small change going from 375.63 up to 375.95 being forced currently through this API change that seems to have happened with the 7.1 SDK.
I want to produce some test files first and compare if they really have been no noticeable bitstream differences on the HEVC side of things and some test files for H.264 as well looking at the overall improvements there. So far i found 1 visual issue on Nvidias Encoder side in form of Nvenc im overall not happy with it's visual retranscoding outcome for the Performance, especially not vs H.264 CPU but overall it doesn't do bad for UHD almost 50 fps realtime at reasonable bitrates, i mostly hit 30 fps though on GM204 If that result should have improved with the Driver update it would be really interesting Hmm it seems to work without --audio-copy so the direct copy transfer seems to fail interesting this is being shown when aborting the execution. [mp4 @ 00000000091fd680] sample rate not set avout: failed to write header for output file: Invalid argument Ignoring attempt to set invalid timebase 1/0 for st:1 encoded 0 frames, 0.00 fps, -nan(ind) kbps, 0.00 MB encode time 0:00:03 / CPU Usage: 75.59% @JohnLai you could be right it seems to be rather a muxer issue with that ADTS track, but then practicaly every muxer fails geez. with the default audio transcoding overhead ~0.5x Realtime and the internal 10->8bit conversion [26.2%] 2572 frames: 30.78 fps, 24654.49 kb/s, remain 0:03:55 https://devtalk.nvidia.com/default/t...am-correction/ hehe yeah funny though that the Encoder is as powerful as GM206 but the Decoder is Hybrid and pretty damn weak on the Performance GTX 970. So some files the Encoder creates most GM204 can't even Playback flawless but GM206 can And the part about the Decoding support in the Matrix doesn't fit either for it based on the Assumption that NVCUVID is now transformed to NVDEC Normally it should be as well shown as supported in the NVDEC Matrix even if heavier CPU Depending as on GM206 Quote:
__________________
all my compares are riddles so please try to decipher them yourselves :) It is about Time Join the Revolution NOW before it is to Late ! http://forum.doom9.org/showthread.php?t=168004 Last edited by CruNcher; 22nd January 2017 at 00:35. |
|
22nd January 2017, 04:15 | #88 | Link |
Registered User
Join Date: Mar 2008
Posts: 448
|
[@CruNcher]
30fps hevc encoding seems to be about right due to cpu decoding. Can't expect high quality visual transcoding from GM204 fixed function encoder. Encoder itself could handle 8bit HEVC 4k at 60fps just fine. Then again, not even core i7-3770k at 4.5ghz (nor my i5-3570k 4.2ghz) can decode the source 10bit HEVC 4K60 50Mbps without dropping frame. Very ironic indeed. However, there is a bug with color range for nvidia hevc encoding https://devtalk.nvidia.com/default/t...range-colors-/ This particular bug doesn't happen with H264. |
22nd January 2017, 11:59 | #89 | Link |
Registered User
Join Date: Apr 2002
Location: Germany
Posts: 4,926
|
I find it already visual very pleasing for the Performance it achieves and you shouldn't forget this is not yet a full GPU developed Video Codec, that thing is currently working only in Nvidias Lab
That Intel would beat it at even lower Power in every of their High End Notebooks @ around 35W is a really masterful architectural achievement that even AMD has a hard time to reach yet with their APU integration and Fusion idea (HSA) Im throwing currently around 150W out of the Gen2 System for that 30 fps result as much as for the Decoding actually @ flawless non dropping 60 fps @ around 70W It will be interesting to see what i can achieve with VP9 and AV1 at those 150W against Kyrion and Titan https://youtu.be/BaiPRAPOnjA?t=184
__________________
all my compares are riddles so please try to decipher them yourselves :) It is about Time Join the Revolution NOW before it is to Late ! http://forum.doom9.org/showthread.php?t=168004 Last edited by CruNcher; 22nd January 2017 at 13:02. |
22nd January 2017, 13:09 | #91 | Link |
Registered User
Join Date: Aug 2010
Location: Athens, Greece
Posts: 2,901
|
I've just read his email he sent me.
You are fast! He also wrote this: Details: https://github.com/rigaya/VCEEnc/releases/tag/3.00 "Please note that VCEEnc still lacks some features compared to QSVEnc/NVEnc, like HW HEVC decode or sw decoding by libavcodec." I'll try to post some encodings later today.
__________________
Win 10 x64 (19042.572) - Core i5-2400 - Radeon RX 470 (20.10.1) HEVC decoding benchmarks H.264 DXVA Benchmarks for all |
22nd January 2017, 13:44 | #92 | Link |
Registered User
Join Date: Apr 2002
Location: Germany
Posts: 4,926
|
Please try todo the best retranscode you can of Samsungs Journey of Colors in 8 bit and a target of 25 Mbps
gona release my test result shortly in the Decoder Evaluation thread of it encoded 6646 frames, 32.25 fps, 22602.53 kbps, 298.75 MB encode time 0:03:26 / CPU Usage: 72.36% frame type IDR 31 frame type I 31, avgQP 23.48, total size 15.90 MB frame type P 6615, avgQP 28.70, total size 282.85 MB Format : MPEG-4 Format profile : Base Media / Version 2 Codec ID : mp42 (isom/iso2/mp41) File size : 299 MiB Duration : 1 min 50 s Overall bit rate : 22.6 Mb/s Writing application : NVEncC (x64) 3.02 Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main@L5@High Codec ID : hev1 Codec ID/Info : High Efficiency Video Coding Duration : 1 min 50 s Bit rate : 22.6 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 59.940 (60000/1001) FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.045 Stream size : 299 MiB (100%) after testing the new Driver result and comparing it
__________________
all my compares are riddles so please try to decipher them yourselves :) It is about Time Join the Revolution NOW before it is to Late ! http://forum.doom9.org/showthread.php?t=168004 Last edited by CruNcher; 22nd January 2017 at 14:06. |
22nd January 2017, 13:46 | #93 | Link | |
Registered User
Join Date: Mar 2008
Posts: 448
|
Quote:
EDIT: One can use directshow filter in conjunction with LAVfilter DXVA Copy back to get hardware acceleration decode and piping it to vceencc. EDIT2: Don't forget to use "--quality slow" and "--pre-analysis auto". You know, cause last time intel TU has different min/max rectangle partitions for each target usage. Worry if AMD also has same issue. Last edited by JohnLai; 22nd January 2017 at 13:50. |
|
22nd January 2017, 14:31 | #94 | Link | |
Registered User
Join Date: Nov 2002
Posts: 93
|
Quote:
Pitou! |
|
22nd January 2017, 14:51 | #95 | Link | |
Registered User
Join Date: Apr 2002
Location: Germany
Posts: 4,926
|
Quote:
And Amd is lacking behind on UVD/VCE they just started to keep up Mikhail has a interesting Background as a PMTS https://www.youtube.com/watch?v=6GncOvnc_S0 MTUCI not MSU
__________________
all my compares are riddles so please try to decipher them yourselves :) It is about Time Join the Revolution NOW before it is to Late ! http://forum.doom9.org/showthread.php?t=168004 Last edited by CruNcher; 22nd January 2017 at 15:14. |
|
22nd January 2017, 15:24 | #96 | Link | |
Registered User
Join Date: Mar 2008
Posts: 448
|
Quote:
Because almost all reddit users at /AMD actually believe Polaris has 10bit HEVC encoding support. ~.~...... |
|
22nd January 2017, 15:27 | #97 | Link | |||
Registered User
Join Date: Aug 2010
Location: Athens, Greece
Posts: 2,901
|
Quote:
Give me a link for the above clip. Quote:
I urgently suggest you to open a new thread here in Doom9 regarding GPU/HW encoding of H.264/ H.265 for all (AMD, Nvidia, Intel) You are the most suitable guy to do that, since you dedicate a lot of hours testing, reading, evaluating mostly Nvidia HW encoders but also you are clearly interested in all HW encoders. You are very helpful and detailed suggesting solutions to users and you will get a lot of feedback because I think HW encoding is a trend right now. That thread is clearly missing from doom9. Go on and we will all contribute to that, starting from my results of Polaris HEVC encoding Quote:
It would be much better to do it in the new thread regarding HW encoding that JohnLai will open soon
__________________
Win 10 x64 (19042.572) - Core i5-2400 - Radeon RX 470 (20.10.1) HEVC decoding benchmarks H.264 DXVA Benchmarks for all |
|||
22nd January 2017, 15:37 | #98 | Link | |
Registered User
Join Date: Mar 2008
Posts: 448
|
Quote:
Speaking of H264....seem like only Intel IGPU (haswell onwards) and AMD VCE (except Polaris) support b-pyramid. Nvidia never support b-pyramid. I wonder why. |
|
22nd January 2017, 15:41 | #99 | Link |
Registered User
Join Date: Aug 2010
Location: Athens, Greece
Posts: 2,901
|
It is exactly your specialty, at least from all the users writing here.
And what do you mean specialty ? We aren't exactly professionals, we only want to help users. Come on! You are the best on HW encoding and you don't have to know everything. Just make the beginning and all the rest will follow.
__________________
Win 10 x64 (19042.572) - Core i5-2400 - Radeon RX 470 (20.10.1) HEVC decoding benchmarks H.264 DXVA Benchmarks for all |
22nd January 2017, 15:44 | #100 | Link |
Registered User
Join Date: Dec 2008
Posts: 589
|
This VCEEnc 3.0 actually works on my Windows 7 machine, with my XFX RX 470 card. A's video converter didn't show the HEVC option.
So if you want me to do some test, paste the command line and a link to the sample input file (if any particular one is desired) and I can do tests for you guys. I did a test encode of a 1280x536 5mbps vbr ~1min video and it encoded it at around 135 fps 1600 kbps ... it was the absolute minimum command line parameters to get it to work, like -c hevc --avcee (or something like that) -i file.mp4 -o file.hevc |
Thread Tools | Search this Thread |
Display Modes | |
|
|