Byron Dickens

Actually, you need to work on your reading comprehension. That's not anything CLOSE to what I or anyone else said. No one said anything about CbB being incompatible with ASIO either. That is the preferred driver mode.

? That's good news! Glad you got it all working.

It might not. You might just have to deal with it. My Korg X3 is too old and too slow for that to work. Your Ensoniq is even older.

Midi Ox did not work at all for me.

Try Send SX. I had similar trouble with my Korg X3. https://www.bome.com/products/sendsx

I stopped bothering with it quite a while ago. It's too bad it hasn't been maintained. I used to use it to mock up guide tracks for myself to record the real parts to.

I had nothing but problems with ASIO4ALL. I've seen so many others have extensive problems. I never seem to see the same issues raised by people using real ASIO drivers. ASIO4ALL is just a wrapper for the WDM driver that fools your system into thinking it is an ASIO driver. WASAPI is superior to WDM so even just ditching ASIO4ALL and using WASAPI is better. Therefore ASIO4ALL is redundant at best. The best choice is ASIO because it is purpose designed for professional multitrack audio. You set the Focusrite up as your audio device and run the audio output from the keyboard into it while using the MIDI I/O from the keyboard to record MIDI into CbB and to let CbB control the keyboard. All the more reason to RTFM. I am only any good at the technical stuff not because I am so much smarter than anyone else but because I read the documentation and closely follow the instructions. In my former life, I was often able to fix cars - especially electrical, electronic and driveability issues - that no one else could because I would thoroughly read the service literature FIRST, before even getting started, rather than only resorting to it after I had gotten in over my head. That is a habit I developed early and have carried over.

Use another VSTi.

No, it is not.

I guess it wasn't that important....

Presonus supplies their own proper ASIO driver. Using ASIO4ALL with that is just ... Redundant.

I get that. I don't have money to throw around either. $100 is an amount I have to think about. Heck, $50 is an amount I have a think about. But in this case, not for very long when it will instantly solve 99% of my audio troubles and I can get on with making music. Its a no-brainer for me. I am too, but I won't let that be an excuse for substandard equipment. It doesn't have to be top of the line, but it does have to be quality. If it works for you, great. Even if I was working 100% in the box with only VSTis and loops, I'd still get a proper audio interface because 1) it's just simpler 2) sounds better because the converters are better and the onboard chips tend to be poorly insulated from electrical noise and 3) I want to mix on decent studio monitors; computer multimedia speakers won't cut it. They are not accurate. For mixing you really want speakers that are accurate, not that sound good. Decent speakers don't come in a pair with one 1/8" stereo plug. The OP mentioned his Roland FA, which is a very good multi-tembral workstation. I can only assume that he's wanting to use the sounds out of that. I know I would. So he's not working in the box. He's recording external audio. Which brings us back to a real audio interface with real drivers for best results. The reason why I emphasize that is because just the other day somebody was having problems with his Focusrite interface. He had no idea there was an ASIO driver for it. He didn't know because he hadn't followed the instructions. The instructions that were in the box. If he had followed the instructions, step three is download and install the software.

If a man says something in a forrest but there isn't a woman around to hear him, is he still wrong?

That might be a good place to start.

Only disagreement I have is that if you don't have an audio interface that supports ASIO, you need to get one. Stay away from ASIO4ALL. It tends to be problematic

Audio and MIDI drivers are totally unrelated. A real audio interface will solve this.

Only disagreement I have is that if you don't have an audio interface that supports ASIO, you need to get one. Stay away from ASIO4ALL. It tends to be problematic. I would also stay away from hardware instruments and stay with software until you get a solid handle on the basics first.

Need some information about your system such as processor, RAM, what audio interface, etc but I would try rebooting first. If you don't have a dedicated audio interface with proper ASIO drivers, you should seriously consider getting one. In the meantime, switch driver mode to WASAPI.

What do you mean "not a deal?" Spitfire's Originals are so good they'd be a bargain at twice the price.

I think you are confused. Its a keyboard, not an audio interface. ASIO is an audio interface driver. Second time: what audio interface do you have?

https://help.uaudio.com/hc/en-us

The Apollo 8P is a soundcard. UA doesn't have an ASIO driver?

I don't see how anything in my post connotes anger or antagonism. Its just the straight, unadulterated truth. If you choose to get upset because don't want to hear it, I can't help that. I say what I say because I've been down that road. My advice is not geared towards " making things work" with kludges, workarounds and half measures. Nor is it geared towards massaging people's feelings and encouraging them to continue suboptimal solutions. It's geared towards making things easy. I don't like banging my head on the wall and tearing my hair out. When I put together my current system a number of years ago, one of the things I did was buy a proper audio interface with a proper ASIO driver. And set it up FOLLOWING THE INSTRUCTIONS IN THE MANUFACTURER'S DOCUMENTATION. How many posts from me (or others like me) have you seen about "no sound," crackles, latency, sync issues, etc? EXACTLY!

I hear ya. I say what I say because I've been down that road and it is one major league PITA when that upgrade finally forces itself....