Is this a bug?..yes.. Is it annoying?....yeah,
specifically because the ramifications are more than just the use of Maschine.
As additional information for users (and cakewalk) i will add that (assuming a 1 measure count in) this delay is:
a. Present when ANY audio or midi track in the project (not just maschine) is being recorded.
b. not in the tracking or sequencing of maschine... the position marker of maschine runs correctly to now time of Sonar, and midi input to maschine is registered correctly at now time.
c. represented as an audio delay of one measure from indicated now time.... ie now time = sonar measure 2, maschine indicated measure 2, Sonar maschine audio track plays measure 1.
had this been an issue with simply recording of a Maschine track then a simple workaround would be to record directly into maschine using Maschine rec button and have Sonar in Play mode.. however this bug means that the rhythm track is always one measure behind whenever
any track is being recorded.... effectively this means that to use Maschine fully as a VST you must sacrifice the entire project to have zero count in for the entire duration of recording....
so the workarounds are:
a) No record count-in.
b) use midi metronome : cannot be directed to soft-synth - needs external midi synth or PC midi synth (sluggish)..
c) Record Maschine as stated above (Maschine REC/Sonar PLAY) and then freeze Maschine VST on all other record operations...
d) Use Maschine standalone and drag/drop loops or export tracks to Sonar.
none of these methods are efficient or ideal.. so add my +1 to "please please address this"