-
Posts
7 -
Joined
-
Last visited
Posts posted by Achmed
-
-
I am wondering if the 20 second delay to start playing a file in plex is something that can possibly be reduced with future developments to Stablebit Clouddrive? I know Netdrive works completely different but it can usually start a stream via plex in about 5 seconds for me.
I think it would be possible, I'm moving a heap up to the cloud, but I'm also happy to keep a massive amount of local cache as well (I think I have 100Gb set atm)
Anyway, I really want to come back to CloudDrive, I find the drives more responsive for browsing, and I like the product more. But until the down and up are working at a more reasonable rate, then I can't work with it.
My NetDrive works mostly perfectly, just uses (well seems to at least) more resources than CloudDrive.
-
I'm having to move my media back to NetDrive at the moment, the speeds offered are just not workable for a smooth stream.
(I'm not a fan of NetDrive, browsing is much slower, less configurable etc) - but my Plex Playback is the most important for me, and that doesn't seem to be working as well as it should right now.
I really hope this is fixed soon.
-
-
Thanks - got the license extension.
Suggestion - In the email -the license has curly brackets { } - if you copy / paste those into the license (as it wasn't clear if they were required) then the app hangs attempting to activate.
Either don't include them in the email, or if they are included - handle the { } in the field by stripping them out first.
-
Thanks, I was on 1.0.0.403
I've updated to the latest beta build.
So looking forward to proper Amazon speeds, btw, this is an awesome product outside of the limitations on Amazon.
418 / 419 failed to start properly.
The Service keeps dying and restarting. (Windows 10 x64)
Faulting application name: CloudDrive.Service.exe, version: 1.0.0.418, time stamp: 0x5653e1c8Faulting module name: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f38c3Exception code: 0xe0434352Fault offset: 0x000000000002a1c8Faulting process id: 0x11a4Faulting application start time: 0x01d12879284e244cFaulting application path: C:\Program Files\StableBit\CloudDrive\CloudDrive.Service.exeFaulting module path: C:\Windows\system32\KERNELBASE.dllReport Id: 7d1241b8-bd7f-4b2d-940a-f3bd51f0dca1Faulting package full name:Faulting package-relative application ID:AND
Error report file saved to:C:\ProgramData\StableBit CloudDrive\Service\ErrorReports\ErrorReport_2015_11_27-05_35_05.0.saencryptedreportException:Where do I upload the crash report?
Depends on what version you're on. If you haven't already, update to the latest public beta version. If you're on that (1.0.0.403), then try grabbing one of the internal betas. That should reset the trial period.
Index of /CloudDriveWindows/beta/download
If that doesn't help, let me know, and I'll send you a trial extension.
-
I'm at 7 days away from my trial expiring and the key purpose of this is to use Amazon Drive.
Any chance of extending the trial? I'm super keen on this product over Net2Drive, however, I want to be sure of the speeds available in this product.
Drive is marked Read Only when a drive is missing from the Pool
in General
Posted
When using DrivePool in conjuction with CluodDrive I have a problem when uploading a large amount of data.
I have the following setup.
3x 3tb Drives for Cache for CloudDrive with 500Gb dedicated and the rest expandable.
I am in an EU Datacentre with 1Gb/s internet connectivity
I have a DrivePool with 3 different accounts - 2x Google Drive and 1x Dropbox.
I have another DrivePool for where my downloads go, that consists of space left over from the listed drives above.
When I attempt to copy / move files from the Downloads DrivePool into the CloudDrive DrivePool, one drive always drops off, Randomly, never one in particular.
But then DrivePool will mark the Drive as read only and I can't move media to the new drive.
I would have thought cache would handle this temporary outage, I would also expect that the Local Drive cache should handle the sudden influx of files, and not knock off the CloudDrives. I also would think that DrivePool would still be usable and not mark the drive as read only?
What am I doing wrong? - how do I fix this behaviour?