netcam_tolerant_check
- Type: Boolean
- Range / Valid values: on, off
- Default: off
- Option Topic
Set less strict jpeg checks for network cameras with a poor/buggy firmware.
Comments
I am not sure I like this option name. It does not really tell what it does.
netcam_strict_check which is default on and can be turned off or netcam_tolerant_check which can be turned on may be more descriptive
Best would be to not have an option and just let the code discover that the camera is buggy and self adjust to a looser algo.
--
KennethLavrsen - 15 Aug 2008
Yes , maybe is not the best name ... i added to work arround to some network cameras with buggy firmware .
At the moment for 3.2.11 no plannig to add any code to discover buggy firmware , so let's choose a name for this option.
1) netcam_strict_check
2) netcam_tolerant_check
3) netcam_ ...
--
AngelCarpintero - 16 Aug 2008
I am OK with either netcam_strict_check or netcam_tolerant_check.
How will most non-broken camera operate if the feature is enabled?
--
KennethLavrsen - 25 Aug 2008
For not buggy network cameras this parameter will passthrough images that have :
cinfo->err->msg_code == JWRN_NOT_SEQUENTIAL ( Invalid SOS parameters for sequential JPEG )
I cannot reproduce this in a not broken netcam , probably this "error" could be ignored , in general all
JWRN_ from jerror., alhought is a good idea to allow setup this as parameter to avoid break some network
cameras.
--
AngelCarpintero - 26 Aug 2008
I have a setup with bugs, but I am not sure whether it's really the firmware. Most jpgs are corrupted due to short reads. Unfortunatelly the new function doesn't work, as I still get triggered events due to short reads. Is there some way to check jpgs for correct size or completeness ?
--
JudasHui - 24 Sep 2008
Please open a Support or Bug with detailed information about your devices and motion logs ( ./motion -n -d 10 )
--
AngelCarpintero - 26 Sep 2008