similar to: Clocks drift again

Simple streaming is fundamentally flawed this way. "The man with two clocks, does not know what time it is." Your source is clocked from one crystal in your source sound card, and played back on the basis of the clock crystal in the client sound card. There is nothing to say or keep these crystals locked to the same exact frequency, which is REQUIRED to maintain no clock drift. Unless

> In those cases, when you get let's say 1000 packets of 20ms from the mic > you may have only 990 packets of 20ms from RTP incoming stream. > > Thus, before sending outgoing mic/RTP stream, you would wait for 1000 > incoming packets: where last packet in fact arrive 10*20ms = 200ms > after it was supposed to. I have from my experience already seen 4s > of clock deviation

Hi Shridhar, Sample rate conversion is not enough to solve this problem. I have tried this method several months ago. The first step is to measure the difference between sample rate of capturing and rendering. Then resampling (by what you said "sinc interpolation") one signal to eliminate the difference. The frequency step in my experiment is less than 0.1Hz. I have tried speex AEC

Hi On 5.3 i have a situation where some boxes have been 3 or 4 seconds out and restarting ntpd has fixed the issue. What i dont understand is why the clocks did not drift to the correct time when the config seems correct in that restarting ntp did correct the time. Is there something 'special' i need to do in order for the drift to work? $ cat /etc/ntp.conf restrict default

Hi, We have a little over 100 servers, almost all running CentOS 5.7. Virtually all are Dell servers, generally a mix of 1950s, R610s, and R410s. We use NTP and/or PTP to sync their clocks. One phenomenon we've noticed is that (1) on reboot, the clocks are all greatly out of sync, and (2) if the PTP or NTP process is stopped, the clocks start drifting very quickly. If it was isolated to

On 04/13/2011 02:58 AM, Shridhar, Vasant wrote: > I am doing this right now with no problem. I am not using speex for this at the moment though. Group delay is the biggest problem. I implemented a version where the input and output sample rates are known up front. The routine than interpolates between the jitter. This should solve the problem. The crystals used to clock the input and

The time appears to be perfect inside dom0, however all the domU''s tend to have a slightly faster date which gets further out of sync every day. I''m currently using Xen 3.0.3 with Gentoo Linux, under 3.0.2 I had no problems with domU clocks. Are there any known issues which could cause this? I''d strongly prefer not to run ntpd in every domU, having all domU clocks in

Hi all, I am recently using icecast from server streaming, and even though I succeeding setting everything up to have a radio broadcast, I still have a few questions regarding icecast use. First, latency. I have a setup on a LAN, where I can add audio files to the stream, with a python script that automatically send the location of the file to be played continuously. I wanted to measure the

Hi, I've noticed that one of my new servers (new mobo) if drifting slowly backwards in time (in aprox. 24 hours, system time drifts back 5 minutes). I have an ntpd process which is supposed to sync with a lan time server but it's not quite working. So I'm launching a manual ntpdate or ntp-client once an hour and that seems to work. However, suppose I update system time at every hour

Hello Thomas and Karl, thank you for your answer and time. We've tested with several listeners and different connections, using WinAmp and JW Player. For about 15 minutes, everything is ok. After 15-18 minutes, WinAmp starts do blink that "red square" (packet loss or instability), and after about 20 minutes sounds starts to "pop", with small cuts, and then starts to

Hi All, Many Thanks to Underwood for her excellent review of our big trouble which prevent LMS-based AEC algorithms to be used in most computer. Maybe it can be summaried as follows: 1. Different sample rate of sampling and rendering does exists in most low-cost soundcards (In my experiments over more than 20 soundcards, the differences range from 0.5Hz to more than 50Hz when sample rate is set

1. Shouldn''t the GPLPV drivers take care of the (bad) clock drift I''m experiencing in my Windows XP HVM? Or is there some other way around this problem that I haven''t been able to find on Google? How can I tell if the GPLPV drivers are active? I''ve added the /gplpv switch to the boot.ini file and the virtual NIC is definitely using the GPLPV version but other

In reading the Xen list there are frequent postings regarding NTP time drift issues for virtualized guests, correct configurations, etc. We have a solution (no cost) for monitoring time drift of hosts for anyone needing to do so or to determine whether their environment is maintaining time synchronization. For etiquette I am not publishing the information to the list mailing. If interested,

Hello everyone! I been observing some peculiar time drift on my Xen domains (dom0 and domUs). The time (as returned by timeofday) on my domains drifts at an almost steady rate from the real time ( as read from the time stamp counter ). The drift is so constant that it makes me think there should be some simple explanation for it in the way Xen keeps time. Some info about my set up: guest OS:

This must be documented somewhare but I checked the Xen 3.0 manual and the word "clock" doesn''t even exist in it. I checked the FAQ as well. I am running Xen 3.0.1 and an AMD64 CPU. I found that DOMUs time clock drifts ahead. I installed ntpdate and it reports to change the time but it does not. David _______________________________________________ Xen-users mailing list

Dear R-Users, I have the following problem to solve and I wonder if there are means in R that can help me. At irregular time intervals I observe a random walk process, Y, with time-varying drift. I assume that the drift, D, is a (linear) function of some parameter X. The goal is to estimate D(X). I could regress Y_{t+dt} - Y_{t} ~ X, but it's probably not appropriate since Var(Y_{t+dt} -

>> Actually, the jitter buffer in Speex tends to cope relatively well with >> non-synchronised clocks. > > Can you explain why? > > My problem is not at all related to local input/output non-synchronised > clocks: my problem is really between non-synchronised clock between one > PC and another... What happens is that my jitter buffer is designed without any

We have a local time server and all of our machines are pointed at it for the time. How can the clock drift by a day and a half? [root at devserver21 ~]# date Fri Aug 13 14:43:29 EDT 2010 [root at devserver21 ~]# rdate -s 192.168.1.67 [root at devserver21 ~]# date Thu Aug 12 07:02:39 EDT 2010 [root at devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ restrict default nomodify notrap

Hi all, We all know that mismatch between clocks of ADCs of far-end voice and near-end voice is not allowed in a time-domain or frequency-domain LMS based AEC system. It means that capture and render audio streams must be synchronized to a same sample rate. However, I found that this restriction is removed in microsoft AEC from Windows XP SP1. Anyone knows how microsoft AEC do it? This technology

Hello, On a xenserver with several (39) domUs, we experience problems with the system clock of the domUs. The clock seems to drift away several seconds up to two minutes from the dom0 clock. We do have set independent_wallclock=0. According to the docs (i.e. http://wiki.xensource.com/xenwiki/InstallationNotes) that way domUs should use the dom0 clock, but apparently that''s not the case.