Is this a Windows-only issue?
Yes, I believe it is. It apparently affects a wide range of Adobe products (AE, PS, and Bridge to be sure).
Not an authority on subject but think the issue is very low on Adobe priority. It is a nusiance, but does not cause problems so they will probably ignore it. Deleting mvm files seems to cause no problems.
Actually, it does indeed cause problems, unfortunately. It writes them to whatever drive has the most space, and for many people that is often an external USB/FW/ESATA drive. The problem is it can cause major slow-downs, or even crashes as a result.
Also. the MVM files are locked until you shut-down the "offending" program (at which time they disappear anyway). It seems to be really inconsistent when it writes these files. I thought it was only when PNG's were used, but then opened up a project with PNGs, messed with them on the timeline, etc. but no MVM's were written. I'm not sure why it is such a myster to the foks at Adobe.
I also don't see why it would be so hard to fix it, basically telling ANYTHING that would use scratch/temp space to ALWAYS use the designated locations (either OS and/or APP driven). I just don't get it.
That was fixed a year ago.
CS6 writes the Mondo scratch files to the same drives as Photoshop scratch.
Of course, After Effects and other apps may not have picked up all the updated plugins.
Hi Chris, and thanks for the info. Well then, that's very encouraging to hear. However, that begs a few questions (at least for me), I hope you won't mind answering:
- Will this only be fixed for CS6 users? I'm still on 5.5.
- What exactly are "Mondo scratch files"?
- When you say AE, etc. may not have picked up all the updated plugins, what do you mean exactly?
- Is it caused by particular plugins? If so, is there a list somewhere or can you tell me which ones?
Yes, it was fixed in CS6. No, we will not be putting out patches for older versions.
The MVM files (Mondo VM) - Mondo is the framework for many of our plugins.
I mean that AE didn't pick up the updated plugin code from Photoshop.
It is caused by most of the Photoshop plugins that have any UI.
…When you say AE, etc. may not have picked up all the updated plugins, what do you mean exactly?…
It seems to me Mr. Cox is just referring to "the other teams".
Inconsistency between or among applications in the artificial "suites" should come as no surprise.
The "suite" concept is a fabrication of Adobe marketing and bean-counting types. The engineering teams are totally independent of each other, they are not only in different buildings but in different cities and states of the American Union, even in different countries.
The fact that they have little if any communication among them is highlighted by requests occasionally made in these forums by top Adobe engineers to let the other teams know when there are problems in one application that impact our workflow in another one.
You are saying that was fixed year ago. I'm using the latest Photoshop Elements (11) and have the same issue. So it wasn't fixed even in Photoshop only familly.
Elements is yet another team, and they also are not always up to date with the Photoshop codebase.
…I'm using the latest Photoshop Elements (11) and have the same issue. So it wasn't fixed even in Photoshop only familly…
You may want to post in the Elements forum: