@Bub - i will check that out - another freeware app - how it works better than the 1st one. thanks

Hi rcassent:

I did skim over your posts here, but a lot was unclear to me about what you really mean.

No need to get touchy. You talk with a tone of a person pretty familiar with advanced computer related operation, so that's how I'll come at you hereafter.

If you've updated Windows with Windows updates, updated your drivers for the motherboard, updated BIOS if possible, updated graphics card and audio interface drivers, done the tweaks of disabling any power management functions you may have in the BIOS (also disable HPET if you have that in your BIOS), the DPC Latency checker is showing readings in the green (though you don't indicate where in the green [usecs?,])) and you set Windows power management to always on, it seems the thing left to do (since you're still getting drop outs) is a complete uninstall of X1 including registry entries, and re-install SONAR X1, then, see how it runs.

If you're still getting drop-outs after a complete uninstall and reinstall of X1, it's appears it's time to contact a DAW builder such as Jim Roseberry of http://www.studiocat.com/3/index.php/Home for a consultation about the best way forward, or leave off using X1, as you mentioned earlier.

@thomas barnes, sorry about there tone of the email but i am an IT person during the day and the computer is too new for new drivers as i just purchased it on jan 19th so there is nothing to update for drivers. my appologies if i came off harsh. 
 
 i have already uninstalled and reinstalled sonar using different audio and midi cards and both fail. i was thinking of trying to install sonar 8.5. maybe i need to go back and reord this thread. anyway, everything i tried for this in this blog has been yet to be unsucessful. i will talk again with sonar support, motu support, and dell support.  i have been using Cakewalk since it conception and i did not have thies issues with sonar 7 and 8.5 or anything other version that was not solvable with a phone call to tech support. just dont know what the problem is but thanks for the suggestions
 
EDIT:spelling and gammer - i thought i posted somewhere that i ripped out Sonar and did a reinstall on Saturday DAY4. i have to go back and look

For me, Sonar occassionally stops and gives me a message about audio drop-outs.  This is infrequent but very annoying and can only be fixed via reboot.  I have not been able to find a cause or pattern.

Running Win 7 64-bit, i7 processor, 12GB, V-Studio 700, X1B. PC is Sweetwater Creation Station optimized as a DAW so no junk applications running in the background that I know of or see when I investigate.  I use a fair amount of virtual instrument plug-ins—10-14 instances on some projects.  Not sure if that contributes.

If I come up with something that helps, I will share.

OK just did some more attentative reading of your posts.

Things I failed to recognize at first but now see:

Your firewire card doesn't appear to be TI chipset based. Is that right? TI chipset based cards are usually reliable. You should use one for a firewire audio interface.

However, you have a Delta 1010. After all the tweaks and configuring of the new machine, have you tried the Delta in both modes: ASIO and WDM? In my experience reading here Tascam audio interfaces have drivers not usually capable of running projects at lower latency settings (256 samples and lower) with good performance and stability.

If you are saying the demo projects run well on a different machine using SONAR 7. That's really saying nothing. Do you have SONAR 7 on the new machine and have you run the demo projects on the new machine with SONAR 7?

There's a need to keep the troubleshooting related tasks performed on the new machine.

I don't know if the new machine has a PCI slot on the mobo so you can run the Delta 1010, but I would test with that audio interface in both driver modes (ASIO and WDM,) if possible.

I would try the MOTU unit with a TI Based chipset. The TI based chipset is really important.
Using a TI Based chipset firewire card have been known to solve problems of dropuots, pops, and clicks, and stuttering in playback/recording.
And maybe try running the demo projects on the new machine with SONAR 7, for comparison to X1.

Cya around.

Just to be clear, I don't think the MIDISport 4x4 is much to do with it, just making the OP aware that their drivers aren't without issues, but also having said that on my latest system they seem to be more stable than my previous one.

I'd also agree with thomasbarnes that you can't really compare V7 & X1 on two different machines. I'd try installing V7 on the problematic machine and see how that runs. My money is on a driver somewhere.

It's also worth mentioning that the latest drivers aren't necessarily the greatest. I'm currently running an older than current driver for my ZED-R16 because the new driver has issues.

RCA: unless the chipset/inf drivers are install'd updated for the os.. the system/systems will have a hard time landing devices's. !!

thomasabarnes


OK just did some more attentative reading of your posts.

Things I failed to recognize at first but now see:

Your firewire card doesn't appear to be TI chipset based. Is that right? TI chipset based cards are usually reliable. You should use one for a firewire audio interface.

However, you have a Delta 1010. After all the tweaks and configuring of the new machine, have you tried the Delta in both modes: ASIO and WDM? In my experience reading here Tascam audio interfaces have drivers not usually capable of running projects at lower latency settings (256 samples and lower) with good performance and stability.

If you are saying the demo projects run well on a different machine using SONAR 7. That's really saying nothing. Do you have SONAR 7 on the new machine and have you run the demo projects on the new machine with SONAR 7?

There's a need to keep the troubleshooting related tasks performed on the new machine.

I don't know if the new machine has a PCI slot on the mobo so you can run the Delta 1010, but I would test with that audio interface in both driver modes (ASIO and WDM,) if possible.

I would try the MOTU unit with a TI Based chipset. The TI based chipset is really important.
Using a TI Based chipset firewire card have been known to solve problems of dropuots, pops, and clicks, and stuttering in playback/recording.
And maybe try running the demo projects on the new machine with SONAR 7, for comparison to X1.

Cya around.

@thomasabarnes - thanks for the feedback. i will answer as best as possible:
 
1. Your firewire card doesn't appear to be TI chipset based? - yes not TI, it is LSI and is confiremed compatable via sonar support.
 
2. you have a Delta 1010? yes bit i am not using Delta1010 in any of the above scerio's. only use Motu and midisport toghters or the Tascam. you might want to cehck thru my artilce again as i never mention delta1010. :)
 
3. Do you have SONAR 7 on the new machine ? no it is running on a sepearte Dell XPS comuter which is still my production machine for the studio since it is stable. i did the comparison to see if there were issue with the files. more the file i created and i use as test bed for X1 than the demo's. i am thinking about installing Sonar 8.5 on the new Dell Perscions in place of X1 to see if it works. but first, i am going to pull some hardware for the persion to see if there are interupt conflicts
 
4. There's a need to keep the troubleshooting related tasks performed on the new machine.?  =- yes, i agree!
 
5. I would try the MOTU unit with a TI Based chipset. ? - as stated before, i anot useing the Delta 1010 anyware in this scenerio

OK I'm aware you didn't mention you were using the Delta. What I'm doing is drawing your attention to use the Delta rather than the Tascam unit because from reading users' experiences in this community with Tascam units, the drivers make Tascam units poor audio interfaces  for running projects with moderate payloads (or heavier,) such as some of the SONAR demo projects, for example. I would not recommend a Tascam unit to anyone. And this is mostly because of user reports in this community.

However, I have experience with a Delta unit. I have the Delta 1010LT, and I can run the demo projects you mention at a 64 sample size and 44.1 with no dropouts using my delta 1010LT. And M-Audio has a history of being praiseworthy for writing good drivers for their Delta series.

Bless Cakewalk's tech support heart. However, even though they tell you the LST based firewire card is supported by SONAR, I'm telling you from many experiences here with users reports, including my own, MOTU firewire units most likely yield better and stable performance when connected to a TI based firewire unit, rather than a non-TI based firewire card.

There are some via chipset based firewire units that work OK with MOTU units, but most reports and experiences point to a TI based chipset unit as reliable to help yield the best performance from MOTU firewire units. Moreover, I'm bringing your attention to using a TI Based firewire chipset because in the past, users here with non-TI based firewire chipsets have reported dropout issues, and issues with clicks and pops during playback/recording, and they have come back to report the drop outs, pops and clicks issues were resolved after they got a TI based firewire card (and in addition some even had to use the legacy driver for the firewire controller.)

Now, will this mean your dropout issues will be resolved if you get a TI based firewire card? No. But depending on how important it is for you to get a stable DAW system, it may be worth a shot to try one.

Believe it or not, I'm telling you what has made a difference for a number of users, and although that's no guarantee it will resolve your dropout issue, maybe you will feel it's worth a shot to try.

I know you're probably tired of trying things we are suggesting may help solve your problem, but once you finally get the issue resolved, I'm sure you will find it worth the effort.

Goodluck to you.

And the cost involved getting one is lower than the trouble it might get you if not getting one...

Bristol_Jonesey


Any of the specialist DAW builders will tell plain & simple - if you're running Firewire, you MUST make sure it's a TI chipset.

Otherwise you'll get dropouts...........................

@Thomas abarnes-  i only use my USB Tascam unit on my laptop. i use it for small portable projects. it works fine for that scenario. nothing big on my laptop.
 
was forced to use it in this scenario to try and prove to sonar support that both interfaces failed, hoping one would work over the other so it would point to a device and maybe drivers. the tascam is USB and the Motu is firewire use with midsport 8x8 (USB)for midi.

its all i had to use that was external device. :)

 now, i do have the delta 1010 but it is a PCI based card and i would have to start yanking PCI cards to put it in. i do have that option and have not ruled that out especiallyl after what i have been thru. i did download the drivers in preperation. 
 
@ this forum:
 
my next step is to talk with Dell:
1. i plan on pulling some PCI card tonight but i want to test with motu and midisport one more time once some interrupts are freed by PCI slots
 
2. Sonar helpdesk are looking thru files i sent them today and will get back with me at 5pm (hardware stats)
 
3. Sweetwater support is chimming in since i bought all hardware from them and they are folliowing this blog.
 
4. Motu support is not replying to any emails.
 
5. NI is out of th mix since i unistalled there software, but they were not a cause in the probelm as far as i can see 
 
6. last but not least, i have NOT been deserted by this forum so i am trying almost everything you all throw at me
 
 
 

i will post all details tonight for the Dell Persion. i did send you what i know via PM! - thanks

i will talk with dell tonight also

> Thanks to everyone for your input/support.. after talking im PM in back and doing leg work I have plan of action ! < RCA: anytime your ready !!

 let me read your post a few times 1st

RCA: update time !! http://www.dell.com/support/drivers/us/en/19 Intel-Driver Intel_Chipset-Software-Insta_A02_R293337.exe (2MB) Recommended 4/5/2011 9.2.0.1019, A02 do that reboot your system !!