Can't help you much even though I've used Sonar X3 for many years, and Cakewalk Pro from 20-yrs ago. But I have had numerous issues with instruments staying connected, not to mention several other problems.
So I installed the Cubase and other software that came with the MoXF, and am struggling through learning that. (Did I mention I am NOT a programmer?) I've had a breakthrough this week in getting the Cubase VSTs & MoX to work together and have made a direct-to-audio recording without significant problems. Next step is trying to integrate another keyboard through my AI.
Hopefully, someone else here has figured out Sonar instrument settings, maybe even the MoX Remote Editor, which is pretty cool.
I'm considering going back into Sonar and ensuring all my songs are saved as General MIDI (1 or 2?) and possibly using Cubase to make future edits.

Do you have a MOX instrument definition for Sonar? If I can find that, I'm going to give Sonar another shot. Not sure that Cubase is any better.

The moXF VSTi will not integrate properly into any other host other than Cubase. This limitation is built into the VSTi by Yamaha / Cubase.
Other than that it should function as well as any other external synth using the std midi type tracks.

@ Jelani

So I've downloaded the latest drivers from the Yamaha website, and I've restarted both my Windows 10 machine and the MOXF8 unit itself. I've got "Yamaha MOXF8" selected as my input and output drivers for recording and playback, but when I arm my tracks to record, I don't hear anything or see any of the waveforms, even though the DAW level lights are lighting up on the keyboard itself. It feels like there's some setting that I'm missing. Under the "USB I/O" tab in the Utility section of the keyboard screen (I was about to say interface... haha... VISUAL interface) I have "Mode" selected as "2StereoRec" ... but it seems like changing that setting doesn't make much of a difference.

Is there something else I'm missing here?

Windows 10 machine running Sonar Platinum, connected via USB cable. Not sure what other spec info you might need.

I'm not a Sonar user so I can't give you specific places to go (other than the Sonar Manual) but setup of DAWs takes the same form in all programs. You want to ensure the Yamaha Steinberg USB driver for Windows is selected as your audio Device driver. This is usually found under Options.
The MOXF outputs audio on two Stereo USB buses. USB 1/2 default to the A/D input, while USB 3/4 are the default for the Synth sounds. You need to know this or you may be looking down the wrong pipe for the water. The MOXF synth sounds by default use the second pair of stereo outputs, outputs 3/4!

Do you see where you can select to receive audio via USB 3/4? This is usually setup on the Audio Track's setup window. That's what you want to look for. The MOXF and its meter show it is sending audio - just make the appropriate setup to receive it. Create a stereo Audio Track, and route USB 3/4 to that track. Audio from the computer will return to the MOXF through the DAW LEVEL Fader on the front panel.

@ Ted

Can't help you much even though I've used Sonar X3 for many years, and Cakewalk Pro from 20-yrs ago. But I have had numerous issues with instruments staying connected, not to mention several other problems.
So I installed the Cubase and other software that came with the MoXF, and am struggling through learning that. (Did I mention I am NOT a programmer?) I've had a breakthrough this week in getting the Cubase VSTs & MoX to work together and have made a direct-to-audio recording without significant problems. Next step is trying to integrate another keyboard through my AI.
Hopefully, someone else here has figured out Sonar instrument settings, maybe even the MoX Remote Editor, which is pretty cool.
I'm considering going back into Sonar and ensuring all my songs are saved as General MIDI (1 or 2?) and possibly using Cubase to make future edits.

You don't have to be a programmer to setup audio and MIDI in a computer. You need to know just two things: one is there are going to several recording situations you will use, over and over again. Record, overdub, and mixdown- expect to learn the difference and what changes in the setup. Every DAW, including Sonar and Cubase allow you to STORE your setup, so that once you get things set you never have to do this again. You simply recall your setup. If you find that you have to redo your initial setup every time... it's really your fault. Follow instructions through to where you are confident you've Stored your setup!!!

Like setting up your computer to play a video game, once setup, it just runs from then on. Same theory applies!!!

Take your time. Learn to read an installation and setup guide (and here is the key) WITHOUT skipping a step... and try to understand WHY you are making a setting. It helps complete the dots.

Forget crutches like instrument definitions until you are confident on the basics of setup.

@ Peter

The moXF VSTi will not integrate properly into any other host other than Cubase. This limitation is built into the VSTi by Yamaha / Cubase.
Other than that it should function as well as any other external synth using the std midi type tracks.

The MOXF EDITOR Standalone/VST can run in any DAW that is VST3 compatible. Of course, naturally it works in Cubase... Steinberg invented VST protocol. But any DAW that is updated to run VST3 protocol can run the Editor fully integrated INSIDE the DAW.

If your DAW is not VST3 compatible, you simply launch it and run it "Standalone" right next to your DAW - and get this: the only difference is you have to SAVE a separate file when you finish. (Instead of the Editor file being bundled with the DAW data)... not really a big deal.

You do not have to change your DAW, use whichever you are comfortable with. The only difference is in "housekeeping"... you'll need to save your MOXF Editor file separately.

Just FYI. That "limitation" (sic) is also brought to you but Yamaha 🙂

@Bad Mister.
The stand alone editor is a windows executable and does not run in a DAW but in it's own separate process.

The MOXF6_MOXF8.vst3 is a Windows dynamic link library that runs in the DAW process using the LoadLibrary API.

It has nothing to do with VST3 compatible. I have two vst3 compatible DAWs and a VST SDK construction kit and NONE of them can use port 1 as it is not available in the VST (blocked)
If the host process does not conform the one of the security strings the VST will ** NOT function* correctly as Port 1 is blocked by design.
You cannot send MIDI note / controller data to the VST other than control system / sysex data on port 4.
Contact Yamaha if you doubt it!

The security strings in the MOXF6_MOXF8.vst3 DLL file are at 8AF34 and cover 7 cubase products.

Can you give me the name of a single DAW or hosting product where the MOXF6_MOXF8.vst3 exposes Port 1 as it does in cubase????

@ Jelani
I can give you the ins file for moXF if you require it.

@Peter
Sorry, you are having issues with the Editor. The Standalone does not run inside Any DAW, It is called Standalone because it runs outside of the non-VST3 DAW. If your particular DAW is not VST3 compatible, you can launch the Editor as a *separate* application, thus the term stand alone.

VST3 compatible DAWs it run within the program.

Contact Yamaha if you doubt it!

(I'll contact Yamaha next time I get to a mirror) 🙂

Sorry if you misunderstood what I said but please re-read the post. The program when installed, installs two versions, one that is full *VST* capable, the other is an executable *standalone* version.

@ Bad Mister

I see you had posted an ins file in a dropbox, but it is no longer valid, From Feb of this yr.

I have never used that stuff, not a techie, just an old keyboard player going thru changes

I have always been a ROLAND user until the FA08 I had gotten was incapable of playing a midi file without dropping tracks in performance

I now have a Yamaha MOXf8, and I am going crazy using Sonar Artist, trying to figure out how to get instrument definitions happening.
It has 3 preset banks for the MOTIF, and i can get no help from Cakewalk, Sonar, Yamaha....
I'm trying to get this thing up and running ASAP as we have gigs, and the OLD XP80 is in the process of dying... I'd had to go back to using that after returning the FA08.

If you can help me in anyway, I would be so grateful. My wife says she might be able to figure out this dropbox thing with a little instruction.

Hi Terry,
I don't recall dropboxing that file... they are only as useful for the Preset banks because your User banks will not be represented in the definition. And when creating your own music, often customizing (editing) of a sound is necessary. If you lock your selections to just the Presets, they will be recalled just as the factory set them. You also cannot take advantage of the MIX VOICE feature, which lets you store custom edits locally within the Song/Pattern Mixing setup.

If you use the "Yamaha MOXF6/MOXF8 Editor" instead, as your interface to select sounds for use in the DAW, it will always be updated to represent all the Voices, both Preset and User (even MixVoices), currently in your MOXF. I think if you always worked with Instrument Definitions, it is worth it to try this new method for selecting/storing/recalling sounds, the MOXF Editor.

When addressing the MOXF (hardware), this Editor is a graphic interface that, when ONLINE, is a 1:1 representative of the MOXF hardware on your computer. Changing something on the graphic interface is the same as changing it on the hardware and vice versa, anything you change on the MOXF hardware itself instantaneously happens in this software editor.

Think of it as not only a listing of all available sounds, but is instantly and always up-to-date with what's in your MOXF... with access to every parameter, and every parameter setting. So instead of just recalling a Voice for a Part from a list (which is all the instrument def offers), you then can adjust its volume, pan position, tune it, note limit it, change and adjust the effects assigned to it, adjust the filter setting, envelope, etc., etc., etc., and it stores and will recall any changes you make to that sound!

Hopefully, once working with it a few times, you'll agree that going back to the Instrument Definition workflow, is less satisfying.

Just a suggestion. Are you using the EDITOR yet? We can help you get started.