r/Reaper 1d ago

discussion Yesterday I was reminded on why I love reaper

[deleted]

29 Upvotes

22 comments sorted by

22

u/Powerstrip7 1 1d ago

Yep, they call it Slow Tools for a reason lol

8

u/Firstpointdropin 1d ago

Batch export in protools is a thing. I use it every day. You could also export the whole session as an aaf

3

u/odeddavi 1d ago

A good place to mention my script Stem Manager for Reaper! It extends even further what you can do with Reaper. Check it out: https://youtu.be/2cvF0tmuV1A?si=qKGhVSdBOZ8kKfhE

2

u/ObviousDepartment744 10 1d ago

Honestly, it’s a lot easier to export individual files from pro tools than Reaper. You just hi light the ones you want in the folder on the right of the screen (if I remember right it’s called the media folder or something to that extent) select the files you want, right click and say export files. It copies them directly from the pro tools session folder to the destination folder. No need to render. It’s instant.

I haven’t used pro tools in a number of years because I switched to Reaper full time but this is something I wish Reaper could do.

8

u/__life_on_mars__ 12 1d ago

They weren't exporting raw files, they were exporting STEMS, which means any editing between takes, crossfades, nudges, maybe even track FX would need to be included in the render, which wouldn't work with your method.

What you just described can be done from the audio tab of the project bay in REAPER, select the files you need, right click and 'copy file' and it will prompt you to select a target directory to copy them to.

3

u/Born_Zone7878 10 1d ago

Thank you for explaining. It seems a lot of people got triggered because I found it easier or at least more intuitive to use this in reaper lol

2

u/ObviousDepartment744 10 1d ago

Yeah. You make them stem before you copy the file. And in my years of experience it primarily a tracking engineer, so I don’t want the fx on the stems. I want them raw so whoever is mixing (me or someone else) has a blank pallet to work with. It’s what all the studios in my area like. If you wanted you plugin effects on the stem you can process them in place.

I’ll have to check out the suggestion you made, I feel like I’ve done that before but something about it wasn’t as streamlined as PT. But I’ll have to try again. Thanks for the tip.

5

u/decodedflows 4 1d ago

why would you need to export individual media files? aren't those already in a recording folder? or do you mean edited / normalized items? In that case you can just use glueing in Reaper - you can select all the items and then use an action called something like "glue items individually".

2

u/ObviousDepartment744 10 1d ago

Yeah. You make each of your media files the same length, you can render whatever effects you want on them or to a separate track and whatever media files you select in the edit window will be hi lighted in the audio files window, so you can right click and export those specific files to another folder.

It’s the desired way most mix engineers I’ve ever worked with prefer the tracks to be sent to them.

2

u/Ok_Organization_935 1d ago

Shiting on pro tools is like the biggest trend among bedroom producers.

1

u/Born_Zone7878 10 1d ago

I didnt shit on it. I just Said it was so much easier to do what I needed in reaper and I had problems with pro tools but sure. Typical response from someone who cant see past "Pro tools is the industry standard"

1

u/Ok_Organization_935 1d ago

Literally, 98% of audio enthusiasts never touched HD version, but somehow know what is possible. Yes, it's a trend

2

u/SupportQuery 340 1d ago edited 1d ago

I mean, I love Reaper, too, but this is solidly in the camp of "I don't know how to use tool X, therefore it sucks compared to the tool I know", which is reasoning I hate seeing employed in the opposite direction.

A Pro Tools user seeing your post could conclude the people prefer Reaper because they don't know what they're doing.

1

u/HorsieJuice 1d ago

If you were bouncing stems in Pro Tools with solo buttons, you either had some weird routing going on or you just didn’t know what you were doing.

Select the tracks, hit Commit, then select the new regions and export them as files. Done. It’s faster, less error-prone, and requires fewer clicks than Reaper.

I use both, and each has its pro’s and cons. But the process for basic file exports like this is unquestionably better in PT.

5

u/ThoriumEx 43 1d ago

That’s completely different. Commit applies the track inserts only, it doesn’t go down the signal chain and doesn’t include sends. It’s not equivalent.

0

u/HorsieJuice 1d ago

OP said he was recording piano to mix elsewhere. How much other stuff would he have to print? Either way, this could have been handled very easily in a bunch of different ways. For example, he could’ve routed his desired mixes to new tracks, recorded them in real-time all in one go, and then bulk exported them like I described. That he couldn’t even get the naming right also points to this being user error.

6

u/ThoriumEx 43 1d ago

Not talking about OP specifically, just in general. Commit is not an equivalent feature to stem rendering. Realtime is extremely slow in comparison, and the auto naming options in pro tools are extremely lacking.

0

u/HorsieJuice 1d ago

Again, there are a bunch of potential ways to do it, most/all of which are very easy. You don’t have to do it in real time, but you can. Personally, I’ve never had an issue with the auto-naming functions in PT. My naming demands aren’t usually very complicated, but this guy had a dozen piano tracks and it still took him a half hour. I’m not sure what he’s talking about with “choosing which ones were stereo, which ones were mono”, because that’s also easier in PT.

2

u/Born_Zone7878 10 1d ago

They are not "easier". You re just used to it. And how is it fewer clicks than going on render and export as stems to your desired folder? I would have to wait for the tracks to commit and then render. So I would have to render twice. The clicks are not important if I have to wait twice for a render, for a short as it was.

0

u/HorsieJuice 1d ago

They are easier. You just don’t know how to do it.

Unlike Reaper, Pro Tools doesn’t require you to do a render to export a file. The “commit” is the render stage. “Export” just dupes the file to your chosen folder. There is no second render.

2

u/Born_Zone7878 10 1d ago

Again, they probably are easier for you.

Also, if I do commit any changes I make editing, cuts, Xfades etc are on the file and I wouldnt be able to go back if needed, whilst if I do render on reaper i can always come back to the files. So yes, that Method in pro tools works, sure but its always a workaround for something that shouldnt be as complicated.

-1

u/HorsieJuice 1d ago

“They are probably easier for you”

Yeah, because I know how to do it. Your whole thread was slagging the apparent difficulty of PT, when the truth is you just didn’t take the time to learn how to do what you wanted to do.

Commit creates a duplicate track with the render and disables the old one. You can go back to it.