The definitive feature request & bug fix roadmap

[DanH]

@d-healey indeed you are right. Better to remove altogether imo :)

I had the exporter pointing to wrong version of HISE, the compiled plugin using develop branch crashes on load

[DanH]

BUG FIX:

Issue when changing sample maps that manages to trigger fx in send / return using routing matrix

EDIT - potentially something to do with Simple Gain module as this can still happen without using the Routing Matrix

https://forum.hise.audio/topic/4370/combo-box-fx-routing-matrix-bug/2

[ustk]

Node Feature
envelope.simple_ar doesn't yet have an external data slot menu.

[MikeB]

BUG AudioLoopPlayer is empty

In my current project, they appear at init through Engine.loadAudioFilesIntoPool();
a sample in the AudioLoopPlayer. Others are loaded via script.

if I open the project with the last develop version
the AudioLoopPlayer is empty
Loading samples via script does not work!

[Natan]

@MikeB You Need To Change The Audiowaveform Index To 0 And It Will Show Up :)

[Lindon]

Feature Request

Its a bit of a pain every time I build a new HISE image to have to go modify the source to account for these so....:

The ability to set (in ProJucer) the text of a couple of dialog boxes:

• audio interface not found:

https://forum.hise.audio/topic/4079/looking-for-audio-interface-not-found-message/2?_=1625066208727

The Samples not found dialog:

https://forum.hise.audio/topic/2006/the-sample-directory-does-not-exist-how-can-i-change-this-text

So can we have a couple of variables like the one for envelope animation...?

[d.healey]

@Lindon Can't those dialogs (including text) be customised with LAF?

[Lindon]

@d-healey - not that I am aware of - they are not in your application - HISE triggers them.

[d.healey]

@Lindon I'll check

[MikeB]

@Natan Which AudioWaveForm index???

[lalalandsynth]

Feature Request

Multiple sources into one Data plotter.
To visualize how modulators combine.

[d.healey]

@Lindon

Looking at the source I can see it's a message window

showMessageWindow("Audio Driver Initialisation Error", message, PresetHandler::IconType::Error);

It should be customisable using this LAF function. However I don't think it will work because the obj provided by the function doesn't have a message property. So I think you should change your feature request to have the message property added to that LAF function's obj.

[ustk]

@Lindon For custom customisations ( ), you can create your own branch and keep your mods into it, that’s what I do.

[lalalandsynth]

Feature request or bug report , not sure.
Fix the convolution volume bug and be able to add a small fade in/out when switching impulses to avoid the bad tick sound when switching.

Also read about hi freq distortion in the convolution module on the forum, please have a look at that :)

[crd]

Feature Request

The granular module in the develop branch is super exciting. It would be great to get a few more parameters available for it. Especially some way to manipulate the envelope of the grains or "smooth" the grains. Adding a way to make some of the grains go an octave up or below the played pitch, similar to Omnisphere's granular engine would be incredible.

[crd]

This post is deleted!

[ustk]

Preferences Option Request

Allow disabling User Presets and Expansions folder creation at init. Not all projects need them.

[d.healey]

@UD-AUDIO said in The definitive feature request & bug fix roadmap:

Feature Request:
Interface Designer 3D <3
(Again exotic, even if it's not realtime)

but:
"...anything that survives this process
can be considered to be implemented at some point" :)

This is already possible, we have OpenGL - https://forum.hise.audio/topic/4187/i-ll-just-leave-this-here?_=1625139400298

[Lindon]

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

@Lindon

Looking at the source I can see it's a message window

showMessageWindow("Audio Driver Initialisation Error", message, PresetHandler::IconType::Error);

It should be customisable using this LAF function. However I don't think it will work because the obj provided by the function doesn't have a message property. So I think you should change your feature request to have the message property added to that LAF function's obj.

not really bothered how it gets implemented....

[Lindon]

This post is deleted!