[Updated 10/08/2018] [v2.6] Multiple Displays + Servers, 4K UHD (DirectX 11) Windows Screen Grabber

  • It's a basic HTTP server for now, current commands are:


    http://localhost:29445/API?command=ON&force=false
    http://localhost:29445/API?command=OFF&force=false


    Where force parameter means force the command thru even when we have time exclusions active, this is used in Kodi and Mediaportal addon.
    Additional command which returns capture active state (true / false):


    http://localhost:29445/API?command=STATE


    Original topic from the older fork with some more info:


    https://forum.team-mediaportal…tive-to-atmolight.137035/

  • nice work
    but im still a little bit confused how to use it...
    is there a instruction somewhere?


    im runnign the grabber on windows 10 with ubuntu subsystem + hyperion


    i dont have the hardware for my ambilight yet so i cant really test with a usb grabber...
    does your windows grabber also supports a usb grabber?


    im also not sure what ip adress i have to enter in your grabber for hyperion server?
    (the hyperion server ip is where hyperion service runs?)


    also im not sure what i need to do inside of the hypercon config file.
    do i need to active or deactive the intern and extern grabber?


    a little insturcition how to setup up the basics would be very nice :D


    i also found a error in the gui... im using windows 10 64bit 17063 release preview


    thanks


  • Try this solution for fixing the UI: https://hyperion-project.org/posts/8183/


    IP address should be of the RaspberryPi or any other machine which runs Hyperion service. I haven't used Ubuntu subsystem but if it's the same machine use the address 127.0.0.1 or localhost.


    The grabber won't support USB grabber. That you can use with Hyperion directly provided that you have the required drivers.

  • thanks, i will take a look at the fix...
    i got hyperion runnign on win10 subsystem, im really new to linux, its working but i still need to work on the autosart... because of windows...


    now at least i know i need to use the ip where hyperion service is running (in my case the windows machine) inside of the windows grabber...
    but im still not sure if i also need to change something inside of the config from hypercon?


    what grabber options i have?
    when using the grabber built inside of the hypercon there is no windows grabbing...
    can i use both?
    i would like to use the windows grabber(from you) and a extern usb grabber at the same time with priority settings...
    so if no signal from the usb grabber is coming it should use your grabber...
    is this possible?


    i will get me a grabber in a few days, then i can test it better... without the hardware its hard to explain and test :D

  • thanks, i will take a look at the fix...
    i got hyperion runnign on win10 subsystem, im really new to linux, its working but i still need to work on the autosart... because of windows...


    i will get me a grabber in a few days, then i can test it better... without the hardware its hard to explain and test :D


    Yes, priority will work but the problem is that the USB grabber will show a no-signal available image (vertical lines) when you don't provide any input to it. Hence, the grabber will continue to be prioritized and windows grabber will never be consumed.


    Windows grabber uses the Proto port configuration in Hypercon

  • thanks alot,
    i will need to get the setup up before i can continue on planning any further.
    one more question.... for understanding the grabbers for hyperion...


    im planning on connecting all devices to a hdmi receiver with two hdmi outputs. one of the devices is the htpc with hyperion service on it.
    the hdmi2 output of the receiver will be connect to the usb grabber.
    The usb grabber is connected to the htpc...
    so basically the htpc would grab its own hdmi output..
    is this possible?


    if yes, i think there would be no need for a intern graber, kodi integration and windowsgrabber for me...
    i could just let everything run over the usb grabber..


    sorry for all the questions


  • It should work using AVR


  • Thanks for the log file. Unfortunately I not able to reproduce the issue for some reason. It was happening to me earlier though. Hopefully I can find the root cause.

  • Noticing an odd bug:


    - Enable HSC either via systray or API
    - Start playback of 24P content (switches from 60hz) via Kodi for instance
    - Tested and toggle capture still works while playing
    - Stop playback
    - Toggle via systray and API reports success but capture is still running, logs show successful shutdown without errors.
    - Only way to fix atm is to restart HSC


    Best guess is some capture task isn't attached or incorrectly marked as successfully shutdown and only happens when I use refresh rate switching, anyone else that can reproduce this?


  • That shouldn't happen! Specially something which depends on refresh rate. Maybe I missed something with the shutdown code.


    Noted down here: https://github.com/sabaatworld/HyperionScreenCap/issues/19

  • Thanks for the log file. Unfortunately I not able to reproduce the issue for some reason. It was happening to me earlier though. Hopefully I can find the root cause.


    Hi, I was playing around with the config file settings last night to try & fix this - & I think it might be linked to the automatic capture on startup. I set that to false and then just double click the icon to start capture & it seems to work every time without shutting down.
    Hopefully that info will help you!
    Cheers

  • Hi, I was playing around with the config file settings last night to try & fix this - & I think it might be linked to the automatic capture on startup. I set that to false and then just double click the icon to start capture & it seems to work every time without shutting down.
    Hopefully that info will help you!
    Cheers


    Yup, that is indeed causing the issue. I think I have found a fix that I'll be adding to the next release. Issue is being tracked here: https://github.com/sabaatworld/HyperionScreenCap/issues/15


  • I'm still not able to find what is causing this issue. It would be great if you could help me debug it with Kodi.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!