Posted: Tue Jan 31, 2006 09:52
Hey I'd be happy to discuss vidNet with any of you at dave@inside-us-all.com
It was designed to be used by VJ App developers, with a long term goal of getting multiple VJ Apps supporting the same standard. For commercial applications it has a development licence charge to go with it, negotiated on a per customer basis.
The protocol is very low on processor usage [DMA transfer direct from host memory to network adaptor buffer] and very low on latency. It was designed specifically for performance video, where as most streaming protocols are designed for low bandwidth, which results in high processor load.
it is based around a windows dynamic link library, written in c. I don't use java so I'm not sure if/how it would be compatible, maybe you know more about this.
Edwin is right, the documentation is currently pretty poor, but if I had further interest in the protocol I would update the documentation accordingly.
hope the info helps, best regards
Dave Green
inside-us-all
It was designed to be used by VJ App developers, with a long term goal of getting multiple VJ Apps supporting the same standard. For commercial applications it has a development licence charge to go with it, negotiated on a per customer basis.
The protocol is very low on processor usage [DMA transfer direct from host memory to network adaptor buffer] and very low on latency. It was designed specifically for performance video, where as most streaming protocols are designed for low bandwidth, which results in high processor load.
it is based around a windows dynamic link library, written in c. I don't use java so I'm not sure if/how it would be compatible, maybe you know more about this.
Edwin is right, the documentation is currently pretty poor, but if I had further interest in the protocol I would update the documentation accordingly.
hope the info helps, best regards
Dave Green
inside-us-all