|
|
Post by gravesnumber9 on Jul 18, 2023 12:11:07 GMT -6
Don't answer the second part!
But seriously, I can't understand why I can't get my head around sub-projects. I'm doing a lot of mixes of long live recordings for my own band rehearsals. I just do a baseline pass and then template it from there. It works but I end up with like 7 projects and then the burden of basically mastering an album for something that really isn't supposed to be that involved.
I just can't get a grasp on how sub-projects work but it seems like this is what they are made for. Or maybe I'm already doing it the most efficient way?
|
|
|
|
Post by lowlou on Jul 19, 2023 7:32:44 GMT -6
It's a bit too convoluted for me too. I don't think the implementation is 100% there. I'm not using it either. I liked the idea, but never used it.
|
|
|
|
Post by svart on Jul 19, 2023 9:02:05 GMT -6
I don't use it, but I understand it because I use something similar in my daily work.
First thing to understand is that it's a hierarchical device. You can reuse the same part(s) in any project while maintaining the original. Kind of like using a "rubber stamp" instead of writing the same thing out over and over.
Say you have a drum beat called X and you plan on using it for 5 different tracks. You can create a sub-project with X inside of it and drop that sub-project in each of your 5 tracks. It's mostly the same as just importing a rendered version of X into each of your 5 tracks.
The difference is that maybe you noticed that there's a beat that's wrong in X and instead of editing the rendered version of X in each of the 5 tracks, or re-importing X into each of the 5 tracks after fixing the original X and rendering it again, you can simply edit the sub-project of X and it will automatically update ALL 5 of the tracks with the fixed version of X.
The other understanding here is that you can use it instead of "Glue" (which is also the same as "render in place" or "freeze" in other DAWs). If you take a set of tracks in Reaper and use them to create a sub-project, the rendered sub-project will take the place of the tracks same as if Glue was used. The difference is that you can still edit it in the sub-project later if needed, whereas Glue is permanent without re-importing the original tracks back into your project.
|
|
80hz
Junior Member
Posts: 66
|
Post by 80hz on Jul 20, 2023 14:57:03 GMT -6
I use it when developing tracks for live production for artists. Essentially I'm using it in a similar fashion to mastering an album but essentially, I put together tracks for each of the individual songs inside of their respective sessions. Then I create a new project in reaper that is the artist's live set. I drag and drop the individual sessions onto the timeline and not only does this allow me to time the full length of the set, but more than anything I get tracks from finished masters, demos, or some songs don't have any tracks and need them built. Being able to quickly audition songs against one another to ensure the mixes are balanced properly against each other is essential.
Can't tell you the amount of times I've been at a show for an artist who doesn't have a good tracks person and they move to a new song and the tracks are like 1/3 louder than the previous song lol.
|
|
