"Freeze Track" cuts off sounds with slow attack

[no_barcode]

I have a track that starts with the Operator preset "Slow Saw Octave" under "Pads". When I freeze the track, it cuts off the attack -- not by much, but enough to cause a small pop at the start of the track.

[jasefos]

I have a track that starts with the Operator preset "Slow Saw Octave" under "Pads". When I freeze the track, it cuts off the attack -- not by much, but enough to cause a small pop at the start of the track.

In a project I'm working on currently I'm having big problems with the first chord going missing from Freezes of Steinberg's Virtual Guitarist. Although I'd double checked to ensure the note events triggering the first chord of a clip start on or after 1.1.1 unfortunately it goes missing once Frozen.

I've also noticed similar behaviour from Korg Legacy Collection's MS20 ... once frozen the first note of bassline for some MIDI clips I've made in session view disappear.

I'm sorry Abe's however I don't have 100% confidence in Freeze in 5.02.
Very much hoping this will be remedied soon in 5.03 ...

I'm very much loving the workflow benefits offered in L5.xx regardless now we have automated Freezing functionality.

Cheers

[no_barcode]

It's a bit of a bummer. I checked the wave file in the "Sets" folder too, just to make sure Live actually recorded the wave file with its attack missing -- and it did.

It works fine when you render the song, as long as you unfreeze the "problem track" first. Seems odd that it will render just fine, but track freeze causes problems. I would imagine track freeze is based on the same concept as rendering...? Maybe not though.

Freeze is still a great way to save CPU cycles while composing. It also seems to work fine for most of my stuff. But I think it needs some improvements.