No v4l2ucp is do correctly control of hue and working with negative hue. I spoke about amsn is not support correctly negative hue. In this case maybe some other applications cold be unsupported negative parameters for control of picture. Really the correct value is between -180 degree to +180 degree. But this is relative angle from some point named 0 degree, In this case maybe some applications is not support negative values. I understand this is the bug into amsn not in the driver and V4l2 standard is damaged by amsn. But really for final user that not mean who write correct code he ask only to work correctly the camera with exactly application. Also the end user is see only the not working control. In this case maybe is more good idea to apply the control in positive value only until some userland applications fix the bugs in V4L2 protocol. Else some users who is migrated from Windows to Linux is say " the camera is not working under windows i just install the driver and all is OK". Also the depends from libv4l2 is not installed automatically on each distribution and for typical user all 'magic' about installation and tuning is not understandable. I'm just a user friendly oriented and test each my code with different camera clients. That is just a my point of view. Also we test the hue/set/bright/cotr control only on 2 types of camera my and Stefan's (we have 6270) and your camera. For me all pathes (also Josua) seems OK. Brian Johnson wrote: > So you are saying the that when you use v4lucp to adjust the hue > control below 0 that he hue does not actually change? And that the > function sn9c20x_set_optical_parameters is never called? > > 2009/3/19 Boris Borisov <[email protected]>: > >> Exactly the function is not call via V4L for negative hue. And I not >> found the reason for missing call. >> >> Brian Johnson wrote: >> >>> Boris, >>> I'm not sure what you mean by the function is not being called when >>> hue is negative using this patch it certainly seems to work with >>> negative hues for me. About the issue with sysfs i did a quick >>> modification that should fix that >>> >>> 2009/3/19 Boris Borisov <[email protected]>: >>> >>> >>>> Brian, >>>> I get the current version of driver and apply the my patc and your >>>> changes for range. But from V4L if hue is negative the set function is >>>> not call. I can't find where is mistake. I attach the patches. Also from >>>> sysfs the values is only positive. >>>> Brian Johnson wrote: >>>> >>>> >>>>> Boris, >>>>> >>>>> Can you post a fixed patch ithat includes the -180 - 180 fix plus >>>>> fxing th checkpatch.pl errors and adding the code to add hue as a >>>>> module param? >>>>> >>>>> If you post the patch in the thread i created called weekend patches >>>>> it willl give us till the end of sunday for people to hoopefully look >>>>> at and review the patch before actually committing it. >>>>> >>>>> 2009/3/19 Boris Borisov <[email protected]>: >>>>> >>>>> >>>>> >>>>>> I agree. The mistake is my because I working in night and firs version is >>>>>> similar as you patch and hue betweeh -180 and 180 degree. But after coup >>>>>> of >>>>>> >>>>>> >>>>>> >>>> snip >>>> >>>> >> > > > > >
--~--~---------~--~----~------------~-------~--~----~ Lets make microdia webcams plug'n play, (currently plug'n pray) To post to this group, send email to [email protected] Visit us online https://groups.google.com/group/microdia -~----------~----~----~----~------~----~------~--~---
