40th Floor

Then you may safetly presume I did not reply to your post. Tip: Consider posting a link next time if you take more than 100 lines, or 10 posts in a row because whatever you have to stuff doesn't fit in fewer. No one reads all that. I know I don't. Comment directed to you: I know of you from the Foscam board, where you banned my account because you don't like being wrong. And here you are, again, making everything about you. This is my last reply to you, and any topic you are in (except for a topic which I may start).

"The future of cinema and TV: It’s game over for the hi-res hype" http://www.theregister.co.uk/2013/06/25/the_future_of_moving_images_the_eyes_have_it/ About FPS versus resolution or, how low FPS of moving pictures at higher and higher resolution is doing it all wrong.

Lots of hardware there. This one (if the mini-pic makes it) runs on anything in the last 8 years. The pic is of the service manager. Coming really soon is the plan but I said that last summer. Super-secure (NSA proof? I think so) and super efficient. The transcode in the pic is using hardware (I have the app at minimm scale (it can go full screen and keep the same contents, just bigger); it uses Direct2D for the clients so scales as if it were vector-based (no jaggies). It's super-smooth and responsive. The service/server which this svc mgr manages, does the recordings, event processing, alerting -- phone, even voice, e-mail, whatever -- is a plain console app that runs as a service, using a lowly Local Service account. Any number of instances, each doing from 1 to 20 camera. It can also run AS a user-run, console app. It is designed for remote access; everything to/from it is over an encrypted TCP/IP network (SRP, SSL, and then again the stream is encrypted). The svc mgr (in the pic) can manage any running server (each slot there can be to a different server/location). I expect a low price, and a completely free 1-camera (otherwise complete) package. And no DRM. I don't like DRM. Never have used it. BTW, the transcode is done at the server. It's to make viewing otherwise high-bitrate streams remotely possible, at a much lower bandrate. No extra camera connection (you never connect directly to a camea).

Looks to be the same thing I've been using for about a year. The elephant went by and no one noticed? No creds needed to get this snap. Or is Dahua + no creds just a given?

http://en.wikipedia.org/wiki/AVC-Intra

My impression of Q-See tech via custhelp.com is poor. The guy tried repeatedly to BS me. While I could chalk one up to ignorance, after the second, even deeper BS, I knew it was not going to stop at that. (He signed as one Brendon Welch.) It could not have been worse for Q-See.

Not Dahua by name, but with the Costco Q-See 7001, through its onvif API, I can access the camera without authenticating. That would be snapshots, streams, system reboot, even a factory reset, free to the world. If for some reason I wanted to authenticate, admin/admin always works the first time, and after a reboot (no persisting). Lots of onvif things that should work don't seem to work, either. All I wanted was a way to reboot the camera, but I got that and a lot more (that I didn't).

This is likely much faster at getting it up. viewtopic.php?f=19&t=32939

I whipped up a viewer for the Costco camera boxed by Q-See. The 7001 bullet one. Here's a bit, and a couple of links. 1 Nov 2012 o --- REQUIRES A CostCo Q-See 7001 IP camera An H.264 stream Windows 7 or later : : Hardware acceleration is used, if available; CPU use is well below one percent for full HD at 30 FPS. The full text is here: http://40th.com/qc/QC_costcocam_40th.com.txt And the small 273 KB zip is here: http://40th.com/qc/QC_costcocam_40th.com.zip Not much more to put here, other than,it works well.

This brand is overly shilled here It's a dead-end camera brand (wait) Just my opinion, of course And these are not good shills - way too obvious - no spidey senses needed

Nope, don't need it. I've already shown the stream in the last post I did. He has that running 15 FPS. Not interesting. Anyway, CK2 works with any standard camera, yesterday, today, and tomorrow. But you have to know what you are doing. Remember when you asked me why (anyone) would use MPEG4/H264 when it only saved JPEG? You thought that was the way everything worked because all you know was Blue Iris. And that was recently! Hey, what's with this? To focus a dawho? How hard can that be? Posted: Tue Aug 14, 2012 3:09 am I would contact the people that sold it to you for instructions on focusing the camera. For network camera articles and reviews, visit my blog at http://www.Network CameraCritic.com http://www.networkcamerareviews.com/forums/about6729.html On a side track now, thanks to you. Here we go. I've given you ideas on how to do a critique before. I don't call what you do shilling since people reading your stuff know you get the stuff for free. The post here saying "there's a shortage", by two guys using the same sort of name, here for a few days, linking to a particular store. Yeah, that's overly-shilling. But you took that personally. I wonder why? (And what are you doing in that very same thread? Isn't that ironic.) Since you are into this sort of thing, how about starting all 'reviews' with this, in plain sight, like the first sentence: "This is a review I did on ________, which was sent to me by __________ for the purpose of writing this review." Hey! Try it. And how about using it for a few weeks or more, before blogging. You can't find problems, like the guy here whose recordings self-erase, after a day or two. The end P.S. Nice that you keep the nwcamreview site from turning into a dustbowl. True, they are posts about your new blog reviews, but that can get a few things going. I don't follow here much so I can't say how dry things are, but when I see nearly the whole of the index showing dawho, it's probably a shill job. And I am right.

The post right before mine viewtopic.php?f=19&t=32021 and in general here. And for Carl, who never can quuuuite get these things http://img715.imageshack.us/img715/8369/dahuaipchdb3200c704x480.png but that's not the point (dawho has no docs on how to make its cameras work -- even the guy who gave me this stream URL didn't know how to get it to 2 MP mode, from his browser, ... well, here, read yourself http://www.networkcamerareviews.com/forums/about6729.html As for CK2, it is where it has been for the last few years. Runs 24/7/365/3 years now. Same version. If it weren't for SPs and long power outs, it would be over 1000 days of 100% uptime. But, that really is OLD news. Anyway, soon to replaced. What? You didn't know.

Why go Ir when you can go visible? Bad guys like the dark. Make it light. Better to scare them away than capture ghost-like images of them carting your stuff away. There is a backyard light already there. And it's off. LED is not the way to go; much better light-for-the-buck with newer CFLs. Get a dusk-to-dawn. Lasts three years. 65 W gets you a lot of light. And no ghosts.

Android is also a tablet (may not even have a cell radio). Anyway, going to an even more extreme of oblivion, Windows Phone 7. It does do multiple camera (up to 10 at a time), and even h264 at a smooth 30 fps. http://www.windowsphone.com/en-US/apps/66274dac-f8c0-42e7-9537-ec1aff1c1477

Take a look at the screenshot. The camera windows are 320x240, but the full resoltions are pulled and decoded; the directx is doing the scaling down. No diff if I pop the windows up to full size, move to other monitors, or time of day (well). If the attach doesn't, here is an imageshack, too (an 8-bit PNG, about 333 KB) The taskmgr is at the far right. Yes, 2% CPU with the 9 cams viewing. (Can't add the PNG here since the limit for me is 150 KB, but JPEG that wasn't anything but awful was much bigger than the 8-bit PNG.)

The 207 line has an updated FW 4.44.1 and 4.44.2 that might have this in there (it's not in FW 4.40). I say might because I had to take it off mine. See this for why: http://custforum.axis.com/viewtopic.php?t=1481 (the follow-up post). There were several breaking changes in the API to bring it more or less to the v5 FW API, and since the scheduled snapshot is in v5 (m10*), you may be in luck. If you use MPEG-4, you will want to avoid 4.44.x for the 207, 207w, and 207mw. It's that bad.

Samsung dev register does not like a space in the city. San Antonio won't work. Weird.

Don't use port 554 for motion-jpeg. Don't use rtsp for motion-jpeg. I suppose some cameras stream mjpeg over rtsp, but it's pretty weird. Usually, mjpeg is done over http, port 80.

I can't say about MP, but here's an Atom N270 (single core w/HT) at 640x480 at a smoooooth 25 FPS Yes, this is h.264, an Axis M1031w. It's quit bad at low light noise so very poor compression (mpeg4/2 does a bit better in this location, and much less CPU still). The p-frames are almost the same size as the I-frame; at 320x240 it does much better (much smaller p-frames) at this location. That's CastleKeeper2. Below is a link to the same shot (a few days later) with more light. The exposure gain in the above pic was set to Max. +30 dB). The CPU use is much less (10-15%), and the bitrate more reasonable (about 0.67 Mbps). The same machine, only a Classic XP theme is the difference. http://castlekeeper.40th.com/gfx2/tmp/asus1000ha_m1031w_h264.jpg To show that it can do h264 (640x480@25 pretty easily), not that you'd want to use an Atom to decode. For recording, though, an Atom like the 330 (which I use to record), is perfectly fine since it uses practically no CPU at all, not even when recording six full-rate streams. P.S. "CPU %" is based on having 2 cores, so seeing "15%" is 15 over both. If you consider it running on a single core (which any one decode does in CK's case) then it's more like 30%. Other cores can run other cameras (or the UI, etc.). The point being, as long as it finishes the job (decoding each frame) on time, it works. To put it in perspective, here's the same on a Q8200 (cheapest quad Intel used to make), different location. The TaskMgr blipped every now and then. http://castlekeeper.40th.com/gfx2/tmp/Q8200_233_h264.jpg It also shows that the Axis M10* line is not focused for outdoor use; the older 207s could be focused.

An i5/i7, anything except Atom, will always beat an Atom. ha Thing is, if you are not CPU-bound, it doesn't matter. Here's a screen shot I used before, elsewhere, a long time ago, and at the time I didn't think much of it. It's an Atom (330) recording, at the time, six IP cameras. The bottom of TM shows CPU usage: 1%. This is a little server (ws2k3, 2GB, Atom 330, runs 1.6 GHz (Atom GHz)). Plenty of power. The hardware (headless) was under $200, including case/PS (150W. maybe more), 2GB DDR2, 750GB WD blue. Uses about 50W or so, by itself. Link is to image shack, inline (just to see if I can), but URL first: http://img710.imageshack.us/img710/3452/netuse6cams.png

If you are talking about digital, as in IP cameras, then there's nothing different about HD or any other D. There's no more effort in recording 1920x1020@30fps than there is recording 640x480@30fps since it's all just a stream of bits. There are more bits, but it's a trivial job to write 10 Mbps (that's only about 1.2 MB/s, and a typical OS/disk can write 30 to 100+ MB/s, per disk). For software that needs to decode to get events, then there is much more work since the stream has to be decoded, and processed, and this can be intensive,(it's an area thing - it's probably linear time - but still abouy 600% more intensive between the two sizes I used). As for just plain putting it on disk, like all good software should should (uh-hm, like mine), that's hardly a blip.

Yeah, I've heard of that but haven't thought about it for a while. Anyway, http://img687.imageshack.us/img687/1583/def169254.png Instead of messing with the camera, I put the camera onto my second network (it is working), from 192.168,0 to 192.168.1 I'd think that would have the same end result. If I had the guts I'd switch the camera, but it's not easily gotten to if it doesn't work (assuming the default address [169.254.] given is not the norm). It found the camera, but the address is ... well, maybe I've got one too many switches in there. I'm sure it would work connected up directly. Ethernet adapter Local Area Connection 7: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.0.180 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : fe80::201:29ff:fed6:2f15%4 Default Gateway . . . . . . . . . : 192.168.0.32 Ethernet adapter Local Area Connection 13: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.1.180 Subnet Mask . . . . . . . . . . . : 255.255.255.0 IP Address. . . . . . . . . . . . : fe80::201:29ff:fed6:2ee3%5 Default Gateway . . . . . . . . . :

I suppose that would work if you plugged the camera directly into the PC, or an old-style hub. It won't work if you plug it into a switch because it will never make it to the PC. You may need a crossover cable for the direct connection (maybe not). If (OP) has used wireshark, run that while you're at it. You may see the camera broadcast something. Connect the camera directly to the PC.

Using a where's my camera applet won't do anything more than he already has done. If the camera is assigned a static ip on, say, 1.2.3.4 and his network is on 192.168.0 then it won't ever see 1.2.3.4 (or anything not on 192.168.0). Nothing short of a reset to factory defaults will do this. You could call in an IP camera psychic detective, but they are hard to find. The LEDs will go back on as soon as you properly do a reset. Check the manual again. Some Vivos need the power removed, then while pressing the reset button in, power it on (and continue holding until you get a sequence of some sort). [ .sig would go here (you could bing "40th" )] (getting there)

Intros: Computer programmer for devices, with network cameras being my current interest. Current as in last two years. Coming RSN is a general-release version of all I've done the past two years with network cameras, built upon the stuff I've done the 25 years prior. Nothing short of perfect will do... ideally; sacrifices are made but only where it doesn't matter. [ .sig would go here (you could bing "40th" )]