It's the worst problem to identify. An intermittent situation. I had problems using bluetooth with my computer and my new Peavey board on the channel. So I opted for USB connect to the channel (I could use either), and at first blush USB worked fine.

But though it first worked, it would drop out ... audio engine would kill itself randomly at various incomprehensible trigger points. I wouldn't do anything but play. It worked ... it works ... goodbye ... and then -- 

Well ... hello again ... moments later. 

My initial guess is it is a driver conflict hamstringing the program. I'm porting out through ASIO4all on Sonar, and that may be the issue ... as there might be inherent program conflict ... but why the "he loves me, he loves me not" behavior of Sonar? If it works, shouldn't it continue to work? What the flaky hello and goodbye?

X3 had no issue with USB connect and was rock solid ... never a disconnect ... although I was working then through a Peavey USB to XLR audio adapter and connecting via analog conversion of the Peavey unit (also using ASIO4all) ... but the program should do the same right to the new board w/ the USB inputs. 

It was extremely frustrating to try to work with the program live tonight. Once working, I expect it should continue to work and not cut in and out. Being in the middle of a song and having the program crap out is unacceptable.

As I said, it may be ASIO4all ... and I will experiment with direct porting to the board via Windows drivers ... but this is a straight out USB out of program to a board, and it really should not be as temperamental as it apparently is.

Any thoughts are warmly welcomed. 

Kev-

Audio engine is not engaging AT ALL using WDM drivers w/ USB audio out. It won't even turn on.

ASIO4all is finding the Peavey Mixer ... but should I engage those drivers as the ones to use in Platinum, they don't work.

The USB drivers DO work, but they aren't stable ... and continue to cut out.
 

WASAPI drivers are nothing but crackle. They work, but they crackle badly.
 

Repeat post ... oops.
 

When you say 'drop out' does audio stop altogether ? Does the Audio dropout dialogue come up ?
or does it momentarily glitch & keep playing ?
 
Does the CPU spike (got to the red) when this happens ?
does the counter pause when this happens ?
 
Chuck

I hate to say it, man... and I think I alluded to it in your blutooth thread, but you may want to consider a DAW that's a little less resource heavy/more known to be stable in live situations than Sonar.
 
Reaper is extremely low footprint and inexpensive. Ableton Live is pretty much designed to work... well... live.
 
I of course love my Sonar for all the crud it lets me do sitting all by my lonesome in a dark room happily writing/noodling away. I really don't think I would trust it in a chaotic live scenario especially using questionable hardware, hookups and drivers... which seems to be what's going on here.
 
That said, some people around here apparently make it happen BUT they are vigilant about using solid, ASIO compliant devices and go out of their way to really cover any and all possible problematic scenarios. Even then there seems to be issues.
 
Actually IIRC user Flybertlb (sorry... can't recall his exact handle) does this type of live thing. Maybe he'll stop by or you can check out some of his threads (where he goes into elaborate detail on his setup).
 
Cheers.

Synaptic
When you say 'drop out' does audio stop altogether ? Does the Audio dropout dialogue come up ?
or does it momentarily glitch & keep playing ?
 
Does the CPU spike (got to the red) when this happens ?
does the counter pause when this happens ?
 
Chuck

The audio engine in Sonar turns itself off, and after a couple moments, back on. No spike. No dialogue box.

I was just experimenting with the rig and the various driver configurations I could run ... and though WDM works in Sonar w/ the Realtek drivers (preloaded on the laptop), the audio engine won't even turn on when set to USB.

ASIO works when USB device is selected, but not when the Peavey Mixer is engaged through ASIO4all. The engine doesn't shut itself off, it just doesn't do anything. In fact, even turning the Peavey Mixer drivers "on" in ASIO4all kills the USB device drivers. Again, the audio engine in Sonar stays on, but nothing plays.

Wasapi will keep the audio engine on, but slide latency and buffers around doesn't rid the crackle.

I've not yet tried MME ... for I DO know how to make things work, but now I'm puzzled by the random turning off and on of the audio engine in Sonar when ASIO is engaged.

As one might guess, in a live performance situation, going dark on and off is not acceptable behavior. :D

To ask an obvious question..

Have you updated to the latest drivers and firmware for the Peavy and other devices inc your display driver.

Also try deleting AUD.INI.

Have you updated your motherboard chipset drivers and BIOS?

Try disabling arm record monitoring in Sonar preferences.

Temp disable your virus scanner.

Try it in a USB2 socket not USB3.

If that does not work I would roll back from Jamaica release, I have as I'm not impressed with the stability, it's not surprising considering this is a major release..

Before you do all this I would completely remove ASIO4ALL.