Insert synths are not in synch when recorded.

Did you have snap to grid on when you entered the notes?   If not, then depending on your settings in staff view it can look as though you have entered the notes in a neat orderly fashion(quantized) but it will actually put the notes in precisely where you entered them but show at the resolution setting you used.  Quantizing may resolve it with some tweaking.  If you check what you entered in piano roll view you can get a much better idea of where the notes actually landed. 

It is a good idea to have you display resolution, snap to grid settings, and note length the same or better still do it in PRV where what you see is what you get.

Well - I will behind my DAW within a few hours, so I can test this out around then. In the mean time - some questions...

I do not know how familiar you are with music software, so I want to ask some questions that can be very obvious if you have some experience.

First - I see you are using dropzone. This is essential a sample player (if my brain does not play tricks with me). Are you using a sample file? If so - are you sure the sample does not have a "build-in" attack (especially some free pad samples have this problem). If you are using a attack setting in dropzone on top of this this can add up, giving the impression the sound lags behind. In reality it does not, but the sound level at attack time is just too low to be heard..

Secondly - are you using some FX in your instrument track? Especially a delay or reverb can play tricks with you if you forget to mix the dry and wet signal (especally a delay with only wet output on a instrument FX bus will give weird timings).

Sorry if I am stating the obvious, but it is nice to rule out any "noise".

Last question - is this only happening when you are using the staff view for input? If you have no problems using the piano roll for input, there is something wrong with the staff view I guess.

Thanks for the responses. On a side note i forgot to mention another insert synth. It was the "PSYN II" insert synth.  Heres the weird thing. The PSYN II plays in synch perfectly with the session drummer 3 but they don't play in synch with dropzone or square I. But dropzone and square I play in synch perfectly together. To test it out I started fresh on a new project even on staff view and step sequencer they were off. Its definately not an attack or delay issue because these are samples i created myself and i made sure there were no gaps, silences, or spaces in front of the sample. So when you strike the keyboard you hear the sample right away with no delay. brundlefly's comment may be it. I may have to take your advice and try the timing offset option. Unless theres something else i can investigate. Could it be a clock speed issue in preferences?

PSYN II plays in synch perfectly with the session drummer 3 but they don't play in synch with dropzone or square I. But dropzone and square I play in synch perfectly together. 

That's because PSYNII (a DXi)and Session Drummer (either DXi or VSTi, depending on your SONAR upgrade path) are both native x64, and do not use Bitbridge, while both Dropzone and Square 1 need to be bridged, and will be delayed the same amount by Bitbridge.


I can virtually guarantee the Bitbridge bug is what's causing this.

(and certainly won't wont take part in the good/bad 64/32 discussion)

That isn't even an issue here.  The issue for me would be to get the most work done with the least effort.

Both versions of Sonar are supplied and behave impeccably alongside each other for the cost of the tiniest amount of disk space, get the best of both worlds why not?

Bridging by it's very nature is a kludge and will have matured fully when it is no longer required.

64 bit plugins are the answer, until they are available one can run 32 bit ones just swell in a 32 bit app.

EDIT: Using the Timing Offset on the MIDI Track Inspector with a negative value might be the least disruptive way of solving the problem for the time being

brundlefly  


 

brundlefly

fali

brundlefly





EDIT: Using the Timing Offset on the MIDI Track Inspector with a negative value might be the least disruptive way of solving the problem for the time being, but I recommend getting JBridge; Google it.

How do i do that? On the track inspector the only thing i see which seems useful is when i click on clips. Then i choose "properties" and you see a "start" option which defaulted at 1:01:000. When i change it to 1:01:240 the psyn II plays in synch with dropzone. However that is similar to the nudge option. It doesn't change the timing when i add anything new to the track. I want the entire track to automatically be set to that delay offset. So when i add any additional recordings to the track i don't have to edit the delay again. Sorry if i sound like noob, but i am one. Sorry i did forget to mention i am using the 64 bit system. So i could download the 32 bit version of sonar x1 with no conflict with the 64 bit version which i have currently? I could try that too.

See the Time+ field at the lower right corner of the Inspector for a MIDI track (or the MIDI tab of an Instrument track). Entering a negative value (in ticks) will cause everything in the track to be played back early by that amount.

You can install the x86 version of X1 from your original download. The installer prompts for what version you want to install.

Thanks. I didn't notice the other tabs located on the bottom of the inspector.  The timing offset option will help me alot in the future.  I didn't try downloading the 32 bit version but in my opinion this is best quick fix option until they fix the bug.  Thanks for everyone's help.