jerblack

My eyes are pretty light-sensitive, so I enabled Dark Mode in Windows 10 and also the High Contrast theme in accessibility settings in Windows 10. This is great because almost every app that I use runs in a kind of dark mode for Windows and I'm not blinded by bright white backgrounds in apps any longer. Well this is true for most of the apps I use, but yours is an exception. With your app, you've chosen to allow the font color to change with theme changes, but not the background, so enabling the High Contrast theme puts a white font on your hardcoded white background. Here's what that looks like: / Can I ask that you do one of two things? 1. Hardcode everything so the text is black where it needs to be to stay visible. Why allow it to change when changing can only cause problems if you are not going to change any of the rest of the interface when the theme changes? 2. (Ideal) Properly support themes in Windows so that when High Contrast is enabled the interface is displayed properly, the background can darken, and the text will be more readable. It should look closer to this when High Contrast is enabled.

Totally agreed on this. Warning me that you don't like my password is one thing, but enforcing it as a requirement and placing restrictions on what I can and cannot choose is going too far. Keep your opinions out of my environment please. You're not my administrator here, and thinking it's your place to enforce policies on my system is not cool at all.

It might be necessary to adjust the prefetching depending on whether you are importing or watching content. From what I understand of prefetching, it's saying that anytime more than 1MB (the prefetch trigger) is downloaded, it will continue to download another 100MB (the prefetch forward) from that same file with the assumption that will will need that part too. This is a good assumption when you are playing the whole file, and it certainly seemed to smooth out many of the playback issues I encountered when I first started using CloudDrive with Plex. However, if you are importing a ton of media to your Plex library, it might be overkill to download that extra data (especially set at 100MB forward), and it will probably end up slowing down the import process quite a bit. At the moment, I am experimenting with reducing or disabling prefetch during import and turning it back up when I'm done.

What steps should I be performing to ensure my CloudDrive survives a build to build upgrade with no problems? I've been (1) clearing my local cache and then (2) detaching the disk before upgrading, and then I just reconnect to the disk after upgrading and rebooting. Is all that necessary, or are there additional steps I should be performing to be safe? To be clear, I am talking about upgrading periodically from here: http://dl.covecube.com/CloudDriveWindows/beta/download/. I've been upgrading every 3 or 4 builds recently. Thanks.

I am currently sharing video content through Plex to multiple remote users by just having my Plex server index the content that is stored in my CloudDrive hosted on Google Drive. I have gigabit fiber with no caps though and unlimited space on my Google Drive, so It's easier for me to host Plex for remote access that way. I found that I need to jack up to prefetch settings quite a bit to get acceptable performance. (Trigger:1, Forward: 40, Window: 3600), but after making that change I have no problem streaming from my CloudDrive. I have the bandwidth to support that though. If you are bandwidth constrained, then you can try using Plex Cloud Sync (needs Plex Pass). Then you can store your content in your CloudDrive, and then sync it to Cloud Sync (this means two copies of all your content in the cloud). When your remote user streams from Cloud Sync, they are streaming directly from your cloud provider (Google Drive, ACD) bypassing your Plex server and it's limited bandwidth entirely. You still need to use your upload bandwidth to sync the content up to Cloud Sync and your CloudDrive initially, but once it's there, it's there and all streams will come from the cloud. Some people also use SeedBoxes (a 3rd-party hosted VPS) to host Plex along with their torrents, but you would need a Windows-based host to make that work with CloudDrive. Check out r/seedboxes on Reddit for more info.

I tried that too. Getting RPC server unavailable from within Disk Management. I also get it the same error from diskpart.

Also, what is the current recommended (stable) build to use that has Google Drive support.

I have just begun my testing of CloudDrive and I'm already running into an issue with creating a new on my unlimited Google Drive account. I've tried on two machines so far, and while I was able to create a drive at first, I destroyed it and tried creating another and now anytime I try to create a drive the formatting never completes. I moved to another Windows 10 machine and installed the trial there and I can't create a drive even the first time there. Sometimes the formatting times out and I see an RPC server unavailable error in the CloudDrive GUI. Sometimes the drive just stays uninitialized. This is on the latest 64-bit beta build 1.0.0.444. Here's the settings I am testing at the moment, though I've varied most of them and still saw a problem creating the drive. Drive name: GDU Drive size: 20TB Local cache: 1GB and autounlock set Drive Encryption : On with pass key Local cache drive D: (my second, non-system SSD) Sector Size: 8kb Storage Chunk size: 100mb Chunk cache size: 100mb Verify chunk integrity: on Format and assign: on That knight-rider status bar switches from yellow (formatting) to green (status) and then back to yellow (pinning data) and then back to green, but I never see a new drive letter appear. This is also the time when I get the RPC server unavaiable error. (HRESULT: 0x800706BA). When I look at the disk in disk management, it just shows a 20TB RAW formatted parttition. If I try to format it, the format dialog does not show a file system or allocation unit size in the dropdown, so I can't proceed. What should I try next?