Releases: T-Troll/AlienFX-SDK
Releases · T-Troll/AlienFX-SDK
3.0.0 (FULL Alienware devices support)
- Code and naming cleared up, changes into API levels and naming
- Full support for external monitors
- More clear and simple example
- APIv8 (external keyboards) - numlock/capslock/scrollock secondary color support
- APIv6 (monitors) - bug fixes and effects support
- Bug fixes for other APIs.
2.1 (APIv9)
- Full APIv9 (Alienware external keyboards - AW410k/AW510k) support:
- Color change
- On/Off/Dimming
- Per-key effects
- Global effects
Known issues:
- APIv9 devices quite slow, full keyboard update requires about a second.
2.0 (New data structures for mapping and state changes)
Reflect new control concept and data structure changes for release 6 of AlienFX-Tools.
1.2.0
See full list of supported and tested devices here
Notes:
- There are 2 projects available: alienfx_sdk and alienfx_sdk_NOACPI. The difference between them is second one doesn't support ACPI-controlled lights (Aurora R6-R8), because this kind of control require 3 other projects from alienfx-tools (alienfan-tools/alienfan-low, alienfan-tools/hwacc, alienfan-tools/KDL), this is greatly increased overall footprint and complexity. So use NOACPI version for most cases.
- APIv6 (Monitors) and APIv8 (AW768 keyboard) is into alpha stage - devices will be detected, but not work. Unfortunately, i have none of these devices, and my volunteers still not finish testing.
1.0.0
- Global Hardware effects support for v5
- Power button support for v1-v4 (there is no power button at v5 device)
- Full effect support for v1-v3
- Bug fixes
It's final release for now, only bugfixes or new hardware (like mouse, keyboard, monitor, crazy desktop) can alter it. All notebooks supported 100%
0.9.0
Full APIv1 - v5 support:
- 9 bytes 8 bit/color, reportID 2 control (v1)
- 9 bytes 4 bit/color, reportID 2 control (v2)
- 12 bytes 8 bit/color, reportID 2 control (v3)
- 34 bytes 8 bit/color, reportID 0 control (v4)
- 64 bytes 8 bit/color, featureID 0xcc control (v5)
Known issues:
- hardware effects doesn't supported for v5
- power button control only supported for v4
0.5.0 - intermediate stable release.
- Full API v3 support - all modes and up to 9 colors per light now supported
- Device init/reinit rework and bugfix - you can scan device list and switch between it any time.
- Other minor bugfixes.
Known issues:
- Only one active device per time supported.
- For API v2/v1, only Pulse mode supported. I need more time for protocol RE for Morph and Power button support.
- For API v2 (and maybe v1) mass light operation, you should sort lights by ID and set up from low to high id (hardware limitation).
- Being honest, you need PWM gamma correction to fit screen colors, especially for v1 and v3 - otherwise some color drifting to white. Do it in you code for now.
0.2.0
- Full support for API v1 (9-byte data, 8 bit per color), API v2 (12-byte data, 4-bit per color), API v3 (34-byte data, 8 bit per color, up to 26 lights/9 colors per command).
- For API v1-v3, it support color and pulse mode set, for API v3 - also Morph and hardware power button control supported.
- Devices and lights name management supported (via registry)
- Multiply devices supported (scan, select, use), but you can control only 1 device per time.
Known issues: - For API v3, default colors not set (it require special processing, see commented part in SetPower).
- For API v3, advanced modes (Spectrum, Color Wave - it can mix up to 9 colors in hardware!) not supported.