• SONAR
  • [Solved] Ctrl+Shift+Spacebar Doesn't "Audition Beat" with AudioSnap
2015/02/17 22:39:35
Anderton
Documentation says it's supposed to do this, but I can't get the shortcut to work. I checked Preferences and it wasn't preassigned, so I set up a keyboard binding but it still doesn't work. Anyone else?


2015/02/17 22:50:02
scook
Make sure to have a project loaded when checking bindings. Here is an image of my shortcut preferences with a project loaded showing the binding.

Don't know if the function works, I need to play around with audiosnap someday.
2015/02/18 00:43:30
brundlefly
Hey Craig, the default accelerator is working okay here.
 
- Select a track
- Set Edit Filter to Transients
- Tab to a marker, and Ctrl+Shift+Spacebar
- SONAR inserts a loop from that marker to the next one, solos the track, and starts playback
 
2015/02/18 15:23:59
Anderton
Aha! I see the problem. I thought clicking on the transient to select it was all that was needed. If I tab to the transient, or place the Now time in the vicinity of a transient, it works fine.
 
Thanks!
2015/02/20 05:11:58
pwalpwal
Anderton
Aha! I see the problem. I thought clicking on the transient to select it was all that was needed. If I tab to the transient, or place the Now time in the vicinity of a transient, it works fine.
 
Thanks!


is this analogous to the track being "selected" versus "focussed"? i would expect that clicking onto a transient marker to "select" it would have the same effect as tabbing to it, but that seems to "focus" the transient marker (or are select and focus the other way around here?) is that right? and placing the now time marker "in the vicinity" seems a bit weird - is that to take into account touch boundaries? (ie, wider than the marker graphic)
 
is there a clear description of "selected" versus "focussed" and the objects that have such a difference documented somewhere? thx
2015/02/20 06:28:14
gswitz
PwalPwal, I can't see how this might be touch related (I'm pretty convinced the selected-vs-focused thing had to do with multi-touch context requirements). It seems more about the now time and the fact that you might want to modify a transient without moving the now-time.
2015/02/20 06:31:57
pwalpwal
gswitz
PwalPwal, I can't see how this might be touch related (I'm pretty convinced the selected-vs-focused thing had to do with multi-touch context requirements). It seems more about the now time and the fact that you might want to modify a transient without moving the now-time.

i thought touch might explain why just getting "in the vicinity" of the marker work, though mouse-clicking didn't.... other screen elements have been enlarged or spread out more for this reason (fat fingers) but there's only so much bigger you could make a transient marker...
2015/02/20 06:42:00
gswitz
Mine is conjecture at best.
 
Your thoughts are reasonable.
 
Maybe a Baker will answer.
2015/02/20 09:26:35
pwalpwal
yeah, i'm also just speculating in absence of information
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account