Dymanic mic in 1/4" line2 input not workking?

I'm using? a Audigy 2ZS Platinum which came with Cubasis VST 4.0, FL Studio 4, and Wavelab lite.
My system is a Opteron 2.0? with 2 gig ram and windows xp. I'm trying to record from a dymanic mic plugged into the front panel /4" line2 and I can't figure out how to get it to work. I know the mic and cord are good (tested them). When I test for the mic in control panel - sounds the only mic that shows up working is the headphone/mic set. I know I need to use a pre amp with a condenser mic, do I also need to use one with a dymanic mic.

Re: Dymanic mic in /4" line2 input not workking?v The problem turned out to be the AD_Ext cable. I was able to use an old ide cable that didn't have any of the holes in the connector ends plugged. It now works, but I've noticed I don't get much volume from what I record with a mic. I'm using a dymanic mic and I have a shunt on the JP jumper. My setup is as follows:
Behringer ub2 mixer with 4 preamp channels. The mixer is connected to a small amp (which goes to a couple of speakers)
I'm also using rca connectors from the tape out on the mixer to the rca connectors for line 2 on the front panel for the audigy 2zs platinum. The instruments are being recorded with good volume, but the mic isn't. I have the volume knob for the line 2 aux turned all the way up and it didn't help? enough. I have a small 2 channel preamp that I'm thinking of trying to boost the volume of the mic with.

Similar Messages

Line-in input not working correctly in Garageband

Problem:
Line-in input not working correctly with Garageband. Problem occurred AFTER installing and using Blue Yeti USB mic, purchased from the Apple store.
System Details:
'07 20" iMac 2.4GHz 4GB RAM, OSX 10.6.5, Garageband '11 v6.0, Logitech Z4 speakers.
Background:
Before using the Yeti USB mic, I used the line-in jack. I'd connect a Shure mic or guitars directly in, but more recently through a 12 channel mixer. Have connected the Shure mic directly into the input jack, and the computer appears to be picking it up (System Preferences->Sound->Input), it is responding correctly there. Have set the output to the headphone (line-out) jack. When I go into Garageband, I can select from Line-in 1, Line-in 2, and Line-in Stereo. The trouble is that it's the iMac's built-in mic that is active (the one above the screen), not the line-in. I've rebooted the computer, checked the connections, reconnected the Yeti mic and I can't find what's causing the problem. Not sure what to do from here, need some help. Thanks

I have Logic Express on the iMac as well and I worked out how to set the input device back to the Line-In. I went back to Garageband and found the equivalent setting under Preferences->Audio/MIDI. Thanks for reading, sorry I didn't sort it out sooner! Merry Christmas!

Logic Pro 9 - MOTU MK II inputs not available in channel strip

I usually use a MOTU 24 i/o as my main Logic Pro 9.1.5 audio interface. I'm trying to use a MOTU MK II and it is connected via firewire. It shows up fine in the Logic > Audio > core audio driver preference and is checked on. However the MKII in/outs are not available on Logic's channel strip inputs and outputs. Logic still shows the 24 i/o's even though the 24 i/o is not selected in audio preferences and is not even turned on.
I've reinstalled the latest MOTU drivers, trashed Logic's preferences and restarted my MacPro but it is still the same. Only the 24 i/o available in the channel strip input and output.
Is there a second audio i/o setting that I'm missing?
My Mic is registering OK in the MKII so I know it is getting a signal.
Thanks,
Richard

For some reason Logic is listing the 24 i/o inputs.
I've renamed the 828 Mk2 1 & 2 inputs to Vox 1 and Vox 2. The MK2 has 8 analog inputs plus two mic/line inputs for a total of ten audio inputs, not 14 as listed in the channel strip input drop down.
Audio registers in and out of the Mk2 but does not register in Logic's channel strip input. I just switched back to the 24 i/o to test and audio registers fine in Logic's channel strip input with the 24 i/o. Just not with the MK2 selected as the audio source.
I'm curious if anyone else has had this problem or if I'm missing an audio input setting somewhere.
Thanks,
Richard

Logic Mics, Aggregate Devices and The Input Issue

There is a lot of discussion about Logic's inability to accept simple microphone inputs, and I ran into this for two frustrating DAYS of trying all the things in the Logic Express 8 Docs to fix it—to no avail.
But now it is solved, so I'm trying to create a DEFINITIVE list of steps and principles here so others may quickly blast past this issue.
The equipment I have seems to be emblematic to the problem. The Blue Snowball is one of those USB mics that simply doesn't automatically show up in Logic's Preferences > Devices > Core Audio >Device list. The fix for this is never mentioned in the Logic manual or Getting Started docs that I can find. There is a passing reference on page 100 that is virtually zero help, and does not bother to mention how this Prime Gotcha can bring you to your knees.
Principle #1: Logic uses the Preferences > Devices > Core Audio >Device (list) process to identify which microphone you can record with. The list has to have in it an entry that makes sense for both the incoming audio and the playback path that Logic uses to feed earphones or an external monitor.
Normal items on that list look like this:
Built-in Output/Line Input
Built-in Output/Digital Input
Built-in Line Output/Input
Built-in Line Output/Digital Input
Built-in Digital Output/Line Input
Built-in Digital Output/Input
The Built-in Output is the computer’s inner speaker or headphones. The Built-in Line Output is the computers stereo jack for feeding to an amplifier. The Built-in Digital Output is the fiber optic feed that can also feed an amp with up to six parallel audio channels (okay, 5.1 channels).
Nothing on that list will show a fully functional USB microphone that is being viewed on the computer’s System Prefs > Sound > Input page, even though the metering dots there show that the computer sees a live, active microphone.
Selecting the Mic in the Sound prefs page does nothing to pass it on to the Logic > Preferences > Devices > Core Audio >Device list of selectable items. This is frustrating, since GarageBand sees the live mic without any problem, but GB is a simpler program that has fewer options while Logic has many other potentials, so a one-size-fits-all solution may not be its best default setting.
To get the mic into Logic, you have to go into the Audio MIDI Setup utility program where a peculiar option appears that is called “Aggregate Device”.
This keyword is not found in the Mac docs, and understanding it seems to be a big secret. Even the Audio MIDI Setup help page will show you how to find it, but not how it works or how to use it for Logic. Ahem.
You open Audio MIDI Setup and under its header bar Audio is only one item, sure enough, Open Aggregate Device Editor. That opens a window that has two sections, an upper window with Aggregate Devices / In / Out across its top, and a lower window that shows all the options that the computer is aware of. The lower window is called “Structure:” and columns show Clock / Use / Audio Device / In / Out / Resample.
A default item “Aggregate Device” shows in the top panel, and you can add others and double click on one to change its name. You can make many variations here.
By default these will be present:
Built-in Line Input
Built-in Digital Input
Built-in Output
Built-in Line Output
Built in Digital Output
At the bottom of this list any other audio input devices that are plugged into the computer should show up. If they can be seen in the System Prefs > Sound > Input page, they’ll be here, too.
When I plug my Blue Snowball USB mic into the computer, it shows up here as Blue Snowball.
You create an Aggregate Device by clicking on your sound source, in my case, the Blue Snowball, then adding one or more other options.
When you click the Use check box for any entry, it pops to the top of the list.
Principle #2: An Aggregate Device is used by Logic to “see” both an audio input and an audio output path at the same time. The Device you’re creating at this point must include an input Audio Device AND at least one Output item to be fully functional for Logic. A Help page in Audio MIDI Devices called “Combining multiple audio devices” explains this in bare bones, but you can’t see that help page unless the Audio MIDI Devices utility is open.
In my case, I’ve checked the Blue Snowball and Built-In Line Output, so I can use that combo in Logic to define where the mic is coming from and where the Logic audio output should go to my line-input amp and speakers.
In the Audio MIDI Setup utility, simply selecting the Blue Snowball as the “Default Input:” device and/or the “Properties For:” options shows that the Audio Output area of the page has this cryptic message: “Output is not supported.”
At this point, you’re almost ready to go, and you can close the Audio MIDI Setup utility. But there is at least one more “gotcha” to conquer.
Principle #3: Logic ONLY looks for its list of usable Core Audio Devices when it starts up. If you have it open right now, all the choices made for Aggregate Device will not show up as selectable. Save any work in Logic, shut it down, then boot it up again.
Now you can use Logic's Preferences > Devices > Core Audio >Device list to see your Aggregate Device. I’ve named mine “Snowy Line Out” to trigger my recognition of what it contains. Another one is called “Snowball + Line + Digital” and it has both line and digital outputs aggregated to the Snowball mic input.
You can make one in the Aggregate Device Editor that combines a microphone plus earphones (Built-in Output) plus Line and/or Digital Outs, too. You'll have to switch among them in Logic as you work, but each will carry the live mic direct to recording.
I hope this gets you through the frustration of not knowing what to do when confronted with the lack of clear docs and complete steps to get a USB mic or other seemingly opaque input issue. Feel free to add to this so others in my former state of bewilderment can gain understandings.
If Steve Jobs were to encounter the level of opacity, ambiguousness and frustration that setting up a simple USB microphone can create in Logic, you can bet that the several programs and their intimate interdependency would be either automated or fully explained in the documentations that followed his fiery analysis of the issue.

I don't know of another way to get the Blue Snowball USB mic to show up in Logic. If you can do it without having to go through the Aggregate Device route, feel free to post here how to get that to happen.
I didn't have a different mic available when I started trying to do what seemed to be the simplest of things -- record and play back an audio track -- and nothing else seemed to work.
There are a lot of Aggregate Device threads around here, many associated with Blue Snowball, Blue Snowflake and other things, but none of them laid out the principles of how Aggregate Device Setup needs to work or what to do to force it into compliance.
As I said, the clues in the Logic docs and in-mac docs are minimalist, at best, none of them bringing instant head slaps of success readily.

DVI to VGA adapter, monitor says "input not supported"

I have just received my MBP yesterday and, when I attempted to attach it via DVI to VGA adapter to my Acer AL2016W flat panel LCD, the monitor told me "input not supported". I was under the impression VGA is VGA is VGA. Perhaps I am mistaken. There is no DVI port on this monitor so I am, essentially, screwed ATM unless I purchase yet another monitor - this one is less than a year old. I require my MBP to be attached to an external monitor due to a disability, and am not sure what to do. I don't believe it to be an isolated issue, especially after viewing some of the other posts about the graphics card being an issue as well. I wish Apple would come forward with a resolution. I realize this issue has probably been posted somewhere already, however I am unable to sift through all the posts due to the aforementioned disability and inability to attach to external monitor. I just can't sit here for that long, so I offer my apologies.

First off, are you connecting in the proper sequence? That is:
1. MBP and monitor powered on
2. connect monitor's VGA cable to the DVI-to-VGA adapter
3. connect DVI-to-VGA adapter to the MBP's DVI port
In that way, the MBP should autodetect the monitor and set the resolution appropriately. Else, the output resolution of the MBP may not suit the monitor, and the monitor will give a "not supported" error.
As a side note, have you considered the options in System Preferences > Universal Access? Options include Zoom, VoiceOver (spoken screen selections), making the cursor larger, and other enhancements for the visually impaired.
Hope this helps...

While playing a game my iphone went completely frozen, it does not respond to any input, not even to holding down the on/off hey. Any ideas?

While playing a game my iphone went completely frozen, it does not respond to any input, not even to holding down the on/off hey. Any ideas?

Try a reset. That is holding the sleep/wake and home button together until you see the Apple logo and release. That will reset the iPhone, but will not affect your data.
Thanks! It worked just fine!
MRP66

External display and "clam shell" closed lid mode = "Input Not Supported"

I have an Acer AL2016W 20" monitor hooked up to my again Powerbook due to it having a cracked screen. It is working just fine right now, in 1680x1050, when the screen is open. Citing this article,
http://support.apple.com/kb/HT3131
I should be able to close it and have it working as well. When I do close it then wake it, I just get a "Input Not Supported" message on the monitor. Any help?

I'm still puzzled at why it the screen is activated when the lid is closed and woken with an external USB device
That's rather puzzling as the display should not work if the lid is closed. If you have an external drive you're able to install a clean copy of Mac OS X to and boot from you can see if the issue persist there. If it does then it's most likely a hardware issue and you should contact AppleCare. If it doesn't then it has something to do with either your software installation else some utility you've installed.

Input Not Supported

I was in my mac mini playing with the display settings and I clicked on one that was way to big for my monitor. Now its not coming up at all. I can see the screen when it boots up, however when it gets to the OS, the screen goes to a blank black screen and says "Input Not Supported" Please Help. I just got this 4 days ago.

I believe the easiest way to recover from this is to boot into safe mode.
http://docs.info.apple.com/article.html?artnum=107393
That should cause the mini to boot in a lower, default resolution. Once you have a useable image, go into display prefs and set the resolution back to the desired one you were using before and reboot.

Problems with new display, "Input not supported"

So, I just got myself a new LCD screen (Acer AL2016WCbd) for my G4 (DP 1Ghz Quicksilver 2002 w/ 10.5 installed). The monitor seems to work alright and everything with my Windows box, but whenever I try to use it with my G4 the monitor goes black, flashes an error box saying "Input not supported," and then goes to sleep. It does show the boot screen... the gray background and Apple logo... but goes black after that.
I've tried rebooting, resetting the PMU, tried booting in Single User and Verbose mode, tried hooking the G4 up to another monitor and lowering the resolution to 800x600 @ 75Hz and then reconnecting the Acer, but no dice.
My only other ideas are to try hooking it up over DVI instead of VGA (though I'd need to get an adapter for that); playing around with a few different things in target disk mode by hooking it up to my laptop (which I don't currently have); and trying to boot from my Leopard install disk (when I find it). Might any of these things do any good? Is there anything else I haven't thought of? Or am I just wasting my time?

OK, so I can get the display working if I first boot up with another display, set the resolution to whatever I want it to be, then hotswap in the Acer that's been giving me the problems. But once I restart my computer I have to go through the whole process again. Either the tower isn't picking up on the display profile from the monitor or the monitor just isn't sending it to the tower.
My question now is: is there a way to for me to lock the resolution and refresh rate, so it always outputs at, say, 1680x1050 at 60Hz? Both Newegg and Acer have been giving me all kinds of (excuse me here) sh** about how they can't help me, so I really don't want to deal with them anymore by having to return/exchange the monitor or get it serviced. I mean, I know the thing works and I know the resolution I want it to run at. I just want to be able to lock it so Leopard doesn't revert to some unsupported output every time I reboot.

I have acer al1916w and i have a problem message that say input not supported help

i have acer al1916w and i have a problem message that say input not supported help

under windows 7 - 8.1right click on your desktop and choose screen resolution set a very basic resolution like 1280x1024 @ 60Hz (frequency can be set under advanced options); you need to have a working monitor to set this and then reboot connecting your al1916w. if it still gives you that message, can be a bad cable or some hardware monitor issue.

Acer AL 707: "Input not supported" - What can I do?

Hello everybody!
I've bought a new Mac mini and I wanted to change the screen resolution and suddenly, the screen got black and a message "Input not supported" appeared. What can I do? I'm totally helpless.

Reset the pram
This should erase your monitor preference.

Mac mini input not supported

After I power up my mac main with 10.4.1 os I type in my password, then the screen goes black and says " input not supported"

Try a safe boot.
     Shutdown your machine. Hold down the shift key. Poweron. Wait awhile; wait awhile while you harddrive
     is being checked.
     http://support.apple.com/kb/ht1455

Intermittent "Input Not Supported"

A few days ago picked up a Mac Mini to make into a video server. I have it currently hooked up to my old PC's LCD monitor (17" Envision cheapy from when LCDs first became affordable 5 or so years ago) while I work on converting my DVD collection to it.
A number of times, when the monitor comes back on (after it times out), it will show as "input not supported". I turn the monitor's power off and back on and eventually it will bring the display back. A couple times it was somewhat scrambled along the bottom edge also.
I have the display settings to a resolution that works with this monitor and OSX automatically detects the display (EN-7100e).
I haven't used this monitor much recently, but when running on the old PC didn't have any issues with it. Would OSX be confusing it possibly when awaking the monitor? Have others experienced this issue?

Now that's an interesting data point. The mere act of viewing the mini's screen from a remote client should not cause any change in the video output of the mini. There is definitely something strange going on.
Here's a question: if you cold boot the mini while it is connected to the Envision, but the Envision is powered off, and if you then remotely connect to the mini from the MBP with the Envision still off, what screen resolution is the mini running at in that case? Also, if you look at Display's preferences on the mini from the MBP (Envision still off), does it indicated the Envision is attached or not?

HT201412 Touch screen input not responsive.

Touch screen input not responsive. Cannot slide to power off. Appear message "iCloud Backup: This ipad hasn't been backed up in 2 week. Backups happen when this ipad is plugged in, locked, and connected to wi-fi" Touch OK but nothing change. Does follow instruction but nothing works

Thank you for your help.
I did all of trouble shooting procedures but it did not work.
I called Apple Care and explained what kind of problem i had and they booked me up with Genius Bar @ Apple Retail Store.
I went to them last Saturday and they replace my troubled iPhone with the new.
they said it is very rare problem reported so far and i could be the first few ones.
it was no hassle and they all were very kindly listened to me.
anyway, problem solved with replacement and i was lucky to have back up for iPhone.
Anyone has same problem, call 800-MY-IPHONE and book yourself to nearest Genius Bar to get your iPhone served or replaced.
thanks

Make my field as input not possible.....

Hi all...
in module pool screen.....
How can i make one input field as "input not possible" for one perticuler condition met??
ex: iam having one input field in my screen.... so i can enter the values for it.... similer ly iam also having another one... here if i enter value in the second one and push the pushbotton to do some caluclation part.
then my first input field has to appear but in no input possible mode...
Thank you,
Naveen

Hi,
You said you have two fields on your screen and a pushbutton...
So You can do like this....
if sy-datar = 'X'.
loop at screen.
if screen-name eq 'FIELD1'.
screen-input = 0.
endif.
Modify screen.
Endloop.
Endif.
Or you can also do like this....
If sy-ucomm = 'PUSHBUTTON'.
loop at screen.
if screen-name eq 'FIELD1'.
screen-input = 0.
endif.
Modify screen.
Endloop.
Endif.
here PUSHBUTTON is the Fcode for the Pushbutton and FIELD1 is the screen name of the field which has to get diabled.
Reward if helpful.
Regards,
Syed

Dymanic mic in 1/4" line2 input not workking?

Similar Messages

Maybe you are looking for