Hi gang, long time member of the old SCS forum (lost my username in the move :-( ) looking for some suggestions to solve a problem:

I have just updated to a new PC. I haven't used my Motu 828 Mk II in vegas pro for a long time: I was on Win 7 and VP 12 (not 13) when it was last used successfully. But I am now on VP13, Win10 with 16 Gb of ram and the same Motu 828 Mk II recently dusted off. The Motu drivers are recent, 10.0.12393.0 dated 15 July 2016.

Although the Motu Mk II inputs show up under the "Windows Classic Wave Driver" in Vegas Pro 13, any attempt to "Arm for Record" would result in nothing happening the first time (as if I didn't press Arm button), and the second time would result in a traditional Vegas "Low on memory" and then a warning the action had been aborted. (The system has 16Gb, with more than half free).

I cycled through all the other audio device types (Microsoft Direct Sound Mapper, etc) trying to replicate the problem. It did not replicate. I then went back to the muto inputs under Windows Classic Wave Driver and selected the Motu again, and now it will let me Arm, but the "line in" VU meter in Vegas is empty. And when I record, no "sound object" appears on the timeline (its not just silent, there's no object as the timeline advances).

The Motu Console program will change the bitrate on the device fine (so windows can see the unit, plus windows does its "found device" sound when I turn the Motu on). I did notice that after attempting a recording, the Muto gets flicked back to 44Khz instead of 48 that I am starting on: normally I need to change these manually through the Console program. There's also sound coming to the Muto - the VU meters give that away.

I have also noted I cannot make Vegas output sound to the Motu's headphones: selecting the Muto's headphones for the output device results in the motherboard's built-in sound card being used.

Any suggestions? I'd be grateful.
Entilza.