1.1.0 - after recording a sample the box offers to assign it to a track for you, yet it doesn’t really. If you choose a track, it will say that A107 (or whatever the next blank slot is) is assigned to the track, but the new sample never gets copied into the project. It seems like it should. I then manually add it to that slot and all is well. I’m guessing this may be somewhere in this thread but I didn’t see it on a search so posting here just in case.
1.1.0 - Muting a bus doesn’t mute the audio coming through the bus. If you lower the volume of the bus, it does, however. It would be nice if the muting of a bus actually muted the audio coming through it as well.
Example: Audio in AB to Bus 4 - muting bus 4 and the audio still plays from the AB input.
I’m having problems in using the USB Midi from Ableton, the device keeps disconnect from it and at the moment I’m using a good old USB to Midi Din cable , is this a bug?
I don’t disagree with that but then there seems to be no way to instantly “turn the volume to zero” on a bus - I shouldn’t say there is no way - it’s an elektron box, there is likely another way.
However, I do think this should be an option to allow the mute (or func-mute) to mute it more like a real bus on a mixer might work.
I have the drop connected via midi and when I stack NRPN messages in slots any med-fast modulations cause the elektron sequencer to glitch. Have you run into this?
Not that exactly but I haven’t got into NPRN only CC so far. my main issue was slow saving but that appears to be resolved now. I hooked it up to TV again at the weekend and it was much better. I’ll probably start pushing it a bit harder now and run into that.
I keep meaning to log the issue properly but im lazy.
After 1.1.0 update this noise became even louder with empty disconnected inputs.
It really sed, I’m using TV with iPad via usb, but can’t disable analog inputs because they paired with usb input.
The left arrow issue seemed to have resolved itself for me, but I am indeed noticing some LED issues elsewhere. Looks like maybe more of a software issue than a hardware one, which is a relief.
Funny, because I just resolved a hardware LED issue on one of my Octatracks.
My 1 trig issue is still there. Different patterns, tracks and projects. I agree it’s more than likely a software issue though, so for me very pale cyan means a trig, slightly brighter cyan means no trig, until it’s patched out.
Oof My tonverk just completely reset in the middle of playing.
Sequence was playing back, i was treaking the lpf fx on a bus and then poof whole project completely reset, everything emptied.
Had to reload a previous save and I’m sad to report that the magical sweet spot i had going is lost
No and I don’t understand why ? The same for track mutes… i wonder why this simple functions on the digis are not implemented on Tonverk… Very frustating…
So bug reports or feature requests😁?