[DIY] Amblight project/guide - Hyperion - WS2801/ WS2812B / APA102 (4 Viewers)

[Rick164]

Checked the Hyperion handler and there's currently a 250ms delay for led disable actions to allow color commands to be processed before we do the clear priority channel (mostly for network/hardware delays) which is what Hyperion uses for clearing leds, since it's random blue leds instead of last state colors it's most likely an hardware issue however.

We could also make the delay configurable but for now attached an test version based on the DEV_Delay_not_starting_correctly branch with a Hyperion led disable delay of 500ms which sends the clear command 3 times with an 250ms interval, if this solves it then it also means there's a significant delay on the hardware end.

 

[TheBatfink]

OK. Thanks for looking at it! It's strange because, if anything, I'm toying with adding a manual delay.. the lights seem just ever so slightly ahead of the picture but not enough to totally bug me.

I'm going to test with Live Mode on menu's off and also with the old MePo exe, then move onto your branch for testing. Seems since I used that new .exe for live mode in menus MePo is behaving funny and not resuming like it should. I've had to hard kill MePo twice since the weekend when I made the swap out and it's been some time since I had to do that. Could be unrelated of course.

I also started turning off the lights with Hyperion app at the end of the night to kill of the blue LED's. I find whenever I do this, MePo never seems to regain control of the lights (can't turn them on and they never activate with media etc.). I have to shh in and restart Hyperion, then it all starts working again on it's own without interaction from me.

The joys of PC's

Edit: Checked out the log. Hyperion is complaining whenever MePo resumes after I turned the lights off with iPhone Hyperion app. Any idea why this is?

Also, since using the new MePo.exe and dll from @Lightning303 Auto3D is freaking out too.. Maybe this is why MePo fails to resume a few times recently? Attaching logs.. Thanks!

 

[TheBatfink]

So I tried with the old exe and no Live Menu lights, the dim random blue lights remain. Tried with the delay version you kindly posted and sadly I still have the same random blue dim leds.

Turning the brightness right down with the app is still turning them all off completely. This is the app I am using: https://github.com/tvdzwan/hyperion/wiki/Hyperion-Remote-for-iOS

 

[Lightning303]

I also started turning off the lights with Hyperion app at the end of the night to kill of the blue LED's. I find whenever I do this, MePo never seems to regain control of the lights (can't turn them on and they never activate with media etc.). I have to shh in and restart Hyperion, then it all starts working again on it's own without interaction from me.

Have alook at the priorities within hyperion. If your ios app has a higher priority than mp, and you set your leds to off with it, then mp cant change anything anymore because its priority is not high enough. I think lower values mean higher priority, but not 100% on that.

For the blue lights, have you twisted your cables? Just so we are 100% sure we can rule this out, can you attach a photo if you have twisted them?

Regarding Auto3D and resume issues, will have to look at that in more detail, maybe tomorrow. Also if you run into another MP freeze, so you have to kill it, can you attach those logs please?

 

[TheBatfink]

The logs above were directly after the freeze on resume (screen showed the time the system when to sleep in the MePo window and it never recovered and refreshed). There was also a Trakt rating dialogue open at the point it went to sleep, could be that. I killed it with task manager and took the logs above immediately anyway

Not done the twisting yet. I need to get help to get the TV off the wall so will have a go at the weekend. I'm assuming you mean the wires coming out of the Arduino?

Will have a play with the priorities, I had wondered what that did the app has no config for it that I have seen will go the trial and error route to see what works! Thanks!

For info I moved the original exe back, will see if that really is the cause of the Auto 3D errors in log and the resume issue. Could of course be total coincidence. Always seem to touch one thing and break two others!

 

[TheBatfink]

I can confirm higher value = lower priority. Set app to 101 and set a fixed colour, MePo takes over when media starts. It does remember the previous state Hyperion was in prior to media playback as when it ended it returned to the fixed colour rather than turning off. Guess that is intentional?

 

[Lightning303]

The logs above were directly after the freeze on resume (screen showed the time the system when to sleep in the MePo window and it never recovered and refreshed). There was also a Trakt rating dialogue open at the point it went to sleep, could be that. I killed it with task manager and took the logs above immediately anyway

Ah ok Thanks!

Not done the twisting yet. I need to get help to get the TV off the wall so will have a go at the weekend. I'm assuming you mean the wires coming out of the Arduino?

Yeah, the 3 wires going to the leds.

I can confirm higher value = lower priority. Set app to 101 and set a fixed colour, MePo takes over when media starts. It does remember the previous state Hyperion was in prior to media playback as when it ended it returned to the fixed colour rather than turning off. Guess that is intentional?

I would say no, if you set AtmoLight to LED disabled, they should get disabled, but it sounds like AtmoLight is only lifting the priorities. But @Rick164 is the expert on all things Hyperion. So lets see what he says .

 

[Rick164]

In the Hyperion app there's an option to clear all priorities called "clear all" which flushes them if you ever have any issues with priorities being stuck as they are persistent and only cleared when the app or AtmoLight sends that clear command.

I can confirm higher value = lower priority. Set app to 101 and set a fixed colour, MePo takes over when media starts. It does remember the previous state Hyperion was in prior to media playback as when it ended it returned to the fixed colour rather than turning off. Guess that is intentional?

That is most likely because the AtmoLight priority channels get cleared on playback stop and any remaining priorities (higher values) if set get activated again, so if you set the color in the Hyperion app and forgot to clear it then that color will be activated again if no higher priority channels take precedence.

 

[Lightning303]

That is most likely because the AtmoLight priority channels get cleared on playback stop and any remaining priorities (higher values) if set get activated again, so if you set the color in the Hyperion app and forgot to clear it then that color will be activated again if no higher priority channels take precedence.

Question is, at least from me, ist that the right behaviour? If i use my HTPC and it is taking control of my ambilight, and i tell it to disable the leds, shouldnt the leds be disabled? Instead of just getting cleared from their priorities?
If i select "LEDs disbled" in the context menu, i want them to turn off, and not to take the color that was used before i started my htpc.

@TheBatfink i checked the Auto3D source code, and the changes done to MP.exe and core should not interfere with it. Can you double check that Auto3D is actually not working with the patched files, but working without them?
Not seeing anything regarding resume problems either. Have you maybe used some other patched files before? Maybe from the resum problem thread?
Of course i also could have messed up while compiling the files :/. Will redo them later.

 

[TheBatfink]

Hey @Lightning303 to my knowledge this is all standard MePo. I try and avoid swapping out core files because of the trouble getting support. It's 1.10 final so I could of done something between it's release and now but I don't remember doing anything like that. The only thing I currently use that isn't straight out of Extensions Manager is OV 2.0 beta.

I haven't seen any resuming issues since removing the .dll and .exe. I know with the nature of MePo it could be anything causing it though but it's Client + Server so should be no delays with TV Service and it's a reasonably beefy HTPC. Raid SSD, 8GB ram drive - ussually resumes in like 3 seconds flat.

I checked the logs and still have the Auto3D errors but no resume issues. I'll follow up with him why they are there..