Hmmm...It would help to figure out what you are trying to accomplish here. I rarely use bulk voice dumps any more. With there MOXF8 I use the editor and recall everything in there on a per project basis. I also save voices locally in MOXF as well as "all" files.

Is there a reason why you want to use sysex?

Sysex is something that is transmitted and received, not something that is stored with a Voice or Performance. You could recall a sysex string in the MOXF sequencer or from Cubase.

Thank you Blake,

I also save voice in "all" file (X6A) . But loaded this kind of file is very long.

It is why, when I only need 2 or 3 user voices for my song, I would prefer to use sysex data.

Also I use an old TG77 and it is the easiest way to load voices. TG77 has no USB interface and can not load file.
So, in Cubase I record sysex data that I dump from my TG77.

On my TG77, it is easy to send sysex to :
- select a user bank/path
- send voice data
- send a store command.

With MOXf, I can send sysex data to load mixing data in song mode and store it.
I can record in Cubase voice dump.

I can retransmit this voice data but I can't find sysex to send a store command.

May be it is not possible on this synth.

It is possible with this synth... In the years since 1990 (when the TG77 walked the earth) much innovation has occurred so that users would not have to manually manage such data.

The “Yamaha MOXF6/MOXF8 Editor Standalone/VST” is designed to capture/save/restore your MOXF setup automatically when you SAVE your DAW File. It allows you to run the MOXF as a VSTi within a compatible DAW... this means not only can you process your MOXF with plug-in Effects, you’ll be able to use Cubase features like FREEZE, RENDER IN PLACE and EXPORT AUDIO MIXDOWN, and just like a VSTi, the sounds and settings are stored and restored automatically when next you open your Cubase Project.

I fondly remember manually making bulk dumps from each piece of gear and archiving them individually... but as mentioned that was back in the last century! lol

If you’re not using the Editor... this maybe a good reason to do so.

There are two separate message types... one restores the data to the instruments Edit Buffer— While in this Buffer, you can play it, Edit it, manipulate in any number of ways without having to overwrite any internal location. To make the data permanent, you simply press the [STORE] button on the MOXF... You can then direct it to the current or any other User Bank location.
The other type of message bulks the data directly into the instrument’s memory.

Are you using the Editor VST?
Is there some reason the data being in the Edit Buffer doesn’t work for you?
Simply press [STORE] ... when you want to write the data into the instrument’s memory...

Let us know.

Thank you Bad Mister.

Just to let you know, Data sent to Edit buffer work perfectly. But, as you mentionned, I need to manually press [STORE] button and select user bank on MOXF. this is these commands I would like to automate by transmitted some sysex data.

I will continue to search for an hidden sysex command to do it.

PS : I tried to use Yamaha VST editor, but like loaded x6a file, it is a very slow process.

I tried to use Yamaha VST editor, but like loaded x6a file, it is a very slow process.

No, neither process has to be a very slow process. You simply need to learn to streamline the process to suit your need.

Loading a new Song can take, literally, seconds when you know how to streamline the process.
Bulking a setup from the Editor can take, literally, seconds when you know how to streamline the process.

Extra Credit:
Loading data from an All Data File .X6A takes a long time because you are loading a ton of data that you actually don’t need. What you want to do is be efficient and load only the exact data you do need. An ALL file contains 384 User Voices, 256 User Performances, 128 Master Programs, plus all the Songs, Patterns, Arps, etc., etc. etc. probably all you need to load is the Song Mixing or Pattern Mixing Setup for the one composition you’re getting ready to play. Obviously, if you could load just that Song Setup, instead of waiting for all that stuff you’re not using to load, how does two seconds sound?

A Song and it’s Mixing Setup can literally load in two seconds (barring any User Sample Data). You can SAVE your Sequence data and it’s MIXING setup as ALL SONG (.X6S) or you can opt to Load just one Song from an ALL Data File. Doing so takes the “very slow” process and makes it darn near instantaneous.

If your MIDI data is playing back from Cubase, then loading the Song Mixing will be even faster.
Press [FILE]
Set TYPE = SONG
Highlight the File Name, it will ‘open’ and show a list of Song Titles
Execute the load. In less time than it took to read this, your Mixing is restored.

What you need to do to make this work... because it only loads the Song data (if any) and the Mixing Setup (the Voices in the 16 Parts of the Setup), not all 384 User Voices, if you have customized any Voices be sure to create Mix Voices - a Mix Voice is *stored* in the Song data. Therefore, you can avoid having to wait for all 384 of them to Load. When you load the single Song, it loads everything you need to make that Song play!

But believe it or not, there is an even faster way to automate all of this... if you are using Cubase Artist 8.5 to playback your Song data, why not have Cubase store and restore each MOXF Mixing Setup. Here’s the (streamlined) workflow for this. You will be able to open your Project File and tap the space bar to playback the file.

When properly setup and configured inside Cubase, the act of opening the Project File (.CPR) will automatically bulk the 16 Part Mixing Setup to your Keyboard. All you will need to do is open the file and tap the spacebar.

Running the MOXF6/MOXF8 Editor Standalone/VST as a VST, you can configure it to automatically restore just the “Current” Song Mixing Setup... the one you used to create the Project. Within the Editor VST you have three options... to restore the “Global” settings (basically, these are the Utility Mode settings), the “Current” settings, and “Voices”... well you don’t need the Global setting so deactivate that option, and you certainly don’t need all 384 Voices... so deactivate that option. You only want the “Current” — which refers to the Mixing Setup that was there when you SAVED the Project File.

You want to set the DIRECTION of the data to go FROM the computer TO the keyboard.
This means when you open the Project it will automatically restore the MIXING to the hardware... quick as a bunny!

If you have it set to restore all 384 Voices, that’s why you probably feel it takes a long time (because it does!). Streamline. Make the technology work for you.
By using Mixing Voices you do not have to worry about loading and manipulating any extra baggage.

If you need any assistance in configuring this let us know, we can fill in the details. Please trust me on this, it’s something we (Yamaha) have worked hard on... restoring the setup to the hardware in a convenient manner. The biggest advantage in integrating the Synthesizers Editor into the DAW is you wind up with all your data in one place. Just open the Cubase Project, and wham! You’re ready to play... the computer does all the heavy lifting.

Let us know....

Thanks for all these very useful informations.

It is easy to insert mixing data inside a Cubase project and transmit it to MOXF. And of course , transmitting this is very fast.

For a few user voices inside a Cubase Project, I will try again MOXF Editor VST. For sure, I did not configure it correctly as it always sent 384 voices. (it is why I said slow process)

Thank you again.