Midi Latency in X1

which driver mode are you using herb?  what are your buffer settings for your focusrite?

I was all up in the settings last night... trying one thing after another that I thought might affect it. 

I'm running only a few cake default reverbs and eq's so the processing should not be an issue. 

I'm running the Cakewalk sound center piano also not a "heavy" synth. 

ASIO is the driver, and buffers are set to 256 which I did set to a lower number, even going as low as 5 just to see....and I got audio drops on 5.... (256, 200, 100, 20, 5) << settings I used. 

As I stated above..... I have NO latency that is noticeable when the project is stopped. I can play and hear it when I touch it. It's when the time line is moving for either playback or in record that I'm getting this latency.

I can close the project, re-open it in MC4 and after the warnings that some aspects may not play correctly, I can then play the same synth, in the same project with NO noticeable latency.  

I don't mind closing one DAW and opening another but ultimately, I'd like to get it all done in X1. 

Since it works in MC4 but has latency in X1, I'm thinking it's a setting that is not set up properly somewhere that deals with midi/latency/buffers. 

BTW: my latency slider is grayed out and I think the number also grayed out is under 5ms. 

I suspect delay compensation. Try the PDC button in the mix module. Does the delay happen in a project with only the synth in it? I had a similar problem when I left Ozone on the master bus. Cheers, Peter.

That is what I'm planning to try next... open a new project in X1 and import the audio tracks into the new project....then pop in a synth and see what happens. 

I tried it with several synths.... Cakewalk Sound center and Kontakt4, both had the latency in the run mode, neither had latency in the standby mode. 

Maybe this is a Cake support question...a possible bug. 

I'm also going to create the new project in MC (and probably first) since when I opened it in MC (this morning)  after having had it open in X1, and it was created in Sonar, it had the latency in MC as well. That is unusual since I never had latency issues in MC...ever! Not even once.

I'm thinking it might be the settings that came with the file (bundled from another sonar user) so by creating the new project and only importing the audio files, I can eliminate any settings that may have come for the ride. 

I will dig into this and take it to the bakers if needed. 

These are plugs and synths that work "latency free" in Music Creator. 

I did not have time yesterday to load a new project and drag the audio in..... maybe today.... for sure this weekend. 

ok...so I look for and shut off ADC

F12 toggles snap on/off, so it isn't that one.

Interesting thread though - keep us informed Herb.

So I looked up the ADC thing and followed the directions. The default was set to 250ms.... the directions suggested an increase so I bumped it to 1000 ms...or 1 second.  No immediate reaction difference in the existing project


So far, I opened a new project in MC4 and everything is latency free. 

I saved and closed it in MC and opened it in X1....

Then I open in X1.... waaa laaa... no latency... add a new soft synth and play along with the previous synth recording..... perfect ... no latency.


I'm guessing that there is something in the project that I received from another caker (working on the mastering/sweetening) that is causing the latency. 

Yeah it has to be something in that project that keeps the latency as an issue..... I opened a new project in X1.... dragged in the exported wave from the sweeting project and popped in a soundcenter piano..... man, it's rock solid.... no latency.... 

Problem solved as far as I'm concerned. Thank you all for the advice on where to go hunting for the problem.... I might did in to the project when I have some spare time to see if I can track it down.... maybe not... move on since I know what the deal is now. I was planning to drag all the waves one by one into a new project and delete the old one.... I figured that would also eliminate the problem setting. 

Again.... solved.