After a 2nd look I do stand corrected 
1 Like
Posted on the wrong thread
Hi Guys,
I just received my new Metropolix yesterday, owning and loving the original Metropolis this new X is more than I expected. Mine has V 1.20 - Have been playing all the functions …and not a hiccup !
Now … A question about the 1.3 firmware update … what type of USB is it needed, also is any type of USB port supported ? … my mac has USB 2 I guess.
USB 2 is great, there is a USB micro connector on the back of the module, you can plug in there, and follow the instructions in the updater app itself for how to load on the firmware. If you’re on windows, you’ll need to install the drivers first, If you have a Mac, it’s a bit simpler.
1 Like
Ok thanks!
Hope I don’t screw up things … this updates are, for me at least, a bit frightening.
Anyway … thanks for the info
Great update!
Not sure if this is a regression, but after updating I can’t seem to be able to reset the sequence when it is not running. Looking in the updated manual, I’m not seeing any new control schemes for doing so. 
example: I have a sequence that runs along with a separate sequence on my drum sequencer (steppy) when experimenting and the rythms get off track with each other I used to just stop the metropolix and hit reset on it and then reset on steppy to get them both back to one, then hit run again. not anymore. 
Hi - sorry for my constant questions regarding Metropolix but I have spent ages trying to search the manual and can’t find an answer to this question.
Is there a way of overriding the gate type per track? I want to set up a simple call and response pattern with two voices. Stages 1 - 4 only trigger voice 1 and stages 5 - 8 only trigger voice 2. The whole sequence plays 1 - 8 but only sends gates to the respective voices.
Ignore that, all you need to do is select “rest” in the gate type mod lane. This has been annoying me for ages not being able to figure that out 
1 Like
It should do the reset when the you start the sequence. It never performs a reset when stopped. Internally resets happen on the next pulse, unless they happen at the exact same time as a pulse.
A couple things to try:
There is an newer option, setting Setup > UI Setup … > Run Button to Run/Stop will handle the reset automatically when you toggle the RUN button, but you can no longer “pause” the sequencer on it’s current pulse.
1 Like
In the Track Menu, you can override the switches with a fixed value per-track.
1 Like
Not sure how I missed that, but works like you said. thanks for the reply!
1 Like
Updated my module to 1.3 and I haven’t spent extensive time with it, but I did notice a bug effecting an old preset. I knew it wasn’t sounding right and after taking a look at the mod lanes I had set up for it, I noticed that the target parameters were all off by one. A mod lane that had originally been modulating Pitch Pre was set to Pitch Post and another that was originally set to Pulse Count was set to Probability. Anyways, just turning the encoder one notch to the right to change the parameter assignment to the next one over solved it, but ostensibly this is going to effect all my presets so if this is actually a widespread behavior, perhaps a patch is in order?
I’ll double check that here, what version did you upgrade from? If it’s an issue, then a patch will fix it. Is it Aux and Ctrl too? or Just Mod Lanes?
Updating from 1.2. I can try to check more thoroughly later, but I did notice that the Ctrl assignment on this particular preset was still intact.
Bug Confirmed, I missed a portion of the preset upgrade routine on the Mod Lanes data. I will put out a release today or tomorrow.
Your existing presets will load properly, no need to re-save everything.
3 Likes
1.3.1.0
- Fixed incorrect Mod Lane assignments when loading presets saved on an older firmware version.
- Fixed when tracks are set to ignore the Global Reset, they should still reset in a Preset Chain or Delayed Load.
- Fixed Factory Reset boot shortcut, it was clearing settings, but not properly setting defaults.
Mac: https://intellijel.com/downloads/firmware/Intellijel_Firmware_Updater_macOS_2021-07-12.zip
Win: https://intellijel.com/downloads/firmware/Intellijel_Firmware_Updater_Windows_2021-07-12.zip
Thanks freqout!
2 Likes
Thanks for the update!
I’ve been attempting to play with the new Preset Chain feature and I’m finding that the chain isn’t being ‘cycled through’ when Metropolix is running (I see a flashing chain link and “1/3” showing at the first preset in the chain). The second preset is never reached and “1/3” continues to show on the first preset indefinitely while Metropolix is running.
I went into each of the presets and defined “Pulses” for both tracks and that didn’t seem to help. I’m using v1.3.1
Any ideas? 
You’ll want to define the “Total Pulses” (SETUP Menu) to define the length of a preset (the Chain will use this value) this is saved with each preset.
There is also a fallback number that is used by the Preset Chains incase Total Pulses is not set.
SETUP > Preset Setup… > Queued Pulses
This value is used when Total Pulses is Empty. The default on modules shipped BEFORE 1.3 is “-” (disabled), so you may need to configure. The new Default is 16.
Great! Thanks for pointing me in the right direction. I now see that I had to edit the “SETUP > Total Pulses” for each individual preset and re-save them before the preset chain would work. Now it’s working beautifully.
And of course I now see this mentioned in the manual: “The length of time for which each preset plays is determined by its Total Pulses value (as set per-preset on the SETUP screen). Specifically, the number of pulses set there will determine the length of 1x playback.”
You CAN go and set all of the Total Pulses, but like i mentioned, you can just set Queued Pulses to a value that will play nice with your presets (16, 32, 64, whatever) and it will use that value when Total Pulses is empty.
2 Likes