back again - maybe?!

[MikeB]

Hi all,

after not doing anything with HISE for almost 5 months now, I want to slowly work on the project I started last year.

However, one reason why I stopped was that various functions were not available.

So before I jump into the next round, here are a few questions:

1. for my small drum machine, it is important that the arp continues to run without stopping even when changing presets - as well as with all the drumvst I have like this (which is almost all of them).
   Is this possible in the meantime?

2. factory presets should not be able to be overwritten by the user. A user preset should always be created when saving.

3. is it possible in the meantime for the arp to output midi data or at least drag and drop it into the DAW?

4. are the HISE docs reasonably up to date - a lot of new things have been introduced - if you don't keep up with the ball you will miss this info.

[Lindon]

@MikeB said in back again - maybe?!:

Hi all,

after not doing anything with HISE for almost 5 months now, I want to slowly work on the project I started last year.

However, one reason why I stopped was that various functions were not available.

So before I jump into the next round, here are a few questions:

1. for my small drum machine, it is important that the arp continues to run without stopping even when changing presets - as well as with all the drumvst I have like this (which is almost all of them).
   Is this possible in the meantime?

If you dont put your start stop buttons in the presets then this should keep running as theres no status change to the timer callback... but its always been like this, so nothing new there...

2. factory presets should not be able to be overwritten by the user. A user preset should always be created when saving.

We've had pre and post preset save callbacks for a while now - you should make sure the user isnt trying to save a factory preset in the pre- call... but again thats been there a while now...or maybe Im thinking of pre-load and post load - so not so useful. But you can always set your preset to read-only, or build your own preset panel.

3. is it possible in the meantime for the arp to output midi data or at least drag and drop it into the DAW?

You can interrogate your arp controls and build a MIDI file based on it - then save your MIDI file...again been there a long time...

4. are the HISE docs reasonably up to date - a lot of new things have been introduced - if you don't keep up with the ball you will miss this info.

i cant say the HISE documentation has changed much in terms of coverage - some is good some not so good...

[d.healey]

For 2 there is a check box in project preferences to make the presets read only.

[MikeB]

1. that would be a pity - according to CH, the issue of the Arp continuing to run when the preset is changed should have been resolved by September/October 2021?
   That would be the absolute KO criterion for my project.

All drum vsts do NOT send note off commands when changing presets!

Unfortunately, I would then have extended my Patreon with David for nothing.

[d.healey]

@MikeB said in back again - maybe?!:

1. for my small drum machine, it is important that the arp continues to run without stopping even when changing presets - as well as with all the drumvst I have like this (which is almost all of them).

Changing preset will stop the arp playback. You'd need to roll your own solution to get around this.