Hive 2.0 sanity check

[rumos]

Nice update! Especially the GUI Design.
Is it possible to modulate the X or Y position in the XY pad by an LFO for example? A record function for the path would be nice as well.

[dermage]

Any chance of a non mirrored skin?

We've hired another Ui designer for something completely different. Just wasn't ready in time, will be added when ready.

Eagerly waiting for that!

As I like the new GUI more than the old one. I feel it's still not too much fun to use compared against the Plugmon Eclipse, which has a super fast workflow imho. Especially when using sequencer/ARP/Effects which are way more sorted and easier to see for me.
I know this is probably a matter of taste. But I find it harder to navigate in the effect section, as the knobs are not very separated and too packed in the Hexagon. Another taste matter is the sequencer, which in Eclipse is more visual (as in Bazille).

Thanks for hearing us Urs and doing another skin.

[Urs]

Nice update! Especially the GUI Design.
Is it possible to modulate the X or Y position in the XY pad by an LFO for example? A record function for the path would be nice as well.

No, these controls are meant as Macros, like the "easy knobs" in many NI products. Modulating them would defeat the purpose: Their meant for realtime hands-on control in a live situation, or automation in a production environment.

However, as you can see, unlike the XYs in Zebra2, the XYs in Hive are based on the very same principle as the ModMatrix. So whatever means you have to modulate XYs, you can do the same thing in the ModMatrix itself.

That said, a "modulation recorder" is something I could contemplate. I don't know if I would go for an XY-approach though, as the concept would clash with the existing XYs. We have dropped the concept of Vector Synthesis due to this clash (and we did the superset of 2D wavetable synthesis instead). Anyhow, I'm just very happy with how Hive 2.0 turned out right now, let's first see how everyone goes with it before we make new plans

[Urs]

Ok after using new hive, only 2 thing that pops about about the GUI:

1. Browser font somehow feels too small

We have a ticket for that. I'm not sure if the font size changed from our other products, but I totally get that it might be helpful to increase it when necessary.

2. Not a fan of sandy grain effect on grey panels (i also remember on previous gui mockup there was no effect?). But im not a fan of that effect at all on any media except on video games as it hides some inperfections

I guess it makes Hive sound a tad "warmer" when there's a bit of grit on the UI.

(ducks away)

[PieBerger]

I guess it makes Hive sound a tad "warmer" when there's a bit of grit on the UI.

(ducks away)

[exmatproton]

Ok after using new hive, only 2 thing that pops about about the GUI:

1. Browser font somehow feels too small

We have a ticket for that. I'm not sure if the font size changed from our other products, but I totally get that it might be helpful to increase it when necessary.

2. Not a fan of sandy grain effect on grey panels (i also remember on previous gui mockup there was no effect?). But im not a fan of that effect at all on any media except on video games as it hides some inperfections

I guess it makes Hive sound a tad "warmer" when there's a bit of grit on the UI.

(ducks away)

ah....didn't know the grain was doing that...mystery solved!

[joris.roling]

No, these controls are meant as Macros, like the "easy knobs" in many NI products. Modulating them would defeat the purpose: Their meant for realtime hands-on control in a live situation, or automation in a production environment.

However, as you can see, unlike the XYs in Zebra2, the XYs in Hive are based on the very same principle as the ModMatrix. So whatever means you have to modulate XYs, you can do the same thing in the ModMatrix itself.

What are the exact rules for ModMatrix/XY affecting the actual parameters. I've seen double assignments of for example Delay: DryWetMix in X4 & Y4. I don't get what amount of impact X4 vs Y4 have on the Delay: DryWetMix. How does that work?

[Vertion]

Urs, I have an actual bug. I have FL12 loaded up. The H2 GUI is noticably slowing the FL gui down, even the typing keyboard is lagging on note-ons. It does seem to reduce a bit when I decrease the gui size to 100%, but still very noticable. This is occuring on only about 50% cpu, so it is not an overrun issue. Granted it's running on an older machine running Win. I'm not sure if this is thread locking issue or what. Ideas? I can send a video if needed.

[Urs]

What are the exact rules for ModMatrix/XY affecting the actual parameters. I've seen double assignments of for example Delay: DryWetMix in X4 & Y4. I don't get what amount of impact X4 vs Y4 have on the Delay: DryWetMix. How does that work?

You can of course create your own XY settings.

In some cases our automatic assignment got confused and double-assigned stuff, usually simply because there wasn't anything else it found to assign. In those cases both macros have the same effect, and they stack up on each other. We'll try to avoid those in future.

[Urs]

Urs, I have an actual bug. I have FL12 loaded up. The H2 GUI is noticably slowing the FL gui down, even the typing keyboard is lagging on note-ons. It does seem to reduce a bit when I decrease the gui size to 100%, but still very noticable. This is occuring on only about 50% cpu, so it is not an overrun issue. Granted it's running on an older machine running Win. I'm not sure if this is thread locking issue or what. Ideas? I can send a video if needed.

Note ons will

- redraw the keyboard control
- start a lot of change in the Scope
- start a lot of change in the wavetable visualisation

These can have an impact on CPU, as often described above. In our own tests we only saw a large impact when the Scope or the Wavetable tabs in the hexagon were open, even on six year old machines. However, it's totally possible that the keyboard control and the mini-scopes in the Synth UI have a big impact on some machines too. In that case we'll probably try to publish an alternative skin without these elements - or simply smaller versions of them.

I can double check, but I don't think there are any thread locking issues.

[Teksonik]

How about an option to turn off animations ? Let's be honest they're nothing but eye candy.

Anyway I'm not seeing any lag in FL Studio 12 here even when the Scope or WT's are displayed and this test system is really under powered (i3 , onboard graphics, Win 10).

[Stefken]

Any chance of a non mirrored skin?

We've hired another Ui designer for something completely different. Just wasn't ready in time, will be added when ready.

Eagerly waiting for that!

As I like the new GUI more than the old one. I feel it's still not too much fun to use compared against the Plugmon Eclipse, which has a super fast workflow imho. Especially when using sequencer/ARP/Effects which are way more sorted and easier to see for me.
I know this is probably a matter of taste. But I find it harder to navigate in the effect section, as the knobs are not very separated and too packed in the Hexagon. Another taste matter is the sequencer, which in Eclipse is more visual (as in Bazille).

Thanks for hearing us Urs and doing another skin.

+1

[Urs]

How about an option to turn off animations ? Let's be honest they're nothing but eye candy.

With the voice of... I forgot who: Well, well, well!

People have been demanding visual feedback for modulations forever. I've always been against "balls in orbit" of knobs, because they doesn't visualize fast modulations well. The filter and wavetable animation however visualize the two most important modulations in Hive (apart from pitch, which is less mistakable than anything else). For everything else there's the scope (which can display almost anything except filter curve or wavetable position).

So in my view, these things go hand in hand. Are they a necessity? - No. But there was demand for them, hence...

Anyway I'm not seeing any lag in FL Studio 12 here even when the Scope or WT's are displayed and this test system is really under powered (i3 , onboard graphics, Win 10).

Good to know, thanks!

[Teksonik]

With the voice of... I forgot who: Well, well, well!

Sorry, I don't get what you're trying to say.....

People have been demanding visual feedback for modulations forever.

That's why I said the option to turn off animations for those us who program our synths by listening to them instead of watching them.

After all they're musical instruments not video games.........

Anyway I won't "demand" anything but the option to turn off animations would be welcome and used immediately here.

[cowby]

Nice update! Especially the GUI Design.
Is it possible to modulate the X or Y position in the XY pad by an LFO for example? A record function for the path would be nice as well.

Just about to post my comment as your last suggestion : Rec the movement/path of 1-4 and TBH, like Mr Rob Papen's Vecto/Go2. Though the XY pad can be mod'ed by many parameters, but I think if I can see the movement will be more helpful. Don't know if it eats up more CPU resources ??