REAPER can't save projects in Google Drive File Stream

Kenten · 07-25-2019, 11:22 AM

I use Google Drive File Stream to sync Reaper project files between multiple work and personal computers. One of these computers is having a weird problem. When I try to save a project in Reaper, it says "Error writing to project file. Disk full?" Neither the local hard drive nor the Google Drive are full. This is a windows computer, and I am not having the problem on any other windows or mac computer. Other types of files, such as Word documents, can save into the Google drive folder no problem. Reaper can save projects to other locations outside of the Google Drive folder. Reaper version 5.978. Any ideas?

suchatravesty · 07-27-2019, 11:38 AM

I use Google drive to back up my Reaper stuff and I don't have any issues. I don't trust any kind of syncing though, I just go the drive website in a browser and upload any new work manually after I put it on an external backup drive.

I used the google drive sync software years ago and it gave my machine all kinds of problems, I was a lot less tech savvy back then though.

ezolhof · 05-29-2020, 09:06 AM

Did anyone manage to fix this? I'm having the same issue as of today

waltzy · 07-16-2020, 09:49 AM

Reaper 6.12c, Windows 10 x64, v2004 problem is still here. Anybody got a fix? Cubase don't have any problems working on cloud drives

poetnprophet · 07-16-2020, 01:20 PM

I'm not sure what the File Stream is, but I use Google Sync almost daily, I have several folders included in the backup list, on different physical drives, all works ok to me. I'm not sure if it's the same thing as File Stream, but I'm on 6.12 or the most current.

However, I have run into an issue at least once where I pulled a file/folder from the backup google drive (for another computer running reaper) and it was corrupted/unusable. who knows what else out of the 2TB is like that

waltzy · 07-21-2020, 01:32 AM

Quote:

Originally Posted by poetnprophet

I'm not sure what the File Stream is, but I use Google Sync almost daily, I have several folders included in the backup list, on different physical drives, all works ok to me. I'm not sure if it's the same thing as File Stream, but I'm on 6.12 or the most current.

However, I have run into an issue at least once where I pulled a file/folder from the backup google drive (for another computer running reaper) and it was corrupted/unusable. who knows what else out of the 2TB is like that

Drive File Stream emulates physical hard drive. So you can specify which files or folders are available online or offline in specific cache location. Reaper can load all audio and project files even i online mode, but can't save project file to DFS. However Reaper can write audio files without any problems so it's a bit strange behavior

jcgurango · 08-10-2020, 09:46 AM

Strangely, I've started experiencing this as well. It was working a few months ago. Is there some logs I can take a look at somewhere that might point to why? I've even tried making the entire folder "Available Offline" to no avail. My workaround at the moment is to save the project file somewhere else, and copy it into Drive FS.

lawrs · 08-10-2020, 10:45 PM

Me too, also using Google Drive File Stream. Been using it for a month, and problem only started occurring recently. Must have been a change on Google's side.

Liarco · 08-13-2020, 07:47 AM

I'm using the latest version available (REAPER 6.13) and I'm actually able to save projects, but whenever I bounce something it doesn't matter which folder I choose, the whole path is replicated twice from the root of my shared drive to my target folder.

The problem is that Google Drive identifies files and folders by IDs, not by name, so having multiple files/folders with the same name is perfectly fine for it. This means that if I try to bounce to a file like "SHARED_DRIVE_ROOT/Client/Project/Bounces/My Song.wav" then I will have two "Client" folders: the original one and a new one which contains just the folders down to the "My Song.wav" file.

I'm on MacOS 10.14.6, Google File Stream is updated and no other software is behaving like this at the moment.

-------------
Update: 2020-08-20

Today I'm facing the same issue with freeze. While I can render to an external folder and then move my files manually, having to do that for each freeze is a real nightmare

spwyatt · 08-25-2020, 09:00 AM

I've just started using Drive File Stream having been using Google Drive for years.

I'm experiencing exactly the same issue.

Reaper seemingly has no problems writing peak files, glued files or FX chain configs to the File Stream drive, but won't save RPP or RPP-bak files - giving the same error as others have been experiencing:

"Error writing to project file. Disk full?"

I'm running the latest FS client on Windows 10.

Any ideas? I moved from Google Backup & Sync as Google are changing the way shared drives / folders work and Drive Stream seemed a much more sensible way of working.

ezolhof · 08-25-2020, 09:08 AM

I've quit using Reaper for now because of this. Back to Nuendo until they fix the issue