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.

anyone? :)

Is there anyway to use addToMacroControl with Macro Modulation Sources of frontend macros? I essentially want to assign the macros using buttons - not the frontend controls, but I can't seem to get it to work. Here's what I've tried:

const var Button2 = Content.getComponent("Button2");
const var slider1 = Content.getComponent("slider1");


inline function onButton2Control(component, value)
{
	 if(value == 1) 
	 
    {
	    
    slider1.addToMacroControl(0);
    
    }
};

Content.getComponent("Button2").setControlCallback(onButton2Control);

@candlefields that would just adjust the amplitude of the instrument though? That's not anything to do with the loop points or crossfading.

The current problem with the loop player is that it doesn't have a crossfade - so if you loop a sample and it clicls/pops, there isn't (currently) a solution for that other than using the full sampler, which for some projects adds a lot of unneeded overhead.

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

@d-healey I've never had to do that before - where are you inputting that? Into the Juce compiler? I'll try compiling it again with that and see if it makes a difference.

@Straticah Hmm LFO's seem to be working for me, but odd that you're also missing 1/16ths, just in a different place. I suspect there is something going on with the recent commit

just to prove I'm not going crazy...

@paper_lung The default value for me seems to be 1/1

@d-healey I'm on a recent commit as of last week, not sure what's happened in that case. I've just made a fresh project and the 1/16 value isn't there at all.

@Chazrox Huh. how strange! I've not amended any of the code for the arp.