How do I prevent Premiere from placing all scratch disk information onto the G drive before I open an older file?
I'm not sure that you can. Scratch disk settings were global in CS3. You set it once and it applied to all projects. They are now project based in CS5, and can be set differently for each project (a much welcomed improvement for anyone working on multiple projects). So older projects will default to the Same as Project the first time they're opened, until you change it manually.
The good news is they should stay changed for that project. You'll only have to change them the first time you open the project. If that's not the case for you, something is wrong. (Though I'm not sure what.)
· The odd thing was the scratch disk in CS3 for all the projects’ scratch disks was not on the G drive, but the setting was where I also now want them to go - the D drive. The settings were always on the D drive in CS3, yet they now mysteriously default to the G drive in CS5 when nested.
The "Same as Project" is simply the default. Keep in mind that CS5 isn't reading the old CS3 setting. In CS3 is was a global setting. In CS5 it is a project setting. Things changed between versions. So it won't matter what it was set for in CS3, CS5 will use the default until manually changed.
Thanks. Now I know that anytime I import a CS3 project file into a CS5 project, that it will change the whole project scratch disk settings to the default without warning.
One wouldn’t think that just one imported file would change the whole overall project file (out of many imported files…not project files that do not); it is odd that Premiere changes the setting of the new overall Cs5 project without warning.
This doesn't smell right.
I don't think we should be changing the scratch disk location in an existing project when you import something into it.
What happens if you import the sequences individually?
edit, 10 minutes later:
I see that the scratch disks are indeed changing when a new project or sequence is imported, even when both projects are CS5 projects. That might be the designed behavior, and until I can verify that (tomorrow), you should file a bug.
edit, 20 minutes later:
No need to log this, we already have it.