The long/short files names did catch me off guard. I went back through this thread searching for specs on your new machine and didn't see it. Can you let us know what machine you got as a replacement, operating system, etc.? Also what OS you came from (assuming XP) would be helpful, as the jump from XP->W7 can make older external hardware not function.
 
When I saw the long/short comment it made me worry we are all chasing the wrong rabbit.

mettelus
When I saw the long/short comment it made me worry we are all chasing the wrong rabbit.

Exactly... More info please!
I was afraid the pit maneuver above might have distracted my point here. Thx for repeating it.

Wow..this thread got pretty big....I think  he's on the road....so let me chime in for him...
 
He just got the computer....I think he ended up with a Dell (can't remember the model)...but it's an i5 processor, 8GB RAM, single 1TB HDD, Windows 10 OS
 
Roland Quad Capture for an interface
 
No external controllers.....he's strictly micing his guitar amp....goes direct in with the bass (I believe) and is trying to get used to VST's....specifically drums....specifically Addictive Drums 2 (or Session Drummer, I suppose...though I've tried to get him to concentrate on AD2)
 
Not a lot of software on it, I wouldn't think...as far as I know, the only thing he's installed is the software for Sonar, Addictive Drums 2 and whatever else came with the Sonar Professional package.
 
He'll correct me if I'm wrong...
 
I think that he's got some settings or configurations incorrectly set, and/or he's just not sure where to look for things or how to use them when he finds them.
 
I'm also wondering if at least a small part of his issue could be some sort of conflict between his onboard audio and the Roland....I know I turned my onboard off in the BIOS when I built my current machine....and that cleared up a couple of weird issues I was having at the time.  I suggested turning off his onboard either in BIOS or device manager, but not sure if he did or not.
 
I highly doubt a complete system reinstall is necessary at this point....not out of the realm of possibility...but...I'm pretty hopeful that his issues are just a number of minor things that can be fixed without too much hassle. :)
 
I've been trying to get him to let me remote into his machine so that I can take a look and maybe help him figure some of his issues out....as I'm too far away to just drop in and sit at his desk.
 
 
Maybe after the Holiday weekend....

Hi Anthony, I have a youtube channel on which I do tutorial videos on mixing. If you like you can PM me with details about what you would like to know, and if I know, I can do a video for you, then after the first video you can tell me what you want to cover next and so on. I'm sure your not the only one to have problems so I would have no issue doing the vids, Just let me know the specifics of what you want to know. I'm a sonar user since x1 and like you I use a roland quad capture and I use Addictive drums 2 in all my projects.
All the best,
Andrew

Okay this help is really wonderful. I think I need to look at the step sequencer. I am stuck in the paradigm of the drum machine. I am used to programming a Dr. Rhythm drum machine using PA9 to trigger via MIDI and then physically recording on two tracks. I will chuck the drum map. Ad2 and session drummer both work fine (as far as sound) when loaded by themselves. I'm confused as to how to get the drums named on the step sequencer and then to get that info to an Audio track. I never use loops. Punching in beat by beat in the step sequencer is really appealing to me. Love the drum sounds. I think my failure to understand soft synths is the road block. How to get the step sequencer patterns to an audio clip. Timescale, step sequencer, everything else is set.


The long/short name was a help recommendation in cakewalk. It was based on the error message I only got with the drum map-loaded cakewalk file. Looking in the directory on my computer I did have that 'problem'. Short names were not visible.

AnthonyMangos
The long/short name was a help recommendation in cakewalk. It was based on the error message I only got with the drum map-loaded cakewalk file. Looking in the directory on my computer I did have that 'problem'. Short names were not visible.

I'm assume this is it...?

http://forum.cakewalk.com/tm.aspx?m=2681013

I see the cakewalk quote:

'Ultimately we will try and move away from this dependency but it involves backwards compatibility issues with projects so we can't completely sever this tie.'.

That was in 2012 not sure if anything changed or not. This isn't a hack I'd like to dive into anyway.

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

Just to let everyone know. I received an e-mail from Addictive Drums with helpful hints ( won't be at my computer until Saturday to try anything). The customer service from Cakewalk and XLN is above and beyond.

AnthonyMangos
Just to let everyone know. I received an e-mail from Addictive Drums with helpful hints ( won't be at my computer until Saturday to try anything). The customer service from Cakewalk and XLN is above and beyond.

 
+1

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.
 
The far more usual things (in my opinion) that I have seen is where folks:
 
1) Had ASIO4ALL installed from some attempt at using it, but left it on their machine after moving on to the ASIO drivers of an actual audio interface, where ASIO4ALL somehow had interfered with the other ASIO drivers.
2)  Were having issues trying to use ASIO with multiple audio interfaces from different manufacturers at the same time.
3) Were using the ASIO drivers of their audio interface, BUT also had the Windows Default Audio Device trying to access the ASIO drivers of their audio interface, and conflicts arose.
4) Had ASIO drivers available for an audio interface, (which others were using successfully), but for some reason were using WDM/MME (non-ASIO) drivers, and getting poor performance.  (please note that for some, better success has been reported using WDM rather than ASIO for their particular audio interface)/
 
Some folks also choose to go into Windows Device Manager, and disable their on-board audio drivers there, rather than going into the BIOS.
 
Others, like myself, run using the ASIO drivers for their audio interface, and have their Windows Default Audio Device set to the on-board audio, and then run the output from the computer's audio to 1 of 3 places: 1st - a set of separate speakers than what the audio interface uses, 2nd - they feed the computer's audio output back into the audio interface into an input channel on the interface (sacrificing an input for the sake of better sound than computer speakers), or 3rd - (and this is what I do), I use multiple HDTV's as display monitors, and I select an HDMI output for my Windows Default Audio Device, and it sends the audio through the HDMI cable to one of the monitors - using its built-in speakers.
 
I think that when the original poster becomes available, and perhaps with your assistance, as well as others here in the forum, that we can methodically go through a review of the connections, settings, and such, and likely get his computer up and running properly.  The fact that there are not bunches of people posting about Sonar failing to produce audio output is a good indicator that the issues are local to that computer and its setup/configuration for audio streaming with Sonar, and therefore quite likely able to be resolved with some interactive guidance.
 
 
There will still be a learning curve, but really, for basic recording, playback, and editing, many of the functions are the same, it's just a matter of remapping the 'how to do them' that is needed.  Newer features can be learned after figuring out the basics of it all in the new user interface.
 
Bob Bone