Midronome Community

Hi :) Thanks for the suggestion! I think this would be difficult, both because it might be specific to your setup but also because even if other people have the same setup they would need a different note so it needs to be configurable somewhere. The easiest workaround is to send the note you want o...

I have been having reliability issues with my Korg SQ-1 when syncing it via analogue to the Midronome. Every now and then, it would jump a few steps and get out of sync. I see - great info! All your ideas seem to be very on point :) Would you mind creating a post about it in the “Midronome Bugs Rep...

Bruno wrote: ↑07 Dec 2023, 16:54 Somehow the advises in the manual from denis dosen`t solve my latency problem, also not with external audio effect.

Wait a few more weeks for Firmware 3.0 - that might solve your issues

Simon

but all the jitter is still happening between the daw and midronome? so the midronome stabilizes it? Well no that's the point, the Midronome uses the audio clock as a reference, so the only jitter it gets is the audio clock's jitter (which is usually very low ) +/- 0.5 samples. When you sync stuff ...

Thanks for reporting! I assume with "plugging the Midronome into the MRCC" you mean using USB - if not please let me know. That's going to be a toughie, and I'm afraid to say it probably is a bug on the MRCC (my first guess is that it cannot handle the multiple USB-MIDI interfaces of the M...

so... a clock taking the route of daw>midronome>hardware is more stable than just daw>hardware? Ha ha that does go against natural judgement indeed :D :lol: The key point is the first line. If I call 1, 2 and 3 the communication lines: daw ---> midronome ---> hardware 1---^ 2---^ daw ---> hardware ...

I understood that as having the need for an additional power plug for the module, for example another USB port.
That will be the case for a big module that uses a lot of power which would be too much to get from the module interface.

Well actually the circuit could not be simpler, the module will simply attach to the current device, no other power supply needed (for now all modules will follow this idea actually). The only difficulty is that MIDI Clock (sent on the Midronome's module interface as well, but it would be the same w...

Hey Tim :) Yes it's definitely planned and will come in a few months hopefully. The modules have been slightly delayed by the coming release of FW 3.0, but they will get there eventually ;) Note that, at first, the modules will only be designs (which will be free), but I will guide you to fabricate ...

In the video and also in the manual it says that „Locked“ only lights up for each bar - in my case its always on. I see - the manual says that the Midronome syncs and the LED lights up after one bar, which is the case in 24P mode (it takes one bar to start the sync). In "2.4.P." mode it s...

Oh I see, it was syncing fine, but you were wondering why the Locked LED was on? Ha my bad I misunderstood :D Well if it's syncing fine then all is good - and yes when it's syncing the Locked LED turns on, to let you know precisely that your Midronome is sync'ed (i.e. "locked") to your DAW...

Hi :) Sorry about the small mistake in the manual - you're correct it needs to be a MIDI track not an audio track. Anyways you've got past that now :) Regarding the current issue: when the Locked LED is on it means the tempo is locked (to the DAW). What happens when you turn the large knob, does the...

Correct

This is the potential roadmap for firmware 4.0. ETA : no ETA for now. New Major Features: Start/Reset for ANLG output - https://forum.midronome.com/viewtopic.php?t=210 Tempo presets - https://forum.midronome.com/viewtopic.php?t=211 Sync to 1-12ppq signal + improved tap tempo - https://forum.midronom...

Hello Vincent, welcome to the community, very glad to have you here!!

Simon

Hi :) So it seems that: The MC6Pro is sending data only to the first USB-MIDI interface (i.e. MIDI Commands), which explains why you can control the Midronome but not get it to forward data (as that would require sending MIDI to the second and third USB-MIDI interfaces) The MC6Pro and the Midi Monit...

Hi :) That setup sounds fine to me - you could also sync the Midronome to Ableton using the plugin and then sync everything else (including the Elektron stuff) to the Midronome via MIDI and/or DIN and/or analog clock. I am not sure why the MIDI Hub is not working the Midronome, that is very strange....

juradub wrote: ↑23 Jan 2024, 21:07 You mentioned there's none in stock, but is there any way i can pre-order, join a waiting list, or pay upfront ahead of the next batch release?

Yes simply join the mailing list (at the bottom of the website www.midronome.com )

Simon

Hi :) Yes it sounds like you figured it all out - looking forward to hearing what the tests show ;) Note that you to send commands to the Midronome from the MC6Pro you will need to send them to the first USB-MIDI input interface (called "Midronome Commands"), and only on channel 12 as you ...

Hi :) If a session in Logic X for example, is running at 118bpm and I want to start the clocks/sync at bar 65 and not bar 1, will it do so? The DAW is the Master Clock yeah? (my eurorack system is a mixture of Din Sync and midi to CV fed into the Squarp Pyramid sequencer). Yes Logic is the master. T...

Oh I see, my bad :) Well my first guess would be that the new Android or BH does not like the multiple MIDI interfaces on the same device, since that audio interface only has one MIDI in and one MIDI out which is much more standard. Just a thought, could you try firmware 2.1 (which is a beta firmwar...

I don't understand, did you test with other USB devices? but I'm not quite sure if the problem comes from BH implementation or Midronome implementation or Android itself. Testing with them will answer that question - if it works then there must be smth different with the Midronome, if not then the p...

Hi :) Well maybe someone else will answer, which would be great to give you another point of view. What I can say, is that sync with DAWs is a complex thing. There are many variables in play, and many things that can go wrong. So as much as I'd love to have one, I think inventing a "one sync bu...

Hi :) Thanks for asking here - I'm assuming you're the one who sent me an email as well. As I wrote in my email, yes I believe it would work fine - I have a Keystep I regularly use for testing and no issues so far. ​ Maybe someone else would answer here, I know quite a few people from the Midronome ...

Interesting thoughts, you're not the first one to ask about it either :D It seems there are no official request about it in the Feature requests forums, so I am moving this topic there. Just FYI, this behavior comes from the very early days of the Midronome, my thoughts were that a masterclock shoul...

That is very strange indeed. Are you sure the only thing which has changed is the Android version? Can you try with other USB devices, for example an audio interface which has some MIDI ports?

Cheers
Simon

Hi! :) Well that's an interesting setup :D Right now the Midronome will not sync to incoming MIDI Clock. If you can, I would generally recommend rearranging the setup and making the Midronome is the master, it can only benefit your setup. The Midronome's master clock is very precise, while if it was...

nobuyoshi wrote: ↑10 Jan 2024, 20:18 This could also be prevented by letting bigger sysex data *only* pass when there´s nothing running, ie the audio input does not receive clicks and the MN´s own transport is on "stop", if I´m not missing anything?

I like that - no extra option and pretty safe for the user

Thanks for posting here. It's an interesting point - my main reason for disabling long sysex messages is because they will for sure disturb the clock. But maybe that's an acceptable behavior, thinking nothing important will be happening while long sysex messages are sent (typically for updates, conf...

Let me add here that a reason for this feature could be the Linn Drum, which requires 48ppq.