Activity › Forums › Adobe Premiere Pro › Workspace Layout CS3 (am I the only one?)
-
Workspace Layout CS3 (am I the only one?)
Posted by Greg.ekborg on July 20, 2007 at 3:00 pmAfter getting completely ramped up for the new CS3 Master Collection upgrade, I have had nothing but bugs!!! and Lots of them…from missing .dll files when opening Ps to custom keyboard customization crashing my PC when trying to customize. I finally found that having too many fonts locally crashes keyboard customization dialog box. OK?
So now I can’t save my workspaces in PPro CS3. Every time I open a project, I have to reconfigure all of my panels. WTF?!?!?!?
Does anyone else have this issue and what is the fix if there is one?
Thx
—
greg
creativeProducer
netXstudiosGreg.ekborg replied 18 years, 10 months ago 3 Members · 9 Replies -
9 Replies
-
Steven L. gotz
July 20, 2007 at 3:59 pmWhy can’t you save workspaces? Does the file exist after you save it? Can you select it off your list? I have not seen a problem.
Steven
-
Greg.ekborg
July 20, 2007 at 4:25 pmHeres is what happens in a nutshell; Open a project; Setup panels, save workspace……now while working in this project…the name of my workspace is on the list from the drop down menu of workspaces…but if I was to click on a default workspace, say “Audio” and then click on my saved one, it doesn’t revert back to the layout I set up….also, when I close down the project…ie…shut down ppro all together…and then open that same project up again…then it doesn’t open with last panel layout…like AE or PS does. Also there is no list of my saved spaces…all the default workspace layouts are only on the menu. So i have to spend more time setting up my panels and layout again.
—
greg
creativeProducer
netXstudios -
Greg.ekborg
July 20, 2007 at 4:27 pmAlso, if you mean a file in xml under layouts within my documents or where ever ppro saves them…i haven’t seen that. If you know of the location of where the layout files exists on the c drive i would love to troubleshoot that to see if that exists.
—
greg
creativeProducer
netXstudios -
Steven L. gotz
July 20, 2007 at 7:04 pmI am not happy with the way the workspaces are stored, but with a decent Find and Replace program, I was able to search all of the XML files and found my workspaces under the following directory:
C:\Documents and Settings\Steven\My Documents\Adobe\Premiere Pro\3.0\Layouts
Notice that they are numbered, not named. The name is inside the file under
UserName .Steven
-
Greg.ekborg
July 20, 2007 at 7:50 pmHmm…
In C:\Documents and Settings\greg.ekborgI have Encore.pref files adobeFnt10.lst file and UserCustomPreset_After Effects.vpr files but no \adobe folder and no adobe ppro cs3 files.
What I did find however is this on our network drive….
P:\Adobe\Premiere Pro\3.0\
In there is a layouts folder with two xml files userworkspace1.xml and workspaceconfig.xml
also there is a Archived Layouts folder…and a Styles folder with a workinset.prsl file.
Completely strange huh!
—
greg
creativeProducer
netXstudios -
Greg.ekborg
July 20, 2007 at 7:52 pmGet this Steven,
I moved the adobe directory to where yours is and the moment I tried to save a workspace, I got a fatal error crash!
—
greg
creativeProducer
netXstudios -
George Socka
July 20, 2007 at 9:22 pmAre you possibly on a domain with user documents and setting redirection group policy pointing to P? That might be a clue, if PPro is looking for your domuments folder and finds it on a network drive.
-
Steven L. gotz
July 20, 2007 at 10:02 pmI don’t know how you got it loaded with preferences set to the network drive in the first place. Try deleting your preferences and then see what happens.
Steven
-
Greg.ekborg
July 23, 2007 at 2:29 pmOk, I tried all the normal things and nothing worked ofcourse. I found out that on the network inside this corporate building…there are group policies that have each user on the domain going to a networked “mydocuments” folder. Not locally on the C Drive. So combination of Adobe putting the layout files in mydocuments (strange) and then a network group policy having mydocuments on a shared drive was the issue. We had to get our I.T. dept. to remove all Premiere stations of the group policy.
—
greg
creativeProducer
netXstudios
Reply to this Discussion! Login or Sign Up