Native non-destructive glue

Native API for "real" Non-destructive glue 

Bug or Feature Request?

Awesome idea !

Isn't this sub projects ?

This is how it should be done: Simply amazing workflow possibilities here, especially if you can create pooled copies just like MIDI. Do please stop spamming though.

Matthew can do this! Let's support him adding some required functions to API!

+1 This is a must! Please devs consider adding this!

Im still waiting to see if the devs add an API function that allows me to do something similar to the existing "Propagate take properties to similarly named items on all tracks" action, most importantly a version of this that can be called via Lua scripts AND one that allows me to specify that I only want the wav src property of the selected items take to be copied to all other similarly named takes. Either if this is added to Reapers API, or if someone like the SWS devs could add a native C++ function that I can somehow use via Lua, that would work too. My existing method of updating take sources manually in a big loop in Lua is just not performant enough. Until then I really havent got much motivation to debug this and make sure it works with current Reaper version. Sorry :/

Ok you have an "API for non-destructive glue". You glued take "non-destructively", reversed it (or part of it), added stretch markers, added takeFX, added envelopes. Now unglue it. What do you get? Right, total shit. There isn`t ever proper description or implementation suggestions here. Won`t happen.

Wow someone got out of the wrong side of the bed. Actually no, you are completely wrong. My implementation, which is just some Lua scripts, easily accounts for your big "gotcha" issue. When you unglue an item, my script simply remembers the state of the item you just unglued, stores that temporarily, and inserts the source items into the project in their ORIGINAL state. NOT reversed/stretched etc. and then when you reglue the child components, it renders the new glued wav, then reinserts the item you unglued and just updates the wav src of it and all other items in the same group. Since only wav src is updated, all items in the group maintain their position, stretch, reversing, take fx, and any other per-item/per-take stuff you want to do to it. Its just the source wav that gets updated. So, if i can think of a simple solution for this supposedly huge problem you think youve come up with, if the Reaper devs did decide to do something themselves i doubt they would have even the slightest issue.