Traveler and 896's together, anyone do this?
Moderator: James Steele
Forum rules
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. for Mac OSX
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. for Mac OSX
Traveler and 896's together, anyone do this?
I currently use two origional MOTU 896's and go up to 20 channels using all 16 analogs and both AES inputs. I'm thinking of getting a traveler for a couple reasons. It would be easier to use than the 896 (in racks) when I need only four channels on remote. I also want to increase my track count with the traveler bringing me above 20 inputs and up to potentially 28-30 inputs. I'm not sure what kind of performance I'll get with my firewire drives at that track count for tracking but I've definitly done 20 tracks for full live sets flawlessly. Anyway, anyone use 896's and Traveler with DP at the same time? Any issues?
-
- Posts: 2
- Joined: Fri Aug 11, 2006 11:33 am
- Primary DAW OS: MacOS
- Contact:
Traveler and 896's together, anyone do this?
Were you ever successful in combining the 896 and Traveler?
I'm trying to do the same and I can get the two devices to lock together but the signals are out of phase.
I'm trying to do the same and I can get the two devices to lock together but the signals are out of phase.
Re: Traveler and 896's together, anyone do this?
I have similar problems with 896HD and Traveler (Firmware 1.07).
Recordings not in phase, and random clock drop-outs.
External or internal clocking doesn't seem to make a difference. If Clock Source is set to any of the 896's clock options, the data stream from the Traveller will drop for a few seconds randomly. If Clock Source is any of the Traveller's options, same goes for the FW data from 896.
BUT: Each on their own work like a charm.
Seems like communication via Firewire between 896 and Traveler doesn't properly work. Anybody got a hint what to do?
Workaround for smaller dates would be to use one as a stand-alone device without PC connection, with its ADAT output feeding the other's ADAT input. This would give me 18 channels including the AES pair. On dates requiring more inputs, however, I'd need a second ADAT input.
Recordings not in phase, and random clock drop-outs.
External or internal clocking doesn't seem to make a difference. If Clock Source is set to any of the 896's clock options, the data stream from the Traveller will drop for a few seconds randomly. If Clock Source is any of the Traveller's options, same goes for the FW data from 896.
BUT: Each on their own work like a charm.
Seems like communication via Firewire between 896 and Traveler doesn't properly work. Anybody got a hint what to do?
Workaround for smaller dates would be to use one as a stand-alone device without PC connection, with its ADAT output feeding the other's ADAT input. This would give me 18 channels including the AES pair. On dates requiring more inputs, however, I'd need a second ADAT input.