Song Duplicate include deviating layer configuration which sounds disharmonic

VST Live
1

Dear VST-Live-Team,

If I copy a song at VST LIVE and try to play the newly created duplicate of the song then I can hear very fast that in this new song (duplicate) further settings are ignored. For example 2 vibe sounds which are using the same VST instrument and have 1 octave difference (config at VST live) on the same zone (keyboard area) you can hear with the first sound that the different is not 1 octave because it sounds disharmonic. That meany by coping further configuration settings are getting lost or manipulated which leads to disharmonic results.

image

Below I created a the following vide recording for you to show what I did in VST live on the screen and to let you hear in parallel the results:

image

Link to Video:

https://app-share.mailbox.org/appsuite/api/share/08fe42fa08890a5889f358a8890a45489e793158dc45e692/1/8/MTUxMA

A Link to the copy of my “private” VST LIVE project file was provided to Spork on 26th of Feb. 2026 at 22:13 (CET central european time) via email.

It would be great if you please could help to analyze this topic.

Again many thanks for your great work for this great product I really love!

Kind regards

Sam

This issue was extacted from an ticket in which i documented different issues which happend in a workflow sequence which caused different issues (bugs) in the same workflow. To simplify the topic I extracted the single issues into single tickets.

2

If I’m not completely mistaken, the layers in your source song that are causing trouble later on are shared layers. Meaning both layers connect to the same instance of the instrument and share the same “internal” settings like patches etc.

In your copied song these layers don’t seem to be shared anymore. Are you sure that in your copied song both layers still route to the same instance of HALion7? And, in the copied song, do you see the same HALion patches active in both layers?

3

With paste Layer (which also happens when pasting/duplicating a Song, as with your 2nd issue), there may have been a missing update on the transpose values. With the next version, we enforce this every time a Layer is activated, so please try again then.

@Kai_Schwirzke, good point, we were also suspecting that. However, octave and transpose values are part of the Layer, not the shared instrument, so it is quite unlikely that it is related - unless the Halion instances would not store internal transpose in the settings provided to the host, which is also unlikely.