Seq Mod Problems

[BosseCory]

So I was having some serious problems where my sequencer mod refused to be programmed and would not let me change values, it would only display +/- 0%. I was about to hit send on my technical support case when the timer on my space heater turned it off and the thing started working suddenly.

So apparently the lesson here is, don't put your Brute on the same circuit as your space heater. Because...of all things...the sequencer mod will stop working. Everything else worked, even pre-programmed mod sequences. But new ones could not be entered.

Learn from my mistakes!

[DrJustice]

It's a bug in firmware 1.1.0.73 - so don't worry about your Brute, the heater has not damaged it (although I would keep things like heaters on a different circuit since the thermostat/switching can be quite noisy).

I have established a 100% repeatable pattern to get it working again, if only temporarily: By pressing Record and Play simultaneously it will start working as normal. It may get stuck at +/-0 again after a while, but you just repeat the Record+Play trick and it works again.

[BosseCory]

Thank you so much! This has been really frustrating and I just discovered it was still doing it, so it's good to know there's a temporary fix and it's a known bug.

EDIT: Looks like I'm having even further issues with this. The Record+Play trick now causes the Seq Mod to SHOW values, but it doesn't hold on to them and keep erasing my input when I move to the next step. This is extremely annoying, as I've got legitimate work that needs to be done on this thing.

[DrJustice]

It's working here - I tested it right now: starting with an init patch, selecting the Ladder for VCO 1, recording some notes, doing the play+rec trick, entering mod values with step button + mod amount knob, assigning SeqMod to Ladder filter cutoff at 100%, setting Ladder resonance high to clearly hear the modulation. This works, and the mod values will stick, also across a save/load cycle. 


(BTW, the bug seem to be consistently triggered by having been in Record mode)

[siliconscientist]

EDIT: Looks like I'm having even further issues with this. The Record+Play trick now causes the Seq Mod to SHOW values, but it doesn't hold on to them and keep erasing my input when I move to the next step.

I got my Matrixbrute last weekend and almost immediately came across the SEQ MOD bug. The problem was exactly like in the quote above but after some experimenting I've found out that the following workaround seems to get the bug out of the way:
1.  press REC+PLAY
2.  stop the sequencer if necessary
3.  initialise the sequencer (PANEL+SEQ).

I haven't tested it for very long so I don't know yet if the bug will return after some time. But for the time being, it works.