So close to Rubberband-ing

iamlamprey

Okay so (at least) one of the issues is that RB can't process in-place or on an alias, it needs a separate input and output vector.

dyn<float> outPtrs;

template <typename T> void process(T& data)
	{
		if (!rb) return; // safety check in case the rb object isn't constructed yet

		auto ptrs = data.getRawDataPointers(); // RB needs pointers
		outPtrs.referTo(data, data.size()); // dyn confuses me		

		rb->shift(ptrs, &&outPtrs); // ??? 

		data = outPtrs;		
	}

@Christoph-Hart do you have any suggestions for creating a blank vector the same size as the one from getRawDataPointers() for RB? I assume memcpy() isn't ideal in the audio thread

iamlamprey

(laughs in thall)

Writeup soon

HISEnberg

@iamlamprey Amazing work, it sounds pretty great! Excited to test the results myself

d.healey

@iamlamprey Oh so close :) very exciting. Is it the sort of thing where it's easy to swap out one algorithm for another? I'm thinking of trying the Bungee library.

iamlamprey

@d-healey The actual DSP in the third-party node is pretty simple, the main stuff was getting all of the includes to work together (and using the right class in RB that doesn't need 2 separate buffers)

The RB time-stretching stuff might also be possible using this third-party node and just swapping a few things out, I don't want to give out false hope just yet but