DT bug reports - OS 1.02

i checked … no it doesn’t light up … it gets just a bit brighter … and as i said, what sense would it make if it lights up while you press it?

after making my DT master sync controlling MD, MnM and micromonsta i am having no crashes. crashed constantly when DT was slave.

also my FUNC button only gets a bit brighter as well

not sure if this is a bug or i’m doing something wrong…

i have my micromonsta on DT midi A, playing a long sweeping pad chord. when i stick to a single pattern the sound is played constantly, there is no note off. when i switch between patterns 1 and 2 with the same chord in the same place on both the sound cuts out then starts again when the note is triggered

anyone else get this?

Wel because the others did, i figured this one would as well.

@Ess Sorry to bother but any chance you guys could give us some info on what’s going on?
We’re not evil :smiley: we just want to be kept in the loop as in many cases return timeframes are crawling and it can get nervous while trying to figure out what to do.
Mine is not even here yet but considering when first people started posting it would be nice to know what’s up.

Thank you in advance.

2 Likes

We’re currently working on fixing the MIDI-related freezing issue. OS update coming very soon.

The best way to know is to simply contact us via either a support ticket or through the contact form on our website. There is a lot on my table, and Elektronauts is not officially part of my job - so that’s why I haven’t been posting here much lately.

EDIT: Oh, and - sample loading issues have been solved.
A few interface improvements, and some workflow enhancements as well.

32 Likes

thank you! appreciate you taking a moment!

No problem at all!
I’m fine with answering here, it’s just difficult to find the time to read posts at the moment.

7 Likes

Update and status info is super appreciated – thank you for that.

1 Like

Thx so much for the info.

1 Like

Thank you for the Info. Much appreciated!

1 Like

Not sure if this is a bug or just something that has to be worked around but reloading the pattern with func+no does not reset any feedback that is audible, the dials reset but the noise carries on. At times it sounds like other fx parameters carry over too spoiling the reload feature in some instances, I am yet to hear any leftovers from the non function based parameters.

seems very similar to the post a few minutes before yours.
probably posted while you were typing yours in.

Thats the way aha aha I like it aha aha :notes:

Hi Simon,
did you manage to fix the FX settings reload bug (Screen recalls correct values, but it doesn’t)?
Thanks for the update anyway, looking forward to it!

Exciting

1 Like

I really hope to somehow browse my samples through the “+drive sound browser” thats pretty much my only issue with the device right now. midi sync is very important but im still learning my unit before i let it play with my other toys. Great device! Having tons of fun with it so far. Thanks so much for all your hard work! :slight_smile:

That makes sense as i always have those moments where im like “oh this sounds great for another track” lol. Perhaps if we could access both through the ‘sound browser’ seems logical like i said to have a centralized place for all your sounds

1 Like

Can’t hear preview of sampled waveform if internal tracks are muted.

Sample something in
Edit length etc but if you use func + yes it’ll be silent if things are muted.

Expected , I can hear it.

1 Like

I’m seeing strange behaviour with LFO depths.
Sample start set to 60, Length 10 and LFO depths of around 30 take me way off the end of the sample into buzz/pitch increase territory in the positive cycle and doesn’t reach low enough towards beginning of sample in the negative cycle.

It’s as if the LFO depths don’t correspond to actual 0-120 in sample length but there’s no detail in the manual I think? And this makes sense as LFO range is +63-64.

So maybe not a bug just a detail missing in manual ?

1 Like