This is going to sound crazy, but I bet if you write in to Elektron they will tell you this is expected behavior. I thought something similar about a possible bug relating to changing delay feedback to above 100 (for example) and trying to reload with FUNC + NO and the delay continuing to feed back; it was so weird that I even convinced myself it was different on the DT1. But no, apparently because the note was triggered that way, only newly triggered tracks will respect the reloaded state parameters - hence why stop/start works or new triggers work.
I’m not saying this is correct or that I like it, but I’d be curious to hear whether Elektron support says basically the same thing to you.
Is it a bug that when I go to a different track it no longer shows me the loaded sample name like it did on the DT? If it’s not a bug, can we make it one and have them fix it?
After setting some p-locks in a pattern, it seems like the trig behavior froze as if I were still holding down a trig in grid mode
So when I press (only) rec or play, it would perform the secondary function (copy, paste trig). The only way I could get back to normal behavior was to power off and back on
Yes seems to be working now for me too. Pretty sure I’ve run into a bug though as it definitely wasn’t working earlier. Can’t even recreate it when I try
I thought I should post here that I was having major issues uploading samples with Transfer, but I got past the issues. When I got it, I merely put it in place of the DY V1, hooked up midi i/o usb (through a hub w/all other Elektron devices) & power that were already in place. I had major issues trying to get more than a couple of samples to transfer at once -computer & DTII restarts aplenty just to get going again… Then I decided to hook it up with the PSU/usb cable sent with the unit, directly into my mac (via usb-a to usb-c adapter). Now it’s transferring without seizing up, but slowly.
Really hoping to be a part of the OB beta testers, as I have a complex system, and I do studio tech & design work (and session engineering), and I feel qualified. This issue is of particular importance to me, as I like to run OB on all possible devices, and I’m interested in why the use of a USB hub (or something connected to it) is causing a transfer issue even though I plugged it into the same hub as my DN, A4 & ST.
The first time I played with the perform kit I instinctively hit func + no, because that’s what I always did on the DT1 to return to normal. It completely wiped the sequence.
I thought it was weird as I had saved that project and I would expect func + no to always return to the last saved state.
I tried to replicate it and the next time all my sounds returned to normal except roughly half an octave lower than they should have. I didn’t try again.
Worth remembering there is a separate place for Transfer 1.8.6 bugs … useful to have that all logged in one place rather that spread throughout this thread ?
As far as I can tell, the usb input is fine, but the line inputs have a -12db reduction on them.
This is something that I hope they fix soon, it’s difficult sampling something that can’t sit in the mix properly (in the context of your music). Of course once it’s sampled, it’s fine.
