Billy Biggs <vektor@xxxxxxxxxxxx> writes: > > Sort of. The buffer size is determined by the current video format at > > VIDIOCGMBUF time. Which happens to be just the default > > (320x240xRGB24) for most v4l applications, because nobody calls > > VIDIOCSWIN before VIDIOCGMBUF ... > > Interesting. Should I call VIDIOCSWIN before VIDIOCGMBUF ? Better use the v4l2 API, this hasn't those hidden features :) In theory VIDIOCSWIN / VIDIOCSPARM (palette field) should be used to set the capture size format. It is required for capture via read(). Drivers might use it to calculate the buffer size for VIDIOCGMBUF. In practice this is nearly nowhere used that way because bttv doesn't need this for historical reasons. Requiring applications to do that now would likely break lots of them. > > I've changed the default capture size in the latest snapshot. > > To the maximum capture size? 768x576 @ RGB24 Gerd -- Weil die späten Diskussionen nicht mal mehr den Rotwein lohnen. -- Wacholder in “Melanie”
