rory

also see this post ... might be useful down the road .. http://www.cctvforum.com/viewtopic.php?p=116003#116003

Ubuntu and Wine Just tested simplevue from Wine on Ubuntu and it worked. But this is after having to copy some additional windows files mostly for the VBruntime and also at least one additional DLL required by the Geo ActiveX. I will do some more testing but so far it looks like this, running wine from a terminal window as root (admin) - BTW I know nothing about Linux, this was basically my first time using it with any kind of administration. Also it was being run in Virtual Box which is kind of slow on this PC.

so far it looks horid. but i might be missing something, doubtful but maybe there is something else i need to enable or turn on that didnt have to do with older versions .. which isnt in their SDK help and samples .. to get better quality. Also maybe the quality just sucks with the older cards.

Well its a little more then that ... ill check it out. 8.3 remote video quality sucks though.

Could be condensation. Take off the cover on the front and if it goes away then let it dry out for a few hours in the heat, then close it back up again (tight) and check the back part of the camera where the cable comes into it, seal with caulking.

Yeah but like that, one can still just click the CTL-ALT-DEL key or click the windows key to gain access to Windows. The Geo server software itself only prevents minimizing or exiting the Geovision software.

No, apparently no older software will work with the new cards, only 8.3xx will work with the 8.3 cards. But ive never tried it myself, im just going by what others have said on this forum so far.

Another player in the industry and also a member on this forum is Nuuo. I cant say how they are as I havent used them yet, but the software looks very detailed, like Geo, and their hardware compression cards are much cheaper.

Hey ... yeah Geo screwed us all. Even their own Remote player doesnt work with 8.3. Sorry but im not using their DM multiview. Anyway, all older activeX controls will connect to the new 8.3 but you wont see any video, as it does decoding differently now among other things. they also disabled directdraw overlay by default so you get blocked video in larger video sizes .. but it is auto enabled when you use their specific control panel modes .. but to get what mode we want (plain one) there is a right click menu that cant be disabled .. and that kills my app obviously. BUT just last night I figured out a way to beat that and get it to work so I can right click without their menu popup AND get directdraw overlay. Unfortunately though the old app wont work with the new version 8.3xx no matter what though, and i no longer have that code or would even work on that old code. Im working on the new code to get it working for 8.3 now that I know I have a fix. I had version 7 that worked up to 8.2 almost ready to role out besides the admin code ... then came 8.3 and killed it all! LOL. As for the web pages you can just swap out the activeX for the new one .. ok not as simple as that but it is pretty easy. The liveX code is about the same, different ID, only thing is as it is you will have blocked video .. there is one more line that has to be added ... LiveX.SetGUIMod 3, 0, 0 But beware as a menu pop up will appear everytime you right click. Additionally, we cant change the background color of the activeX anymore, it will always be "Blue" now. I even tried using API calls but it doesnt like it at all. I posted about 8.3 webcam issues in the dealer section ... One thing I noticed the other day when setting up a Geo DVR with 8.3 for the first time (yes I always use 8.12 but my colleague wanted 8.3 as he thinks new is better LOL), was that the webcam has no setting for the codec anymore. I then noticed that is controlled via the webcam activeX control now. This would explain why the 8.2 and earlier ActiveX controls connect fine but show no video, it seems (appears so though I could be mistaken so dont take this as fact) that they no longer do the codec processing for webcam on the DVR side. http://www.cctvforum.com/viewtopic.php?t=18553 Ive yet to confirm the above though, it was just a first impression. Rory

ofcourse i dont want to get ahead of myself .. there were still alot of awful vcr recordings .. but playback SVHS to a CCTV monitor with SVHS input and you could see alot clear on say a 20" CRT monitor .. its the evidence sharing that really sucked .. well we just gave VCR tapes to the courts but to digitize was a pain. Luckily I was in it at the end of that era though Then again look at some cheap 4 channel DVRs on the market today .. awful evidence sharing

i came into the industry when VCRs were still being used .. SVHS .. it took longer but we were still able to catch the crooks. The funny thing is the clarity was typically very good back then with CCTV cameras .. even the VCR recordings were not as bad as some current exported DVR recorded quality .. it took longer ... but its like it got worse, or really people just buy cheaper cameras and run everything at low quality now .. and so many crappy quality DVRs (worst then VCR) on the market these days . probably alot due to more DIY and all the online stores just selling anything they can get their hands on and to anyone that has the money Wasnt that long ago we were using Muxes with 1 channel DVRs ... some people are still using them .. they just work.

check the system idle protection. by default if enabled it will log out ... uncheck that first box and check the second box instead. also, make sure disable any channels that are not connected, and or turn off the watchdog for video loss.

when you did the database repair did you check the box to rebuild all info? If not try that. Also make sure the data paths are the same. Additionally you could check the INI file in the windows folder manually for any path problems.

The only thing in your setup that is not normal are the baluns, I would join the cables together without connectors temporarily and see if that fixes it. If not, then put them back on and would need to look at what else might be causing it. The other thing to do is to power them all individually, they may not have built in isolation and one maybe grounding somewhere, or one camera may just be bad. Also could be the DVR but first try to rule out the cameras and power.

the PCI-e Geo card are x1 so should fit in at the least a x1 slot, and should fit in the x16 also using the first part of it. Requires power from the PSU, so check the PSU is good also. Strip down the PC .. use onboard video if you have it, put the video card aside for now. Disconnect the DVD/CD drive, and any additional HDDs, just leave: mobo, 2GB memory, CPU w fan, 1 HDD, PSU. AND DVR card ofcourse Disconnect the audio card if you connected it. Make sure the right pigtail is being used .. not using VGA extenders. Reformat and load XP SP2, and install drivers and nothing else BUT the geo server software. Then see whats up.

yeah the party has stopped now

1990 .. wow .. yeah i was in my early 20's and life was one big party http://www.patentstorm.us/patents/5091780.html

there are some cheap panasonic chips in some cameras out of asia these days .. not sure what the deal is with them but they pretty much suck as I have used them in the past; they do seem better than the Sharp CCD though. But its not the same as the Panasonic cameras we are talking about.

Someone else said the new cards only work with the new 8.3 software ... so that would explain the keypro errors at least.

i dont get involved in retail sales so I dont know what that is (unless you mean a wristband with a bar code used in the clubs, but cant be that), but I have seen other things .. ive seen the cashiers just pocket the money cold .. but i mostly just get called in when someone gets stabbed, shot or killed.

Dont bother, just post the brand and where to get it, its not for me. I guess you clearly missed the part where i said "As far as I know". I do not know it all .. just an FYI. If you have something to add to the discussion, please feel free to do so.

do you have it sitting flat? remember that is a piece of metal spinning around all the time ..

How do they save? Dont they need an internet connection, VOIP account, and an ISP that is up with broadband bandwidth 100% of the time? When people call me from the US using VOIP i just hang up on them now, I tell them call me back from land line, or just email me, still too many issues.

I'll try that, tnx. So if the WD drive (that has no apparent bandwidth issues) can only sustain 50mb/sec then an SSD that has a "Sustained write speed" of 50mb/sec would be the performance equivalent? Im no expert, but i imagine that is about right. Reason i figure HDD specs dont mention it as much if at all is that most will always be around the same, like a 7200 across the board wont be much diff from the next, 10,000 etc. but with SSD the speeds vary so much, such as for example my soldered on Eee PC SSD is approx 25mb/s and an SD card can run anywhere from 5-18mb/s .. a 4200 rmp HDD around 40-45mb/s .. a USB 5400rmp drive around 40mb/s .. but now they have so many variations and types of SSD going up as fast as 230mb/s (max) ... actually thats it right there ... the SSD specs will have their MAX read I guess .. not sustained, or will spec the sustained separately.

My automotive HD run at 100MBytes / sec. Model ST980818AM, page 10/50 in this spec sheet: http://www.seagate.com/staticfiles/support/disc/manuals/ce/EE25%20Series/EE25.2/100448541e.pdf The same advertised data transfer rate is true for my current drive (WD1600JB) but the seek time is much less that the automotive drive because the spingle speed is 7200 instead of 5400. I'm going to bolt the dvr onto a piece of OSB and set that flat in the trunk, see if that stops the corruptions. the 7200 WD drives (the JB series to be specific) only read around 50-55mb/s, the raptors, their FASTEST Hard drives read average of 75mb/s with 85mb/s being the fastest, those are 10,000 rpm drives. That 100 might be the max or the burst rate but when comparing to the read and write specs of the SSDs you need to use the average read speed. Download and run HD Tune to really test the average speed, not the max transfer rate or burst rate. The average really tells you the speed of the hard drive. Between the raptor and the JB you can really feel the difference.