Early adopters beware of Cubase 5/PA2Xpro
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Early adopters beware of Cubase 5/PA2Xpro
I've found a rather nasty bug in C5. The application won't launch if my Korg PA2xpro is connected via USB. Everytime the Korg is powered on and I then start C5, it crashes with an error signature of "Modname d52asio.dll Modver 2.1.0.0. Offset 0000397b.
This is repeatable ever time. If I remove the Korg USB, then C5 starts normally. This problem never existed with C4 and SX3 which I still use. I've reinstalled C5 and the Korg usb midi driver but the result is always the same. The workaround is that I will have to resort to using midi cables again until it's fixed. I'm pretty sure this isn't a problem with Korg but I thought I'd just make you guys aware.
Cheers
Simon
This is repeatable ever time. If I remove the Korg USB, then C5 starts normally. This problem never existed with C4 and SX3 which I still use. I've reinstalled C5 and the Korg usb midi driver but the result is always the same. The workaround is that I will have to resort to using midi cables again until it's fixed. I'm pretty sure this isn't a problem with Korg but I thought I'd just make you guys aware.
Cheers
Simon
- BasariStudios
- Approved Merchant
- Posts: 6510
- Joined: Sun May 29, 2005 4:56 am
- Location: NYC, USA
- Contact:
Then i'd have to give up on my PA800.
http://www.basaristudios.com
Cubase 8.5 Pro. Windows 7 X64. ASUS SaberTooth X99. Intel I7 5820K. ASUS GTX 960 Strix OC 2GB. 4x8 GB G.SKILL.
2 850 PRO 256GB SSDs. 1 850 EVO 1TB SSD. Acustica: Nebula Server 3 Ultimate, Murano, Magenta 3, Navy, Titanium.
Cubase 8.5 Pro. Windows 7 X64. ASUS SaberTooth X99. Intel I7 5820K. ASUS GTX 960 Strix OC 2GB. 4x8 GB G.SKILL.
2 850 PRO 256GB SSDs. 1 850 EVO 1TB SSD. Acustica: Nebula Server 3 Ultimate, Murano, Magenta 3, Navy, Titanium.
- Rob Sherratt
- Platinum Member
- Posts: 4590
- Joined: Mon Apr 16, 2007 1:49 pm
- Rob Sherratt
- Platinum Member
- Posts: 4590
- Joined: Mon Apr 16, 2007 1:49 pm
The Microsoft USb MIDI driver is a standard supported feature and if you plug the kcable in to your keyboard and the keyboard is generating MIDI clocks, then the USB driver should install automatically.
However with Windoze's ubiquity there are always "gotchas", and the thread below reveals that many people have been struggling, and there is a registry hack that seems to solve one particular issue prevalent on Core 2 Duo machines:
http://forums.techarena.in/windows-devi ... 577567.htm
The funny thing is that I have a Core 2 Duo desktop machine running the Microsoft USB Midi driver with no problems and my M3 on the other end. I never had to do any registry hacks. I de-installed the Korg USB MIDI driver after I experienced a number of crashes reporting a problem with that device driver, and the Microsoft one was auto-installed in its place as soon as I plugged the M3 into the other end of the cable (with MIDI clock master on the M3).
Best regards,
Rob
However with Windoze's ubiquity there are always "gotchas", and the thread below reveals that many people have been struggling, and there is a registry hack that seems to solve one particular issue prevalent on Core 2 Duo machines:
http://forums.techarena.in/windows-devi ... 577567.htm
The funny thing is that I have a Core 2 Duo desktop machine running the Microsoft USB Midi driver with no problems and my M3 on the other end. I never had to do any registry hacks. I de-installed the Korg USB MIDI driver after I experienced a number of crashes reporting a problem with that device driver, and the Microsoft one was auto-installed in its place as soon as I plugged the M3 into the other end of the cable (with MIDI clock master on the M3).
Best regards,
Rob
- Rob Sherratt
- Platinum Member
- Posts: 4590
- Joined: Mon Apr 16, 2007 1:49 pm