Input monitor

Input monitor is not working. Im using a M-Audio FireWire Solo. The guitar records fine and plays back fine but I cant monitor it as I am recording or hear the levels. I have checked the 'Input Monitor' box and have core enabled
Jon

I have tried everything to get the input monitor to work but it still wont work. If there is anyone that can offer suggestions that would be great. I failed to notate in my first question/comment that I am using Logic Express version 8. thanks.

Similar Messages

Input monitoring problem

Hi all!
I've got the latest version of GarageBand that runs on my OS X Mavericks. The problem is with my guitar tracks. I plug in using my line-in input with simple cord and at first, there is no problem. I can hear my guitar playback live in real time(i.e. input monitoring is on) on the guitar track. But then something happens and my guitar sound disappears from the track, although the input monitoring function is still shown as working. Can somebody please tell me why this is so?
All help much appreciated.
therealking

I have a similar problem, although I'm on Logic Pro 8.
I can't seem to record my guitar track (mic'd cabinet) without having the result monitor back through my studio monitors unless I turn off software monitoring in Preferences/Audio. But then if I want to record keyboards direct and listen to what I'm playing, I have to go back in and turn the option back on.
In Sonar on the PC, this was much more intuitive. You could arm a track for recording by clicking the "R" button, and separately toggle monitoring on and off by clicking the little speaker button to the right. You didn't have to constantly fiddle with the program preferences.
I have a FireWire410 interface, and the monitoring only happens when Logic is loaded. I would have thought that the little "I" icon was to turn monitoring on and off, but it's some "pre/post-tape" toggle I can't find a use for.
Kevin, how did you control your monitor mix before?

No Skipping in Input monitoring At Playback

I was wondering if there were any way to keep the signal from an input-monitoring track from skipping when you start playback to hear another piece of data. For instance, I keep one audio track on input-monitor in order to process the signal from Ableton Live through Logic's effect plug-ins, because Logic's are much more powerful. However, I create riffs and such with the power of Logic's soft synths, because they're likewise more powerful than anything else out there. However, I want to be able to modify the signal from Ableton while I'm listening to the riff I've designed to see how it sounds. When I do this, though, the signal from Ableton skips, and just wouldn't do in live performance. Any guidance that can be offered is great. Thanks!

Mec36 wrote:
It's actually not rewired, I'm using an application called Jack that at first seems to be overly complicating the process of sending signals from one program to another, but for my purposes, it's not. You need to set the audio drivers for ableton and logic both to JackRouter
Right, I understand what it's doing.
I don't think it's latency, because I've messed around with buffer size/range >a lot; and I don't use ReWire, so it's not that either.
Latency can arise form several sources besides the I/O buffer.
If you have a plug-in with built in latency (time it needs to process the signal) such as a compressor, Logic will automatically compensate the whole system so that audio stays in sync, that means if you're adjusting Ableton to Logic's playback the output (Ableton) will not be in sync with Logic's audio output.
I could be wrong, there's a couple of ways to test this.
1. Create a project with a couple of synth tracks to play along with, do not use any plugins, try Ableton through Jack.
2. Under Preferences/Audio/General turn Plug-in-Delay Compensation Off.
Try Ableton/Jack in an existing project that has plugins and also, a bare bones project per #1 above.
3. There's also the chance that Jack has a built in safety buffer of a few samples, this could also cause Logic to burp.
pancenter-

LPX input monitoring problem, and varispeed

Every time I select a track for a guitar, then turn on input monitoring , once I press play I get no sound coming through.
Same thing once I enable varispeed.
Is there something not checked that needs to be?
Thanks

Turn off input monitoring.
Enable software monitoring instead, you should then be able to monitor if the track is record enabled.

Input monitor doesn't seem to work. What am I doing wrong?

I recently loaded Logic Pro 9.1.5 & the input monitor seems to have no effect. I an play files, but if I connect an instrument, I cannot monitor the input or hear the metronome. Am I missing something?

see this support article:
Troubleshooting Home Sharing

LogicX Rec Problem. I can't hear while recording no matter I turn on Auto Input Monitoring at menu or channel. On certain songs I could thru AUX to REC, my L7/8/9 procedure. Now, inconsistent, not work. Any help?

Logic X Recording Problem
I can't hear (ex.) voice back while recording no matter I turn on Auto Input Monitoring at Record Menu or Channel Strip.
On certain old projects I could when thru AUX to REC, which was my L7/8/9 procedure.
Recording takes place on a consolidated session, all audio tracks with no latency, which actually happens only it can't be heard.
Monitoring is very inconsistent and in fact doesn't work at all. Any help?
Mac Pro 2010 2x2.66 12 Core 32GB OSX 10.9.5 SSD 480
Recording on HD 1TB, Fireface 800

Correction: actually "thru AUX to REC channel" is not effective.
It's just that I can input monitor thru an extra AUX channel independently of the REC channel.
Sending the source to be recordered to aux and audio rec at same time.
Mac Pro 2010 2x2.66 12 Core 32GB OSX 10.9.5 SSD 480
Recording on HD 1TB, Fireface 800

Input Monitoring, and Audio Objects- help?

Hi!
First part:
Input Monitoring. I am used to Input Monitoring (live signal) overriding printed material (regions). I thought that if I had Auto Input Monitoring disabled, and if I would engage Input Monitoring on an Audio Track, ONLY the Live input would pass; any regions on the track would not sound...put simply, engage Input Monitor flicks a switch from regions to Live Input. But, it does not. The ONLY ways I have found to have JUST the live signal is to mute all regions, or actually record on the track. How SHOULD it work?
Audio Objects and Arrange tracks:
If I have 3 audio tracks in the Arrange window, and I assign them all to say, Audio Object 1; why do the Arrange window audio tracks not operate independently? If I solo one, all three solo. If I mute one, they all do. Even worse, if I Rec enable one, all three do!
I thought that Arrange window Audio tracks were independent, and operated as such. Assign tracks to multiple Audio Objects, or to the same, it did not matter. Part of the brilliance of it (I thought, initially) was how you could have different "versions" of a track feeding a single Object, and then priority would determine what actually plays back; but that is not how it works? Part of my delusion, it seems, was that when you mute or solo a track in the Arrange, there is a pause, and if I then do so in the Mixer it is much, much faster, which is due to the Arrange tracks being different...or not? Seems the answer to that incurs a penalty in one case, but not another, and that makes NO sense. Where did I go wrong?
Sorry for the wicked long post, but I see these both as related, and I would love to know why this stuff looks incredibly flexable and powerful on paper, but in practice, it is nothing short of frustrating, with very little benefit over other apps...maybe worse than some other apps...

Hi!
Thx for the reply! I seem to be find the odd questions...
Sampleconstruct wrote:
Click on the track with the regions you want to solo/mute->all regions in that track get selected->use the keycommands for Solo (S by default) and Mute (M by default). Then only the highlighted regions in that track will play/mute
That works well, and I could handle using it as a workflow. But, when one wants to retain individual mute states of specific regions on that track, this would alter that when unmuting. The tip below would be a viable alternative, but...
Sampleconstruct wrote:
Also have you tried the two different modes for Solo/Mute which can be set in Logic Audio Prefs? "CPU save mode" makes the tracks assigned to the same Audio object independent from each other - "Fast"-mode makes them all dependent, so try CPU save mode.
That I did not realize. However, if I rec or input enable, no matter what ALL Arrange tracks assigned to the same Audio Object rec/input enable. Any way to stop that that? Or is that just an "idiot-synchrocy" of Logic 8? (coulda sworn 7 did not do that?) Take recording is cool, but sometimes I might want to have alternates on a seperate track. It seems to defy the reasoning behind addressing Audio Objects...

Help...cannot get audio input monitoring t work

when punching in..I cannot hear audio before and after punch. Please help!!!

Try deactivating Input monitoring so you'll hear the track before and after the punch - like that you're actually listening "post tape". If you have an external Audio Interface/Mixer with monitoring capabilities use that instead.

Input monitoring problem during recording

Greetings,
I recently purchased Logic Pro 9, and am having a problem with input monitoring. I am not able to in any way affect control over my monitor mix during recording. I have tried every combination of options, including software monitoring, auto-input monitoring, etc...but always get the same headphone levels from my inputs (I am actually trying to mute the input signals out completely so that I can play along to only the click.
I am wondering whether this is some sort of software glitch, because I was able to control the mix perfectly before the latest software update. I wonder if that is the problem, or if I am overlooking some minor detail. Please help!!
BTW, I have checked, and this is definitely a software, not a hardware issue...
Thanks much,
Kevin

I have a similar problem, although I'm on Logic Pro 8.
I can't seem to record my guitar track (mic'd cabinet) without having the result monitor back through my studio monitors unless I turn off software monitoring in Preferences/Audio. But then if I want to record keyboards direct and listen to what I'm playing, I have to go back in and turn the option back on.
In Sonar on the PC, this was much more intuitive. You could arm a track for recording by clicking the "R" button, and separately toggle monitoring on and off by clicking the little speaker button to the right. You didn't have to constantly fiddle with the program preferences.
I have a FireWire410 interface, and the monitoring only happens when Logic is loaded. I would have thought that the little "I" icon was to turn monitoring on and off, but it's some "pre/post-tape" toggle I can't find a use for.
Kevin, how did you control your monitor mix before?

No Input Monitoring Button on track

Hi all.
I'm a beginner with Logic 8.0.2
On the track I have buttons for Mute, Solo and Record, and on the channel strip I have buttons for Mute and Solo. When I <ctrl> click on the track to configure the track header, the Input Monitoring button is selected (along with the other three) only it doesn't show up on the track!
Does anyone have any idea why? And what I can do to fix it?
Thanks a lot.

donko8999 wrote:
Hi. I told you I was a beginner.
I'm using Software Instrument tracks, which I now realize doesn't have (or need) that function.
Well, at least you are not a clueless beginner, and able to think for yourself.
Thanks for putting me on the right path.
I appreciate it.
I appreciate you thanking me.
regards. Erik.

Input monitoring noise

Hi there,
Whenever I select input monitoring in an audio track i get an extremely loud hiss/hum and everything I play on my keyboard is distorted. As soon as logic starts up I can hear background noise faintly, then when I turn on input monitoring it goes nuts! I've pulled the gain on my mbox down to almost nothing and the level on my keys is also very low. I'm not quite sure what else I can do to fix this, so any suggestions would be much appreciated...
thanks

turn the input gain at minimum...
try to change cables
try to adjust matching gain Input/output with you Speaker Monitors...
I think there is a point to obtain a good S/N ratio compromise...
But, yes, USB audio device comes with noise....
G

Please allow input monitoring in waveform recording.

It's a little absurd that such a sophisticated piece of audio software does not allow this simple function. Audacity has it and so should Audition!
Sure, it;s possible in multitrack mode and also through one's audio interface, however when recording directly to a file via Soundflower or other internal routing software these solutions do not apply.

Traditionally, software monitoring must be on, otherwise Logic does not send audio signals live through the mixer.
As for monitoring - the signal presumably will be sent wherever that channel is sent to - if you set that channel to output to outputs 5 and 6, presuumably that is where they will go if that channel is in input monitor mode (can't check at the moment). Is this not the case?
As for your last point, there isn't much you can't do in LP8 that you could do in LP7. If you want to create custom mixer layers, and create your own audio objects etc, you must turn off LP8's auto-management of audio objects, and create your own custom audio layer as per LP7.

Silent feedback from microphone after pressing the record ready and or input monitoring buttons

Hi Community,
So I am running a microphone(xlr cable)-->mbox mini--->macbook and have been able to successfully record many songs in the past. Just recently I have run into an intersting issue which I hope someone can provide a solution to.
When I hit the ready record button or the input monitoring button my level automatically shoots up about a third the volume bar without me even singing into the mic (My monitors are muted and I am wearing headphones). After recording, the wavform looks like there is a thick bar on the top half. I can still hear vocals but they are very faint, unlike how i used to get a clear, quality sounding recording. My input on the interface is also at about halfway and my phantom power is on. Here are some pictures to give you a better understanding of what I am looking at.
I hope this is clear
If ANYONE has a solution to this issue please let me know
-J

Trying another interface is probably the next step. I would also make sure the Mic is ok, do you know anyone with an interface or mixing board that supplies phantom power? Make sure your cables are good, a shorted mic cable can blow an interface op-amp in less than a second. The Mini may have blown on it's own, as I recall the mBox series did have some problems along those lines.
The general rule with phantom power is, do not plug (or unplug) any device with it on, this holds true for the interface into the computer or to XLR->Mic / XLR->Interface. After turning off phantom power I usually wait at least 15-30 seconds to let voltage drain from the circuits before starting to remove cables...etc.
As you can tell, I'm on the cautious side when it comes to phantom power and mics/mixing boards, I worked at a studio that had mics valued at $5,000 - $10,000 and a mix board that cost far beyond that... always play it safe.

Which adapter do I use for my DVI and RGB only inputs Monitor?

My Samsung monitor only has RGB and DVI inputs. I can't figure out which adapter from Apple to buy since I'm new in the Mac world and not sure of the limited port options I have.
Thanks.

You don't say which Air you have.
Provided yours is one with a Mini-Displayport or Thunderbolt, this should do the job.
http://store.apple.com/us/product/MB570Z/B/mini-displayport-to-dvi-adapter

9.2 Update killed my audio input monitoring during play!

I can monitor my audio input while I'm stopped, but as soon as I loop and play (not in record mode) it automatically kills monitoring of the signal. YET, I can still record if I need.
This didn't happen until I updated to 9.2.
Has anyone else had this problem?
Thanks!

I got other problems after updating Logic, they occured twice. One was not having 'open recent session' and the other was not having 'incompatible' plugins menu item in Logic AUs. Perhaps this is similar to my problem and the solution was to trash Logic preserences and rebooting. Try it, you don't loose anything that way. I'm not at my mac now but the preferences can be in MacHD/library/Preferences (start with com.apple.logic) or in your user Library/preferences. There are 2 files and I'm not sure which one but if you trash both (without deleting the files, only trash) you can try if it brings the requested feature back. One of the files will reset your settings but if you restore it after the test you will have them back (of course with the 'bug' itself. Later today I will pot you the exact one to throw.
Message was edited by: samplaire

Input monitor

Similar Messages

Maybe you are looking for