The decade old project is still evolving! The new firmware v2.3 update adds a number of new features all of which are intended to make it easier to create dynamically changing sequences during both studio and live performance. Here are some of the new features:
- Variable step length – no more boring same length steps!
- Step jumps – easily control which part of the sequence is being played on the fly
- Note scale constraints – change notes manually or randomize them on the fly without hitting a wrong note.
- Alternate step notes – specify up to three alternate step notes which will be played instead of the main step note under selected conditions
- Locked step notes – exclude certain steps from randomization creating stable notes
- Most step parameters now have conditions further improving sequence variability
MidiSizer 
Hi,
I’m trying to install this new firmware (looks great!), but I can’t enter firmware update mode. The click function for Encoder A click isn’t working – and it doesn’t work to open the command pages in normal programming mode. How can I trouble shoot it?
Thanks,
Steve
if your MidiALF is in a case, try to remove the EncoderA knob and see if the encoder click works w/o the knob — sometimes it blocks the vertical shaft movement.
If this is not the case, check the continuity of the signal that carries the EncoderA click. The easy way to check it is to use a jumper wire to short MCU pin 26 and ENCA_C contact — if this activates Command Page, you have discontinuity of the PCB trace which you need to repair. If it does not, the encoder needs to be replaced. Cut its legs and remove one by one.
Thanks for the really quick response!
When I short the right hand switch contact (as seen from the rear) and MCU Pin 26, then it goes to command page. I’ve checked continuity and the switch is working when pressed. So I suppose the discontinuity is in the trace leading to the left hand switch contact. If that is right, can I solder a jumper from that contact to somewhere to make it good?
Sure you can, howeer, you may first wat to try to repair the trace. First reheat MCU pin26 and EncA_C pins, maybe there is a cold joint. Then check to see if there are breaks in the traces visually. If there are none, scratch the enamel from one of two vias present on this trace, check continuity. If there is non, repair by jumper wire between the pin and the via. If continuity, repeat for the second via. Here’s the highlighted trace: https://www.kvitek.com/tmp/MidiALF_EncoderA_Click.jpg
Oh no… I tried to update the firmware and now I’ve bricked it! I powered on while shorting as above to reproduce the action of encoder A switch and it went into update mode the LEDs came on and then went off and the screen showed white blocks. I sent the .syx file via midi ox, but there was no response from Alf, no progress indication. I left it to complete from midi ox, but nothing happened with Alf. After waiting a few minutes I switched it off and on again and it just shows white block on the top line. I’ve just recently used the same equipment to change the firmware on a midigal, and that worked fine. Any ideas?
No worries, the boot loader is still intact so you can repeat firmware update until it works. Please make sure you are using a decent MIDI interface — most of those cheap MIDI Cable Dongle interfaces cannot handle long sysexes.
Also, set sysex buffer size and count in MidiOX sysex config to 256 and 256, ad delay between sysexes to 250ms … if still does not work, try 1024 and 1024 buffer/count.
Success! Using those settings. Jumper wire installed and the switch is working. Now to try it out. Many thanks for your help.
Bad news, it’s not working right. The sequence is running really fast, like the step is stuck at the fastest rate 64t and the step rate doesn’t change anything. it runs super fast whatever the step is set at. It ran fine on the old firmware, but maybe something has happened with the bricking / repair. Is the old firmware available? I could stick that back on and check it still works ok.
Ok, scratch that – it was running on individual step lengths, I’ve found where to edit them and now it’s running at a normal tempo. It looks like all the saved patterns are set like this (individual step lengths set at 32t. Initializing a pattern works to set the individual step lengths to off “-“.
Update: Inititialising the whole machine, by powering on with the B encoder pressed, got everything to ‘normal’. I don’t know if mine is a unique case, but maybe add a step 6 to the update instructions to initialise the machine.
Sorry for the panic / alert. Everything looks to be OK now.
Now back to exploring the new features….
Hi,
I recently got a 2nd hand MidiAlf.
And I’m trying to upgrade the firmware from v0.93 to v2.3.
But i cannot get into the firmware update mode by pressing and holding EncoderA while turning on the MidiAlf.
It just boots like normal, like it wasn’t pressed at all.
The EncoderA does work, since pressing it after booting triggers the copy sequence function.
Does v0.93 use a different update strategy perhaps?
Any idea why i cant get into the update mode?
Kind regards,
Davd
Chances are that the microcontroller in your MidiALF does not have the boot loader flashed in. Boot loader is a small program that should be present for firmware updates to work, however, it is not required for normal sequencer operation.
Contact me using the email address specified at the ordering page and we’ll figure out what to do.
Great to see this get an update, the variable step length is a fantastic addition, but it seems that the LFO pages have been removed, and it’s no longer possible to select a different scale per step. Any possibility these functions could be reintroduced?
MidiALF is at it’s limit of available program memory, so in order to add new features LFO code had to go. There are lots of other ways to add MIDI LFO in your setup.
What is the use case for a step specific scale setting?