FWIW, this is my number one feature request for the next update. Why include controller-only features (like the velocity sensitive keyboard in a non-velocity-sensitive synth) if it can't be used as a proper controller? I'd love to be able to control what I need to without plugging or unplugging to cut internal sounds.

Why include controller-only features (like the velocity sensitive keyboard in a non-velocity-sensitive synth) if it can't be used as a proper controller?

I'm feelin you, but I think Bruno and the Arturia loyal fanboys here will tell you that the Minibrute has 'Alternative' DAW controller features and that it 100% can be used as a DAW controller (just not at the same time as using it as a synthesizer).

They will also tell you to be patient, stop complaining and remind you that it is being considered in a Firmware update (even though the start date of this thread is July 2012).

The Minibrute is a nice synth and some may call it 'quirky', but if you read through the forum threads you can see the amateurish way this synth has been designed/built. Lots of manufacturing/quality issues, a number of questionable design decisions and a few glaring errors.

yeah considering how they are usually really on top of things on the forums, why are they willingly ignoring this? if it's just not possible with the hardware or firmware, then fine just tell us. but if it is then why not just let us know yes / no if it's going to be put in?

this is under "details" on minibrute page "MIDI In/Out : Sequence MiniBrute from your computerís MIDI interface and DAW, or any other MIDI-Out enabled gear you have. Alternatively use MiniBrute as a master keyboard for your DAW or other MIDI-enabled equipment."

really a pain to use it as a master keyboard without the local on/off feature imho, and a bit deceptive...

Said this earlier in this read already, but the gist of the problem is this...

If you read through the forum threads you can see the amateurish way the Minibrute has been designed and built. Lots of manufacturing/quality issues, a number of questionable design decisions and a few glaring errors.

The missing local on/off mode is a huge error, but the lack of controls on the digital side of the synth make it really tough for them to include local on/off in a way that:a) is easy for the user to implement b) won't result in less experienced synth users thinking their Minibrute is broken when in local off mode, which would then result in Arturia getting lots of false repair queries

They really screwed the pooch on this one, that's why I suspect Bruno is keeping very quiet

If you read through the forum threads you can see the amateurish way the Minibrute has been designed and built. Lots of manufacturing/quality issues, a number of questionable design decisions and a few glaring errors.

I don't think that looking at the forum topics is a fair way of assessing quality.There are naturally going to be maybe a majority of the threads about issues with the synth, because people will post here when they have a problem. You don't post something every time something works as it should.Yes, it's not the best built synth ever, but you get what you pay for, and I think this is a powerful synth for its low price.

The MiniBrute is intended to be a synth, then it's a bonus the more . It is not meant to be a midi keyboard.We must take things for what they are and ignore the "marketing" and you'll see that life becomes much more enjoyable as well.Ok I spellsPs: Bruno has heard for the local off; turn down the level volume

This would be a very nice addition to the MB. It's ok if it's not going to be implemented but please tell the users so they can look for alternative midi routing setups. Having people Invest in midi routing and then getting it on a firmware one week later would not be kosher...