hipersayanX

```/dev/video1: Inappropriate ioctl for device``` Also, this confirms that the driver is not responding to formats and resolution listing, but may work if forcing one, that's why try to run...

Try as with ffmpeg as follows ```ffmpeg -f v4l2 -input_format yuyv422 -video_size 640x480 -framerate 30 -i /dev/video1 test.webm``` This defines every single parameter needed.

[Here](https://github.com/FFmpeg/FFmpeg/blob/daee46ed7efa71ac317abfa835c3d3d00fd8eab4/libavdevice/v4l2.c#L876) is where the initialization sequence starts in FFmpeg, is some of those ioctl which is failing. Try running the compliance test, this should say which features are supported and...

Other, information that wold be useful is ```uname -a``` for the kernel version.

So these are the only available ioctls: VIDIOC_QUERYCAP: OK VIDIOC_G_FMT: OK VIDIOC_TRY_FMT: OK VIDIOC_S_FMT: OK VIDIOC_REQBUFS/CREATE_BUFS/QUERYBUF: OK Which confirms my guess, its possible to start and capture from the camera,...

Compliance errors may vary from each kernel, and are in most cases just a mere warning, the important part here is if the client software can detect and capture the...

>ERROR: from element /GstPipeline:pipeline0/GstV4l2Sink:v4l2sink0: Device '/dev/video1' is not a output device. Because, probably confusing the device, /dev/video0 is probably the output device and /dev/video1 is the capture device. >[in#0 @...

Show me the the full /etc/akvcam/config.ini.

For the moment, the output device [only supports RGB24](https://github.com/webcamoid/akvcam/wiki/Configure-the-cameras#defining-the-formats), I want to port the Webcamoid's video format conversion code to the virtual camera in future versions. Change the config.ini to:...

Did you had reloaded the module after editing the config.ini?