AtmoLight - 1.18.6.0 [2016-09-21] (2 Viewers)

[Rick164]

You're welcome and glad to have you on the team

 

[TheBatfink]

Hey, me again. I'm having a really hard time with Hyperion at the minute. It's completely stopped working. All I get is connection to Hyperion was lost errors. I can connect via the iPhone Hyperion app no problems.

So I did a full reinstall of my PC. Windows 10 Pro 64bit fresh install, fresh MePo and all the plugins from the extension manager. I still get the connection was lost errors and also now MePo is just exiting to desktop randomly. I just played a youtube video in OnlineVideos and as soon as it finished MePo dumped me to desktop with no error messages. From the error logs it looks like Atmolight is upset about something..

Any help would be much appreciated. Thanks.

 

[kenwonders]

It looks like its having a problem after failing to connect:
[2016-07-30 21:45:09,709] [Error ] [37 ] [ERROR] - AtmoLight: HyperionHandler - Error while connecting
[2016-07-30 21:45:09,718] [Error ] [37 ] [ERROR] - AtmoLight: HyperionHandler - Exception: No connection could be made because the target machine actively refused it 192.168.1.247:19444

I think you need to open up the firewall or perhaps the ip/port is wrong? @Rick164 has a hyperion setup so he should be able to help further.

 

[Rick164]

@kenwonders Yeah it's the connection error like previously which I couldn't trace back to the root cause especially since I can't reproduce it here on reconnections / hard disconnects

@TheBatfink would make sure Hyperion is up2date and monitor Raspberry CPU usage as most likely something is crashing at that end or just dropping connections, maybe a fresh OpenElec or Rapbian (preferred nowadays) install could help as well to rule out any setup issues.
The new hyperion-project wiki has some better instructions as well and latest Hyperion release (V1.03.2) is recommended:

https://hyperion-project.org/wiki/2-Installation

Mediaportal crash I'm not 100% sure because AtmoLight will catch all known exceptions however we could try to reproduce that and see what triggers it exactly as crash to desktop I haven't seen before with it.

 

[TheBatfink]

Hi Rick. Yeah I though reinstall the rPi was the next step, but don't all those guides assume you first have the OS installed? Might need some more hand holding than that but will try find a Rapbian guide.

Now I remember having to configure something special with the USB (to speed it up) from your old guide.. is that no longer needed?

 

[TheBatfink]

Actually looks like they got me covered. Noobs ha, fitting.
Need to wait till I can get someone to help me get the tv off the wall but will give it a shot. Thanks

 

[gibman]

just installed 1.18.5.0.

Using a 240led setup arduino adalite sketch on ambibox 2.1.7.

Configged as mediaportal Direct.
The left hand side of the tv is not illuminated when I test within mp.
The 3 other sides are ok.

ambibox windows8 mode works ok..all leds light up .. but i miss black bars handling in mp.

It seems it maxes out at 200 leds.
Any ideas?

I have another tv setup with 140 leds which works ok. Same setup hw wise.

Gibman

 

[Rick164]

Hi Gibman,

Will check the code but afaik we don't have any hard led limit in AtmoLight, couple of things so we can pinpoint the problem:

- Did it work correctly with the previous AtmoLight version?
- What are your AtmoLight settings (screenshots preferably)
- Errors logs if any

 

[gibman]

It did not work in earlier version either.

ambiboxhandler.cs

ledCount = int.Parse(SendCommand("getcountleds", true).Split(separators)[1]);
if (ledCount <= 0)
{
return false;
}

so it queries the API for the led count.
I wonder what value we have here ?
sadly the code does not log this. could be useful to do.

if the value is lower than the expected 240 then I guess it could be a ambibox issue.
a hack could be to harcode the value to 240 and see how it goes.

Id be glad to try a custom build.

on a sidenote, it seems ambibox supports the use of profiles.
example I could create 1 profile per aspect ratio.
then I could have the viewmodeswitcher plugin or similar call/activate these profiles in ambibox.
The benefit would be to avoid the API calls which would just make the latency worse.
What I mean is; ambibox internal mode should be the fastest.
ofcourse I would then lose a lot of the features found within the atmolight plugin, like VU for music etc.

regards
Gibman

 

[Rick164]

Thanks for the pointer, this was made a by a now retired dev (Lightning303) so not familiar with AmbiBox handler that much but added some logging there so we can see what led count it reports back
Think some logging there could be useful in all cases so we might as well keep it in for debug log at least, we could also add view mode switching to the AtmoLight context menu (with profile selection) as the code is in there just not reporting back from core to plugin side atm.


// Update
New build attached so you can test both options:

V1 = extra logging for led count
V2 = same as V1 but ChangeProfile from AtmoLight context menu it should now show a profile list retrieved from AmbiBox allowing you to set a profile manually (untested)
Also made sure we hide ChangeProfile for unsupported handlers like AtmoOrb and Hyperion.

Commit log:

https://github.com/ambilight-4-mediaportal/AtmoLight/commit/15ce17f480d547a1ca765549bb32f1649cb12a7d