Transform tool force merges all clips in a track!

Author
cboshuizen
Max Output Level: -88 dBFS
  • Total Posts : 122
  • Joined: 2015/03/15 16:28:31
  • Status: offline
2017/08/06 09:54:11 (permalink)
0

Transform tool force merges all clips in a track!

If I have a midi track with multiple clips, and I use the transform tool on that track, all the clips are suddenly merged as if the entire track had been bounced. This is super frustrating if you like to keep clips spit and named for different sections. Editing one section will merge all clips and delete all clip names!
 
It's super easy to reproduce. Split a midi clip a few times. Use the transform tool (inside one clip or overlapping many, it doesn't matter) and it will merge all of the clips, even ones that aren't near by. 
 
Correct behaviour: Clip boundaries should be respected when using the transform tool. 

// Silent PC, i7-6700K, 16GB RAM, 512GB SSD, Windows 10 Home Creator Update  // Sonar Platinum - latest monthly release // Melodyne Editor 4.1, Addictive Drums & Keys, Z3TA+2, Dim Pro // FL Studio Producer 12.4 all plugins + some FL VSTIs in Sonar //
#1

3 Replies Related Threads

    SquireBum
    Max Output Level: -84 dBFS
    • Total Posts : 347
    • Joined: 2013/06/26 13:23:55
    • Status: offline
    Re: Transform tool force merges all clips in a track! 2017/08/06 17:02:29 (permalink)
    0
    I am seeing the same behavior on my system running SONAR Platinum 23.7.0 BUILD 37 [2017.07] x64.  A GIF animation is attached:
     

     
    -- Ron

    Cakewalk by Bandlab, Sonar Platinum x64 2017.10, X3E, X2a, X1d, 8.5
    Windows 10 x64
    AMD Phenom II X4 955 3.20 GHz
    8 GB Ram
    Nvidia GeForce 9500 GT
    Echo Gina 3G
    #2
    Bob Currie [Cakewalk]
    Administrator
    • Total Posts : 58
    • Joined: 2016/09/07 10:10:01
    • Status: offline
    Re: Transform tool force merges all clips in a track! 2017/08/07 15:43:58 (permalink)
    +1 (1)
    Hey guys,
    Yeah, I think that the merging is unnecessary for transforming velocity data.  Good point.  However, there is a big reason for merging the clips when ramping CC data, and that is that the ramp usually creates numerous NEW controller events across the clips.  Without merging first, the data often intermixes with disastrous results.
     
    I'll see what I can do about avoiding the merge for velocity data.  Thanks for the heads-up.
    ~Bob
    #3
    cboshuizen
    Max Output Level: -88 dBFS
    • Total Posts : 122
    • Joined: 2015/03/15 16:28:31
    • Status: offline
    Re: Transform tool force merges all clips in a track! 2017/08/08 19:17:02 (permalink)
    0
    Interesting, fair enough. What about adding the new CC date in a new clip in a new take lane, and leaving the bouncing up to the user?

    // Silent PC, i7-6700K, 16GB RAM, 512GB SSD, Windows 10 Home Creator Update  // Sonar Platinum - latest monthly release // Melodyne Editor 4.1, Addictive Drums & Keys, Z3TA+2, Dim Pro // FL Studio Producer 12.4 all plugins + some FL VSTIs in Sonar //
    #4
    Jump to:
    © 2024 APG vNext Commercial Version 5.1