AlienFX Pidgin + Winamp plugin

So has anyone contacted Ingrater? I would love this plugin for the m14x and im willing to help, but I cant seem to find a way to pm.

 

I do, but no reply.

 

I too would like to help in any way I can. I spent about 4 hours this morning trying to look for any options that we could possibly change that might be stopping our m14x lights from working with the alienfx Winamp plugin but I still couldn't get this plugin to work. I looked through practically every line of xml in the config, settings, and devices xml files and even tried replacing the .dll file for the plugin with the .dll from the led tester (since the led tester works perfectly) and nothing helped. Now, I'm not very knowledgeable when it comes to hardware addresses, but I was wondering why Ingrater used different device IDs in his blog post detailing how to use his plugin with later Alienware models:

Log file:
Old Alienfx Device
Model description: Area-51 m15x
Leds still on: power led
Led 0x1: touchpad
Led 0x20: light pipe
Led 0x80: alienware logo
Led 0x100: alienhead
Led 0x10000: touchbar

devices xml file:
[I can't seem to post xml and actually have it show up, so this is the post I'm talking about: http://3d.benjamin-thaut.de/?p=19. Near bottom of the page.]

How did Ingrater come up with the code "0x000001" for the led id "0x1"? (Yes I know he added leading 0s to make the total length of the address 6 characters but I don't understand why this was done) Nonetheless I tried out both types of led codes but neither of them worked.

In the settings file there's a model value="5"/ line. What does this mean? I know that model value 3 is used with an "old" Alienware model (which I found out by looking at the settings xml file of an older Alienware model). When I tried to set this value to "4" the plugin didn't recognize any devices at all.

I apologize in advance if all of this information ends up being unhelpful, but I've been trying really hard to get this plugin to work and I need some more experienced people to help me make sense of all of this information :X

 

ok so it'd be really cool if someone could send me a specific link to the actual plugin. Does it have an installer? Or what? maybe I'm just stupid but at the download site it gives me files and tells me to put them in C:/.../appdata/...winamp/ and I don't have that file.
What step did I miss? Someone help me out here. R3 M17x system btw. i have to change my signature to match that.

 

No, it does not have an installer. If you can't find that folder location it's because you haven't made hidden files and folders visible in Windows. Open explorer, go to "Organize" -> "Folder and search options" -> "View" tab -> "Show hidden files, folders, and drives"

 

no i have hidden files enabled and compatability files are enabled as well. on the install notes, it says:
copy the libgcc_s_dw2-1.dll to your root Winamp directory (typically C:\Program Files\Winamp
copy the vis_winamp-alienfx-plugin.dll to the Winamp\Plugins directory
copy the alienfx_vis_config.xml to your appdata\Winamp\Plugins directory (C:\Users\Your Username\appdata\Roaming\Winamp\Plugins for Vista and 7).

well, I do not have 'winamp' in my program files, nor in my roaming files. Where do you get winamp? Because i don't have it. My m17x is an R3 model. Thanks for the feedback. i just need a little more.

 

It sound like you dont even have Winamp installed, Go here: Link To Download Winamp. After you install it you will see those directory both in the program files and the AppData

 

OMG Thank you!!! I got it working, but I have to program it all now. Andddd...I'm not doing such a great job. At times it is mostly black. Any preset saved files I could have?

 

doubt it because nobody i know of has actually got the thing to work right.

 

You can edit the zone by go to Option > Preference > Plug-in > (under) Visualisation > (Select) Alienfx visualisation plugin > Configure. Then it will bring up the AlienFX Zone Editor where you can edit how the light response to the sound/beat of the music.

Although My M14x is not support so I have no idea which setting is good though.

 

i din't even read what kind of system you had. just skimmed through and just figured you had m14x. sorry lol

 

looking into adding support of the m14x into the file itself and got kinda stumped. figured out how to add it in some places but not in others.

void Zone::SetModel(SupportedModels pModel){
for(int i=0;i<32;i++)
_FreqBandUsage = NULL;

_Model = pModel;
_Leds.clear();
switch(_Model){
case AREA_51_M15X:
_Leds.resize(6);

_Leds[0]._Name = L"Touchpad";
_Leds[0]._LedBit = ALIENFX_A51_M15X_TOUCHPAD;
_Leds[0]._Used = false;

_Leds[1]._Name = L"Lightpipe";
_Leds[1]._LedBit = ALIENFX_A51_M15X_LIGHTPIPE;
_Leds[1]._Used = false;

_Leds[2]._Name = L"Alienware Logo";
_Leds[2]._LedBit = ALIENFX_A51_M15X_ALIENWARE_LOGO;
_Leds[2]._Used = false;

_Leds[3]._Name = L"Alienhead";
_Leds[3]._LedBit = ALIENFX_A51_M15X_ALIENHEAD;
_Leds[3]._Used = false;

_Leds[4]._Name = L"Keyboard";
_Leds[4]._LedBit = ALIENFX_A51_M15X_KEYBOARD;
_Leds[4]._Used = false;

_Leds[5]._Name = L"Touchpanel";
_Leds[5]._LedBit = ALIENFX_A51_M15X_TOUCH_PANEL;
_Leds[5]._Used = false;
break;
case ALL_POWERFULL_M17X:
_Leds.resize(10);

_Leds[0]._Name = L"Keyboard right";
_Leds[0]._LedBit = ALIENFX_AP_M17X_KEYBOARD_RIGHT;
_Leds[0]._Used = false;

_Leds[1]._Name = L"Keyboard middle right";
_Leds[1]._LedBit = ALIENFX_AP_M17X_KEYBOARD_MIDDLE_RIGHT;
_Leds[1]._Used = false;

_Leds[2]._Name = L"Keyboard middle left";
_Leds[2]._LedBit = ALIENFX_AP_M17X_KEYBOARD_MIDDLE_LEFT;
_Leds[2]._Used = false;

_Leds[3]._Name = L"Keyboard left";
_Leds[3]._LedBit = ALIENFX_AP_M17X_KEYBOARD_LEFT;
_Leds[3]._Used = false;

_Leds[4]._Name = L"right speaker";
_Leds[4]._LedBit = ALIENFX_AP_M17X_RIGHT_SPEAKER;
_Leds[4]._Used = false;

_Leds[5]._Name = L"left speaker";
_Leds[5]._LedBit = ALIENFX_AP_M17X_LEFT_SPEAKER;
_Leds[5]._Used = false;

_Leds[6]._Name = L"alienhead";
_Leds[6]._LedBit = ALIENFX_AP_M17X_ALIENHEAD;
_Leds[6]._Used = false;

_Leds[7]._Name = L"alienware logo";
_Leds[7]._LedBit = ALIENFX_AP_M17X_ALIENWARE_LOGO;
_Leds[7]._Used = false;

_Leds[8]._Name = L"touchpanel";
_Leds[8]._LedBit = ALIENFX_AP_M17X_TOUCHPANEL;
_Leds[8]._Used = false;

_Leds[9]._Name = L"touchpad";
_Leds[9]._LedBit = ALIENFX_AP_M17X_TOUCHPAD;
_Leds[9]._Used = false;
break;
case ALL_POWERFULL_M15X:
_Leds.resize(10);

_Leds[0]._Name = L"Keyboard right";
_Leds[0]._LedBit = ALIENFX_AP_M15X_KEYBOARD_RIGHT;
_Leds[0]._Used = false;

_Leds[1]._Name = L"Keyboard middle right";
_Leds[1]._LedBit = ALIENFX_AP_M15X_KEYBOARD_MIDDLE_RIGHT;
_Leds[1]._Used = false;

_Leds[2]._Name = L"Keyboard middle left";
_Leds[2]._LedBit = ALIENFX_AP_M15X_KEYBOARD_MIDDLE_LEFT;
_Leds[2]._Used = false;

_Leds[3]._Name = L"Keyboard left";
_Leds[3]._LedBit = ALIENFX_AP_M15X_KEYBOARD_LEFT;
_Leds[3]._Used = false;

_Leds[4]._Name = L"right speaker";
_Leds[4]._LedBit = ALIENFX_AP_M15X_RIGHT_SPEAKER;
_Leds[4]._Used = false;

_Leds[5]._Name = L"left speaker";
_Leds[5]._LedBit = ALIENFX_AP_M15X_LEFT_SPEAKER;
_Leds[5]._Used = false;

_Leds[6]._Name = L"alienhead";
_Leds[6]._LedBit = ALIENFX_AP_M15X_ALIENHEAD;
_Leds[6]._Used = false;

_Leds[7]._Name = L"alienware logo";
_Leds[7]._LedBit = ALIENFX_AP_M15X_ALIENWARE_LOGO;
_Leds[7]._Used = false;

_Leds[8]._Name = L"touchpanel";
_Leds[8]._LedBit = ALIENFX_AP_M15X_TOUCHPANEL;
_Leds[8]._Used = false;

_Leds[9]._Name = L"touchpad";
_Leds[9]._LedBit = ALIENFX_AP_M15X_TOUCHPAD;
_Leds[9]._Used = false;
break;
case ALL_POWERFULL_M11X:
_Leds.resize(5);

_Leds[0]._Name = L"keyboard";
_Leds[0]._LedBit = ALIENFX_AP_M11X_KEYBOARD;
_Leds[0]._Used = false;

_Leds[1]._Name = L"right speaker";
_Leds[1]._LedBit = ALIENFX_AP_M11X_RIGHT_SPEAKER;
_Leds[1]._Used = false;

_Leds[2]._Name = L"left speaker";
_Leds[2]._LedBit = ALIENFX_AP_M11X_LEFT_SPEAKER;
_Leds[2]._Used = false;

_Leds[3]._Name = L"alienware logo";
_Leds[3]._LedBit = ALIENFX_AP_M11X_ALIENWARE_LOGO;
_Leds[3]._Used = false;

_Leds[4]._Name = L"touchpanel";
_Leds[4]._LedBit = ALIENFX_AP_M11X_TOUCHPANEL;
_Leds[4]._Used = false;
break;
case M17X_R3:
_Leds.resize(9);

_Leds[0]._Name = L"Keyboard right";
_Leds[0]._LedBit = ALIENFX_M17X_R3_KEYBOARD_RIGHT;
_Leds[0]._Used = false;

_Leds[1]._Name = L"Keyboard middle right";
_Leds[1]._LedBit = ALIENFX_M17X_R3_KEYBOARD_MIDDLE_RIGHT;
_Leds[1]._Used = false;

_Leds[2]._Name = L"Keyboard middle left";
_Leds[2]._LedBit = ALIENFX_M17X_R3_KEYBOARD_MIDDLE_LEFT;
_Leds[2]._Used = false;

_Leds[3]._Name = L"Keyboard left";
_Leds[3]._LedBit = ALIENFX_M17X_R3_KEYBOARD_LEFT;
_Leds[3]._Used = false;

_Leds[4]._Name = L"right speaker";
_Leds[4]._LedBit = ALIENFX_M17X_R3_LEFT_SPEAKER;
_Leds[4]._Used = false;

_Leds[5]._Name = L"left speaker";
_Leds[5]._LedBit = ALIENFX_M17X_R3_RIGHT_SPEAKER;
_Leds[5]._Used = false;

_Leds[6]._Name = L"alienware logo";
_Leds[6]._LedBit = ALIENFX_M17X_R3_ALIENWARE_LOGO;
_Leds[6]._Used = false;

_Leds[7]._Name = L"touchpanel";
_Leds[7]._LedBit = ALIENFX_M17X_R3_TOUCHPANEL;
_Leds[7]._Used = false;

_Leds[8]._Name = L"touchpad";
_Leds[8]._LedBit = ALIENFX_M17X_R3_TOUCHPAD;
_Leds[8]._Used = false;
break;
}
}




not totally sure what to add where it says _Leds.resize(6);
its different on every model and not sure where he got that from unless you put one more number for how many leds you have. guess thats worth a try

 

jimbo, what file did you get that information from? It looks like it could be useful...

 

I'm not sure if anyone has answered this but has anyone been able to get this to work on the m18x?

 

its a file included in the source files from ingraters website. i think ive put everything in that i need to now i just need to compile all of the files together and see what happens

 

having trouble building. giving me 8 errors.

Error 1 error C1083: Cannot open include file: 'boost/function.hpp': No such file or directory c:\users\johnny\desktop\winamp-alienfx-plugin\callback.h 3 1 winamp-alienfx-plugin
Error 2 error C1083: Cannot open include file: 'boost/scoped_array.hpp': No such file or directory c:\users\johnny\desktop\winamp-alienfx-plugin\xmlconfig.cpp 7 1 winamp-alienfx-plugin
Error 3 error C1083: Cannot open include file: 'boost/function.hpp': No such file or directory c:\users\johnny\desktop\winamp-alienfx-plugin\slider.h 4 1 winamp-alienfx-plugin
Error 4 error C1083: Cannot open include file: 'boost/scoped_ptr.hpp': No such file or directory c:\users\johnny\desktop\winamp-alienfx-plugin\main.cpp 19 1 winamp-alienfx-plugin
Error 5 error C1083: Cannot open include file: 'boost/function.hpp': No such file or directory c:\users\johnny\desktop\winamp-alienfx-plugin\callback.h 3 1 winamp-alienfx-plugin
Error 6 error C1083: Cannot open include file: 'boost/function.hpp': No such file or directory c:\users\johnny\desktop\winamp-alienfx-plugin\config.h 4 1 winamp-alienfx-plugin
Error 7 error C1083: Cannot open include file: 'boost/function.hpp': No such file or directory c:\users\johnny\desktop\winamp-alienfx-plugin\button.h 4 1 winamp-alienfx-plugin
Error 8 error C1083: Cannot open include file: 'hidclass.h': No such file or directory c:\users\johnny\desktop\winamp-alienfx-plugin\alienfx.cpp 9 1 winamp-alienfx-plugin

these files here are not files included in ingraters source files. do i need to take out the lines that say #include boost/function.hpp through all of the errors or did he exclude some of the files necessary to complete this? anybody know anything?

 

This isn't really a crash, just something acting a bit odd, it seems that whenever
I set up everything it only works about half way so to speak.

I am using an "m11x R1",

running Windows 7 64bit Home Premium,

It is not really a crash, but set up alienfx_vis_devices.xml and issue appeared

Again it is not really a crash, but can only get LEDs working when using PIDs
"0x8161" and "0x8162" but unable to configure all LEDs properly. Change PIDs to
something else and can configure all LED's but receive no response from them.

I know this is an odd issue, and one that I cannot figure out.
I have attached the alienfx_vis_devices.xml

I am using the default config.xml and have used the configuration utility to set
up the various LED assignments. I guess what I am trying to say here is, I am
getting a generic LED list from the configuration screen and unable to assign all
of my LED's properly, or unable to get them to do anything when I am able to see
all of them listed. I have tried setting Protocol Version to both 1 and 2 (not at
the same time of course). After finding this plugin around the beginning of this
year I have been checking very so often to see the m11x supported, and quite
honestly I am extremely happy that it is working at least to some degree. I would
love to see it fully working correctly with my laptop so that I can configure all
of the LEDs properly. I wouldn't mind attempting to tweak the source code, but I
honestly don't recognize the program language and I am afraid of messing it up
because I don't know it. Though I have no issues with attempting to learn it so
that I can try to help out from home since I don't have a stable internet
connection for a remote session.

If for any reason my post is confusing please feel free to tell me and I will try
to clarify as soon as possible, or whenever my internet connection is working well
enough to post.

(I decided to attach all 3 configuration xml's just in case)

***Edit***
Ok, I need to correct my myself a bit..
I was looking through the source code and found why it seemed like I was not able
to configure all of the LEDs. To be specific, I read through "Zone.cpp" and found
the m11x section where it defines the configurable zones. This is where I noticed
that the line "_Leds.resize" was set to 5, yet there should be 7 LEDs that can be
configured. After checking all the dependencies listed in this file I checked
each one until I found "alienfx.h" listed the hex addresses for all of the LEDs.
This is where I found that the m11x power LEDs are listed, complete with their
hex address.

So my conclusion is simple, since the plugin is setup to properly detect my laptop
it works great, as long as I don't have an "alienfx_vis_devices.xml" file created.
Correct me if I am wrong, or missing something, but wouldn't it be possible to add
the approximately 6-7 lines of code to Zone.cpp, change "_Leds.resize(5)" so that
it reads "_Leds.resize(7)" instead, and recomplie the plugin to allow the power
button to be configured within Winamp? I ask because I do not fully understand the
C++ programming language myself and do not know if it would be that simple of a fix.
I look forward to feedback about it, hopefully someone can tell me if I am correct
or not. I would attempt to compile it with the change to test (still have a couple
years on my full coverage/accidental damage warranty), I just do not know what I
would need to even begin.

Sorry for the sort of long winded post, and again, let me know if I need to clarify
anything.

 

I got the device ID for m18x
"0x518"

Results log.
New Alienfx Device
Model description: m18x
Led 0x1: numpad
Led 0x2: keyboard right
Led 0x4: keyboard middle
Led 0x8: keyboard left
Led 0x10: macro keys
Led 0x20: chassis left
Led 0x40: chassis right
Led 0x100: alienware logo
Led 0x200: touchpad
Led 0x800: media keys

Can't find led code for the power button. But I know it has one because color can be changed thru themes editor. I followed the readme and both blog entries. When I press start in winamp nothing happens. Latest version winamp, alienware command center.

dsaem we may need dev support, hope he still follows this thread.

 

I'll try to find the dev. Maybe he has a blog somewhere. I'll post back if I find anything.

 

Ingrater’s 3D Blog Alienfx winamp plugin update

no way to contact him, other than these forums

 

Small status update:

I'm currently swamped with real life stuff, but I'll try to find some time to make the plugin work with newer alienware laptops.

If you want to compile the plugin yourself you will need boost: Boost C++ Libraries

 

Thanks Ingrater. When you get this working on the m18x where can I donate for your awesome work?

 

got the boost libraries and got them in right place but now i have 150 more errors and 6 warnings. after i got boost in place it wanted hidclass.h, hidpi.h, hidsdi.h, and hidusage.h downloaded those from koders.com. wonder if i got wrong files. i dunno. probably about 30 or so errors have to do with main.cpp and are something to do with intellisense. got several with alienfx.cpp dealing wigh hidd_attributes and the rest are dealling with hid files with mostly syntax errors. not making any head way

 

What's this even mean lol. I had to post that out of confusion lol.

 

its just some errors im getting in microsoft visual studio while im trying to add the m14x to the source files of the winamp alienfx plugin.

 

If possible I can work with you to configure the AlienFX on the M14x laptop next month, because after next month it will be my 3 month summer holiday in NZ. Just let me know when you're free. However I have a very very little knowledge to those C++ or Java or whatever programming languages available, but i do know some V Basic stuff (man I should have focus more in those boring programming classes >.< lol)

 

You will also need the Windows Platform SDK and eventually also the Windows Driver SDK

 

think ill just wait till someone that knows what they are doing does this. i suppose i need change the directory for the sdk files to where it installed the windows platform sdk in microsoft visual studio but couldn't figure out how to change it. went through all the options but didnt see what i needed to change.

 

Some bad news: Due to a file system error I lost all my progress on the plugin I made since the beginning of 2011. This is going to delay the version that supports the latest laptops quite a bit.

I learned from it and started a public git repository for everyone who wants to monitor the progress or help with developement.

https://github.com/Ingrater/Winamp-AlienFX-Plugin

Kind Regards Ingrater

 

ohhh Fish
Do we have any other development on AlienFx for M14X?

Guys I would also like to know if any of you can provide with Themes for M14x.

 

this is won't mess my alienfx, right? i'm new to all of these

 

No, it wont, unless you doing it wrong. But I dont think it would either because it is actually not use the command centre that much though, however there're some issue like after using it, the light will stay at whatever the last light is flashing, or it will turn itself off and sometime it will restart sometime it doesnt. The fix to that is to restart the AlienFX.

 

thanks, and oh, btw, does this work with my M17X-R3 version? thanks, i'm realy excited if that so!

 

I had reports that the m17X-R3 is working.

 

HELP!!
When I select"alienware visualization pligin..."to start,it shows that"Alienware Device not found. Plugin not active"
What should I do?

 

What type of Alienware you have? Because it only work with the older M11x, M17x and the M15x. If you have the newer M11x, M14x, and M18x, it will display that error you have there.

 

The type of my alienware is MX17 R3.

 

It's m17x r3

 

btw, i dont have to do this, i can do this with WIndows media player by select alienfx visual effect, and the show begun? but it's not good as people doin with Winamp player,.. only change colors.. but not that good as the Winamp one.. :S

 

Please read the very first post of this thread for instructions how to setup not (yet) supported alienfx laptops.

 

Ingrater sent me a file last night to try for the plugin and its made my m14x light up like a christmas tree oto the music on winamp. thanks ingrater for the time and the added support. don't know if he means for it to be the official release but now everone knows that it does work and you should be able to download your update soon.

 

Same here. For m18x

The good - debug dll works with dual nvidia 580's
The bad - debug dll does NOT work with dual AMD 6990m's
The ugly - Stock Dell video driver and winamp crash with AMD 6990m's (Screen super DIM after crash)

I'll share my config with everyone as soon as Ingrater gives the ok. (At this time only works with ndivia)

I still have a system with dual 6990m's that has to go back to Dell. I'll try different drivers and settings to see if I can get it working b4 I return it.

 

Additional info for Ingrater

m18xR1
AMD 6990m's - Current version doesn't crash stock Dell video driver or winamp. Doesn't work, no error given.
nVidia 580's - Current version doesn't crash video driver or winamp. Doesn't work, no error given. (Debug works )

System info

PHP:

<device name="m18xR1" protocolVersion="2" productid='0x518'>

alienfx-leds-tester:
works on both AMD and nVidia
results log:

PHP:

New Alienfx Device
Model description: m18xR1
Led 0x1: numpad
Led 0x2: keyboard right
Led 0x4: keyboard middle
Led 0x8: keyboard left
Led 0x10: macro keys
Led 0x20: chassis left
Led 0x40: chassis right
Led 0x100: alienware logo
Led 0x200: touchpad
Led 0x800: media keys

Fails to find alienhead power button led ID

 

Update:

AMD 6990m users:
Catalyst 12.1 preview drivers work with AlienFX Pidgin debug version. Fixes brightness controls too!!

@ Ingrater - There was some error about zones not matching. I should have written it down. When the error dialog came up I just pressed "ok". After the error you can configure zones and it works.

@ everyone else - AlienFX Pidigin works way better then windows media plugin. More responsive, more configurable, more colors. I was honored to beta test. Hope I have given Ingrater enough info to release for m18x soon.

 

I second this, everything's great. The only thing I could ask for would be a version without the debug window, since it isn't necessary when everything's working.

I also noticed last night that it seems like the left and right vents on the front have been referred to as speakers for the longest time... I mean, they aren't vents either but they're closer to vents than speakers!

 

I released a new version. Download link is still the same. The new alienware laptops should now work using the devices xml. If you get your laptop to work please be so kind and post your devices.xml file.

Once we have a working set of devices.xml files I'm going to include them into the release so new users don't have to create their own devices.xml.

I unfortunately don't have a paypal account you can donate to, but maybe you manage to get enough people together to get me Skyrim on Steam ;-)

@Nuroo
The error messages appears if you try to use the zone settings on a different alienfx device. It only appeared because I changed the numbering scheme of the devices. Won't happen in the future again.

 

Today I tried again with the new version that Ingrater has update and manage to get it partially working with only the Status light, the ALIENWARE Logo, the L&R Grill, and the T-Pad. However the keyboard now working for some unknown reason. Can anyone who has a working device.xml, post one here please?

 

Thank you again Ingrater. +rep

New version AlienFX Pidgin + Winamp plugin works great on m18x.

Follow original instructions on install, except use newest versions of files.

m18xR1 owners:
I'll save you a few steps, use my alienfx_vis_devices.xml

PHP:

<?xml version="1.0" encoding="UTF-8"?>
<devices>
  <device name="m18xR1" protocolVersion="2" productid='0x518'>
    <led name="numpad"                            code="0x000001" />
    <led name="keyboard right"                    code="0x000002" />
    <led name="keyboard middle"                   code="0x000004" />
    <led name="keyboard left"                     code="0x000008" />
    <led name="macro keys"                        code="0x000010" />
    <led name="chassis left"                      code="0x000020" />
    <led name="chassis right"                     code="0x000040" />
    <led name="alienware logo"                    code="0x000100" />
    <led name="touchpad"                          code="0x000200" />
    <led name="mediakeys"                         code="0x000800" />
  </device>
</devices>

You'll still have to set up zones according to your music tastes. Use plugin config in winamp for that.
For R&B use mine:


Enjoy !

 

Thanks Ingrater! Really appreciate your work man.

 

Okay here's a weird problem. When I'm in the settings and I have the frequency analysis open, it looks great. As soon as I close that beat detection window, all the lights stay on and in no case will they turn off (eg. between beats)