Hi mates, a friend of mine got one this week and comes with firmware 1.10E B on the screen. Is this a beta firmware?
Does it look like this ?
B 1.10E
If it does, the B is irrelevant to the firmware, and 1.10E is new firmware not yet listed on the website, 1.10D is the latest there.
2 Likes
yes i saw the D is the last on the web site. Weird to get it with a newer firmware not listed
Just unboxed mine and was wondering as well.
Hi folks ā
Iām not sure if this is a bug but on Digitone 2 I have noticed that if I hit the āstopā button 3 times, the sequencer kills the send FX on external audio coming into the Digitone (which is good). The issue is, after pressing play, the FX are not present and the only way to get them back is to restart the unit.
Iām using firmware 1.10C
edit: whoops. i already figured out that an easy way to get around this is to just send something from one of the other tracks back through the send FX. problem solved. disregard!
This is not a bug, itās a āfeatureā (donāt ask me the logic behind).
To hear the FX, the usual trick is to set (on a regular audio track) a step that has VOL trig-locked to 0, possibly with trig condition 1st.
3 Likes
thanks ā indeed, that was my issue. I was using the DIgitone MIDI transport send to start the sequencer on a Moog that I had routed back into the DNās FX block. The sequence on the DN was empty, however.
it took me a while to figure out why old projects with all sorts of trigs programmed didnāt have this problem but a new empty project did.
appreciate the explanation!
Yeah this behaviour has always been there on all machines since the analogs I believe
2 Likes
I was going to write up a bug report on the following, where the time between trigs is never consistent, there is a jitter:
But now Iāve recorded the DN2 directly into a DAW and it seems it too suffers from the same clock jitter that the DT2 has, so trigs in the DN2 also never play back exactly in time (for details of how exact see the above thread for tests) So Iām wondering if this is just a fundamental limitation of the hardware of the DT2 and the DN2 as they share the same CPU.
1 Like
Hey,
I have a bug here, iām using the FM drum engine on track 1, mode ADSR, a kick super basic, nothing weird, 1 BAR. I have 5 tracks playing at the same time, unison mode off, and there is voice stealing on track 1, when i mute the others tracks i still have some voice steal during like 4 bars. Even when i stop to play the sequence and i trigger solo the track 1, voice steal. I really have to play it solo for a long time by muting the others tracks for not having this bug. When i turn ON reuse, the glitch disapears. Anyone experienced that ?
Did you set a maximum number of voices for the track, or set track to āmonoā in the track setup?
Another possibility could be that you have long tails = high value for a release or long note duration.
There are chances this is a good old case of user error (weāve all been there).
It is probably because of a small hardware revision change which needs a tiny adjustion in the firmware. Happened before with syntakt and if Iām not mistaking I once bought a DN with firmware 1.40C while 1.40B was the latest version available on the website.
2 Likes
Itās me again, so when i set the play mode of the track in mono, there is no sign of voice steal. But i i just realised by mimic the same kick with the fm tone engine, there is no voice stealing.
So it might come only from the FM DRUM engine.
Have you understood the voice menu?
Yes but do you have something to say concerning this problem ?
If you understand voice settings: you can make sure other tracks donāt interfere with the tracks you are analyzing by allocating e.g. 2 voices to Track 1, in your example above.
I fail to understand this sentence.
Please rephrase it so that you explicitly describe
- the context/settings (e.g. youāve locked 2 voices for your track, ruling out other tracks stealing voices)
- what you see
- what you expect
2 Likes
Digitone 2 ā MIDI settings between patterns are not copied correctly ā
When I copy and paste a pattern that contains sound + MIDI data (only the MIDI channel, no bank/program changes for my Moog Minitaur) into an empty pattern, the sound of my Moog gets completely messed up.
To fix it, I have to enable [PROG] on the MIDI track and manually select ā2ā to get the correct sound back. However, when I reload the new pattern, the sound is broken again.
Really weird behavior. Is this a bug, or am I missing something?
Donāt know if this is a (known) bug or user error, but there seem to be something funky with the LFO tempi.
I have two identical tracks with identical trigs. Theyāre panned to each side. LFO 2 modulates amp volume. However, one track has LFO tempo 1x512 and the other 16x32. Should be the same, but they drift out (both set to trig mode). When I change so both are 16x32, they donāt drift out, and when both are set to 1x512, they go Ā«itās gonna rainĀ». Maybe not the easiest reference, but they go totally out of phase. To me it seems like 1x512 is off (and if thatās correct, I assume more math is off with either the multiplier or the SPD, but havenāt dug into this).
Just had a weird issue, noticed there were a bunch of āphantom trigsā in my sequence after booting.
I definitely didnāt add them, they didnāt play, appeared to have p-locks, but holding down on them shows no p-locks, but holding down on them also enables them to play again, when releasing the p-lock indicator is removed.
Here you can see trig 2 does not play until I hold it down.
You can determine if a trig is a phantom trig by tapping it, if it doesnāt go away it was a phantom trig, if you tap it and it goes away it was a real trig and you lose its settings >_<.
2 Likes