1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

WIP Windows Grabber

Discussion in 'Development' started by Brindosch, 10 May 2016.

  1. Rick164

    Rick164 Administrator Staff Member Administrator

    Messages:
    159
    Hardware:
    RPi2, +Arduino, +AtmoOrb
    Dxdiag and config looks fine, same hardware setup I had last month (GTX970) as well so can rule out any issues there :)
    Below is a new build which will output all displays it can find to the debug.log including their indexes, also a few other things to try:

    - System DPI is currently set to 144 DPI and while I don't suspect this can interfere with capture would try it with 100% (no upscaling)
    - Would try english language / locale, while unlikely we can then rule that out as well.

    Download link for debug build:

    https://1drv.ms/u/s!Aik_1r9bUPQAihHnUshtTZJpSLk_
     
  2. danielfmo

    danielfmo New Member

    Messages:
    13
    Hardware:
    RPi2, 32/64bit, +Arduino, +nodeMCU/ESP8266
    @Rick164 Thank you for the new build but same result :(

    I've attached the debug.log, HyperionScreenCap.exe.config and the new DxDiag.

    Regards
     

    Attached Files:

  3. Slimboyfat

    Slimboyfat New Member

    Messages:
    5
    Hardware:
    RPi1/Zero, +Arduino
    Hi, i got the same error. This is my debug with 0,1,2 as screen.

    Gonna use monitor with index: 1
    Index: 0
    Device name: \\.\DISPLAY1
    Refresh rate: 60
    Is primary: True
    Gonna use monitor with index: 0
    Index: 0
    Device name: \\.\DISPLAY1
    Refresh rate: 60
    Is primary: True
    Gonna use monitor with index: 2
    Index: 0
    Device name: \\.\DISPLAY1
    Refresh rate: 60
    Is primary: True
    Gonna use monitor with index: 0
    Index: 0
    Device name: \\.\DISPLAY1
    Refresh rate: 60
    Is primary: True
    Connected to Hyperion server on 192.168.1.124!
    Gonna use monitor with index: 0
    Index: 0
    Device name: \\.\DISPLAY1
    Refresh rate: 60
    Is primary: True
    Connected to Hyperion server on 192.168.1.124!
     

    Attached Files:

  4. Rick164

    Rick164 Administrator Staff Member Administrator

    Messages:
    159
    Hardware:
    RPi2, +Arduino, +AtmoOrb
    Very odd, so one display with the correct property readout (index 0) out but not working :(
    Not sure why at this point but will dig around in the code a bit :)
     
  5. danielfmo

    danielfmo New Member

    Messages:
    13
    Hardware:
    RPi2, 32/64bit, +Arduino, +nodeMCU/ESP8266
    Hi,
    Just remember one thing... I'm using a TV as a monitor, and despite windows telling me that the refresh rate is 60Hz in all games I get 59Hz instead...
    Just an hint...
     
    • Like Like x 1
  6. Doc.Ex

    Doc.Ex Member

    Messages:
    73
    Hardware:
    RPi2, +PhilipsHue
    Maybe it has something to do with the tv. I only get the error for my tv as well. The tv is connected to an avr which is connected to the pc.
    But my tv outputs 60hz.
    Couldnt try the new version but will when i am home tomorrow evening. Can provide a debug log then, too.
     
  7. Rick164

    Rick164 Administrator Staff Member Administrator

    Messages:
    159
    Hardware:
    RPi2, +Arduino, +AtmoOrb
    Maybe something with scaling or Wndows 10 is handling them differently for some reason, do use it on my TV now and again for Youtube mainly which works with these settings:

    1080p
    60hz
    12bit with full dynamic range in Nvidia control panel

    Scrolled thru a few SlimDX examples and all looks in order so far but might be overlooking something :)
     
  8. Doc.Ex

    Doc.Ex Member

    Messages:
    73
    Hardware:
    RPi2, +PhilipsHue
    I do use scaling when on tv, so maybe that causes the problem. Will turn that off and test tomorrow
     
  9. Slimboyfat

    Slimboyfat New Member

    Messages:
    5
    Hardware:
    RPi1/Zero, +Arduino
    i change my resolution to 1920X1080p and scaling to 100% instead of 200% on windows 10 and got a positiv Connected message!
     
  10. Doc.Ex

    Doc.Ex Member

    Messages:
    73
    Hardware:
    RPi2, +PhilipsHue
    Scaling must cause the issue. It works on my TV when I set the scaling to 100%. Was 125% percent before. I don't know how the scaling works in windows 10 but is it possible to support scaling while grabbing? Because now I can't read anything :D
    But at least it works, so I have got that going for me which is nice :p

    Also, a Hotkey to toggle the grabber on/off would be nice. :)
     
  11. danielfmo

    danielfmo New Member

    Messages:
    13
    Hardware:
    RPi2, 32/64bit, +Arduino, +nodeMCU/ESP8266
    I just confirm that the issue is the scaling, I've tried again to set it to 100% and it works.
    Note that in order to make it work I had to restart the machine, just doing a log out as recommended by windows is not enough.

    Let me know if somehow I can help with a fix to this issue with the scaling and also to make it work with any application other than dx9 :)
     
    • Like Like x 1
  12. LooseChange

    LooseChange New Member

    Messages:
    21
    Hardware:
    RPi2
    Wish I would have known about this grabber a long time ago, I have been sitting with a broken ambilight since Oct 2015. I just put in the IP and ran the app, and my LEDs turned on! Wow this is incredible.

    I use a tv as my monitor and watch tv/movies in media center. win7 64bit, 1080p
    I havent found any demo videos to run yet, but I just wanted to report my excitement :)

    I did notice a problem though, kind of a big deal to me, when I play anything in windows media center the LEDs all go black. So close, but so far.
    VLC, and windows media player both work with the windows grabber but I need media center for all the delicious features such as commercial auto skip, 2 week epg, etc. I am guessing it is a video overlay issue of some sort. Is there anything I can put in the config to make media center video get sent to hyperion?
     
    Last edited: 16 July 2016
  13. Brindosch

    Brindosch Administrator Administrator

    Messages:
    585
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Good! This one is just some months old so nothing to bother :)
     
    • Agree Agree x 1
  14. Doc.Ex

    Doc.Ex Member

    Messages:
    73
    Hardware:
    RPi2, +PhilipsHue
    After using the windows grabber a lot the past weeks I must say I really like how accurate the colours are.
    But some things bother me:
    1. It causes a lot of CPU load. About 12% on an i5 6600K.
    2. It doesn't work on some games and just produces white (Rocket League DX9)
    3. On Ark - Survival Evolved (DX11 I think) it works but causes stuttering. The game is still rendered with 30+ fps but the display output is maybe half of that.
    4. It doesn't support scaling in Windows 10
    Following features would really benefit the experience and usability:
    1. lower cpu usage/more efficient display capturing
    2. Scaling support
    3. automatic disabling when screen can't be captured (this way a physical usb grabber can be used as fallback)
    4. Hot-Key to enable/disable, maybe the possibility to exclude programs from being captured
    Otherwise I really like it. Its faster than the bulky adapter-usbgrabber-chain and has really great colour reproduction. Its just not perfect yet.
     
  15. Brindosch

    Brindosch Administrator Administrator

    Messages:
    585
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    @Doc.Ex
    thank you for your detailed report. For sure developer could look into it :)
    ping @hanselb
     
  16. Rick164

    Rick164 Administrator Staff Member Administrator

    Messages:
    159
    Hardware:
    RPi2, +Arduino, +AtmoOrb
    Last edited: 3 September 2016
  17. Brindosch

    Brindosch Administrator Administrator

    Messages:
    585
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Great work Rick!
    Will test it :)

    // Sad news for slimdx
    Which libs use programs like fraps and such?
     
  18. Rick164

    Rick164 Administrator Staff Member Administrator

    Messages:
    159
    Hardware:
    RPi2, +Arduino, +AtmoOrb
    Not sure, could be native C++ capture like AtmoWin does or SharpDX which might be a better fit :)
     
  19. nash

    nash New Member

    Messages:
    3
    Hardware:
    RPi2, RPi3, 32/64bit
    Hi team,

    Firstly, thank you very much to Hyperion Staff, you are awesome, I can work with APA102 and RPi2 like a charm!
    On the other hand, thanks to Rick and djhansel for the Windows Grabber, it could be the perfect addon for Windows PCs.

    I have Windows 10 Prof. x64 (Anniversary Update) and I have installed the last release from djhansel repository (v1.4) without issues, my config is:
    [​IMG]

    Where 192.168.2.4 is the IP Address on my RPi (I have changed only this, the other options are by default), when I save and close, the Screen Grabber is change to Enabled status, however, my leds strip are grabbing the Kodi (OSMC) and not my PC, do you know what I'm doing bad? Should I change the Port?

    HyperCon works without issues, connecting via SSH... :(
     
  20. Brindosch

    Brindosch Administrator Administrator

    Messages:
    585
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Is your scaling at 100%? I tested the new version on Windows 7 and it works so far.

    //update start post
     
    • Like Like x 1