I have tried all (free) of them - most of them don't work properly with V2, especially with the scope display. Or they look even worse than the original skin. A pity.Urs wrote: Sun Jun 08, 2025 3:02 pmThere are some nice custom skins for many of our plug-ins, including some for Hive 2, maybe there's one you like more:
https://u-he.com/PatchLib/skins.html
ACE vs Bazille/Zebra3 and Hive2 vs Zebra3 questions
-
- KVRist
- 227 posts since 4 Jun, 2019
-
- KVRAF
- 3140 posts since 28 Mar, 2008 from a Galaxy S7 far far away
The easiest way to adjust this is to open the hive 2 background in a graphics editor, I use paintdotnet for everything.
In there you can use a built in plugin to change the HSL of the background image. You can do this with any other parts of the skin that require adjustment too.
As always, make a backup first.
In there you can use a built in plugin to change the HSL of the background image. You can do this with any other parts of the skin that require adjustment too.
As always, make a backup first.
-
- u-he
- 30188 posts since 8 Aug, 2002 from Berlin
Hehehe, one can even change HSL in our plug-ins directly. I'll eventually need to make a video about it...
-
- KVRAF
- 3140 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- u-he
- 30188 posts since 8 Aug, 2002 from Berlin
If you know how to open the UI Editor, press p to open the graphics viewer. It has controls for Exposure, Offset, Gamma, Hue, Saturation and Brightness.
In the Script file this is saved for each graphic like so:
Code: Select all
GRAPHIC name='H2-FiltRoute-O1' path='4' type='multi'
GR_PROPERTY graphic='H2-FiltRoute-O1' name='Exposure' id='0' value='0.00'
GR_PROPERTY graphic='H2-FiltRoute-O1' name='Offset' id='0' value='0.00'
GR_PROPERTY graphic='H2-FiltRoute-O1' name='Gamma' id='0' value='0.00'
GR_PROPERTY graphic='H2-FiltRoute-O1' name='Hue' id='0' value='0.00'
I can't remember the actual ranges, I guess they go from -1 to +1, not sure.
-
- u-he
- 30188 posts since 8 Aug, 2002 from Berlin
Here's a screenshot of what that looks like:
There's a good chance that this only work on Mac, but I think that since we fixed Key Control and made it a prominent feature, the key commands in the editor may work as well.
Save changes by right-click into grey background and "save changes".
There's a good chance that this only work on Mac, but I think that since we fixed Key Control and made it a prominent feature, the key commands in the editor may work as well.
Save changes by right-click into grey background and "save changes".
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 3140 posts since 28 Mar, 2008 from a Galaxy S7 far far away
I can't recall how to enter UI edit mode! Is it standard for all u-he plugins?
-
- u-he
- 30188 posts since 8 Aug, 2002 from Berlin
In a top level preset called "default.h2p" (which you can open in any text editor) you add the following linesl23 wrote: Wed Jun 11, 2025 9:00 pm I can't recall how to enter UI edit mode! Is it standard for all u-he plugins?
!EDITOR=YES
You can basically create an empty text file, call it "default.h2p" (without .txt ending) and put that single line in there. Then start the plug-in. Works in any of them.
-
- KVRAF
- 3140 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRAF
- 3140 posts since 28 Mar, 2008 from a Galaxy S7 far far away
I created a new file as described, containing "!EDITOR=YES" without the quotes, placed the file in the root of the UserPresets folder but it doesn't show up in the Hive preset browser.
I'm on Windows though, you say it may only work on Mac?
I seem to remember this differently as some years ago, I read about a different method to enter edit mode, wasn't there some other way? I do recall it being complex to edit though.
I'm on Windows though, you say it may only work on Mac?
I seem to remember this differently as some years ago, I read about a different method to enter edit mode, wasn't there some other way? I do recall it being complex to edit though.
-
- KVRAF
- 3140 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Ok, it needs to be in the Hive.data/Presets/Hive folder.
Doesn't really do anything other than show a red box when hovering over something, even then, the hover is way off the cursor position.
Clicking opens a box to name/rename the current graphic.
Right click brings up a menu that is way to confusing to suss out!
That's all I can see it doing.
Doesn't really do anything other than show a red box when hovering over something, even then, the hover is way off the cursor position.
Clicking opens a box to name/rename the current graphic.
Right click brings up a menu that is way to confusing to suss out!
That's all I can see it doing.
-
- u-he
- 30188 posts since 8 Aug, 2002 from Berlin
As I said... we'll eventually need to do a tutorial on this. But that is a week or two of work involving our UI designer and myself, and even that is just going to scratch the surface. We don't ever really have that time, and many 3rd party skin designers prefer to work on the text file directly.
-
- KVRAF
- 3140 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRer
- 1 posts since 12 Jun, 2025
I always come back to Hive 2. Does the conventional stuff really well, and has some crazier features for spice (function gens, reverb/sideband etc). Those more niche parts take some learning, but they’re very worth it once you figure them out.
As for Zebra3, it’ll have much more advanced features for sure. But naturally it’ll be a slower workflow… so I guess it depends on what you value.
(Sidenote: If you really want to get into wavetable stuff, there’s always .uhm scripting for Hive 2 too!
)
As for Zebra3, it’ll have much more advanced features for sure. But naturally it’ll be a slower workflow… so I guess it depends on what you value.
(Sidenote: If you really want to get into wavetable stuff, there’s always .uhm scripting for Hive 2 too!
)