OK people, 0 latency monitoring is different than having actual 0 latency. By 0 latency monitoring they mean that you can monitor your inputs from the audio interface and send them right back out through your outputs with no delay. This is usually a dry signal, meaning if you have a reverb effect on input 1 through sonar, when using 0 latency monitoring, the reverb effect is not going to be present, because the signal is being sent back out just as it comes in. If you use sonar's input echo monitoring, the effect will be there, but you'll have some latency, whether it be a few miliseconds, or an actual second or so, there will be latency as the signal goes in, is mixed with the effect or ran through it, and then comes back out. That entire process which consists of turning analog signla into digital (sometimes), sending the digital signal to ram for processing, running the digital signal through whatever effects are on the track, and then being sent back from ram to the audio interface, the interface converting it to analog and then sending it out to the speakers. Most of this happens instantly, but the bottleneck occurs in the signal path in the computer.. The reason why hardware for the most part doesn't have this issues is because they use circuits and filters etc, this happens instantly, just like electricity flows. When it comes to soft synths playing back from the computer, there can be very low latency, but 0 latency is probably impossible. The process of 0 latency monitoring doesn't apply for soft synths, only for inputs from the card. When playing soft synths, it is up to your computer to speedily get the signal/sound from the soft synth to the digital/analog converters for them to reproduce the sound to your speakers. When you have a long pause between playing a note and hearing the sound, that means your computer is taking too long to deliver the signals to the interface for playback. As mentioned various times in different of my messages, this can be dependent on a few things. If you hear crackling while holding notes or while sound is playing, it might mean that you have a buffer problem, or your computer can get the signal to the sound interface in a fast enough manner/time, but it has to work extremely harder to do this and some components (chipset, RAM, CPU) can not keep up with the load. There's way more to talk about here, such as bios configuration and how your components are handled by the bios/OS and drivers, tweaks and configurations, but..........
HTH, D!J!X! -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andy B. Sent: Monday, September 20, 2010 9:37 AM To: 'JSonar -- JAWS Scripts for Sonar discussion list' Subject: Re: [Jsonar] latency please help This is wierd. You have a faster better computer than I do and The only problems with Dimension Pro I have are the strings and pianos? How does that work? And even then, I can get them to work sometimes... -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of matthew shifrin Sent: Monday, September 20, 2010 7:53 AM To: JSonar -- JAWS Scripts for Sonar discussion list Subject: Re: [Jsonar] latency please help Dimension pro always pops and crackles no matter what sound I'm on. This also happens while playing Sonar sample content. This is strange, since it states in all the reviews that with the audiophile 2496 you'd have 0 latency Monitoring. I guess not. What system would you reccommend? Matthew _______________________________________________ Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org. Jsonar mailing list [email protected] http://jsonar.org/mailman/listinfo/jsonar_jsonar.org _______________________________________________ Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org. Jsonar mailing list [email protected] http://jsonar.org/mailman/listinfo/jsonar_jsonar.org _______________________________________________ Find JSonar and Sonar FAQs, articles, guides and downloads at jsonar.org. Jsonar mailing list [email protected] http://jsonar.org/mailman/listinfo/jsonar_jsonar.org
