1 |
<meino.cramer <at> gmx.de> writes: |
2 |
|
3 |
OK, one last trick, that will work with a coax camera. |
4 |
A coax output camera, can be connected to either |
5 |
a h.264 encoder/mux (standard industry equipment) |
6 |
or to a pci card that has external coax inputs. |
7 |
You can then put a coax splitter (a mechanical tee) |
8 |
and run the camera output to 2 differnet computers. |
9 |
One encodes and records (writes to) the HD, then |
10 |
other for viewing. Hokey, but we used it to test |
11 |
the encoding delays of various video surveillance boxes. |
12 |
Camera's that output h.264 direclty, usually use |
13 |
a custom encoder that will differ from vendor to vendor. |
14 |
Vendors do this because each algo, code_block and patent |
15 |
is managed my the MPLA and vendors engineer what to put |
16 |
inside of a video camera that outputs h.264 by playing |
17 |
"what if" with a myriad of offerings directly or indirectly |
18 |
from software vendors. |
19 |
|
20 |
It you can, a video camera with coax outputs is best and you |
21 |
can run your own h.264 encoding on a workstation or a |
22 |
stand alone video encoding board. |
23 |
|
24 |
Probably too much work for your needs, methinks....... |
25 |
|
26 |
I have threatened to pick up the zoneminder code and fork |
27 |
it, as have others, but I just dont have the time for that. |
28 |
It's a large effort to say the least. |
29 |
A google summer of code genius could/should do that, because |
30 |
support for h.264 and V8 (media-libs/libvpx) would be very, very |
31 |
keen, imho added to ZM. V8 is superior to h.264 and is |
32 |
not patent encumbered. |
33 |
|
34 |
sorry I'm not more help, |
35 |
James |