Color Editor 2.1.1 BETA Released

[martin.deimos]

For all guys who are beta-testing Winamp 5.5 (http://forums.winamp.com/showthread.php?threadid=277166),
you will once again need a new color editor!

Download Color Editor 2.1.1

During testing the updated color editor, i had some bugs when you keep the old studio.xnf. So if anyone has the same bug - delete studio.xnf!

If there are any Vista users, can you test creating new themes, copy themes. I get crashes when i apply the new theme name. Win Xp works ok.

If it works for you, enjoy Winamp 5.5 and stay tuned for new betas

Submit your Color Themes for the new Winamp Bento skin here:
http://forums.winamp.com/showthread.php?threadid=276371

[pjn123]

Yes. I get crashes too. Win Vista.

Clone >>> New name >>> CRASH

PLEASE PLEASE PLEASE sort this out asap. Realy need the color editor.

[martin.deimos]

Thx - i feared i am the only who get this.
pieter - do you get this crash only w/ coloreditor or also on editboxes w/ azenis?

[pjn123]

Just the color editor...

[RandomCarpet]

Just found another bug (kinda): If you switch to a theme by selecting it in the theme list and pressing ENTER and if you happen to press ENTER again after that -> winamp.exe crashes.

This seems to be an old problem, managed to reproduce it with aa clean Winamp 5.35 + Color Editor 2.1.0 installation too. It would be great if it is possible to fix this.

[martin.deimos]

will forweard this to benski, thx

[VooDoo`]

Hi,

Winamp chrases if i do the following:

double click a theme where windowbackground's and windowgradient's saturate channel is on.

then deselect the saturate channel at windowbackground and then at windowgradient and winamp will crash.

try it with the xp_blue 2 theme I made.

[r.e.e.d]

another crash...

color editor:

delete custom >crash

using winXP

[r.e.e.d]

Bento Skin related:

Color Editor is loosing custom Bento colors when winamp is restarted.. > is not saving..

[Jimekus]

Reposted from Winamp 5.5.1568 discussion where it wasn't noticed. I've started to work with the Color Editor ,,, and, not-withstanding the numerous execution errors on WinXP, I've encountered a lapse in design in 2.1.1. This probably has to do with the XML structure of the RGB colors that adds 4096 to the 0-255 structure. What I want that I haven't been able to find in any other skin is the ability to set a color code to allow the Frame Buffer to shine through on all the backgrounds. This color code is RGB(31,0,15). It can't be faded or altered in any way if Windows is to ignore painting anything in this area and thus allow the AVS visualizer to display (paintng) the desktop into the foreground of all controls, as it were. I need this because when Winamp is minimized with a slow AVS then the CPU usage is very low. This is important if I am to get multiple instances beat-mixing on a relatively low powered Via CarPC. Maybe someone can tell me of a Modern Skin that has all its background colors set to 31,0,15. Thanks, because it just looks so good.

[RandomCarpet]

Just found another sequence of actions that crashes winamp.exe (Winamp 5.5 Build 1600 + Color Editor 2.1.1 BETA, not sure for older versions):

1. Open Color Editor.
2. Click New Theme or Clone Theme.
3. Close the dialog that asks you for a theme name not by clicking Cancel, but by clicking the Close Window (X) (standart frame button, usually in the upper right corner).
4. Click New Theme or Clone Theme again to open the corresponding dialog.
5. Fill in some theme name and confirm with Ok or close the dialog with Cancel.
6. The crash occurs.

Strangely enough it seems that in skins that don't skin the standart frame, steps 2 and 3 must be completed at least twice before going to 4 and 5 for the crash to occur.

[Mecha25]

Dude, this thing is crap on my vista. It installs, the menu item appears, but it won't select no matter what happens. Not only that, but now my Album Art window shows magenta when there is no album art loaded, I can't change skins, and uninstalling it fixes none of these issues, I.E. my winamp is now permanently broken, pending a reinstall.

No offense intended, but take the color editor offline till you can work out these bugs, I don't want anybody else's winamp screwed over.

[akahige]

I've searched the forums high and low for some info on how the Color Editor is supposed to work, and have struck out on all accounts. Since there seem to be a lot of complaints about bugginess (which are matched by people saying "I dunno... it works for me..." I thought I'd post my problems here and see if anyone could point out the obviousness of what I'm doing wrong. (Nothing in the FAQ seems to cover this.)

I'm trying to build a Bento color theme based on Nucleo's NLog skin. I clone a color scheme (so I can edit it), open NLog in a graphics viewer and fire up a color picker so I can pull out the RGB values. And this is where things go all pear-shaped.

The RGB preview renders the correct color, but when I plug the same values into the settings sliders, the colors are nowhere near what they should be. This post had some suggestions about how to convert standard RGB 0-255 values to -4096-4096 values, but it didn't work for me.

On first look, the Color Editor seemed pretty straightforward and obvious, but I can't make it work. Is this thing horribly broken or is it just me...?

[DamageIncM]

Hello,

I have a problem with the Color Editor:

When I do anything, creating a new theme, clone an existing theme and edit it, whatever and then save it,
it will stay put for as long Winamp is running, but when I start Winamp the next time the colors will be gone and not saved either.

Could anyone find a fix for this problem please?

I have the latest Winamp, latest Color Editor (from this thread), Windows XP Professional SP2 (Build 2600), barely any plugins installed and none used for as far as I know... ask for any additional details needed.


ThanX
- Damage Inc.

[trollbabe2000]

Same problem here that others are having, just slightly different version of the details. I downloaded the Editor and installed it successfully and was able to pull up the Editor without anything crashing.... I avoided doing the things others have already said cause problems, such as closing out of the "New Skin" or "Clone Skin" dialog with the upper x rather than the cancel function... then tried to create a basic skin just as a test.

Selected "Royal Black" from the options, then opened the Color Editor and chose "New Skin." Named it "Basic Shock Pink" which showed up in the list of available skins on the left side of the Editor. Adjusted the display text to hot pink, made no other changes, and saved the skin.

Closed winamp and reopened it. It had defaulted to Royal Black, and "Basic Shock Pink" was nowhere to be found. Tried three times but no dice. Just won't recognize new color themes. No crashing, but no saving either.

One other note was that while installing the Editor, Vista threw up its "this software may not have installed correctly" messages, which if you've seen one, you know precisely how useless that information is. Reinstalled the Editor a couple of times but made no difference. Got the same warning message each time. My experience with Vista tells me this likely means Vista just doesn't like whatever you tried to install, particularly if the item is more XP-friendly (as some have commented here).

Good luck getting the Editor Vista-compatible. Meanwhile I have yet another reason to wipe my drive and install XP! Though if XP users are also having problems saving new themes, I suppose I can hope my issue isn't necessarily OS-related....

Thanx,

trollbabe2000

[DamageIncM]

Well, if it's a problem between XP and Vista.
I suggest they make a Winamp just for Vista, or else a version of the Color Editor just for Vista and XP separate.

I think they should rebuild the Color Editor (almost) from scratch again anyways.
Because it's not even being displayed right for as far as I know, unless it's Bento's fault which is all I used it with.
And then I find the Color Editor also not so handy to work with.
Like I can't find the colors I need easily, sometimes the Editor falls behind the skin and I have to close and open the Editor again, etc.

[RandomCarpet]

Originally posted by DamageIncM
I think they should rebuild the Color Editor (almost) from scratch again anyways.
Because it's not even being displayed right for as far as I know, unless it's Bento's fault which is all I used it with.
And then I find the Color Editor also not so handy to work with.
Like I can't find the colors I need easily...

I don't think this will happen, but... skinners have the freedom to change the way the user interacts with Color Editor within their skin (they can create a completely different interface for Color Editor). Take a look at the attachment, this is what Color Editor looks like in Sakura, a skin currently in the making. It would be good though, if at least some of the bugs are fixed (especially those vista related). About the "closing out of the "New Skin" or "Clone Skin" dialog with the upper x" bug, mentioned some posts back, I found a solution for this, but it's skin related, I mean it solves the problem only for the skin it's implemented in.

...sometimes the Editor falls behind the skin and I have to close and open the Editor again, etc.

I suppose this happens because of the way Bento works with component windows (it is a SUI skin, but Color Editor opens up in a seperate window), I could be wrong though.

[DamageIncM]

Originally posted by RandomCarpet
I don't think this will happen, but... skinners have the freedom to change the way the user interacts with Color Editor within their skin (they can create a completely different interface for Color Editor). Take a look at the attachment, this is what Color Editor looks like in Sakura, a skin currently in the making. It would be good though, if at least some of the bugs are fixed (especially those vista related). About the "closing out of the "New Skin" or "Clone Skin" dialog with the upper x" bug, mentioned some posts back, I found a solution for this, but it's skin related, I mean it solves the problem only for the skin it's implemented in.



I suppose this happens because of the way Bento works with component windows (it is a SUI skin, but Color Editor opens up in a seperate window), I could be wrong though.

I like how it looks in the screenshot.
That's kinda what I mean actually, a more straight forward editor.
So that it's just improved as more user-friendly, quicker (both technically and to work with), things like that.

Just like I personally don't completely get how to get a certain color.
You have to keep messing around with the 3 color-bars you get and the color source thing doesn't seem to matter.
Unless it's Bento's fault again, which I don't know.

Of course I like it if you have a lot of variety and detail, but it shouldn't be too hard or complicated to get just one color.

[MosIncredible]

Originally posted by DamageIncM
Hello,

I have a problem with the Color Editor:

When I do anything, creating a new theme, clone an existing theme and edit it, whatever and then save it,
it will stay put for as long Winamp is running, but when I start Winamp the next time the colors will be gone and not saved either.

Could anyone find a fix for this problem please?

I have the latest Winamp, latest Color Editor (from this thread), Windows XP Professional SP2 (Build 2600), barely any plugins installed and none used for as far as I know... ask for any additional details needed.


ThanX
- Damage Inc.

Exact same problem for me. Clicked save theme and all.

[MosIncredible]

edit to my post above:

When I export my color edit and place it in the C:\Program Files\Winamp\Plugins\ColorThemes\Big Bento folder, it works fine. If I want to edit it again, I have to clone it & export again because its locked when I do it that way but I found my work around.

[DamageIncM]

Originally posted by MosIncredible
edit to my post above:

When I export my color edit and place it in the C:\Program Files\Winamp\Plugins\ColorThemes\Big Bento folder, it works fine. If I want to edit it again, I have to clone it & export again because its locked when I do it that way but I found my work around.

But you can't save it to a new/different name that way?

[MosIncredible]

Originally posted by DamageIncM
But you can't save it to a new/different name that way?

Think I understand what you're saying like if I created a MonoDark theme (my favorite in the Modern Skin) and I wanted to edit it, I'll clone it, but have to change the name to something like MonoDark2. After I have the new one, delete the old xml file, clone the new file (MonoDark2), and rename it back to MonoDark.

[r.e.e.d]

To martin.deimos

I've just have discovered the reason to not saving..it is... but in wrong place

The color editor is saving the custom theme at "C:\Documents and Settings\(user)\aplication data\Winamp\Plugins\Freeform\wacs\coloreditor\data"...

...and reading from "c:\program files\Winamp\Plugins\Freeform\wacs\coloreditor\data"


Btw: Bento Color Pack uninstaller is removing the color editor uninstaller instead his own...

[DamageIncM]

Originally posted by r.e.e.d
To martin.deimos

I've just have discovered the reason to not saving..it is... but in wrong place

The color editor is saving the custom theme at "C:\Documents and Settings\(user)\aplication data\Winamp\Plugins\Freeform\wacs\coloreditor\data"...

...and reading from "c:\program files\Winamp\Plugins\Freeform\wacs\coloreditor\data"


Btw: Bento Color Pack uninstaller is removing the color editor uninstaller instead his own...

You're right, when I follow the first directory you mentioned, where it saves the custom colors to, and I open the only XML-file that is in there, it shows a small blue line (of the code I guess) with the name I made up for my custom color-theme.

So how do we fix this, by moving the XML-file(s) to the program's directory, as in the second directory you mentioned?
Or can I change the "save-directory" in Winamp or something like that?

[r.e.e.d]

it recomended wait for the next build..

but..

before (re)start winamp, - after save the custom theme, of course - go to first directory that i've mentioned and copy the xml file to the second one...

depending on the skin that you´re editing, the files are:

bento.xml
big bento.xml
or
winamp modern.xml

[Daybreak]

Looking forward to the next build..

[figure_me_out]

Guys, I got this problem and it's really starting to drive me nuts..

How on earth do I start the Color Editor?
- Windows XP
- Winamp 5.531
- Color Editor 2.1.1

I downloaded and installed Color Editor 2.1.1 and then I restarted Winamp. I looked in the plugins preferenses but found no plugin called Color Editor. Then I checked "C:\Program Files\Winamp\Plugins\freeform" to see if there was an executable, but found nothing. Then I tried to look for some sort of readme.txt for instructions, but there's no readme with the instructions on usage provided with this installer either. Then I looked on the Winamp Forums.. still no luck. I looked in my WinXP Start menu, but nothing new was added. Finally I looked in every context menu I could find in Winamp to see if there was an extra option called "Color Editor", but found nothing.

I'm really stuck here. Could someone please tell me how to open the Color Editor? Thanks!

[RandomCarpet]

Since Winamp 5.53, Color Editor 2.1.1 is not supported anymore.
You need Color Editor 2.1.2

[DamageIncM]

Well, to just open it.
Just click right anywhere on the colored frame of Winamp.
Then you get the menu you know,
with all the settings and windows/modules you can open/close.
Then there is also 'Color Editor' which simply opens it.

Hm, I didn't think of the version.
I think the older one indeed doesn't show up with a newer Winamp.

[RandomCarpet]

Yes, it should be either that or figure_me_out could be trying to use Color Editor with a classic skin. In that case it won't show up in the menu.

[figure_me_out]

Thanks, that fixed it. I just updated to Color Editor 2.1.2 and the option appears in the right-click menu now ^^

[akinap]

setuping is caused to pc problem.

[nathan909]

Looking forward to the next build....

[RandomCarpet]

If you had read only a few posts back, you woud have noticed that 2.1.2 is available... here