Can you reproduce this bug with latest version of v4l2ucp?