Resolume Forum

Hi there
Having a problem with streaming from workstation to workstation. both machines are playing fine 640x480 (indeo 5.1) from ineternal discs, but there is visible delay when using vidnet. (it will jerk 1 or 2 times in 5 sec). very anoying on big screen.
have tried fire wire and gigabit ethernet, but same result.
both machines are 3200 AMD, raptor raids, 2 Gb Ram etc
as I said they can handle easily 640x480.
No Firewalls, no antivirus softwers runing. No routers. (straight card to card connection)
Is this usual limitation with Resolume streaming?
Does bridging firewire and 1Gb ethernet helps (can one actualy achive 1.4 Gbps? I've tried but new bridging connection shows only 1 Gbps.)
Any sugestion or similar experience is more than welcome.
cheers

since no one replyed here are some sugestions for the people with similar problem that I got at vjcentral forum
cheers

-----------------------------------------
Vidnet should support 640 x 480 resolution video data via gigabit Ethernet, but when it was designed and written the gigabit ethernet standard was newly emerging, and therefore it wasn't tested thoroughly. In theory the frame rate is limited only by your choice of network implementation [100 Mbit/firewire/gigabit LAN etc]. It is possible to calculate the possible frame rates mathematically. E.g

320 x 240 x 2 (16bit) = 153,600 bytes
x 8 = 1,228,800 bits

So to achieve a single stream of 25 fps would require 1,228,800 x 25 = 30,720,000 bits [30 Mbit] per second of bandwidth.

using the same calculation 640 x 480 at 16bit should require around 124Mbit & 248 Mbit for 32bit colour. This should be comfortably within the available bandwidth of gigE networks [& firewire, but not 100Mbit]

However, since gigE has become a well established standard I've occasionally noticed the same jittering on resolutions above 512 x 384. I'm not entirely sure why this is.

I suspect it could be a number of things.

1. Other services on the network holding off packet despatch whilst they use the socket buffer.

2. Packetsize exceeding standard packet size and the socket layer breaking the packets up.

3. The physical timing of the packets being sent & recieved from & to resolume.

You could use some kind of network packet monitoring software and analyse what packets are being sent around your network, and shut anything but the vidnet/resolume packets down. That could resolve issue 1.

Issues 2 & 3 would need to be looked at by the developers, so lets try and eliminate issue 1 first.

I'm presuming your running point to point too? once u use a network hub, switch, etc. that too can add timing issues.
-------------------------------------------------------------
Out of interest are you using correct speced cable, point to point needs a crossover cable as sure you know, however some older cat5 cables only supports 10/100 and was superceeded by Cat5e to support 10/1000 as does cat6.

Just worth checking.

Have you tried via a hub and a workgroup? Not sure what difference it would make.

hi superdovla,
We didn't give a reply here yes as we saw the reply you've got on vjforums.
And you got the feedback from Dave wich in fact is the one who developed vidnet so we feel we had nothing more to add.

We will do some testing on higher reseolutions next time he comes over to our studio. We have an idea of using some compression scheme to limit the bandwidth a bit and to see wether that minimizes the stutters/jerks.

Cheers
Edwin

thanks edwin

Hi guys,

most of my materials are 640X480 and never had such problem as you had superdovla.
for me it is a bigger minus for vidnet that if the laptops loose the conncetion, both resolume is crached, so restart is a need on both. why can they not see each other if the connection is already for long time set up?

1st laptop is a Compaq Pressario 3200 series, 1600 MHz Athlon-M processor with a Gforce3 videcard, 2nd laptop is an IBM T42 1,6 GHz Pentium M. ,Video card Radeon 9600. Both laptop with 768 MB of RAM.