Audio peaks rebuild with drag/drop concurrent projects

[John Rofrano]

[Jim Greene] “I have found an anomaly, in that if I save/close project 2 then reopen it and drag the file, the peak file isn’t rebuilt. Not a great solution.”

It sounds like maybe Vegas is taking a snapshot of the files in that folder and it isn’t seeing that you built the peaks already. Try pressing the refresh button in the Vegas explorer of the second project before dropping the file into it and see if that helps. (just a guess)

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Jim Greene]

Thanks, I never use the the explorer in Vegas, I always use Windows Explorer to drag files. But I just tried it and it didn’t make any difference.

However, I have found the reason it happens. I normally use the preference to *not* “close media files when not the active application”, that is, this option is unchecked in preferences. So it seems that any other Vegas instance can not see the .sfk file if the associated media file has an open Windows handle. That’s too bad, as the preference to keep file handles allows me to switch back and forth between projects without much reloading delay. I always edit with two projects open, especially to help synchronize portions using PluralEyes, or to use as an event trimmer since the one in Vegas is always Full Resolution and basically useless for h.264 files.

-Jim.

[John Rofrano]

Great detective work! 🙂 If you usually keep two projects open at once, you really should allow Vegas to close media files so that you can edit them with other applications and Vegas will refresh with the changes.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Jim Greene]

Yes, I like the feature of editing outside of Vegas and having it pick up those changes, I do that often. But I simply set the preference temporarily then set it back to keep files open so I can switch between projects faster.

As for the Windows handles, I was trying to logically determine the cause as it made no sense. Then my 20 years of computer software development kicked in and I thought of the answer. It’s still strange behavior, and really a small bug, because if I shut down both projects then open them again, project 2 doesn’t need to rebuild the peaks — it’s just an anomaly when the project that first built it doesn’t allow the 2nd to see the peak file until the first project closes the file handle of the event. And the peak file isn’t locked during this period because project 2 will overwrite it. Just the event file is locked. Weird.

-Jim.