Quote:

See, John and John, here is where I get lost. Now we add MidiYoke to the equation. Coyote, Leopard, Panther, Armadillo... whatever.... I plug my M-Audio into my USB port and I hit play. I don't use soft synths, I don't add this 3rd party software or run that widget.... when I need supplemental instruments I play them into my computer myself through my MIDI interface, and record them as audio tracks into RB. (Mainly so I don't forget how to actually play since this software is so good it plays better than I can.)

Now here's another aspect. I call my M-Audio my MIDI Interface. What I consider my sound card is that RealTek stuff that is built onto the motherboard. Back in the day I had a Soundblaster AWE Gold 64 that made the Windows beeps and blips and played radio stations and that is what I considered to be a "sound card". Anything I can plug MIDI cables into I call a MIDI interface, and I am getting lost in some of these conversations because of terminology. Yes, sound comes through that M-Audio MIDI Interface, so I guess that makes it my "sound card" as well as my MIDI interface.

So now, for my specific application, my big concern is that the mixer does not respond when I slide the sliders. It takes a good 4 beats. Silvertones John told me about buffer size, and I have not tried changing that yet. IN the past, however, someone told me that if I changed to ASIO drivers, that latency issue would go away with the driver change, and it did for the 5 minutes the ASIO driver worked. Now also know that the M-Audio site says:


Q: When I launch my recording application, I get an error message indicating The ASIO sample rate is not supported . . . Please check your sync settings in the Control Panel. How do I resolve this?

(That is the error I get as well. How do I change the ASIO sample rate to one that IS supported? This driver comes from THEIR web site for THEIR hardware, and says it is not supported.)

A: There is currently a known issue with the device drivres for M-Audio USB interfaces that affects multi-client operation. This error can occur when launching an ASIO application and another application, or in some cases the Windows operating system, is trying to access the device. If you are receiving this error message, quit your recording application, then go to the Windows Control Panel and select your computer's built-in sound card as the default playback and recording device. This will allow you to use your M-Audio device with your ASIO application.

When you would like to use your M-Audio device for non-ASIO applications (e.g. iTunes, Internet Audio, Windows Media Player, etc), you can set your M-Audio device as the default playback device from the WIndows Sound Control Panel.

Now, reading that, I have 2 issues.

1 is that when posters here say "control panel", do they mean WINDOWS control panel or the BIAB/RT audio setup "control panel"?

2 is that under no circumstance would I ever use the computer's built in sound card for anything.

I really don't see why we would ever be required to be switching back and forth. We should be able to set it one way or the other and have it function universally.

What am I not understanding here? All I want to do is have the mixer respond to the gradual changes to the piano or guitar track as I slide the slider, not 4 beats later. I can't mix with a 4 beat gap. I HOPE Silvertones suggestion about the buffers will resolve it but it is really difficult to deal with that latent response.



The midiyoke thing is a trick. A lot of people only have VSTi/DXi synths. In the output drivers all that is listed then is either:
1. MidiMapper
2. MS wav table synth
3. none
You are forced to choose one of these even if it's not really being used. This is what seems to mess up the ASIO. By installing a virtual midi driver like midiyoke it gives you a fourth choice. By choosing this fourth option it seems to let ASIO work better.

John
ESI Gigaport HD+
Lenovo Turion II /4 Gig Ram/ Win7x64 be
15.6" Monitor
"The only Band is a Real Band"
www.wintertexaninfo.com/BANDS/JohnnyD.php