Archive for category Reviews
I have been looking for a cloud storage, backup, and syncing solution for some time.I heard about Bitcasa’s much-hyped “infinite storage,” and decided to give it a chance. Here’s the high Level Take-away:
- I do not yet regret paying Bitcasa $100: The value proposition of paying $100 per year to meet my ever increasing storage needs is compelling.
- I really like that Bitcasa encrypts my data; for real.
- I plan to use Bitcasa for video and image storage and backup. I’ll use Dropbox for syncing, sharing, and collaboration.
- Bitcasa 188.8.131.52 is a step beyond beta. It lacks the intuitive feature set and interface of Dropbox.
- There is no “off” switch.
- Bitcasa is not Enterprise-ready.
- “Mirroring” is buggy.
- Bitcasa 184.108.40.206 is a memory hog, and will cause significant system degradation while uploading.
- Once it’s on Bitcasa’s (Amazon) cloud, don’t ever count on being able to delete it.
- I’m going to stick with Bitcasa for a while. I think it’s got a lot of potential.
Paying for the same hard drive every year doesn’t make sense
First, let me tell you why I find Bitcasa’s model so appealing. Once I purchase a hard drive, I shouldn’t have to buy it again next year. That’s why I’m an avid user of the free version of Dropbox. I’ve got somewhere around 11.5GB of free space, which I use to back up sync and share. But the idea of paying for the same storage again and again just doesn’t appeal to me. Yes, I know that I’m also paying for near universal access to my files, but that value proposition just doesn’t hold water for me.
I’ve found that the 99% of the files I need to access and share on a regular basis are primarily office documents—Word, Excel, PowerPoint, etc. These files tend to be relatively small, and I can easily fit them within my 11.5GB Dropbox allotment. But the remaining 1% of my files take up terabytes of hard drive space. I want a safe backup for family photos and videos, even though I’m not going to access them on a daily basis. Even if I theoretically purchased “unlimited” space from Dropbox, I would still be limitied to the size of my local hard drive, since Dropbox only syncs local drives and does not provide additional cloud storage.
Consequently, I’m not willing to pay a recurring fee for static storage every year. But I am willing to pay for ever-increasing storage needs every year, especially if I can free up local hard drive space for other needs. So the idea of paying $100 per year for unlimited storage makes sense to me.
Although I understand how Bitcasa offers “infinite” storage, I don’t quite understand how Bitcasa’s business model intends to deal with enterprise clients who will want to store Petabytes per month, assuming they have the bandwidth.
They’ve got the right idea about privacy
From my understanding, Bitcasa encrypts your files using a hash of the file itself as a key (please correct me if I’m way off base). This means that Bitcasa doesn’t actually know the contents of your files, but can still know if your file matches a file that has already been uploaded. This way, instead of storing 5,000 copies of Bieber’s latest hit, they can save space by storing just one and linking it to 5,000 accounts. In contrast to Dropbox, Bitcasa doesn’t know that it’s a Bieber MP3; they just know it’s the same file. I appreciate that.
This means that I’m much more likely to store sensitive documents on Bitcasa. Although I still have to worry about securing my Bitcasa username and password.
From a privacy perspective, Bitcasa has the right idea, though I think their privacy representations are a little over-the-top:
(Bitcasa Legal Policy, emphasis added). Presumably Bitcasa won’t share your content with law enforcement because it can’t share it with law enforcement.
That’s actually a slight exaggeration. For example, let’s say that two parties are in a dispute. Party A says that Party B stole Document C and stored it on Bitcasa’s cloud. A court could certainly order Party A to give Document C to Bitcasa, which Bitcasa would upload, and its systems would instantly know how many other copies of Document C exist on the server, who owns it, when it was uploaded, etc. That information would then be open to discovery.
While I don’t really have a problem with that sort of particularized discovery, I could easily imagine Bitcasa having to build tools to allow parties like the RIAA to upload MP3s to see who has a copy, if ordered by a court. I think Bitcasa is on the right track with privacy and security; I just think that some of their promises are a little over-the-top.
“Mirroring” is not like Dropbox
“Mirroring” is when you designate a folder to be synced on Bitcasa. I thought it would work like Dropbox, but I was wrong.When I installed Bitcasa, the setup asked whether I wanted to mirror my hard drive or key folders, like My Documents. I checked “yes,” and finished the installation. Very quickly I had second thoughts and decided to cancel the mirroring.
I unmirrored My Documents, then deleted the “Mirrored Documents” file, but somehow Bitcasa re-mirrored it and started uploading without my knowledge. I unmirrored again. Ironically, even though Bitcasa re-mirrored My Documents and uploaded it, the folder didn’t appear in my Infinite Drive.Try as I might, I could not un-mirror the folders. On occasion Bitcasa would indicate that a folder was un-mirrored, only to re-mirror it moments later. I panicked, and deleted the “Mirrored” folder on my Infinite Drive, and expected the uploading to stop, but uploading continued at 5Mbps (my max FiOS upload speed at the time), for 10 more hours. I could not stop it. There was no “off” switch.
Even though I had unmirrored my files, the icons continue to be marked “Mirrored,” but if they were mirroring, I could not see where they were mirroring to, because there was no “Mirrored Files” folder on my Infinite drive. And in the online interface, the “Delete” option was grayed out. For several hours I felt like I had lost control of my computer, and that Bitcasa was sucking it to the cloud, and there was nothing I could do about it. For the record, I attribute this to an immature product UI and feature set, rather than any malicious intent.I hopped on Twitter and engaged with @BitcasaSupport. Here is a synopsis of that conversation:
Me: How do I stop Bitcasa from mirroring my entire drive? Where’s the off switch? Should I just uninstall and reinstall?
BitcasaSupport: Sorry for the confusion – you can only unmirror via the desktop app, which you can download here: http://bit.ly/YGcr3C. When you right click on the folders mirrored, select Stop Mirroring to Bitcasa from the Bitcasa contextual menu.
Me: That’s what I tried- “stop mirroring” is grayed out everywhere. I chose “Mirror whole computer” on install. But I don’t know all of the local locations that Bitcasa is mirroring. It’s quite frustrating.
I mirrored my computer, then unmirrored it, but @Bitcasa continues to suck 5Mbps from my computer for 10 hrs. Very concerned. Why does @Bitcasa continue to suck up 5Mbps of my files without my consent? Can I stop it?
I had to kill the process to stop it from uploading. I have no idea what its been uploading for the past several hours. Is there any record of what has been uploaded, and how long @Bitcasa keeps it?
I am able to see old versions of my files, but the Delete button is grayed out. That is a problem because there are uploaded files that I never intended to upload. Is there a way to get rid of those files?
Support then opened a ticket for me, and addressed some of my concerns. In short:
- I had to completely uninstall Bitcasa, manually deleting folders. Fortunately I did not have to edit the registry.
- There is no “off” switch. Bitcasa chooses when and whether to upload.
- You cannot unmirror sub-folders. You must unmirror the top folder… if you can remember which one is the “top folder.”
- I still have no idea what Bitcasa was uploading for 10 hours after I had told it to stop mirroring everything. And I won’t ever have a way of knowing for sure.
- There is currently no way to delete old versions of documents, even if you didn’t want them online in the first place.
Bitcasa is a Resource HogI think this image says it all. Bitcasa significantly degrades performance when it’s uploading. To give you an idea of how much it affects performance, I am writing this article in Notepad right now, because my browsers and word processors are too painfully slow.
When I asked support about this issue, they replied that a recent instability fix created the memory problems. “We’re currently working to improving the memory usage of the application without hindering upload stability, and anticipate that improvements will be made very soon.”
You need a fat pipe to upload all of your junk
I mentioned earlier that I have a 15Mbps down/ 5Mbps upload internet connection. I learned that it takes a long time to upload several terabytes of data at 5Mbps. I upgraded to 50Mbps down/ 25Mbps up so that I won’t have to wait a month to upload (nevermind that my pipe is testing at 25 down/ 21 up–curse you, Verizon!). I thought this was worth mentioning because the cost of an Infinite drive may well exceed $100 per year, if you include the cost of additional bandwidth.
Even with a 21Mbps available, Bitcasa rarely uses that much. Occasionally uploads have spiked at 21Mbps, but as I type, my upload speeds are averaging 3Mbps. The last day or two, they’ve averaged 6Mbps. Not surprisingly, Bitcasa support is quick to point out the many factors that affect upload speed… none of which are them. While I have no problem blaming Verizon for many of my problems, I have a hard time believing that my ISP is solely responsible for a 85-90% degradation in my upload speeds. Sorry, Bitcasa, I still think you’re the choke point.
Notwithstanding the mild drama, I’m still hopeful that Bitcasa will pull through. As I mentioned earlier, I think they’ve got the value proposition right, and I think they’re on the right track for privacy and security. They can have my $100.
I recently purchased two sets of podcasting gear to record podcasts with someone in another state. The gear included two TASCAM US-144 mkII interfaces, two Audio-Technica AT 2020 condenser microphones, two mic cables, two stands, two pop filters, two sets of headphones, etc. As I recorded I noticed an inconsistent whine in the audio. Sometimes the wine was little more than a vinyl-record-like scratch, other times it was a scream, and still others it disappeared altogether.
To track down the source, I started by changing out the AC power for battery power, switching USB cords, switching mic cords, switching microphones, switching interfaces, turning on and off the wireless network, unplugging my wireless router, changing rooms, and even moving to a location several miles away. None of these things had any consistent effect on the whine. After a lot of trial and error, I have narrowed the problem down to two three variables: Temperature, Phantom Power and the MIC/LINE-GUITAR select switch.
The whine appears with the phantom power on, while the interface is cold (ie, less than about 65 degrees Fahrenheit). It gets worse when the MIC/LINE-GUITAR select switch is set to “Guitar.” Setting the MIC/LINE-GUITAR select switch to “Guitar” makes it act as an unbalanced input jack, which probably explains the noise. But turning on the phantom power while the interface is cold produces a lot of noise.
The solution: Sit on the interface to warm it up. My home “studio” is in a very cold room with two exterior walls, and it’s the middle of winter. So in order to warm up the interface—no joke—I actually put it under my thigh for a good 10-15 minutes. I didn’t read that helpful work-around in the manual. I thought about using an electric blanket, but I was afraid that might cause some induction damage.
I conducted a test to demonstrate the whine, which I have included here. For the test I had the following setup: I plugged an Audio-Technica AT 2020 condenser mic into the MIC IN L XLR balanced jack. I also plugged a crappy old dynamic mic into the LINE IN R/GUITAR IN jack TRS 1/4″ jack. For the “Cold” test, I left the interface in a box in my car for 30 minutes, where the outside temperature is around 25° Fahrenheit. For the “Warm” test, I basically sat on the interface for about 15 minutes until the interface housing was noticeably warmer than room temperature.
I then recorded a systematic test of the phantom power, left and right input levels, and the MIC/LINE-GUITAR select switch in 10-second intervals. I included the results in a table below, with each numbered setting corresponding to a period of time on the non-normalized .mp3 file. You can skip around to compare the different settings if you’d like. Please ignore the ambient noise of the HVAC system, as well as the lousy line quality for my crappy dynamic mic.
|Setting||Time on Tape||Phantom Power||INPUT L Levels
|INPUT R Levels
|1||0:00-0:10||OFF||Line (Low)||Line (Low)||Line/Mic||None|
|Setting||Time on Tape||Phantom Power||INPUT L Levels
|INPUT R Levels
|1||2:40-2:50||OFF||Line (Low)||Line (Low)||Line/Mic||None|
My home studio is in the basement near an outside wall, so it’s usually around 65°. Every morning the whine reappears until I physically warm the unit to around 75°+.
At lower temps, the phantom power whines and bleeds over into the 1/4″ inputs, which surprises me because most electronics are happier when they’re cold. I’d chalk it up to a defective unit, except that I purchased two 144 mkII’s, and both units display the same behavior. Regardless, I’m not looking forward to the hassle of returning or exchanging the interface. It’s going to put me back several weeks.
I wonder if anyone else has experienced these same problems. The helpful guys at Sweetwater didn’t seem to have bumped into the problem before.
[Update Jan 14, 2010]
I have decided to return the mkII’s to Sweetwater in favor of another brand, perhaps an M-Audio. I haven’t decided. At first I was content to swap them out for non-defective mkIIs, but apparently TASCAM has temporarily stopped shipping the US-144 mkII. More precisely, they are taking orders without providing a firm ETA. This is apparently quite unusual, and in the estimation of the guy I talked to it likely indicates that they are doing some re-tooling.
I decided that I’m probably better off not being the guinea pig for the “fixed” version (if, in fact they are re-tooling). And even if they’re not re-tooling, I don’t want to wait indefinitely for TASCAM to fill the order.
[Update Jan 25, 2010]
I decided to go with a Lexicon Omega instead. So far (in some preliminary recordings) I haven’t had any noise problems, thought the levels are significantly lower than the Tascam 144 mkII. I’ll just have to do more post-normalization. I hope the noise levels stay tolerable.