robert_e_bone
I have seen only a small number (2-3) that I can recall, where someone did indeed have some sort of conflict where turning off their on-board sound resolved it.

I can't and won't speak for everyone, I just know it worked for me.  And it's just one option.  And yup....you can do it in device manager as well, and that would work just fine...BIOS is the way I chose to do it.
 
But I agree....I think he has settings /configurations improperly......set. :)

Bob thanks-

I'm now getting Audio fine except when I use a file with a drum map I downloaded. The drum map I loaded got me the names of the drums and had them routed to tracks but I couldn't then get sound.

All other audio works when I don't use the drum map file.

I am going to read up and find how I can get drum names onto the step sequencer and then how to get that onto an audio track. X3 Power does not really explain that.

Getting drum names and then getting the step sequencer patterns to a track are my hurdles now.

AnthonyMangos
Bob thanks-

I'm now getting Audio fine except when I use a file with a drum map I downloaded. The drum map I loaded got me the names of the drums and had them routed to tracks but I couldn't then get sound.

All other audio works when I don't use the drum map file.

I am going to read up and find how I can get drum names onto the step sequencer and then how to get that onto an audio track. X3 Power does not really explain that.

Getting drum names and then getting the step sequencer patterns to a track are my hurdles now.

You may want to take a look at the MIDI map in AddictiveDrums. It's a pop up page that shows what each kitpiece/articulation is mapped to which MIDI Note (on a keyboard graphic to make it easier to understand). You can compare that to your Step Sequencer "Rows" to make sure each "Row" triggers the desired kit piece/articulation. You just set the row to trigger the correct note for each element (like Kick, Snare, Hats, Bass, etc and you can add rows for the "articulations" as well like Snare Stick Hit, Hi Hat open and Close, etc).
 
I cannot recall how (or if) you can manually rename the Step Sequencer rows but just looking at that AD2 map might help you start making more sense of it all.
 
Essentially your Step Sequencer "Rows" each trigger a different "MIDI Note" that then triggers the corresponding note in AD2 (according to AD2's MIDI Map). You just make sure the note aside to each row corresponds with the correct kit piece/articulation on the AD2 MIDI Map.
 
The AD2 manual will show you how to access the MIDI Map. You can even adjust the map to make things easier if you want so if you want to keep all your kit pieces in the C1-C2 range just change the AD2 map to do something like put your Kick at C1, your Snare at D1, your hats on E1, your ride on F1, etc. That way it's all compact. 
 
Then you can save your new AD2 MIDI keymap as a map preset and access it whenever you want for step sequencer work (so just load the MIDI Map in AD2 and use those notes in SS for a simple, MIDI note based SS row setup).
 
Just some cool stuff to chew on that might help you wrap your head around the relationship between the SS and AD2.
 
Cheers.
 
PS: That is NOT a Sonar Drum Map situation. In fact it totally avoids drum maps intentionally. It's super simple once you take a look at what I'm talking about. That is all referring to the internal MIDI Note mapping INSIDE AD2... so disable your drum maps if you intend to do this.

AnthonyMangos
Bob thanks-

I'm now getting Audio fine except when I use a file with a drum map I downloaded. The drum map I loaded got me the names of the drums and had them routed to tracks but I couldn't then get sound.

All other audio works when I don't use the drum map file.

I am going to read up and find how I can get drum names onto the step sequencer and then how to get that onto an audio track. X3 Power does not really explain that.

Getting drum names and then getting the step sequencer patterns to a track are my hurdles now.

Also check what I said in post #137

Bristol_Jonesey

Also check what I said in post #137

Indeed and just in case it was missed here it is again...
 

Bristol_Jonesey
One thing I don't think has been mentioned about drum maps.
 
If you open the map you must ensure that the Out Port on each mapped key corresponds to whatever VSTi you're using, otherwise nothing will sound

Without routing THROUGH the Drum Map using a bunch of drum map voodoo on the track(s) you're boned. That's why I was saying that perhaps that getting just a little too advanced at this point because Drum Maps do a TON of stuff and need to be set up/routed just right.
 
I think based on the limited time to OP has to play with things and limited experience with the program direct mapping would be better to see what's going on there and THEN digging into the Drum Map stuff can take it to the next level if he needs it.
 
IDK... I try to be a "path of least resistance" dude and based on what Anthony has said it sounds like he just wants to program a simple beat in the SS to trigger AD2 and then go apeballs with his guit and bass over top of it.
 
I can TOTALLY sympathize with/understand that because that's where I was when I started and really what I do now isn't far off from that setup.

To use Drum Maps they have to be setup right. You get to them via the Drum Map manager.
 

 
 The picture is the default outs for the drum map. Clearly it will not trigger AD 2. It is set for in this case to my XV5080 Roland hardware synth.
 

 
Now you see it set to Addictive Drums. The way I do this is while holding down Shift + Ctrl and clicking on the drop down arrow I set it to AD and all the outs will set to the same. From there when you open the SS or the PRV (Piano Roll View) you will see the names of drums not notes. 

Bristol_Jonesey (#137) had the same thought I did. Drum maps not only specify note value for each drum trigger, but also a midi port.  This is a valuable feature if you want to create kits using a combination of different drum sources.  This value might be mis-set as a global value for the entire drum map, or it might apply to individual note/trigger mappings, so be sure to check both.  (I'm personally not too map savvy.)
 
And, AnthonyMangos, be patient.  The flexibility of the SPLAT (Sonar Platinum) interface gives you the flexibility to work the way you want once you get past the initial learning curve. And the CCC control panel--while initially a bit unfamiliar--ends of creating an expressway for new features and improvements to flow into your system.  Most ideas stem from discussions on these forum (fora?) so you have already contributed your experience into the community.

 
BTW, I really agree with an earlier post about the challenges of accessing documentation.  Again, the frequent updates make flexible docs essential.  You can't make monthly improvements and expect paper (or even pdf docs) to stay perfectly in synch.  </feature_suggestion> Bakers, why not put links to documentation onto the CCC installation page for each application?  </feature_suggestion> 

AnthonyMangos

Getting drum names and then getting the step sequencer patterns to a track are my hurdles now.
 

Another thing occurred to me that has not been mentioned yet. AD2 uses it own proprietary drum map (internally) to take advantage of its entire kit. Realistically (and especially first starting out and wanting to make something), you may be more familiar with General MIDI (GM format). In the upper right of the AD2 UI, the "?" has a "Map Window" option. In the upper left of that window, you can change "Map Preset" from "AD2 Standard" to "GM"
 
A few options to expedite things:

1. Open an old project you made and save it with a new project name (so the original is not altered). With AD2 set to GM per above, you can insert an instance of AD2, choose a kit, and set the Output of your original drum MIDI track to AD2. Play the project, and should sound with the AD2 kit (versus what you originally used).
2. If creating a new project, leave the AD2 internal drum map set to its default (AD2 Standard). On the Beats tab in AD2, "Sync Tempo" in the lower right allows you to change SONAR tempo and have AD2 stay synced. Two things you can do:
   1. Drag a beat pattern from the left pane into your AD2 MIDI track for editing. Doing this, you will then need to right click that clip and "Convert MIDI Clip(s) to Step Sequencer" and a popup will give you resolution. Just choose default initially, and then double clicking that clip should open the Step Sequencer (but no names). If you then output the AD2 MIDI track to ->New drum Map->AD2 Standard (for the templates in the blog above), the names should then appear.
   2. Alternatively, can use a MIDI controller to enter notes. Unfortunately, just clicking on kit pieces in AD2 does not create any MIDI track data (which would be simplest).
3. I am also not a drum map fan, but IIRC, there used to be an issue that drum map names did not show unless at least one MIDI event existed on the track.

Having said that, I do copy/paste a lot for MIDI events using Piano Roll View (PRV). After inserting an instance of AD2, again set the output to "New Drum Map"-->AD2 Standard (and leave AD2's internal map to "AD2 Standard" as well). If you have already been playing around, that with actually be in the first-tier output options.

1. Right click the empty MIDI track for AD2->View->Piano Roll View (PRV).
2. Hit Shift-D to maximize this view.
3. Tricky part (but important you know this) - by default, the PRV will only show you keys, and is not obvious that there is another pane ABOVE those keys. Hover the mouse over the top key until you get an "=" with and arrow at top/bottom (will drag the pane divider). When you get that cursor, left click and drag it to the bottom of the PRV... now the left pane should show kit piece names.
4. Single clicking in that left pane will "fire" any pieces mapped in the kit... can even left click and move the mouse up/down the kit to find pieces.
5. Double clicking in the right pane will add transient events based on your snap-to-grid settings.
6. With a few notes added, you can right click and drag to lasso-select things, then copy (ctrl-c), select a new time position at the top, then paste (ctrl-v).
7. "D" will restore/minimize the Multidock (containing the PRV) to help you jump back and forth between Track View (TV) and PRV.
8. Say you have created 2 bars that you like and want to loop it (as you would with Step Sequencer)... hit D to see the Track View, then left click/drag through your looping content. Right click and "Bounce to Clip(s)" to meld them into one unit (needed if you used copy/paste in the PRV). Then right click again and select "Groove Clip Looping" - this creates a loop and visually will lop the corners off the clip. If you hover over the right edge, you will see a "<-|->" cursor... left click that and you can drag your loop to any length and it will auto repeat as it fills. Right click and bouncing to clip(s) will render a single clip to easily chop/swap things in the middle, add transients/fills, etc.
9. You can also copy/paste into the track view, and bouncing/groove clip looping is convenient.
10. You can also use multiple MIDI tracks to feed the same AD2 instance, so can keep Hi Hats/Cymbals on one, Kick/Snare on another, or whatever you choose.

I just wanted to throw that second option out for you, as I typically use TV/PRV combo to lay down drums (even if pulling a MIDI clip from AD2's "Beats" tab initially).
 
The Step Sequencer and I have not gotten along well, so I admittedly have not used it seriously for some time.
 

Thanks to everyone fro their help, but this is all I want to accomplish:
 
1)  I create a new file - basic
2)  I have track 1 - audio, track 2 - midi
3)  A was able to load Addictive Drums to the audio track under FX - AD2 is set for Studio Rock - Perfect. 
4)  I wasn't able to load Addictive Drums to the midi track - do I even need to?
5)  The step sequencer view is not selectable.
 
At this point, I can't worry about the drum names.  My sound is working.
 
I want to:
 
1)  Make the step sequencer selectable
2)  Then enter a beat into it (I know how to do that)
3)  Get that beat to an audio track. 
 
What are the steps -
1)  What track(s) do I need to create; what will the settings be? 
2)  What will their purpose be?
3)  How do I arm them for the MIDI? 
 
I've read hundreds of pages and not found the above.  I've spent three more hours this morning.
 
X3 Power keeps wandering off to information that is beyond me.   The AD Manual just shows set up.  And Sonar Help is of little use in this matter.  Being able to do this will allow me to understand how these work and what is happening.  One of the tutorials showed how I could create a groove track and split/edit it, but not how to set it up.
 
Plus since I've always entered drumbeats note by note, this will allow me to enter any drumbeat I want with the studio rock kit. 
 
 

When getting started, it might be easiest to add AD2 via one of the menu options instead of adding tracks and then adding the synth. To add AD2 either
1) From the main menu Insert > Soft Synth > VST2 > select AD2 from list or
2) From the browser click the Plugins tab, click the instruments button, open the VST2 folder in the treeview and drag and drop AD2 into the project or
3) Click the synth tab in the browser, click the plus to insert a synth and follow that menu to AD2.
All of these will open the "Insert Soft Synth Options" dialog. To add a synth with an audio and a MIDI track, click MIDI Source and First Synth Audio Ouput to create the tracks to use by the synth.

Select the MIDI track
Open the Step Sequencer view
 
 
This will create an audio and MIDI track with AD2 as the audio track input and the MIDI track output. The last two step also add the Step Sequencer ready to add data to the MIDI track.
 
There is no need to arm any track for recording when entering data directly into the Step Sequencer or Piano Roll Views. Arm the MIDI track if you wish to record MIDI from your controller and/or arm the audio track if you want to record the synth directly.