The definitive feature request & bug fix roadmap

[d.healey]

Bug:

Sample selection issue with merged multi-mics.

Fixed.

[lalalandsynth]

Feature Request:

Playhead sync.

Already there: https://docs.hise.audio/scripting/scripting-api/transporthandler/index.html

[Natan]

Minor Bug 1
Develop Version Won't Remember The Last States Of Parameters Connected To Nodes. "

Minor Bug 2
File_Player's Pitch, Changes Drastically After Reopening The Project.

Minor Bug 3
Not Possible To Script And Connect A Parameter To Nodes With The New Version.

Fixed

[Natan]

Bug Report
By Enabling Audio Loop Player's loop Button And Then Clicking On Hise's Piano Keyboard You Will Get An Instant Crash.
Info: Latest Develop Version

Fixed.

[DanH]

FIX: Parametriq EQ - Node numbering begins at 0 - perhaps better to begin them at "1" for the benefit of the user.

[d.healey]

Feature: Add Message.setPan() function.

Nofix: Unfortunately the HiseEvent class can't be extended with more properties or it will violate the 128bit size requirement...

[MikeB]

Please make the hover colour of the FloatingTile "Keyboard" editable.
the current soft pink does not work at all :-)

[Natan]

Feature Request
setValue Api On Node's, To Connect Knobs With Scripting.

[Lindon]

@d-healey said in The definitive feature request & bug fix roadmap:

Feature: Add Message.setPan() function.

Nofix: Unfortunately the HiseEvent class can't be extended with more properties or it will violate the 128bit size requirement...

@Christoph-Hart - this is a problem - Kontakt 6.6 will extend it's per-note capabilities, and it can already do per-note stuff HISE cant (fade-in for example), so I think we should seriously consider how to get past this problem....

[Christoph Hart]

But you can do fade ins with Synth.addVolumeFade() and the pan can be set with a stereo fx so I don‘t see the need for breaking the 128 bit rule...

[Lindon]

@Christoph-Hart said in The definitive feature request & bug fix roadmap:

But you can do fade ins with Synth.addVolumeFade() and the pan can be set with a stereo fx so I don‘t see the need for breaking the 128 bit rule...

yeah, but no. "VOLUMEFADE" is not the same as note fade in Kontakt - by a long way.

Volume Fade() wants a specific dB as a target - and Note fade_In in Kontakt doesnt - it works out (from the velocity of the inbound note) what to fade in to.

Here's the manual entry:

fade_in(,)
perform a fade-in for a specific note event

the ID number of the note event to be faded in the fade-in time in microseconds

It very difficult, if not near impossible to code a Synth.addVolumeFade() that works consistently and accounts for the note on velocity and accounts for the sound being used at the time... so frankly Synth.addVolumefade() has really limited utility.

Meanwhile StereoFX pan works on all current notes - not specific ones...so tis not a note based solution...

[d.healey]

@Lindon said in The definitive feature request & bug fix roadmap:

it works out (from the velocity of the inbound note)

Are you sure? I always thought is was based on the standard gain of the notes, so you can set the gain manually before doing a fade. Or do you mean it only fades in to the maximum gain limited by a velocity modulator in the amp section?

So far I've been able to recreate all of my Kontakt legato scripts that use fade ins/outs in HISE without noticing any issues, but I'm generally avoiding using velocity to control volume anyway. Looks like I was using change_vol in KSP.

@Christoph-Hart Maybe this discussion should be spun off into a separate thread.

Meanwhile StereoFX pan works on all current notes - not specific ones...so tis not a note based solution...

Seems polyphonic StereoFX + a modulator can be used with multiple notes

HiseSnippet 1088.3oc6W0raaaDDdojXPcaZPRQPQOpC8lQCDsr9gmhs0O1p1JjVT01pWBVStRbcn1Ud4RYS+NzGl9FzGof9BzNKorEEJqiiPiCPP4ABNyryreyO6rCsEbWRXHWfz1XX7LBR6o5NwLoeKeLkg50Fo8L893PIQTNk0dwyvggDOjlVw8ULz1nDJ448udOb.l4RVxBgNgScIGQmRkK4ZuygzfftXOxP5zLqd6c54xYs3A7H.OE0qflgceGdB4MX0xJnizdRGOpjKbjXIIDoUZOtWriO+JV55OgFROOfnHLPNfgRY2kG3oPr5aTKeZfm8s9cHBooauLJTLMJ7R89TO5c7WFMddhfxK0Ha7Pqv8AOirvqRtvyHG3gxftRonC.A2KJ.KWEYpzwBAT9pYpdLIgERkwYSWeVg6KzsoRW+7wagbvKjn9Ti2EI+uUuy3wDW4RvVRu6YOtY5mkBkuQ2gxHImHS.x2mPW9T7bR48ILhPETM92NT9Gk9ye6gdnb1C9PokqD19gBLKbFObEC6PlRGxYpHxRl+RHoqfb4.UVNK+VbrHWQu+0cAmLWcbvxHQR4xtS4QL4JkGEev4jrMGV8TSl0mSmhR+emhD3V7gA2bhfZ1+iabdNTSOcV.oCaNIfCbTX76zaSFiiBj2xc0h79bFelOmQcyVALfHEzISHhrXOWGZWoDtZYImWty.R.AmsZ9G24HnJDKf3DYMiEFO7Xw8ku9A8T3VVcxr7WFc3K9ETG9OhQMxlx0SwxWq6.SWQ3v9q.xSWPVt6YqVxaiyLq0ncNk5A2Ijgwiec4y0AL8opdbMCpO4V7tqPfiuCzK5ojvr7cbM9vHdO5Ld.VnlIwIf5QD1vAw1XIFU32KnWyXqWAOi2T81rE7pp0Gh9vqM3l123KpQYcFco0AcjRyC90iMp0R5MTX4wwWaN9x86TmdZs.g0oWDFaN+PWm5NfpgKnqP2qQruvcdp8Ft0EmUKtyn5Lqp0NdRh82N9l98BrBj8N17BYuqp5.l125JPUyygsdKk8FYAegaN9DvpwUemrmBu26i+IWzzb7vp0pq7m4IqeyFC1pciX.jyshto+tYoSjqd0Hc8f+ZtP+AStLxJW6k3eJ+etxeoK7OvelYwwCDlI1KUd2Q0aqr+3Fp3YrR9vMs+4ycap1eCU7YjBOWzTYeCqiO75S1DhGG2zoVP6JJ4amDup2BDIsZGdPcSfzstiqi+h3cZ9HIekr+GAhpojys9Xy+eFoQ+m0i.MfGIorI8wvMtWC8xdSzTGXBQWBzdfwHAfw00JnlxKkthhNcDQlWBweAOKDZnn0VHz3VgOJ6wTrqf+VXBWofGnZl7UIb.+lk7Sma.+8KPW1.MGGDALz0q7pJnovncu00UcuwOA24juNasF5TcMzY60PmZqgN0WCcZrF5z7d0QMU8tQR9zz6b.F1cRZHqo0gggp2jl4n+FbOMuUC

[d.healey]

Feature request:
Per group volume control.

Done: Sampler.setRRGroupVolume()

[MikeB]

Where did the step size 1 go with the knobs?
There is only 1.0

1.0 == 1 in Javascript world. SNEX => compile error

[MikeB]

Bug?
In the develop-version there is now a look-function
I understand this in a way that you can protect an element in the FrontendPanel against visible moving.
Which is very useful for many elements - as well as in Photoshop or InDesign.
However, this does not work. Despite the lock, I can move the element!

[ustk]

Documentation

Seeing the number of questions we all have concerning building Hise or compiling projects, having a compatibility chart in the documentation would be great.

• OS version
• Processor
• Xcode/VS version
• IPP version
• known DAWs issues maybe... but that would require DAWs version for it to be reliable so...

[d.healey]

@ustk said in The definitive feature request & bug fix roadmap:

Documentation

Seeing the number of questions we all have concerning building Hise or compiling projects, having a compatibility chart in the documentation would be great.

• OS version
• Processor
• Xcode/VS version
• IPP version
• known DAWs issues maybe... but that would require DAWs version for it to be reliable so...

I don't think Christoph should do this, this can be a community job. Maybe make another thread to gather all the info before adding it to the docs.

[ustk]

Feature Request

Add Server.getPendingCalls() API

EDIT: API added, pull request done. Accepted.

[Lindon]

Feature request
Message.isNoteActive(id)

Done: Synth.isArtificialEventActive() - only works with artificial events, but it should cover almost all use cases of this method.

[d.healey]

Feature Set number of times to play loop. A sampler option (probably) that lets us specify the number of times a loop should play before continuing on to the end of the sample (with the option of endless looping of course).

Nah, that's too complicated (plus I think the streaming engine caps away the audio material after the loop point so making this edge case work would be super complicated).