#117

@expertsleepers asked me to post this (discourse rules are blocking him from posting):

If you’re sequencing the SD Multisample via CV/gate, the gate offset parameter is the first thing to fiddle with. Not relevant for MIDI/i2c use though.

3 Likes
#118

Does anyone know if it’s possible to start up Disting Ex with a preset and mapping pre-loaded as default, rather than the Matrix Mixer? Would be nice to not have to load them manually each time, as I use them a lot.

#119

Yes, there are settings for that.

2 Likes
#120

1.4 firmware has been officially released: https://www.expert-sleepers.co.uk/distingEXfirmwareupdates.html

includes 2 new algos - dream machine and filter bank, and a fix for sd multisample voice allocation, among other things.

9 Likes
#121

Perfect :ok_hand: thank you. I have change for a Sandisk Extreme and all the samples are now played without crackle and noise.

Edit: after few test, the card Extreme not solve the problem.

#122

hello everybody, I tried for the first time to hook up ansible and disting ex via i2c and I experienced a weird behaviour using kria in multisample mode (with some piano sample): ansible and grid see the disting with no issues, but, as soon as I make a sequence, the notes come out super glitchy and noisy. the notes are hearable but under a fair amount digital crackles. this happens also using relly short env time amount. is this a known issue? does anybody experienced something like this? thanks in advance!

Ansible Development and Beta Firmware Discussion
#123

what version of the disting firmware are you on? try updating to the latest (1.4) and see if it fixes it - it sounds like something that was addressed in that version.

#124

thanx for hitting back! :slight_smile:
I’m actually on 1.4 which is the latest one. I tried reflashing it but unfortunately the issue is still there. here’s a short video of what’s happening (sorry for the lowest quality but it just need to let you hear the weirdness :slight_smile:) , hope it helps to solve the problem. thanks again!

1 Like
#125

it’s hard to see but on the bottom line on the disting it should display note allocation. if you notice the noise starting when all 8 notes are allocated, it’s the same issue as before, which i thought was fixed in 1.4

try switching to fixed voice allocation in ansible and see if it fixes it. shorter envelopes can help too. this is very likely a disting problem, not ansible related - you will likely get the same noise if you sequence this sample with CV inputs instead of i2c.

1 Like
#126

here’s another awful video to let you hear the differences between cv connection and i2c connection sequencing. as you can hear using i2c gets thing pretty mayhem :slight_smile:

#127

i can’t tell from the video - can you check in both scenarios if all voices are allocated in each case? the bottom line on the disting ex screen will show allocated notes.

#128

just checked. in both scenarios all voices are allocated. cv plays fine, i2c unfortunately still produces harsh noises while the sequence is playing. no matter what env time, no matter what sound (and it’s relative sample length).

#129

sound like it is a disting bug, not i2c. the difference is likely because gates are not retriggered when using CVs (i2c will always generate a note off before sending a note on).

this is exactly the scenario i ran into - there is a crackling noise when it runs out of voices. for me the bug was only present with certain samples - like long strings.

pinging @expertsleepers

as a workaround for kria specifically i suggest switching to fixed voices mode instead of allocated.

#130

@scanner_darkly @vrcvs
I have exactly the same problem when using i2c via Teletype. Noise and crackling artefacts.

I had the feeling it gets better when

  • not using all eight voices, better 3-4
  • not calling higher voice numbers, like 36 and higher

Bought a new SD card (SanDisk Extreme microSDHC U3) but that didn’t help.

1 Like
#131

I tried using another micro sd (the one suggested on a MW thread about a similar issues experienced by other users) but it didn’t work. The noises persist, some sample set starts working better using 4 voices or less, other longer sample sets need to lower voice number even more. Hopefully os will read and help out to find some solution (if there’s a solution) to this issue :slight_smile:

1 Like
#132

So I’ve been looking at this recently. I don’t really need Swiss army knife of micro utilities. Is there something unique and really useful in the module?

#133

Multi sample mode is the most unique feature on the EX, I’d say. There are videos on YouTube. It’s really very lovely.

#134

Has anyone successfully used the MIDI/CV converter (G7 in dual mode) on the EX? I can’t figure it out for the life of me. I have the midi breakout, and have confirmed that it’s working correctly (by playing samples in the sample player). But in this specific algo, output A is sending out a constant negative voltage that doesn’t change with midi input. Any thoughts?

EDIT: Ok, so, a little progress. It works fine on the left side of the module, and not at all on the right side. Guessing that for whatever reason the breakout is addressing the left hand outputs, but not the right. Is this maybe definable in params somewhere? Will check it out.

SOLUTION:

Thanks @UMCorps!

#135

In dual mode the left side defaults to receive on midi channel 1 and the right to channel 2.

1 Like
#136

I agree with @Byzero about the multisampling.

What totally blew my mind was finding out about the autosample feature. Disting will actually do all the sampling work for you, including multiple velocities and multiple recordings per note! Simply hook it up via midi (or CV) to an external synth (or any other instrument), set up the note range and just watch it doing its thing. It’s absolutely amazing.

After the automatic recording procedure, everything is immediately 100% ready to go and accessible as a new multisample instrument. :exploding_head:

6 Likes