Greetings- I posted this question under the MOTU hardware forum already but thought I'd give it a shot here as well...
Basically, I'm trying to record 24 channels of analog through 3 MOTU 896/896HD's. Each MOTU will have 8 mono mics, and the motus will be daisy-chained via firewire cables, and to a g4 powerbook. Recording is at low sampling rate/bitrate.
I'm a biologist, and just need simple .wav files w/ no mixing, editing etc, so was looking at some biologically geared recording software (specifically, Raven from Cornell Lab of Ornithology) rather than Digital Performer.
Raven (and many bioacoustics programs i think) only accept 1 audio device at a time, so I am trying to use the "Aggregate Device" option in the Audio MIDI Setup. I've had some success, in that I can create an aggregated device, Raven can see it, but I still get a max of 8 channels. Raven can also see the individual MOTUs and record off of either one.
MOTU tech support thinks this may be a software problem with RAVEN, but I'm not quite ready to give up yet, so if anyone out there has experience with daisy-chaining MOTU's together and can offer some advice with configurations in the audio MIDI setup and motu firewire console, please let me know.
Thanks, and happy holidays!
help with "aggregate device" under Tiger
Moderator: James Steele
-
qo
- Posts: 873
- Joined: Sat Jan 22, 2005 10:01 pm
- Primary DAW OS: MacOS
- Location: San Jose, CA
- Contact:
Hi Alan,
The following Apple Developer FAQ implies that aggregate device (AgDev) support should be transparent to applications (since it, apparently, is even transparent to drivers).
But, have you tried accessing the AgDev with DP? If you can, then that would implicate Raven, I'd think. Having setup and used an AgDev in DP, I can say that you will still see the in/out's of the individual devices (and, you can still select and use them), but you'll also be presented with the AgDev's in/out's.
Maybe, for example, Raven has an issue with displaying more than X number of in/out's? This would be an orthogonal issue to AgDev support.
The following Apple Developer FAQ implies that aggregate device (AgDev) support should be transparent to applications (since it, apparently, is even transparent to drivers).
But, have you tried accessing the AgDev with DP? If you can, then that would implicate Raven, I'd think. Having setup and used an AgDev in DP, I can say that you will still see the in/out's of the individual devices (and, you can still select and use them), but you'll also be presented with the AgDev's in/out's.
Maybe, for example, Raven has an issue with displaying more than X number of in/out's? This would be an orthogonal issue to AgDev support.
Thanks qo!
Haven't looked at DP yet, but will do that when I get back. We may end up using DP after all. The guy that wrote the sound annotation program that we might use said he could modify it to make it a bit easier to deal with the single-channel .wav files that DP spits out (we need them zipped together into a multi-channel .wav file).
I am using a demo version of Raven, so its entirely possible that they only put in support for 8 channel input... It should do at least 16 (mentions this in the manual), and my tests this week were only using 2 motus, so it should have worked. I'm waiting for word from the bioacoustics folks at the Lab of Ornitholgy.
Anyway, thanks again.
Haven't looked at DP yet, but will do that when I get back. We may end up using DP after all. The guy that wrote the sound annotation program that we might use said he could modify it to make it a bit easier to deal with the single-channel .wav files that DP spits out (we need them zipped together into a multi-channel .wav file).
I am using a demo version of Raven, so its entirely possible that they only put in support for 8 channel input... It should do at least 16 (mentions this in the manual), and my tests this week were only using 2 motus, so it should have worked. I'm waiting for word from the bioacoustics folks at the Lab of Ornitholgy.
Anyway, thanks again.
