Beiträge von Sabaat Ahmad

Zitat von darkside40

Okay hooked the LED's incl. the Arduino up to an 8€ Orange Pi Zero i had laying around, watched the first 4K movie with Hyperion Screen Cap and it is working.
Now i have one problem, i cant manage to autostart Hyperion Screen Cap when Windows starts. Tried it via Autostart Folder and Registry, result was both times the same. It wont start anymore and directly crash after that even if i try to start it via the Desktop icon. Even new install does not solve it. I have to delete the Settings which are somewhere located inside the Users Folder and redo the Startup Wizard to get it running again.

Could you add a "Startup with Windows" Setting in the next Version?

To be honest this program makes Kodi on Windows useable for me, because without i could only run outdated solutions to get Ambilight.

Once the software starts, there is an option in the setup window to enable launch on startup. I think that you are facing one of these issues:

• One of the user's has reported that the screen grabber does not work when "explorer.exe" is not running: https://github.com/sabaatworld/HyperionScreenCap/issues/14
• There is another issue where the software does not start even on clicking the desktop icon: https://github.com/sabaatworld/HyperionScreenCap/issues/15

Zitat von darkside40

Is there a way to use this grabber with my directly via usb connected adalight clone LED's, or do i have to have an rPi running the hyperion daemon for this?

I don't think that there is a way to run the LEDs directly.

Zitat von azzuro

hello @Sabaat Ahmad
i try to use the V2.3 version without sucess.
my culprit is the API server, it don't start,

I think there is a code issue introduced in v2.3 which does not allow API server to start. Did you try using API server in v2.2?

I have opened an issue to track the fix: https://github.com/sabaatworld/HyperionScreenCap/issues/13

Zitat von dolittle

Hi,

I'm rugreat if the grabber would recognize this and also automatically adjust the scaling factor. In this case it should change from 32 for 4k to 16 for FullHD.

Thanks very much.

Alles anzeigen

Hi,

To fix the issue where only one corner is being captured in your games at full HD, try the following fix:

• Go to Program Files and locate HyperionScreenCap.exe
• Right click -> Properties -> Compatibility
• Set Override high DPI scaling behavior to "Application"

Zitat von dolittle

Hi,
unfortunately running the app as administrator didn't do the trick. It crashed again. Please see the log attached

and OFF completed
2017-10-27 19:53:43 [INFO] [7] HyperionScreenCap.MainForm.ExecuteToggleCaptureCommand:0 - Toggle capture lock unset
[/SPOILER]

Thanks for helping

I have logged the issue here: https://github.com/sabaatworld/HyperionScreenCap/issues/12

Zitat von dolittle

Ok. Now I was able to capture the error. I started the aerial screensaver manually with an active screengrabber. As

I have no idea where the actual error occured but I hope it helps to track it down.

Thanks again.

That helps a lot. Thank you. Seems like for some reason the app does not have access to view the screen saver. I'll try it out with the Ariels screensaver but for now can you try running the application as Administrator on Windows and see if that helps.

Zitat von dolittle

Hi,
thanks very much for the new version. My logging shows a reoccurring exception that sometimes appeares also on the desktop as a notification.
.... In this case it should change from 32 for 4k to 16 for FullHD.

Thanks very much.

Thanks for sharing the log.

1. It seems like like the capture works for you some times. Can you tell me when does this error happen?
2. Screen capture does not work for Netflix and other such apps that specify that the content they are displaying is considered as protected. When the frame is captured, this section of the screen is rendered as a black rectangle. If you come across any solutions for this then let me know.
3. Capturing the above left portion is happening because the screen resolution changes when the app is launched. I'll try to think of a short term fix for this. My long term plan is to implement a new technique to capture DirectX applications like games which will greatly improve the performance the LED lights without impacting the gameplay (FPS). I have logged this issue on GitHub: https://github.com/sabaatworld/HyperionScreenCap/issues/10

Zitat von Rick164

@Sabaat Ahmad

For multi-server support there's a separate branch:

https://github.com/RickDB/Hype…enCap/commits/multiserver

Using that at the moment to switch between PC and media-center (2 led setups connected to 1 rpi) but code wise it could use some cleaning up and improving as it was meant for quick fix here
When using DX11 capture there's a 2-3s delay to the leds which I can't pinpoint yet but cpu load wise it's very nice with max 1% on the 1800X

Alles anzeigen

I'll look into the multi-server code to see if I can copy over some of it.Thanks!

I have been using this with the RPi connected over LAN to my router. This 2-3 second delay was present when a lot of frames were being sent over to Hyperion. I fixed this my adding the MAX FPS field which explicitly delays the next frame capture. If you are not using the default settings on the advanced tab, can you try them out.

More details and download links can be found here:
https://hyperion-project.org/t…dows-screen-grabber.1018/

Hello @sl81! Do you know a cheap downscaler for 4K -> 1080p?

I finally wrote my own Windows grabber that supports 4K @ 60 Hz that uses DirectX 11 to capture the screen.

Demo

Forum
https://hyperion-project.org/t…en-grabber-available.1018

This happens when you don't have enough power available for all LEDs. Try out two things:
1. Connect power to both sides of the LED strip - Data line should be only connected from one side
2. Change the LED count being used by Hyperion and try to turn half of the LEDs white. If they turn white then it means your power supply is the issue.

Zitat von Flautze

thanks for the fast reply.
Protoserver is set up, about the priotity I will see. As I dont use an external grabber is it okay to deactivate both I guess.

About preview: I just thought I can - for example - on the Hyperion see a grab of the Screen. SO I guess I will have to wait for my LEDs.

The error which Comes up is from Windows. Googling it suggests it is somehow Windows Update related. It could jsut happen if you deactivate too much stuff in Windows (Antispy), therefore I want to try with a fresh install of Windows. I will let you know if that worked for me.

Use the version 2.2 that I just released. This version automatically logs everything to a log file which you can share with me to help me fix any issues that you are encountering. There are other bug fixes as well.

Zitat von Flautze

First of all thanks for doing this.
I have been able to successfully install. Having a bit of Trouble (think it is a Windows 10 issue though).
[I can connect with HyperionScreenCap, but after like 20 seconds I get Windows error - Out of Memory]
I will try a fresh install of Win 10, hopefully this will go away.

But my question: How do I have to set up Hyperion to use the Screencap? I have deactivated the internal and external grabber Is that even correct? Is there something else I have to adjust? Is there some way - without LED to check if Hyperion can use the sent data ?

Hyperion is running on a Pi Zero connected via wifi in headless mode. Data is sent via Protobuffer.
At the Moment I dont have LEDs yet, they will arrive later this or next week.

Alles anzeigen

Another user has recently reported the OutOfMemory Issue: https://github.com/sabaatworld/HyperionScreenCap/issues/5

I'm not sure what is causing this right now so I haven't been able to fix it up yet. Setting up Hyperion to the data sent by the Windows Grabber is easy. You just need to ensure that the Proto port is enabled and that the priority used by the screen grabber is the lowest among all the sources Hyperion is configured to use.

I am not aware of any solution that will let you see that the LEDs will work. The RPi's CPU usage could be one indication of the data being processed.

Zitat von dolittle

Hi,
thanks for the fast reply. I'm running Windows 10, so I think the system should be up to date.

But I'll watch for the exact error message. It is possible that it's different. Unfortunately it's just displayed in a notification box. Is there a way to log it? I'll let you know as soon as I can get the exact message.

The error message will probably be different for you. If the screen capture keeps failing for approximately 30 seconds, it is turned off and the error message is displayed.

It won't get logged at the moment. I'll look into what can be done about the logging events in the apps to enable debugging. If you know how to use Visual Studio, you can clone the source code and add a break point to debug.

Zitat von dolittle

Hi,
at first I'd like to thank you very much Sabaat. Very nice work. I love it. Almost no lag with 4k and 1/16 scaling.

But experienced the same error as Brindosch from time to time. This is what the screen shows when clicking on the "view available DX11 monitor" option.

The adapter and monitor index seems ok to me.

Thanks again for your superb work.

Alles anzeigen

The adapter and monitor index settings seem to be correct. The error DXGI_ERROR_UNSUPPORTED means that DX11 is not supported by the graphics card hardware. I think in addition to the that you might need Windows 7 Service Pack 1.

Is this the error you get? And when does the error happen?

did anybody get 4k working with the RCA converter mentioned in this thread?

Zitat von sbouba

Hi there,

Just wanted to say thanks for your work. It works perfectly well on Windows 10 with DX12. I'm on a 21:9 screen with 3440x1440 resolution. No lag at all and 0.1% cpu usage. Great work ! Thanks again

Since you are on a 1440p resolution screen. You can also try to decrease the Image Scaling Factor value. That will send a higher resolution picture to Hyperion and will probably (not tested yet :D) provide more accurate colors per LED. More information can be found in the "Help" tab of the Setup window.

Zitat von WaRFaiR

How did you configure the splitter DIP-swiches? EDID MIX?
Bought the same splitter, but struggling to get it to work at 4k@60Hz.
I can still only get 4k@30Hz with the RCA-converter plugged into the splitter. Tried a bunch of different DIP-switch settings, but nothing.

Summary of my setup:
Shield TV (2015) connected to input on Denon AVR-X1200 Receiver. Receiver output goes to splitter input, and output1 to TV Panasonic TX-65CX802B and output2 connected to SSRiver HDMI-2-RCA.

Thanks!

I have actually developed a DirectX 11 capture Windows grabber to run my LEDs at almost 60Hz. See: https://hyperion-project.org/t…r-windows-available.1018/

DIP 1 2 3 4
X 0 0 0 : copy output1 EDID only - This does not work unless the RCA convertor supports 4K @ 60Hz
X 0 0 1 : EDID MIX
X 0 1 0 : EDID Download (RS232)
X 0 1 1 : 4K X 2K 30HZ
X 1 0 0 : 4K X 2K 60HZ - Works with a 4K @ 30Hz RCA convertor (). I still got 60Hz on monitor.
X 1 0 1 : 1080P 3D 2ch
X 1 1 0 : 1080P 2D 2ch
X 1 1 1 : 1080P 2D 5.1ch

These above EDID modes are copied over from AliExpress. More accurate information is available in the splitter's user manual. Note that I had tested this stuff out with a Windows 10 PC and not Nvidia Shield.

Please do not buy the RCA convertor from Amazon that I linked in this post. It did not last more than an hour.

Zitat von b1rdhous3

Hi this sounds great. I quickly tested it (not much time :() and it worked ootb

On my quick test I recognised one thing: If you right-click on the tray icon it always say "Change DX9 monitor index" but I think I am using DX11 since it is checked in the settings as the screen capture method.

But: Great work so far!

Yes, that needs to be fixed. I did not work much on improving the tray icon options. And I think the Change DX9 monitor index option is partly broken as well.

Zitat von Brindosch

So, i will give some feedback
On Windows 7 64bit i get this in the following order with DX11:

• Connected to Hyperion XYZ With notifications set to error i get this:
• After 10-15seconds: Error occured during capture: The object ref had no object instance (The second message part was german, this is a vague translation

DX9:

• Worked

Ping all people of the old topic, not sure if they recognized your work you put in here. Also feel free to post improvement/extension ideas
@Doc.Ex @HalbesHaehnchen @Rick164 @TPmodding @danielfmo @Slimboyfat @LooseChange @nash @iiidefconiii

Alles anzeigen

Can you please verify the selected monitor and adapter index values in the settings? Also please share a screenshot of the message box that comes up when you click "view available DX11 monitor" option.