Don't know if this is a bug report or a feature request... Seems screen sets are not local to the project, but global. The last loaded project determines the screen sets for all projects. Thus, loading in a new tab a project with no defined screen sets removes the screen sets defined for any loaded project. Screen sets should really be project local. Do the following (Reaper 3.04): 1. Start Reaper, with create new project 2. Save a new Screen set for the new project 3. Create a new project in a project tab 4. Now the screen set defined for the first project is gone Something similar to this was reported by Marah Mag already for 3.00 ().

Screen sets should be local to the project 

No-one else having problems with this? It bugs the hell out of me... I had one project with carefully set up screen sets. I loaded an old project with no screen sets just to grab an FX Chain, closed the old project, inserted the chain and saved the new one. No carefully defined screen sets there anymore... And I found no way to undo them back... Window sets I can accept to have global, it seems natural. But screen sets, they are g*******t project local. I actually think that now that we can have several projects loaded in the same Reaper instance, screen sets and window sets should be divorced. Screen sets should be local to the project, and defined in the project, whereas window sets should be global to Reaper and defined in a global context. Screen sets should be local to the project, did I say that...?