# Render in place doesn't copy automation lanes with multi-output VSTi

**URL:** <https://forums.steinberg.net/t/render-in-place-doesnt-copy-automation-lanes-with-multi-output-vsti/713558>\
**Category:** Cubase\
**Tags:** issue\
**Created:** [April 20, 2021, 4:31pm UTC](https://forums.steinberg.net/t/render-in-place-doesnt-copy-automation-lanes-with-multi-output-vsti/713558 "2021-04-20T16:31:32Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![barri](https://avatars.discourse-cdn.com/v4/letter/b/94ad74/32.png) [@barri](https://forums.steinberg.net/u/barri)\
**Post date:** [April 20, 2021, 4:31pm UTC](https://forums.steinberg.net/t/render-in-place-doesnt-copy-automation-lanes-with-multi-output-vsti/713558/1 "2021-04-20T16:31:32Z")

</div>

Hello all.

Proccess to replicate the issue:  
1.- Create a VSTi track with a multi-output instrument (for example, Superior Drummer, but it can be any other). Activate 3 outputs  
2.- Program an arrangement (in our example, kick drum, snare, hi hat and crash)  
3.- Route kick drum to output 1 in the VSTi  
4.- Route snare to output 2 in the VSTi  
5.- Route the rest of sounds to output 3 in the VSTi  
6.- Insert a compressor in output 1  
7.- Insert an equalizer in output 2 with a low pass filter at 1Khz  
8.- Automate the threshold and ratio in output 1 (kick drum)  
9.- Automate the low pass filter equalizer frequency to 20Khz  
10.- Automate the volume of output 3  
11.- Select the event with the arrangement  
12.- Click Edit-\>Render in place - \> Render settings  
13.- Select the first option “Dry (Transfer Channel Settings)”  
14.- Click “Render” button  
15.- Cubase will generate 3 audio tracks with the audio and the original inserts BUT WITHOUT the right automation lanes.

If you try to do the same with a one-output-VSTi it works well: the automation lanes are copied to the new audio track.

My system is Cubase 10.5.30 in macOS 10.14.6.

---

<div class="post-metadata">

**Author:** ![Martin.Jirsak](https://avatars.discourse-cdn.com/v4/letter/m/85f322/32.png) [@Martin.Jirsak](https://forums.steinberg.net/u/Martin.Jirsak)\
**Post date:** [April 21, 2021, 8:27am UTC](https://forums.steinberg.net/t/render-in-place-doesnt-copy-automation-lanes-with-multi-output-vsti/713558/2 "2021-04-21T08:27:33Z")

</div>

Hi,

This is known and already reported issue. Thank you.

---

<div class="post-metadata">

**Author:** ![barri](https://avatars.discourse-cdn.com/v4/letter/b/94ad74/32.png) [@barri](https://forums.steinberg.net/u/barri)\
**Post date:** [April 21, 2021, 8:51am UTC](https://forums.steinberg.net/t/render-in-place-doesnt-copy-automation-lanes-with-multi-output-vsti/713558/3 "2021-04-21T08:51:42Z")

</div>

Many thanks for the answer Martin.

Do you know if it is a Cubase 10.5 only issue or it affects Cubase 11 too?

Apologizes for my ignorance: if it is a known issue, does it mean that it will solved in a maintenance update or will it be fixed in next versions of Cubase?

Many thanks for all the information

---

<div class="post-metadata">

**Author:** ![Martin.Jirsak](https://avatars.discourse-cdn.com/v4/letter/m/85f322/32.png) [@Martin.Jirsak](https://forums.steinberg.net/u/Martin.Jirsak)\
**Post date:** [April 21, 2021, 8:55am UTC](https://forums.steinberg.net/t/render-in-place-doesnt-copy-automation-lanes-with-multi-output-vsti/713558/4 "2021-04-21T08:55:07Z")

</div>

Hi,

It’s the same in Cubase 11.

The fact, it’s a known issue means, it has been entered as a bug in the internal Steinberg’s bug-tracking system. Then it’s up to the Product Owner to decide if and when this will be fixed. I don’t know this information and I cannot affect it, sorry.

---

<div class="post-metadata">

**Author:** ![barri](https://avatars.discourse-cdn.com/v4/letter/b/94ad74/32.png) [@barri](https://forums.steinberg.net/u/barri)\
**Post date:** [April 21, 2021, 8:59am UTC](https://forums.steinberg.net/t/render-in-place-doesnt-copy-automation-lanes-with-multi-output-vsti/713558/5 "2021-04-21T08:59:40Z")

</div>

Great information Martin. Many thanks!

---

<div class="post-metadata">

**Author:** ![jambourgie](https://avatars.discourse-cdn.com/v4/letter/j/dfb087/32.png) [@jambourgie](https://forums.steinberg.net/u/jambourgie)\
**Post date:** [February 21, 2024, 7:20pm UTC](https://forums.steinberg.net/t/render-in-place-doesnt-copy-automation-lanes-with-multi-output-vsti/713558/6 "2024-02-21T19:20:55Z")

</div>

Has this been fixed yet? Having the same problem trying to back up some old projects that use the old GrooveAgent ONE Multi-Output VSTi. I only realised it wasn’t copying the sends automation after about a week of laboriously backing up projects!

---

<div class="post-metadata">

**Author:** ![barri](https://avatars.discourse-cdn.com/v4/letter/b/94ad74/32.png) [@barri](https://forums.steinberg.net/u/barri)\
**Post date:** [February 21, 2024, 9:20pm UTC](https://forums.steinberg.net/t/render-in-place-doesnt-copy-automation-lanes-with-multi-output-vsti/713558/7 "2024-02-21T21:20:40Z")

</div>

🥶🥶🥶🥶🥶

---

<div class="post-metadata">

**Author:** ![Puli](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/puli/32/92391_2.png) [@Puli](https://forums.steinberg.net/u/Puli)\
**Post date:** [February 22, 2024, 8:15am UTC](https://forums.steinberg.net/t/render-in-place-doesnt-copy-automation-lanes-with-multi-output-vsti/713558/8 "2024-02-22T08:15:48Z")

</div>

Once your drum is ok in the project why you don’t just render the drum tracks and then write all the automation eq and stuff with the obtained audio tracks?

---

<div class="post-metadata">

**Author:** ![barri](https://avatars.discourse-cdn.com/v4/letter/b/94ad74/32.png) [@barri](https://forums.steinberg.net/u/barri)\
**Post date:** [February 22, 2024, 8:43am UTC](https://forums.steinberg.net/t/render-in-place-doesnt-copy-automation-lanes-with-multi-output-vsti/713558/9 "2024-02-22T08:43:47Z")

</div>

It is the same problem: what if I need to change those drums after the render in place is done? I loose all the automation

It is a very old bug and need to be solved.

---

<div class="post-metadata">

**Author:** ![Puli](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/puli/32/92391_2.png) [@Puli](https://forums.steinberg.net/u/Puli)\
**Post date:** [February 22, 2024, 4:03pm UTC](https://forums.steinberg.net/t/render-in-place-doesnt-copy-automation-lanes-with-multi-output-vsti/713558/10 "2024-02-22T16:03:04Z")

</div>

“what if I need to change those drums after the render in place is done?”  
You can render the new changed drum and move on their existing audio tracks, part of them or all of them, then you can bounce. It takes nothing to do it . Or just save any track preset and load to the new tracks. Keep in mind that any change on the drum track you’ll need to render audio as well, it’s just a little step more (loading track preset). Furthermore the saved presets could come useful with new projects.

---

<div class="post-metadata">

**Author:** ![barri](https://avatars.discourse-cdn.com/v4/letter/b/94ad74/32.png) [@barri](https://forums.steinberg.net/u/barri)\
**Post date:** [February 22, 2024, 4:50pm UTC](https://forums.steinberg.net/t/render-in-place-doesnt-copy-automation-lanes-with-multi-output-vsti/713558/11 "2024-02-22T16:50:44Z")

</div>

obviously you can do that and many other workarounds that I had developed during years of this bug identified and not solved

call me fussy, but I think it should work as expected
