828 mk3 1400 Drivers Cubase Hangs, I know something...
Posted: Wed May 06, 2009 3:04 am
Hello MOTU Fans,
I recently bought a 828Mk3 and tested it with some standalone VST Instrumtents with the ASIO Driver. Firmware is 1.06 and Drivers are Version 3.6.8.1400. I am on Vista Home Premium 32Bit insalled on an Acer Aspire 5920G. The unit worked perfect on the internal Ricoh FW controller as well as an TI chipset equipped Expresscard FW controller. Yesterday I wanted to prepare a multitrack session for tomorrow with Cubase SX3. The thing hangend when initializing VST Connections. I could start Cubase without the interface, then switch it on, change the driver to MOTU Asio and as soon as Cubase wanted to "talk" to the Asio driver it crashed: AppHangB1, code 52e5. I did not found anything on google. I know the problem is known on this board. There is jus one thing I want to share: The same thing happened on a Windows XP IBM/Lenovo Notebook in Sonar 8 (Asio Driver). But I got the free Reaper DAW running with Asio Driver by checking "Ignore Asio reset messages (needed for some buggy drivers)"-checkbox in the Asio control panel of Reaper! Suddenly Reaper worked (it had the same issues until then)...
Does this help? I will send that report to MOTU as well!
Regards,
Martin
I recently bought a 828Mk3 and tested it with some standalone VST Instrumtents with the ASIO Driver. Firmware is 1.06 and Drivers are Version 3.6.8.1400. I am on Vista Home Premium 32Bit insalled on an Acer Aspire 5920G. The unit worked perfect on the internal Ricoh FW controller as well as an TI chipset equipped Expresscard FW controller. Yesterday I wanted to prepare a multitrack session for tomorrow with Cubase SX3. The thing hangend when initializing VST Connections. I could start Cubase without the interface, then switch it on, change the driver to MOTU Asio and as soon as Cubase wanted to "talk" to the Asio driver it crashed: AppHangB1, code 52e5. I did not found anything on google. I know the problem is known on this board. There is jus one thing I want to share: The same thing happened on a Windows XP IBM/Lenovo Notebook in Sonar 8 (Asio Driver). But I got the free Reaper DAW running with Asio Driver by checking "Ignore Asio reset messages (needed for some buggy drivers)"-checkbox in the Asio control panel of Reaper! Suddenly Reaper worked (it had the same issues until then)...
Does this help? I will send that report to MOTU as well!
Regards,
Martin