Modulation Wheel

[LordVampyre]

been looking for this updated firmware 1.0.3.3 and I cant find it anywhere. Arturia site has 1.0.3.2

[fwestivus]

Looks like it's been quiet here for a while, but I thought I'd ask anyway:

My MicroBrute pitch wheel had the problem of jumping down then going up when I bent upwards - I initially thought this was the pot, so replaced it, which didn't work, then I found this thread and the calibration software, which stopped the jumping problem, but now it doesn't work as a pitch *bend* just a shift. It's either all up or all down, rather than bending. I've tried calibrating it again a few times, but no luck.
Any idea what the solution could be?

[skinfaan]

My pitch wheel was jumping, but I changed the bend value from 12 to 6 in the connection software and now it's working.

Peter

[mcviga]

Hi everybody, the pitch wheel on my microbrute is working bad, when I getting down it is working perfectly but when I getting up, it jump down at the biggining of range and jump down at the end of range ... the calibration proccess fix the problem but when I turn off the brute and turn on again, the problem is back again ! How I can fix and save with the calibration tool ? I'm sure it is not an hardware problem but I did the calibration proccess a lot of time and allways the same problem !! help 

this is the problem i'm dealing right now! Calibration helps! But only before first restart. After restart pitch wheel (up position) faults again

[mcviga]

Oh, thank God:) i think now it works for me too:)
The problem was in a firmware version. I thought that i have the latest one. 1.0.3.2 (as it supported on Arturia's website).
But i downloaded the files uploaded here https://owncloud.arturia.net/index.php/s/Br2HYsOOsXoY40q
And there's a newer version 1.0.3.3. I updated firmware, ran calibration test and after restart pith wheel works fine.
I will test the synth from the begining now. Hope not to find any more faults

[fwestivus]

My pitch wheel was jumping, but I changed the bend value from 12 to 6 in the connection software and now it's working.

Peter

I tried this but no joy.

[fwestivus]

I hadn't thought to check it over midi before now - it's doing the jump on midi, too.
So, I've calibrated, tried changing bend range, updated the firmware, calibrated, tried changing the bend range, replaced the pot, calibrated again, tried changing the bend range, updated the firmware again and calibrated again and changed the bend range again, and still it jumps. This is really bugging me.

[americanhanko]

I received my MicroBrute from Amazon yesterday evening (April 27, 2019) and I'm currently experiencing a couple issues. I opened a Technical Support ticket earlier this morning, but wanted to post an update here since the information in this forum immediately solved one of my issues. Also, I updated the firmware to version 1.0.4.114 immediately upon receiving the MicroBrute using MIDI Control Center version 1.8.0.1031 (formerly known as MicroBruteConnection).

• The first two white keys (C and D) are sticking when releasing them. It almost feels like they are grinding up against something below them. They feel noticeably different than the rest of the keys. Still experiencing this issue.

• When using the Pitch wheel, just a short bit after turning it either up or down, it skips over the pitch modification for a short distance. It reverts back to unmodified signal, and then continues on with the modification. The Mod wheel does the same thing, only this happens at the bottom of the wheel. The signal modification starts, reverts back to baseline for short distance, then continues on with the modification. This issue has been resolved thanks to the Windows-only WheelCalibration software, and has stayed fixed even after reboot. At the time of this post, I successfully ran the WheelCalibration software on the latest version of Windows NT 10.0 (Windows Server 2016 / Windows 10).

• I cannot get the sequencer to work. I have followed all the instructions carefully, but PLAY mode does not play the inputted notes while RECORD mode is engaged. Still experiencing this issue.