Option to disable auto rendering of subprojects

[heda]

REAPER is smart to always have subprojects updated. It will auto open the subprojects and render them if it detects it needs updating. This could work well for small subprojects, but I'm using subprojects to arrange a master project of big full songs subprojects that take time to render. Sometimes I am working and I don't want to render all subprojects now, but leave it for later.

When does REAPER do auto render? I've detected at least two situations:
- When opening a project
- When you switch to another application and switch back to REAPER

FR: Option to disable automatic opening and rendering of subprojects.
and
Add action to update all needed subprojects in project manually when needed

Thanks!

[mccrabney]

bump.

[mschnell]

Originally Posted by heda

FR: Option to disable automatic opening and rendering of subprojects.
and
Add action to update all needed subprojects in project manually when needed

Did you read (and understand - which I did not) the text on that in the Guide page 224 ?

Of course it might be sensible to disable automatic rendering and just do rendering manually when you think it's appropriate.

Moreover to me it makes even more sense to have an (easy to use: just a "kind of subproject" setting in the subproject's features) option way to do subprojects that are never pre-render (to a file) at all, but just "play" when needed, the output streams connected to the item that represents the subproject.

So a collection of the subproject kinds that recently have been discussed here:

- automatically pre-renderd (current standard)
- pre-rendered manually (this FR)
- "live" (never pre-rendered to a file)
- "remote" (a "live" (or maybe also pre-randereable) subproject that lives on another box, attached via Network)
- VST (the subproject is useable as a VSTi in Reaper or in another Program (DAW or e.g. BiaB) )

Reaper rocks (and will rock even more in future...)

-Michael

[Dobly]

I need to have the subproject PROX file disabled too..

My band uses Reaper for playing back backing tracks. We also use it between our sets where i play a single Reaper project with hours of MP3s lined up on a single track one after another.

The problem is the Reaper has decided to create a PROX file for this project. That files is just over 6GB!!! The issue is that our backings and such are shared with all band members. And every time I add or remove a song from the backing, the darn PROX file gets altered and uploaded again.

How do I disable it??

[Dobly]

So I thought I'd delete the 6GB PROX file from my playback project. But as soon as I opened the project again it began recreating it. I don't want it.

Please how do I stop it. Reaper did not use to do this.

[mschnell]

I just am doing test with Reaper -> Reaper rewire.

This seems like the poor man's version of a subproject without pre-rendering.

Enhancing the Subproject paradigm to include the subproject "kinds" "pre-rendered", "realtime" (not pre-rendered), and "remote" (like realtime, but living on a different machine attached via LAN) would be very welcome !

-Michael

[mpl]

Big +1. Because of this currently I`m using subrojects in a stupid way like:
- move tracks to subproject
- save subproject as regular project
- render into specified path
- delete subproject from original project and add prerendered file

[Dobly]

Alright this thread as been here several days now I judging by the response it is not possible to stop Reaper generating a PROX file.

That being the case, is there a way I can set the path that this file gets created. At least then when it generates my 6gb PROX file, it could be in a folder outside of my Google Drive folder so all my buddies don't end up with it.

[ReaDim]

If master project is closed there is no rendering when save. Until you open the master project again. I always use this trick.

[Dobly]

Originally Posted by ReaDim

If master project is closed there is no rendering when save. Until you open the master project again. I always use this trick.

My project in question is just a single project. No sub projects. Nothing. I did NEW project, dropped in hours of MP3 files on single track and hit save. All was fine until a recent update to Reaper. After the update this project renders a PROX file EVERY time I open or save the project.

[mschnell]

So somehow the project feels that it is a subproject ?!?!?!?

Supposedly some unintentional click ?

-Michael

[Dobly]

Originally Posted by mschnell

So somehow the project feels that it is a subproject ?!?!?!?

Supposedly some unintentional click ?

-Michael

Perhaps. But frankly I don't know how to create a sub project.

What I'll do is a New project, and copy and paste in all the songs from the cursed project.