Greetings, and first of all thanks to the author of this zmodopipe software.
I am not sure this falls under the proper scope of zmodopipe usage, but it seems this thread is about the only place to ask for help.
I am attempting to use zmodopipe for a slightly different purpose than with zoneminder, which I believe should work, and am having problems.
I do not have zoneminder installed on my laptop because I do not want a webserver running on it. (When another computer is available, I do plan on using zmodopipe and zoneminder on it)
For now, the zmodo device is sufficient for my needs of recording security camera footage. However, it is in another physical building and not easily accessible, especially via linux.
So I would like to be able to intermittently pull up live camera footage on my laptop for casual observation, i.e., not having to leave my desk and look out the door every time the dog barks to see if I have visitors.
I have successfully made zmodopipe connect to my DVR and when I use the -v command line option, I see a steady and reliable series of dots to indicate progress.
(zmodopipe works! thank you very much!)
I then attempt to view the fifo pipe with VLC, and initially I get footage. However, after a few seconds this footage stops and I see an interruption reported in the terminal where zmodopipe is running.
VLC closes and the zmodopipe dot progress resumes.
Code: Select all
Ch 2: Received signal: 13
Ch 3: Pipe closed: Broken pipe
Ch 2: Ch 3: Connect result: 0
Ch 2: Ch 3: Send result: 68
If I use -t 10 in the zmodopipe command line, it seems to circumvent this failure for a short time, but VLC eventually still bails after a minute or couple minutes.
In my observation, when I have tried to use ffmpeg between the two (and I really don't know how to properly), the progress dots in the zmodopipe terminal stop, or stop and restart, and I haven't been able to get anything else to work. Everything I try "stops the dots" and yields no playback, and/or yields ffmpeg errors, except for one combination of VLC and zmodopipe.
Even when I just try to use ffmpeg to make a playable video file, it suffers from the "stop the dots" failure.
First suspicion is that two programs are somehow fighting over the /tmp/zmodo2 file, but I don't know if that's
really what is happening.
Here is the command line that I use when starting zmodopipe
Code: Select all
./zmodopipe -s 192.168.1.100 -p 18600 -c 2 -c 3 -n zmodo -u mobile -a 123456 -m 1 -t 10 -v
with it's output, which is consistently a repettiion as follows:
Code: Select all
Ch 2: Ch 3: Connect result: 0
Ch 2: Ch 3: Send result: 68
..............................................................Main: Child 8119 returned: 14
Ch 3: Failed to create pipe: File exists
Ch 2: Ch 3: Connect result: 0
Ch 2: Ch 3: Send result: 68
and here is the command line that I use to view it via VLC
with it's output, which is always similar to:
Code: Select all
VLC media player 2.0.3 Twoflower (revision 2.0.2-93-g77aa89e)
[0x21ba108] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
[0x326c9e8] h264 demux error: this doesn't look like a H264 ES stream, continuing anyway
[0x3295a18] main input error: Invalid PCR value in ES_OUT_SET_(GROUP_)PCR !
[h264 @ 0x3f79220] slice type too large (2) at 0 0
[h264 @ 0x3f79220] decode_slice_header error
[h264 @ 0x3f79220] no frame!
[0x3295a18] main input error: ES_OUT_SET_(GROUP_)PCR is called too late (pts_delay increased to 705 ms)
[0x3295a18] main input error: ES_OUT_RESET_PCR called
[0x3295a18] main input error: ES_OUT_SET_(GROUP_)PCR is called too late (pts_delay increased to 754 ms)
[0x3295a18] main input error: ES_OUT_RESET_PCR called
[h264 @ 0x3f78d80] slice type too large (2) at 0 0
[h264 @ 0x3f78d80] decode_slice_header error
[h264 @ 0x3f78d80] no frame!
How can I correct this, or is there a more reliable way to use zmodopipe to play a stream into a simple video player?
I do not require playback via VLC in particular, it could be any player that works on Debian 7 as far as I am concerned.
I would like the option of leaving it streaming for long periods of time, for example as I watch TV or read a book, instead of just a minute or two before it crashes.
Again, thanks to the author, and to anyone who can instruct me.
and happy new year