Autosave to Creative Cloud

[James Edmunds]

I cannot add autosave to Creative Cloud 2014, get an error message when checking the box on preferences Auto Save - "Savie backup project to Creative Cloud."

Error message:

"Saving backup projects to Creative Cloud requires a Creative Cloud Files directory. Please install the Creative Cloud desktop application on your computer to enable this feature."

Choice to use Creative Cloud then greys out.

However,  I do in fact have Creative Cloud installed on computer and do in fact have a Creative Cloud Files directory.

Thanks in advance for any help you can provide.

-James Edmunds

New Iberia, LA

[Please choose only a short description for the thread title.]

Message was edited by: Jim Simon

[JOHN MONDO]

Jim_Simon wrote:

with Adobe you get zero response to a problem

The response to bug reports isn't immediate, but it is there in the form of fixed bugs.  Same with new features.  We don't normally get any acknowledgement when filing those (I imagine that would be a huge time suck for Adobe), but we do get new features.  If you didn't get yours, it's because they're still working on it, not enough people want it to make it worth their effort, it's not technically feasible, or it's just plain a bad idea.  (I'm sure they get those aplenty.)

JIm what I'm saying is thats not good enough (on bugs at least) - this is a software company - there should be an interactive online system that once you lodge a bug report you can go back and check on its progress. It takes less time in the end than responding to emails etc if all a tech has to do is update a published table.

I've seen this system in operation and it works well - just 3 columns - the bug lodged along with a number, the confirmation column ( yes we've confirmed thats a bug or we can't replicate it - more information needed) and the third column is where its up to. Once its closed its closed. It saves hundreds of users lodging unnecessary bug reports because you can check and see if its already been logged. Well I'm oversimplifying because with Adobe you need to know versions, platform etc but you get the picture?

And at least you know without having to wait for the next software release whether a bug is being addressed. What your proposing is wait until the next software release and see if its been addessed? And you think that's good enough? And enough positive feedback to encourage users to keep using that system? What if it hasn't been addressed - do you just assume that:

a - Its a problem with my system?

b - Adobe can't replicate the problem because they don't have enough information.

c - Adobe know its a bug but have have classified it low priority (they haven't got time to fix)

d - Adobe have scheduled it for release xxxx

It's just my opinion but I think the first system has a lot more merit.

[Kevin-Monahan]

there should be an interactive online system that once you lodge a bug report you can go back and check on its progress...

While I appreciate your ideas, please give us feedback here. In the future, keep forum posts on topic. Take off topic discussion to the Video Lounge.

Thanks,

Kevin

[JOHN MONDO]

Hi Kevin

I can report all fixed with latest version v9.1.0

cheers

John

[excited_Genie16B8]

What I would like to see is when enough users complain about a particular problem that someone at Adobe actually takes ownership and follows it through all the way to a solution.

They do exactly that.  But they don't use the forums as their gauge, they use the Bug Reports.

[Guest]

Thank you so much spnsir (and of course Bill Mountney) for your help in explaining this. It's such a simple yet effective workaround!

As for you Adobe - your customers spend enough time and money on this software, so can we keep these ridiculous issues to a minimum please?!?

[DarrenManden]

This was excellent. Thanks very much to both you and Bill Mountney​ for this. It's been a bane for ages, until I saw the registry fix, and boom! I suddenly have my files backing up to the cloud again.

Time to submit another bug report...

[RodRJ]

Bill Mountney escreveu:

I have a better workaround for anyone who isn't afraid to edit their Windows registry.  Yes, it's possible that you could screw up your whole system by editing your registry, but on the other hand you could get electrocuted while changing a light bulb.  Just be careful.

Thanks to the wonderfully useful utility Sysinternals Process Monitor, I was able to determine that Premiere Pro is looking to find your Creative Cloud folder path in the registry key "HKCU\Software\Adobe\CreativeCloud" in a string entry named "CloudFolderPath" that does not exist.  When I examined the other entries in that registry key, I found one called "ActiveCloudFolderPath" which suggests to me that the Creative Cloud developers changed the name of the entry and the Premiere Pro team didn't get the memo.

Anyway, if you add the missing string entry "CloudFolderPath" and set it to the same folder as "ActiveCloudFolderPath" it solves the problem.  Undoubtedly, if you were to change your Creative Cloud folder location afterwards, you would need to remember to update this entry manually to match, since only the "ActiveCloudFolderPath" is going to get updated automatically by the Creative Cloud program.

Now, this comes with the usual disclaimers: try it at your own risk, I'm not responsible if your mouse explodes, etc.  It solved the problem for me, and as someone who has been involved with IT and programming since the eighties, I can't see any way that adding this entry would cause any major problem -- and if it did you could certainly solve it by removing it again.  If Adobe releases an official update that solves this issue, it might be best to go back in and delete the key before installing it, but as long as it's pointing at the correct folder even that would be unlikely to cause a problem.

Now yes. thank you.

[Brea Bill]

Yup, that did it.  Thanks!!!

[Shadreck Rukweza]

Same problem here!

Edited by Kevin Monahan. Please see community guidelines for allowed content.

[jonathana52588246]

Nearly bought a new macbook today on the back of this feature, so glad I didn't bother!

[chrislohar]

I'm having the same problem. CC 2.3.0.151 and PP CC 2015.0.2 release. OSX El Capitan v. 10.11

I save the files to their appropriate project folders on various harddrives. And I keep the autosave files in the "same as project" folder. I don't want to create an autosave directory in the cloud. I want to create a backup directory in the cloud.

Is this solved yet?

[turnleftkr]

Has this been fixed in the new update or are we still SOL?

[excited_Genie16B8]

Working for me.

[Shadreck Rukweza]

Working for me.

How did you get it to work for you?

[excited_Genie16B8]

I updated PP and turned the feature on.

[turnleftkr]

I am mid-project so I have to wait to update, but that's good news if it now works...

[excited_Genie16B8]

Waiting might be a good idea.  I think I've found some audio bugs with 2015.1.  (Still testing.)

[turnleftkr]

Thanks, just saw your post on DVXuser, too

[Guest]

This was working initially on the new version, but now I'm having the same problem as before. Uugghh!!

Has anyone else experienced this problem?

[abdelkarimy82346684]

Thanxx you so much spnsir and Bill Mountney

[turnleftkr]

Just installed PP 9.1.0 and autosave to cloud is fixed...

[Maskkot]

not fixed for me. running latest update of el capitan installed on a clean drive and the latest PP CC 2015 with the latest update. nothing else is installed. clean iMac  with PP. Logged in the cloud. same issue.

[dzsokolino]

Not fixed on here on Mac OS either running the latest software.

[cowboycoffee]

I'm running the latest Mac OS and everything was fixed for me when this update came out. It's been pretty bullet proof for a couple weeks now.

[onefjef]

Yes, I just reformatted and clean installed everything on my 2015 iMac, and this still isn't working. Newest updates.

I'm kind of flabbergasted, actually -- I thought a clean install would solve it, but I guess I'll just have to pretend this feature doesn't exist.

Keep up the great work, Adobe.