Slow Performance in VDMX when using AMD FirePro D500

Steps causing the bug to occur

  1. Run VDMX
  2. Choose a simple ISF Generator - Runs at 60fps
  3. Apply the mxfx_SphereDisplace_04 VuoFX - immediately drops to 20 fps

Have you found a workaround?

This plugin was developed on a mobile GPU. NVIDIA GeForce GT 750M, and runs optimally on that GPU.

Other notes

  • Vuo version: 1.1.1
  • macOS version: OS X 10.11
  • How severely does this bug affect you? It prevents me from using Vuo at all.

I have stopped development on most of my plugins, as I’m unsure if they’ll run on this hardware efficiently.

mxfx_SphereDisplace_04.vuo (5.87 KB)



Thanks for reporting this problem.

We were able to reproduce the problem on an ATI Radeon 7970, which uses the same driver as the AMD FirePro D500. Although the composition ran at 60 fps from Vuo Editor, it visibly slowed down when run in VDMX. (How did you get VDMX to show the framerate?)

With a simple passthrough composition (published input → Share Value → published output), it slowed down by about the same amount.

So it looks like the slow part is transferring the images between VDMX and Vuo (using IOSurface) with the ATI Radeon 7970 and AMD FirePro D500.

We probably can’t do anything about the slowness per IOSurface, since it’s most likely a driver bug, but we can try to cut down on the number of IOSurfaces.

Most unfortunate. All of these driver issues on Apple’s end are becoming a disaster quickly. To show FPS in VDMX you need a preview plugin, and enable the fps in the UI Inspector for the preview plugin. Thanks for looking into it.

Hey @jstrecker these ATI bugs and Nvidia’s new cards (and current GPU’s) are starting to make me sway towards Nvidia. Are these sort of bugs present on Nvidia GPU’s?

Although Apple officially support ATI for GPU’s currently, Nvidia has a well maintained OS X Web Driver which may be useful for Vuo Power Users, (ie: running large concert shows etc).

@alexmitchellmus, we’ve encountered driver bugs with NVIDIA, too. Since some of our team’s own computers have NVIDIA GPUs (GeForce 9400M and GeForce GT 650M), we tend to catch those particular driver bugs sooner. At least for Vuo, the GeForce GT 650M performs nicely whereas the GeForce 9400M is pretty terrible, so I couldn’t make any generalizations about the NVIDIA brand.

@jstrecker. What driver errors should I be looking for so that I can have more information on my end?

@krezrock, I don’t know of anything you could look for. Usually the only symptom of a driver bug is something messed up with the graphics on a certain machine — either it’s slow or it doesn’t draw right. For slowness, OpenGL Profiler can tell if it’s a software fallback or not. If not, the process is pretty much trial and error to pinpoint the problem and discover a workaround. (Though I’m not sure what we could try for this particular bug, other than reducing the number of IOSurfaces.)

1 Like

@jstrecker, understood. thank you for the feedback. Seems like a deep rabbithole without a map. I’ll avoid protocols for now and work on standalone apps. I have another question. Is this bug re-producible when using this Vuo composition in Coge?