Metric Halo Discussion Forum: MIOConsole » Seeking 2882 signal routing advice from Bias PEAK PRO Users

Seeking 2882 signal routing advice from Bias PEAK PRO Users [message #85215]

Fri, 30 December 2011 17:12

jduesenb
Messages: 2
Registered: December 2011
Location: Boston, MA

Junior Member

Excuse a very new newbie who is surprised to see so few messages and topics up here. This isn't really about "MIOConsole", either, except insofar as MIOConsole configures signal routing...

I'm the proud new owner of a MH 2882 interested in communicating with anybody who might be using some current version of Bias Peak (I use Peak Pro 7) with a 2882. I'm having a lot of problems setting up this software with the 2882 - probably because I'm stupidly misunderstanding something about MH2882, Peak, or both.

First of all, on the MIOConsole side, I'm starting with the 2882 Basic Setup Template, with no changes except physical routing of the mixer sum to Analog 3+4. I'm reasonably convinced that the 2882 and MIOConsole are properly sending/receiving FireWire signals to/from the Mac host in general.

Peak is not a "DAW" but more of a general audio utility and mastering app. that deliberately handles only mono or 2-ch. stereo inputs/outputs/soundfiles. As such it will see the 18 FireWire audio signals coming from/to the 2882 as a set of 9 stereo pairs. (Given that the 2882 is online with Core Audio and is selected as the Sound Control Panel input/output device).

Peak only lets you select 2882 ins/outs as represented by lists of the form:

"Record Thru:
In 0 1 & 2
In 2 2 & 4
...
In 16 17& 18"

or
"Play Through:
Out 0 1 & 2
Out 2 2 & 4
...
Out 16 17& 18"

This representation SORT OF make sense... My problem is, I don't know how the above stereo pairs map to MH2882's "FW 1...18" (send to "DAW app") or "DAW 1..18" (return from "DAW app") - either logically, or physically. All I can say is, sometimes Peak sees inputs and sometimes it doesn't.

There is something basic I'm probably missing here,,, I've already talked to BIAS support and while they are very nice, they can't be expected to solve every particular problem with every particular device that might be trying to interface to their software. ANY CLUES OUT THERE?

I'm going to try the mobileIO maillist as well - seems to be more activity up there.

Thanks and happy new year... JD

Report message to a moderator