![]() ![]() Seems I either have to 1) Overwrite my existing audio files so the new project file points to the same audio directory correctly, or else 2) Attempt a risky procedure of renaming my current Audio directory so the un-bundling procedure won't overwrite anything and then save the project file so it will be pointing to the right directory which I will subsequently then delete and re-name the original audio directory back again. Problem is that method creates two options - both of which are problematic. All I can figure thus far from experimenting is that I have to un-bundle the bundle file and then re-save the project file. How do I extract or create a project file from a bundle safely without overwriting the current audio files the project had been pointing at? Essentially I use one main Audio file directory for all legacy projects (I know not so smart) and now I need to recover a project file from a Bundle. I deleted an S5 project file by accident. And I don't dare test what will happen since unbundling may or may not ask for verification on overwrite.Īpologies for asking a legacy Sonar question but I am in a real bind. But I don't want to risk unbundling directly to that audio folder for fear it might overwrite files. What I want is to end up with a project file that will point to the original "Audio" directory where the legacy audio files reside. So if I safely unbundle to another directory, the project file is then going to be looking under that subdirectory for audio files. Apparently I have unbundle EVERYTHING(?) and then re-save the project file, which then points to where the audio was unbundled. I was hoping to be able to open the bundle and get the original project file back, but I learned it doesn't work that way. ![]() And separate directories for each project file and bundle (backups). I have an "Audio" folder for all legacy audio files. ![]() I'm not sure the situation came across clear, likely due to my poor explanation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |