"-r 1 " is just going to use the input file sampling rate, no? I don't think this is a sampling rate problem unless there's signs of "rolling shutters" or total disconnect in the expected output playback.
"You need to check with V4L utilities or ffmpeg, which formats / resolutions your v4l2 device provides. I would guess that docker gives you only an abstraction (it's a kind of virtualization, right?)." Agree with that. Cameras are getting smaller and smaller.... and in order to get away with that software is used on the the intake signal and unwrapped/decompressed into larger resolutions as it goes to our screens. The reason I suggested scaling is because you didn't complain about the image not making sense... which means ffmpeg was able to decode the stream and encode it into some format ( maybe not the ideal one. ) My guess is that the pre-packaged web cam software driver might perform a software unwrapping of the data, which allows it to have a higher resolution than perhaps something you can grab from ffmpeg. That proprietary software might also preform a scaling operation using a nice/custom filter to up-rez it so that they can claim it has X resolution even though the raw data might not actually be that. I have not heard about this problem with web cams but it is a conversation I've witnessed when people get data from cameras mounted on drones. On Mon, Feb 26, 2018 at 9:05 AM, Moritz Barsnick <barsn...@gmx.net> wrote: > On Fri, Feb 23, 2018 at 00:34:26 -0500, DiegoUG wrote: > > I'm doing a capture of an image from the docker using my web cam, but the > > docker is doing it at a resolution of 176x144 and outside of the docker > in > > my localhost it takes it to 640x360, in both it's the same installation, > I > > do not know it's happening: > > You need to check with V4L utilities or ffmpeg, which formats / > resolutions your v4l2 device provides. I would guess that docker gives > you only an abstraction (it's a kind of virtualization, right?). > Perhaps you only get USB 1.1, and that doesn't allow for your device's > larger resolutions (despite "-r 1"). Hmm, just guessing. > > Moritz > _______________________________________________ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". > -- There be monsters out there... consider using PGP/GPG encryption for confidential communications. My public key can be found here <https://drive.google.com/file/d/0B9VvIkxWz5nhWkd5SFVUaWZqVWc/view?usp=sharing> . _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".