GForce Minimonsta2

[ELEX]

...Which format is that (VST, VST3, AU)?

That was VST. VST3 acts the same, afaict. On windows, at least.

[vulpes777]

I will take Minimonsta, extra sugar is welcome for me

Was gonna upgrade today, but the intro offer of £25 appears to be over (?)
Just wrote to GForce to confirm

Try logging on to your user account and then add Minimonsta2 to the shopping cart. The upgrade discount is still there for me.

Regards,

--
Marco

[Dencheg]

Some gripes:
1) The knobs are too bright;
2) Consistently inconsistent mousewheel support across the synth line of GForce. In Minimonsta 2 some some slider and knobs don't work at all (like waveform knob, which could simply jump between waveforms). The knobs which supot jumping through integer values (pressing Ctrl key) do that only counterclockwise with mousewheel.
OMG, why not to support it properly and entirely like in Imposcar 2 or u-he synths, or get rid of it at all like in OB-E & SEM

[DNnX]

upgraded last week and installing now
waiting for impOSCar3 (with fix for 192kHz crashing)!

[thecontrolcentre]

I will take Minimonsta, extra sugar is welcome for me

Was gonna upgrade today, but the intro offer of £25 appears to be over (?)
Just wrote to GForce to confirm

Try logging on to your user account and then add Minimonsta2 to the shopping cart. The upgrade discount is still there for me.

Regards,

--
Marco

Thanks Marco, but that's not working for me. At checkout it's still $59 (inc VAT).

[MrJubbly]

I feel Gforce should be commended on their recent product updates and features. I really like their new preset menu system being included in their latest updates.

However, I do have a suggestion to help improve the workflow of this feature, which just requires a re-jigging of the button configuration to make it a bit more accessible and intuitive for users.

Currently, I feel the navigation button placement is not quite as intuitive as it could be by making just a few tweaks.

My main issue currently, is that the Previous/Next preset buttons are on the opposite (left-hand) side of the preset menu screen to the actual preset selection column (right-hand) side.

I feel this can be more intuitive to the user if these navigation buttons were shifted closer to that end of the GUI. Currently, when I'm browsing presets and shifting between manual selection and the Prev/Next buttons, I am zig-zagging across the GUI, rather than having the related buttons in a more intuitive and closer proximity to each other, such as in this mock up:

Gforce Preset Menu - Button Configuration_.png

I did make this suggestion to Gforce and I hope they will consider this tweak in a future minor update.

[Echoes in the Attic]

I just wish the next and previous buttons were side by side rather than stacked on top of each other in that small space.

[mholloway]

but if you're hitting prev <> next, you don't need to click on the preset names, that's the whole point-- so who cares if it's underneath the preset name list or not? it makes no difference, it's an either/or operation. this is such an incredibly minor quibble I'm kinda of shocked at the effort you're putting into describing it......but whatever, to each their own.

but things are indeed getting pretty pedantic in here.... I'd much rather they fix the clipping/aliasing output than move some prev/next buttons four inches to the right

[Echoes in the Attic]

but if you're hitting prev <> next, you don't need to click on the preset names, that's the whole point-- so who cares if it's underneath the preset name list or not? it makes no difference, it's an either/or operation. this is such an incredibly minor quibble I'm kinda of shocked at the effort you're putting into describing it......but whatever, to each their own.

Huh? What the hell are you talking about? Who said anything about the preset browser? I’m talking about the previous and next buttons. Only. I can’t even comprehend what you are on about with regards to the preset list. If the preset list is open you’re not even using those buttons. I’m obviously talking when the browser is closed.

Previous and next buttons makes no sense stacked vertically when there is horizontal space. That’s why everyone does them side by side.

[ELEX]

I don't think there actually is any unintended clipping in this synth. Minimoogs are supposed to saturate and eventually – when feedback is cranked – clip, aren't they ? Which is exactly what Minimonsta2 does. Full scale oscillator input shows soft clipping*, cranking the feedback will drive things into hard clipping, at which point the feedback loop becomes self oscillating at decreasing and harmonically related frequencies ( and may jump wildly between those. ) Here's how the clipping looks:

minimonsta2 clipping.gif

*at his point, some mild artifacts occur at high pitches ( above C6 ), none of which sound particularly nasty.

[mholloway]

but if you're hitting prev <> next, you don't need to click on the preset names, that's the whole point-- so who cares if it's underneath the preset name list or not? it makes no difference, it's an either/or operation. this is such an incredibly minor quibble I'm kinda of shocked at the effort you're putting into describing it......but whatever, to each their own.

Huh? What the hell are you talking about? Who said anything about the preset browser? I’m talking about the previous and next buttons. Only. I can’t even comprehend what you are on about with regards to the preset list. If the preset list is open you’re not even using those buttons. I’m obviously talking when the browser is closed.

Previous and next buttons makes no sense stacked vertically when there is horizontal space. That’s why everyone does them side by side.

Yikes, relax. I was referring to MrJubbly's images of the preset browser, not your post, where he's specifically talking about the location of prev + next buttons in the browser. He even posted pictures and everything, with red arrows, etc. I thought it was obvious. Guess not. Try not to lose any sleep over it.

[MrJubbly]

but if you're hitting prev <> next, you don't need to click on the preset names, that's the whole point-- so who cares if it's underneath the preset name list or not? it makes no difference, it's an either/or operation. this is such an incredibly minor quibble I'm kinda of shocked at the effort you're putting into describing it......but whatever, to each their own.

but things are indeed getting pretty pedantic in here.... I'd much rather they fix the clipping/aliasing output than move some prev/next buttons four inches to the right

No, you're wrong. I do this all the time in most other plugins where the prev/next buttons are situated nearer to the manual preset selection area.

Simple example: You manually select the preset starting point, then you intuitively navigate to the nearby prev/next buttons to cycle through them 'from your insertion point'. Almost all other synth preset menus are configured this way.

Where these buttons are currently situated (far left of GUI) makes no sense, because, even if you were to change the 'collection' group (which is the column these buttons are currently under), the prev/next will not function (cycle through the presets) 'until' you select a preset (located on the far right).

So currently, if you change the collection (far left), you must then click on a preset (to the far right) to select the starting point, then move the mouse back over to the far left to start cycling through the presets.

There's basically no scenario, where it makes more sense to have these located on the left side, than on the right, directly under the preset names themselves.



[EDIT]: But luckily, it appears GForce themselves, seem more receptive to this idea. I have since, received their reply to my suggestion:

Thanks. I think that's a great suggestion, and certainly a valid strong argument. Thank you for sending it, I'll pass it on to the team for discussion.

For now, you may find life a little easier using the Next/Prev arrows on the right of the Parameter display, which are closer to the preset list, or arrow keys on your QWERTY keyboard, which will both do the same thing.

[Uncle E]

That was VST. VST3 acts the same, afaict. On windows, at least.

Thanks. I'll alert GForce about it from my end, as well. It appears there is something wrong with the Windows version.

[Echoes in the Attic]

but if you're hitting prev <> next, you don't need to click on the preset names, that's the whole point-- so who cares if it's underneath the preset name list or not? it makes no difference, it's an either/or operation. this is such an incredibly minor quibble I'm kinda of shocked at the effort you're putting into describing it......but whatever, to each their own.

Huh? What the hell are you talking about? Who said anything about the preset browser? I’m talking about the previous and next buttons. Only. I can’t even comprehend what you are on about with regards to the preset list. If the preset list is open you’re not even using those buttons. I’m obviously talking when the browser is closed.

Previous and next buttons makes no sense stacked vertically when there is horizontal space. That’s why everyone does them side by side.

Yikes, relax. I was referring to MrJubbly's images of the preset browser, not your post, where he's specifically talking about the location of prev + next buttons in the browser. He even posted pictures and everything, with red arrows, etc. I thought it was obvious. Guess not. Try not to lose any sleep over it.

Sorry, I must have been having a grumpy day.

[NothanUmber]

16 voice polyphony sounds good. Is it also MPE compatible? (So, can foremost the filter be modulated per voice or is it in the global audio path)?