Apple Logic Pro /LogicExpress Discussion group photo

Yahoo Groups archive

Apple Logic Pro /LogicExpress Discussion

Index last updated: 2026-04-28 23:06 UTC

Message

Re: Monitoring Latency (was Pro Tools...Logic??)

2007-07-25 by Gregory

On Jul 24, 2007, at 3:53 PM, GAmoore@... wrote:

> > Latency, TDM systems are still the shizzle when it comes to this. I
> > cannot record a whole band in Logic, unless I use a hardware mixer,
> > or a software mixer to do a direct path back to headphones. This is
> > something that still infuriates me about Logic/Native rigs, how hard
> > can it be to figure out these latency issues...... it is after all
> > 2007......
> >
>
> Won't the new Apogee do 16 channels of input?
>
> Latency is not a trivial matter to fix. The only real solution is  
> to have a
> bypass loop of some sort to monitor the direct input. A/d and D/a  
> take time, as
> does saving megabytes to disks.
>
So here's what I don't understand - I've not been comfortable  
monitoring via an a/d - d/a pathway, so always use "zero latency"  to  
monitor.  But the lower end hardware available makes this very  
difficult.  I can monitor a summed output via the headphone out, but  
what I need is individual outs to add to the summed out on the  
headphone amp for the "more me" requests.

My Firepod can do standalone mode OR interface mode, but can't do  
both.  For that I needed to have bought the FireStation, I believe.   
With most mixers and interfaces (under $800) with preamps you are  
lucky to get direct outs on 1 or 2 channels.  So what do people do to  
put together a recording setup with individual monitor mixes?  Is  
there some low-cost trick I am missing to split individual signals  
between the interface and headphone amp?  Or am I dismissing  
monitoring through Logic when there is a low-enough latency option to  
make it work?  I'm on a Mac Pro.

Thanks,

Gregory

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.