Sounds positive, if confirmed.
Perhaps Battlestar Galactica 2004-2009 complete. 
That beta firmware was released as version 1.01A.
Dang…well the crackles are still happening.!! Oh well
Damn, was trying to fix something and have reformatted the +drive but forgot it would erase all the factory stuff too and haven’t got it backed up! Does anyone know if it is available anywhere like the OT stuff was/is?
I’m fairly sure one of the factory reset options will restore that for you.
1 Like
You can restore the factory content by holding FUNC while powering on, then choosing 3 from the menu. Ask me how I know: I’m about to do it for the third time 
1 Like
Thank you both of you!
If i want to rename a Sample, it says “Error”. What iam doing wrong? Or is this a (maybe already mentioned) bug?
I even tried to erase it from the RAM and rename it in the Drive, but got the same result.
1 Like
Pretty sure I hit that one. I renamed it via transfer instead. But … yes, a bug.
1 Like
OK, so I have completed a few band rehearsals with the DTII and have experienced a few bugs or weird behavior. Curious if anyone else can reproduce and confirm these or maybe comment on what I am doing wrong.
Perform mode kit reload
- Activate “Perform” mode
- Tweak sounds
- PROBLEM: FUNC+NO should now (in my opinion) take all sounds back to the state they were in when Perform-mode was activated, which makes the most sense from a performance perspective. But instead, it just loads garbled versions of all the sounds, not even close to either the Perform-state nor the underlying pattern sounds.
- WORKAROUND: I can work around this by pressing FUNC+YES immediately after activating Perform-mode so I have a saved state to go back to, but this should not have been necessary and is not logical from a usability perspective (IMHO).
Song mode mutes
- Activate song mode
- Change view to purple pattern mutes
- Do some mutes and unmutes with and without “prep mutes”. Tweak some sounds, FUNC+NO and do some more mutes.
- PROBLEM: Mute lights and actual mute states are very inconsistent. Sometimes the lights change but not the mute states, and vice verse. Sometimes I have to tap a trig three times for the light to actually change, sometimes the track makes sound but no light, sometimes light but no sound.
- THOUGHTS: I faintly recall that this occasionally was a problem on both my ST at DT as well after song mode was launched.
Double-triggering
- Activate mute mode (either)
- Mute and unmute all trigs repeatedly.
- PROBLEM: A few select trigs occasionally double-fire. In mute mode you can see this very easily as the trig mute lights appears not to change (it goes off and on again extremely quickly). You can also see this if you have p-locks on a trig, and the p-locks suddenly disappear when you hold the trig to check or adjust p-locked values. What happens is that the double-firing is causing the trig to first be removed and then immediately re-activated but now without any p-locks.
- THOUGHTS: This might be a hardware issue. But I suspect this is more common than people realize? I have had this exact same problem on TWO of my previous Elektron machines (DN & DK), and on my new DTII it affects 1-2 trigs often (every 5th press) and 3-4 trigs sometimes (every 10th-20th or so press). Extremely annoying when I loose p-locks all the time, and when my mutes aren’t tight during performance…
Mentioned already a few times in this thread but it’s still useful to officially report this to Elektron as a bug.
2 Likes
I do wonder when Elektron are going to release the bug fixes for the large number of issues this unit and the latest Transfer version has 
6 Likes
Im guessing they are beavering away at it since some seem pretty major
5 Likes
For the first issue why not just switch back from Perform Mode? I thought everything was supposed to revert.
True, but it will then revert to the sounds on the active pattern, and not to the sounds on the starting pattern where you brought your “perform kit” sounds from. The whole point of perform mode is to bring changes you have made to your sounds to the next pattern in your performance as a B-section of a song with the same sounds, as far as I understand?
FUNC+NO should reset all sounds to the last temp save (your latest FUNC+YES). But in perform mode, that does not happen. It doesn’t reset to the pattern temp save NOR to the perform kit starting point (which should also be treated as a temp save state to revert back to in my opinion).
Maybe not a bug per se, maybe by design, but I think Elektron could improve this aspect usability wise, because now it makes no sense.
1 Like
it’s func & perform button to revert to original kit, no? rather than func & no.
func & no is to reload temp save state.
Yes. But I don’t want to revert to the original kit. I want to revert to the perform kit as it was when it was activated. Now, it does neither. Just gibberish sounds.
gotcha. weird indeed.
I encounter this bug with 1.01.A:
- Loop a sample continuously with forward-loop.
- Set a “1st” conditional trigger to play the loop.
- Temp save the pattern with Func+Yes.
- Change a few params.
- Reload saved state with Func+No.
Actual: The pattern is played back with the state from step 4.
Workaround: Save the patten on a new slot and switch the pattern. Alternatively, just stop the sequencer and start again.