MidiALF and MidiREX firmwares were also updated getting the better internal clock implementation with more accurate swing and tap tempo.
-
Follow
Following
Already have a WordPress.com account? Log in now.
MidiALF and MidiREX firmwares were also updated getting the better internal clock implementation with more accurate swing and tap tempo.
MidiSizer 
Hello, I have here a MidiREX updated to v1.01, and I am not sure if this is something related to the update, but it is not sending MIDI clock at all. NoteOn/Off works, start/stop work. Only tempo is not in sync.
‘MIDI Clk source’ is set to ‘internal’.
Already tried ‘Clk output’ both ‘while running’ and ‘always’, with no difference.
Also tried to init the MidiREX, both from the ‘Init all’ page, and holding 1+3+Sel on startup.
Tested MIDI Out from MidiREX straight to a Volca Keys, and also a Korg NTS-1, both set to accept external clock input. Also checked that both Volca and NTS-1 can get MIDI input and clock from an Arturia Beatstep, so I am sure it is the MidiREX.
Any pointers?
Will check it out today or tomorrow.
I can confirm the issue goes away downgrading to v0.97 and reappears after updating to 1.01. Will stay in 0.97 for now.
Have you considered uploading the source to Github? It would help with troubleshooting.
Firmware version 1.02 fixes problems with output MIDI Clock.
Peter, where can I find 1.02 firmware?
The usual place, MidiREX DIY Resources
Direct ink: https://midisizer.files.wordpress.com/2022/06/midirex_102.zip
Hello Peter! Is posibble to You share 0.97v firmware?
Hello! Just built two midirex and they seem to be pretty cool so far. One I built with a pre-programmed mcu you sent me a while back that has 0.97 firmware the other unit has a chip that I programmed myself with 1.01 firmware. The v1.01 unit will not output a click no matter what I do but it will sound the click note when selecting it on the click page. The v.97 unit outputs the click as it should. Can I download the v.97 firmware anywhere to swap it out for testing? Thanks.
I’ll have a look at 1.01 to see what’s going on with the clock output.
hey, did you look into this yet? If not, can you link me to a v.97 firmware? Thanks.
Hello. Hope I’m in the right place here…(?)
I have a MidiAlf that has been working perfectly in all respects. Turned everything on and the unit is not sending MIDI out when running externally via DAW (Bitwig Studio-latest version). Internal works perfectly when plugged directly into various synths respectively.
However, when I set to external and plug the out port directly to in port of a synth, hit play on the DAW, I get a very strange mash of sound from the synth which then emits a continual buzz when I stop play on the DAW – it seems that the MIDI kind of freezes due to a ‘bad signal’ from MidiAlf. I then have to turn the synth off and on which resets the MIDI ‘freeze’ issue on the synth. This only happens when set to external.
I checked MidiAlf with MIDI-OX, nothing. Then did a full reset and checked out port with MIDI-OX again (also checked via different MIDI ports in both instances) — nothing.
Is there anything I can do to get my beloved Alf to work externally again? 😦
Thanks
Sounds like a classic MIDI loop to me. Check if MIDI events sent by MidiALF are somehow routed back to it.
Thanks for getting back. Indeed it was as you said. Having bought more kit and thus having to add a MIDI expander, MidiAlf wasn’t happy. It is now! Took a while as I also declined to notice config page 3 needs to be set to ‘none’ as am now running through a DAW… DUH!
Cheers and Happy New Year!!
:))
Glad you sorted it out!