Haha the easter bunny has delivered.

[d.healey]

@ustk I use audacity and then export the list to csv, open in a spreadsheet, and filter the data. Might be too slow though if you have a lot of samples

[ustk]

@d-healey Yeah but remember it has to be doable in a compiled project in the end ;)

[Lindon]

@ustk cant you use Loris in HISE to generate the SDIF file and then some other (not open source) process to read the partials from the SDIF?

[Lindon]

@Lindon what format is the SDIF file?

[ustk]

@Lindon Don't you know what an SDIF file is, Lindon? Because... well... I don't... :)

WikiWiki:
"SDIF, "Sound Description Interchange Format" is a standard for the well-defined and extensible interchange of a variety of sound descriptions."

[Lindon]

@ustk its the partials analysis produced by loris analyse - essentially the sines and their envelopes that (when combined) re-generate your original audio...

[ustk]

@Lindon A nice idea indeed, if it's authorised by the license

[Christoph Hart]

@ustk you can also build an open source analyser app that stores the data in a format that you can define yourself so you don‘t have to come up with an SDIF parser.

[ustk]

@Christoph-Hart I just need to get the harmonics from any FFT solution so let stay simple, especially since Hise probably has everything I need at some modifications away :)

[hisefilo]

@ustk https://sourceforge.net/projects/sdif/files/sdif/SDIF-3.11.4/SDIF-3.11.4-src.zip/download

[A Former User]

@ustk said in Haha the easter bunny has delivered.:

It crashes on mac with a mouseUp in the upper previewPanel so I changed this

Engine.playBuffer("", "", 0.0);

into this

Engine.playBuffer([], "", 0.0);

I had the same issue on Windows, thanks for the easy fix :)

[A Former User]

I've written a temporary method for the Save button, for those of you just as impatient as me :) :

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

inline function onSaveButtonControl(component, value)
{
	if (value)
	{
		//Grab suffix

		local suffix = SuffixLabel.get("text");
		local fileName = LorisProcessor.CURRENT_FILE.toString(1);
		local audioFilesDirectory = FileSystem.getFolder(FileSystem.AudioFiles);

		//Write buffer to audio

		local bufferToWrite = LorisProcessor.ooo;

		local fileToExport = audioFilesDirectory.getChildFile(fileName + "_" + suffix + ".wav");

		local isMultiChannel = isDefined(bufferToWrite[0].length);

		if (!isMultiChannel)
			fileToExport.writeAudioFile([bufferToWrite], Engine.getSampleRate(), 16);
		else
			fileToExport.writeAudioFile(bufferToWrite, Engine.getSampleRate(), 16);
	}
};

Content.getComponent("SaveButton").setControlCallback(onSaveButtonControl);

[Christoph Hart]

@iamlamprey yeah, go open source! Now do a realtime synthesizer next.

[d.healey]

@iamlamprey Thanks for that!

@Christoph-Hart This is amazing. I've just been playing with the pitch lock and my dynamic layers crossfade perfectly without any noticeable chorusing. I didn't even make much of an attempt to line them up, I just auto-trimmed the starts and dropped in some loop points.

[A Former User]

@Christoph-Hart said in Haha the easter bunny has delivered.:

Now do a realtime synthesizer next.

Any suggestions on optimizing the number of partials? I don't think I can do 2000 lol

[Lindon]

@iamlamprey

@hisefilo is our additive synthesis expert I think - last time I looked at his published stuff he was using only about 8 partials to get something viable, so you could "optimise" down to this, build an additive synthesis engine to utilise these, and then keep adding partials until you are happy.

Of course "build an additive synthesis engine" is a 5-word description of a HUGE job...

[hisefilo]

@Lindon @iamlamprey LOL, not that expert but spend a lot of time dealing with partials. I think 128 harmonic partials + residual noise can create almost any sound in a credible way. (lower registries from C2 and below will need up to 256 partials but you can optimize that for each octave)

I haven't checked the Loris integration yet. But I guess many of the 1930 partial you have is noise turned into partials. Have you checked how many partials you see on Spear for this sound??

[A Former User]

I actually have some semi-working additive nodes I made in SNEX a while back, they just didn't have working envelopes. IIRC they utilized about 40 (?) sines and waveshaping to add overtones without a noticeable CPU hit

The 1930 partials seem to be the Loris algo being overly sensitive, a lot of the extracted partials are extremely close in frequency to each other:

These are sorted by loudness, you can see there's multiple 552.x partials, there's probably some parameter for filtering these but I'm dumb :)

[d.healey]

@iamlamprey

The 1930 partials seem to be the Loris algo being overly sensitive,

I assume that's why the resynthesis sounds so good. But for an additive synth it's probably overkill.

This is probably what you need: http://www.cerlsoundgroup.org/Loris/docs/utils.html

collate : collate the Partials to reduce their number without assuming any harmonic structure (cannot distill later!).

[A Former User]

@d-healey Yeh I noticed that command, not sure how to use it in the HISE implementation, I tried

lorisManager.process(CURRENT_FILE, "collate", ???);

No idea what to use for the third parameter, or if the collate string is even viable there lol

I currently have a hacky solution by just rounding the values before pushing them to the array, then using pushIfNotAlreadyThere to remove the duplicates, it works for now