Arpeggiator questions

[ulrik]

When I have an arpeggiator running, I am able to change any parameters value, num steps, note numbers, velocity, length, well all parameters except "bypass" and "reset" of course, and the arpeggiator updates to the new values without stopping.

But if I script the changes and use the knob.changed() function the arpeggiator stops running, why is that?
And how should I code it so the arp will continue running?

[MikeB]

@ulrik Hi ulrik,

you may remember me - you had worked on a problem for me last year. Your question is the reason why I have interrupted my project until today. My project required the arpeggiator to keep running when changing parameters - or a preset change. It does not. Unfortunately, Christoph has not found a satisfactory solution to the problem.
All of the 12 drum plugins I have like Superior Drummer, Atlas, XO and various Kontaktdrummer are able to create a preset change without stopping the arp or sequencer.
That's frustrating that HISE can't do that.

[DabDab]

@MikeB I am agree with you.

[Matt_SF]

@ulrik I haven't used arps yet. I really don't know but maybe it could work with a transport handler? : when calling knob.changed() you could get the current beat position and make the arp start again from that position?

[ulrik]

@MikeB Of course I remember

Yes it's a pity it will not work, is there a solution to this @Christoph-Hart ?

[ulrik]

@Matt_SF hmm yeah that might be a solution, I'll look in to it thanks!

[Christoph Hart]

@ulrik The proper solution for this is synching the Arpeggiator to the master clock of HISE (which itself can be either free running or be synced to the host). I'm currently implementing this system which allows a much more stable synching for basically all time-synched modules (MidiPlayers, Arppegiators and LFOs), but it's subject to change at the moment and the docs aren't up yet.

[Christoph Hart]

But if I script the changes and use the knob.changed() function the arpeggiator stops running, why is that?

Aside from the user preset loading issue, this sounds funky to me - a normal value change shouldn't reset the arp (unless you call Engine.allNotesOff() or perform a heavyweight task like samplemap loading that causes the sound engine to be suspended.

[MikeB]

This post is deleted!

[MikeB]

@Christoph-Hart @ulrik

I have been waiting for such a function for almost a year.
I would be very happy if it continues here.

Since it works with Juce programmed PlugIns like Atlas or XO it can't be completely impossible - can it?

[MikeB]

@Christoph-Hart Do you have an example for this - When I call a new preset the arp stops.

[DanH]

@Christoph-Hart switching sample maps doesn't stop the arp here actually, although the sound does cut out while the samples load obviously

[ulrik]

@Christoph-Hart yeah, I found the issue (my fault of course )

I accidentally called .changed() on the reset button.

Actually it's working now as I would expect it to, me happy

this is what I'm working on (sequencing different presets after each other, however it's not user presets loaded with the preset browser, but I store them in a panel at the moment, I guess the way @MikeB do it, the preset browser sends AllNoteOff right?)

[Matt_SF]

@ulrik Nice !

[ulrik]

@Matt_SF thanks!

[MikeB]

@ulrik Does this also work if you change the preset in the dropdown at the top while the arp is running?

[ulrik]

@MikeB Yes

[MikeB]

Actually, the Arp only has to run independently of the NoteOn of the keyboard. So it should have its own start and stop button.

This way the Arp could run without reacting to the NoteOff event during a preset change.

Is this not possible?