amazing.
I might have to invest in one of these.
amazing.
I might have to invest in one of these.
I’m trying to sync the keystep with TV in the following way: TV sends clock to keystep. Keystep sends midi notes (no clock) to tonverk. Tonverk is receiving the midi notes but apparently not sending out the clock.
Have I been too naive again expecting this would work?
Did you check page 70, 71 manual?
Yes, I did
Edit: rebooting helped
The melty face is the Drop so we are talking about the same parameter ![]()
Yes, I had drop and freeze mixed up in my head.
I was testing it a bit yesterday and found it to be quite ok to use on strings and pads or sustained sounds but doesn’t work at all with drums or stabs etc. But still would probably be useful to make it less sensitive.
Yes, and a bit of attack and decay would be nice. For me it is unusable as is.
ok so honeymoon period is over, the annoying bits that i initially glossed over because of all the exciting new stuff are starting to get on my nerves.
i’m also a little concerned that they’re going to be hesitant to change/replace/remove stuff to maintain backwards compatibility. i feel like numerous existing parts of this machine just aren’t finished or feel off design-wise, and i’d rather have elektron do bold and disruptive changes to the entire machine if it makes for a better UX rather than just adding new features on top of what we have.
Anyone already tried to backup a project and reimport it? Could I just copy a project onto a new tonverk without having missing samples or anything like that
I did backed up projects, but I haven’t tried restoring them.
Considering the size of the project folders, I assume they don’t contain any samples, so the best way of backing up would be with the same folder structure for samples.
TBH, I miss the way DT handles this.
simple things like trying to parameter lock a retrig rate are sometimes maddeningly close to impossible
Hi there, waiting for my Tonverk to arrive.
Question: is it possible to trigger individual subtracks from an external sequencer? They obviously share the same MIDI CHANNEL but are they mapped to notes in some lower octave like Digitakt multi map?
User case: OXI ONE Mk2 with Multitrack sequencer triggering the SUBTRACK.
Sorry if it has already been asked (would be incredible if it hadn’t) but I tried to use the search function on the forum but I did not find any result.
yes
Thank you, which octave is it? C0?
C5 I think
Edit: deleted my post since I misunderstood your question. In the manual they describe how to access subtracks over MIDI, they each have a note and you would use NRPNs for individual subtrack parameters.
Now that I’ve had the TV for a month, I thought I’d chime in with things I personally find really hard to swallow about the TV’s current state & are stopping me from being able to rely on it / recommend it 100% (like I would my ST/DN2 and with a few asterisks the AHFX) – hope people who are in the process of making The Decision find it useful.
Side note – I really like the TV overall. Could’ve returned it for a full refund but it never crossed my mind. It’s ambitious, a super exciting new direction for Elektron and the identity of the instrument seems to be more clearly defined w/ each coming update. Just saying that to avoid triggering the “entitled” police.
Anyway, here goes, sorted by my own level of frustration with particular issue.
Save/Load workflow
I’m sure this will be addressed at some point somehow but it’s just baffling to me how restrictive the TV is when it comes to experimenting with patterns / kits & being able to come back to previous states.
At the moment if you want to fuck around with a pattern, you have to Func+Memorize first. If you Func+Recall without step 1, nothing happens. Sometimes when you Func+Memorize and then load a different machine / FX, the Memorized state disappears and you have to reload the entire project to go back. In fact, whenever you want to reload anything and either fail to Memorize or Memorize fails you, you have to reload the whole project. Gah.
(I have literally zero interest in the current Perform mode for experimentation as you can’t save the state if you get to an interesting point. Also audio dropouts occur when exiting it on busy patterns.)
TV also doesn’t have:
Bare minimum going forward:
Ideally:
“Oh but the A4/OT/ whatever doesn’t have reload” sure, but kits. “The ST doesn’t have kits” sure, but paste pattern with kit, reload sequence from og pattern, done. Every single Elektron has ways to demolish a pattern & then go back w/o having to reload a project that can take ages to load
… Pls @Elektron let’s change this ![]()
Perform mode & so on
This is just a wishlist thing, but super strong one. A proper A4/AR/OT performance macros mode would 10x this device in my eyes. I refuse to believe the TV has a dedicated Perform button to only ever have the current iteration of Perform mode (which to me personally feels a bit meh and overlaps with func+memorize & func+recall a lot). I think they just wanted to avoid a Torso S4 “this button will start to function at some point” situation so they put in something that’s at least partially useful for some folks but the real Perform mode is in the works.
You can rely on modwheel macros but quite a few parameters can’t be mapped to that & it is obviously cumbersome.
Hanging notes
There’s a lot of weird midi stuff happening. Sometimes a note gets triggered despite nothing being sent to that channel. Notes hang quite a lot. Hoping for a proper cleanup here… Tested with and without Midihub in the middle.
Ghost parameter changes
It’s been reported by other users that the TV changes its parameters on its own. If you for instance have the Degrader FX on main, FREZ can go from 0 to 1 which then engages the freeze effect randomly without you touching anything. Meh.
Bugs
There’s less of them than I thought there’d be (started on 1.2.0) but there’s still plenty. Had just one or two freezes but tons of very iffy behavior with (mostly) sample/preset management.
The “Nice to have” stuff:
Sorry for the length of this thing, again – love mine, hopefully someone finds this useful.
Edit: Massive +1 to this:
Glad you penned this. For some who haven’t gone as deep into the device, these reports act as a compass for issues to look out for.
And for issues we’ve encountered, it does add some consolation. It’s definitely in better shape than before. But still has to get some of the basics right.
Since it’s wednesday today and an update might happen in the near future. I really hope we get boring bug fixes and qol improvements and less hype-features