Wrong project file saved when saving with media copy (FIXED)

[vmnsk]

Hello,

I believe I've run into a bug in saving projects with media copy enabled. I've been preparing final project (project 1) cleared of unused tracks etc. for archiving and noticed that if I open another project (project 2) while waiting for the media from project 1 to copy, then project 2 file is saved in the target folder along with project 1's media. This also happens after just switching project tabs.

What I expected was that the project file I chose to save would be saved along with the correct media and I would be able to start working on another project in the meantime.

Reproduction steps:

-Save project as...
-Copy all media into project directory
-Hit Save
-Open another project (or switch project tab) while media files are being copied
-Once media copy is finished, the currently selected tab is the project that is saved along with it.


Reproduction is possible with any project which has media large enough to give you time to load another project. This behavior is present on both Windows and Mac versions of REAPER v6.04.

[akademie]

If true, it would be a serious bug then!

I cannot test it right now here, because I am at work :-D , but definitely will do later today.

EDIT:
What version of Reaper? , 32/64 bit architecture? and OS? are you using, please?

[vmnsk]

Windows 7 and macOS Mojave, version 6.04 as mentioned in the OP, both on 64 bit.

[akademie]

Originally Posted by vmnsk

Windows 7 and macOS Mojave, version 6.04 as mentioned in the OP, both on 64 bit.

Yup, sorry, I did read too fast, I think

Nevertheless, I will try later today on Win7 32 bit with few versions of Reaper 32bit. Will report then.

[akademie]

I cannot switch to another project tab while the saving of current tab is in progress.
It is Reaper v6.04 (32bit) (also v6.0) in Windows 7 Pro (32bit).

While clicking again and again on the next tab, it switches only after copying is done, then when checking new folder, there is a correct filename and its contents is also correct.

Can you try it with Reaper 32bit version? (I cannot try 64bit Reaper in Window 32bit of course).

[vmnsk]

I finally got around to recording the bug in practice. The following video is from REAPER v6.05 on Windows 7 x64.

https://www.youtube.com/watch?v=onAc_bx6UoU

[akademie]

Originally Posted by vmnsk

I finally got around to recording the bug in practice. The following video is from REAPER v6.05 on Windows 7 x64.

https://www.youtube.com/watch?v=onAc_bx6UoU

Oh I see now, you are opening the second project from Explorer while the first tab is saving. Will have to try later and will report back.

P.S.: And greetings from near Prague

[akademie]

Ohh my God, it is for real !!! Confirming this bug
And it's realy nasty bug.

Fortunately it is easily reproducible as vmnsk wrote in first post (+ opening new project while saving has to be done by drag'n'drop in portable install, or by double click RPP file in standard install).

Justin, schwa, please, take a look at this important bug as it defacto corrupts the project.

Thanks vmnsk for reporting.

[akademie]

Bump.

It is a serious bug.
Please...

[Justin]

I will look at this, but the fix will likely be to prevent opening projects from explorer while doing a file copy operation! So stop doing that!

[ivansc]

I know this is definitely a serious BIG DEAL type bug, but I did have a little smile at your response, Justin!

[akademie]

Originally Posted by Justin

I will look at this, but the fix will likely be to prevent opening projects from explorer while doing a file copy operation! So stop doing that!

Great Justin. I think that preventing other operation while saving in such cases is more welcome than ruining a project without even knowing that it happened, only to find out later, when it's too late.

So for me, I vote for your proposed restriction to prevent opening projects altogether until saving is done.

Well, and stopping doing it ourself is/seems easy for sure , but it may happen unintentionally by doubleclicking the project icon and then Reaper will allow it in current state - it should get the user warning sign and prevent it, you know
Anyway thanks for the response.


P.S.: To be true I have never done that, because as was my first reply here "I cannot switch to another project tab while the saving of current tab is in progress." but then OP responded with his videocapture of the process and my second reply and confirmation was "..wow... opening new project while saving has to be done by drag'n'drop or by double click RPP file..."

So prevention is already built in, just does not cover all use cases.