#10

I have tried, and failed, not to get sucked in and speculating on answers.

If you are using Just Friends as an envelope generator then it does not retrigger with a new gate/trigger:; it always plays the envelope in its entirety. When you talk about it ‘lagging’ but being OK past twelve o’clock, then this suggests to me that you are sending triggers too quickly to JF. If you have it past twelve o’clock then the envelopes will be short enough not to have this issue.

Right, that’s the best I can offer: again, try to troubleshoot yourself.

1 Like
#11

you should mult ansible gate outputs to disting trigger inputs instead of going via just friends. can you try that?

#12

Yes as said earlier. I get this problems with „fast“ playing.
Well i need to play slow motion to not get it… i dont think i am such a fast palyer.

#13

Will do right away. Thanks!

#14

also, what mode on disting are you using? and when you say “disting trigger in” which input on disting is it?

#15

That sounds like standard behaviour from the Just Friends envelopes to me; it’s what the module is designed to do. If you put repeated triggers into it, with longer envelope times, it will not respond immediately to the subsequent triggers.

4 Likes
#16

Well i tried… just to remind myself that i get those delayed note reaction if not going through JF.

Precisely: when set up as mentioned above, going through JF, transients above 12, i do not get those trigger issues. Thats why i even do that.

If i skip JF i will have a grid pad or keyboard key playing 2-3 times until its actually changing the sample to its correct one.
Example i play C D# C A#
And it plays back C C C A#

I can get around it by playing controlled slow staccato:D not really a solution.and i still get at least 1 „delayed note“

As i said i am lost here too. It seems a timing and/or Envelope issue.

#17

we need to eliminate all extra variables, it is simply not possible to investigate the issue with multiple factors/modules involved.

let’s start from the beginning. can you describe what mode you are running on disting and what ansible outputs are connected to on disting?

#18

Disting firmware 4.7 mode J6 multi sample (pretty new)
2 distings loaded with the same sd cad content.
Same sample selected (mellotron flute)

As said, gates direct/multed to distings trigger in (x) = problems with delayed selection of samples while playing .

Going through JF as described eleminates that problem for grid, but not really for midi.

Ansible CVs go to disting (y) pitch in.

#19

Since drums as mentioned work much better if i go through JF…

Could this simply be a overload of the Sd/Ram since those instrument samples are 4-8 seconds long each.

Maybe just too heavy load??

Mh no… i get those hiccup triggers with drums too if not through JF. So without the JF method i would be basically screwed actually.

#20

this is likely the issue with either ansible issuing a trigger before the CV is set (so disting is sampling the previous CV) or disting delayed reading of the CV. which explains why delaying triggers via just friends helps.

do you have this issue when using just friends as a sound generator? do you have any other sequencers to try instead of ansbile and see if you’re getting a similar problem?

1 Like
#21

Jf as voice works fine (but not via ansible midi)
No other sequencers no.

Yes i think the issue is somehow connected to exactly that. Some mess with timing of triggers vs cv.

Another reason to love just friends even if it feels like a crazy fix for my problem

#22

i’ll test ansible (in earthsea mode) with oscilloscope tonight to see if there is a delay between trigger and CV.

the midi issue seems to be a separate issue. what happens when you use ansible midi with just friends as the voice?

1 Like
#23

Daaaaaammmmnn… just realized midi couldnt work in this context since ansible midi isnt poly duh. Another confusing variable elemianted

#24

Ansible midi with JF as voice sounded weird. Need to try again. But want to keep things patched as is now to study the present situation more

#25

Btw that is what the disting maker suggested to me but i havent yet found a way to record cv and gate together to wav to send him. The scope should bemuch more precise

#26

i have screenshots and a new version to try.

first i measured the delay between CV and trigger updates when using ansible earthsea:

time1
time1.jpeg914×518 87 KB

it looked like CV updates were delayed by 1-2ms compared to trigger delays. i then measured ansible midi:

time2
time2.jpeg905×267 53.6 KB

which was significantly better, under 0.15ms (you can see it’s actually taking almost as much time for the trigger to reach the peak). which was surprising, so i checked the code and realized the method i used was based on a 3ms timer, while the midi mode called the immediate update method. after i changed earthsea to also use it its update delay also dropped to under 0.15ms:

time3
time3.jpeg869×327 63.4 KB

can you give this version a try and see if it makes a difference? ansible.hex (265.6 KB)

2 Likes
#27

Thank you. Yes that looks good.
So the hex is same as present available firmware but with a delay tweak for the cv recognition to not be behind Tr?

I will loose my saved presets right?
Have to record one melody before flashing.

I dont really get why my midi lag seems worse tough.

#28

the fix is the latest version that includes earthsea with the fix to have CV outputs not being delayed compared to gate outputs.

yes

i’m not sure what you mean. you are seeing a lag between CV and gate outputs when using midi with this new version? or something else? there shouldn’t be any lag when using midi, and this version did not change anything in the midi app.

#29

Not yet flashed this version. Give me a few days.
No i just meant so far (and unlikely to change) contrary to your measures my midi seems lagging more then cv/grid.

So i might look for that issue elsewhere. Maybe trying to power the midi divice externally .