Zynewave.
ZynewaveI’m thinking about how to implement relative snap, and I would appreciate your input.
“Relative snap” means that dragging events along the timeline will not snap the start of the event to the grid line, but instead will offset the start position by whole grid units, maintaining the relative position to the closest grid line.
I have two possible solutions:
1: Adding a “Relative Snap” option to the bottom of the quantize menu (after the Dotted and Triplet options).
2: Using the Shift key shortcut to activate relative snap.
I prefer solution 2, as I think it will provide a faster workflow, and you are not always in doubt whether relative snap is enabled.
The shift key shortcut is already used for locking the x or y position of the events depending on the direction you drag. It should be ok to extend the shift key functionality to also activate relative snap. It means that you can’t drag events in both the x and y directions with relative snap, but I think that’s ok.
Opinions or suggestions?
LiquidProj3ctThanks you Frits, this is one of my biggest problems with Podium (and I have to use other host to do this).
I like the way Reaper implement this: it’s always turned on. You move the note and it’s snapped to the closest grid or relative snap unit, whatever is closest. Try its demo please.
pavouk100@Zynewave wrote:
2: Using the Shift key shortcut to activate relative snap.
I prefer solution 2, as I think it will provide a faster workflow, and you are not always in doubt whether relative snap is enabled.
IMHO solution 2 is better. There is yet another possibility, idea stolen from cubase; implement ‘snap-point’ setting in event. This means that you can set up snap-point in the event (similarly as you set up fade-in point in event), and the event snaps automatically to the snap point instead to its beginning. I’m not sure if this is better or not, just throwing in the idea…
Pavel
SlomoI prefer solution 2.
Another possibility, similar to the one pavouk100 describes, is Pro Tools ‘sync point’.
http://fromtoys2noise.com/2010/02/pro-tools-8-quick-lesson-6-snap-region-to-sync-point-or-marker/
R
LiquidProj3ctI think Reaper is more perfect that Protools managing relative snap. The note/clip/event just snap to the gridlines and relative snaps while you’re dragging it. It easy and quick, you don’t need do nothing, it’s perfect for a good workflow.
And if you allow me an opinion, shift key should be reserved to ignore all snaps point and move the note freely, because ‘T’ is pretty far from the left hand that usually is in Ctrl-Alt-Shift-D-F.
Relative snap and ignore snap should work with note start and note lengh. I’m pretty interested in this feature, it’s really critical for me.
ZynewaveThe snap/sync point feature is something I also plan to implement. A relative-snap feature is still needed, as it would be overkill to support snap points on note events.
The snap point feature is needed in connection with beat-slicing, to support accurate quantization/swing on sliced beats. The beat-slicing will add a fade-in up to the transients, so the beat-slice command should really set a snap point at the transient start on each slice.
Snap point should of course be available for sound events, but do you think it should also be available for sequence events? It could be useful if you for example create a curve sequence with a fade-in, and set the snap point at the end of the fade-in.
kyranI like solution 2
thcilnnahojDoing this with the Shift modifier sounds good, as it seems related to the other effect that currently has (locking h/v position).
Gotta take a look at Reaper’s way now…
This is completely unrelated to the function that dynamically links the snap setting to the zoom level, which would be “smart snap”, I believe, right?
kyran@Zynewave wrote:
Snap point should of course be available for sound events, but do you think it should also be available for sequence events? It could be useful if you for example create a curve sequence with a fade-in, and set the snap point at the end of the fade-in.
Sound and sequence event should stick to the same snap rules/settings, IMO, if only for the sake of consistency. I’m sure relative snap will also prove useful on sequence events in a beat slice/glitch session 🙂
Zynewave@kyran wrote:
@Zynewave wrote:
Snap point should of course be available for sound events, but do you think it should also be available for sequence events? It could be useful if you for example create a curve sequence with a fade-in, and set the snap point at the end of the fade-in.
Sound and sequence event should stick to the same snap rules/settings, IMO, if only for the sake of consistency. I’m sure relative snap will also prove useful on sequence events in a beat slice/glitch session 🙂
Just to clear up any possible confusion: “Relative Snap” mode will always affect all events.
My question was whether the possibility to set a Snap/Sync Point inside a sound event also should be available for sequence events. I’ve decided to do this, at least for reasons of consistency, as you mentioned.
I’ve browsed the documentation for various other hosts. Pro Tools calls it “Sync Point”, Cubase calls it “Snap Point”, Samplitude calls it “Hotspot” and Reaper calls it “Snap Offset”.
So what should Podium call it? I’m leaning towards “Snap Point”.
SlomoI clearly see why “Offset Sync Snap Spot Point” wouldn’t work 😉
I vote for “Snap Point” so it doesn’t get mixed up with syncing external hardware or whatever one might try to confuse “Sync Point” with…
R
pavouk100I vote ‘snap point’ too because I’m used to it from old Cubase days 😉
Zynewave@LiquidProj3ct wrote:
I think Reaper is more perfect that Protools managing relative snap. The note/clip/event just snap to the gridlines and relative snaps while you’re dragging it. It easy and quick, you don’t need do nothing, it’s perfect for a good workflow.
I tried the Reaper 3.51 demo, and I don’t see the behaviour you describe. To me it seems that you either get absolute or relative snap, but not both at the same time. You toggle between absolute/relative in the Snap options dialog. You can make Reaper snap to the start/end of other events, in addition to absolute/relative snap.
And if you allow me an opinion, shift key should be reserved to ignore all snaps point and move the note freely, because ‘T’ is pretty far from the left hand that usually is in Ctrl-Alt-Shift-D-F.
The Shift key is used for locking dragged events in the x/y drag direction. I find this shortcut very useful. What do you suggest as a replacement for that?
LiquidProj3ctThanks you for try it. Please watch this video, it’s a rar file, it compressed the video from 1.300Kb to 50Kb 😮
You can see how I use Reaper demo’s piano roll. When I move the note it always snap to the nearest grid or relative snap point. When I ignore snap I’m using shift key.
I never used Shift key in Podium to restrict the movement, it’s something that doesn’t help to my workflow because you can move again the mouse to fix the possible movement error.
However if I want do a groove in Podium I need to enable/disable snap constantly, because sometimes I want to move the notes snapping and others without snapping and quicky fix any start or duration with shift key. It’s lightning fast and it appeals me to work.
All of this is only a personal opinion, but I think lots of people share this point of view… take a look to VIP Zone, I’m going to post something right now.
edit: oops, here is the video: http://www.megaupload.com/?d=YECGT24X
edit2: about shift key to ignore snap, I’ll be happy with caps lock or ‘A’ or ‘Z’ to temporary enable/disable snap