Yamaha ESP 3 VST - works fine after reboot

Anyone try the new Yamaha ESP 3.0 VST plug-in in Gig Performer 5? It crashes the moment I try and change a patch. Just curious if anyone else is seeing the same thing or if it’s something I have to tinker with.

Can you upload the crash report please (compress it first)

Thanks, I did upload it when it requested, but I uploaded another with my email and how to recreate.

O, I mean upload it to this forum.

fe55296b-be5f-4836-a1da-71bd59dcf42f.zip (62.2 KB)

Thanks, we will investigate

1 Like

Well, guess what, it works fine after a reboot – I shoulda known! :slight_smile:

The crash did occur inside the Montage plugin so there’s no guarantee it won’t happen again.

Thanks for confirming. Probably won’t be using it in a gig to say the least.

You should report it to Yamaha in case they’re listening

1 Like

Gosh… I was always thinking to buy Montage M8X, leave it at home, and play live with ESP.
It doesn’t seem a suitable path yet…
It is so expensive, it must be perfect.
Was this case of problems on a Mac or on a PC?

PC in my case, so to be fair it might be a lot better on Mac — my PC is admittedly pretty dirty, has OneDrive on it (although I had it turned off) which is known to cause problems like this. But yes, I thought to do the same and have the best of both worlds. It’s a pretty big resource hog as well and I frequently get CPU hits at 128 samples/44.1khz. Never do on anything else.

I read somewhere that Yamaha - Steinberg developers start programming on windows and then port to Mac.
Someone wrote that ESP on windows runs better than on Mac for that reason.
Maybe I got this info from the YouTube Channel named Scott’s Synth Stuff.

Working pretty well for me other than a couple of issues (im pretty sure its all associated with the plugin itself).

  1. High CPU use. This is about the most CPU intensive sample playback unit i own. This uses more CPU cycles than Diva or Serum. That said it appears to be stable during the high usage so no pops, clicks or CPU spikes. My guess is with it being fairly new in VST world, it is unoptomized.

  2. User presets that uses user samples, fail to load after saving and reloading projects, which is a shame because it has one of my favorite string pateches for playing live.

  3. Havent thought of elegant way to utilize Super Knob with Gig Performer but this might be more me because the super knob is non automatable and must be done via midi cc. Not sure the best way to handle.

Great sounds.

i think if they made this a plugin for purchase and made its GUI a bit more friendlier, this would be a knock out the park.

Closest competition is the Korg V Collection which is more powerful on the synth front, but somewhat dated on the sample side of things.

I heard Halion Sonic is supposed to be their VST equivalent with a better Fm engine, and Analog Engine than the Montage M. Although i have no idea of the Sample patches compared to a Montage.

Halion has a fantastic FM-X engine.
When I got my first MODX I steered clear of the FM side. In my head it was DX7 stuff and ive done that and moved on. One day I was going through some warm pads and stings etc and realised i was hearing FM-X. Really surprised me at how far FM has come along.

  1. Map widgets to CC parameters of a MIDI In block connected to the ESP
  2. Complain to Yahama for not making that superknob host automatable

By the way, what does the superknob actually do?

I think Super knob can control multiple parameters ccs at the same time In different directions and different amounts.

So you should be able to control 128 parameters at the same time in this way. ( By assigning them to one knob.)

It sort of brings them all together.

Also not sure if this is because I am running an m4 computer, but I don’t have much problems with the ESP plugin. I use it live.

Do agree that it uses a lot of resources but I can push it much harder with m4.

So no different than linking multiple widgets together and using their individual scaling curves.