I never knew that you could add an Input audio object, to control the incoming audio signal, until today; what I normally do is just set an audio track to Input 1 (or Input 1-2 for stereo) and get recording - the signal comes in as my interface receives it from the board. Since I've never created or used an Input object but have always been able to record just fine (no need to adjust levels in Logic, etc.) I'm not sure why I would want to create and use an Input "channel strip." Are there situations where it is advantageous to use an Input object, over the method I described above? Brian :::::::::::::::::::::::::::::::::::: Logic Audio Pro 6.4.1 PowerMac G4 933MHz OS X 10.3.3 1 GB RAM M-Audio Delta 24/96 (fed via S/PDIF from a Yamaha DSP Factory)

--- In logic-users@yahoogroups.com, Brian Pylant <bappo@b...> wrote: > Are there situations where it is advantageous to use an Input object, > over the method I described above? A - For monitoring inputs without record-enabling tracks - though Auxes can do this as well. B - Plugins instantiated on an Input object will be recorded into the audio file... John Pitcairn ------------------------------------------------------------- Logic Control emulation for generic midi controllers: LC Xmu demo: http://www.opuslocus.com/lcxmu/ -------------------------------------------------------------

On Mar 28, 2004, at 9:56 PM, Brian Pylant wrote: > I'm > not sure why I would want to create and use an Input "channel strip." > Are there situations where it is advantageous to use an Input object, > over the method I described above? > Adding EQ and compression or other FX to your recording on input ( print to drive ), and then creating a custom input setup for a client. Love it, use it _all_ the time. George www.utopiaparkwaymusic.com Now both Mac OSX and Windows XP... the only way to fly ;-)

> Adding EQ and compression or other FX to your recording on input ( > print to drive ), and then creating a custom input setup for a client. > Love it, use it _all_ the time. Ahh, I see... I never use Logic plugs during tracking, simply because when I turn on software monitoring (in order to hear them) I get an awful delay between Logic's output and my sound card's direct output to my monitors. Very unnerving... once I figure how to get around that one I can use Logic FX while tracking (which I'd really like to do). Sorry to keep asking all these dumb questions, but up to this point I primarily only record myself so the features I need are pretty limited - I'm just starting to work on learning the more advanced concepts that Logic brings to the table. I appreciate you patience! Brian :::::::::::::::::::::::::::::::::::: Logic Audio Pro 6.4.1 PowerMac G4 933MHz OS X 10.3.3 1 GB RAM M-Audio Delta 24/96 (fed via S/PDIF from a Yamaha DSP Factory)

On 04-03-30 06.35, "Brian Pylant" <bappo@...> wrote: >> Adding EQ and compression or other FX to your recording on input ( >> print to drive ), and then creating a custom input setup for a client. >> Love it, use it _all_ the time. > > Ahh, I see... I never use Logic plugs during tracking, simply because > when I turn on software monitoring (in order to hear them) I get an > awful delay between Logic's output and my sound card's direct output to > my monitors. Very unnerving... once I figure how to get around that one > I can use Logic FX while tracking (which I'd really like to do). I'm afraid you can not "get around" latency. It's the way hardware (computer, AD process) works. If you want to use Logic's effects directly on the input object but find the latency annoying, then simply turn the track level down and pick your monitoring from the direct output of you audio card. Best wishes Per Boysen -- www.boysen.se www.looproom.com

On Mar 29, 2004, at 8:35 PM, Brian Pylant wrote: > Ahh, I see... I never use Logic plugs during tracking, simply because > when I turn on software monitoring (in order to hear them) I get an > awful delay between Logic's output and my sound card's direct output to > my monitors. Very unnerving... once I figure how to get around that one > I can use Logic FX while tracking (which I'd really like to do). > Small I/O buffer size (128k or less) = imperceptible latency (the name for the delay). Try it, you'll like it ;-) G www.utopiaparkwaymusic.com Now both Mac OSX and Windows XP... the only way to fly ;-)

> I'm afraid you can not "get around" latency. It's the way hardware > (computer, AD process) works. It's not latency, but rather a weird audio routing issue; what's happening is the input signal is being routed directly to the monitors, AND the output signal from Logic when "software monitoring" is enabled) is being routed as well... okay, I guess that is technically latency, but what I mean is that I suffer zero latency when I leave software monitoring disabled, but of course that prevents me from using Logic FX during tracking as well... if I can figure out how to turn off the signal being passed directly to the monitors and only use Logic's output during tracking I think I'll be OK, but I don't think the M-Audio control panel allows for that... Brian :::::::::::::::::::::::::::::::::::: Logic Audio Pro 6.4.1 PowerMac G4 933MHz OS X 10.3.3 1 GB RAM M-Audio Delta 24/96 (fed via S/PDIF from a Yamaha DSP Factory)

> Small I/O buffer size (128k or less) = imperceptible latency (the name > for the delay). > > Try it, you'll like it ;-) I absolutely will, thanks for the tip... hopefully it will work for my situation! Brian :::::::::::::::::::::::::::::::::::: Logic Audio Pro 6.4.1 PowerMac G4 933MHz OS X 10.3.3 1 GB RAM M-Audio Delta 24/96 (fed via S/PDIF from a Yamaha DSP Factory)