Posts by Sabaat Ahmad

Quote from gazm2k5

I got my Raspberry Pi B+ model and APA102 lights working with a USB screen grabber, but have no idea how to set up HyperCon for the Windows screen grabber. Nor can I figure out how to set up the screen grabber itself.

Are there any instructions? I can't figure out what any of the settings refer to, I don't know what ports I'm meant to be using, I've tried all the logical guesses but it's not working. Could really use a noob guide to help set it up.

You basically need to enable proto port on Hyperion and point the software to it. Also give priority to proto over others in Hyperion.

Quote from vasyltheonly

Hey, just wanted to say that this works great on my ultrawide monitor, color reproduction is great and low delay. I have one question, is there a reason why when Start Capture is enabled, Gsync does not work anymore? The second that I once again Disable Capture, gsync function as usual. Any insight would be great.

not sure why that happens. unfortunately I don't have a Gsync monitor

Quote from bastianum

Hi Sabaat,

I set up Hyperion on a Raspberry Pi 3 with WS2812B LEDs connected, and it works fine from HyperCon on my windows machine. I can send colors through the panel and the LEDs change accordingly.
I then installed your ScreenGrabber and tried to set it up, but it does not work for me. using Windows 10, I think I configured something wrong.
Which IP do I need to enter? I connect to my Pi over 192.168.3.116 in HyperCon, the SSH Log says localhost:19444 though.
As well, is it right that I deactivate the internal and the external grabber in the config.json?
Thanks for your help in advance.

Bastian

EDIT: I am able to get a connection now (with 192.168.2.116:19444), I get a message that the connection is established. As soon as I start a YT video though, I get this error message:

2018-10-24 13:49:59 [ERROR] [5] HyperionScreenCap.Helper.HyperionTask.StartCapture:0 - HyperionTask[ConfigurationId: 1c49f1]: Exception in screen capture attempt: 1
System.Exception: Error occured while sending image to server: In die Übertragungsverbindung können keine Daten geschrieben werden: Eine vorhandene Verbindung wurde vom Remotehost geschlossen. ---> System.IO.IOException: In die Übertragungsverbindung können keine Daten geschrieben werden: Eine vorhandene Verbindung wurde vom Remotehost geschlossen. ---> System.Net.Sockets.SocketException: Eine vorhandene Verbindung wurde vom Remotehost geschlossen
bei System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
bei System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
--- Ende der internen Ausnahmestapelüberwachung ---
bei System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
bei HyperionScreenCap.ProtoClient.SendRequest(IMessageLite request)
bei HyperionScreenCap.ProtoClient.SendImageToServer(Byte[] pixeldata, Int32 width, Int32 height)
bei HyperionScreenCap.Helper.HyperionTask.TransmitNextFrame()
--- Ende der internen Ausnahmestapelüberwachung ---
bei HyperionScreenCap.Helper.HyperionTask.TransmitNextFrame()
bei HyperionScreenCap.Helper.HyperionTask.StartCapture()

It basically says that there is an error while screen capturing and that no data can be written into the established connection.. any idea what went wrong here?

Best

Bastian

Display More

Replied on GitHub

Quote from sh4dow

Hey Sabaat,

I have connected via HDMI an ultrawide monitor ( 2560x1080 ) to my laptop. I have it as an extended monitor setup. The index of this monitor is 1. The laptop display is 0.

The thing is that the monitor with index 1 resolution is viewed as 4480x1080 by hyperion screen capture. I think that's because of the extended monitor setup of windows because 2560 + 1920 = 4480.

Can it be possible for the hyperion screen capture to grab the actual resolution of the monitor rather than the extended resolution of them both ?

Thank you.

Edit: A temporary fix for this would be setting the external monitor with index 1 as the main display. This though will mess with the width of the other monitor.

Display More

This issue is now fixed. Please download and install v2.6. Note that if "Check for Updates" option does not work, you will need to manually download the update from GitHub.

Quote from sh4dow

Hey Sabaat,

I have connected via HDMI an ultrawide monitor ( 2560x1080 ) to my laptop. I have it as an extended monitor setup. The index of this monitor is 1. The laptop display is 0.

The thing is that the monitor with index 1 resolution is viewed as 4480x1080 by hyperion screen capture. I think that's because of the extended monitor setup of windows because 2560 + 1920 = 4480.

Can it be possible for the hyperion screen capture to grab the actual resolution of the monitor rather than the extended resolution of them both ?

Thank you.

Edit: A temporary fix for this would be setting the external monitor with index 1 as the main display. This though will mess with the width of the other monitor.

Display More

This seems like a bug in the code; can you please open an issue on GitHub for this. I will investigate this.

I think DX9 capture should still work fine.

Quote from abrenoch

Best of luck - I have tried a ton of different devices and configurations (including the combo dave posted here) and none of it has worked for me. I honestly am at a loss because all the pieces are there and it still just doesnt work (cant get a signal to the pi at 4k even with 2 different scalers).

Please be sure to share your results!

I think you should buy "Dream Screen" from a startup which claims to do 4K and HDR. Otherwise one could also buy a ~$300 device that someone mentioned in this forum.

Personally I am still sticking to the windows grabber plugin for Hyperion which works with 4K and HDR.

Quote from Xynar

Hi Dave

Is there any confirmation that this splitter and downscaler combo that you have supports HDR?

I haven't got any confirmations yet. But if you think about it, supporting HDR for Hyperion would probably mean to covert 10-bit color signal to 8-bit. It will also required the device to remove the HDR instructions from the main signal. I haven't seen any cheap device that would do this.

Quote from abrenoch

Hey Sabaat, I'm taking my best shot at an android grabber right now and have a quick question for you!

Assuming you are using the protobuf server to send image data to hyperion, what dimensions would you recommend for the image data? I see in your configs you have an 'image scaling factor', but I have no idea what that actually equates to. Right now I'm looking at 427x240, but I'm not sure if that is too large or not.. I'm getting some opengl errors when trying to render it smaller but I'm not sure if that is a fault of my own or not yet.

Just trying to get an idea of what you guys are currently doing!

Thanks!

Image scaling factor just mean by how much to divide the screen resolution. So if the image scaling factor is 32 and screen resolution is 1920x1080, then the image sent to Hyperion has the size 60x33. Ideally you would want to send an image close to 60x60. That should be fine for running the ambient lights.

Quote from Rick164

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?

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.

Quote from pv_8

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

Quote from Rick164

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

Quote from pv_8

Hi,

Thanks for making this!

I have a problem where the program just insta-shuts down after I open it. Sometimes after rebooting my PC it will work, but only around 1 in 5 times will it connect to my pi & stay open.

Here's a link to my log file

Thanks

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.

Quote from diddydave

I just got this set: https://www.clearvisionsystems.co.uk/electronic-con…ombination-pack
So far testing with the 2017 shield TV it works.

This looks promising. The product page says that it supports HDR. Can you try grabbing a HDR signal please?

Quote from abrenoch

Thanks for the response.

Understood, I'm thinking (read as: praying to all the gods) I might be able to make it work with my configuration. ARC Isn't a concern for me since my shieldtv provides all the functionality from the TV I would need ARC for. I did pick up this thing (https://www.hdtvsupply.com/18gbps-repeater-4k-scaler.html) which I am hoping will solve any issues with the signal before it hits the convertor.. So hopefully all the pieces will fall into place for me!

Great work with the windows screen grabber also! I would love to figure out something for android but it presents a lot of problems.

Are you trying to do a real time grabbing of an Android screen?

Quote from abrenoch

Sabaat - am I understanding correctly that you where going directly from the splitter to the RCA adapter? Is that a sustainable setup (assuming you have it working now)?

I kind of have the feeling that your converter may have burned out because it was being forced to run 4k@60 - I have that same one and I believe it only supports the HDCP1x standard where 4k@60 requires the HDCP2x standard. Purely speculation.

I'm trying to make this work with my setup, but the splitter I tried thus far has no edid management and forced my resolution (I'm using a shield TV) to 1080p.

I did however grab a little gizmo that is supposed to downscale a 4k@60 signal to 1080p@60 (which is compliant with HDCP1x), but dumb me didn't realize I need a splitter with edid management to actually use the feature the way I intend. The only problem is the splitter advertised to work with it does not advertise as supporting CEC, so I am a bit hesitant to grab it right now.

I ended up removing the grabber, splitter etc from my setup cause it did not work perfectly for me. I was unable to find any cheap solution that would work with HDR and hence I am using the Windows Screen Grabber ( that I am working on: https://hyperion-project.org/threads/update…n-grabber.1018/ ) with my PC.

The splitter I linked does support CEC and EDID management. The TV will also recognize it having ARC capability. However, ARC will not work. One thing that I learned while playing around with these things is that EDID management is that the splitter will never act as a signal convertor so if you connect two devices to it with different supported resolutions, one will not work.

Quote from Rick164

For the API server not starting bug made a fix here:

https://github.com/RickDB/Hyperio…a6c16440b8f6589

Grapevine v4 documentation site not loading so went by trial and error and tested working after that change

Great to see this fix. Can you please send a pull request or else I'll include this fix manually.

Quote from drc85

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

Display More

It should work using AVR

Quote from drc85

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

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

Quote from drc85

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

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

thanks

Display More

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.

Do note that due to a bug in the latest release, the API is not working.

https://github.com/sabaatworld/HyperionScreenCap/issues/13