Control: tags -1 moreinfo Hi, On 20/02/18 16:30, peter@easthope.ca wrote: > Package: mpv > Version: 0.23.0-2+deb9u2 > Severity: normal > Tags: upstream You tagged the bug "upstream". This tag usually means that the bug is known to be in upstream mpv. How do you know this? > Dear Maintainer, > > * What led up to the situation? > Display of output from a Logitech camera > M/N: V-U0006 > P/N: 860-000177 > PID: LZ944BN > * What exactly did you do (or not do) that was effective (or ineffective)? > Connected USB and executed "mpv tv:// --tv-device=/dev/video0" > on two similar systems, imager and dalton. Transcripts appended. Does ffmpeg's v4l2 support work better? mpv -v av://v4l2:/dev/video0 I should point out that all the code for tv:// has been removed in upstream mpv, so if this is a bug in mpv, it is unlikely to be fixed (upstream now tells you to use the av:// form above). I don't know what "imager" and "dalton" mean. Do they have identical versions of mpv and identical kernels (probably the 2 most important bits here)? Please recreate the transcripts with the -v option to get more verbosity. Testing with newer kernels and mpv versions would be helpful, but this might be a bit harder. > Note the differences from the same procedure on two almost idential > systems. Eg. > [tv] Current format: YUYV > versus > [tv] Current format: MJPEG > * What was the outcome of this action? > The images appeared with numerous complaints. Eg. > [tv] ioctl enum norm failed: Inappropriate ioctl for device > [tv] Error: Cannot set norm! > * What outcome did you expect instead? > A concise and tidy report to the terminal with no complaints, errors or warnings. > In the present state, the software is not good release quality. Does your webcam actually play in mpv? Is it just the log messages that bother you? Thanks, James
Attachment:
signature.asc
Description: OpenPGP digital signature