Should have read the whole thing. Has been reported before.
itâs working here ⌠but together with midi sync it freezes very often
first itâs working, then after some minutes the midioutput starts to dropout, then DT freezes
1 Like
Donât want to waste anyoneâs time here but this is a long thread so apologies if this has already been covered BUT - Func & Sound browser = +Drive Has No Sounds message every time. In fact whenever I try and access the +drive from anywhere it just says itâs empty. Iâve sampled stuff but thatâs nowhere to be found and Iâve transferred samples from my mac using C6 âThe samples will automatically be transferred to a default directory (if no other is set) âtransfers-yymmddâ that is created in the +Drive storage of the Digitaktâ says the manual - this doesnât exist, where are they? Import/ manage sounds just brings up A:001 /////////////////// etc. Either Iâm being stoopid or this just ainât right.
If you press func+ src followed by func+yes and then keep the func held whilst scrolling, do you still not see anything?.
Func + SRC brings up the 8 Digit sounds; if I keep scrolling using the Level/ Data knob it just reverts to the +Drive Has No Sounds screen.
Did you follow that by pressing func+yes and then hold func whilst using the arrows to navigate. I couldnt fing anything untill I did.
1 Like
Remember, there is a difference between Sounds and Samples.
A Sample is the actual waveform, a Sound is a collection of all the parameters and Sample of what you customized.
You can create your own Sounds by loading a Sample and tweaking it to taste and then hit [FUNC] + Pattern(Imp/Exp).
Export Sound and select a slot. This Sound is now stored in the +Drive that keep whining about being empty.
Add some tags for easy access later.
So the +Drive has no Sounds by default, but the +Drive does have Samples.
4 Likes
Todayâs DT-boot suddenly shows in- and out port (Digitakt in1, Digitakt out1), but I think there is a kind of âcrossoverâ because Cubase offers the out-port instead of an expected in - i.e. midi-clock target.
Are the +Drive-Samples in 1.02 still missing or do I miss something?
Edit: no crossover, seems normal this in/out crossing, didnât realize it yet
Edit2: Hooked the DT to an ESI Midi-USB-device, turned off USB-Input so it runs over MIDI only. For safety I disconnected USB. The result is a quite stable DT. Whereas it chrashes at once on a simple Start-Stop via USB it accepts these commands now, I got 3 Midi-channels running including some CCâs.
The DT doesnât like the slightest change in DAW-setting, i.e. changing a MIDI-channel on an instrument track while itâs running - this freezes the box once the new channel is on.
AHHHHH, scroll left and right with fun held down is yielding results. Cheers
1 Like
Thanks man, getting it now. All good and have to say in the last 10 minutes Iâve figured a few things out I thought were bugs but are actually just quirks. Happy customer.
3 Likes
Samples and Sounds are not the same thing. You can view your samples using the sample manager. You need to export sounds from a pattern to make them available as sounds to be used in other kits / patterns. Samples you transfer should end up in the âincoming folderâ
right now the most stable setup is had by having the dt sent out no midi notes at all. i played with mine as part of a live set for hours last night while it was slaved. no crashes.
1 Like
you like to live dangerously 
1 Like
it can be clocked but there is a bug right now in 1.02 that it canât send midi notes while clocked. if itâs master itâs apparently fine.
found a bug:
when in the Global Mutes Track16/MidiH is muted the Mutes are not stored when powering the machine down and up again - in that case in comes up with all tracks unmuted
bug is reported
Is this pattern mute as well? Do we know if global mutes are supposed to be saved?
the globals mutes a restored nicely (as on all other Elektron machines) - unless Track 16 is muted too
the pattern mutes are not affected , they are working as expected
A little reminder, official bug reporting is to support, it seems they are also checking here too whilst there is a lot of reporting happening, so try to keep the thread limited to bug reports or discussions of previous reports
the more general discussion about stuff just makes this potentially useful thread harder to plough through ⌠and nobody wants to hamper the progress ⌠Iâve just moved scores of posts which had drifted off-topic ⌠that also makes establishing if an issue had been listed before that bit trickier to the casual browser as well as making it harder for 
to spot bug posts
9 Likes
Thatâs very helpful. Iâve been having a difficult time navigating samples.