YamahaSynth.com Forums

This is the place to talk about all things related to Yamaha Synthesizers!
  1. thelittlegumnut
  2. MOTIFXF
  3. Wednesday, 27 January 2016
Specs (getting old... I'm pretty sure these are bare minimum specs) {

Everything is 64-bit! Including drivers, VST, everything.

Windows 7 Home Premium SP1
Intel Pentium Dual-Core CPU E6700 @ 3.20 Ghz
4GB DDR3 RAM
MOTIF Editor VST 1.6.4
motif extension 1.1.1
Cubase 8.0.30

drivers:

Yamaha Steinberg USB driver 1.9.6
USB-MIDI driver 3.1.4.0

}

Scenario 1:

I have a Cubase 8 Pro project containing 13 MIDI tracks filled with a bunch of MIDI notes and CC. Each routed out to the Motif XF VST - Midi In. I'm using USB-MIDI as usual, so there's no FW involved here. The messages go to my XF via USB port 1. The stereo-outs of the XF are plugged into my audio interface and the interface forwards the audio to the XF VST's stereo-out audio track for playback through my monitors.

Scenario 2:

I use the same project as above. I use the same 13 MIDI tracks. I manually route out the MIDI directly to the XF through USB port 1. I manually route the audio from the XF's stereo-outs to a new audio track for playback through my monitors. (It's worth noting that I completely remove the XF VST from the Instrument rack in Cubase)

--- --- --- --- --- --- --- --- --- ---

Both scenarios are fine when I'm simply playing back the project in Cubase, but when I export audio mixdown, things go a bit crazy with my CPU...

With scenario 1, I use Windows' resource monitor and notice that my CPU usage is oscillating between values such as %50-%60 and %95-%100. Sometimes, during the mixdown, I get an error simply stating that the mixdown can't be performed because my CPU was overloaded. This happens whenever Cubase's real-time VST meter breaks it's limit. The "average load" also in the VST meter indicates a very low amount. Probably about %5 of the bar is green. It's just the real-time meter that is constantly jumping from values much like the average load to values like %95, but only for a split second. It seems weird to me because this is all about 1 track. All of these weird spikes occurring for 1 track.

With scenario 2, I do the same thing and notice my CPU hover consistently at around %40-%50. I simply don't get any spikes and/or errors. It seems reasonable given the fact there's barely any audio to process. It's just 1 track. The "average load" isn't even visible, as if there's no load at all. The real-time performance meter is constantly at about %2. I can add insert effects like crazy and I see barely any increase in it's value.

What's even more strange is that with scenario 2, I have the buffer settings for my interface at 64 samples. Whereas for scenario 1, I have the buffers set to 512 samples. It seems backwards that scenario 2 would perform better.

Are there any known issues with the XF VST? Is it just my specs? Perhaps the XF VST consumes more processing time+power than I expected it to?
Responses (6)
Bad Mister
Yamaha
Accepted Answer Pending Moderation
Thank you for your question... We will look into this.

First a few notes... There is a update for Cubase Pro 8 (8.0.35)
The Motif XF does not use the Yamaha Steinberg USB driver 1.9.6 - (it will do no harm, but just FYI, your Motif is not one of the products that uses this driver which sends Midi and Audio through USB, like the MOXF, MX, UR22/UR44, etc.,). Your XF is using the Yamaha USB-MIDI driver for MIDI
Make sure you're set to output the XF's audio return to the ports of your audio interface. That is, not only should the analog outputs of the XF connect to two jacks on the physical interface, you must "return" the audio via the MOTIF XF VST (Editor). Here's how:

Scenario 1:
Please go to FILE on the Motif XF Editor VST
Select VSTi SETUP
make sure you have the "Motif XF OUT" is connected to the two ports of your audio interface, for Left and Right "Audio Return Ports"... To DAW "Motif XF 1"

This will ensure you MIDI Tracks will trigger the XF, and that the XF will return audio to your audio interface... And this audio can be seen returning to the Motif XF VST *audio lane* in Cubase. This allows you to use EXPORT AUDIO MIXDOWN

Please note: we realize you may already be doing this, but that is not clear from your post (that you are). If scenario 1 is properly working, there is no need for scenario 2. So let us know.

if you are returning properly, and getting these results, then indeed there is some kind of problem or bottleneck in the VST3 routing and acquisition of data... VST3 should only use processing power when it is actually processing signal. I don't have a Windows 7 computer (any longer) to make an actual test, but in the meantime, let us know about your VSTi SETUP page, and we'll see if we can get someone to test this setup.
  1. more than a month ago
  2. MOTIFXF
  3. # 1
Accepted Answer Pending Moderation
Just for that extra bit of clarification, scenario 1 and scenario 2 technically both function. Everything is routed correctly and mixing down actually works. It's just that with scenario 1 I'm getting all the spikes and even CPU overloads to the point where the mixdown won't complete and will issue an error message halfway through. The error message refers to the "CPU overload during mixdown".

As for my VSTi setup page, I have MOTIF XF 1 = UR22 left | UR22 right
The UR22 is my audio interface and the Motif's left and right stereo outputs are plugged into the corresponding UR22 TRS/TS inputs. Hence why I have the Yamaha Steinberg usb driver 1.9.6.

It's worth mentioning that my CPU does in fact overload occasionally when running the VST in scenario 1 (the VST meter lights up red at the end) however it doesn't issue an error when playing back normally. Instead, I'll usually get a loud buzzing or beeping while all the audio cuts out for a few seconds. The strange behaviour is the spikes, because the average load is incredibly low and most of the time, the real-time performance is as well.

I don't understand why scenario 2 is so much faster because with my current setup, all the VST does is transfer MIDI and bulk data.

EDIT: I also updated Cubase 8 pro to 8.0.35 as of a few hours ago.
  1. more than a month ago
  2. MOTIFXF
  3. # 2
Bad Mister
Yamaha
Accepted Answer Pending Moderation
Thanks for the additional information. I will pass it along.

Okay, I must have missed that you were using a UR22. That will factor into this, as well.
Is anything connected via MIDI to the UR22? If so, does it have a clock?
  1. more than a month ago
  2. MOTIFXF
  3. # 3
Accepted Answer Pending Moderation
Nothing is connected via MIDI to the UR22.

A side note I guess is that I have the Motif set up to receive MIDI clock from Cubase via my USB-MIDI cable port 1. That's it.
  1. more than a month ago
  2. MOTIFXF
  3. # 4
Accepted Answer Pending Moderation
I have an update after further testing. I went into the VST settings section in my device setup. Upon switching off ASIO-Guard as well as Multi-Processing, Almost all real-time peaks were gone. Coupled with a higher sample buffer, and it's where I would expect it. There's no longer a significant difference between the two scenarios. Apologies for any inconvenience.
  1. more than a month ago
  2. MOTIFXF
  3. # 5
Bad Mister
Yamaha
Accepted Answer Pending Moderation
Good to know it was a setting. Thanks for the follow up.
  1. more than a month ago
  2. MOTIFXF
  3. # 6
  • Page :
  • 1


There are no replies made for this post yet.
Be one of the first to reply to this post!
2021 © Yamaha Corporation of America and Yamaha Corporation. All rights reserved.