The definitive feature request & bug fix roadmap

[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!

[d.healey]

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

BUG REPORT - nasty one....

Set up multiple samplers with the same sample map loaded into each....

-set one and only one sampler to play in reverse.... they all play in reverse...

Reverse Sampler Behavior – Identical sample maps in two samplers will both be reversed

Hello all, Currently, I have 8 samplers which can be tweaked individually in the interface (i.e. you can pitch one sampler up, filter another, pan another, e...

Forum (forum.hise.audio)

[DanH]

FEATURE REQUEST: Audio Looper - ability to set custom loop points, rather than the whole selection looping (similar to the sampler really).

Also being able to change the start/end point in real time with the mouse - currently it snaps back to origin point if you play the sample and move the points with the mouse at the same time

And while I'm at it loop direction too please :grinning_squinting_face:

[Lindon]

This post is deleted!

[MikeB]

The same project

Open in Master Branch

Open in Develop

SOLVED!

Because all values in the develop version are floating point now, an integer calculation of slider values is
of slider values is only possible with "parseInt".

In this example the sample folder is called "Kit9" the 9 is now displayed as 9.0.
and therefore no longer found. Only with parseInt(value) it becomes 9 again.

[MikeB]

@DanH Do you mean something like this?

HiseSnippet 1370.3oc4W8zaaTDEe13Ls0tXDUsHg3zpHN3HURV25VpDBwl33fhnI0Jts.WvLY2w1ix5YVs6roMTEQ4FW36PuwU9nzK8i.24Bmg2L6Zuy1r1I0ofPf6gz4Mu+7ad+e6FI7nwwhHjU0GdbHEY8N3dGykiZOhv3nc1BYcc78EhvdALOZTeGm0FwBQadbHINl5irrp7EJFsptLR+62+7MIADtGMmDB8XAH78YiYxbpgteIKHXahO8grwFb2xcGOAusHPj.fpB1AER7NjLjtGQw1RXj0k53yjhndRhjFirVdSg+w8FIdBOk+GyhYGDPUGZh5AJJk71h.eEhUTQsGwB76N4wGiPV3t4thJothaf2k4ylRO2k7d5KrykvzeXsz7fWSS34TJ7bJCdVFva4T3cMbOuHVnL+FE1tJdGtjFMf.g.SXkxKZoWUA2V.bvkqMlbHc6H3vTIZbWGmaZeGGmU+z50pWCBDwR6iHQ1pT.Zj8mYqSNVaHUtQhOSziLNLfNE.MVIkuUThm9eWKlJS4ZeBeHsAn96cuacZCzg6CZeBx.82VLNTvgCMVAtSqwbtAeajbl7quckTKv3ALN0dPB2SxDbaAGzlRrHQPCuIxbSPqAIzUqW6Y0qUsbjq0pxROVwZiUmHCXlSzlZNfWoqLi1lDDb.jQ2vDIyBqZatPnUywMUtUCHeVXMywUNZMwRJdS+WdTI.PxLCJpKWYhbm9kptd9Oz50ry9k+h2PJiXGjHoMxno9SGNApu7MhOy+UmhrxezFvRoHC.umPRe.uwp0dVsp0Nol8qe0fAkdWlxBnQkdspWXz7DrAOY7AznIOtILBMEJ10AO6tNlME8R8HFLJ36vYxGDR4ypUIJyMBckVNCUPOYotmz6m0SR2c3qHGQGHhFiX9pdlEn0Doe.lSIhTIt5rL.9V+7Uyn.ovpy+5iPnArfrw.svq+nXZT75iId9zinAhv02hFenD9aqa2W2kpe69Ns52qa+VsZs1SHGkBbMZqjh12MCsvvMeZjFlWFmhfhn6C+E2yivXrBrEEM3UyVzMSjRAWK5kvpTsS6TPOZmsHRhZBPlaGBEPltjohxVaQOBFslNOnJNyCniKYo2vK5MNx7zb.zw83oGd91tgSRC1Aj6J3zhNzSX9xQSYy8D2QT1vQ4y5c+VkKXJftzY57M.vdF.36BbikzvdrumZtvwXxT9e9O8aEL0kOiPUtgdYnggdw3xMj4hNeiaA69GErK9rhy4F9ELCCGl3JoOETPcsu09A70gFIHzoG9CqfH7SBHxh6knVFK6BnsQgE.TC44wL4wlOoK7xJk1f3bB2qg6xjdiJGuKUBdgpf+twa1pe0wcFLf5IyA6x3s+52t64cVP45Sfht7LqVSAkoEdydM7W91eMbnmpGDpJTQnieOLBlUx3CMMkwbXSx6KDR0zwbZccS2ZQW3Cpu.2Pi8n3hZX6K1H.cIb5vEc4a5bEUI4zAO5l1Z3qm67C+Hj0U4bGpad9Woe4+07EGWjh3KdOmJmO3dFeTT0IXrGSkO0gqyHnYMZ1hNfjDHmR0Dj6J3hvQBNyqXxGrZ4vgzHSnW56AVBEJ.xobC28oATRrQV9G4deXeWRzqW+7F3JZd9cEyKb8A3T3ZqJ2s+uwnhJ++bTw9hDIz1cWBjnpZksWx3dP2ZOJfDNmFn9J.qkT6qmd1YR2sdTtu9veB+xtro5rU1kMmb4+H1.5eGI56ktirJW9JZJv6lqazWEuq5r8zOY.icVyAZk6y564ob2ebSDpbYt0BHysW.YZs.xbmEPl6t.x7IKfL2atxnlEsQhTLNsTDHzsi9qTrrlNz2pB5u74oJRB

[DanH]

@MikeB No. I mean creating loops much like you can in the sampler (.ie sample starts from x and loops from y -> z). Now that I think about it Loop Direction would be a nice touch too!

As for real time manipulation of the start / end points I mean the mouse drag function of the looper. Your method requires (I think) you to know the length of your sample so you can set the slider range accordingly - unless there's a way of fetching the sample length and changing the slider max value?