View Profile
View Forum Posts
Private Message
You have this backwards. You adjust the monitor to standard video levels. Then you adjust your VHS caps to those standard levels.Originally Posted by vhelp
Start by adjusting the black/white levels. This post has a levels test pattern you can use for that:Originally Posted by vhelp
https://forum.videohelp.com/threads/374734-Color-Levels-Question?p=2414529&viewfull=1#post2414529
Download the MPG file and play it. Make sure the player isn't messing up the video -- disable any proc amp or other filters of the player. Then adjust the graphics card's video proc amp until blacks are as black as your display can get, and whites are are as bright as you want the monitor to display (generally you do this by adjusting the backlight). Then adjust the proc amp controls so the video chart looks like the second image in the above post.
Note that cheap LCD monitors can't display very dark blacks. You may have to settle for a dark grey.
And you usually want to turn off all "auto" adjustments of the graphics card and player. That is, turn off anything like auto contrast, auto color, auto skin tone, etc. Also disable any noise reduction, deblocking, sharpening and other "enhancements". All those things do is mess up your video. You want to see what your video really looks like, not some caricature created by the player or graphics card.
Try StreamFab Downloader and download from Netflix, Amazon, Youtube! Or Try DVDFab and copy Blu-rays! or rip iTunes movies!
+ Reply to Thread
Results 61 to 90 of 135
Thread
-
Last edited by jagabo; 19th Oct 2016 at 09:39.
-
Note: I move the discussion about the LCD monitor issue here:
https://forum.videohelp.com/threads/374734-Color-Levels-Question?p=2463439&viewfull=1#post2463439
Here are the specs for the dell-i7-6700 work pc
http://ark.intel.com/products/88196/Intel-Core-i7-6700-Processor-8M-Cache-up-to-4_00-GHz
and the specs for the x265 encoder: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2 FMA3 LZCNT BMI2
--preset slow @ 12fps
Code:--crf 20 --frames 1619 --rdoq-level 1 --min-keyint 23 --keyint 240 --aq-mode 1 --pmode --profile main10 --level-idc 4 --deblock -3:-3 --psy-rd 0.5 yuv [info]: 720x480 fps 24000/1001 i420p8 unknown frame count raw [info]: output file: i:\videos\video.2.0.045.20161018tue.PV-4662.matrix.A.02.crf.20.LQ.slow.hevc x265 [info]: HEVC encoder version 2.0+45-7f9aeed70c0d x265 [info]: build info [Windows][GCC 5.3.0][64 bit] 10bit x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2 FMA3 LZCNT BMI2 x265 [warning]: Limit reference options 2 and 3 are not supported with pmode. Disabling limit reference x265 [warning]: Specifying a decoder level with constant rate factor rate-control requires x265 [warning]: enabling VBV with vbv-bufsize=30000kb vbv-maxrate=30000kbps. VBV outputs are non-deterministic! x265 [info]: Main 10 profile, Level-4 (High tier) x265 [info]: Thread pool created using 8 threads x265 [info]: Slices : 1 x265 [info]: frame threads / pool features : 3 / wpp(8 rows)+pmode x265 [warning]: Source height < 720p; disabling lookahead-slices x265 [info]: Coding QT: max CU size, min CU size : 64 / 8 x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra x265 [info]: ME / range / subpel / merge : star / 57 / 3 / 3 x265 [info]: Keyframe min / max / scenecut : 23 / 240 / 40 x265 [info]: Lookahead / bframes / badapt : 25 / 4 / 2 x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0 x265 [info]: References / ref-limit cu / depth : 4 / off / off x265 [info]: AQ: mode / str / qg-size / cu-tree : 1 / 1.0 / 32 / 1 x265 [info]: Rate Control / qCompress : CRF-20.0 / 0.60 x265 [info]: VBV/HRD buffer / max-rate / init : 30000 / 30000 / 0.900 x265 [info]: tools: rect limit-modes rd=4 psy-rd=0.50 rdoq=1 psy-rdoq=1.00 x265 [info]: tools: rskip signhide tmvp strong-intra-smoothing x265 [info]: tools: deblock(tC=-3:B=-3) sao [ 0.1%] 1/1619 frames, 1.11 fps,1285.79 kb/s, eta 0:24:16 [ 0.3%] 5/1619 frames, 4.15 fps, 666.63 kb/s, eta 0:06:28 [ 0.5%] 8/1619 frames, 5.44 fps, 628.34 kb/s, eta 0:04:56 [ 0.7%] 11/1619 frames, 6.34 fps, 618.84 kb/s, eta 0:04:13 [ 0.9%] 14/1619 frames, 6.89 fps, 598.29 kb/s, eta 0:03:52 . . . [98.9%] 1601/1619 frames, 12.31 fps, 553.82 kb/s, eta 0:00:01 [99.1%] 1605/1619 frames, 12.32 fps, 554.32 kb/s, eta 0:00:01 [99.3%] 1608/1619 frames, 12.31 fps, 554.39 kb/s, eta 0:00:00 [99.6%] 1612/1619 frames, 12.32 fps, 554.13 kb/s, eta 0:00:00 [99.8%] 1616/1619 frames, 12.32 fps, 554.05 kb/s, eta 0:00:00 x265 [info]: frame I: 22, Avg QP:20.07 kb/s: 2202.97 x265 [info]: frame P: 375, Avg QP:22.09 kb/s: 1258.50 x265 [info]: frame B: 1222, Avg QP:26.19 kb/s: 337.96 x265 [info]: Weighted P-Frames: Y:4.8% UV:3.5% x265 [info]: consecutive B-frames: 5.8% 1.0% 5.5% 54.9% 32.7% encoded 1619 frames in 131.13s (12.35 fps), 576.52 kb/s, Avg QP:25.15
--preset placebo 1.6fps
Code:yuv [info]: 720x480 fps 24000/1001 i420p8 unknown frame count raw [info]: output file: c:\videos\video.2.0.045.20161018tue.PV-4662.matrix.A.03.crf.20.LQ.placebo.hevc x265 [info]: HEVC encoder version 2.0+45-7f9aeed70c0d x265 [info]: build info [Windows][GCC 5.3.0][64 bit] 10bit x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2 FMA3 LZCNT BMI2 x265 [warning]: Specifying a decoder level with constant rate factor rate-control requires x265 [warning]: enabling VBV with vbv-bufsize=30000kb vbv-maxrate=30000kbps. VBV outputs are non-deterministic! x265 [info]: Main 10 profile, Level-4 (High tier) x265 [info]: Thread pool created using 8 threads x265 [info]: Slices : 1 x265 [info]: frame threads / pool features : 3 / wpp(8 rows)+pmode x265 [info]: Coding QT: max CU size, min CU size : 64 / 8 x265 [info]: Residual QT: max TU size, max depth : 32 / 4 inter / 4 intra x265 [info]: ME / range / subpel / merge : star / 92 / 5 / 5 x265 [info]: Keyframe min / max / scenecut : 23 / 240 / 40 x265 [info]: Lookahead / bframes / badapt : 60 / 8 / 2 x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 1 x265 [info]: References / ref-limit cu / depth : 5 / off / off x265 [info]: AQ: mode / str / qg-size / cu-tree : 1 / 1.0 / 32 / 1 x265 [info]: Rate Control / qCompress : CRF-20.0 / 0.60 x265 [info]: VBV/HRD buffer / max-rate / init : 30000 / 30000 / 0.900 x265 [info]: tools: rect amp rd=6 psy-rd=0.50 rdoq=1 psy-rdoq=1.00 tskip x265 [info]: tools: signhide tmvp b-intra strong-intra-smoothing x265 [info]: tools: deblock(tC=-3:B=-3) sao [ 0.1%] 1/1619 frames, 0.59 fps, 1343.02 kb/s, eta 0:45:50 [ 0.1%] 2/1619 frames, 0.96 fps, 1270.24 kb/s, eta 0:27:56 [ 0.2%] 3/1619 frames, 1.25 fps, 1040.95 kb/s, eta 0:21:33 [ 0.2%] 4/1619 frames, 1.46 fps, 836.97 kb/s, eta 0:18:28 [ 0.3%] 5/1619 frames, 1.60 fps, 718.26 kb/s, eta 0:16:47 . . . [99.6%] 1613/1619 frames, 1.66 fps, 519.83 kb/s, eta 0:00:03 [99.7%] 1614/1619 frames, 1.66 fps, 519.87 kb/s, eta 0:00:03 [99.8%] 1615/1619 frames, 1.66 fps, 519.69 kb/s, eta 0:00:02 [99.8%] 1616/1619 frames, 1.66 fps, 519.55 kb/s, eta 0:00:01 [99.9%] 1617/1619 frames, 1.66 fps, 519.61 kb/s, eta 0:00:01 x265 [info]: frame I: 22, Avg QP:19.96 kb/s: 2242.98 x265 [info]: frame P: 335, Avg QP:22.84 kb/s: 1257.03 x265 [info]: frame B: 1262, Avg QP:26.36 kb/s: 320.69 x265 [info]: Weighted P-Frames: Y:3.9% UV:2.4% x265 [info]: Weighted B-Frames: Y:3.6% UV:2.6% x265 [info]: consecutive B-frames: 7.0% 1.4% 2.8% 47.3% 16.5% 16.8% 3.9% 2.8% 1.4% encoded 1619 frames in 975.02s (1.66 fps), 540.56 kb/s, Avg QP:25.54
--preset ultrafast @ 157fps
I don't know, but does this seem slow for a 720x480 source for this cpu ?Code:yuv [info]: 720x480 fps 24000/1001 i420p8 unknown frame count raw [info]: output file: c:\videos\video.2.0.045.20161018tue.PV-4662.matrix.A.03.crf.20.LQ.ultrafast.hevc x265 [info]: HEVC encoder version 2.0+45-7f9aeed70c0d x265 [info]: build info [Windows][GCC 5.3.0][64 bit] 10bit x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2 FMA3 LZCNT BMI2 x265 [warning]: Specifying a decoder level with constant rate factor rate-control requires x265 [warning]: enabling VBV with vbv-bufsize=30000kb vbv-maxrate=30000kbps. VBV outputs are non-deterministic! x265 [info]: Main 10 profile, Level-4 (High tier) x265 [info]: Thread pool created using 8 threads x265 [info]: Slices : 1 x265 [info]: frame threads / pool features : 3 / wpp(15 rows)+pmode x265 [warning]: Source height < 720p; disabling lookahead-slices x265 [info]: Coding QT: max CU size, min CU size : 32 / 16 x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra x265 [info]: ME / range / subpel / merge : dia / 57 / 0 / 2 x265 [info]: Keyframe min / max / scenecut : 23 / 240 / 0 x265 [info]: Lookahead / bframes / badapt : 5 / 3 / 0 x265 [info]: b-pyramid / weightp / weightb : 1 / 0 / 0 x265 [info]: References / ref-limit cu / depth : 1 / off / off x265 [info]: AQ: mode / str / qg-size / cu-tree : 1 / 0.0 / 32 / 1 x265 [info]: Rate Control / qCompress : CRF-20.0 / 0.60 x265 [info]: VBV/HRD buffer / max-rate / init : 30000 / 30000 / 0.900 x265 [info]: tools: rd=2 psy-rd=0.50 rdoq=1 early-skip rskip tmvp fast-intra x265 [info]: tools: strong-intra-smoothing deblock(tC=-3:B=-3) [ 0.1%] 1/1619 frames, 10.00 fps, 1105.29 kb/s, eta 0:02:41 [ 2.1%] 34/1619 frames, 97.14 fps, 426.21 kb/s, eta 0:00:16 [ 4.6%] 74/1619 frames, 123.33 fps, 425.44 kb/s, eta 0:00:12 [ 7.1%] 115/1619 frames, 134.98 fps, 410.25 kb/s, eta 0:00:11 [ 9.6%] 156/1619 frames, 140.92 fps, 387.83 kb/s, eta 0:00:10 . . . [87.6%] 1419/1619 frames, 154.96 fps, 427.51 kb/s, eta 0:00:01 [89.9%] 1456/1619 frames, 154.78 fps, 430.27 kb/s, eta 0:00:01 [92.9%] 1504/1619 frames, 155.50 fps, 427.40 kb/s, eta 0:00:00 [96.0%] 1554/1619 frames, 156.39 fps, 420.94 kb/s, eta 0:00:00 [98.8%] 1600/1619 frames, 157.06 fps, 420.20 kb/s, eta 0:00:00 x265 [info]: frame I: 7, Avg QP:23.37 kb/s: 1636.34 x265 [info]: frame P: 406, Avg QP:24.74 kb/s: 896.79 x265 [info]: frame B: 1206, Avg QP:27.33 kb/s: 276.89 x265 [info]: consecutive B-frames: 1.0% 1.7% 1.7% 95.6% encoded 1619 frames in 10.26s (157.72 fps), 438.22 kb/s, Avg QP:26.66Last edited by vhelp; 19th Oct 2016 at 08:46.
-
I don't use x265 but from what I've read those numbers don't look unusual.Originally Posted by vhelp
-
Also test without --pmode
-
i7-6700K and i7-6700 are (slightly) different CPUs.Originally Posted by vhelp
http://ark.intel.com/products/88196/Intel-Core-i7-6700-Processor-8M-Cache-up-to-4_00-GHz
http://ark.intel.com/products/88195/Intel-Core-i7-6700K-Processor-8M-Cache-up-to-4_20-GHz -
I just double-checked through device manager, that was a typo on my part. I meant to say i7-6700, not 6700K.
-
If your work pc is a Skylake how about some QS tests?Originally Posted by vhelp
-
I will be happy to, but someone will have to give me their recommended command line parameters, for all: x264, QSVEncC.exe and x265.exe
-
Not to sound like a broken record but why not use Staxrip which makes it easy to configure the encoders, just test QS with the highest possible settings.
Thnx. -
Because that would be funless and anti-sportiveOriginally Posted by sophisticles
-
I found a barebones mini-pc that supports using a desktop CPU with up to a 65W TDP, including the i7 6700. The case is perforated on 4 of 6 sides, which allows enough heat to escape to prevent over-heating. Both items below are the same thing, but unfortunately newegg is presently sold out.
https://www.amazon.com/WIN-IW-DESKMINI-DESKMINI-USB3-0-MOTHERBOARD/dp/B01L1HCHWY
http://www.newegg.com/Product/Product.aspx?Item=N82E16856158048&cm_re=mini_pc-_-56-158...048-_-Product#
Review - http://www.tweaktown.com/reviews/7744/asrock-deskmini-110-mini-stx-pc-review/index.html
Barebones means that you get the motherboard, case, power brick, and 2 special SATA cables for connecting HDDs. It includes DisplayPort, HDMI, VGA for video, 2 USB 3.0 ports and 1 USB 2.0 port. A WIFI card + antennas appears to be be included, with newegg's version.
For this build, you will still need to buy your operating system and
CPU -- about $180 for an i5-6500 or about $280 for an i7-6700 from Microcenter
RAM -- about $84 for 16GB https://www.amazon.com/Kingston-Technology-HyperX-HX421S13IBK2-16/dp/B014R8JRRW?th=1
If you don't have a notebook drive that you can use:
HDD -- about $45 http://www.microcenter.com/product/415206/Blue_Laptop_Mainstream_320GB_5400RPM_SATA_II...MYH3200ANCNRSN
You will have to find a work-around to install Windows 7. There is no PS/2 port, and the SATA data and power connections are not standard, so you probably cannot attach an optical drive to run the installation media. At least one of these two things will be true for most other mini-PCs as well.
[Edit] You could use an SSD ($70) instead of an HDD: http://www.microcenter.com/product/463425/750_EVO_Series_250GB_SATA_III_6Gb-s_25_Inter...on_MZ-750250BW
[Edit 2]YouTube demo: https://www.youtube.com/embed/Xg8L6iK1dDMLast edited by usually_quiet; 21st Oct 2016 at 11:20.
-
could you do a QSVEncC.exe --check-features to see what the "beast" can do and not do.Originally Posted by vhelp
I will be happy to, but someone will have to give me their recommended command line parameters, for all: x264, QSVEncC.exe and x265.exe
after that we can see for some recommandations for the command line -
QSVEncC --check-features
Code:QSVEncC (x86) 2.57 (r1177) by rigaya, Sep 29 2016 23:14:33 (VC 1900/Win/avx2) reader: raw, avi, avs, vpy, avqsv [H.264/AVC, HEVC, MPEG2, VC-1, VP8, VP9] Environment Info OS : Windows 7 (x64) CPU: Intel Core i7-6700 @ 3.40GHz [TB: 3.88GHz] (4C/8T) <Skylake> RAM: Used 2981 MB, Total 8052 MB GPU: Intel HD Graphics 530 (24EU) 350-1150MHz [65W] (10.18.15.4279) Media SDK Version: Hardware API v1.16 Supported Enc features: Codec: H.264/AVC CBR VBR AVBR QVBR CQP VQP LA LAHRD ICQ LAICQ VCM RC mode o o o o o o o o o o o Fixed Func o o o o o o x x x x o Interlace o o o o o o o o o o o SceneChange o o o o o o x x o x o VUI info o o o o o o o o o o o Trellis o o o o o o o o o o o Adaptive_I x x x x x x x x x x x Adaptive_B x x x x x x x x x x x WeightP o o o o o o o o o o o WeightB o o o o o o o o o o o FadeDetect x x x x x x x x x x x B_Pyramid o o o o o x o x o o o +Scenechange x x x x x x x x x x x +ManyBframes o o o o o x x x o x o PyramQPOffset x x x x x x x x x x x Ext_BRC o o o o x x x x o x o MBBRC o o o o x x x x o x o LA Quality x x x x x x o o x o x QP Min/Max o o o o o o o o o o o IntraRefresh x x x x x x x x x x x No Debloc x x x x x x x x x x x No GPB x x x x x x x x x x x Windowed BRC x x x x x x o o x x x PerMBQP(CQP) x x x x o o x x x x x DirectBiasAdj x x x x x x x x x x x MVCostScaling x x x x x x x x x x x Codec: HEVC CBR VBR AVBR QVBR CQP VQP LA LAHRD ICQ LAICQ VCM RC mode o o x x o o x x o x o Fixed Func x x x x x x x x x x x Interlace x x x x x x x x x x x SceneChange o o x x o o x x o x o VUI info o o x x o o x x o x o Trellis o o x x o o x x o x o Adaptive_I o o x x o o x x o x o Adaptive_B o o x x o o x x o x o WeightP o o x x o o x x o x o WeightB o o x x o o x x o x o FadeDetect x x x x x x x x x x x B_Pyramid x x x x x x x x x x x +Scenechange x x x x x x x x x x x +ManyBframes x x x x x x x x x x x PyramQPOffset x x x x x x x x x x x Ext_BRC o o x x x x x x o x o MBBRC o o x x x x x x o x o LA Quality x x x x x x x x x x x QP Min/Max o o x x o o x x o x o IntraRefresh o o x x o o x x o x o No Debloc o o x x o o x x o x o No GPB x x x x x x x x x x x Windowed BRC o o x x o o x x o x o PerMBQP(CQP) o o x x o o x x o x o DirectBiasAdj o o x x o o x x o x o MVCostScaling o o x x o o x x o x o Codec: MPEG2 CBR VBR AVBR QVBR CQP VQP LA LAHRD ICQ LAICQ VCM RC mode o o o x o o x x x x x Fixed Func o o o x o o x x x x x Interlace o o o x o o x x x x x SceneChange o o o x o o x x x x x VUI info o o o x o o x x x x x Trellis o o o x o o x x x x x Adaptive_I o o o x o o x x x x x Adaptive_B o o o x o o x x x x x WeightP o o o x o o x x x x x WeightB o o o x o o x x x x x FadeDetect x x x x x x x x x x x B_Pyramid o o o x o x x x x x x +Scenechange x x x x x x x x x x x +ManyBframes o o o x o x x x x x x PyramQPOffset x x x x x x x x x x x Ext_BRC o o o x x x x x x x x MBBRC o o o x x x x x x x x LA Quality x x x x x x x x x x x QP Min/Max o o o x o o x x x x x IntraRefresh o o o x o o x x x x x No Debloc o o o x o o x x x x x No GPB x x x x x x x x x x x Windowed BRC o o o x o o x x x x x PerMBQP(CQP) x x x x o o x x x x x DirectBiasAdj o o o x o o x x x x x MVCostScaling o o o x o o x x x x x Supported Vpp features: Resize o Deinterlace o Scaling Quality x Denoise o Rotate x Mirror x Detail Enhancement o Proc Amp. o Image Stabilization o Video Signal Info o FPS Conversion o FPS Conversion (Adv.) o Checking for QSV...Last edited by vhelp; 20th Oct 2016 at 20:55. Reason: fixed a typo
-
you should update your driver, it's v1.19 api now
if no new features in v1.19 -> no look-ahead mode, no b-pyramid ...
so default cqp with --quality best should already be the best setting. -
Can't update work pc driver, it is locked.
On another note.. I don't get it. Why did Intel add hardware (mpeg/avc/hevc/vp/etc) encoders in our cpu's and not advertise about it ?
I learned about it, (quicksync) on this board. But I've never seen any ads or publicity about it. Plus, what was the intended purpose of including it without software to utilize it ?
And it does not appear to be hard-core, like x264 is. If these encoders are based off of one "slab" then all cpu's with QSV should produce the same image quality level. -
Also, something else to bring up while I was researching my computers.
I discovered that my 2+ year old Dell Venue 8 Pro tablet, Windows 8.1, Intel Atom Z3740D cpu quad-core @ 1.33GHz 2GB ram 32GB Storage 1280x800 has Quicksync (AVC) as well.
cpu specs: http://ark.intel.com/products/78416/Intel-Atom-Processor-Z3740D-2M-Cache-up-to-1_83-GHz
amazon: https://www.amazon.com/Dell-Venue-5000-Windows-Tablet/dp/B00FEE7B1I
I tested it out and it is functional but needs its media sdk version updated, I believe.
QSVEncC.exe --check-features
and, a quick test encode... aprox 85 fpsCode:QSVEncC (x86) 2.57 (r1177) by rigaya, Sep 29 2016 23:14:33 (VC 1900/Win/avx2) reader: raw, avi, avs, vpy, avqsv [H.264/AVC, HEVC, MPEG2, VC-1, VP8, VP9] Environment Info OS : Windows 8.1 (x86) CPU: Intel Atom Z3740D @ 1.33GHz [TB: 1.81GHz] (4C/4T) <Silvermont> RAM: Used 801 MB, Total 1933 MB GPU: Intel HD Graphics (4EU) 9650-10800MHz (10.18.10.3349) Media SDK Version: Hardware API v1.7 Supported Enc features: Codec: H.264/AVC CBR VBR AVBR QVBR CQP VQP LA LAHRD ICQ LAICQ VCM RC mode o o o x o o x x x x x Fixed Func x x x x x x x x x x x Interlace o o o x o o x x x x x SceneChange o o o x o o x x x x x VUI info o o o x o o x x x x x Trellis o o o x o o x x x x x Adaptive_I x x x x x x x x x x x Adaptive_B x x x x x x x x x x x WeightP x x x x x x x x x x x WeightB x x x x x x x x x x x FadeDetect x x x x x x x x x x x B_Pyramid x x x x x x x x x x x +Scenechange x x x x x x x x x x x +ManyBframes x x x x x x x x x x x PyramQPOffset x x x x x x x x x x x Ext_BRC o o o x x x x x x x x MBBRC o o o x x x x x x x x LA Quality x x x x x x x x x x x QP Min/Max x x x x x x x x x x x IntraRefresh x x x x x x x x x x x No Debloc x x x x x x x x x x x No GPB x x x x x x x x x x x Windowed BRC x x x x x x x x x x x PerMBQP(CQP) x x x x x x x x x x x DirectBiasAdj x x x x x x x x x x x MVCostScaling x x x x x x x x x x x Supported Vpp features: Resize o Deinterlace o Scaling Quality x Denoise o Rotate x Mirror x Detail Enhancement o Proc Amp. o Image Stabilization x Video Signal Info x FPS Conversion o FPS Conversion (Adv.) x Checking for QSV...
Code:QSVEncC --quality higher -i "c:\tools\movie.avs" -o "e:\videos\video.Quicksync_avc_video.h264" QSVEncC (x86) 2.57 (r1177) by rigaya, Sep 29 2016 23:14:33 (VC 1900/Win/avx2) OS Windows 8.1 (x86) CPU Info Intel Atom Z3740D @ 1.33GHz [TB: 1.81GHz] (4C/4T) <Silvermont> GPU Info Intel HD Graphics (4EU) 9650-10800MHz (10.18.10.3349) Media SDK QuickSyncVideo (hardware encoder), 1st GPU, API v1.7 Async Depth 4 frames Buffer Memory d3d9, 3 input buffer, 13 work buffer Input Info Avisynth 2.60 (yv12)->nv12[SSE2], 720x480, 24000/1001 fps Output H.264/AVC High @ Level 3 720x480p 1:1 23.976fps (24000/1001fps) Target usage 2 - higher Encode Mode Constant QP (CQP) CQP Value I:24 P:26 B:27 Trellis Auto Ref frames 2 frames Bframes 3 frames Max GOP Length 240 frames Scene Change off [ 3.7%] 60 frames: 74.81 fps, 577 kb/s, remain 0:00:20 [ 8.1%] 131 frames: 81.62 fps, 540 kb/s, remain 0:00:18 [12.3%] 200 frames: 83.09 fps, 507 kb/s, remain 0:00:17 [16.6%] 269 frames: 83.85 fps, 505 kb/s, remain 0:00:16 [20.8%] 337 frames: 83.96 fps, 492 kb/s, remain 0:00:15 [24.9%] 404 frames: 83.71 fps, 509 kb/s, remain 0:00:14 [29.2%] 474 frames: 84.09 fps, 525 kb/s, remain 0:00:13 [33.5%] 543 frames: 84.33 fps, 530 kb/s, remain 0:00:12 [37.7%] 612 frames: 84.47 fps, 541 kb/s, remain 0:00:11 [42.1%] 683 frames: 84.89 fps, 549 kb/s, remain 0:00:11 [46.3%] 752 frames: 84.97 fps, 549 kb/s, remain 0:00:10 [50.5%] 820 frames: 84.89 fps, 546 kb/s, remain 0:00:09 [54.7%] 887 frames: 84.78 fps, 555 kb/s, remain 0:00:08 [59.0%] 957 frames: 84.95 fps, 554 kb/s, remain 0:00:07 [62.8%] 1020 frames: 84.53 fps, 556 kb/s, remain 0:00:07 [67.2%] 1090 frames: 84.70 fps, 552 kb/s, remain 0:00:06 [71.5%] 1160 frames: 84.85 fps, 547 kb/s, remain 0:00:05 [75.8%] 1230 frames: 84.98 fps, 551 kb/s, remain 0:00:04 [80.1%] 1300 frames: 85.04 fps, 552 kb/s, remain 0:00:03 [84.4%] 1370 frames: 85.11 fps, 550 kb/s, remain 0:00:02 [88.7%] 1440 frames: 85.23 fps, 548 kb/s, remain 0:00:02 [93.1%] 1511 frames: 85.37 fps, 547 kb/s, remain 0:00:01 [97.4%] 1580 frames: 85.36 fps, 539 kb/s, remain 0:00:00 encoded 1623 frames, 85.99 fps, 533.94 kbps, 4.31 MB encode time 0:00:19, CPULoad: 42.45 frame type IDR 7 frame type I 7, total size 0.08 MB frame type P 406, total size 1.77 MB frame type B 1210, total size 2.46 MB -
Video encoding is a niche market so it's not mentioned often. But it's usually mentioned in all the press releases and reviews of new processors.Originally Posted by vhelp
As with most software, I believe Intel's intention was that they would offer the hardware and a minimal proof-of-concept encoder to show how it's used. They expected other software developers to make their own encoding software with improvements. What's happened, at least with all the free encoders, is they just use Intel's sample library.Originally Posted by vhelp
Each generation of QS has offered incremental improvements and more abilities (with h.265 added in the last few generations).Originally Posted by vhelp
-
I do not believe that the driver needs to be updated, and !'m pretty sure that the SDK doesn't need to be installed in order to use the binary, only to compile it from source.Originally Posted by vhelp
The problem is that you are using al old build of QSVEnc, why are you so opposed to using a GUI like Staxrip?
I honestly don't understand why there are some people that absolutely insist on only using CLI encoders, you guys don't use text based browsers do you? You don't use DOS or a *Nix without X enabled, so why do you have such an aversion to using a GUI for encoding?
As for "publicity" regarding QS, Intel has promoted it from before Sandy Bridge was released, every review I have ever read about SB and later Intel processors has covered it and in many cases tested it, they have entered in in every MSU test since it debuted, I don't see how anyone has not heard of it.
As to your other point about not offering software to use it, I agree with you, Nvidia did the same thing with CUDA based encoders, and then with their NVENC and AMD has done the same thing with their encoder.
If you ever go on any of their developer forums you can see reps from each company that have basically said the same thing, Intel/Nvidia/AMD designed and built the hardware, created an SDK, coded up some samples and expect ISV's to create the software around it.
In Intel's case though they did try to reach out to the x264 developers when SB first came out to see about getting x264 to work with QS but long story short the were given a rather impolite version of "No Thanks'. Intel does sell a 5 grand software package that utilizes QS and that is that encoder that was tested by MSU and they do work with the FFMPEG project which does offer accelerated encoding on Windows and I believe Linux via QS. -
Is he?Originally Posted by sophisticles
Originally Posted by vhelp
-
I am not opposed to staxrip. I'm sure its a good software. But I write my own software to work in the way I prefer. Now, if its just a matter of compiling the necessary pieces (I don't know which pieces nor where to get them and compile) then maybe I can compile it and incorporate it into my gui front end app.I do not believe that the driver needs to be updated, and !'m pretty sure that the SDK doesn't need to be installed in order to use the binary, only to compile it from source.
Well, then, how the heck are you soppose to use Intel's encoder unless they supply the working app? What am I missing here? Comm'on, what's the big secret?I honestly don't understand why there are some people that absolutely insist on only using CLI encoders, you guys don't use text based browsers do you? You don't use DOS or a *Nix without X enabled, so why do you have such an aversion to using a GUI for encoding?
This still sounds like a GUI for their app or sdk. My guess is that staxrip is the wrapper, the software (Intel's) is compiled and then encorporated into staxrip. Its the same thing. And I can do it. But i'm not a c/c++ developer. I'm a pascal developer. So its harder for me to do something similar. If I new how to compile c/c++ software (ie, Intel's quicksync) I would! And then incoporate it into my custom gui. Or, someone who knows how to compile c/c++ apps and wants to be helpful could compile it. Or, tell me what compiler and other pieces of software to install, and show me how to compile it. From there, I can recompile it to the latest version and incorporate it into a GUI. Problem solvedIf you ever go on any of their developer forums you can see reps from each company that have basically said the same thing, Intel/Nvidia/AMD designed and built the hardware, created an SDK, coded up some samples and expect ISV's to create the software around it.
In any case. With respect to the media sdk, I still believe that there is a bit more to it than I know. Take a look at the --check-features report, where you will notice the rows showing O's and X's. Anything with an "O" is to denote the lack of support for that feature. So, my guess is that the media sdk needs to be updated with those non-supported features. Somewhere, there is an *correctly* updated version, and that needs to be installed on each of my computers, thus my Dell Venue 8 pro tablet and my Dell Inspiron laptop since they *both* have the same Intel quicksync. The same engine is in all the intel computers that has quicksync. They are like eproms: they have to be refreshed with the latest instructions.
CPU: Dell Desktop pc, i7-6700
CPU: Dell Venue 8 Pro, Atom Z3740DCode:QSVEncC (x86) 2.57 (r1177) by rigaya, Sep 29 2016 23:14:33 (VC 1900/Win/avx2) reader: raw, avi, avs, vpy, avqsv [H.264/AVC, HEVC, MPEG2, VC-1, VP8, VP9] Environment Info OS : Windows 7 (x64) CPU: Intel Core i7-6700 @ 3.40GHz [TB: 3.88GHz] (4C/8T) <Skylake> RAM: Used 2981 MB, Total 8052 MB GPU: Intel HD Graphics 530 (24EU) 350-1150MHz [65W] (10.18.15.4279) Media SDK Version: Hardware API v1.16 Supported Enc features: Codec: H.264/AVC CBR VBR AVBR QVBR CQP VQP LA LAHRD ICQ LAICQ VCM RC mode o o o o o o o o o o o Fixed Func o o o o o o x x x x o Interlace o o o o o o o o o o o SceneChange o o o o o o x x o x o VUI info o o o o o o o o o o o Trellis o o o o o o o o o o o Adaptive_I x x x x x x x x x x x Adaptive_B x x x x x x x x x x x WeightP o o o o o o o o o o o WeightB o o o o o o o o o o o FadeDetect x x x x x x x x x x x B_Pyramid o o o o o x o x o o o +Scenechange x x x x x x x x x x x +ManyBframes o o o o o x x x o x o PyramQPOffset x x x x x x x x x x x Ext_BRC o o o o x x x x o x o MBBRC o o o o x x x x o x o LA Quality x x x x x x o o x o x QP Min/Max o o o o o o o o o o o IntraRefresh x x x x x x x x x x x No Debloc x x x x x x x x x x x No GPB x x x x x x x x x x x Windowed BRC x x x x x x o o x x x PerMBQP(CQP) x x x x o o x x x x x DirectBiasAdj x x x x x x x x x x x MVCostScaling x x x x x x x x x x x
CPU: Dell Inspiron laptop, i3-2370MCode:QSVEncC (x86) 2.57 (r1177) by rigaya, Sep 29 2016 23:14:33 (VC 1900/Win/avx2) reader: raw, avi, avs, vpy, avqsv [H.264/AVC, HEVC, MPEG2, VC-1, VP8, VP9] Environment Info OS : Windows 8.1 (x86) CPU: Intel Atom Z3740D @ 1.33GHz [TB: 1.81GHz] (4C/4T) <Silvermont> RAM: Used 801 MB, Total 1933 MB GPU: Intel HD Graphics (4EU) 9650-10800MHz (10.18.10.3349) Media SDK Version: Hardware API v1.7 Supported Enc features: Codec: H.264/AVC CBR VBR AVBR QVBR CQP VQP LA LAHRD ICQ LAICQ VCM RC mode o o o x o o x x x x x Fixed Func x x x x x x x x x x x Interlace o o o x o o x x x x x SceneChange o o o x o o x x x x x VUI info o o o x o o x x x x x Trellis o o o x o o x x x x x Adaptive_I x x x x x x x x x x x Adaptive_B x x x x x x x x x x x WeightP x x x x x x x x x x x WeightB x x x x x x x x x x x FadeDetect x x x x x x x x x x x B_Pyramid x x x x x x x x x x x +Scenechange x x x x x x x x x x x +ManyBframes x x x x x x x x x x x PyramQPOffset x x x x x x x x x x x Ext_BRC o o o x x x x x x x x MBBRC o o o x x x x x x x x LA Quality x x x x x x x x x x x QP Min/Max x x x x x x x x x x x IntraRefresh x x x x x x x x x x x No Debloc x x x x x x x x x x x No GPB x x x x x x x x x x x Windowed BRC x x x x x x x x x x x PerMBQP(CQP) x x x x x x x x x x x DirectBiasAdj x x x x x x x x x x x MVCostScaling x x x x x x x x x x x
Code:QSVEncC (x86) 2.57 (r1177) by rigaya, Sep 29 2016 23:14:33 (VC 1900/Win/avx2) reader: raw, avi, avs, vpy, avqsv [H.264/AVC, HEVC, MPEG2, VC-1, VP8, VP9] Environment Info OS : Windows 7 (x64) CPU: Intel Core i3-2370M @ 2.40GHz (2C/4T) <SandyBridge> RAM: Used 2587 MB, Total 6044 MB GPU: Intel HD Graphics 650-1150MHz Media SDK Version: Hardware API v1.3 Supported Enc features: Codec: H.264/AVC CBR VBR AVBR QVBR CQP VQP LA LAHRD ICQ LAICQ VCM RC mode o o o x o o x x x x x Fixed Func x x x x x x x x x x x Interlace o o o x o o x x x x x SceneChange o o o x o o x x x x x VUI info o o o x o o x x x x x Trellis x x x x x x x x x x x Adaptive_I x x x x x x x x x x x Adaptive_B x x x x x x x x x x x WeightP x x x x x x x x x x x WeightB x x x x x x x x x x x FadeDetect x x x x x x x x x x x B_Pyramid x x x x x x x x x x x +Scenechange x x x x x x x x x x x +ManyBframes x x x x x x x x x x x PyramQPOffset x x x x x x x x x x x Ext_BRC x x x x x x x x x x x MBBRC x x x x x x x x x x x LA Quality x x x x x x x x x x x QP Min/Max x x x x x x x x x x x IntraRefresh x x x x x x x x x x x No Debloc x x x x x x x x x x x No GPB x x x x x x x x x x x Windowed BRC x x x x x x x x x x x PerMBQP(CQP) x x x x x x x x x x x DirectBiasAdj x x x x x x x x x x x MVCostScaling x x x x x x x x x x x -
So here's the answers that will explain why it's not working on your test systems:
https://trac.ffmpeg.org/wiki/HWAccelIntro
Intel QSV
Intel QSV (Quick Sync Video) is a technology which allows decoding and encoding using recent Intel CPU and integrated GPU, supported on recent Intel CPUs. Note that the (CPU)GPU needs to be compatible with both QSV and OpenCL. Some (older) QSV -enabled GPUs aren't compatible with OpenCL. See: http://www.intel.com/content/www/us/en/architecture-and-technology/quick-sync-video/qu...o-general.html https://software.intel.com/en-us/articles/intel-sdk-for-opencl-applications-2013-release-notes
To enable QSV support, you need the Intel Media SDK integrated in the Intel Media Server Studio: https://software.intel.com/en-us/intel-media-server-studio
The Intel Media Server studio is available for both Linux and Windows, and contains the libva and libdrm libraries, the libmfx dispatcher library and the intel drivers. libmfx is the library which selects the codec depending on the system capabilities, falling back to a software implementation if the hardware accelerated codec is not available).
FFmpeg QSV support relies on libmfx, but the library provided by Intel does not come with pkg-config files and a proper installer. Thus the easiest to install the library is to use the libmfx version packaged by lu_zero here: https://github.com/lu-zero/mfx_dispatch
Requirements on Windows: install the Intel Media SDK packaged in the Intel Media Server Studio, which comes with a graphic installer, and a MinGW compilation enviroment (for example provided by MSYS2 with a corresponding Mingw-w64 package). Then you need to build libmfx and install it in a path recognized by pkg-config. For example if you install in /usr/local then you need the update the $PKG_CONFIG_PATH environment variable to make it point to /usr/local/lib/pkgconfig.
Requriments on Linux: you need either to rely on the Intel Media Server Studio for Linux, or use a recent enough supported system, with the libva and libdrm libraries, the libva Intel drivers, and the libmfx library packaged by lu_zero. Note: in case you use the Intel Media Server Studio generic installation script, the installation script may overwrite your system libraries and break the system.
Check the following website for updated information about the Intel Graphics stack on the various Linux platforms: https://01.org/linuxgraphics
To enable QSV support in the FFmpeg build, configure with --enable-libmfx.
Support for decoding and encoding is integrated in FFmpeg through several codecs identified by the _qsv suffix. In particular, it currently supports MPEG2 video, VC1 (decoding only), H.264 and H.265.
For example to encode to H.264 using h264_qsv, you can use the command:
ffmpeg -i INPUT -c:v h264_qsv -preset:v faster out.qsv.mp4
If you have a Kaby Lake CPU, you can encode with HEVC using hevc_qsv:
ffmpeg -i INPUT -c:v hevc_qsv -load_plugin hevc_hw -preset:v faster out.qsv.mp4
So the above information should allow you to build ffmpeg with QSV enabled, on either Linux or Windows depending on what you prefer, and once you have the binary you can integrate that into your own Pascal (you sure you didn't mean Delphi?) coded app.
Alternatively you can find a current build with non-free enabled and use that. -
This project is turning into a headache. I read through all that and went to the various links posted for the media sdk, etc., and its just over my head. To do something so simple is yet so complicated. Anyway.
I downloaded the latest ffmpeg build and it no longer supports avisynth scripts. I'm not building any raw files for testing. Sorry. Just not gonna do that.
is returning the following error and I am stumped as to why it won't work even though avisynth is enabled.Code:For example to encode to H.264 using h264_qsv, you can use the command: ffmpeg -i INPUT -c:v h264_qsv -preset:v faster out.qsv.mp4
C:\tools\ffmpeg\ffmpeg -i "C:\tools\movie.avs" -c:v h264_qsv -preset:v faster -y "c:\videos\ffmpeg_video.h264_qsv_v1.mp4"
Code:ffmpeg version N-80906-gd5edb6c Copyright (c) 2000-2016 the FFmpeg developers built with gcc 5.4.0 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib libavutil 55. 28.100 / 55. 28.100 libavcodec 57. 48.101 / 57. 48.101 libavformat 57. 41.100 / 57. 41.100 libavdevice 57. 0.102 / 57. 0.102 libavfilter 6. 47.100 / 6. 47.100 libswscale 4. 1.100 / 4. 1.100 libswresample 2. 1.100 / 2. 1.100 libpostproc 54. 0.100 / 54. 0.100 C:\tools\movie.avs: Unknown error occurred -
-
Thanks, sneaker. That worked when I switched to the 32 bit version, but I'm still getting an error. Must be related to ffmpeg, a missing param for this _qsv encoder perhaps, since the x264.exe encoder works w/ no problems. I mean, the avs script is good.
C:\tools\ffmpeg\ffmpeg -i "C:\tools\movie.avs" -c:v h264_qsv -preset:v faster -y "c:\videos\ffmpeg_video_h264_qsv_v1.h264"
Code:Guessed Channel Layout for Input Stream #0.1 : stereo Input #0, avisynth, from 'C:\tools\movie.avs': Duration: 00:10:58.28, start: 0.000000, bitrate: 0 kb/s Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p, 720x480, 23.98 fps, 23.98 tbr, 23.98 tbn, 23.98 tbc Stream #0:1: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s [h264_qsv @ 04c96f80] Error initializing an internal MFX session Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (h264_qsv)) Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height -
update.. regarding the Intel Quicksync encoder for H264/AVC encoding.
First, I'm wondering if anyone has gotten ffmpeg to work with quicksync, for AVC and/or HEVC. Otherwise.
I believe I may have finally figured out how to get that to work. And, tomorrow, I will test the method on my pc at work, on the i7-6700 but using the H265/HEVC encoder.
In the mean time, I'd like someone to verify some encoded samples that I made. But I have to upload them first. Also, I just saw some new samples here and want to encode those and upload those as well, and someone can verify if they were encoded through quicksync and compare quality to their encode they made of those clips, etc. to see if the QS encode is as good or better than the x264 encoder. -
Just found this thread. I have a new Titan X Pascal on my i7 6700K based PC I just built. What are my NVIDIA options in terms of accelerating h264 encoding? Tired of handbrake CLI and waiting hours for files to encode. I have this monster Titan X and want to figure out a way (preferably via Windows command line I can craft into an intelligent batch file) to take advantage of it.
Any ideas? Thanks in advance for the help.
DOM -
The options are listed in the fullhelp under the nvenc AVOptions, nvenc_h264 AVOptions for h264 , and nvenc_hevc AVOptions for hevcOriginally Posted by domenic
You can print out text file and use a text editor/search because the full help is very long
Very nice card! But I hope you play games with it because but a "cheap" GTX1050 will encode as fast as your card. Shaders aren't used for encoding; the dedicated silicon part responsible for encoding used by nvenc is separate from the shaders used in games and such. And it's the same across all pascal cards in the same generation (same with maxwell2, maxwell)Code:ffmpeg -h full 1>ffmpeg_fullhelp.txt
-
I am a big gamer but wanted to also use the card for encoding. So you are saying with just "stock" ffmpeg it supports nvidia hardware encoding or do I need to load some sort of nvidia SDK or similar? If this works I was thinking I could pickup a just released GTX 1050 card fro $130 and throwi it in a dedicated "encoder box" - still same encoding capabilities as the Titan?
Today I have a handbrake cli batch file, want to "convert" it to plain ffmpeg using the nvidia capabilities.
FOR /F "tokens=*" %%G IN ('DIR /B \\SYNOLOGY1\Media-Processing\Incoming\a\*.mkv') DO \\SYNOLOGY1\Thumper\data\Apps\HBCLI\HandBrakeCLI -i "\\SYNOLOGY1\Media-Processing\Incoming\a\%%G" -o "\\SYNOLOGY1\Media-Processing\Finished\%%G" --preset="High Profile" --x264-preset=veryslow --quality 22 --audio 1,2,3,4,5,6 --aencoder copy -
Originally Posted by domenic
You need a ffmpeg build compiled with nvenc ; the common freely distributed builds might not come with it by default . The nvidia drivers have everything else required for nvenc encoding
Yes, a GTX1050 has the same ASIC IP block used for encoding as all Pascal generation cards (every card in the same generation will be the same speed , same quality for encoding since kepler)
https://en.wikipedia.org/wiki/Nvidia_NVENC
NVenc quality is not very good compared to x264 . But it's very fast. You need substantially more bitrate for similar quality, maybe 1.5 -2x more at typical bitrate ranges
So you can't really take a handbrake CLI batch and "translate" it to a ffmpeg h264_nvenc batch, because so many things are different.
Nice thread hijack btw
-
Yes, looks like I did "pivot" the thread...
I will do some googling to try and figure out how to get a build of ffmpeg with nvenc included. I thought I read somewhere that prior to Pascal Nvidia / nvenc quality was an issue but with Pascal its "better". Guess I will have to see for myself.
Quote
Similar Threads
-
tool to view x265 encoding parameters
By vhelp in forum Video ConversionReplies: 14Last Post: 28th Oct 2017, 08:34 -
I want to learn x265 encoding by command line.
By knightplex in forum Video ConversionReplies: 21Last Post: 3rd Nov 2016, 09:22 -
ffmpeg and encoding blu-ray to x265
By madhatr in forum Blu-ray RippingReplies: 15Last Post: 29th Jan 2016, 06:54 -
Specific file size for x265 encoding...
By alryan011 in forum Video ConversionReplies: 2Last Post: 26th May 2015, 17:09 -
Encoding movie with x265 feasible?
By -Habanero- in forum Video ConversionReplies: 1Last Post: 21st Mar 2015, 13:31