Create a keycommand/function to reset snap points

[vncvr]

It happens all the time when editing small chunks of audio.

There is no quick way of resetting these snap points which affects all sorts of editing workflows, parameters and other basic commands like Quantize.

You can see the error in quantize

You can see me correcting snap points one at a time.

The only way to reset a snap point, is with the command ‘Snap Point To Cursor’, which does not work great when you have multiple events at different starting points.

This is a request that has been asked for years.

[GuyHaska]

This drives me nuts. Cubase seems to move the snap points randomly at times, I’ll be working on a project and a random piece of audio will suddenly have its snap point changed. I’ve never been able to figure out why this happens, if it’s me, or literally just random. Catches me out all the time. I have zero use for moveable snap points personally, so I’d prefer a command that snaps the snap point back to the start of the event instantly without moving the cursor to the start of the event and then reseting.

It’s rare I get the situation you describe but it does happen.

[Chikitin]

For now, what if you select all the audio and type the start of them in the info bar?
My parts move randomly too. I learned to use Locking events as soon as I think I am done. But recently I learned that locking events not always lock everything such as voicing or chords if it following the chord track!

[vncvr]

@guybuss

This drives me nuts. Cubase seems to move the snap points randomly at times, I’ll be working on a project and a random piece of audio will suddenly have its snap point changed. I’ve never been able to figure out why this happens, if it’s me, or literally just random. Catches me out all the time. I have zero use for moveable snap points personally, so I’d prefer a command that snaps the snap point back to the start of the event instantly without moving the cursor to the start of the event and then reseting.

It’s rare I get the situation you describe but it does happen.

In this instance, I’ve discovered it is ARA2/Spectralayers causing it when an event isn’t perfectly on the grid/start of a bar.

But this can’t be the only cause, I’ve had this problem occur a lot way before ARA2 was invented. Maybe as far back as SX3.

I have hundreds of projects, song ideas, etc with this problem. It becomes apparent when opening up old projects, or importing tracks to project.

There is also the issue of, and another instance I believe this pops up, is if you are recording I think there is some sort of “smart” placement of the start point that isn’t always correct, and or, if you have a long record buffer in which you are lengthening the start of the recorded events to include buffer.

[vncvr]

These creates SO MANY EDITING and EXPORT ERRORS - - - - PLEASE FIX THIS

[vncvr]

I figured out what can cause this!

BOUNCING WITH THE RANGE TOOL

(As well as initiating ARA2)

[faridbostan]

+1

[vncvr]

@faridbostan

+1

Thanks, this has been such an annoying quirk for so long!

[vncvr]

Anyone know if this was improved in Version 11? This has been complained about since probably SX3.

We need a key command/function to RESET - - - ALL - - - SNAP POINTS SELECTED EVENTS.

Automatically move all snap points to beginning of events?

Is there a way to automatically move ALL “snap points” in audio events to the beginning of all selected events? I want to move only the snap points, not the audio. See the picture below… the snap point is obviously not at the beginning of the audio event. Thanks, Todd [image]

Snap Point not aligned to the start of Recorded Audio Events

Cubase Pro 8.5 Event Snap Points not aligning to the start of Recorded Audio Events (Group Track Mono recordings in this case) I have never had this issue in Cubase 7 through to 8.0.30. The Event Snap Points would always be at the start of Split and Recorded Audio Events. There are no Snap Point preferences to be changed that I am aware of. The only other Event Snap Point issues ive ever experienced was in Cubase 7 where sometimes when moving Split edited Audio Events around on the Arrangeme…

Shortcut to remove "event snap points"

Well to be clear then, what i want it to do is reset all snap points to the beginnings of objects. With the way I edit there’s never a reason for them to be anywhere but that. Cubase never puts them anywhere BUT the beginning. So, you are somehow overriding that behavior. No way dude, i don’t think so. I posted about this some time ago, and no one seems to have an answer so I gave up. I swear to god sometimes these things show up out of nowhere at the most RANDOM spots. They are a nu…

Snap Points. HELP US TO ERADICATE!

+1 for an option to disable them globally.

Snap points

Yes, that’s a nice idea. Indeed it doesn’t do it at the moment, so you have to go back and drag/snap the sample. I tend to approach snap points in a slightly different way. I move the region (zoomed in) and then set the snap point using ‘snap point to cursor position’. So, I generally turn Snap off, then drag the part to line it up in the project window, audition it, then turn snap back on, line up the cursor on the barline and set ‘snap point to cursor’ (using a shortcut key). This way I g…

How to deal with snap points

How do you guys deal with snap points? Cubase places by default these snap points at the closet quantize value you have selected. You do not really need these snap points. Events should always snap at the begining of the event, whatever edit your are doing. These snap points kind of do the same thing as moving snapped to “grid relative”. I do not understand why we need these (they’ve been there a long time) and they just confuse people. Am I missing something here? (even after more than 10 …

FEATURE REQUEST - move snap point to event start

Under audio, I see there is an option for “move snap point to cursor”. I would like to request that an option be added for “move snap point to event start”. Why? I used hitpoints and sliced up a bunch of events into thousands of smaller events. The hitpoints worked great for this… however, I want to do some specific editing to some of the events. It seems that the snap points though are now no longer at the beginning of the events. I would like to be able to select all 100 events, and jus…

Snap Points - what's a quick way to set several at once?

I don’t know a way to set the snap point to the event start for multiple events, unless they start at the same time. Doesn’t Locate Selection, Snap Point to Cursor do it for individual events (It’s in the Key Commands)?

https://forums.steinberg.net/t/key-command-function-reset-snap-points-of-all-selected-events/143942

[vncvr]

I’ve discovered this also happens when exporting events and importing back into the project via ‘Create Audio Track’.

you can test this with a series of cycle markers guiding the export, if the cycle ranges are off the snap grid setting, it will add snap points automatically to the nearest grid line… sooooo annoying.

[nebulon5]

I LOVE this. Voted!

GOD I hate those dang things. They’ve created SO MUCH unnecessary work for me over the years.

[nebulon5]

@GuyHaska

This drives me nuts. Cubase seems to move the snap points randomly at times, I’ll be working on a project and a random piece of audio will suddenly have its snap point changed. I’ve never been able to figure out why this happens, if it’s me, or literally just random. Catches me out all the time. I have zero use for moveable snap points personally, so I’d prefer a command that snaps the snap point back to the start of the event instantly without moving the cursor to the start of the event and then reseting.

It’s rare I get the situation you describe but it does happen.

This happens to me CONSTANTLY as I import lots of events. They seemingly appear at random. Next time it happens I’m going to screenshot it and post here.

[eirik_myhr]

I agree, it would be good to be able to turn off the snap points globally. It seems like an old relic that was once a real plus, but nowadays could be working against both hitpoints and relative grid mode. I HAVE used snap points on some occations though, to quickly be able to timeline syncronize different rendered versions of the same mastered song, et cetera. And for sound design it could also be a plus. But shutting it off globally as an option, aye (maybe even as a default).

As a workaround in the meantime: Maybe select the event, then create a macro of “left selection to cursor” and then “set snap to cursor”, and then assign that macro to a key command…? Or if that doesn’t work, maybe a macro like " locators to selection", “go to left locator” and then “set snap to cursor”…?

[mixRyan]

After testing, I found a solution. I don’t know whether it works for you.

The set event snap point is not at the event start position

I found a solution,Uncheck Isert iXML Chunk in Export Audio Mixdown settings. There will be no dislocation. [3.pg]

[mlib]

@mixRyan

I found a solution.

You found a work-around. It’s not a solution and is still an issue that should be addressed by Steinberg devs. In the meantime, thank you for finding a work-around! <3

[Scavneck]

Steinberg are really starting to piss me off with these criminal bugs.

[Sector1]

Please address this Steinberg, this creates headaches and lost time for our dev team.

The above linked threads date back to 2012… 10 years ago!

[Electriks]

This costs so much time, often. If for whatever reason Cubase will always put in random snap points at times then there needs to be a simple, immediate way to reset the snap points with one command for as many events at a time as needed.

Is there progress on this? It still exists in C13.

[jrose]

SO NOW WE HAVE 2025! --I am starting to get really a… now!

First! I can add some more missbehavor of this grid or raster point marked “R” in a wave sample/event in Cubase!
And I know the ideas behind, when this was invented with Cubase in the 1990thies.
It was all about just meaningful, musically syncing to MIDI data these days.
But before I go on, I have to say, that this grid anchor point of an audio files syncing to other wave events is an absolut BASIC FUNCTIONALITY of every time aligned and groove orientated recording system!
(Have a look to Ableton Live, Melodyne e.g.)
Why? OK, let’s say we have a wave event which didn’t start with an obvious groove but evolves into one - solution here is a “R” grid point syncing to a musical “one”. And then this “R” point has to hold its wave event within this musical context. (let’s say the “one” in a grid)
And when I look onto the cubase elastique audio feature then the “R” point is essentially needed to be the anchor point for a musical “one”!
But today it is not in every “new” function integrated so it seem not to be reliably working for us users!

So I wonder that this is not been addressed since let say at least the last 15 years!

For now I have to use other software for time alining groove tasks or changing tempo, for a group of files because Cubase can not reliably handle this without the perfect right “R” base functionality! And elastique audio (audio warp, music mode) in groups would then also be an almost unusable feature.

For only simple move and editing, there should be a “switch of” or bypass functionality.
(but then, there must be clear, every tempo change is a manual work/move for every special audio event - reversed cymbals eg.! And the switch to musical grid would be useless. As a result, the musical anchor for a audio event has to be always this “R” snap point as a first or last hit point, and it is, almost!
And this is the way Cubase wants to be designed, I guess - please tell me if I’m wrong.

So, what don’t work with “R” snap point / anchor point for wave snippets (events) in Cubase 14 right now:

• tempo change before an audio event with “R” position at the end (eg. reversed cymbals) - algo. takes always the beginning of the event and moves this audio musically wrong!
• a track group move do not snap to the grid, even, when all events have the same “R”, always the beginning of the first wave events (in that group) is locked, which could be meaningless in a sense of musical groove, and the “one” gets lost! - manual repair is the consequence, and we have to move it, one by one!
• in group edit mode, only the “R” position of the first wave event ist changed - dangerous!
• a longer audio with sync to “R” to the beat - it didn’t hold the wave event on the beat, when a tempo change in a project is made- important one for elastic audio!
• in group move mode it is not snaping, in fact, a group should have an actor/snap point for the group (so I could forget all the already single synced wave snippets, like it is already realized for parts )
• missing snap to “R”, snap could help for sample precise operations
• container for wave events (= parts), every wave event has it’s own “R” sync point, not only the beginning of an event! (not implemented, as it is for single audio events, yet)
• even a audio part should have an option for a own “R” snap

As we can see, there are some missing consistency for the “R” snap point.
And as we can see , this leads to misunderstanding and sometimes to frustration for the user.
(see here Create a keycommand/function to reset snap points - #18 by Electriks)

Steinberg Dev, feel free to contact me for a more precise idea for an perfectly implemented anchor/snap point, it could making Cubase a way more exiting experience, working with daily.

And I know this new fancy stuff is also necessary, these days, but a logical use of “R” in all the program units would make a lot of sense to me.