NEW MicroBrute Firmware coming!!!

[AustinBru]

I honestly had given up hope for the long-forgotten firmware of the MicroBrute despite some minor, but known issues (LFO phase issues, Sequence pattern 1 will play on boot up regardless of which sequence is selected via the knob).

I am honestly quite happy with the way my MicroBrute performs, but I have long day-dreamed of improved features that could be implemented on the software side of things... So I probed Arturia support a few days ago, just to see if we can expect anything in the future.

And... today they replied:

"For your information, a Microbrute update will be released in less than two weeks."

Let the speculation begin.

What features would you all like to see implemented?

[alberto]

It's already out on the download page, 1.0.4.114.

New features
- Added Midi Stop handling

Bug fixes
- Various Sequencer/LFO synchronisation improvements
- The correct sequencer pattern is played at power on
- Switching sequence keeps the correct pitch
- Send & receive midi channel use values form 1 to 16, 17 is used as ALL channel for receive
- When Externally synchronized, seq rate does not change gate lenght anymore
- No more crashes when setting CC #111 at value 126 or 127
- All Notes Off message is sent when switching to local control off (CC122)
- Gate Length (CC113) does not impact sequencer Step Size (CC107) anymore
- Sequences are now properly updated after loading sequences from the MCC
- No more LFO Saw glitches at high frequencies
- No more Clock bleeding when the LFO amount modified via mod wheel when synchronized externally
- No more ModWheel and PitchWheel conflict using external MIDI in

[erstlaub]

It's just a real shame that they didn't manage to fix my one massive gripe where it can't/wont run the sequencer from an external clock OR the internal clock depending on how it's connected/set up in Microbrute Connection.

Sometimes I want to run sequences without turning on my clock modules but having to externally patch the Brute's only LFO back into itself as a clock to run the sequencer just kills the immediacy and requires digging out USB cables and a computer and then trying to remember to change it all back.

[alberto]

Did you check and verify that it isn't fixed?

I know that sometimes things are fixed but missed to be mentioned in the changelog.

[erstlaub]

Yep spent a good long while today trying out all the possible settings possible and no dice.

[improziv]

MAC OSX 10.11.6 - can't seem to be able to update the firmware. Microbrute connection center shows firmware to be  version 1.0.3.2  When I click to update is says it's downloading then it asks to reboot the brute and click ok. When I do all of that, the connection center still shows 1.0.3.2 .   Has anyone else experienced this? Should there be an updated connection center to go with this firmware update?

If instead, I manually download the firmware file - where and how should it be installed?

Thanks!

[alberto]

You need to use the MIDI Control center now, not the Microbrute Connection

[improziv]

You need to use the MIDI Control center now, not the Microbrute Connection

That did it. Thanks! I wonder where they notified users of the change in update procedure?....

Cheers

[avantronica]

Phase Issues :

So, the TRI LFO is  still  out of phase with just about every other tri shape out there that i know

It starts -90deg out of phase, so it always starts low (key sync / free / seq off)

think of the vibrato case, you normally want that to start on the pitch and to then wobble about it

this was one of the gripes i had about it

it seemed so hopeful looking through the release notes that this would have been addressed

when the sequencer is playing the phase (and key sync is on) the phase is +90 (as opposed to -90 when the seq is off)

if the rate is tied to seq rate (and seq is off) keysync is ignored

so i guess these are not by mistake

the other thing is that the LED's seem to be all over the place in terms of phase/sync too

e.g. the square phase is high, but the led on state is low, so it's not following key sync or the phase of the shape as drawn, same with saw

i had high hopes this was what had been fixed

is there any good reason for it to be this way?  it seems like a strange call imho .. the only thing i can think of may be that the phase of all the shapes seem to sync on the natural rhythm of them  ( if you were to listen to a sustained note and tap fingers along, you'd naturally sync with the phase as it stands )

Oh, I really wish sample and hold (random) was a toggle option for substituting the square shape in the connection s/w .. even just a toggle for the saw phase could be nice

anyone ? might be good to have this looked at now in case the update cycle takes years to come around again

[alberto]

After the firmware upgrade, the version is shown as 1.0.4.0. But it is actually the last one, here's Arturia's reply on this:

Hello.

There is a little bug in the Arturia Software Center preventing to correctly read the firmware revision.

So simply ignore this, once updated, your firmware will be up to date.

We will fix this display bug in the forthcoming firmware update.

Best Regards.

Edouard
--
Arturia Technical Support

[AustinBru]

I must admit... I was hoping for more "features"

But I am just SUPER glad that they are still supporting the project.

Maybe a dumb question: - Gate Length (CC113) does not impact sequencer Step Size (CC107) anymore. I suspect the CC values for Step Size are what? Short, Medium, and Long? Does Gate Length have full resolution? I've always used the Decay slider to achieve that Gate Length fiddling.

[microdude]

First of all, thanks to Arturia for still supporting the Microbute.

I was, however, expecting some new LFO features (single-cycle saw, s+h, stationary wave, monopolar...). Besides, the only new feature is somehing I don't know what it is. Any clues about the Midi Stop handling? I've tried MIDI MMC but doesn't seem to work.

Regarding the LFO, as avantronica has previously said, the LFO LED is off at the beginning of the cycle only when it runs free. This is strange and confusing and could be easily fixed, I presume.

About the version related issue, my MicroBrute says it's the 1.0.4.0 version. I believe this is correct because when I ask it with a General Information Identity Request that is the version it returns. (See the last four bytes before the ending byte.)

Code: [Select]

$ amidi -p hw:1,0,0 -S 'F0 7E 7F 06 01 F7' -d
F0 7E 01 06 02 00 20 6B 04 00 02 01 01 00 04 00 F7


[alberto]

I guess what happened is that the developer forgot to update the firmware version string to 1.0.4.114 in the source code and left it to 1.0.4.0, which is what is reported back by the Microbrute. As Eduard of Arturia already said before, it is fine. We have the latest firmware installed.

[milchschnitt]

Bug fixes
- Various Sequencer/LFO synchronisation improvements

So I take it – the way this statement  is phrased -  the microbrute has still loads of issues wrt the sequencer an the lfo?
I'd love to purchase a microbrute soon but I am not willing to put up with serious bugs.

[Art1]

It's been a very long time, but finally the new firmware is really here! Thank you very much for it and for not abandoning the MicroBrute. I've tested it and it's OK, except one bug which I found some time ago.

When I send a SysEx to my Casio CZ-1000 via a standard MIDI cable, MicroBrute freezes and it's necessary to restart it completely. I have a MIDI splitter on a way from my computer sequencer, so SysEx go to both synths, but I thought that:
1) MicroBrute doesn't accept any SysEx via a MIDI cable, only via USB (I was never able to send any SysEx to MicroBrute via a MIDI cable, which I would like).
2) MicroBrute accepts only SysEx with the Arturia ID number.
So why does it freeze every time it sees a Casio SysEx?

Which brings me to another question: Would it be possible to change the firmware to accept SysEx also via a MIDI cable? It would be nice for example for sending sequencer programs or some system parameters.