Metropolis : Clock and Sync outputs feature suggestion

[Plexusgel]

Hi,

I wanted to bump the Metropolis 1.36 thread but since this version is the official release since February 18 I created a new topic for features that perhaps might come in a new firmware.

It’s essentially about extended control over the Clock and Sync outputs.

Concerning the Clock output, the idea has already been proposed at the time of release 1.36 :

Metropolis 1.36

Bug or feature request - not sure… the current implementation of DI and DO clock division.
Right now, there is a direct dependancy between DI and DO - a higher DI division always resulting in the CLK output slowing as well. Essentially, DI clock rate is passed to DO for further division to CLK output. For me, it would be much more intuitive to have DI and DO working independently (‘in parallel’) to the master clock rate, so that changes to DI leave the CLK output rate unaffected and controlled by DO only.
What I am trying to accomplish, is having a higher CLK out rate (controlled via DO) than the internal sequencer clock rate (controlled via DI). Example: (external) master clock rate set at 160 BPM. Setting DI_4 and DO_2 then results in internal sequencer rate moving at 40 BPM, external CLK output triggering at 80 BPM.
Actually, the manual seems to imply that it works this way, but perhaps that’s just me misreading it?

Feature request - on top of all this! - would be that DI and DO supporting basic multiplication of the BPM master rate instead of only dividing. So: DIx2 in addition to DI_2, etc.
This would be completely awesome, removing the need for an external clock multiplier (or even an external clock generator at all).

I have nothing to add to what Hanz said, I would love to see this feature implemented !

And along with this idea of using Metropolis as an advanced master clock, I wonder if the behavior of the Sync output could be set up to behave independantly from the sequence length.
That would be a simple division of the internal clock : for example Sync generating a trigger every 16 pulses that can be used as a reset for other modules, wether Metropolis plays 8, 16, 32 (etc) pulses before resetting itself internally.
I have been using Sync as a reset signal for drum sequencing modules, but if I want to extend the Metropolis sequence over 2 bars and shift the number of Pulses in Fixed mode from 16 to 32, my reset signal is also divided by two and my drum pattern changes completely. I am using a clock divider just for this reset signal every 16 pulses, I would be glad not to have to.

I’m aware these features represent a significant amount of work, but in my opinion they would lift up the already ace Metropolis to a whole new level !