donkeyteethux / kcam Goto Github PK

What is a picture directly? Current working directory is writable, what is the problem saving there?

At least error message should show the path to the directly that is not being found.

Obviously, the picture directly should be adjustable from CLI.

When starting the program, it seemed to work fine, then the camera went black.

I wouldn't exclude a technical problem on my side yet.

kcam should support at least kcam --help. I expect positional argument to be the device name and optional argument for setting initial image options (the same as can be adjusted with sliders). Additionally, I expect V4L2 options for opening the device (e.g. picture size, mjpeg vs YUV) to be also adjustable from CLI.

Hi Alex

I love that you took an initiative to create a good web cam apps in an open source manner so a big thank you for your work.

I have been wanting to contribute to some newish open source projects that could benefit from a design revamp/improvement. I am a ui/ux designer by the day and have been wanting to contribute towards better looking open source design?

Do you think there is anything you need help on? I can already see the tabs, icons, spacing, typography, visual components- everything can be fine tuned to make it looks nice and clean and modern.

This would be nice to have. It should be possible to write the jpg buffers more-or-less directly to a .avi file, though I'm not sure exactly how that works.

If anyone wants to try this, feel free (:

$ RUST_LOG=info kcam
[2022-08-30T14:08:25Z INFO  kcam::util] Device check failed for Some("Virtual1") at "/dev/video0": Failed to open stream.

    Caused by:
        0: failed to set format
        1: Invalid argument (os error 22)
thread 'main' panicked at 'Failed to start: No capable video devices found. Run with RUST_LOG=info for details.', src/main.rs:26:27

$ strace -fe ioctl kcam  |& rg VIDIOC_[GS]_FMT
ioctl(3, VIDIOC_G_FMT, {type=V4L2_BUF_TYPE_VIDEO_CAPTURE, fmt.pix={width=640, height=480, pixelformat=v4l2_fourcc('Y', 'U', '1', '2') /* V4L2_PIX_FMT_YUV420 */, field=V4L2_FIELD_NONE, bytesperline=640, sizeimage=460800, colorspace=V4L2_COLORSPACE_SRGB}}) = 0
ioctl(3, VIDIOC_S_FMT, {type=V4L2_BUF_TYPE_VIDEO_CAPTURE, fmt.pix={width=640, height=480, pixelformat=v4l2_fourcc('M', 'J', 'P', 'G') /* V4L2_PIX_FMT_MJPEG */, field=V4L2_FIELD_NONE, bytesperline=640, sizeimage=460800, colorspace=V4L2_COLORSPACE_SRGB}}) = -1 EINVAL (Invalid argument)

Why does it try to switch it to MJPEG mode?

ffplay /dev/video0 plays the virtual camera successfully.

Other end of the virtual camera is streamed by ffmpeg ... -vcodec rawvideo -pix_fmt yuv420p -threads 0 -f v4l2 /dev/video0

Hey! I saw your project on r/rust! This sounded like something up my alley and I noticed it didn't support osx.

I created this which contains a subset of the functionality but has all of the boilerplate necessary to deal with all OSX if this was something you wanted to eventually add.

I'll also take a crack at it when I have the time.

Looks like this project may not support Windows machines.

$ kcam
thread 'main' panicked at 'Failed to start: No capable video devices found. Run with RUST_LOG=info for details.', src/main.rs:26:27
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

$ echo $?
101

This should be a regular error (with exit code 1 or 2), not a panic.

I get a "No such file or directory" error when starting the app.

I already found out, where this comes from: My camera does not have /dev/video0, but only 1 and 2.

What I would do (in this order):

• iterate over all webcams and choose the first one, that's found
• generate a list of all found webcams and display them in UI (if possible using a meaningful name, if you can find one)
• recognize, when webcams are plugged in or out, automatically update the list, switch the currently selected camera if none is available