Announcement

Collapse
No announcement yet.

driver intel HD Graphics 530 Quicksync Win 10 Pro

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • driver intel HD Graphics 530 Quicksync Win 10 Pro

    Win 10Pro 64 bit (1809) MB ASUS 170H-PRO i7-Core intel HD Graphics 530. Edius 8 Pro (53 3262) Quicksync (H.264)--Does not work.
    put the last 5 drivers - does not work.

    What version to install the driver intel HD Graphics 530 Win 10 Pro?
    I use 2 monitors.

  • #2
    Originally posted by Andre129130 View Post
    Win 10Pro 64 bit (1809) MB ASUS 170H-PRO i7-Core intel HD Graphics 530. Edius 8 Pro (53 3262) Quicksync (H.264)--Does not work.
    put the last 5 drivers - does not work.

    What version to install the driver intel HD Graphics 530 Win 10 Pro?
    I use 2 monitors.
    Do you have monitor hooked up to the intel GPU? It must have a monitor hooked up to it for it to become active.
    Edius WG 9.55.7761, various 3rd party plugins, VisTitle 2.9.6.0, Win 7 Ultimate SP1, i7-4790K @ 4GHz with HD4600 GPU embedded, MSI Z97 Gaming 7 Motherboard, 32GB Kingston HyperX RAM, nVidia GTX680 4GB GPU, Matrox MX02 Mini MAX, Corsair 750W PSU, Corsair H110i GT Water Cooler, Corsair C70 case, 8TB Internal RAID 0/stripe (2x4TB Seagate SATAIII HDD's, Win7 Software stripe), 1TB Crucial MX500 SSD, Pioneer BDR-207D, Dual 1920x1080 monitors (one on GTX680 and one on Intel HD4600).

    Comment


    • #3
      two monitors connected.
      1-nvidia 1660
      2-intel 6700 HD 530

      Comment


      • #4
        Originally posted by Andre129130 View Post
        two monitors connected.
        1-nvidia 1660
        2-intel 6700 HD 530
        I don't use Win10, so I can't help you a lot on that, but I do recall some posts here on the forum saying that with some motherboards, the intel GPU had to be set as the primary GPU in the BIOS and Win10 in order for Edius to use it for quicksync.

        In particular, I believe it was David Clarke that posted this information if I am not mistaken.

        Perhaps if you do a forum search with that in mind you may find more details.
        Edius WG 9.55.7761, various 3rd party plugins, VisTitle 2.9.6.0, Win 7 Ultimate SP1, i7-4790K @ 4GHz with HD4600 GPU embedded, MSI Z97 Gaming 7 Motherboard, 32GB Kingston HyperX RAM, nVidia GTX680 4GB GPU, Matrox MX02 Mini MAX, Corsair 750W PSU, Corsair H110i GT Water Cooler, Corsair C70 case, 8TB Internal RAID 0/stripe (2x4TB Seagate SATAIII HDD's, Win7 Software stripe), 1TB Crucial MX500 SSD, Pioneer BDR-207D, Dual 1920x1080 monitors (one on GTX680 and one on Intel HD4600).

        Comment


        • #5
          On my motherboard I have to have Mulitgpu enabled in the bios, or make sure the Intel is set to enabled in the bios, not auto. The 6025 drivers worked well for me, which are now fairly old. With those I could have the nVidia set to the primary and intel set to secondary. With other drivers I had to have others set the Intel to the primary in Windows.
          The other important question is which version of EDIUS are you using?
          EDIUS silver certified trainer.
          Main edit laptop: DVC Kaby Lake desktop processor laptop, 32GB RAM, 3.5Ghz i5 desktop processor, nVidia 1060, Windows 10.
          Desktop: 4Ghz 9900K processor, 32GB RAM, nVidia 1660TI GPU, Windows 10.
          Desktop: 2Ghz 12 core Xeon processor, 32GB RAM, nVidia 1060, BM Intensity Pro, Windows 10

          Comment


          • #6
            Two graphic cards are included in the BIOS.
            EDIUS 8 Pro 53

            Comment


            • #7
              I am only using EDIUS 9 currently so have not tested EDIUS 8 with the latest drivers. I did set up EDIUS 7 on Windows 10 with the 6025 drivers and that was ok, so it would seem silly if EDIUS 8 does not work.

              Firstly I would take out the nVidia and just use the on-board to see it if will work. Since the hardware tick box will appear even when QS is not working open task manager and look at the performance of the Intel GPU when encoding to see if it is being used.

              Secondly test using a simple timeline with just clips and no effects. I generally use HD AVCHD. I did a test for a customer using ProRes clips on a timeline and the Intel GPU was only working at about 30% when encoding, but on the same system it worked at about 80% on AVCHD. The ProRes timeline had two clips with a layouter on both plus a graphic overlaid. All the extra CPU processing meant not a lot was left for QS.

              What makes you think QS is not working - no hardware tick box or just very long encoding times?
              EDIUS silver certified trainer.
              Main edit laptop: DVC Kaby Lake desktop processor laptop, 32GB RAM, 3.5Ghz i5 desktop processor, nVidia 1060, Windows 10.
              Desktop: 4Ghz 9900K processor, 32GB RAM, nVidia 1660TI GPU, Windows 10.
              Desktop: 2Ghz 12 core Xeon processor, 32GB RAM, nVidia 1060, BM Intensity Pro, Windows 10

              Comment


              • #8
                long coding time even with hardware coding enabled.
                video h.264 FullHD t=4,23 min driver HD 530 26.20.100.6866 coding--5 min.
                video h.264 FullHD t=4,23 min driver HD 530 22.20.16.4691 coding--58 s.
                In the task manager, you can already see the work of graphics intel HD 530.

                Comment


                • #9
                  Originally posted by Andre129130 View Post
                  long coding time even with hardware coding enabled.
                  video h.264 FullHD t=4,23 min driver HD 530 26.20.100.6866 coding--5 min.
                  video h.264 FullHD t=4,23 min driver HD 530 22.20.16.4691 coding--58 s.
                  In the task manager, you can already see the work of graphics intel HD 530.
                  58 seconds to encode a 4 minute 23 second video is not slow.

                  H264 is a very difficult/complicated codec to encode. FHD H264 encode times using QuickSync, in the 20% to 25% of total duration are normal.

                  H265 is even more complicated and slower.
                  Edius WG 9.55.7761, various 3rd party plugins, VisTitle 2.9.6.0, Win 7 Ultimate SP1, i7-4790K @ 4GHz with HD4600 GPU embedded, MSI Z97 Gaming 7 Motherboard, 32GB Kingston HyperX RAM, nVidia GTX680 4GB GPU, Matrox MX02 Mini MAX, Corsair 750W PSU, Corsair H110i GT Water Cooler, Corsair C70 case, 8TB Internal RAID 0/stripe (2x4TB Seagate SATAIII HDD's, Win7 Software stripe), 1TB Crucial MX500 SSD, Pioneer BDR-207D, Dual 1920x1080 monitors (one on GTX680 and one on Intel HD4600).

                  Comment


                  • #10
                    Всё тему можно закрывать, всё работает нашёл нужный драйвер.
                    Для всех:
                    Win 10 64 1809,ASUS 170H-pro. i7Core 6700 EDIUS 8.53
                    2 GPU 1.nvidia 1660

                    2. HD 530 ставим драйвер 22.20.16.4815 от 26.09.2017=QS.

                    Comment


                    • #11
                      Originally posted by Andre129130 View Post
                      Всё тему можно закрывать, всё работает нашёл нужный драйвер.
                      Для всех:
                      Win 10 64 1809,ASUS 170H-pro. i7Core 6700 EDIUS 8.53
                      2 GPU 1.nvidia 1660

                      2. HD 530 ставим драйвер 22.20.16.4815 от 26.09.2017=QS.
                      Sorry, I don't speak/read Russian.
                      Edius WG 9.55.7761, various 3rd party plugins, VisTitle 2.9.6.0, Win 7 Ultimate SP1, i7-4790K @ 4GHz with HD4600 GPU embedded, MSI Z97 Gaming 7 Motherboard, 32GB Kingston HyperX RAM, nVidia GTX680 4GB GPU, Matrox MX02 Mini MAX, Corsair 750W PSU, Corsair H110i GT Water Cooler, Corsair C70 case, 8TB Internal RAID 0/stripe (2x4TB Seagate SATAIII HDD's, Win7 Software stripe), 1TB Crucial MX500 SSD, Pioneer BDR-207D, Dual 1920x1080 monitors (one on GTX680 and one on Intel HD4600).

                      Comment

                      Working...
                      X