I managed to remove the root note pitch detection, thanks for the tips everyone. For anyone interested, I commented out the following code in the AudioLooper.cpp file within the source files:

/*if (copy.getNumSamples() > 0)
	{
		auto freq = PitchDetection::detectPitch(copy, 0, copy.getNumSamples(), sr);
		
		if (freq == 0.0)
			return;

		Array<Range<double>> freqRanges;

		freqRanges.add(Range<double>(0, MidiMessage::getMidiNoteInHertz(1) / 2));

		for (int i = 1; i < 126; i++)
		{
			const double thisPitch = MidiMessage::getMidiNoteInHertz(i);
			const double nextPitch = MidiMessage::getMidiNoteInHertz(i + 1);
			const double prevPitch = MidiMessage::getMidiNoteInHertz(i - 1);

			const double lowerLimit = thisPitch - (thisPitch - prevPitch) * 0.5;
			const double upperLimit = thisPitch + (nextPitch - thisPitch) * 0.5;

			freqRanges.add(Range<double>(lowerLimit, upperLimit));
		}

		for (int j = 0; j < freqRanges.size(); j++)
		{
			if (freqRanges[j].contains(freq))
			{
				setAttribute(AudioLooper::SpecialParameters::RootNote, (float)(j), sendNotification);
				return;
			}
		}
	} */

I've not fully tested it yet, but hopefully proves useful to someone.

@d-healey That seemed to do the trick, thanks.

I find the LFO modulators to be quite fast - the lowest rate is 0.50hz. It would be really nice to be able to have these set to slower rates, if possible. Ableton modulators for example can go all the way down to 0.1hz.

Hi all, does anyone know how to amend the sample install LAF? I've got numerous other LAF functions within my script but unsure which one is affecting this dialog and how to edit it directly.

Went to a previous version of Faust and it's working, all good!

@Oli-Ullmann Perfect, thanks!

@jeffd my recommendation is to use Gumroad just to get started. I did this before moving onto Shopify, then Wordpress/woocommerce. Gumroad doesn't cost you anything to get going and makes it easy. You can learn things about web-dev as you grow - that's what I did. You can embed Gumroad products on a website of your choosing if you want, as well.

@Lindon said in Sample Import Tutorial - It's Broken!:

@griffinboy said in Sample Import Tutorial - It's Broken!:

@Christoph-Hart
Thanks for the response, I was hoping to tap into the sampler to make use of the disk streaming and other fancy optimisations, but you are right.
A custom solution will allow for much more direct control over the buffer(s), which will probably be much more beneficial in the long run.

But actually @Christoph-Hart - getting the loop points to work correctly is something I'm really going to need in an up-coming project so sorting this to be consistent would eb a win for me.

+1 - I would love to make use of the tutorial project for this as well. as an alternative, adding a crossfade function to the audio loop player would be a great solution

@d-healey Haha, well that was easy. I just didn't change it enough to see the change, thanks!

@BWSounds That text can be altered by editing the source files. I can't remember where it is, but look for the 'drop audio file or right click to open browser', then edit that string. You'll need to recompile Hise once you've done that.

@d-healey you mentioned here that a recent commit which added AVX caused issues on some VM's, any chance this could be the issue I'm seeing? Do I need to disable AVX somewhere? https://forum.hise.audio/post/109773

disabling IPP had no effect

@d-healey I'm wondering if IPP might be the issue as it's flagged as on, and while I have it installed, my previous plugins did not use IPP so I'll check that first

@d-healey good shout - I've just re-exported an older project, and it no longer shows in any DAW's and fails the pluginval with the same error. runs fine on my windows pc.

Hi all, I've exported a VST3 plugin (using a recent Hise dev commit) which loads fine on my Windows 11 machine, however - when attempting to load the VST3 on my m1 Mac running Windows via Parallels, the plugin does not load at all in any DAW, and instantly fails pluginval with the following:

Num types found: 0 !!! 
Test 1 failed: No types found FAILED!! 1 test failed, out of a total of 1 Finished validating: 
C:\Program Files\Common Files\VST3\Signa.vst3 *** FAILED: 1 TESTS FAILED!! 1 test failed, out of a total of 1 Finished validating: C:\Program Files\Common Files\VST3\Signa.vst3 
*** FAILED: 1 TESTS 

any thoughts what could cause this? Have I missed something in the Projucer or Hise settings that could cause builds to not run on ARM? Running absolutely fine on my other machine and my previous plugins have worked on both computers with no problem, so I'm a bit stumped.

@d-healey That's just assigning MIDI CC though right?

@d-healey If I have a filter cutoff control on my UI, how would I assign the Modwheel to that control?

Hi all, just wondering if anyone has any tips of the best way to implement Modwheel assignment in a Hise project? Unsure where to look, can't find anything in the docs.

@d-healey that makes sense - thanks! what are the different save modes for in the xml? am I correct that 0 is if you want to use the original samples rather than the monoliths, 2 for using the monoliths, 1 is for...?

@d-healey ah ok so maybe I've misunderstood what that's doing. so are the ch1 files just compressed samples? they don't store the data from the xml files?