|
|
|
12-22-2016, 07:52 AM
|
#1
|
Human being with feelings
Join Date: May 2016
Posts: 2,065
|
More Intelligent Finding Of Files When A Project Is Moved
When I'm done with a mastering project, I move it over to a different archive hard disk. Sometimes I need to reopen the REAPER session after the entire project folder has moved. I move the entire folder so the folder and it's subfolders all stay intact the same way, the main folder is just in a different location.
The REAPER session is a subfolder within that main folder. All the files REAPER needs are within this main folder in the same arrangement so it should be simple. It's not messy.
It seems that I always have to help REAPER find the first file before it can figure out where the rest of the files are now located.
Is there any way to add ability for REAPER to reconstruct the session even though it's been moved to a new drive without having to help it out?
__________________
REAPER, just script it bro.
Last edited by MRMJP; 12-22-2016 at 07:59 AM.
|
|
|
12-24-2016, 04:39 PM
|
#2
|
Human being with feelings
Join Date: Jul 2015
Location: Stockholm, Sweden
Posts: 1,343
|
I think Prefs/Project/Save projects with relative paths names does exactly this.
|
|
|
12-24-2016, 09:35 PM
|
#3
|
Human being with feelings
Join Date: May 2016
Posts: 2,065
|
Quote:
Originally Posted by mlprod
I think Prefs/Project/Save projects with relative paths names does exactly this.
|
Thanks. I'll try this when I get back to it next week.
__________________
REAPER, just script it bro.
|
|
|
12-25-2016, 01:14 AM
|
#4
|
Human being with feelings
Join Date: Feb 2015
Posts: 1,096
|
If you use Melodyne on any tracks, by any chance, make sure you render them to new tracks before you save the project elsewhere, otherwise you may lose the melodyne edits
|
|
|
12-28-2016, 09:38 AM
|
#5
|
Human being with feelings
Join Date: May 2016
Posts: 2,065
|
Quote:
Originally Posted by mlprod
I think Prefs/Project/Save projects with relative paths names does exactly this.
|
It turns out I already had this option turned on. However, if I move an entire folder containing a REAPER project to a new hard disk, I have to help REAPER find the first missing file before it can locate the rest.
__________________
REAPER, just script it bro.
|
|
|
11-22-2017, 07:05 PM
|
#6
|
Human being with feelings
Join Date: May 2016
Posts: 2,065
|
I figured out what's going on here. REAPER can find the files I recorded which logically end up in the Audio Files subfolder for the project.
What REAPER can't find is any associated files that are not in the Audio Files subfolder but still remain in the same relative place of the main folder that the project is in.
For example. Each project of mine has this folder structure:
Artist Name>Project Name
From there, there are other subfolders. One is a subfolder of the original source files that get loaded into my REAPER sessions for mastering. Then there is the REAPER project folder itself and some others.
My point is, not all the files for my REAPER session live in the Audio Files folder that REAPER creates for each project.
However, the files are still in the same relative place as far as the main folder of the entire project.
It would be nice if REAPER could understand this when I go to open a project after it's been moved to my archive drive.
In other words, the entire project is on a new drive but nothing about the relative folder structure has changed. All REAPER knows is that the hard drive name/location has changed and it has a problem with that.
__________________
REAPER, just script it bro.
|
|
|
11-24-2017, 04:45 PM
|
#7
|
Human being with feelings
Join Date: Jul 2015
Location: Stockholm, Sweden
Posts: 1,343
|
This has never been a problem for me. But if I understand your post right, you have files belonging to the project in a folder which are not below the project file.
The solution being that you must have the RPP in the very top level folder of the project, otherwise the relative thing wont work. Reaper cant know what is going on above its project file.
|
|
|
11-24-2017, 04:47 PM
|
#8
|
Human being with feelings
Join Date: May 2016
Posts: 2,065
|
Quote:
Originally Posted by mlprod
This has never been a problem for me. But if I understand your post right, you have files belonging to the project in a folder which are not below the project file.
The solution being that you must have the RPP in the very top level folder of the project, otherwise the relative thing wont work. Reaper cant know what is going on above its project file.
|
Maybe I'll think my file structure system but right now, the main project folder and the source files folder are at the same level. This is because they're not reaper recordings, they are files that have been sent to me.
I guess you're right that REAPER can't see files that are at the same or higher level than the main folder the RPP file is in.
__________________
REAPER, just script it bro.
|
|
|
11-24-2017, 05:27 PM
|
#9
|
Human being with feelings
Join Date: Jul 2015
Location: Stockholm, Sweden
Posts: 1,343
|
Quote:
Originally Posted by MRMJP
Maybe I'll think my file structure system but right now, the main project folder and the source files folder are at the same level. This is because they're not reaper recordings, they are files that have been sent to me.
I guess you're right that REAPER can't see files that are at the same or higher level than the main folder the RPP file is in.
|
Yep its has to be in the same actual folder or below.
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 08:30 AM.
|