Delay / Track Offsets

[Dell]

Trogluddite's explaination is just worded differently than mine and use different examples.

A quick skim indicates you are missing a module. Search for the module entitled "Delay Compensation." Delay Compensation tells the host the amount of delay the effect offers in which will show in Samplitude's effect rack.

This is why Tzarls asked you if you have the “Delay Compensation” module in your OSM. Without "Delay Compensation" you will encounter a glitch in the sound when using the delay module.

You will not be able to manually adjust the delay settings once it is exported to VST in Samplitude for Samplitude chooses the default latency settings. So, select a latency based on your requirements. Think of it as Samplitude's "buffer Settings." The "buffer settings" in Samplitude cannot be adjusted once an audio signal is passing through.

Bear in mind the "Delay Compensation" settings will increase times two if you up sample the audio file (48 kHz to 96 kHz). And of course divide by two if you are down sampling from 96 kHz to 48 kHz.

[SBMastering]

Ok, but still it's not going to work anyway, the way I intend, right?

[Dell]

Sorry.

What you are asking for would require a plug-in embedded in the DAW's design architecture like an offline effect ( Samplituude's sMax 11 for example). Real time effects are not given that type of control in Samplitude.

[Tzarls]

I still think we are talking about different things here.... what the OP wants has nothing to do with latency (in the sense of hardware/driver latency). He doesn´t want to alter the delay compensation either - in fact, I think he wants NO delay compensation at all. All he needs is a processor that gets samples and outputs samples. No special magic. In the case of his processor, Internally it has a circular buffer with some fixed length, and some controls to alter that length. By definition, that processor is called delay, but since from the host´s POV a plugin is just a blackbox, what the processor is doing internally is actually of no importance.

Now that I think of it, even if he had a Delay Compensation primitive, he could still get the audio to be delayed by certain amount - for example, if he sets the PDC to 10 ms and the delay time to 100ms, he should get 90ms of delay.

And since his plugin (apparently) works fine with other hosts, I suspect the problem is Samplitude not following the standard - Occam´s razor.

[Dell]

If SBMastering doesn’t want a delay, he merely uses his effect plug-in without the need of the “New Track Offset Test” device in Samplitude.

Unless SBMastering made an error in his design which is very possible since he is new to designing plug-ins, all he needs to do is export his plug-in(s) into Samplitude's vst folder as he would with Synthmaker’s stock plug-ins and it will work without any delays.

It appears SBMastering is trying to make his “New Track Offset Test” device insert a silence by a few milliseconds on the actual waveform before the music starts, which can be accomplished in Samplitude using the off-line effects.

Mastering does not require the lowest latency as if someone is playing a live instrument. Only those who are playing live instruments requires the lowest denominator to prevent an offset between plucking/pressing a string/key on the instrument and how fast it is heard through the loudspeaker.

In Mastering, whether the buffer settings are configured to 209 ms or 3 ms it will not make the any difference when you are playing back a pre-recorded audio file. However, when you are using 10, 20, 30 vst plug-ins you want the buffer settings high to prevent CPU overload due to excessive processing power.

[trogluddite]

I suspect the problem is Samplitude not following the standard

Yes, I would say that is the case too.

I still think we are talking about different things here....

He he, quite so
I should have made clearer in my post that I wasn't suggesting PDC as a cause of the problem. I was just making a bad job of explaining why I thought it was a 'red herring'!
Apart from plugins that need to 'look ahead' in the audio, PDC is rarely an issue for most plugins and can be safely ignored.

So I would return to my earlier suggestion of testing Samplitude more thoroughly to see exactly what VST data (if any) it is communicating. If PPQ or Sample Position are working, then there is a good chance of a workaround.

[SBMastering]

Again, I apologize for my lack of experience -- but I tried to do the PPQ / Sample Position test, but both output a stream. I don't know how I can display a stream to test. How would one do such a test?

[Mo]

I don't know how I can display a stream to test. How would one do such a test?

Search your toolbox for "readout".

[SBMastering]

Hi,

I tried the Sample Pos and PPQ primitives with Samplitude. No luck there. Both just show zero. I'm not sure if I possibly did something wrong so I am posting screen caps.

Does this spell the end of my offset idea?

Sample PPQ Test.jpg (58.64 KiB) Viewed 1040 times

Sample-PPQ-Test-2.jpg (31.6 KiB) Viewed 1039 times

[Mo]

Hi,

Better use blue mono for the readout (use mono readout).

[treacherousumbrella]

the problem there may be that you are using a poly readout rather than a mono readout

edit: beaten to it

[Tzarls]

Hey, SBMastering, any news on this? Did you try using mono instead of poly?