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]
UDPsockerror
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?..........
:(:(:(:(
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?..........

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
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
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.... =[
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
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.....
Duno if this is worth trying to fix or 2 wait for V3 to be released.....
-
- Posts: 14
- Joined: Wed Jan 16, 2008 21:28
Re: UDPsockerror
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 ?
Its backwards .....arggh

How do i get it to flow the right way ?
-
- Posts: 14
- Joined: Wed Jan 16, 2008 21:28
Re: UDPsockerror
Anyone still reading this thread?