New skins for Bazille... 3 different colorways based on the Gearporn skins...

[sqigls]

GREAT ARTSTS STEAL...

Well, I'm not a great artist, but the Gearporn Bazille skins have been peeled again!
Ones & Zeros provides 3 new colorways to dress up your savage bacteria.
I hope you find some inspiration from them.

A big thank you to cbas for the uploads I've plagiarised, and to U-he for the amazing beast that is Bazille.
Also to anyone posting something constructive here, you're awesome thanks heaps!
Some resources posted below for anyone interested in making skins for U-He synths. cheers



BLUE
https://ufile.io/v8air

GP-OZ-GUI-Blue.jpg

GREEN
https://ufile.io/9uk27

GP-OZ-GUI-Green.jpg

ORANGE
https://ufile.io/gaku2

GP-OZ-GUI-Orange.jpg

Hexadecimal color code for transparency

All hex value from 100% to 0% alpha:

100% — FF
99% — FC
98% — FA
97% — F7
96% — F5
95% — F2
94% — F0
93% — ED
92% — EB
91% — E8
90% — E6
89% — E3
88% — E0
87% — DE
86% — DB
85% — D9
84% — D6
83% — D4
82% — D1
81% — CF
80% — CC
79% — C9
78% — C7
77% — C4
76% — C2
75% — BF
74% — BD
73% — BA
72% — B8
71% — B5
70% — B3
69% — B0
68% — AD
67% — AB
66% — A8
65% — A6
64% — A3
63% — A1
62% — 9E
61% — 9C
60% — 99
59% — 96
58% — 94
57% — 91
56% — 8F
55% — 8C
54% — 8A
53% — 87
52% — 85
51% — 82
50% — 80
49% — 7D
48% — 7A
47% — 78
46% — 75
45% — 73
44% — 70
43% — 6E
42% — 6B
41% — 69
40% — 66
39% — 63
38% — 61
37% — 5E
36% — 5C
35% — 59
34% — 57
33% — 54
32% — 52
31% — 4F
30% — 4D
29% — 4A
28% — 47
27% — 45
26% — 42
25% — 40
24% — 3D
23% — 3B
22% — 38
21% — 36
20% — 33
19% — 30
18% — 2E
17% — 2B
16% — 29
15% — 26
14% — 24
13% — 21
12% — 1F
11% — 1C
10% — 1A
9% — 17
8% — 14
7% — 12
6% — 0F
5% — 0D
4% — 0A
3% — 08
2% — 05
1% — 03
0% — 00

Some U-He colour name codes for Bazille...

COLOUR name='CC unset' rgba='44a00dff'
**** colour of the MIDI learn circles, MIDI page lines & preferences rectangles ****

COLOUR name='CC set' rgba='44a00dff'
**** smaller text on MIDI table page ****

COLOUR name='GP_DisplayBG' rgba='171e19f1'
**** Rectangle box behind text on main GUI ****

COLOUR name='GP_DisplayTXT' rgba='b2b496c5'
**** Text in rectangle box on main GUI ****

COLOUR name='GP_Graph_Full' rgba='ff6f21ff'
**** Main screen, MapGen playhead, FX names, microtuning + patch file names ****

COLOUR name='GP_Graph_Trans' rgba='783410ff'
**** FX slot borders, FX background rectangles, scroll bars, MapGen BG ****

COLOUR name='GP_Graph_TxtHL' rgba='142912ff'
**** selected item text in Patches box and microtuning box ****

COLOUR name='GP_LabelsDark' rgba='999b96ff'
**** text - inverter rectifier lag generators, glide voice pitch etc ****

COLOUR name='GP_LabelsLight' rgba='999b96ff'
**** text names of knobs rate tune etc, FX edit ****

COLOUR name='Pref Black75' rgba='be'
**** background shade for preferences panel ****

COLOUR name='Pref White 75' rgba='ffffffc2'
**** this is the text colour for preferences panel ****

My original post...

Ok, so i'm just starting by doing two of my own bastardised versions of the Gearporn skins. The green one is kinda done, it's a bit hard to get some contrast for the arrow indicator on the knobs, but the orange one I'm not sure what to alter in the Bazille.txt file to change the colour of the scroll bar, the text background rectangles, at least one of the colours of the Mapping Generator, and the highlight rectangles for the effects section and Patches buttons...

If anyone has any info it would be awesome. I have the following info from Urs, from a thread a few years ago, ( http://www.kvraudio.com/forum/viewtopic ... 1&t=345467& ) but i still can't figure out the above mentioned.

Or just use Wordpad/Textedit, create a new document, type that line...
!EDITOR=YES
save as "default.h2p" into root preset directory.

On Mac, copy Scripts and Images from PluginName.component/Contents/Resources/ (right-click show package contents) to MacHD/Library/App...Supp.../u-he/PluginName/

Restart host, there you go.

Move/Resize knobs etc. toggle between editor and gui with esc, and definitely check right-click on all sorts of things, including the empty grey space (to save changes...).


There's also a "color lab". Press c on Mac and either c or a function key on PC.

There's more function palettes, but most of them are scary. As of today I guess I'm the only one who knows what they do The transform one (x) might be useful, and the information one (i)

When designing Diva skins, make sure to use a 10 x 10 pixel raster. This is a prerequisite for the new resize algorithm.

Once I've figured this stuff out, I'll make the skins available for download, then I'm gonna have a go at doing my own skins from scratch.
Any info or feedback is welcome, cheers!
Simon

[Funkybot's Evil Twin]

So I'm sure you've figured this out, but from what I've gathered through editing the RePro skins is that there are 1) the graphic UI elements (PNG) and 2) the script controlled UI elements.

First thing is first: familiarize yourself with all the PNG's in the Skins folders and sub-folders. I find it much easier to edit the PNGs in an image editor (plug for Gimp) since it's basically a "what you see is what you get" approach. So assuming you've done that already and I'm telling you things you already know, that means the UI elements you're looking to edit are controlled by the script, which I'm less familiar with. That said, changing colors in the script is generally easy.

Go download something like Notepad++ (if you don't already have it). It's basically a text editor that respects unicode line breaks and will help you make sense of the scripts file. Open the scripts file in Notepad++. It's a nightmare to make heads or tails of in the regular Windows Notepad so Notepad++ will make things much easier. The colors used in the skins are usually defined near the top, so if you're just looking to change some colors, it's just a matter of finding the right ColourName (or whatever the value is called might be ColourLabel) and replacing one color with another. Off the top of my head, the colors are basic Hex values but they're not RGB. I think they are BGR, and they'll also to start with ff if my memory serves me well. So basically, what I'd do is find the traditional RGB hex value for a color (for instance, #4286f4), and prefix it with ff and re-order the values to BGR (#ff86f442).

When I'd want to move an existing UI element, I found it easier to just use the skin editor, but that was just for making slight tweaks to an existing skin versus trying to create a whole new one. Also I believe I read around here that the Windows version of the Skin Editor has some non-functioning features and as I'm sure you've already found, there's no documentation. I think most people working with custom skins are likely doing it via the scripts. My skins were just basic edits, so I can't be of much more help when it comes to the hardcore script editing or skin editor.

Anyway, experimentation is key. Hopefully drzhn and plugmon or some of the other folks around here who really understand skinning can chime in with actual help.

[sqigls]

Cheers, yeah i should have added, I'm a graphic designer by trade, so that side of it is no problem.

Off the top of my head, the colors are basic Hex values but they're not RGB. I think they are BGR, and they'll also to start with ff if my memory serves me well. So basically, what I'd do is find the traditional RGB hex value for a color (for instance, #4286f4), and prefix it with ff and re-order the values to BGR (#ff86f442).

I'm not sure about this, can someone from U-He chime in and tell us, how do we translate Photoshop RGB colour codes into U-He skin rgba codes?
A list of what is what in laymen's terms would also be good! As in, "GP_DisplayTXT: is the text used on such and such..." ...but with the above info at least I can work out my own list.
Cheers and thank you for your time!

[Funkybot's Evil Twin]

...can someone from U-He chime in and tell us, how do we translate Photoshop RGB colour codes into U-He skin rgba codes?

Sorry, I just double checked this. They're just standard RGB (not sure why I thought they were BGR). Don't have Photoshop but the Gimp color swatch has the option of showing hex values in addition to RGB. I'd be surprised if Photoshop wasn't doing the same. Alternatively, if you google "RGB to Hex" you'll get a bunch of different sites that all basically do the same thing. For instance, here's one:

http://www.javascripter.net/faq/rgbtohex.htm

So if you go there and enter RGB values of 0, 80, 255 it will return a hex value of #0050FF. In the script, you remove the hash and add another FF at the end for the alpha layer. So if I wanted to add that color to a U-he skin, I'd find the color name and change it to: rgba='0050FFFF'

In terms of finding which color names translate to which parameters, the skin editor will tell you all that. Once you're in the Skin Editor, click on any UI element and there will be a display at the top that shows you what color it is, and the color name as it appears in the script. Here's a screen capture from RePro-5:

ScriptEditor.jpg

[sqigls]

the thing perplexing me though - the U-He rgba codes have "FF" in random places, not just at the end or at the start. Also what about these three for example... 454c45c0, 171e19f1, b2b496c5 ...taken from one of the Gearporn skins.

from what I knew, the "A" in RGBA was a decimal value, from .1 to 1 indicating the opacity.

The problem is for me, it's all too hit and miss if i don't know either how to translate these codes accurately, or what the COLOUR names are representing on the GUI. It's all just stabbing in the dark, and I don't have enough time to do that unfortunately.
Also, there's a few GUI elements that either don't show the name code when I click on them in editor mode (due to layers or something), or a few GUI elements such as the scroll bar for instance, don't feature on the main GUI, so i can't see them or make them appear in order to click on them.

Thanks again for your time!

[sqigls]

ah ok, maybe this?... from 100% to 0% opacity...?
https://gist.github.com/lopspower/03fb1cc0ac9f32ef38f4
piecing it together slowly

[drzhnn]

The color values are in RRGGBBAA format, where:

RR - red channel
GG - green channel
BB - blue channel
AA - alpha channel (opacity)

The intensity of each channel is represented by a hex value - from 00 (no color) to FF (100% color). The final color is a result of the mix of all channels. For example:

Code: Select all

RR GG BB AA
-----------
FF 00 00 FF - full_red no_green no_blue full_alpha =  fully opaque red color
FF 00 00 1A - full_red no_green no_blue 10%_alpha = almost transparent red color
FF 00 00 00 - full_red no_green no_blue no_alpha = fully transparent red color (invisible)

FF 00 FF 80 - full_red no_green full_blue 50%_alpha  = semitransparent pink color
FF 80 00 80 - full_red 50%_green no_blue 50%_apha = semitransparent orange color

[sqigls]

added temp download links for 3 skins, and some resources for anyone wanting to carve out a Bazille skin. Maybe also useful for any of the U-He synths or effects? ...Have fun, best of luck!
Simon

[ENV1]

Go download something like Notepad++ (if you don't already have it). It's basically a text editor that respects unicode line breaks and will help you make sense of the scripts file. It's a nightmare to make heads or tails of in the regular Windows Notepad so Notepad++ will make things much easier.

I was linked here from another thread so i know the thread is old, just thought id share what i know for future reference.

The reason why some text files dont have proper linebreaks in Notepad is because some text editors (MAC, Linux) only write hex 0A whereas Notepad expects hex 0D 0A. This is easily fixed though, and you dont need any 3rd party apps to do it. Heres the procedure:

- Open your Windows folder (C:\Windows)
- Drag the file that doesnt have proper linebreaks in Notepad onto write.exe (WordPad)
- Click the Save button

After that the file will have proper linebreaks in Notepad too.

Alternatively you can of course simply use WordPad to edit the file in the first place. In case Open will add a file as an object rather than displaying the text, just drag the file onto write.exe instead.

[EvilDragon]

Or you can use a proper text editor like Notepad++ or Sublime Text that support all EOL formats and much more

[pekbro]

I always liked ultra edit, it's pretty expensive now though, compared to what I paid for it 20 yrs ago.
UE is great for large text files, try to open say a 1 gb text file in note pad and see what happens.

[ENV1]

Or you can use a proper text editor like Notepad++ or Sublime Text that support all EOL formats and much more

Of course you can, the point was that you dont need to if you dont want to use 3rd party apps.

(If regular Notepad suffices, and you merely want the formatting of a file fixed, re-saving it with WordPad will do the trick because it will auto-convert all 0A linebreaks into 0D 0A linebreaks.)

Choice is yours of course.