And to follow up on my previous post, if this duplicate feature is designed to allow an EXACT copy, including RealTrack content, there would need to be a way to flag the new track so BIAB doesn't replace the RealTrack bits everywhere on the next generate using it's built-in "duplicate RT avoidance system"! Maybe in that scenario a duplicated track and it's source track would both be automatically frozen after the duplication?