How many sends do people really ever use?

[ModuLR]

I was looking into porting it cos it's now all in c++, but I can't find a solution that handles the shared data like in windows. The option that is compatible with both platforms means it would have to be recoded to work like the racks in that you have no choice but to introduce latency = to the size of the audio buffer at least.

the way I did it is like this... (for code junkies)

Code: Select all

//==============================================================================
// Create a shared data segment in dll (these vars become global to all instances)
//==============================================================================
#pragma data_seg("SHARED")

	struct BufferRec
	{
		int   id;
		int   mode;
		float left[MAX_LATENCY];
		float right[MAX_LATENCY];

	};

	BufferRec buffer[MAX_CHANNELS][MAX_INSTANCES];
	
	int       numSendsOnThisCh[MAX_INSTANCES];
	int       numRecvsOnThisCh[MAX_INSTANCES];
	int       instanceSlot[MAX_INSTANCES-1];
	int       randomCheck;

#pragma data_seg()

it's not the "right" way to do it... but I don't care cos it works, and allows zero latency. If I could find the equivalent of that on the mac, I could port it right away... but I have a feeling it doesn't exist due to the way it manages memory. I'd have to do it the proper way which defeats the purpose.

[kL]

About rack latency: I tried to use a send rack to make a separate headphone mix for tracking and the racks absolutely introduced latency. One track I was sending from was a drum softhsynth that was doubling some Reason drums. As soon I stuck the send rack in on the track (post volume, to duplicate the mix at a different output) the drums got audibly out of sync. (Perhaps I should experiment with the send pre volume.)

[tibenmik]

Another comment on rack sends and latency:

Having followed this thread I wanted to check things out for myself. I inserted a simple rack send (rack filter with LR ins connected directly to LR outs) on a track directly after a VSTi drum synth filter and before the volume/pan filter, and a copy of the same rack send on its own track as the first filter, followed by an instance of SIR at 100% wet. The result was that the SIR track was way off time, throwing a pre-delay on the reverb signal. I replaced SIR with the Ambience plug-in at 100% wet, and had no problem at all: both the VSTi and reverb tracks were in perfect sync. So my question is, does Tracktion have an issue with SIR as far as applying PDC?

_mt

[AD80]

So my question is, does Tracktion have an issue with SIR as far as applying PDC?

_mt

No. You have to put SIR INSIDE the rack by itself. The rack doesnt know what plug-in you put outside it so it cant compensate for that.

[tibenmik]

Thanks for clarifying, AD80. I took your comment to mean dropping SIR inside the send rack and connecting it up - this solved the latency but introduced 'track bleeding', where separate tracks (kick drum, snare drum) are hosting the send rack. It seems that with SIR in the rack you can only adjust the dry level(s) by adjusting the input level to each send rack instance, coupled with the overall summed level by adjusting the 'dry' parameter in SIR. I wish there was a way to assign a discreet track for wet send returns (that have been 'racked'), while discreetly retaining the dry signal on each track that sends to the rack. Maybe v2?

_mt

[valley]

the beeld is just because you haven't quite understood what is happening in the rack. Take a look at:

http://www.adbe.org/guides/tracktion/racks1.html