Menu
▾
▴
Re: [Motion-user] No picture displayed
|
From: William M. B. <wb...@mm...> - 2007-12-31 03:28:20
|
Ferry,
If xawtv says your camera is on Composite3, that means you have it
connected to the *bottom* connector instead of the *top* connector
as I previously suggested.
You have two choices:
1) Change the camera connection to the *top* (nearest the RCA
"phono plug") (this will change xawtv to have the picture on
"Composite 0"). In this case, change your motion.conf "input 1"
to be "input 0"
2) Leave the connector as it is (so xawtv shows the camera on
"Composite 3"). In this case, change your motion.conf "input 1"
to be "input 3".
Remember, the *top* connector is for "Composite 0" in xawtv, or
"input 0" in motion; the next connector is for "Composite 1" /
"input 1"; the third connector is for "Composite 2" / "input 2"; and
the 4th (*bottom*) connector, which you currently have your camera
connected to, is for "Composite 3" / "input 3".
You can use any of the video devices (in your case /dev/video0,
/dev/video1, /dev/video2 or /dev/video3) for motion, by changing the
"videodevice" line. Any of them will work. No matter which you
use, the camera mapping which I explained above will be unchanged.
Bill
Ferry Sumendap wrote:
> I tested the xawtv and it displayed the picture when
> Video Source=Composite3
>
> But when I tested the motion by trying putting different values on
> parameters :
> videodevice = /dev/video0 UNTIL /dev/video3
> input 1
> norm 0 UNTIL 3
> webcam_port 8888
> the result of http://192.168.0.101:8888 is only blue screen.
>
> Does anyone know why this problem occur ?
> Thank you. :)
>
>
> Regards,
> Ferry
>
>
>
> john bray <jo...@jo...> wrote: On Thu, 2007-12-27 at 08:46
> -0800, Ferry Sumendap wrote:
>> Sorry for my late reply. :)
>> Thank you for your guidance.
>>
>> Now the xawtv is showing the real picture.
>> But the motion is still showing blue screen.
>> I am trying to fix it , but if you know what's wrong with my
>> configuration.
>> I have tried to modify the motion.conf
>>
>>
>> videodevice = /dev/video0
>> videodevice = /dev/video1
>> videodevice = /dev/video2
>> videodevice = /dev/video3
>
> ferry, i notice you are apparently defining multiple values for
> videodevice? you only want one.
> try this one:
> videodevice = /dev/video0
>
> and plug in the video wire to the one bill told you yesterday.
> set the input to 1:
> input 1
>
> set your norm properly:
> norm 0
> 0 is for pal cams. 1 is for ntsc cams. see the config file for
> other
> values if these are not what you want.
>
> this should be enough to get you a picture.
>
> hth.
>
> john
>
>>
>> All has been tested but,
>> the http://localhost:8888
>>
>> just display blue screen.
>>
>> Please help by telling me the reason :D
>>
>> Wow linux must have improved so much especially with the existence
>> of
>> motion.
>>
>> Thank you for everybody's help.
>>
>> Regards,
>> Ferry
>>
>>
>>
>> "William M. Brack" wrote:
>> Hi Ferry,
>> Ferry Sumendap wrote:
>> > I have executed
>> > rmmod bttv
>> >
>> > AND
>> >
>> > modprobe bttv card=133,132,133,133
>> >
>>
>> Good
>>
>> > AND
>> >
>> > [root@localhost ferry]# xawtv -noxv
>> > This is xawtv-3.95, running on Linux/i686 (2.6.17-13mdv)
>> > Warning: Missing charsets in String to FontSet
>> conversion
>> > Warning: Missing charsets in String to FontSet
>> conversion
>> > Warning: Missing charsets in String to FontSet
>> conversion
>> > libGL warning: 3D driver claims to not support visual
>> 0x4f
>> >
>> > The result is still the same (blue screen is displayed).
>> :(
>> > Any other suggestion please ?
>> >
>> >>From the
>> >
>> > [root@localhost projects]# xawtv -hwscan >
>> xawtv_hwscan_result.txt
>> > This is xawtv-3.95, running on Linux/i686 (2.6.17-13mdv)
>> > looking for available devices
>>
>>
>>
>> >
>> > /dev/video0: OK [ -device /dev/video0 ]
>> > type : v4l2
>> > name : BT878 video (Kodicom 4400R (sla
>> > flags: overlay capture
>> >
>> > /dev/video1: OK [ -device /dev/video1 ]
>> > type : v4l2
>> > name : BT878 video (Kodicom 4400R (mas
>> > flags: overlay capture
>> >
>> > /dev/video2: OK [ -device /dev/video2 ]
>> > type : v4l2
>> > name : BT878 video (Kodicom 4400R (sla
>> > flags: overlay capture
>> >
>> > /dev/video3: OK [ -device /dev/video3 ]
>> > type : v4l2
>> > name : BT878 video (Kodicom 4400R (sla
>> > flags: overlay capture
>> >
>>
>> That much is now correct.
>>
>> >
>> >
>> > It seems that the correct driver is already configured.
>> > But somehow, the xawtv and motion are still displaying
>> blue
>> screen
>> > only.
>> >
>> >
>>
>> That is indeed puzzling. Let's double-check to make
>> something
>> hasn't changed along the way.
>>
>> First, make certain the camera is connected to the "top"
>> BNC
>> connector ("top" and "bottom" may be a little confusing,
>> especially
>> if your card is mounted on its side; when I say "top" I
>> mean
>> the BNC
>> connector on the back panel which is closest to the RCA
>> 2-pin
>> connector). This connector will *always* be camera 0.
>>
>> Next, try booting your Windows OS and confirm that the
>> camera
>> is
>> still working properly.
>>
>> Next, shutdown Windows and boot your Linux system. After
>> the
>> system
>> is up, do the 'rmmod' and 'modprobe bttv
>> card=133,132,133,133'
>> steps
>> as before. Note that the bttv driver for the Kodicom-4400
>> will
>> always preset /dev/video0 to be connected to camera 0.
>>
>> Finally, just run xawtv with no parameters and see if it
>> now
>> works.
>> Note that by default, xawtv should startup using
>> /dev/video0
>> and
>> will set that device to use input "Composite 0", which is
>> camera 0.
>>
>> If xawtv still only shows a blue screen, please make a
>> copy of
>> your
>> 'dmesg' at this point, that is, in your login window type:
>> dmesg > dmesg.log
>> and attach it to your next post so we can try to make a
>> guess
>> where
>> the trouble might be, and what we should do next.
>>
>> >
>> > Regards,
>> > Ferry
>>
>> Good luck,
>>
>> Bill
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Motion-user mailing list
>> Mot...@li...
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>>
>>
>>
>>
>> ______________________________________________________________________
>> Looking for last minute shopping deals? Find them fast with Yahoo!
>> Search.
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________ Motion-user
>> mailing list Mot...@li...
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> --
> cleverly disguised as a responsible adult.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Motion-user mailing list
> Mot...@li...
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
>
>
> ---------------------------------
> Never miss a thing. Make Yahoo your
> homepage.-------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
> Motion-user mailing list
> Mot...@li...
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
|
