Statikk
-
Posts
13 -
Joined
-
Last visited
-
Days Won
4
Posts posted by Statikk
-
-
Any currently supported version of Windows should be fine for CloudDrive. (7/2008 server and up)
One thing to note when using the conversion utility (for me anyways) was that after converting I couldn't mount the drive under the local disk provider until I opened the newly created Metadata file with notepad, copied the uid for the disk (since it was now different) and pasted it over the old one in the folder name.
-
-
Thanks for the info Christopher. Got a GDrive account last night. I'll just use Amazon as an under-performing GDrive backup lol!
-
I was hoping to create new drives because they were older and some data chunks were showing as photos in Amazon's web panel. Is it planned to re-add the capability or will ACD be dropped from CloudDrive completely in the future?
-
After my PC took a dive the other day I rebuilt and reinstalled and decided to install the latest version of CloudDrive. After installing I tried to create a new drive since all of my old drives were created on much older builds. It looks as though creating new drives in ACD has been disabled with this build. Is there any way around this? I was using my own developer key in the previous build also. Has that functionality also been removed?
- KiaraEvirm and Antoineki
-
2
-
I'll have to run RAMMAP next time to see if this is the cause for me but I experience the same issues after a week or so of uptime and lots of uploading. Server slowed to a crawl while showing very little of my RAM in use. Then I reboot and everything is snappy again.
-
Using build 636.
-
When I log in from the ACD web app some of my chunk files are showing up under the photos section. I guess my concern is that at some point amazon may treat these files differently than files that it sees as misc data files and I'll end up with missing chunks. Should I be concerned?
- Ginoliggime, KiaraEvirm and Antoineki
-
3
-
Thanks for the honest answer. I don't mind waiting. I'm still blown away by how well the software works, and with multiple providers. Back in the Bitcasa days after years of development with a team of developers they couldn't even get simple uploads/downloads working properly with their own cloud. What you guys have done is pretty awesome.
-
So should I stop uploading to my current drives until the new provider is created using the new API? I don't want to continue adding more to the drive if it's possible that I will just end up having to transfer it all and into a new drive for it to be compatible with the new provider. Also curious if at some point when Amazon kills access to the old API will we suddenly be without access to those drives? And I guess that leads me to a final question...if at some point any of the providers decided to block our suspend our API access are we able to download all of the chunks etc. that make up our drive and retrieve the data from it offline?
-
I have plenty of space and I figured that if for whatever reason my available bandwidth drastically fluctuates then I'll have enough data prefetched that I won't have an interruption in playback. As far as the timeout I have it set high in case I need to pause the movie and take the dog out, or take a phone call or something.
-
For reference, Alex (the Developer) uses uncompressed (raw) bluray rips (of Star Trek, if it matters) to test the prefetching performance. And he has ~50mbps down, as well.
Sorry for digging up an old thread, but this is exactly what I'm trying to do. It always seemed to work well with lower quality files but not so well with raw bluray. Since creating a new drive with Amazon api keys I can successfully stream after I let it buffer a bit. The performance in Kodi is good enough that I purchased the software, however I'm wondering if you could ask Alex what settings he has found to work best. I already deleted the drive I was testing with, so I'm not sure what my exact settings were, but it was something close to these:
Provider: Amazon Cloud Drive (with api keys)
Drive Size: 100TB
Chunk Size: 100MB
Pinning: Directories and Metadata
Cache size: 45GB (expandable)
Download Threads: 5
Upload Threads: 2
Upload Throttling: 11776 Kbps
Prefetching: Enabled
Trigger: 1 MB
Forward: 5 GB
Window: 3000
I think the biggest problem is the amount of time it takes to start playing, which I assume could be decreased by decreasing chunk size but that would probably sacrifice download speed as well as potentially leading to problems creating download threads (denied by Amazon or something). My provider is Comcast and I'm usually between 100-140 Mbps down and 12 Mbps up. My testing was performed when there was nothing to be uploaded on the test drive.
I also wanted to say thanks for the bundle package. The value for the money is amazing and I love all 3 products! It would have taken me quite awhile before I could have scraped together the cash to get all 3 separately (if ever) and they all compliment each other so well!
"The given key was not present in the dictionary."
in General
Posted
I recently decided to attach my amazon cloud drives after months of them being completely detached. I was basically just hoping to move the data off of them. When I try to attach every one of the drives using the older version they were last attached with and the newest release version I am getting the error "The given key was not present in the dictionary." and the METADATA file for that drive is moved into the ACD trash automatically and the drive is marked as destroyed. If I restore the METADATA file and refresh the drive no longer shows as destroyed but repeats the same behavior when I try to mount it. I realize that ACD is no longer a supported provider, I'm just hoping there is a way to attach my drive a final time to pull some things off.