Just gave this a go, and it worked brilliantly, except that before you:
ComboBox1.setControlCallback(loadImpulse);
you need to
Engine.loadAudioFilesIntoPool();
Otherwise, brilliant.
Just gave this a go, and it worked brilliantly, except that before you:
ComboBox1.setControlCallback(loadImpulse);
you need to
Engine.loadAudioFilesIntoPool();
Otherwise, brilliant.
@d-healey grazie!!
None of the scriptnodes would compile for me, but I was able to get the develop to compile.
And, amazing, the convolution reverb works!
@Lindon thank you kindly!
OMG, that is brilliant. I was spending a ton of time trying to get deeper and deeper attributes from the arp and setValue and diving deep into sliderpack data, but low and behold, the property editor saves the day again.
I am also interested in this possibility, so thought I would give the topic a bump.
@Eskano thank you for the reply.
Yeah, but do you have any insight into how to check the gain between each module?
I'm curious if anyone has a suggestion for the best gain staging practices in HISE?
Should I be putting a gain processor before every other processor to control for clipping?
What about instances where you can create clipping within a single processor, like a delay processor with the mix and feedback high enough to create clipping? And to that end, I'm able to get a lot of clipping in the dynamics processor by virtue of the release time.
I've attached a HISE snippet here that has a Sine Wave Generator and just two modules (inactive, but when activated the each can create clipping when a chord is played).
HiseSnippet 935.3oc6W0saSiDEdbRlEJkEUPUHtBEgP6cfRVXAtKtMooTQS2n3.6xUnA6SiGg8LlwiKDtFj3Uf63cfW.dDPZeAVtFoU8MXYFa23wMVQkncYEn0W4y2wmY9N+Lmy3gBtKDGyEHqUFOMBPVmE6LkI865SnLzN8PVmCOfDKAQyLnMmFQhiAOjkU8s0.Vqz.k9bXmMIADlKT.gPOfScgcogTYA5P66QCB5S7fwzPiu9l163xYc4A7DEepiaghHtOgLA1in+rZXj0OrkGUxENRhDhQVM1j6M0wm+LV12+.ZL8wAfVnMxQsPYv84AdZFqeG00mF3M7H+NFgrvCKhB0yhBqiGP8nyvKhFqkpnYgElwCqZKhdsMoWqJoW6JnGxfcMxXmhDbuj.hrLyzoibETd4L0NLIvhoxoloq+So64wCoRW+p4asJ3qJQ8uMeyS9+Hdq82GbkEjsAt+uurY5ufBwZFbY0LtbJbOHfLMkEmN681khToP5yQ6B6abFaM6YJFQm3anYc69.38X0IKCK9yWr9e04HbSCd+ke0m5rK+YCUaXeA7zYqyq+C66RmCE0yd.84lEYigvHtpkhaoJu5kCe0OYguJxdi3IRJax.hTn2W7dIgNp1GtfJ4wXPfZwwV0PZSSkaok0jvAXdoB+s5IWYasrUtx1GozrB4BYYkyf6MkQBotwoIlUmIVN2rsx61hQTdhmYcrFdru.h8UkCGWwFRoJEXFrznif.fDazq7g1c4gQhTZM2VbXmBkGeiruw6168EpGoO6kq5su4MWwXYKwDkY+jgtx7w9iu3kcRaxChJ72bMU5x45l2qyULmieUCVLf7DHIphkadEeyVwctrJtUwNTFjNZNsj6hoxM+MxAPysAFHzcWaufoye3jNcN5DOc9Wckpserfvhi3wkVXGHjNlyzQ5Bv6GC5lElkboOc4DQkpNrSekSVoMNDYhHctwFg7DlbQ4Z7IKWWd7ow2u3AHVM9+qO7O3LPqgyckz0T05gQApVoG.AbEhluWHGr4QnkK9GvY7HeNi5ZVYLBTGZmLADl9QkN2waHstcEch1UUcRDpXFrn3xR2poTrXQ4tKgynaS8I1leebEv5eGcEvu.p70X5xWi8Hj3J3ORMvPJ3A5Z4Smhn7aV5Oysh5uJUxMaiNfDjn.v3VWuEJT0c7Qtt5v80Twmps4mWBatwRXyMWBa9kkvlasD1b6kvl6rPazCl1HQxCyNJp.FtUOhjnp0mcmNq5nOCbt10fE
But aside from those particular instances, just curious if I need to have a gain processor between every unit and constantly checking the current DB of the output?
Currently, I'm doing a whole lot of output gain knobs that the user can control in the interface (which I like anyway), but I feel like if I can make it so clipping isn't an option, the world will be a slightly better place.
Hi,
Every time I rebuild my interface in the interface designer, I get an error notice in my console that "Component with name _____ wasn't found" for every UI component. However, the interface does rebuild and display and function correctly. So I'm not entirely worried, but should I be?
Also, I followed the advice here and did an XML backup and went to the validator. Everything was valid, so I'm even less concerned, but wondering what what's going on.
Also, I was definitely moving things around in panels, so I imagine that is the cause.
@ustk yup, time to go callback all the way. Actually feels more familiar coming from Kontakt :)
@ustk thanks so much for the reply.
So that means that I cannot use both in tandem? If I want to have a callback for a specific control, I must not use the property editor to set the processorId, but I must script that?
Just gave this a go, and it worked brilliantly, except that before you:
ComboBox1.setControlCallback(loadImpulse);
you need to
Engine.loadAudioFilesIntoPool();
Otherwise, brilliant.
@musictop Thanks so much, I'm gonna give this a go!
I'm sure this must be covered somewhere, but the kind souls on here have been clearing things up for me so quickly, that I figured if I can't find the doc on it after an hour I would post to the forum.
If I create a basic slider, then create a custom callback and test out the callback with a console print, it is all golden. But as soon as, in the property editor, I choose a processorId and parameterId my callback no longer triggers.
Is there any guidance on this?