Digitone issues

have you logged a ticket with elektron?

I had a sound reset to default after a freeze last night. first time.

1 Like

No I go straight to my store who sold it to me, but gonna keep it a bit longer and need to sysex dump my patterns! I noticed before that a sound saved on plusdrive with a lock on has changed!

Looks like a bug, got this phenomen myself two times. Luckily it never freezed.

you have a midi cable connected?

I have no midi connected, just making patterns with headphones, later going to test with MD or Tr8.

Hi!!! … I also had a similar experience
I’ve opened a ticket and now my unit has been repaired (not replaced)
I hope I have been helpful!

cheers :cb_r:

Same LFO problem here, I’ve opened a ticket and they said it’s an hardware fault (user interface board needs to be replaced). Maybe this is the source of (nearly) all your unit problems :slight_smile:

1 Like

Yeah could be, anyway it’ s friday jam night! Going to test a few other things and backup patterns.

If its really jacked, you should just take it to the store you got it at and swap it. Let them deal with sending it back.

But still, make a ticket. That seems like a nasty issue.

1 Like

Got a reply from Elektron within 24h! They asked if I used midi, because otherwise it’s hardware issues, so it’s going back to the dealer! Still need to back up my patterns and sounds. Ah i’m really going to miss this synth. Hope i will get one back that works normal, fingers crossed. So i’m going back to my A4.

2 Likes

Yes, makes sense. It would be weird to set it to 50/50 by default.

Mute modes and a mixer are different things. I don’t understand how that relates to global vs per-track modes, which is apparently the confusing aspect for you.

Correct. Each sound does not have its own instance of effects. There is one set of effects shared by all sounds in a pattern. The sounds only have individual send levels for the shared effects.

2 Likes

I now understand the X and Y as the algoritms are build like that, it’s clear when you look at all of them, was so stupid to not take my time!

Mute modes and mixer is practically the same, a mixer has one function more then mute mode that you can decide how much volume! I prefer fading in and out different synthparts/bassline/etc! I find it difficult with DN to mix different tracks with other gear, it’s either on or off with the mute mode, or I need to set each track vol 0 and … do it like that. A global mute mode applies to all patterns, I get it, etc, think I just wanna have to many features in DN when coming from A4!

@Elektron THANK YOU so much for swapping my broken one for a brand new one! Only did a few hours with the new one, no problems so far, knobs are perfectly, no wobbly or loose feeling, no glitching out of lfo page, no weird behaviour, no freezing when messing with feedback, yeaaaaaaaaaah yiiiiiihaaaa fingers crossed it’s now a good one and let the magic of the elektrons continue…:smiley:

2 Likes

The LFO destination menu is just sensitive encoders. I notice it sometimes. Not related to the engine hardware bug. happens on my rytm mkii and my friend’s A4mkii they have the sensitivity too high need to decrease the velocity sensing methinks. subtle things that they’re getting used to with the new encoders. The thing is some knobs have fewer values and some have tones of values so they seem to scale the encoders function by function which means lots of replicated code is my guess if you find one that doesn’t work they can’t just universally say scale all the encoders down 10% because each one is operating in it’s own scale. there’s some functions on the rytm mkii that blaze through each value in a 1/8th turn even when moved slowly. It can be frustrating but it’s nothing to worry about.

As for the sound browser coming up when doing function moves. double check your Level/Data encoder (just above the function knob) wasn’t bumped by a finger. Function plus that knob will bring up the sound browser window so it’s not out of the realm of possibility that your encoder is sensitive too and it’s sending a false positive for motion while you’re holding FUNC down. easy was would be to just use the hell out of the thing. I found mine did it less and less as you wore the parts in. I had one sticky key too but it broke in after about 2 weeks of heavy use. Glitches seem to be the indicator of hardware faults haven’t had any of that yet but glad to see yours was replaced. :slight_smile:

1 Like

Mine needs to get sent back for freezing as well. So you are not alone.

1 Like

With my new unit I now have a: sometimes jumping value encorder, sometimes it doesn’t move when turning slowly, turning a bit harder it for example jumps from 78 to 80. Bit annoying and weird it only happens within a certain page, haven’t got this with my first unit which had looser, almost wobbly knobs.
Anyone encountered this issue? Think it’s not possible to fix this with an update and that I’ll have to live with that?

Had my first crash with my new machine:
I can narrow the freeze down to using soundlocks I think! I had 3 or 4 tracks with soundlocks (was using it like a 4 track drummachine and plocking some soundsettings per track. Suddenly I had a freeze, couldn’t do anything, had to powercycle again to get out of the freeze, pffffff fucked up shit! Do I really need to send this machine back again? Getting fed up with this behaviour of new Elektrons!!!

What is this freeze/crash? Hardware related or software? I just copied all my patterns, sounds, projects and some demo/free sounds into this new unit. Made a bunch of new patterns and now it freezes again!

Can someone try to make a pattern with soundlocks only? Put soundlocks on every track and let it play for some time… tell me if your machine freezes/crashes?

1 Like

Just curious. Why not return it or send back to Elektron under warranty?

I contacted them and they said it was a software bug and would be resolved shortly- it seems to have been resolved with the latest (overbridge) update (hasn’t happened yet)

Have you had any more problems with this? Just got my machine recently and am searching for possible solutions or what to do about it. It’s happening to me on patterns with sound locks or arp mode on. From what I’ve been seeing, it doesn’t sound like exchanging it will make much of a difference. I really want this to work, let me know if you’ve figured anything else out. Thanks!