CloneBD not detecting iGPU (in combo with GTX 1080)

Discussion in 'CloneBD' started by Ch3vr0n, Aug 8, 2020.

  1. Ch3vr0n

    Ch3vr0n Translator NL & Mod

    So in order to try something with a tool i use for processing 3D discs (got one handed to me, havent done this in a long time), and no. It's not "the monkey" (ugh), i needed to the iGPU. So i went into the bios of my board, enabled the iGPU (multi-monitor mode, set primary display to PEG) and to make sure it got enabled i added an HDMI dummy plug into the onboard video (which simulates an actual attached monitor). in the screenshot below you'll see the top left and center are my actual monitors. The bottom right one is the simulated.

    Windows promptly detected the now onboard video, and asked to install drivers. I did, and rebooted. just to be sure. Intel DCH drivers 27.20.100.8476 got installed and out of curiosity i checked if CloneBD found the iGPU. It doesn't. CLBD refuses to detect the Onboard video (i distinctly remember it seeing enabled alongs side my GTX 1080 in an old version)

    Should i be checking something on why CLBD doesn't detect the iGPU?

    My DVD authoring tool for example (ConvertXtoDVD) does properly detect the Intel UHD graphics (630) built onto the 9900k
     

    Attached Files:

    • igpu.png
      igpu.png
      File size:
      414.8 KB
      Views:
      32
    whatever_gong82 and tectpro like this.
  2. tectpro

    tectpro Translator (ms_MY)

    Same happens with RTX2060, I posted this sometime ago in the German section. Same iGPU.
     
  3. Ch3vr0n

    Ch3vr0n Translator NL & Mod

    looks like a job for @Reto or @Fabian then to investigate
     
  4. Fabian

    Fabian Developer

    can you make a screenshot that's not only blurry?
     
  5. Ch3vr0n

    Ch3vr0n Translator NL & Mod

    Download the image it's anything but blurry. Dual monitor on the top left.

    Sent from my Pixel 3 XL using Tapatalk
     
  6. Fabian

    Fabian Developer

    the image has a full soze of 1598x602 pixels.. I can't read anything there...
     
  7. Ch3vr0n

    Ch3vr0n Translator NL & Mod

    fixed
     

    Attached Files:

    • igpu.png
      igpu.png
      File size:
      594.3 KB
      Views:
      31
  8. Pete

    Pete Forum Admin Staff Member

    whatever_gong82 likes this.
  9. whatever_gong82

    whatever_gong82 Well-Known Member

    Glarioo likes this.
  10. Ch3vr0n

    Ch3vr0n Translator NL & Mod

    Did you have to be so brutal? Now my feelings are hurt and bruised

    had to modify the commandline and add .x64 to the filename to get it to work. Maybe the x64 version is looking for the x86 drone or somethin
     
    whatever_gong82 likes this.
  11. coopervid

    coopervid Well-Known Member

    Chesterson is my favorite
     
    whatever_gong82 likes this.
  12. coopervid

    coopervid Well-Known Member

    Or did you mean Cheddarson Pete? :sneaky:
     
  13. Pete

    Pete Forum Admin Staff Member

    That's strange - the drone tries to decode AVC and the Intel API says "unsupported".
     
  14. Ch3vr0n

    Ch3vr0n Translator NL & Mod

    Anything you want me to test/do?

    Sent from my Pixel 3 XL using Tapatalk
     
  15. Pete

    Pete Forum Admin Staff Member

    I don't have any ideas at the moment, the Intel drivers are terrible when it comes to tracing down problems. All you get is a "no", when hundreds of causes are possible.

    If it's not too much hassle, can you see if it works when you remove the nVidia and plug the actual monitor into the Intel port?
    (Though connecting a monitor should not be required, that was only required when using D3D9 - but according to the output DX11 was used).
     
  16. Ch3vr0n

    Ch3vr0n Translator NL & Mod

    With or without Nvidia drivers still installed.

    Sent from my Pixel 3 XL using Tapatalk
     
  17. Pete

    Pete Forum Admin Staff Member

    I don't know, you judge that.
    My problem is that I have no idea whatsoever. For me, the twin-setup Intel GPU + nVidia GPU works on two different PCs.
    So as long as I don't have a clue whether it's the fact, that there are two GPUs or the fact that there are two sets of drivers or the fact that maybe some part of the drivers is missing, there's not much more left to do but playing around with it and trying what works and what doesn't.
     
  18. Ch3vr0n

    Ch3vr0n Translator NL & Mod

    ok, i'll tinker with it this weekend then. Can't afford to "mess" with the PC during the week :)
     
  19. DrinkLyeAndDie

    DrinkLyeAndDie Retired Moderator

    I've had no luck with Intel QuickSync with drivers dating back to 2019 when it comes to CloneBD. I posted about it back in February of 2019. The last drivers that I am aware of that worked with CloneBD were from 2018. Reference: https://forum.redfox.bz/threads/int...100-6519-breaking-quicksync-in-clonebd.76588/

    With the above being said, since I bought an NVIDIA RTX card I've had no use for QuickSync but it would definitely be nice as an option for people, in general.

    Hardware:

    CPU: Intel i7-6700K
    iGPU: Intel HD Graphics 530
    Discrete GPU: RTX 2060

    Code:
    C:\Program Files\Elaborate Bytes\CloneBD>drone.intel.x64.exe -supportedcodecs
    Trying 00000304 @ version 1.9
            result -3
    Trying 00000302 @ version 1.9
            result -3
    Trying 00000305 @ version 1.9
            result -3
    Trying 00000306 @ version 1.9
            result -3
    Trying 00000307 @ version 1.9
            result -3
    Trying 00000003 @ version 1.9
            result 0
            query -> 1
    
    C:\Program Files\Elaborate Bytes\CloneBD>
    2020-08-19_184825.png

    2020-08-19_185101.png
     
    Last edited: Aug 19, 2020
    tectpro likes this.
  20. Pete

    Pete Forum Admin Staff Member

    Your results are a bit different from Ch3vr0n's.
    His drivers said "Yes, I'm here, but I won't handle video, only games".

    Yours don't even initialize.
    The codes are:
    0x304: activate QuickSync using DX11 on any suitable graphics device.

    And because Intel driver at least used to have a bug, that would have 0x304 fail sometimes, CloneBD continues with
    0x302: activate QuickSync using DX11 on device 0
    0x305: activate QuickSync using DX11 on device 1
    0x306: activate QuickSync using DX11 on device 2
    0x307: activate QuickSync using DX11 on device 3

    Every time the response is "unsupported".
    Until the last one:
    0x3: activate Quicksync any possible way.
    That works, but that's no surprise - it's the super-slow software-QuickSync (orders of magnitude slower than ffmpeg). That one got installed by CloneBD itself.

    I have an nVidia GTX1060 and Intel HD530.
    Intel driver was September 2019, but I updated just now - June 2020. All fine.

    So it doesn't seem to be the driver version or the actual chip and not purely the fact that we have another GPU installed.