Hey so I’m experiencing the same thing. Could you briefly explain what the steps you did to fix this were? I’m sure I won’t be the only one who will have this issue and I’m sure your answer will help me/others.
Thanks
Sorry, which issue?
@Synthetxz
(And anyone else it may concern)
Sounds are not Samples.
Sounds are stored patches from a Track, meaning all parameters from which Sample is being used to the LFO modulation applied. You can save these settings as a Sound to load into any other Track from any Project.
Unfortunately we did not have time to make Factory Sounds, so they will be coming in the next OS version available.
There are however 480 Factory Samples that you may find in the Sample Manager.
Simply press the button with the Cog wheel icon (Global) and select “Samples”, here you will find all the samples on the device.
12 Likes
Other possible bugs:
Could someone confirm?
-
In chromatic mode, steps 1, 4, and 8 are not available. The blue LED doesn’t light up and the notes don’t play. I thought I might have hit some setting by accident, but I loaded the default project that shipped with the unit and it has the same issue on all tracks.
-
I can’t get midi to record either when hitting the keys/pads on the box I’m sequencing or in chromatic mode. I am able to sequence by choosing note per step, but that’s not ideal. I’m not sure if it’s something I’m doing a wrong or if this is a bug.
-
I’m not sure if this is a bug, but the midi notes (e.g. C1, etc) that are supposedly assigned to the pads of my external sampler do not correspond to the midi notes on the chromatic keyboard in Digitakt. I can trigger the sound on my external sampler, but I have to identify and use different notes. It was a real pain to find the notes lol.
The Chromatic mode is laid out like a piano keyboard. Bottom row is white keys, top row is black. So the unlit buttons represent the gaps where there are no black keys.
6 Likes
- works fine … but you know you have to use the realtime-record mode?
- yes there is a 2 Oktave offset … C1 on the DT is C3 in real world
1 Like
- possibly needs auto channel
- c-2 to g8 is also a well established standard for midi notes 0-127
1 Like
Simon,
Thanks for the clarification! So is it normal that if I just turn it on and press play on one of the named patterns there will be no sound until I go into the +drive to assign samples to the patterns?
Also one other quick question just to make sure my unit is fine. In the button test mode in the boot menu when I press the kick button the whole screen is lit up and when I press the snare button the whole screen goes dark. Is this normal behavior?
Please feel free to delete my post if need be.
Thanks. The two octave thing nailed it. F#1 on the SU10 corresponds to F#3 on the Digitakt.
If I have F#3 selected and record in chromatic mode, everything works fine. If I have another root note selected (like F#1), the sounds play back fine in chromatic mode, but doesn’t record the proper notes in the sequencer so it just plays silence. Anyway, with the proper root note selected all works fine. Phew. That took forever to figure out. I hope this helps someone else.
Also, I have no idea what an auto channel is? I see it is set at 14 on the Digitakt in the midi menu, but I don’t see a way to set any kind of auto channel on my external sampler. Guess that’s a problem for another day. I need to get to bed. Lol.
1 Like
The process for loading the preset samples into the patterns. Right now all I have is silence with sequencer data.
Was using it to MIDI sequence another synth and after about an hour the DT froze and I couldn’t do anything.
More specifically: MIDI DIN cable out to JU-06’s MIDI in. Recorded 64 step pattern. Started playing the sequence. Then I selected another track. Hit the stop button a couple of times in a row and it froze.
the AutoChannel is the Channel the DT receives MidiOn for the selected track … the output of the Channel is defined in the Source Page
that is a known bug … I heard they plan a bugfix-release for today
2 Likes
Without wishing to sound rude, that type of bug reporting is good for general anecdotal feedback at best … but it’ll not help you help anybody understand what actually may be behind it … best to provide as much detail about configuration and what you were doing at the time it happened and so on … if you can present a reproducible step by step instruction then all the better
What MIDI/USB/OB connections were there, for instance ! Was the DT slaved !
Just sayin’ otherwise the effort you take to write it down is basically wasted, besides backing up anecdotal reports of a similar nature or confirming something that is already known
1 Like
No problem. I edited it.
1 Like
That sounds potentially different to the freeze bug reported above and the added details can only help bottom it out 
It’s probably worth pointing out to everyone that there are official channels for bug reporting, but I imagine 
folk will be keeping an eye out here in the coming days/weeks … if folk read the reports here and they confirm official ‘we can replicate’ feedback then there’s no need to send again of course
Too soon to know if it’s a bug or faulty hardware.
Anyone else experiencing the record button not flashing when initializing live recording?
Some times the record button doesn’t blink when I use the proper key combo to trigger live recording. But I’m clearly live recording because I can tap in notes or record automation.
I haven’t had this so far
if it’s like other devices, you may have a boot mode which will test elements (like LEDs and OLED etc) and it’ll report any observed hardware faults … iirc, I may have read that issue reported already
1 Like
If I recall from the manual, [FUNC]+[YES] to preview samples uses the Sound of the current track to do the preview. So, if the current track’s settings are highly tuned for another sample (like severe filtering, or very slow attack), you might well get no sound while previewing recordings.