Hi al
I use Project (.wpr) extensively. It’s super convenient and a very powerful organizational tool.
The way I organize things is to make every new session/job a ‘Project’. So, the .wpr file is a common template re-named for the Project (Artist Name_EP_ etc) and always in a ‘WaveLab’ subfolder in the session folder (not the default AppData folder).
This is super useful and works exactly like it should. You can easily come back to the Project when, for example, the next day, or a new single comes in, or there’s a retrieval from backup and so on. Everything is exactly how you left it including all tabs, batch processors and montages. If you are into session organization it is a fantastic feature … thank you PG.
The reason for this post is that, since the latest WL update, more than a few times this happens:
Start WL. Open a Project from the dialogue.
Work on this.
Open another already created Project (different .wpr) from the File>Open>Project menu.
The selected Project should just open and it does almost all of the time.
Randomly, and only very rarely, selecting the next Project results in the Project currently open somehow ‘overwriting’ the newly selected .wpr header data (not the .wpr name though).
The effect of this is that the already open Project now displays (incorrectly) as the newly selected Project you wanted to open.
The .wpr in the selected Project is still named correctly but it now opens as the previous Project that was initially open (prior to selecting the next Project).
The ‘original’ open Project is unaffected.
What seems to be happening is that the .wpr on the open Project ‘overwrites’ the header data in the .wpr file of the selected project without altering its name. It behaves like a ‘save as’ without a dialogue.
The workaround is to copy and save as the .wpr from the last backup. That is ‘re-overwrite’ the troublesome .wpr.
Closing and relaunching WL has no effect. Restart has no effect. This is not surprising if the .wpr header data has been overwritten.
I have no idea what causes this. I cannot reproduce it. I can’t remember this happening before the current WL update . Any thoughts?
Although it can be annoying , it is far from a show stopper provided you do backups…
I am on the latest WL version and current Windows 10 Professional build.
WL is otherwise super reliable and arguably the most ‘solid’ version to date.
Thanks