search for: _tick

...x_jitter_buffer.c wrapper seems to maintain (buffer?) one packet-frame ("current_packet") in addition to the packets already tracked by the JitterBuffer itself. Why is this necessary? Correspondingly, how is the internal JitterBuffer state affected by calling jitter_buffer_get (and _tick) before jitter_buffer_put has a chance to deliver the first packet of a stream? Should this be avoided? jitter_buffer_get can return JITTER_BUFFER_INSERTION and JITTER_BUFFER_MISSING. In both situations speex_jitter_buffer.c makes the codec interpolate a frame. How are these conditions diffe...

Greetings, Launching the virt-manager yeilds following error Error polling connection 'qemu:///system': internal error Cannot find suitable emulator for x86_64 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 440, in _tick conn.tick() File "/usr/share/virt-manager/virtManager/connection.py", line 1414, in tick newNets, self.nets) = self._update_nets() File "/usr/share/virt-manager/virtManager/connection.py", line 1277, in _update_nets lookup_func, build_class) File "/usr/sha...

Hi, I see you're changing the jitter buffer around quite a bit. Could you let us know when it's ready for general testing? (At the moment it doesn't handle missing packets at all) Best wishes, Thorvald

...st "data" for the jitter buffer. By that I mean, just a log of how you are calling it. More specifically: - Every time you call _put(), print the timestamp and span of the packet - Every time you call _get(), print the desired_span argument (it's a new argument) - Every time you call _tick(), with no argument. For example, the file could look like: PUT 1000 100 GET 100 TICK PUT 1100 100 GET 100 TICK ... That would help me make sure that the jitter buffer works for your case. I actually encourage everyone using the jitter buffer to do the same. Cheers, Jean-Marc

...inds the packet, decodes the first frame it contains, and keeps the rest for the next time. If you only use one frame per packet (which most people do), it's not necessary to do that. > Correspondingly, how is the internal JitterBuffer state affected by > calling jitter_buffer_get (and _tick) before jitter_buffer_put has a > chance to deliver the first packet of a stream? Should this be avoided? At this point, this should probably be avoided (I've heard of problems when doing that), but eventually this is a case the jitter buffer should be able to handle. > jitter_buffer_...

...6.x86_64 #1 SMP Fri Dec 23 02:21:33 CST 2011 x86_64 x86_64 x86_64 GNU/Linux Error polling connection 'qemu:///system': internal error Cannot find suitable emulator for x86_64 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 440, in _tick conn.tick() File "/usr/share/virt-manager/virtManager/connection.py", line 1414, in tick newNets, self.nets) = self._update_nets() File "/usr/share/virt-manager/virtManager/connection.py", line 1277, in _update_nets lookup_func, build_class) File "/usr/sha...

...itter buffer. By that I mean, just a log of how you are > calling it. More specifically: > > - Every time you call _put(), print the timestamp and span of the packet > - Every time you call _get(), print the desired_span argument (it's a > new argument) > - Every time you call _tick(), with no argument. > > For example, the file could look like: > > PUT 1000 100 > GET 100 > TICK > PUT 1100 100 > GET 100 > TICK > ... > > That would help me make sure that the jitter buffer works for your case. > I actually encourage everyone using the jitte...

...rror when I try to connect "QEMU" from the Virtual Machine Manager Error polling connection 'qemu:///system': internal error Cannot find suitable emulator for x86_64 Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 440, in _tick conn.tick() File "/usr/share/virt-manager/virtManager/connection.py", line 1414, in tick newNets, self.nets) = self._update_nets() File "/usr/share/virt-manager/virtManager/connection.py", line 1277, in _update_nets lookup_func, build_class) File "/usr/sha...

Hi, I have successfully installed libvirt-.0.10.0 from source ./configure make make install How can I check that if libvirt-python is installed? Search the folders, it seems there is no such file [root@tiger ~]# find /usr/ -name libvirt-python [root@tiger ~]# find . -name libvirt-python [root@tiger ~]#   Regards, Mahmood

...installed all of them. However when I start virt-manager, I get this error Error polling connection 'qemu:///system': internal error Cannot find suitable emulator for x86_64 Traceback (most recent call last):   File "/usr/share/virt-manager/virtManager/engine.py", line 440, in _tick     conn.tick()   File "/usr/share/virt-manager/virtManager/connection.py", line 1422, in tick     newNets, self.nets) = self._update_nets()   File "/usr/share/virt-manager/virtManager/connection.py", line 1285, in _update_nets     lookup_func, build_class)   File "/usr/sha...

Am 08.10.2013 14:46, schrieb Stefan G. Weichinger: >> Try enabling the flag, re-emerging the package, setting the logs and >> then reproduce it again. Check the logs and you should see why it's >> disconnecting. The docs say that libvirtd has to listen on the TCP port ... checked that: # netstat -alnp | grep libv tcp 0 0 0.0.0.0:16509 0.0.0.0:*