I've tried everything I can think of to get the snap function to work in X1. I have the latest update which is D.  I've engaged the grid symbol which looks nothing like the symbol in the manual.  Nothing works! Engaged, not engaged. It's all light up blue, I've selected Measure and everything else listed in the drop down menu. Nothing works! Neither does the global snap. No snap to grid works anywhere at all.

Puzzled. Any ideas?  Thanks!

Here are some things to try.
 
In preferences make sure that you have magnetic strength off.
Turn both the global snap and the PVR snap on and set them to something like 1/4 notes
Zoom in or out to see if you notice the snapping at a different zoom level.
 
I have had some trouble with the PVR snap as well but it was usually just me not having something checked correctly.
 
Let us know if any of that helps.

Are you using a drum map?

That seems to fix it.  Man, thanks a bunch. No, not using the drum map. Much appreciated!

No, not using a drum map.  I can't even find the drum map at all.  I opened up the getting started to check it out  but, there isn't an option for drum map anywhere in the midi track that I can find. I'm working with Battery.  I've just been trying to edit some drum tracks within the same midi track on one piano roll. It's the only way I know how to do it. As far as outputting audio I can send cells or groups to individual audio tracks for additional processing and leveling. Not even sure I need to use a Drum Map.  Since I can't find it, going to be real hard to use it.

drum maps are presented as virtual midi ports, so it's on the track view-input device where they show up, along with drum map manager that lets you change them and make new ones.  Really useful stuff, but not all that intuitive to use at first.  See you are a long time member and may well know all this, thought I'd throw it out anyway in case...

Also, are there really obnoxious penquins out there, outside Gotham City? They always seemed so cute, a jackass one is almost a contradiction.  Zen, perhaps...

In any case...I like the cut anybody's jib who uses a dimbulb phrase like "no worky".  

+1

Could you give me an example of using a drum map. What would a good real world example be? Also, where is it? I can't find it anywhere.  I've read that it's in the drop down menu for the output device. I'm just not seeing it where it's telling me I should. I have View dropdown set to ALL input, output I/O and the such.  Just not seeing it. I remember seeing it! I also remember that the snap function worked. Then that mysteriously vanished. I'm not sure when all this happened. But, I've been using Reason 6 for the most part. But, I wanted to fire up Battery and get back into using Sonar again since I can't use Omnisphere without it. lol.  If I could use VSTs inside the Reason app. I wouldn't use Sonar at all.  

Jackass Penguins are the ones you see the most on TV and the such. I'd say they are the typical penguin. They are called that because the Hee Haw which must have sounded familiar to whoever started calling them that. But, I'm sure they are suborn and ornery too! lol  The leader of a pack of Jackass Penguins is call the Johnny! I don't know why! But it happens to be my name. So, back in the day when we all had to think up band names or come up with user names and passwords, that's what I came up with. No different than Joel calling himself Deadmau5! Well, and I like penguins too.

Wow! I like penguins too! Although they do taste a bit like chicken.

well, you are in the right place - on the dropdown list over in the inspector where it gives you list of choices for output devices for the midi tracks. On that list you should see any drum maps that you have (which is probably none right now) and the option to add new drum map.  You can add one from the list there that has the midi specs for a number of different things.

The basic idea is real-time transformation - midi comes in from a source like a midi keybd or v-drums, and is sent out to the drum map, which maps the incoming midi notes to potentially different notes and also gives you the option to change other things en masse such as velocity - on a per note basis.

Here is the part where it gets, well, less than intuitive - the drum map is not just a way of mapping notes, but also a virtual midi port that once added to the project, becomes a potential midi input for other tracks. Typically they are synths or other midi driven instruments, but can be any midi track. 

So you either choose one that relates to the gear or synth you are using, which you can edit with the drum map manager if you need to change it (where it says 'drum map manager', in that same dropdown), or you can just go straight to the manager and create a new one that you can reuse later. You can also save presets that you changed under the same or different names. 

With keyboard midi, this is not as useful as with drums, hence the name drum maps, though there is nothing about it that is really limited to drums. That;s just where it's useful. I use it for two things - one is to change, or map,the note that a particular drum pad or v-drum component sends in to match what a softsynth like session drummer or battery might be expecting to make that particular drum sound, the other is to get rid of the notes and associated kit pieces that my pads or kit can never make, or that I never play, this makes it a lot cleaner to work in piano roll because you have things with the right names and you don;t have all the extraneous stuff to paw throug, rather only your particular kit pieces that you plan to use. 

Hope this helps.  Drum maps, once I got them down, became one of my favorite things in Sonar.  They could use to rewrite it as a generic transformation tool, IMO, but what it does is very useful.