I’m eyeing a used one in my local area but not sure about it, would be interested to hear about this as it’s hard to get nuanced criticism of the device and I’ve never had the opportunity to try it.
Even it’s been like 5 years on the market without announcing a follow up, they should at least consider to open the code for community to extend its sales. Look at Deluge. Community firmware for sure kicked its sales numbers up.
They have said that they won’t do this because of the complexity of the platform. The hardware requires ann old computer and OS to build it, and the complexity to open source just isn’t feasible.
In the manual it says:
The Harmony algorithm transposes notes to create new interesting chord
inversions with the selected scale. Notes are adjusted by 1 tone at each
iterative rotation ‘click’ of the harmony parameter knob. This is a secondary
function and accessed using. Notes in a chord are individually
transposed at each iteration. Notes are selected based on the harmony
algorithm transposing up and transposing down.
In practice when you click up a couple of tones and then click back the same amount you would expect to go back to your starting position, except it doesn’t and the original chord / set of notes you started with are permanently changed.
Also I don’t like the use of the term ‘chord inversion’ as what happens is not what you would expect from a chord inversion (ie: the notes of the chord are incrementally moved up and down octaves). Instead each note is moved up or down by a degree in the scale you’re working in.
I guess this is how Torso expects Harmony to work. Because of this, I never use it which is a shame as I would use it if it worked as I imagine it should. ![]()
That’s kinda aggravating. It looks like a fun device to play with but I don’t know that I want to spend $600 on an experiment.
Don’t get me wrong, the rest of it is really good and it’s easily the fastest and most interesting sequencer out there.
That’s true.
But there are always nerds who don’t see that as a problem.
This is great and I very much appreciate the update. Has anyone been able to get the save project function to actually work? The furthest I’ve gotten is 26% before it’s timed out.
I had this but sold it.
In some ways I miss it.
I feel like the biggest challenge is finding the use case and devices to pair it with.
A lot of devices already have a sequencer that makes sense.
Melodic and polysynths I would rather play with a keyboard.
I was using it with my Model: Cycles but even then there was some mismatch between the T1 and elektron sequencer.
Yes I successfully backed up my current project after the update, without any issue.
Can someone tell me what “Pattern Change Follows Play” means on the change log? As far as i can tell in means that the pattern changes are instantaneous. Which is cool. But I don’t want that all the time. It seems to have gotten rid of the quantize function. Or maybe I never really understood what the quantize function did.
Ok y’all i’m going to be real honest. I just downloaded the old firmware and installed. I’m really disappointed in this. I had really been looking forward to this firmware and I guess I figured since it had been in beta for so long that all the bugs had been worked out. I could never get it to back up my project after several tries. The new bank LEDs were fuckin hideous. And, most importantly the quantize functionality was completely lost. Every time I did a pattern change it would change instantly and be out of sync with the rest of my gear. I guess this is to say that if you updated and are experinceing bugs you are not alone.
I’m surprised by your comment - I don’t seem to be having the same experience with the new fw. Granted the new choice of colours for the banks is odd, but I went back to check and the quantize function seems to be working as usual on my side. I’m not sure to be honest what the new ‘patter change follows play’ behaviour does, but as far as I know quantize isn’t broken. Might be worth reaching out to Torso in your case, especially if the project save function is also misfiring.
Haven’t had a chance to try it, but this sounds like an old feature request, where chained Patterns wouldn’t update to display the current playing pattern.
Popping back on here to say that I reloaded the 2.1.1 and I am now able to get everything to work as advertised. I was able to back up my project no problem which was the biggie for me. I am still having an issue with transport and pattern changes, but I think that’s because I receive clock and trsnsport from my octotrack. Basically every time I turn on the T1, I have to unplug everything, and then change a couple of patterns, and then plug everythning back in and it works. It’s like I’m having to retrain the T1 everytime I turn it on.
That would be nice, bothered me for the longest time.
Can confirm, the view now changes automatically with the pattern, awesome ![]()
That’s really weird because that was never an issue for me. Always seemed to work.
When changing pattern by an external controller via prg chng?
Please can someone help me out with changing the CC numbers it sends from the defaults, I’ve been at this for days, reading the manual, trying things but nothing I try seems to work, it’s the most convoluted frustrating thing I’ve ever done. I just want to change the CC channel of a CC step to 40 (filter cutoff of Virus). I’m running the latest firmware, not sure if the process has been changed and the manual not been updated?
It says to press VB14 and select VB1 as ON and VB2 as off, fine
Then VB15 and set to 4, fine.
Then VB16 and set to 0, however the minimum I can set it to is 1 (first button lit)?