so your recurring expense is buying new hard drives and moving them around, if you remember
neither do hard drives
if that happens you put your local copy on some other cloud just like you would if your backup hard drive gave up the ghost
so your recurring expense is buying new hard drives and moving them around, if you remember
neither do hard drives
if that happens you put your local copy on some other cloud just like you would if your backup hard drive gave up the ghost
You obviously have no memory of what it's like to live in a place that provides only 1Mbps uplink speeds, and ping times of 24ms. Can you imagine managing multiple TB in the cloud using a link line that?
P.S. I can write 40MB/sec to the NAS, read >100MB/s. What's your link to Dropbox like?
You may as well ask why I didn't just plug it into iTunes and let it back up. I don't have enough space on dropbox free.
24 ms isn't fast? Geeze, I fell cheated!
Rick C.
Tesla referral code --
I recall a software engineering class in college where we defined what a pr operly working computer was. One of the principles was that no instruction could cause un-repairable damage. I asked if that meant it was ok if the computer could cause repairable damage... I'm just sayin'...
Rick C.
Tesla referral code -+-+-
That's just across town. It's 10x that to get to the USA and back.
I remember when we had to go geostationary twice to get from Australia to the USA, and again on the way back. It was about the same time that engineers at SUN Microsystems were thinking that RPC seemed like a good idea...
Clifford Heath.
what makes you certain that it's surely app store software-related and not related to a particularly unlucky series of hardware failures, or caused by a dodgy charger, or a Web-based scripting hack, or environmental, or (very unlikely but possible) some kind of targeted attack at your company's IT/communications infrastructure?
You ask many questions.. those things I have not tried. Your micro sdcard will be full with running on external power I would think. Would likely be simpler to buy 2 or more.... then you have some spare.
I am happy with the thing, exceeded my expectations by far. Sometimes designers get everything right, this is once such a case IMO.
Lasse Langwadt Christensen wrote
I carry a big size USB stick in my pocket that has AFAIK almost all the code I wrote and all the scripts I wrote. Since I have a website with godaddy in the US I have a non-public directory there with the same, that is my 'cloud' and does not cost anything extra, accessable from anywhere with ssh.
Then I have a metal case with close to a thousand optical disks ... some are MDISC same data and more like movies etc.. then I have 2 1 TB harddisks, one with sdcard images ..
But really, once I dropped a huge harddisk, life goes on you know. When the big EMP comes you probably have other worries, like hiding under the table for the nukes...
Cloud I do not believe in, the first thing that goes is connectivity if anything important like war or disaster happens.
And then when it all crumbles, you are better of with a survival course. all them bits do not really mean that much to me.
Can always write it again :-)
gnuarm wrote
Yea, ping 8.8.8.8 (googe nameserver) PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_req=1 ttl=119 time=145 ms 64 bytes from 8.8.8.8: icmp_req=2 ttl=119 time=33.4 ms 64 bytes from 8.8.8.8: icmp_req=3 ttl=119 time=32.7 ms 64 bytes from 8.8.8.8: icmp_req=4 ttl=119 time=31.7 msLOL same times for my website.
All via 4G.
Please don't believe that an IP packet to 8.8.8.8 goes to a specific host, probably one near Google headquarters in Mountain View, CA. It doesn't.
$ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=120 time=1.06 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=120 time=0.995 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=120 time=1.09 ms
In 1 ms, light travels only 300 km, but I live in Switzerland, not in California. Google has a big R&D site here in Zurich, but not a data center yet (the're setting up one, though). I'm fairly certain the physical machine that responded to my ping is not at their premises, but at some well-connected ISP.
- Andi
Andreas Karrer wrote
Of course not, but but but, you can easily verify that:
~ # traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 1 router (192.168.178.1) 0.771 ms 0.868 ms 1.108 ms 2 * * * 3 145.54.66.20 (145.54.66.20) 237.715 ms 262.715 ms 262.790 ms 4 145.54.66.21 (145.54.66.21) 273.032 ms 273.187 ms 273.042 ms 5 145.54.66.22 (145.54.66.22) 272.574 ms 272.781 ms 272.633 ms 6 * * * 7 * 139.156.127.73 (139.156.127.73) 38.578 ms 139.156.127.77 (139.156.127.77) 43.576 ms 8 * 108.170.241.225 (108.170.241.225) 36.604 ms * 9 216.239.41.213 (216.239.41.213) 35.218 ms 108.170.236.138 (108.170.236.138) 36.525 ms 216.239.51.5 (216.239.51.5) 39.181 ms
10 google-public-dns-a.google.com (8.8.8.8) 39.241 ms 216.239.41.221 (216.239.41.221) 36.804 ms google-public-dns-a.google.com (8.8.8.8) 40.706 ms~ # ip_to_country -i 145.54.66.20
145.54.66.20 "NL" Netherlands ~ # ip_to_country -i 139.156.127.73 139.156.127.73 "NL" Netherlands ~ # ip_to_country -i 108.170.241.225 108.170.241.225 "US" United States ~ # ip_to_country -i 216.239.41.213 216.239.41.213 "US" United StatesNow although that IP is assigned to google / US, also google has a datacenter here:
So 8.8.8.8 is local... (hour or so drive from here in a maxed out Tesla with full batteries ;-) ).
~# ping 8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_req=1 ttl=119 time=228 ms 64 bytes from 8.8.8.8: icmp_req=2 ttl=119 time=53.6 ms 64 bytes from 8.8.8.8: icmp_req=3 ttl=119 time=36.2 ms 64 bytes from 8.8.8.8: icmp_req=4 ttl=119 time=43.1 ms 64 bytes from 8.8.8.8: icmp_req=5 ttl=119 time=35.5 ms 64 bytes from 8.8.8.8: icmp_req=6 ttl=119 time=33.7 msI think the first ping switches the connection from gprs to HDSPA or LTE maybe.
But the ping to my website comes from almost next doors, where godaddy has contracted a server: ~ # ip_to_country -i 37.148.205.129
37.148.205.129 "NL" Netherlands~# whois 37.148.205.129 inetnum: 37.148.204.0 - 37.148.207.255 netname: GO-DADDY-NETHERLANDS-BV ....
Yep, anycast.
ip_to_country is on my website, IPV4 only:
It's an easy enough thing to check. Sometimes the internal charge circuit for the battery shuts off the DC/DC converter that drives the device. Most USB power packs work like that, it's annoying.
Just hook it up to the charger and record a few seconds, either it works or not.
You can get pretty big SDcards these days.
24 hours record time would be pretty nice.Clifford Heath.
You did not listen,
Now you own me 2 free drinks I'd say.
BTW THE BACKSIDE IN IN CHINESE ANY CHINESE HERE I'D BE GLAD TO MAKE PICTURE OF IT TOO.
Else just go and buy the f*cking thing and test it yerself.
You did not send that before.
Thanks.
Love to do that - next time I visit NL. Your work always impresses me.
Clifford Heath.
My apologies, I did mention the 32 GB card, as it is HD you will not get much time on it.
Also it violates (adding a big battery pack) the concept of 'small portable hardly visible etc'. you then get into a totally different concept, What then comes to mind is a raspberry pi with camera and a 1 TB USB disk and a huge lipo pack with switcher to 5V. still small, still < 100 $ I'd think. I do not have the raspi camera, I do have several raspis in all sort of projects, not sure that raspi camera is HD, or you could have it send via WiFi, in normal resolution that should work.
Do not underestimate the file size of the HD that 20$ thing records:
Below you see for a 4 minute 3 second, 243 second recording, a size of 1.18 GB. So on 32 GB card the max you can record is ((32 / 1.18) * 243) / 60 = 109.830508 minutes, or almost 2 hours as I stated.
/mnt/sdg1/video # mediainfo MOVI0002.avi
General Complete name : MOVI0002.avi Format : AVI Format/Info : Audio Video Interleave File size : 1.18 GiB Duration : 4mn 3s Overall bit rate : 41.5 Mbps Director : Generplus Original source form/Distributed : Generplus Copyright : Generplus
Video Format : M-JPEG Codec ID : MJPG Duration : 4mn 3s Bit rate : 40.6 Mbps Width : 1 920 pixels Height : 1 080 pixels Display aspect ratio : 16/9 Frame rate : 30.000 fps Resolution : 24 bits Bits/(Pixel*Frame) : 0.653 Stream size : 1.15 GiB (98%)
Audio Format : PCM Format settings, Endianness : Little Format settings, Sign : Unsigned Codec ID : 1 Codec ID/Hint : Microsoft Duration : 4mn 3s Bit rate mode : Constant Bit rate : 512 Kbps Channel(s) : 1 channel Sampling rate : 32.0 KHz Resolution : 16 bits Stream size : 14.8 MiB (1%) Interleave, duration : 1003 ms (30.09 video frames)
HD is a bit of a beast, and they did not save on audio bitrate either! No audio compression..
Too much honor for playing around I guess ;-)
Anyways above are the numbers.
Was thinking of a USB wall wart only, not a battery. Could probably get a Wifi camera in the same size though, and record to the NAS (which has CPU power to compress properly).
Actually with 2 or 3 of these on a drone you could use stereophotogrammetry to build a 3D image of any site you can fly through, even inside a cave. There's open source software for processing video, if you have the CPU grunt or time to wait for it.
Wow, that is huge, I'm surprised. Still, high-quality.
Clifford Heath.
Clifford Heath wrote
Yes, I have one like that, removed the WiFi module in it tough (was hacked once), and it is wired to the LAN, and on a wallwart. Wrote Linux software to record from it,
Yes, seen that.
A drone with a Sony super-had .. now that is something for night flight, videos are on the web:
there is more...
We upgraded from Samsung Note-5s to Note-8s a year ago. They've both been flawless, with enough battery to easily keep us going a day. I'm usually down to 45% at night, even though I use it rather heavily (email and ereader, mostly).
I use my old phones, one a five year old (at least) Droid MAXX, as MP3 players. I also have one at work to use with a FLIR One.
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.