@d-healey Thanks you!

@dannytaurus said in Free-running, or randomised phase, for Waveform Generator oscillators?:

@Christoph-Hart Diving in to ScriptNode now. Fun stuff.

Quick question - if I want several random-phase oscillators, would I do this with multiple simple Scriptnode Sythns (like your snippet) in the Module Tree? Or would I create the whole multi-oscillator thing in one Scriptnode Synth?

I'm guessing both are valid approaches, but is there a benefit of one over the other?

Definitely recommend digging into Scriptnode and just playing around with it. Your best friends in this case are going to be the various container types. So if you wanted multiple random-phase oscillators, you could reproduce Christoph's example a couple of times over, using the split chain.

@d-healey I'll send one over tomorrow - thanks for your help so far, appreciate it.

Use the converter node and then hook it up to the freq ratio parameter.

If you also want a semitone detune parameter you can combine those two like this:

HiseSnippet 1767.3oc4YsraaaDEkzxirshaQRSPQ6NtnKbJBLj7qDitvxOjSEZjifoqQ8JiwjCsFHxYXIGZK0hBTf1E8WHqZ+Fxttp4Gn.En+H4OH8N7gDoDsrjpcZBpLfglW7dt2y80P0ziaP784dJpkNpqKQQcQjdWln0tsvTlR88TT+PTCruf3oEM0Nccw99DSEU0BOUNg5BypD940asC1FyLH8mRQ4XN0f7LpCUze1lU+Jps89XSxQTmT6dsp0M3rc417..OEPkUbwFswmSN.K21LHkuD62RQ8yQquxpFqY9XyUVY8M2v.uAYSKrkUkUMWasMdxlUVcS7ZOYCR40UTKVyjJ3d5Brf3qnN6Nbyt5s3WxhDvwTe5Y1D4fJJ5fjildetsoTEkypraKpsYyDCkuhhJpYeyVgHy1CPMnlzdy227c2vEz5ehzFP0YxBuBYfWkzvqbJ3kCjTSAoYifz8P5FdTWQ+Uj34Nn5LfMsv.OkFJQ6UQ8Unc4vFXhkcvsI66AC5cfk1nb4GoA+6gegU.yPP4LMN6.tf7b1ROrz2WZgR+PIsAWxxJ20jhwiaaS7xcYoqg2nN3Rr.myHdOR6Brc.o2FA0OqMEc01zzTtQjVmZibVcFU7bWB6pbDThMUv29556gEXIQDOGrOWhmfJgf5djKfvfHZYAzdD+1BtKDHLDmAdKby.arHqKjLPKdAvFjg2jjCymJ5lNP7FyuZbg38PMoBiV4iwYxAifk51.iwQie.plkEwPzGfyh1+atcB8RK9ERDeTzTXlzPw+owyv3lDsvoI9TehWkQjO8uF27otic9zjf7Gglj.pQlCsxTlCs36b4PeOHbLSZ9ERvnN0w0lTicAwFx4DhwOBRxXgCrEIyl0QqAmwcawYTiz9VGRDdzyOm3kF64pPaKDPk49y7fpGRrIX+TNeeV0mQYDrGXmHSosnxDWxKW95SPQvUSFcn89aZzB+uIM5nLQyip0Q3gqbcEX9Of8hg1JuMg1g7.AkcdCLD51AZ14f.GcHcuAAfEiQrkM.oNirUknwkkikfPmvLCG7F3S7hUjiUiWrRxho5x4.h3RtW6vnu3uCpcTAN+dE3N0OcAtsss4WtK2wkF6RCdMgy0ja2MIIj5LQ6HA1a6vC.IFi89wC6XyMZqS+NRhZ.2H3HL0V9DzC7gd0LeNSGdNgkMUKbLwyOTlygJuL7GDtbPXBo42Ga.DP2lXnBMD2Ia+C3Qh2xF83yqVmRGADc4jqduR4kTCNByfp5HsmxazjTkDZ.Gn+lXO3oAcaKaZbF0BoZhLJembD3IMiDdKhp6erbUCrsxwxZ1xCEJO41iUzhxst.haYYCpmRF099oT6jMLrp0+viVUlF3VnGbKDA24htiBfqKf8BkhxAvPuJK2eCCC3RHeBzfDe.DuPwe9jW9lql.tF7WDEVJKF4kP5hUBSVm187Hr24Dge70.XDiHG9Ppnto7tztN3SCX9fM.DZO5Vt1bnnGsRJm.IJRFAJPCJKV7IoRV5UMvcFbtp5BhaTPR+TN5sIWFYKyTceu9B9HRGwQ7vuuaOqKvEeMyjXAzuox.BRQItIigle6.A2ARsY1yiL1Qbw9LakogZmCY.Dm+XvqSDatHZW3b2r7YITCvzPcs6NYT5I4PomjCkBYoemfRGvFjgT+3djZl8LLudejIQDvHmBavHpt5.b7u9xSxxwlHmX6qFjrUyUxcZVgR2WSvAdqEwSCyL07gpBZTgFGL.vJga2xi7sZdRRVyMgNz3Vgqw8Mf6SEhgrdQSfmwhnTOkL9EKh1WJ6CkOlA7LJLZOCP9C4Y.A1ua4YLZU30+w+dUHUf0DqEudq70B3JMWkVL+siVfPaaZdSRCYbkTRUMMiq3Ps83QVN0xCGYl4zYCI6LXH4HJmJ2DbI0NIukr8n9t13t6D.WvHJqXlYjYoASPmjdPq4bFwDdvgGOouzLwNESQYkFuXm6NgEJiqYb8bVS74QuuZ8fydpGOvMbvX5JllIyUUVq5Ppxu72CpJ+1KdwuOrpT8mb9ysh5vRlDJ.ZSt6Mj97isqlq9.ymVetSNQSaML0TdBolLIUukInQjqnzzmzdzNdOEj1sudcMD0MS8mlsjumnaHcY7pJU3FhiFkhUL7sB91jiBujWZEKJvVO9tO9JS90EBema4ph05.xfgsS8pofBwPNa7YxN5xf1wvHTOZ1PxYHxHcKUWcGVouj30bQpXaSwvt7Ul7Vteexrj4FV4aW1gya6fCeMNS2ua0aiW5jC1vieZ70Gjp67gy.jAK9sRzPNVqhxECZnbnlzSMLx9nF5fqLsGb0o8fqMsGb8o8faLsG7wS6Aex0eP4ukSb1YoqKj7sYsn95Tqwhhajor+G.Rsebr

@d-healey Yes I have seen in with multiple third Party Plugins

@Orvillain Agreed so far I am really happy about this! Very simple to use. Need to test it out in some real world examples still!

@Dan-Korneff thanks a lot bro!

@Lindon Well that was easy. I can't believe I overlooked that. I had copied the code from another project I did a while back. Thanks for pointing it out.;

@Christoph-Hart Oh I was Using the old commit. I just Compiled the updated one . it works perfect Thank you

@Yinxi lol I like this one

@ulrik this is perfect. Thank you so much.

@Christoph-Hart Amaaaaazing! Thanks Chris 😎

@Yinxi you didn‘t have to pay for a VST3 license before and the immediate real world consequences for plugin developers are not very substantive unless you have a fringe use case that requires a super permissive license. It is rather interesting from a business perspective and will ensure that they cannot pull stunts like with the VST2 SDK.

@sophiejean Hello, welcome to the forum. Please post in English so it's easier for us to help. I did a quick Google translate.

Hello HISE community!
I'm brainstorming a creative concept I'm calling "Chicken Road Games," envisioned as an interactive and gamified sampling engine (or plugin) integrated into HISE.

The main idea: simulate the metaphor of a "chicken crossing the road" using layered samples and random path logic.

Imagine that each step of the "chicken" triggers a different set of samples (clucks, footsteps, ambient road noises), and that users guide the "chicken" through musical "paths" (keys/samples) in real time.

Desired features: user interface with a road pattern, sample banks mapped to paths, random or user-controlled movements, adaptive modulation (e.g., tempo/time stretching during rapid crossing), and possibly a "road hazard" effect (interruptions, glitch samples) for an unpredictable experience.

Has anyone tried a similar concept in HISE, using its scripting and sampling engine to simulate non-traditional interactive behaviors?

What HISE modules or techniques would you recommend for mapping "lanes" to sample groups and managing random path logic (e.g., ScriptNode, JS scripts, state machines)?

For the UI: What are some best practices in HISE for drawing a "roadmap"-like interface and animating movements?

Do you have any suggestions for managing CPU load when randomizing sample paths and applying real-time effects (such as a "hazard glitch" when the chicken crosses incorrectly)?

If anyone is interested in collaborating: I would love to co-develop a prototype Chicken Road Game in HISE and share the project files.

Thanks in advance for your ideas, comments, or suggestions!

That's the right direction, but I would also try to stay within the HISE user preset system so you get the intended loading prodecure (kill voices, load the preset on a background thread, then unsuspend the audio processing).

With the custom data model you can define the layout of the user preset file as you wish. Note that it will be converted from JSON to XML at some point though (which is a bit weird).

They also want to be able to export a preset, and include any sample content with the preset - ie; bundle the custom loaded .wav file, or the samplemap, with the preset. For personal sharing purposes.

I would detach this from the user preset system. A preset with sample mapping data and samples should be

The preset file The JSON (or SFZ or whatever) mapping file The audio samples

all in one folder.

@ustk yes I won't be using it again 😆

Could be references to components that no longer exist. I.e you have a reference to Button1 but deleted button 1.

Check in script view to see if any components are undefined