Ok great. I feel the Pulse Count Mod Lane will prove an invaluable tool with the goal of “freezing” the switch settings on one track in order to move to the other and start fresh. 
You can set them to a fixed value per-track in the track menu, modulation would still apply, this might make it easier to separate, but as you add and modulate pulse counts, the alignment of your mod lanes may go off script a bit; can always sync the lengths with LEN>PULSES.
The Tracks are meant to work together by design, but it’s always interesting to see what people do to make them more independent. At a bare minimum, it make you more thoughtful of the ideas you put into making a sequence and what makes each one so special 
.
I’ve always found the discovery of what is happening on track 2 to be so awesome. Get a groove on Track one, and there is a variation waiting to be found on track 2. Track Out Swap becomes really fun in this scenario as you don’t need another voice to discover it.
I haven’t used Mx in this way yet really but I can totally see where you’re coming from! I’ll definitely give it a try soon.
I have a feeling you guys are close to releasing a new firmware, and I wanted to make one more suggestion: different colored lights for save and load (probably keep red for save). One time I was in save when I thought I was in load and I accidentally saved over a preexisting preset thinking I was simply activating it. Also, having Mx stay in “Load” after loading a preset is brilliant for its use performing live, but would it be counterintuitive if it “exited” save mode after every time you save to one preset? (The way it is now allows you to easily save the same preset to more than one slot but not sure how valuable that is.) This would also cut down on potential mistakes saving incorrectly to the wrong slot. But different-colored LEDs for load would help a ton.
EDIT: Now realizing each bank is a different color…not sure how I would deal with that!
1 Like
I’ve accidentally saved over patterns before! It is easy to get mixed up in the heat of the moment.
Maybe the stage LEDs could flash when you are in save mode. Maybe also it could auto-exit save mode once you make a save. 99% of the time I only want to do one save at a time, unless i’m trying to re-arrange the order of the saves in a bank to correspond to a progression in a performance.
Generally though, I can’t think of much of a reason that I’d want to stay in save mode, whereas load mode is something I use while performing to queue parts up.
1 Like
Yeah. The only time I have found staying in Save mode being helpful was one time where I knew I wanted to take my basic preset and make changes to it in two new separate presets, so I just pressed the buttons for those two new preset slots consecutively. But I’m pretty sure I’d rather have the failsafe of not saving over something accidentally by having it exit Save mode after a single save.
I’m struggling a little making good musical transpositions of Metropolix using Tete and Tetrapad.
Currently, i have a sequence running on Metropolix in D Pentatonic, I’ve set Tete to Notes mode and set the scale on Tete to Pentatonic too, and I’ve got one of the note outs from Tetrapad going into the X in on Metropolix and X is set to ROOT to transpose the pattern.
I’m not getting very musical results, and thought there might be a better way to do this.
Intellijel, what would you recommend for settings on Metropolix and Tete to do this so it’s still sounds harmonically correct when it changes.
Would it be better to config X to one of the Pitch options instead of ROOT? Or using a different mode on Tete?
Some ideas would be very welcome here.
Using Pitch Pre will always be diatonic (in scale). Modulating Root, Pitch Post, Pitch Offset, may all knock your sequence “out of key” depending on the usage.
Pitch Pre/Post, Root are all chromatically quantized. So the source does not have to be, but it can (Like Notes Mode on Tetrapad). You can use the attenuators at full to match your source, but you can dial them back to taste.
2 Likes
I’ll look at some tweaks to the Presets UI, won’t make it to the next release, but maybe the one after.
1 Like
Fantastic, thank you. This is great advice, will try it out later on.
So the “pre” in pitch pre is pre-scale quantisation basically? it lets you adjust the pitch BEFORE it gets quantised by Metropolix?
yep, from the manual, p126 for Pitch Pre…
Positive voltages increase the pitch of all stages on the destination track(s) prior to quantization. This means the pitch changes will also be quantized, and all pitch outputs will conform to the selected scale. Negative voltages decrease the pre-quantization pitch values.
1 Like
Want to thank everyone here for their feedback as well, it all contributes to a better Metropolix. 
4 Likes
I’d love the Metropolix to have the option to force start on the One.
I find myself using the reset input a lot when sequences go a little wild but in use Metropolix also wants me to send a reset on the One to get it started in sync properly. I know I could feed my master reset and random resets via an OR logic path but yeah, allowing the module to do it on it’s own when stopped and restarted would be super useful and save an OR.
X
There is a new option to automatically reset when using the run button in 1.1.0.1:
New Global setting for Run Btn: Run/Pause (Original/Default) | Run/Stop.
But as far as other modules resetting the Metro, there is a couple ways with the reset input, you can use it in Run mode and when the Reset jack goes high, Metro will reset and start running, stop when it goes low; or in reset mode, the reset just needs to come before or with the clock pulse, because we can’t bend time yet ;). If metro gets a clock, it’s going to advance, and the timing needs to be tight.
There is not really a reliable way to auto detect when the clock stops, since it could just be a slow down in tempo, or intended behaviour from the user.
But i might be missing what your request is.
EDIT: you can also just passively mult 2 reset sources together and patch them into reset, don’t really need an or module for that. Using a stackable or intellijel hub.
1 Like
Just played around with the new firmware for the first time last night. Really great… it expands the possibilities of the accumulator in some really cool ways.
Now that we have all these chords available in the scales menu, it would be rad if there was a way to modulate scale/chord and if that’s something you’re planning on doing in the future, I think it would be really helpful to be able to see which scale the modulation ends up targeting as it would otherwise be really tricky to set up some mod lanes to make a chord progression just doing it by ear and incrementing through that list
once again, my metropolix is a bit ahead of yours 
4 Likes
Correct me if I’m wrong, but does Play Order > Shuffle only work when LEN > Pulses = Auto? Can’t seem to wrap my head around that one…?
EDIT: Ok I think I’m understanding this a little more. If Pulses is not “Auto”, then the shuffle will reset at the end of every pulse count for the sequence. So if LEN > Stages = 8 and Pulses = 8, for example, it appears to not be shuffling because shuffle is resetting before it even gets a chance to loop. In this case, setting LEN > Pulses = 32 lets the shuffled pattern repeat four times before it changes again.
I’ve had trouble doing this in the past where it didn’t work as expected - not sure why. I’ll give it a try though.
Yeah, I understand the unknown of when is a clock stopped vs. a paused / slowed down state - which I guess is why I thought it might be good as an option that can be enabled or disabled. I would think maybe 0.5 seconds? I have a DOT by DNIPRO and it has this behaviour - I find it useful as it saves me a reset cable and source.
