curl-devel extension may be required for git on piCore 11 beta 2

[RockJamm]

Hello again.

From a clean install of piCore beta 2

I've installed git and cmake and now I'm trying to pull from git:

git clone https://github.com/mpromonet/v4l2rtspserver.git

and I'm getting:

fatal: unable to find remote helper for 'https'

some suggestion that this can happen if curl-devel is not installed before git.

Does this sound right and if so please can it be added?  Many thanks

[RockJamm]

Some suggestions that running as root might help out there but:

sudo git clone https://github.com/mpromonet/v4l2rtspserver.git

gets same response

[RockJamm]

I have resolved this by using the git transport instead of https

sudo git clone git://github.com/mpromonet/v4l2rtspserver.git

[Juanito]

git updated - you will also need to update ca-certificates

(I haven't tried, but ffmpeg, gstreamer and motion should all be able to stream a v4l2 feed from the RPi camera)

[RockJamm]

git updated - you will also need to update ca-certificates

(I haven't tried, but ffmpeg, gstreamer and motion should all be able to stream a v4l2 feed from the RPi camera)

That's really helpful thank you - on a bit of a learning curve re: streaming but getting there I think!

[Juanito]

This works on an RPI3 with an RPi camera and the motion extension:

edit /usr/local/etc/motion/motion.conf

webcontrol_localhost off
stream_localhost off

Then, on the RPi (or via ssh):

Code: [Select]

$ motion -n
...
[0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /usr/local/etc/motion/motion.conf
[0:motion] [NTC] [ALL] motion_startup: Logging to syslog
[0:motion] [NTC] [ALL] motion_startup: Motion 4.3.1 Started
...
[0:motion] [NTC] [STR] webu_start_strm: Starting all camera streams on port 8081
[0:motion] [NTC] [STR] webu_strm_ntc: Started camera 0 stream on port 8081
[0:motion] [NTC] [STR] webu_start_ctrl: Starting webcontrol on port 8080
[0:motion] [NTC] [STR] webu_start_ctrl: Started webcontrol on port 8080
[0:motion] [NTC] [ENC] ffmpeg_global_init: ffmpeg libavcodec version 58.54.100 libavformat version 58.29.100
[0:motion] [NTC] [ALL] translate_init: Language: English
[0:motion] [NTC] [ALL] motion_start_thread: Camera ID: 0 is from /usr/local/etc/motion/motion.conf
[0:motion] [NTC] [ALL] motion_start_thread: Camera ID: 0 Camera Name: (null) Device: /dev/video0
[0:motion] [NTC] [ALL] main: Waiting for threads to finish, pid: 4228
[1:ml1] [NTC] [ALL] motion_init: Camera 0 started: motion detection Enabled
[1:ml1] [NTC] [VID] vid_start: Opening V4L2 device
[1:ml1] [NTC] [VID] v4l2_device_open: Using videodevice /dev/video0 and input -1
[1:ml1] [NTC] [VID] v4l2_device_capability: - VIDEO_CAPTURE
[1:ml1] [NTC] [VID] v4l2_device_capability: - VIDEO_OVERLAY
[1:ml1] [NTC] [VID] v4l2_device_capability: - READWRITE
[1:ml1] [NTC] [VID] v4l2_device_capability: - STREAMING
[1:ml1] [NTC] [VID] v4l2_input_select: Name = "Camera 0"- CAMERA
[1:ml1] [NTC] [VID] v4l2_norm_select: Device does not support specifying PAL/NTSC norm
[1:ml1] [NTC] [VID] v4l2_pixfmt_set: Testing palette YU12 (640x480)
[1:ml1] [NTC] [VID] v4l2_pixfmt_set: Using palette YU12 (640x480)
[1:ml1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer to 1 items
[1:ml1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer to 4 items
[1:ml1] [NTC] [EVT] event_newfile: File of type 8 saved to: ./0-01-20200606143344.mkv
[1:ml1] [NTC] [ALL] motion_detected: Motion detected - starting event 1
[1:ml1] [NTC] [ALL] mlp_actions: End of event 1

On another machine on the same lan:

Code: [Select]

$ ffplay http://192.168.1.111:8081
..where 192.168.1.111 is the RPi3 ip address

You will basically see a still image until the camera detects movement and begins to record - the videos are saved locally on the RPi3.

You can also see the control interface in a browser using http://192.168.1.111:8080

[Juanito]

Instead of using motion/ffmpeg/libv4l2 on the RPi, this also works with the rpi-vc extension:

Code: [Select]

$ sudo raspivid -t 0 -l -o tcp://0.0.0.0:3333.."sudo" because the permissions for /dev/vchiq are not correct

..and on a laptop on the same lan:

Code: [Select]

vlc tcp/h264://192.168.1.111:3333..where 192.168.1.111 is the RPi3 ip address

[RockJamm]

This looks like an excellent option - thank you!  I missed it last week!   I was always looking for a minimal solution, this looks perfect.

[RockJamm]

Hmm.  Not having any joy at the vlc end though the pi is clearly listening for a connection:

tc@pc-cam1:~$ sudo raspivid -t 0 -l -o tcp://0.0.0.0:3333
Waiting for a TCP connection on 0.0.0.0:3333...

but at the vlc end, trying to open a network location no joy.  Maybe it's a firewall thing.  I'll persist.  Thanks again.

...[Edit] I was not running vlc from a shell but from the gui - now working on shell access instead  [/Edit]

[Juanito]

motion would probably use the least bandwidth..

[RockJamm]

Thanks Juanito.

Motion works but doesn't do what I'm after.  I want highest quality video over LAN as a full-time reliable stream.   I've chosen piCore because I don't want any unnecessary processes going on.  I'm aiming for 1920 x 1080 at 30fps+.  Motion does about 3 fps in both preview and recordings in the test I've done.

I'm very interested in your raspivid only suggestion but I can't get it to work yet. 

[RockJamm]

raspivid to tcp as you suggested is picked up by ffplay -i tcp://192.168.1.138:3333

much better fps, quite a big buffer but I can live with that.