New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cut/Copy selected tracks sends: Runs if no sends on tracks #1681
Comments
Makes sense for these actions in isolation, however changing the behavior may have undesirable side effects:
|
This post was specifically about the actions to cut/copy sends specifically. I don't think the two actions you name ought to be changed... |
… copy in "Copy selected tracks {sends,receives} Closes reaper-oss#1681
… copy in "{Copy,Cut} selected tracks {sends,receives}" Closes reaper-oss#1681
… copy in "{Copy,Cut} selected tracks {sends,receives,routing}" Closes reaper-oss#1681
… copy in "{Copy,Cut} selected tracks {sends,receives,routing}" Closes reaper-oss#1681
👍 I've added special cases to "{Copy,Cut} selected tracks {sends,receives,routings}" for consistency while preserving the existing clipboard-clearing behavior if there's either sends or receives to copy or if it's "Copy selected tracks (with routing)". (All these actions run the same code.) There are builds here if you'd like to try: #1690 (comment). |
… copy in "{Copy,Cut} selected tracks {sends,receives,routing}" Closes reaper-oss#1681
Sounds good! I just tried out the new beta you linked and while |
… copy in "{Copy,Cut} selected tracks {sends,receives,routing}" Closes reaper-oss#1681
… copy in "{Copy,Cut} selected tracks {sends,receives,routing}" Closes reaper-oss#1681
Can't duplicate here (tried creating two identical sends from track 1 to track 2, selected track 1, ran "Copy sends", selected track 3, ran "Paste sends" and it got both). Which steps are you using? (Updated the build, fixed bugs occurring when not all selected tracks have sends.) |
I just tried again and realized that it was user error. Apologies for that, works great! ack |
Thanks! |
I consider this a bug.
If there are no sends on a track, then these actions will erase any previously cut/copied sends in the clipboard, effectively "cutting/copying no sends". This is pretty nonstandard behavior – as a user I would expect that the action would do nothing if no sends are found on the tracks.
The text was updated successfully, but these errors were encountered: