Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't change capture modes (or totally clueless) (or both) #75

Open
ijh-friendlys opened this issue Feb 18, 2015 · 2 comments
Open

Can't change capture modes (or totally clueless) (or both) #75

ijh-friendlys opened this issue Feb 18, 2015 · 2 comments

Comments

@ijh-friendlys
Copy link

Hi we are having trouble getting the drivers to work with a newly acquired 16CH OEM MPEG4 card.

End project destination is to deploy this with motion and we are happy to use the MJPEG support.

We have had some limited success (in that we have captured images) but cannot get a stable frame from our cameras - this is the same pulling from /dev/video0 using mplayer (as per the FAQ.md and with more options) or /dev/video1 using motion.

Both the on-CD drivers and latest pull have been compiled without issues using Centos 6.6 with 3.10.69 kernel from Epel LTS. Some media libraries have come in from rpmforge but otherwise we are using CentOS or EPEL stocks.

Our outputs
01-20150218100331-01
00000048
both feature a rolling mismatch of the frame, as does using mplayer to put video onto an X11 window.

To my limited understanding, this seems to be capturing with the wrong number of scanlines (i.e. PAL/NTSC mismatch). Although we are UK, we believe the camera is in NTSC mode - we have them working in a Windows box and the screenshots it produces are 320x240 indicating NTSC? (though of course that could be the god-awful software on that box!).

Whatever option we specify for norm (or resolution) in motion.conf or mplayer's -tv params it still seems to record in 352x240 (or 704x480) but never a 320 multiple (generally spewing warnings about the need to change resolution) - is this the cause of our issue? Can it be configured?

We are also only getting mono output from the colour cameras, but likewise I assume this could be the wrong norm??

I appreciate that (in the first instance) this may be more appropriate as a Support Forum issue, but the URLs provided are all down at the moment. Any feedback appreciated: happy to post extra output as required.

@curtishall
Copy link
Member

The cameras appear to be PAL, you need to pass video_type=1 to the module:

http://help.bluecherrydvr.com/spaces/manuals/buckets/1469/lessons/26448-Using-PAL-cameras-with-Bluecherry

@ijh-friendlys
Copy link
Author

Curtis, thank you so much for a simple, illuminating and successful
reply!

I have also now recognised a couple of bits of stupidity in what I asked
the first time.

Wonderful support: only comment would be that it might be worth adding
the PAL support snippet into README.md or FAQ.md of the drivers and/or
providing a simple bash script to do the same thing within the util
folder...

Thanks again!

On 2015-02-18 12:56, Curtis Hall wrote:

The cameras appear to be PAL, you need to pass video_type=1 to the module:

http://help.bluecherrydvr.com/spaces/manuals/buckets/1469/lessons/26448-Using-PAL-cameras-with-Bluecherry [1]

Reply to this email directly or view it on GitHub [2].

Links:

[1]
http://help.bluecherrydvr.com/spaces/manuals/buckets/1469/lessons/26448-Using-PAL-cameras-with-Bluecherry
[2]
#75 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants