jump to beginning show previous Showing Logic-users Thread 98425 of 105816 show next jump to end

Forum Index | Read LUG: Policy/Rules Messages Threads Digests | Post New Message | Search!

From: Gregory <glists@candyblue.net>
Date: Wed, 6 Dec 2006 at 6:26:13 PM
Subject: [LUG] Alesis io/14: Mixed latency
Message #221967
The new Alesis io/14 has 4 analog inputs and 8 ADAT input channels that it gets into my Mac via firewire. Add the 2 spdif channels, and you have 14 simultaneous inputs into Logic. I have an EZ Bus with ADAT out, so when recording my band last night, I had 4 mics into the analog inputs on the io/14 and 1 mic into the EZ Bus, then to the io/14, and all getting into Logic via the io/14 firewire. My problem is that the one mic taking the optical route was severely delayed relative to those going directly into the io/14. This makes some sense, in that digital is slower than analog, but I'm surprised there's no compensatory mechanism built in somewhere. It seems that there is no point in being able to use analog and digital inputs simultaneously if they don't arrive to the computer at the same time. Are my expectations too high, or is one of my devices not holding it's end of the synchrony bargain? Thanks, Gregory
Viewed 632 times, 1 reply, 3 messages in thread. Reply to this message.
From: "John Pitcairn" <johnp@opuslocus.net>
Date: Wed, 6 Dec 2006 at 7:57:17 PM
Subject: [LUG] Re: Alesis io/14: Mixed latency
Message #221969
This is a reply to #221967.
--- In logic-users@yahoogroups.com, Gregory <glists@...> wrote: > I have an EZ Bus with ADAT out, so when recording my band last > night, I had 4 mics into the analog inputs on the io/14 and 1 mic > into the EZ Bus, then to the io/14, and all getting into Logic via > the io/14 firewire. > > My problem is that the one mic taking the optical route was > severely delayed relative to those going directly into the io/14. How severely? The EZBus converters and internal digital signal path probably need more time than the converters on the Alesis, and there may be some internal buffering done for the ADAT output. This difference is fairly normal when digtally interfacing different gear. First, measure and set the record offset for the SLOWEST converters (EZBus via optical) - http://www.opuslocus.com/logic/record_offset.php Then measure how far ahead of the EZBus the Alesis converters are (in samples), and add Sample Delay plugins set to that amount on the appropriate Alesis Audio Input objects in Logic (you may need to create these input objects in the environment). Turn software monitoring on, and route the input objects to no output (or mute or pull their faders down) so you don't monitor them all the time. The Sample Delay plugins will be recorded, and everything will be in sync. John Pitcairn ---------------------------------------------------------------------------- - LC Xmu Logic/Mackie Control emulation & management, LC Xview software LC/MC display, Logic environments & stuff... Opus Locus - http://www.opuslocus.com ---------------------------------------------------------------------------- -
Viewed 642 times, 1 reply, 3 messages in thread. Reply to this message.
From: Gregory <glists@candyblue.net>
Date: Sat, 6 Jan 2007 at 12:00:31 PM
Subject: [LUG] Re: Alesis io/14 & aggregate devices
Message #223057
This is a reply to #221969.
<quotes repositioned and trimmed by admin> On Dec 6, 2006, at 8:57 PM, John Pitcairn wrote: > First, measure and set the record offset for the SLOWEST converters > (EZBus via optical) - http://www.opuslocus.com/logic/record_offset.php > > Then measure how far ahead of the EZBus the Alesis converters are (in > samples), and add Sample Delay plugins set to that amount on the > appropriate Alesis Audio Input objects in Logic (you may need to > create these input objects in the environment). Turn software > monitoring on, and route the input objects to no output (or mute or > pull their faders down) so you don't monitor them all the time. > > The Sample Delay plugins will be recorded, and everything will be > in sync. Thanks to John for the know-how on latency compensation. While it still may come in handy, it's moot right now, as my Alesis went all wonky on me and had to be sent back to the retailer. This leads to three new questions: 1. Should I try a replacement Alesis? My problems were most surely due to a defect in my unit (audio disappearing after 1 minute of playback, and failing to power up for 3 days before suddenly working again). If I had a lot of faith in the company I would just have them send me a replacement, but I have heard of big QA problems with Alesis products, and don't want to deal with a never-ending stream of hassles, especially any that pop up AFTER the 30-day return period. What are people's experience with Alesis? 2. Are there any problems with aggregating devices? Another option is to replace the Alesis with a different similarly-priced product, but I would lose ADAT ins. However, I could aggregate my new product (410, Saffire, Konnekt8, Firebox) with my two older products (Duo, EZBus) for the 6 pre-amps I need. But does the aggregate device work to the lowest common denominator, or place extra burden on my CPU or USB/Firewire busses? 3. Or, I could abandon my 3 low-end units and throw another $250 into the pot and get a MOTU 8pre. I have no doubt everyone would recommend this option (or adding $700 and getting a Fireface!) so this isn't really a question. I just have to weigh $250 vs. convenience and quality. I wish the inputs were in the front, like the Firepod though. Thanks for any and all input. Gregory
Viewed 566 times, 0 replies, 3 messages in thread. Reply to this message.

Forum Index | Read LUG: Policy/Rules Messages Threads Digests | Post New Message | Search!

Forum Index | Read LUG: Policy/Rules Messages Threads Digests | Post New Message | Search!


© 1994-2008, All Rights Reserved.