AtmoWin - improvement discussion (2 Viewers)

[pur_berger]

Nein - gar nicht - es gibt dieses Wunderbare Windows Reporting Tool mit dem man sich prüfen lassen kann wo es "Probleme" im Powermanagement gibt:

powercfg -energy - Eine Erkklärung gibt es z.B.hier

Und bei einer Maschine poppt eben auch Atmowin auf - ein paar postings weiter vorne ist der entsprechende Report.

 

[azzuro]

New testing version : 1.0.0.9

Correction of the gradient slider on color gradient dialog. (Azzuro)
Update platform project to VS120.
translate few internal source text.
set capturesize to 96x54 for 16x9 build
set max capture to 768. ( need testing !)
set max zoning to : 256 on TOP / 256 on Bottom / 128 Left & Right (Rick164)
Add com port baudrate on AmoduinoV2 ( Rick164)
Correct/align baudrate setting ( Rick164)

WARNING : using more than 256 LED reduce Atmowin performance.

 

[Kotik]

There is a bug in com port baud-rates for Atmoduino and Atmoduinov2 and i guess for all the rest devices as well, i just don't have them to test it out but someone can look it up. The baud-rate setting is always 1 step lower than the actual setting you set it to be, if for an example you set it to 460800 it will then default to the one below 460800 so your leds will not work.

As a result i always have to set it 1 step higher than the actual baud-rate of my sketch and then it will work.

Happens only in the new testing version : 1.0.0.9

 

[kenwonders]

Hi, I'm having a problem getting the gradients to work with my AtmoWin setup. To demonstrate the effect:
- set windows to a black background
- put AtmoWin in live view
- move it slowly towards the edge
it doesn't seem to matter what settings I try (colour adjustment, sensitivity, saturation etc) there is always a point where the lights immediately jump to white from black. If I adjust the edge weighting, it simply moves that point closer or further from the edge.
With AmbiBox, a slow movement of a white object towards the edge against the black background will result in a slow increase of brightness from black to white.

Because of this, it's very hard to eliminate flicker from the output to the lights, which is a shame, because AtmoLight + AtmoWin are a great setup otherwise for me, I especially like the colour calibration.

Am I doing something wrong? I'm sure when I last used AtmoWin ages ago it didn't do this, and certainly the effect I'm getting isn't represented by the nice gradients shown in the pop up 'gradients' configuration.

 

[Rick164]

@Kotik Thanks for reporting the bug, will check the 1.0.0.9 code for the baud rate index offset which should be a simple fix

@kenwonders does this happen with both 1.0.0.8 and 1.0.0.9?
We could try a my old AtmoWin fork which supports AtmoDuino V1 and up to 256 leds however that doesn't have the fancy xml config saving and win8 capture so for debugging only:

https://bitbucket.org/RickDB/atmowin-atmoduino-mod/downloads
https://bitbucket.org/RickDB/atmowin-atmoduino-mod/downloads/AtmoWin_09_07_2013_Atmoduino+SEDU.zip

Best to put it in another folder so that it doesn't mess up anything else

 

[Rick164]

Visually the COM port for AtmoDuino V1 / V2 stays at the correct one however I made the mistake of not starting at index 0 when reading it back (hench the off by 1) , new version attached and let me know how it goes

 

[kenwonders]

@Kotik Thanks for reporting the bug, will check the 1.0.0.9 code for the baud rate index offset which should be a simple fix

@kenwonders does this happen with both 1.0.0.8 and 1.0.0.9?
We could try a my old AtmoWin fork which supports AtmoDuino V1 and up to 256 leds however that doesn't have the fancy xml config saving and win8 capture so for debugging only:

https://bitbucket.org/RickDB/atmowin-atmoduino-mod/downloads
https://bitbucket.org/RickDB/atmowin-atmoduino-mod/downloads/AtmoWin_09_07_2013_Atmoduino+SEDU.zip

Best to put it in another folder so that it doesn't mess up anything else

Didn't have any affect on the issue sadly. I did notice (on both new and old AtmoWin) that there appears to be some graduation effect, but it seems to only trigger on colours (hue but not brightness perhaps?).

 

[Rick164]

Could you post a screenshot of the current AtmoWin settings (with the latest build)?
What might help is to tinker with the smoothing a bit, been a while since I used AtmoWin however believe it was set to something like:

Edge weighting: 1-12 <-- depends on how deep you want to scan
Filter length: 200ms
Fiter threshold: 74%
Filter smoothness: around 60%
Widescreen mode: off

Under color software adjustment would keep it default for testing at least to see if maybe something there is affecting it.

 

[kenwonders]

Not sure I understand? The filter functionality is time based, but what I'm talking about is positional, regardless of time.

I have tried altering all of the settings to account for change, and I'm pretty sure it's either a bug or 'works as designed'. If I set edge detection that low, it will be detecting elements halfway across the screen.[DOUBLEPOST=1465127882][/DOUBLEPOST]Here's my AtmoWinX.xml in case I'm doing something wrong.

 

[Rick164]

Ah right though it was also affecting the fading in / out, edge detection is correct that way as the lower value increases the level of image data measured from the side so if you set it to 12 for instance it will detect only near the screen border and not further in
Hyperion has it as well only there you have a bit more options for vertical / horizontal with spacing and is % based, where if you were to increase the depth there it will increase the block size from the below screenshot whereas with AtmoWin lower depth value = more data which is weird

With the older AtmoWin builds this worked at least so might be setup related or specific hardware / led count.