I'm currently working on a recording capability so CamDesk can record/take images for x amount of milliseconds (default is 3sec, or 3000 milliseconds) the files will be saved to your hard drive by default.
Now say you work 8h which is 28800s so before you go to work you start CamDesk to record, you come home 8 hours later, and stop it from running. Now if divide 28800 by 3 that will give you 9600 which will be the total amount of images on your hard drive. Remember the bigger the image, the larger the file size. If your house gets robbed you want a larger image to work with so you can catch the perpetrator. I'd recommend watching this
film before proceeding.
So say you have a standard webcam like most people, and you have the dimensions set at 640x480. Now each file size will differ, but just as an example to understand the space you'll be dealing with on a day to day basis if you don't have a large capacity hard drive. Just as an example say every frame takes an image at 640x480 and the file sizes are all the same at 705KB. So in order to find out approximately how much space will be consumed on your hard drive from these files being taken we'll need to multiply 705 by 9600, which gives us 6768000.
1MB = 1000KB
1024MB = 1GB
1GB = 1048576KB
We can now go to Conversion Calculator
and see how much space 6768000KB takes up in gigabytes, and megabytes.
6768000KB = 6,609.375MB
6768000KB = 6.4544677734GB
So just in one day running the webcam at a 3s interval for 8 hours just to work and back will consume about 6.4GB of your hard drive space.
Storing Images in The Cloud
Now I've been thinking about CamDesk storing the images on the cloud. Eventually you'd only haft to pay $1 a month (via pay for storage, if you don't pay, you can't store the files online.) I'd haft to start with about maybe $2.5 or $5 for you to host, and eventually overtime depending on how many people will be hosting their files decrease the price to reach a broader audience, as well help me out with unemployment. I'd need unlimited hosting for webspace, and bandwidth. So if you'd like to helpout with this idea you can contact Michael
, or Google+
Now hosting your images online has both pros and cons. Although I've also been thinking about the recent violent derecho storm that hit, leaving 13 dead, and 3 million without power
With events like this and Hurricane Katrina we can clearly see much our cities rely on mostly fuel for transportation, and even some electronics like a weed trimmer. Also remember that when these events occurred massive amounts of individuals lost everything, they rushed into stores for food, medical, and other resources. Not to mention hundreds of home robberies occurred. However lets say you made a wind mill, or grabbed the electricity from the air
to power your laptop, or even small electronics like your smart phone, and now you can use CamDesk, but you don't have the cash to store your images in the cloud. While it has pros and cons these are things our development team hast to consider when creating CamDesk.
Here's some sources you may wanna checkout...
http://www.wired.com/dangerroom/2012/03 ... tv-remote/
http://www.theblaze.com/stories/monitor ... cking-you/
http://www.theworldsprophecy.com/senate ... rown-food/
http://www.scribd.com/doc/30618074/U-S- ... Gov365-com
http://iblue.hubpages.com/hub/Honey--Ci ... -for-cures
http://www.organicfacts.net/health-bene ... elion.html
http://answers.yahoo.com/question/index ... 104AAoHSp6
Now CamDesk for Android's development isn't going so good, just like the Chrome extension isn't going so smooth either.
The problem currently is that originally when we tried CamDesk for Chrome we had a div display over the page content and added an anchor so when you hover over the div you would close it, but you aren't able to drag it, because we'd haft to have it set to drag the flash swf file which is used to show CamDesk, and if that's done you won't be able to choose allow or deny to function the webcam's display actions. Which essentially means you won't be able to run the webcam, but merely drag it, and will be stick with the screen to allow, or deny the webcam to run.
So the plan now is to use hotkeys to show and hide a div that'll be displayed in a layer type system so we can move, and use CamDesk.
If you're unfamiliar with layers (or z-index in css) think of it as a stack of paper. We'll have div1, or p1 (p1 meaning paper1), div2, or p2, and a1, for anchor 1 via the close button.
So p1 is the div that the webcam will be embedded in, and p2 is the div that will be set on toggle to show/hide via hotkey so we'll be able to move CamDesk.
Now one problem with this idea is that some people tend to change the hotkeys that function their computer, some websites use hotkeys, and you maybe running a program that has/uses global hotkeys like AltWindowDrag on Windows
Although this isn't the biggest problem that we're experiencing. Our biggest problem with the CamDesk for Chrome development is that say I go to Google and I display the webcam, allow it to broadcast, and set it where I want. I do a search for, "DIY HHO Welder", but as soon as I get to the search results the webcam doesn't display, nor will it remain on the page when you change websites, or tabs, but it's still synced to the website you added it to. While some may like this I do not, and it's something that should be optional to choose from, as well as to choose to have it synced with each tab, and website, but currently we haven't figured out how that can be implemented into the application. So currently the CamDesk for Chrome development is at a pause until this is resolved.