HISE 4.0 - Wish List - Add yours.
-
Yeah once I‘m through with this multipage CSS stuff it‘s spring cleaning time.
-
@CyberGen Check out the table envelope. Also check out the tutorial repo for scriptnode versions of base modulators. Also scriptnode for envelopes in general (set any length our curve you want).
For 4.0, Chris has ticket a lot of things off my list. Some of ones still there are;
- sampler GUI needs some love. Dropping samples needs to be smoother, manipulating them with drag and drop, tokenizer needs the RR group issues ironed out. Theres an issue with dropping files from multiple folders where the folder itself gets treated as a sample etc.
- the script tabs UX needs to be sorted out. I wrote about this partially here https://forum.hise.audio/topic/8181/let-s-cure-hise-of-alzheimer-s/6 . script tabs not remembering code line position, script tabs not being saved per processor, script tabs not being openable or closable with middle click (like code bookmarks) etc.
- code formatting https://forum.hise.audio/topic/8867/auto-code-formatting
- change width of the Modules/API/Browser column
So generally Dev UX stuff.
Also the new fast blur.
-
No new features needed. Make the existing ones more reliable and fault-tolerant, and document them fully.
Our question, as developers is not, "Could this feature be added to HISE?" It's "Is there a feature that would help me do what I'm trying to do?" (Because there usually is.) Then, "How do I implement it?" And finally, "Is the problem I've having because I didn't do it right, or is it HISE?" Often, we can't take that chance—so, we don't use the feature. The latter can be compounded by HISE crashing when the API isn't used correctly—that shouldn't happen, especially in an interpreted environment.
HISE is already an incredible and unique tool. All we need as developers is for the great stuff that's already there to be more accessible to us.
Just my $0.02.
-
@clevername27 That is the reason why I started the topic with HISE is already awesome! I agree with every one that bug fixes have to be prioritized over new features. Having said that, not all of us (HISE users) are pro developers. My coding experience is solely on HISE. I've learned to use HISE to create my own instruments, and I can only dream of releasing something commercially. Everything I know of coding I've learned from watching @d-healey's tutorials or from the kindness of cracks such as @clevername27 in the fabulous community that is this forum. I know that there is a way to code a latch mode for the hardcoded arp only because @ulrik was kind enough to share his code with all of us. And I know there is a way to customize the envelope to get longer times with scriptnode, but I still selfishly wish HISE just came with these things for the more ignorant aficionado coder like myself. Besides, I think that if I started a topic called "list all your bugs" @Christoph-Hart would probably not go near it. :beaming_face_with_smiling_eyes: just kidding. It's obvious from reading this forum that he works tirelessly and relentlessly fixing bugs and improving HISE. So I hope no one was bothered by it. Much respect and admiration for everybody on here.
-
@CyberGen said in HISE 4.0 - Wish List - Add yours.:
I think that if I started a topic called "list all your bugs
-
@d-healey exactly!
-
The famous and long time-requested "Expandable UI" feature by many people.
https://forum.hise.audio/topic/7266/expandable-gui?_=1712308730682
-
@Christoph-Hart a property to all components, "additional info" , useful if you want to collect info from a component, just like the "tooltip" property
-
@ulrik said in HISE 4.0 - Wish List - Add yours.:
just like the "tooltip" property
Then why do we need another?
-
@d-healey for additional information
-
@ulrik For who?
-
@d-healey for instance when using getComponentUnderMouse or a Broadcaster, it's great to get additional information from a specific property instead of fiddling around with the "text" property, and information that's convenient to the user, something like this:
My tooltips are often long and with a lot of instructions
I know it's possible to store the "additional information" in other places, and also in the "text" property for the component, and split the text with indexOf(":") etc. but I think an extra "text" property would help
-
I would like to have ..
- Display Wavetable Synth Waveform
https://forum.hise.audio/topic/7172/display-wavetable-synth-waveform?_=1712384198914 - A Free License Authorization Manager System to Lock/Deactivate if buyer claims for a dispute to Paypal
https://forum.hise.audio/topic/9355/how-to-deregister-plugins-if-paypal-claim-is-raised-by-a-customer - GIF Support https://forum.hise.audio/topic/1613/can-i-add-a-gif-image/2?_=1712384198921
- Better OSC and Filter (Both in SN and Core Waveform OSC)
- More LAF Customization (Function)
- Expandable GUI https://forum.hise.audio/topic/7266/expandable-gui?_=1712308730682
- Better FAUST Support
- Custom Audio Visualizer and editor
https://forum.hise.audio/topic/3614/how-to-create-audio-visualizer-in-hise/20?_=1712384198923 - and Please write Better Docs and Code example for API Function. Sometimes we don't have clue how to use it.
- Display Wavetable Synth Waveform
-
- Personally I would just like a gain that I can assign to an envelope without the gain having any latency. simpleGain if you assign it to an envelope it's anything but precise and to create a sidechain effect it's not possible
-
@DabDab said in HISE 4.0 - Wish List - Add yours.:
HISE own License Authorization Manager System.
-
@d-healey said in HISE 4.0 - Wish List - Add yours.:
@DabDab said in HISE 4.0 - Wish List - Add yours.:
HISE own License Authorization Manager System.
Corrected. I want a solution for Free /Donationware Plugins. See the topic.
https://forum.hise.audio/topic/9355/how-to-deregister-plugins-if-paypal-claim-is-raised-by-a-customer -
Since running our own EQ is one of the main thing in DSP:
- A way to get the EQ curve out of a
snex_node
with a display buffer
I remember asking for a
snex_eq
a while ago but, @Christoph-Hart, you said that you'd rather not do this for some reasons related to code maintenance or something like that which I understand. Also, since a proprietary EQ DSP might (often) contain some nonlinearities, this might not be compatible with an "EQ only node". Sosnex_node
is a nice way to go, just missing a display buffer... - A way to get the EQ curve out of a
-
First, I just want to say thank you for making Hise! I downloaded Hise and in 5 minutes I built what would have taken me a few hours in Kontakt. The world needs Hise!
I hate to post a wishlist as a noob, but something thing came to my attention just in trying to recreate my NKI with Hise today.
Flex Env???
My NKI uses the Flex Env + Modulators for time and curve. I found AV's poly flex post. Sounds complex to a noob. I'll dig in, but could Hise have more here out of box? Please forgive me if this is too early of me to ask.Opus sampler support
Lower sys req, wider user base (like many, I'm 100% mobile). I only point to Opus as it is why StaffPad has tiny versions of giant libraries. It seems a good fit.
A side reason is that UPM/APM reject VI's (I've even seen a non-profit require real performances now), so lossless can only be bloat for a mock-up. I've seen similar mp3 requests on other sampler forums. So maybe this would also be something Hise had that others lack? Just a thought. -
-
+1 on the Sampler GUI, drag and drop manipulation. Vel ranges are hard to see clearly.
+1 on tokenizer. It beats Kontakt, but it's not reading ff to pp for me.I think Hise would be more clear with less in some cases (removing buttons like *select all, deselect, undo/redo, zoom), so navigating more useful tools would be easier.
Not complaining... I'm loving basically everything so far.