Page 1 of 1
UDPsockerror
Posted: Fri Aug 31, 2007 04:40
by djdiego71
Anybody can help us with this error?
Using vidnet, when the vidnet source is used on client resulme, crash in the host with this error: Exception UDPSockError in module resolume at 000D42Ae. Null Remote Address.
??????!!!!!
What this mean?????:(:(:(:(:(
XP SP2 version are used without firewall. Avast! antivirus installed.
[Edited on 31-8-2007 by djdiego71]
[Edited on 31-8-2007 by djdiego71]
Posted: Mon Sep 03, 2007 20:35
by djdiego71
For 1 day my Resolume work fine with vidnet, but my XP version (SP2 Extra-Lite) dont work with my two capture cards then I did a format and resintall a fresh, complete and normal version of XP SP2.
Now, vidnet don't work again (but my capture cards yes).
The error is in kernel32.dll on the computers that send video, when I put the vidnet source on a deck.
Why???? Why? Why?..........

:(:(:(:(
Posted: Mon Sep 03, 2007 21:10
by frederico
kernell32.dll got something to do with how windows managed the memory. (from google)
no pc expert here
but google can help!;)
Posted: Tue Sep 04, 2007 23:43
by djdiego71
OK, now is working, after update the XP SP2 system with the latest hotfix.
Posted: Sat Sep 08, 2007 02:57
by djdiego71
mmmm... and really not working well... for only some minutes works, then crash resolume (remote sender, not client)...

Posted: Thu Sep 13, 2007 11:54
by Stickman
I use VIDNET a lot
Sometimes it crashes, but usually when I've overloaded one of the PC's.
Something I've found usefull is to open windows explorer on each PC, navigate to a folder on the other PC (ie a mapped network drive), and leave it open whilst using resolume.
It doesn't prevent VIDNET hanging, but, has reduced the number of network errors / connection timeouts.
Also, if VIDNET appears to hang then I ALT-TAB to windows explorer (which doesn't affect resolume output) and try to navigate around the map'ped drive / connection... sometimes this get's it working again (but only sometimes).
If explorer won't navigate then VIDNET usually won't come back without exiting resolume - sometimes even a complete PC re-start is required.
On the whole I still prefer using VIDNET
Re: UDPsockerror
Posted: Sun Aug 10, 2008 23:47
by Rags
nice tip will try this, as we have beeen having the same problem with Vidnet crashing the pc we are trying to stream to.
we are aslo having issues with one 1 pc being able to see the other pc eg resolume can only stream in one directions, have tryed using fresh installs onf XP using gigabit hub & network cards,
the main issue is vidnet never works properly.... =[
Re: UDPsockerror
Posted: Mon Aug 11, 2008 10:34
by Rags
yer just tryed opening up a network share on both PC's to get the vidnet working in the direction that we want but it is still not showing up on the pc that we want it to and on the pc that it dose show on, it's still crashing resolume and PC.
Duno if this is worth trying to fix or 2 wait for V3 to be released.....
Re: UDPsockerror
Posted: Tue Oct 07, 2008 23:20
by alexius420
Im having same problem, the computer i want to send video from, is not showing up on the vidnet on the computer that i want to broadcast from. I can see my main computer ( the one that does the actuall projection ) on the computer that i want as my " side car ".
Its backwards .....arggh
How do i get it to flow the right way ?
Re: UDPsockerror
Posted: Tue Oct 14, 2008 16:07
by alexius420
Anyone still reading this thread?