Zynewave's Forum Page

@thcilnnahoj wrote:

@Zynewave wrote:

After thinking about it for a while: How about assigning Shift+Alt as the x/y drag lock (currently Shift), and then assigning Shift to override snap? These shortcuts will only work if you press them after you have clicked the events to start the drag.

Sounds fine to me. Would it only work when moving events, or maybe also circumvent the selection rectangle snapping to the grid when you the modifier it while drawing it?

I think it should override all snapped actions.

@LiquidProj3ct wrote:

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.

Thanks for the video. I only tested the snap in the track view, so that’s why I didn’t see both absolute and relative working at the same time. Can’t it sometimes be confusing to have both snap modes enabled? For example, if you have an event that is very close to the grid line, it would be very hard to see whether you have dragged it so that it snaps absolute to the grid, or relative.

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.

edit2: about shift key to ignore snap, I’ll be happy with caps lock or ‘A’ or ‘Z’ to temporary enable/disable snap

After thinking about it for a while: How about assigning Shift+Alt as the x/y drag lock (currently Shift), and then assigning Shift to override snap? These shortcuts will only work if you press them after you have clicked the events to start the drag.

I’d like the key shortcut behaviour for snapping to be identical in all editors, so since Ctrl and Alt are used to drag copies in the arrangement editor (Windows standard), it has to be Shift or some other combination.

@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?

@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”.