Some questions about coding in SDK3 vs SDK2

• In SDK3, a non-audio pin being static is equivalent to "!pin.isUpdated()".
  
• Don't bother calling isUpdated() in your subprocess method. The only time isUpdated() can ever return "true" is during calls of onSetPins().
  
• The behavior of the Gate pin of the Midi to CV module has changed in SDK3/SE1.2. Even though it's an audio pin, pinGate.isStreaming() will always return false. So don't bother using isStreaming() on a pin connected with Gate, use pinGate.isUpdated() within onSetPins() instead.

As you noticed. pin.isUpdated() is how you identify a pin update on a non-audio pin.

2) Does getBlockPosition() in SDK3 have the same meaning as SampleClock() in SDK2? If not, what is the equivalent of SampleClock() in SDK3?

In a DAW, audio is process in 'blocks' (aka buffers or batches) getBlockPosistion() tells you how far though processing the current block your module is. e.g. if the buffer size is 100 samples, a block position of 50 indicates you have processed half the samples in the block and have 50 remaining. Note: SampleClock() returned the *absolute* position since the module started processing audio. e.g. if you are half-way through processing the 3rd block of 100 samples, sampleclock = 250, blockPosision=50

No. Some overloaded member functions, like setPins(), have access to the block position. So you don't need to specify a block position when accessing the 'current' value of an audio input pin. However your processing function (usually called subProcess() ) is required to process a 'block' of say 100 samples. So this function might for example take 100 successive input samples and transform them to 100 successive output samples. In this situation the SDK can't assume the 'current' block-position represents the current time, because the SDK does not know how many of those 100 samples you might have processed already.  In this case you need to provide the block position to indicate e.g. "i have processed 50 samples of this block, so tell me the input signal at block-position = 50. Hope that makes sense.

In SDK I am experimenting with a tweak that simplifies the process function by removing the need to pass block-position explicitly (block-position is  still available via the getBlockPosition() method if you need it). This results in cleaner, smaller code.

The old way is Modules inherit from a base class called MpBase, and have a subProcess with two arguments like:

In this case use macro SET_PROCESS.

The new way is your module inherits from MpBase2, and has a simplified subProcess like:

void subProcess(int sampleFrames);

 in which case you use SET_PROCESS2. (these are a few other small differences too. You can check the example code to see both flavours of module).

Hope that helps,

jeff


Read more: syntheditforum.boards.net/post/new/305#ixzz3yTWKur2k