|
|
|
01-11-2018, 05:37 AM
|
#1
|
Human being with feelings
Join Date: Jun 2016
Posts: 47
|
Incorrect behavior a rendering with tail on (FIXED)
Hi, if i render a project like at an attached picture, then will render everything that beyond a time selection, although notes in second midi item must be muted(not includes in render process).
Thanks!
|
|
|
05-17-2018, 11:57 AM
|
#2
|
Human being with feelings
Join Date: Jun 2010
Location: Berlin
Posts: 563
|
I can confirm this.
It also happens when using the region render matrix. This would be really useful right now ...
|
|
|
06-25-2018, 04:55 AM
|
#3
|
Human being with feelings
Join Date: Jun 2016
Posts: 47
|
Please fix it! A Very annoying thing.
|
|
|
06-26-2018, 04:07 AM
|
#4
|
Human being with feelings
Join Date: Nov 2009
Location: mostly inside my own head
Posts: 346
|
The current behaviour is I would expect, to be honest. I can see where you're coming from though - you want a rendering mode that's equivalent to stopping playback, right?
I think that could be useful, but perhaps it should be a feature request (e.g. a second "stop playback during tail"), particularly because it has lots of edge-cases.
E.g. should the "beat position" sent to the effects keep progressing or not? Should the play-state be still playing? What if the first MIDI item puts the sustain pedal down, and the second one is meant to release it?
|
|
|
06-26-2018, 08:05 AM
|
#5
|
Human being with feelings
Join Date: Jun 2016
Posts: 47
|
yes, but Why need this option if i can just move an edge of time selection?
I think that a tail-option is need for a correct processing reverb, delay and instruments tail, respectively outside of time selection reaper must stop to receive anything midi and audio events and wait for decay FX.
|
|
|
06-26-2018, 10:32 AM
|
#6
|
Human being with feelings
Join Date: Nov 2009
Location: mostly inside my own head
Posts: 346
|
That's reasonable, and I think the behaviour you propose is more useful.
I just think the way it works now is understandable, and if changing it would mess things up for even 1% of users, then you're going to need an option, regardless of which one is more "correct".
|
|
|
06-26-2018, 12:27 PM
|
#7
|
Human being with feelings
Join Date: Jun 2010
Location: Berlin
Posts: 563
|
Render tail pretty much means "render to end and then add tail". The current implementation/bug makes this option redundant as the same can be achieved by setting the regions to the length you need in the first place.
I don't think anybody would expect this behaviour to work differently than the tail option when freezing a track. So project backwards compatibility is really not an issue here. Fixing this would increase consistency.
Apart from that, I made that feature request on the pre-release discussions (during all that game audio/wwise hype). This is a bug or it has been thrown into reaper without proper testing.
|
|
|
03-12-2019, 08:15 AM
|
#8
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 15,751
|
This behavior is changed in the current development builds.
|
|
|
03-27-2019, 12:35 PM
|
#9
|
Human being with feelings
Join Date: Jun 2010
Location: Berlin
Posts: 563
|
Hi Schwa, I tested the bugfix and can confirm that the behaviour is now correct.
During testing I discovered the rendering of midi clips is not consistent with the playback concerning chasing midi events. Can you look into that and chase midi events also during rendering?
|
|
|
07-04-2023, 09:29 AM
|
#10
|
Human being with feelings
Join Date: Nov 2011
Posts: 143
|
Bumped an ancient thread - because it seems that this incorrect behavior has returned in the recent versions (around 6.80). I'm catching stuff in the track after the region, if I add a long enough tail to the region matrix render. That should not happen, right?
|
|
|
07-04-2023, 09:49 AM
|
#11
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 15,751
|
I'm not seeing a problem with this. The second track is the output of rendering the region with a 1000ms tail:
|
|
|
07-05-2023, 12:25 AM
|
#12
|
Human being with feelings
Join Date: Nov 2011
Posts: 143
|
I have a reverb send from another track coming to the track I'm rendering (rendering the reverb separately), and signal from after the render region gets in the tail. Another difference is that there is no audio clip - the signal from the sending track is generated by a plugin with automation clips. So... maybe that's what's causing it?
|
|
|
07-05-2023, 05:33 AM
|
#13
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 15,751
|
The difference between the specified render region (or time selection) and the tail is that media items are rendered within the region and not within the tail. FX are rendered during both the render region and the tail, by design, since that's what the tail is meant for. If you have an FX that is generating sound that does not depend on underlying audio or MIDI media, there's no way for REAPER to know that particular plugin should not be rendered during the tail. You'll need to add bypass automation or some other method to the project itself to restrict when the plugin is rendered.
|
|
|
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:06 AM.
|