I'm using a Midas VF32 (Firewire) console with Mixbus 32c, v7.x (latest) on Windows 10. It's been working like a dream.
I've been able to do everything I've wanted until now.
I just added a standard audio track for a Shaker, and Mixbus all-of-a-sudden won't let me assign the track output to a channel on my board. Nor will it for any additional audio tracks.
I have everything else going to the console flawlessly. When I try to assign the track output, the entire output menu is "whited out" and refuses assignment.
I did notice these entries in the startup list - is there something else I can use other than Portaudio?
Maybe that's the problem? Not sure how it came up as I don't know enough about Portaudio (yet).
2022-03-01T15:01:38 [INFO]: Output channel count configuration not supported
2022-03-01T15:01:38 [INFO]: Input channel count configuration not supported
(03-01-2022, 03:08 PM)davidg25 Wrote: Thank you, but it's fine there.
I did notice these entries in the startup list - is there something else I can use other than Portaudio?
Maybe that's the problem? Not sure how it came up as I don't know enough about Portaudio (yet).
2022-03-01T15:01:38 [INFO]: Output channel count configuration not supported
2022-03-01T15:01:38 [INFO]: Input channel count configuration not supported
That looks as if you have maxed out your output channels.
MMM
Linux throughout!
Main PC: XEON, 64GB DDR4, 1x SATA SSD, 1x NVME, MOTU UltraLite AVB
OS: Debian11 with KX atm Mixbus 32C, Hydrogen, Jack... and Behringer synths
I think by the general behavior that MMM may have called it. I've never had this happen with other DAWS, wonder what gives?
I will reset outputs when it's "mix time" so I'll have a better idea. Some are doubled up on a couple of things, but it's been working great. I can find a workaround if the need persists.