ZoneMinder Forums

It indicates that your card doesn't support xv exntension in format RGB. Only cards that I found working with this are nvidia's with nv driver. Better use gl version it is much faster, and should work with every card if you configure it properly for opengl. Almost every ati and nvidia card should ...

It worked with 0.6.3. How about "WARNING: Couldn't find free Xv adaptor with RGB XvImage support Falling back to ximage - slow and ugly rescalling"? Could you explain this message? Sure. It indicates that your card doesn't support xv exntension in format RGB. Only cards that I found working with ...

I checked video is 24bpp, running xlib_shm as root, zm running. Question: is xlib_shm 0.6 compatible with zm 1.22.3 or only with zm 1.22.2? Just made new version. try version 0.6.3-gl or 0.6.3 it is compatible with 1.22.3. There were some changes in shm beetween 1.22.2 vs 1.22.3 It worked with 0.6 ...

0.6 segfaults after trying to fall back to ximage How can I help debug? Run xserver in 32 bit mode and send me log of strace strace -o log ./xlib_shm -m1 Send log file to my mail. I had xlib_shm running before, but I had to make a new fresh install (Fedora 5) and now I use zm 1.22.3. It gives me ...

# ./xlib_shm -m 1 xlib_shm viewer for zm 1.22.0 version 0.3 imgx=0 imgy=0 delay=10000 shmkey=7a6d2000 monitors:1 ERROR: Failed to shmget Any other hint? Sergio Probably not running zm. Start it with zmpkg.pl start ZM is running. I can access through http. Or you are trying to run xlib_shm on other ...

X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 72 (X_PutImage) Serial number of failed request: 11 Current serial number in output stream: 13 Change your display depth to 24bits in your xserver configuration file. It should work. If not please ...

James,

Just to let you know zm4Linux worked just out-of-the-box on my FC4. Nice work!

By the way, cycle view is on top of my whishlist. And I coudn't find any sources on your site.
Is it opensource?

Sergio.

Hi, When i run xlib_shm (xlib_shm -m 1) as root, screen flashes and returns with the following messages: xlib_shm viewer for zm 1.22.0 version 0.3 imgx=0 imgy=0 delay=10000 shmkey=7a6d2000 monitors:1 X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request ...

@voronwe I will make a configure script when it would be really needed. Or you can write some for me and I'll attach it to package. How about just putting some comment on Makefile, like: # Note for Fedora users: # gcc xlib_shm.o -L$(X11PREFIX)/lib -L/usr/lib/mysql -lX11 -lmysqlclient -Wl,-rpath ...

Hi,

I was wondering, which is better in terms of bandwidth use: to send video stream using mpeg or continuous jpeg images? Does it make any difference?

Thanks,
Sergio.

Hi, I had exactly the same problem: When I open up the watch window, Zoneminder usually shows the current live video feed from the canera. I can force an event and view the capture and I see the images just fine. The same is true for the Cycle / Montage views. If I setup a zone, I can see the image ...

Hello,
When I open event window, there's a light blue grid bar under the image. Shouldn't it
be a progress bar? I don't if it's a TODO or done item, but on my system this bar shows nothing while event is beeing played.
Am I missing something?

Thanks,
Sergio.

I've spc5xx webcam on FC4, zm 1.22.0 and the following warning on logs: WAR [Approaching buffer overrun, consider slowing capture, simplifying analysis or increasing ring buffer size Shared memory was increased: both /proc/sys/kernel/shmall and /proc/sys/kernel/shmmax are 134217728, which I think is ...

I've the same problem: malloc(): memory corruption (ZM 1.22.0, fresh FC4 instalation, bt878) Well, I decided to install zm from scratch, took off bt878 card (which is 4 port) and tried with a plus simple device, a spca5xx USB webcam. Command "zmc -d /dev/video0" continued crashing due to memory ...

Hi, I've the same problem: malloc(): memory corruption (ZM 1.22.0, fresh FC4 instalation, bt878) Yes, I have seen this and if I recall it was the result of putting invalid information or the lack there of when setting up the monitor. Delete the monitor, and create it again with valid information. I ...