Hi all!
Beside the bug http://www.zoneminder.com/forums/viewto ... 5&start=15 I also have a resolution problem with ZM and the Foscam F18918W ipcam.
I cannot get it to work above the 320x240 resolution, in Zoneminder.
Via the webbrowser the 640x480 resolution works normally, when I login to the cam. But when I try to get the stream into a 640x240 mode into Zoneminder it fails.
Anybody experience the same issue or knows a workaround maybe? Are there config files locking the screen resolutions in Zoneminder?
I followed this wiki http://www.zoneminder.com/wiki/index.php/Foscam_FI8918W and this says that Zoneminder can handle the 640x480, but I doubt it after two days of google and playing with the settings.
Any help would be much appreciated!
320x240 resolution only with ZM and Foscam F18918W? ZM lock?
Re: 320x240 resolution only with ZM and Foscam F18918W? ZM l
Post logs of /var/log/syslog and check your shared memory settings, maybe are enough to support 320x240, but not enough to support twice the resolution.
After more than 15 years, no longer using ZM as surveillance system.
Now in the dark side, using a commercial system...
Re: 320x240 resolution only with ZM and Foscam F18918W? ZM l
Thanks for looking in to this, my knowlegde is to short to sort it out. I can see at the end of the log that there is a problem with the shared mem. Hope that you can shout something what I can do to fix it. Thanks in advance!!
/var/log/syslog
ar 15 22:59:48 toshiba-debian zmc_m13[2600]: WAR [Corrupt JPEG data: 2 extraneous bytes before marker 0xd9]
Mar 15 22:59:48 toshiba-debian zmc_m13[2600]: WAR [Corrupt JPEG data: 1 extraneous bytes before marker 0xd9]
Mar 15 22:59:48 toshiba-debian zmc_m13[2600]: WAR [Corrupt JPEG data: 1 extraneous bytes before marker 0xd9]
Mar 15 22:59:49 toshiba-debian zmwatch[2317]: ERR [Can't get shared memory id '7a6d000e', 14: No such file or directory]
Mar 15 22:59:49 toshiba-debian zmwatch[2317]: ERR [Can't get shared memory id '7a6d000e', 14: No such file or directory]
/var/log/syslog
ar 15 22:59:48 toshiba-debian zmc_m13[2600]: WAR [Corrupt JPEG data: 2 extraneous bytes before marker 0xd9]
Mar 15 22:59:48 toshiba-debian zmc_m13[2600]: WAR [Corrupt JPEG data: 1 extraneous bytes before marker 0xd9]
Mar 15 22:59:48 toshiba-debian zmc_m13[2600]: WAR [Corrupt JPEG data: 1 extraneous bytes before marker 0xd9]
Mar 15 22:59:49 toshiba-debian zmwatch[2317]: ERR [Can't get shared memory id '7a6d000e', 14: No such file or directory]
Mar 15 22:59:49 toshiba-debian zmwatch[2317]: ERR [Can't get shared memory id '7a6d000e', 14: No such file or directory]
Re: 320x240 resolution only with ZM and Foscam F18918W? ZM l
http://www.zoneminder.com/forums/viewto ... ory#p72552
Hope it helps, credits to Pada, author of the original script,
PacoLM
Hope it helps, credits to Pada, author of the original script,
PacoLM
After more than 15 years, no longer using ZM as surveillance system.
Now in the dark side, using a commercial system...
Re: 320x240 resolution only with ZM and Foscam F18918W? ZM l
Thanks Paco for the effort!
I will run the script later on and will update if it was succesfull.
I will run the script later on and will update if it was succesfull.
Re: 320x240 resolution only with ZM and Foscam F18918W? ZM l
I've got the same problem with Foscam FI8918W (firmware v11.37.2.48, Web UI v2.4.10.2, Zoneminder v1.25.0, libjpeg-8d-1).
Would be it possible to shift the loglevel from WARN to TRACE for this event (bit of lazy to recompile Zoneminder myself)?
Would be it possible to shift the loglevel from WARN to TRACE for this event (bit of lazy to recompile Zoneminder myself)?