On 5/29/07, <b class="gmail_sendername">leon zadorin</b> <<a href="mailto:leonleon77@gmail.com">leonleon77@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Hmm, it seemed to be sending fine when I got in today implying that it was<br>> running over the (long) weekend. I restarted it with a higher TTL, and I'll<br>> try and keep it running as much as I can (I can guarantee 10am EDT - 6pm
<br>> EDT, sorry that that's an awful time for you guys in Australia, heh).<br><br>Well, some news...<br><br>Firstly, I am able to receive and see your stream here in Birsbane,<br>Australia :-) ... Although the whole thing is rather dark - but I
<br>presume that it is nighttime over in NY (it is noon here :-) and there<br>are no lights "on" in your office :-)</blockquote><div><br>Great! Glad to know it's working, thanks. I guess if you want to see some activity or light you should try checking it earlier in the morning, like 8am-11am your time which is 6pm-9pm here, while it's still light outside. I'll point it out a window before i leave :)
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Both the sender and receiver are 91M; they're from checkouts I did on
<br>> Thursday/Friday.<br><br>91M - the "M" part is interesting, what does<br>cd ag-media<br>svn diff >> leonlog3<br>say? Basically, the "M" means modified... it could be nothing (e.g.<br>there are some runtime generated files which should not be a part of
<br>svn repository), but it would be interesting to see anyway (i.e. if<br>possible, email me the leonlog3 file)...</blockquote><div><br>The only difference is a #define of the svn revision number in an ffmpeg revision file:
<br>Index: Ffmpeg/Revision6182/version.h<br>===================================================================<br>--- Ffmpeg/Revision6182/version.h (revision 91)<br>+++ Ffmpeg/Revision6182/version.h (working copy)
<br>@@ -1 +1 @@<br>-#define FFMPEG_VERSION "SVN-rUNKNOWN"<br>+#define FFMPEG_VERSION "SVN-r91"<br><br>Not sure how that happened but it doesn't seem to be affecting anything.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Now on to your system/logs :-) ... thanks for the log files by the way!<br><br>From leonlog1:<br><br>"libGL warning: 3D driver claims to not support visual 0x4b"<br><br>This could mean that your system is having issues with OpenGL (we use
<br>OpenGL by default for efficient synchronisation with the vertical<br>refreshing of your monitor) so try running vic with "-g" option:<br><br>./vic -g IP/PORT</blockquote><div><br>I was trying the ./runDV script before, so I was already using -g. (I just tried it with only -g and the same freezing happened)
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">This will instruct the vic not to use OpenGL for syncing to VBlank (so<br>in case it was OpenGL issue that made vic "pause" and wait
<br>indefinitely for a vertical retrace - it will be avoided this time)...<br><br>Minor side-note: it appears that you are using an Intel graphics card<br>with i810 driver - this combination will not have proper accelerated
<br>rendering (XVideo's "Overlay" is not sufficient, we need "Blitter" or<br>"Texture" and even then, the newest intel drivers are still rather<br>"slowish")...<br><br>... current recommended setup would be nvidia card with "nvidia" [
<br>binary / closed-source ] Xorg driver - something as per<br><a href="http://www.vislab.uq.edu.au/research/accessgrid/software/advideo/system_characteristics.html">http://www.vislab.uq.edu.au/research/accessgrid/software/advideo/system_characteristics.html
</a></blockquote><div><br>Yeah, I had a feeling it might have to do with the lack of a decent video card in this machine.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Without the XVideo accelerated rendering vic should fallback to Imlib2<br>(software) rendering... but from log files I don't see it using Imlib2<br>rendering though... (vic would output something like "using Imlib2 for
<br>rendering" or similar) - this could mean that the runtime execution<br>path did not get around to it or that Imlib2 was not included in the<br>build...<br>what does<br>cat ag-media/vic/IMLIB2INCLUDE.H >> leonlog3
<br>say?</blockquote><div><br>#include "../Imlib2/Installed/include/Imlib2.h"<br>And that is a valid path.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
>From leonlog2: Minor side-note: you have 2 vics running (one of them<br>is listed as defunct) so *really* killing it (kill -KILL PID) would be<br>a good thing to try... if this does not help and you end up restarting<br>the machine, then please run the "setSystem" script again (so that
<br>/sbin/sysctl net.core.rmem_max shows ~17000000 value)</blockquote><div><br>I just had to kill the original ./runDV script, that got rid of it. Didn't make a difference with the freezing, though.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If running vic with "-g" option does not help, try<br>./vic -g -i -x IP/PORT<br>and then (if possible) click on the black thumbnail to see if the<br>larger video window comes up... this is not a deployment solution, but
<br>would help with testing...</blockquote><div><br>Hmm, this actually works... but in a strange way. Sometimes, if I leave the main window open and visible for too long (5ish seconds sometimes, this part is inconsistent), it freezes. (Sometimes it doesn't freeze at all) But before it freezes, I can open the video windows (which are receiving the videos fine) by clicking on the thumbnails. If the main vic window is visible/frozen (and trying to render I presume?) the video windows keep on displaying fine but they can't process any input (like s/m/l for resizing). If the main vic window is not frozen, the windows can process input just fine. Occasionally the main window thaws if I leave it open long enough.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Oh and I wouldn't worry about 2 vics running on the same machine,<br>using the same class D (multicalt) address and not seing each others
<br>traffic - I think this is OK (i.e. by design this was never an<br>intended scenario - in fact the original vic (from anl) behaves in<br>exactly the same way - so we have inherited this behaviour)...</blockquote><div><br>
Ah, that's what I thought. Thanks for the clarification.<br><br>--Andrew<br></div><br></div>