The only way that Audition can override the default is by having the session rate set at a different rate to the hardware setup default, and enabling record on a track (that's when it actually changes). What this probably means is that your default session rate in Audition is set at 48k. What you need to do is to start a new session, set the rate for this at 44.1k and then save this as the default session. Shouldn't happen any more after that! It certainly doesn't on my MOTU 8Pre, so there's a good chance that this will fix your 828 as well.
First thing I did was to start from scratch again. Full de-install, then re-install. Then checked my MOTU ASIO settings.
I then attempted to set the audio preference in the default session as you indicate. I didn't realize the potential for the default session to override the hardware settings. When I initially went to look at the Audio Hardware Setup, it was defaulted to Windows Sound. When I changed that to the MOTU ASIO driver, as I did before, I get the warning banner that says:
"Adobe Default Windows Sound Driver -- The audio input is not activated. Recording is not possible. Please check your input configuration."
Why is Adobe warning me about the default Windows Sound Driver when I have the MOTU ASIO driver loaded?? Anyway, I clicked OK to acknowledge that, made the changes to 441.khz, then saved the new default session using the Default menu selection. All seemed OK. I then selected the main Edit View so that I could check the Audio Hardware Setup there (versus the Multitrack View), and immediately got the same warning banner again. Clicking OK causes the Audio Hardware Setup applet to pop open - it wants me to fix it right now. In both the Edit View and Multitrack View tabs within that applet, the sample rate has again changed back to 48khz, even though I'd just saved it as 44.1khz in the default session a moment before. Clicking OK to acknowledge that causes the same warning banner per above to show again.
Therein lies the problem. Ideas?
Why is Adobe warning me about the default Windows Sound Driver when I have the MOTU ASIO driver loaded??
That's a very good question - I've never had it do that before. But there again, I won't let the OS use my MOTU for any system sounds at all, and it's completely deselected as an option for this within the OS settings. And if you have it available to the OS, then this will very often over-ride just about anything. So initially I'd be looking to make sure that to all intents and purposes it doesn't exist as far as the OS is concerned.
The other thing that may well be contributing to this is that you should also change the Edit View settings so that they also use the ASIO driver - otherwise it could be that that's overriding things.
>>>But there again, I won't let the OS use my MOTU for any system sounds at all, and it's completely deselected as an option for this within the OS settings.
Thanks again for the reply.
When I go to Windows Control Panel and check Sounds and Audio Devices there are some interesting results in the tabs:
Volume - No audio device
Sounds - Windows Default (other selection is No Sounds)
Audio and Voice - both only specify MOTU options in the dropdowns, no Windows or system options
Hardware - shows MOTU drivers as well as Legacy Audio drivers
I've tried the latest MOTU driver for 828mk2, and also rolled back to my old driver that worked just fine with Au 1.5. Same problem with both drivers in Au 3.0. FYI the motherboard has onboard audio but I keep that disabled in the BIOS and don't load drivers for it because in the past it conflicted with MOTU operation. Figured that was cleanest. Previous 1.5 installation ran just fine with MOTU.
Forgot to mention: Running WinXP Pro SP3, Intel Core 2 Quad, Gigabyte EP45-UD3R mobo, 4gb RAM.
>>>The other thing that may well be contributing to this is that you should also change the Edit View settings so that they also use the ASIO driver
Did that as well, prior to contacting forum. After being problem free in the past, I'm quickly understanding the frustration of those who write in with these one-off snafus.
Yes, it's a pain when that happens. At least you're running a sensible OS - if you'd been trying this with W7, then there's a good chance that things would have been even worse. I'm assuming that you've installed the patch - not that I think that this would make any difference to this situation; from memory, I don't think it altered anything hardware-related. Unfortunately, one of the big differences between 1.5 and everything that came afterwards is that 1.5 was the last version to use the OS APIs and DLLs to provide a record/playback function - all newer versions wanting to do the same thing have to use the Audition Windows driver (or ASIO4ALL) to provide an interface between the software and the OS.
One thing though - for Sounds, the correct selection is definitely No Sounds. If you give the OS the option, it will continually reset your sound device sample rate to play them (they aren't 44.1k!)
On my similarly specified laptop, I leave the on-board sound enabled, leave it set to No Sounds, and have the audio and voice settings set to use the MOTU 1&2 inputs and outputs. This seems to work fine, and I don't get reset issues at all. I've left the internal audio device enabled, but don't use it for anything. Doesn't seem to interfere, though - probably because No Sounds is the selected option - and that really is quite important. It's even mentioned in the Audition installation instructions...
>>>> One thing though - for Sounds, the correct selection is definitely No Sounds. If you give the OS the option, it will continually reset your sound device sample rate to play them (they aren't 44.1k!)<<<<
A-ha, or eureka, as they say. I'll have to correct that. I did not yet select "No Sounds" as the option. And I do perceive your mild poke about the install instructions ;-) .... one of the great things about Audition (and CEP) over the years has been how intuitive it is to use. I haven't had to crack the manual very often. I didn't even think to check specific install instructions, having done other upgrades with no problems. My bad. BTW, I do have the 3.0.1 patch installed.
I'll see what shakes out with the change in Sounds setting. Really appreciate your replies and insight.