Skip to main content
Participant
January 26, 2017
Question

Has Audition changed the way it detects OpenGL since CC 2015 (8.0.0.192)?

  • January 26, 2017
  • 1 reply
  • 509 views

On my computer CC 2015.0 (8.0.0.192) works perfectly in every way that I need. But from CC 2015.1 onwards (including CC 2017) Audition crashes when attempting to import any video file. Also, VST/VST3 plugins that require OpenGL also immediately crashes Audition later than version 8.0.0.192, giving the message that my GPU does not support OpenGL 2.0 (which in fact it does). As said, in version 8.0.0.192 these problems do not exist and everything works perfectly.

I assume this is OpenGL driver related, so what has changed? Why does Audition suddenly no longer think that my computer supports OpenGL?

This topic has been closed for replies.

1 reply

ryclark
Participating Frequently
January 26, 2017

I must admit that I can't see where OpenGL should affect Audition in any way since it is purely to do with graphics support? As regard to VST plugins again I wasn't aware that some of them can make use of the GPU. What graphics card are you using?

It will probably need a Developers input to throw any light of this problem.

Participant
January 29, 2017

My GPU is an Intel HD Graphics 3000, which fully supports OpenGL version 3.1 and is running DirectX 12 and Direct3D 11.1 perfectly on my system.

The reason why I think this is GPU related is because the only error message Audition gave me specifically stated that the GPU does not support OpenGL 2.0.

Other CC 2017 software, like Premiere Pro and After Effects happily loads videos and runs the same plugin without any problems. It's only Audition CC 2017 and the updated CC 2015 version that fails.

Hope this helps.

SteveG_AudioMasters_
Community Expert
Community Expert
January 29, 2017

As I'm on a tablet at present I can't give you a direct link, but in the Audition FAQs there's one called 'Audition crashed - now what?' If you follow the instructions in it and send the results to audiobugs@adobe.com you should get a direct answer.