search for: 23ms

...ppeer' is now Reachable. (29ms / 2000ms) [Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (21ms / 2000ms) [Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (23ms / 2000ms) [Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (21ms / 2000ms) [Mar 12 10:17:27] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (29ms / 2000ms) [Mar 12 10:17:27] N...

I just thought of something: Given the maximum supported network packet size, and the minimum number of channels (probably stereo) for a FLAC broadcast stream, it should be possible to calculate the absolute longest time that a single network packet could span. Once you know that time, you could simply double it, and then make sure the streaming client always buffers up at least that

....x.x.x (x.x.x.x) 56(84) bytes of data. 64 bytes from x.x.x.x: icmp_seq=1 ttl=64 time=13.1 ms 64 bytes from x.x.x.x: icmp_seq=2 ttl=64 time=20.0 ms 64 bytes from x.x.x.x: icmp_seq=3 ttl=64 time=20.0 ms 64 bytes from x.x.x.x: icmp_seq=4 ttl=64 time=20.0 ms # tc qdisc change dev eth0 root netem delay 23ms # ping x.x.x.x PING x.x.x.x (x.x.x.x) 56(84) bytes of data. 64 bytes from x.x.x.x: icmp_seq=1 ttl=64 time=22.2 ms 64 bytes from x.x.x.x: icmp_seq=2 ttl=64 time=29.8 ms 64 bytes from x.x.x.x: icmp_seq=3 ttl=64 time=29.1 ms 64 bytes from x.x.x.x: icmp_seq=4 ttl=64 time=30.0 ms # uname -a Linux yyy 2...

...he main problem is in the Ogg layer, in my opinion. Imagine this extreme use-case with __completely made up__ numbers. This is a scenario where the server is encoding to FLAC on-the-fly from a raw PCM input, either from disk or a live stream. Let's say the FLAC block size is 1024 samples, or 23ms at 44100 Hz. Let's say each silent block compresses to 1 byte. Let's also say that the Ogg packeting layer wants 4096 bytes before creating a page. Again - these numbers are completely made up, but illustrate the point. In this example, it would take 95 seconds of digital silence before...

...g layer, in my opinion. > > Imagine this extreme use-case with __completely made up__ numbers. ?This > is a scenario where the server is encoding to FLAC on-the-fly from a raw > PCM input, either from disk or a live stream. > > Let's say the FLAC block size is 1024 samples, or 23ms at 44100 Hz. > Let's say each silent block compresses to 1 byte. ?Let's also say that the > Ogg packeting layer wants 4096 bytes before creating a page. ?Again - > these numbers are completely made up, but illustrate the point. ?In this > example, it would take 95 seconds of dig...

I can successfully get the contacts from google using OAuth gem in rails. my gmail configuration is : :google=>{ :key=>"***", :secret=>"***", :expose => true, :scope=>"https://www.google.com/m8/feeds/" } now i want to get contact from yahoo and hot mail. How to get that contact I have given following configuration in my

...gnal qemu 24614 [2007-10-19 18:02:57 4489] INFO (__init__:1094) SUSPEND shinfo 000fffff [2007-10-19 18:02:57 4489] DEBUG (__init__:1094) Written done [2007-10-19 18:02:57 4489] INFO (__init__:1094) delta 1231ms, dom0 24%, target 9%, sent 0Mb/s, dirtied 2Mb/s 101 pages 7: sent 101, skipped 0, delta 23ms, dom0 95%, target 0%, sent 143Mb/s, dirtied 143Mb/s 101 pages [2007-10-19 18:02:57 4489] INFO (__init__:1094) Total pages sent= 986073 (0.94x) [2007-10-19 18:02:57 4489] INFO (__init__:1094) (of which 0 were fixups) [2007-10-19 18:02:57 4489] INFO (__init__:1094) All memory is saved [2007-10-19 18:...

The standard controller that has been recommended in the past is the AOC-SAT2-MV8 - an 8 port with a marvel chipset. There have been several mentions of LSI based controllers on the mailing lists and I''m wondering about them. One obvious difference is that the Marvel contoller is PCI-X and the LSI controllers are PCI-E. Supermicro have several LSI controllers. AOC-USASLP-L8i with the