Gee wiz ... Now, my Keystation 49e Won't WORK either!!!

Hey Guru's!
It's me again with a similar device and a totally different prob.  Im hoping this one will go a little smoother with the diagnosis and results, for my last dilemma was with my Radium 49 which I found in the end was due to the fact that sometimes cakewalk (or maybe its the laptop I use) is sensitive to the EXACT USB PORT  that was used the first time I installed the device.  In my case I had used a new cheap little usb extension resembling a human figure with hands and feet being the extra usb jacks. So until I randomly tried that I was having all kinds of inconsistent B.S. But on to the Keystation 49e problem, I bumped my Radium 49 off the stand and it fell on the usb jack and broke it of so until I get the cord that converts midi to mini at Best Buy or make one from Axman, I am stuck with this one: 
 
My CPU Stats are at the bottom of this message.  I have a Gateway laptop using Sonar x1 producer. I have the right driver and supposedly this one doesn't need a driver due to it falling under the category of older M-Audio devices that are USB compatible with anything Xp and beyond or something....  Now I just had my Radium going on this actual projeft and everything and it worked fine so naturally this one plugged in and I can hear right away that it works... However, the latency is real choppy and not like it should be. I usually use it for drums and if that is all I can use it for i'd be happy but anyways, what's weird is when I just touch one key over and over like as if to play a hi-hat, the latency catches up almost and starts acting normal except the notes or drums change with each touch of the SAME key like its going through the whole list of sounds for me.  It does this all over the keyboard even if I hit the little pitch buttons to move the drums up and down the keys like they should but still hit any key twice and get two different drums.  Is this an easy one to figure out my fellow obsessed cake eaters?  I hope so and thanks in advance for any input, I DO appreciate it and hope I can teach myself enough of this program to be of help as well to others here in the future.
 
- Joe
 
Here's my CPU Stats:
 ComponentDetailsSubscoreBase scoreProcessorIntel(R) Pentium(R) Dual CPU T2330 @ 1.60GHz4.43.0  Determined by lowest subscoreMemory (RAM)2.00 GB4.4GraphicsMobile Intel(R) 965 Express Chipset Family3.1Gaming graphics358 MB Total available graphics memory3.0Primary hard disk24GB Free (138GB Total)4.8Windows 7 EnterpriseSystem  

---

 ManufacturerGateway ModelMT6728 Total amount of system memory2.00 GB RAM System type32-bit operating system Number of processor cores2 64-bit capableYesStorage  

---

 Total size of hard disk(s)149 GB Disk partition (C:)24 GB Free (138 GB Total) Disk partition (D:)314 MB Free (11 GB Total) Media drive (E:)CD/DVD Media drive (F:)CD/DVDGraphics  

---

 Display adapter typeMobile Intel(R) 965 Express Chipset Family Total available graphics memory358 MB       Dedicated graphics memory0 MB       Dedicated system memory64 MB       Shared system memory294 MB Display adapter driver version8.15.10.1930 Primary monitor resolution1280x800 DirectX versionDirectX 10Network  

---

 Notes  

---

 

Sounds to me like you've got the keyboard in some kind of command function mode instead of set to regular input and it is browsing through the notes/cycling through MIDI note values. Try it with a piano patch and see if the notes raise/lower in pitch as you hit a single key. If that is the case you may have to refer to the controller's manual to see how to get it out of that mode.
 
As far as the latency thing... turn down your buffers while recording. Turn them back up again when you are done. If you experience dropouts or freeze up when you have them turned down freeze all other tracks and effects and use as few active effects on the track you are working with.
 
Just taking guesses here.

Yeah I kind of glossed over those specs because... well, that's a bit of a mess. lol
 
Upon further inspection that is not a very powerful system and you only have a single hardrive which is getting pretty maxed out. Your CPU is just barely hitting minimum specs from what I remember of the requirements, your RAM is kind of low... IDK. I'm guessing there is a lot of potential problems here if you just took an old system you've been using for general stuff and slapped Sonar onto it. There could be viruses, tons of startup programs and bloatware screwing around, no optimization and quite likely the internal soundcard is being used (no interface).
 
Technically you could make this system work for MIDI input and it sounds like you have already but you really should get rid of any crap you don't need, do some optimization and hopefully get an interface. If you can't afford an interface and you are just doing MIDI you could clean up the system, tweak it and use asio4all which helped me get rid of latency when I was playing around with FLStudio with my padKontrol to test it out before I built my DAW.
 
You should have a restore disc somewhere or the system might have a restore partition on it if Windows came preinstalled. I'd go through all the files and back up anything you need (this is a good opportunity to go through all your files to delete any junk) then restore it to the factory defaults. Install any Windows updates and necessary drivers (you will lose the ones you have and EVERYTHING except what was on the computer when it left the store). Remove any unneeded bloatware like crummy starter promo AVs or other crap (on mine I had a ton of stuff like Netflix starter programs and Microsoft crap that was only designed to make me buy stuff). Once the computer is clean and updated create an image or restore point, look into optimization for audio, install ASIO4ALL if you need to (but better to get an interface and use a true ASIO driver) and read the manuals for your devices and do the Sonar tutorials.
 
Probably best if you don't let your gear fall on the ground too. ;-)

In the future when asking the forum for help make sure you let everyone know you do not have an interface. A lot of people will simply say you need one but others can and likely will help you fix the problem even if you don't. Without that info though you are leaving out a big piece of the puzzle and it can be a little off putting. You could also trim down those system specs so they only convey the necessary info. CPU (model/Ghz), RAM (how many gigs), OS (which version/32 or 64bit), hard drives (type/speed if available) and version of Sonar you are using (including what patch you are on and whether it is 32 or 64 bit). If you get an interface then include that info as well and any other hardware you are using when the problem arises.
 
Just sayin'... oh and don't use swear words in your thread titles even if they are only fake swears.
 
Hope you sort out your problem.

Doesn't offend me (I cuss like a sailor IRL) but some folks may find it rude or aggressive and pass over the question. Just trying help you get the best help you can. This in general is a very polite forum. It's kind of nice compared to some of the other sites I frequent. lol
 
BTW I thought I had broken the USB jack on one of my devices because it stopped sending/receiving signal after I had bumped the connector into something on my desk but I swapped out the USB cord and it started working again. Might want to try that or maybe jiggle it around a bit (gently) to see what happens. I've even seen people use some tinfoil to fix loose USB connections but I absolutely do NOT recommend that unless you are a) really familiar with exactly how physical USB connections/shielding works and b) don't mind potentially frying something. Not even sure if it works but I have indeed seen it before when I worked with electronics.