@T-B-Guang Having this same problem with no obvious reason. Trying this in a new tester project. only a few samples. sampler channels are the same as master channels. Have you found a solution?

@bendurso thank you for this.

Hello fellas,

This is mostly a music theory argument, so bear with me.

For a long time, I’ve noticed that the tempoSync subdivisions in HISE are not arranged in true linear order. At first glance, it might seem logical — for example, "1/8D", "1/8", "1/8T" appear to follow a descending rhythm duration: dotted is longer than standard, which is longer than triplet. That’s fine within that group.

But the problem arises when you move between groups. For instance:

"1/16D" (dotted 16th) is actually longer than "1/8T" (triplet 8th),
Yet "1/8T" appears before "1/16D" in the current list.

This breaks the musical continuity of gradually increasing rhythmic speed. It results in awkward, non-linear jumps when changing values, especially noticeable when modulating tempo-synced effects.

Suggestion:
Reorder the values based on actual timing, not just visual grouping.
For example:

  "1",
  "1/2D", "1/2", "1/4D", "1/2T", "1/4", "1/8D", "1/4T", "1/8",
  "1/16D", "1/8T", "1/16", "1/32D", "1/16T", "1/32", "1/64D", "1/32T", "1/64", "1/64T"

Now, yes — this can be worked around in scripting by rearranging arrays manually, but I figured I’d point it out in case others feel the same. It might be a worthwhile change at the source-code level to ensure smoother musical transitions and better UX and make our coding lives a bit easier.

Thoughts?

@d-healey should I add this to the gitHub issue list?

@d-healey alright, I'll give it a try. thank you.

@d-healey yes, so basically to simplify things I'm just using a knob to switch waveform that is being displayed between the two samplers. It's a bit more complex in my actual project but this should recreate the issue at a basic level.

HiseSnippet 1365.3oc6YszaaaDDdojWmH0zflfTfdo.DF8fbQfgn76VTDYKamZjHGAKmzdKXE4JoElbWhkKchZQ9O0eB4+Q+S368P6r7gHorrisZp6K4CFblcmY914Mr6HE1zf.gDYT8jQ9Tjw8vcGwUCaMjv3nC2CYbebaRfhJMiYs6HeRP.0AYXT9oZFFUV.E8y4OYWhKgaSyXgPuRvroOm4wTYb6z7YLW2CHNzSXd4t8ZMOzVvaIbEg.dJiqi7I1mRFPOhnuVIL56IACQFeMtQ+d1M5u4paYss01at11VVquUu0p2v1Y8sWc0MV0oeisHarEHzh66vTBYWEQQCPFKrqvYT2gh2viMvqXArdtTMgEpKX4X1GHbczOQ82nVCYtNcRcTAHPocxbakicaOB2l4vFyOy88YQGXlIQdGnQohvqbA3YcYvaJPxHGjVHFRO.20Vx7UYmnwymfOjCQy9DHNkGJw2EUhVB2R.2fqVwibJ8.IPLVhZaTu9iMges72VsJDqBTlmQjl6D5vD+.4LZegzyx76LS0v.ppkvyWvAhZKU7ZKo0QUF2kwol8C41JlfaJ3OiK5YoUfT3VyNU5GCFxMjtb0etZkf2vT1CMqkvoBvphMIfZV+afupTzLqDPAS6m5CNzYoGatTWhmuKUFggKJg8PBe.0oV7g8jTxo5uRsh0MzJMtIV4cUqTUaq2ANmo6Ei7OKsr1hIdoVDW2dPkRshNOPw4bqGITzWvqE4.q9tplSdT+9S8rDcAOiodrt.VdUBViG50iJyG9zWDRRKl4u30Ky2N1kj6hB9gbl5E9zD5rRWqoTmfR7oPESoDDBWUEUu74I0KEhSHlitFtXrCE8Xx2lCMoxtehx55xbnxHsbGbTzYRgO+InWd3dDEQWEm.O.x9Toho8LF6QOC5gFWSWAuGM3TkvOB+I4DHC7M9E71w.388ZNJCMG0LWRLLT.mlDqehSZuq3QB5Ga7qfBGo+32fOfYH9cY+DHFFasBzD6hcrfdkBmPWhpXCT8XljCfbqBcszcl3AL0n79yI6ptvkmaUepM8mZly0DtO.2Q2cZ53szTvqNU7uX7lLi5Sw62uO0VkA1EvG7iW4.oO5P4KigxCwcUPGOOFePRBVDdFmtY8wXOC+q8dFcjTWAwIN8L8Zuu4tgf+RVj6uzLxT63IB4ErUBxOl5SIJH7mSl6173iepTD5OoTm+jnjkSjP2avUj+fWvofeWk+M1RJBB5COmHcEj+nNgxAZeUFmiomQkAE4cTnGD64bpaftpz.X8x.pNVyraSTR1aye6HqT+DRT7FV9Jh1ZB5FSPu5DzqMA85SPuwDzalQG6PaS7iWaw1kHg1LdhKL63NWuYGfl5Pf2dtatKavXqDyoXulbWcryOBf4Vg71b+va0NY+4a7V95A2Ov5rURwXWlNTsO+LnXE3nw3Cg4g8IgtpTtEabzVvE9CEblcwRCHUev.pLO1m5CZGkBpLy37nlGScovRfYr9plOGVfkHKVwei7E27U6mZ75Kvwv0T2sy7+FCLK++9AlWkq69IiKMAqKU+CONeObTCdS873+tf5whPELmMcVGFFH1EVBvllerXI8n1X55ZZMf5R4NQD+N7SxgVoyP0GZkdHxNUUvaK46ns6MJS45QGQ6A5BSmcymRG.qZngDL2aFVWpw70klutT90kVD6PBbluoz7MktzMkZLeSo4aJMeSo4aJ8u3MktMPoGwVJdsc7eeWMVuaDG.k7n+sTUvs0zlS4uJrGLu5011EU0EDrwrJ3pypfqMqBt9rJ3FypfaNqBt0GVP85D6DpDdwMSQn1c1ONAzX+wIfkQ+AvxNeLy

@d-healey I'm not a big fan of that. I try to avoid it whenever possible. I've pretty much set everything up so that one set of components works for other in the same category, this keeps my component count manageable. Is processorId a property that must be left alone after initialization?

Hi,

As stated in the title, I'm trying to dynamically switch the processor ID on an audiowaveform. I'm scripting a very basic property change, but it's not working. It shows the change in the property window, but not in the audiowaveform tile. Can you help me figure out what I'm missing?

Thank you.

const var AudioWaveform1 = Content.getComponent("AudioWaveform1");

inline function onKnob1Control(component, value)
{
	switch (value)
	{
		case 0:
			AudioWaveform1.set("processorId", "Sampler1");
			AudioWaveform1.changed();
			break;
		
		case 1:
			AudioWaveform1.set("processorId", "Sampler2");
			AudioWaveform1.changed();
			break;
	}
};

Content.getComponent("Knob1").setControlCallback(onKnob1Control);

@DanH ok, that explains it. Thank you!

@DanH Yes, that's what I'm ultimately trying to do; however, I haven't even gotten to that part yet. Hise crashes when I set the processor ID to any sampler (not dynamically), so I haven't been able to implement the dynamic change. I have changed floatingTile component types dynamically before without any issues, but not with the Waveform type.

@CyberGen Still having this problem...:

Hi friends,

I'm trying to use a FloatingTile in Waveform mode, but it crashes HISE as soon as I assign a sampler in the Data object. The audio waveform component works fine, but I was hoping to use the floating tile dynamically since I'm using it for some waterfall waves. I have included a snippet, but it may crash your HISE when opened. In any case, it's just a blank project with a single sampler and a single floating tile assigned to Sampler1.

Q: Is this a bug, or has the waveform mode been permanently deprecated from the floating tile?

HiseSnippet 1235.3oc4WssaaaCFlJNLq1qsasnWraFfPvtHcHavxNG2tnNG6LZcpgUV6tqfQhxlHRjBTTIwqq.CXOEE49cW.1iPej5av1OkjsjbcSS8Z6F17EF9+D4G+O6tRgCMJRHQF0NbXHEYbcr8PtZvNCHLNp8tHiah6PhTToYJqsGFRhhntHCiJ2Wyvn57njOu5daS7IbGZNKD5wBlC8gr.lJma2VOf46uOwkdHKnf1qzpsifuivWDC3oBtNJj3bLoO8.hVs4vnefDM.Y703FdG4zva8laXso0lquxlVVqtwQqTugi6pa1r4ZMc8ZrAYsM.iVXOWlRHsUDEMBYL+1B2g1CDmxSufGyhXG4S0DVHa3lSYuuv2U+D0+Fsy.lua2QNpHDx.2M2sUI0scGbGlKaL+b22mmHvL2hhNPi4JCuJkfm0aBdSARFEfz7oP5VXaGIKTkKQimOE2lCQSOBDmJBkTcQFuDui.Tfq91.xwz8k.wXCVZs50W1D95teuWL2QwDbSA+.gh9H9R2s1ypUs1yqYNoHOuoJSeMRguOUNUw5TC4kY3R73finxkMOg3GSGqH77K6SW3p4ScRe0ETTvayYpGERynySJrlRD.k41fe8is2knH5fRFOPuPpTwzvwXW5IPIQZHpJdWZzwJQXhtAgBt9DLtgJKmJMnruufnX79Gx.Xy.D7Y3hrrPmkWC8fVCyIZzJNzE7Ba4AAP8iQGnyvTJ.pgeB4DpmPFfNp+nJupK7hW76mqO.lhFjy8OgOk41Hi8upYqnmoxU9hKt32zbSbEF6heVMSyEG6vZ6t32Yt3hKqY1l6ROCH+FqDRvM6KN8IB4wQP4OED3Q7in0dN5TlqZP9qi0JGHM0W44me9uj1f40pEfpPgarOQUtzT2.KS.jaUpdPmzyiXpgEavMY857u4bq5SscxTybthv8V3tLkyfoi24lBdgLvOz3Mq62Mv644QcT4fcd79+zk1p68NT9xTnbarsRRIAPwgMIHDZujfmZ3LJq2GSvBuxSv5JoPopqM6mKn1KascL3ujk49GsRtpsBDw7R2UFx6QCoDED9KXy0Z0q28kh3vIs5U2KIY4PILAEbEEE7HNE76phuwcjhnHO34jbVQEE0MV1W6qx4zidBUFUl2AwAPrmyo9fwXCCcWvHpNVyb5PTR1YE0N4VpeHIIdCi0SnslftwDzMmfdkInWcB50lfd8b5TGZGRnNy.nmbjwmb0FY.GPWB7jKn41r9iO7TNkawTP0w97DbUXmjoLcegOTKb7QsA1e+9sUtZv8sreT0QXzloCU6wOApQANZLdaXhrGI1WMha49EcDbQ3.Am4Tth.xv62mJKh8o9f1RofBxbN2oUOpOkDUnj9qZ8PFmRjkKzem7Eu66JN030WfSgqotIm4+MlSV4+8yIuLW2MylRZB2tT8u7370wI80M0ig+mBp8Dw50vGMhCCyAsgY+NzhSCmSOgMkttlVCHaJ2MgPuTclPqQiN0BsFID4L5nf2V1uSWptBkqGcjr9mOLT1uXJcDrggFRv3sOJnLf3HEO0I8+low50R3.njm7u2qh6noMsPI+eshPM.lW8TGmxG0qYXiY0vlypgqLqFt5rZ3ZypgqOqFtwa2P85DaEqDAoMSQnNc2KMAzXuwIfUP+Er0miyL

@Lindon @bendurso @d-healey Thank you guys, these are great suggestions. Much appreciated. I haven't had a chance to sit down to try to implement them yet. I'll let you know how these work out as soon as I give them a try.

@bendurso Yes, that is true. I had thought of that. But I would much rather keep using expansions if possible, It offers other advantages. I'd like to keep the ability to keep adding features/sounds/instruments through expansions to the platform as it grows (expands) over time.

@d-healey

Not as far as I'm aware.

Oh no, that places a big limit on my project.

@Christoph-Hart, could I kindly request that you open this up?

I'm trying to have multiple independent sound sources that can load samples from all downloaded expansions, not just the active one. Ideally, all samplemaps should be available at all times.

Thank you.

Hi again,

I came across an issue while exploring expansions. I want all expansion sample maps to be available at all times, not just when the expansion that contains the sample map is active. Is that possible?

How do I set that up?

Thanks.

@CyberGen update. So, it turns out the expansions weren't coping to the app support folder correctly and that was causing the shaders not to show up. Once I fixed the expansions folder, the shaders started working again. So it seems it had nothing to do with openGL and everything to do me effing up the export. Cheers!