Surely this shows that there is a problem with tabbing to transient. I expected also the tab in the second take to move to a position similar to what happens in the top take. To explain... in the vid I first press TAB with the top take selected, and Reaper nicely tabs to the next transient. This is clearly visible. Doing the same thing on the second take does not tab so nicely, in fact I think it is just plain faulty; from the edit cursor the next transient clearly occurs much earlier than what Reaper tells us. This is Reaper x86, v.3.66, on W7x64. Tab to transient sensitivity at 90% (the default). Anyone confirm? EDIT: Oops... just now I see this thread is in the OSX forum. Why? None of the questions/replies above are OSX specific, right? So, the thread should really be moved to the general discussion, not? Mods...?
--------------------------- Yale Dakar Club Member #7
don't begin with a transient, like a slurred violin phrase or a vocal performance of a word beginning with an S or W. In fact, thinking of it in terms of "tab to transient" is inherently limiting in the first place - it's next to useless within a highly compressed, distorted legato guitar phrase. Much more of the functionality that's built into the dynamic split function - gate, for example - could be integrated into the "tab to transient" function. In fact, all the code is already in place there to include a lot more functionality - "tab to next pitch in legato phrase", for example. This would give much more *musical* flexibility in what we can choose to tab to.
You can try this set of actions as one macro. It's my custom macro that does what PT's does. Set start point Set end point select all items in track move edit cursor to play cursor move cursor to next transient in items sws : select items under edit cursor on selected track Try it. It works beautifully :) "Set start/end point" are optional depending on your workflow. I prefer time selection cleared whenever I hit TAB.
Поиск
Users
Entrance
RE: Tab to Transient
