Ezdrummer 2 2.1.4 crashes with Line6 Asio driver (version 4.2.7.6)

[Gregory BOURGON]

Hi !

I meet a problem with my Toneport UX2 (the one with the black face). I’m under Windows 10 64 bits Version 1607. My Toneport uses the drivers version 4.2.7.6.

When I launch Ezdrummer 2 (Standalone version 2.1.4), the soft crashes. I re-launch it, then go to the audio options. In Asio Mode, i don’t have the “Line6 UX2 Asio” option. I only have the “Generic Low latency Asio driver”.

I tried to uninstall the UX2 drivers and re install them. The “Line6 UX2” option appears in the Ezdrummer 2 audio options but when i tried to apply the option, it crashed again. After returning to the audio options, the “Line6 UX2” doesn’t appear any more.

Does anyone else have the same problem ?

Topic

[John]

Hi,

do I understand correctly that you can launch EZdrummer 2.1.4 without any problems if you use other drivers than your Line6 UX2 ASIO?

John Rammelt - Toontrack
Technical Advisor

[Olof Hermansson]

Yes we have seen other reports of crashes in Line6 (and Focusrite) ASIO drivers (64-bit). Please report to the driver manufacturer.

Olof Hermansson - Toontrack
Coder

[Patrik Wall]

It seems to be driver related unfortunately, focusrite has the same issue on some audio interfaces.

I found this thread on the topic, maybe there are solutions out there if you continue searching the line6 forum.
http://line6.com/support/topic/14979-ux2-with-windows-10-pro-64-bit/

Im sorry we cannot offer any help but this one is out of our hands =/

Bass player in swedish thrash metal band Defiatory
www.defiatory.se

Coder at Toontrack
www.toontrack.com

[Gregory BOURGON]

There is something strange. I made again a few tests. I ran Kontakt and it works perfectly with the Line6 Asio driver. Also, in Cubase 8.5.20, i can select the Line6 Asio driver and everything works, even Ezdrummer 2 and Ezmix. It seems that the problem comes from the standalone versions, no ?

[Olof Hermansson]

It can seem that way but we have tried many differents builds, and insignificant changes in the code or projects could change whether a crash occurred or not. The cause could be some race condition or uninitialized variables, so you get sort of random results. These crashes always occur in the driver code.

We’ve seen no report of crashes like this in the 32-bit standalone, BTW, so maybe you can use that for now.

Olof Hermansson - Toontrack
Coder

[Gregory BOURGON]

Ok,

thanks very much for your help !

[Author]

Replies