Article View: borland.public.cppbuilder.multimedia
Article #994Re: Audio Input Problem
From: WH
Date: Mon, 22 Apr 2002 09:34
Date: Mon, 22 Apr 2002 09:34
50 lines
3047 bytes
3047 bytes
In another list, I've been taking part in a discussion which has shown that some IBM laptops have a mono 'mic in' socket that magically turns into a stereo line in socket when one enables the Windows mixer's 'line in' channel on record. This doesn't apply on the current X-range, which have a 'line in' jack hidden round the back. FWIW, I've tried this on my (dreadful) Sony laptop and it doesn't work there. Since purchasing this Sony 'multimedia' machine, I've bought 2 other machines - making sure that both (Acer and Asus) had line in sockets and a knob for a volume control. Another thing to watch out for is that laptop mic input sockets are wired as mono jacks (tip and sleeve), whereas, for example, minidisk microphone jacks are wired as stereo (tip and shorter sleeve + ring and shorter sleeve). This makes the lead from, say, a mono mic look the same, but be wired differently. What a mess it all is! Bill Michael Warner <mvw@ozemail.com.au> wrote in message news:5363cu0oo8bda21svg9l4gn2np05bc2l4d@4ax.com... > On Sat, 20 Apr 2002 10:06:02 -0400, "David Evennou" > <dae@data-masters.com> wrote: > > >I have a "Line Out" from a mixer that I want to record from. HP > >said to use the "Mic" input. I tried that, but the impedance mismatch is so > >great that it won't work. After all, a "Line Out" generates something like > >one volt output signal and a microphone does not generate a voltage. > > It does, but a much smaller one, typically 10mV. > > >I can't imagine a company like HP telling me to try the "mic" input for a "Line" > >signal. > > It might work for a signal that can be turned down to a very low > level, though. BTW, mic inputs are usually mono, while line inputs are > stereo. > > What you need to do is put a resistive divider between the line signal > and the mike to reduce the level. If you can't find someone able to do > it for you, let me know and I'll describe it in detail.
Technical Details
Message-ID:
<aa0llj$aos$1@newsg1.svr.pol.co.uk>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!supernews.com!priapus.visi.com!news-out.visi.com!hermes.visi.com!news.maxwell.syr.edu!diablo.theplanet.net!diablo.theplanet.net!news.theplanet.net!not-for-mailReferences:
<3cc1759f_1@dnews> <5363cu0oo8bda21svg9l4gn2np05bc2l4d@4ax.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10d0fc,2292e28121a1cd3e X-Google-Attributes: gid10d0fc,public X-Google-ArrivalTime: 2002-04-22 02:37:58 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!supernews.com!priapus.visi.com!news-out.visi.com!hermes.visi.com!news.maxwell.syr.edu!diablo.theplanet.net!diablo.theplanet.net!news.theplanet.net!not-for-mail From: "WH" <ho200@wildduck.freeserve.co.uk> Newsgroups: borland.public.cppbuilder.multimedia Subject: Re: Audio Input Problem Date: Mon, 22 Apr 2002 10:34:00 +0100 Lines: 52 Message-ID: <aa0llj$aos$1@newsg1.svr.pol.co.uk> References: <3cc1759f_1@dnews> <5363cu0oo8bda21svg9l4gn2np05bc2l4d@4ax.com> NNTP-Posting-Host: modem-175.nickel.dialup.pol.co.uk X-Trace: newsg1.svr.pol.co.uk 1019468275 11036 62.136.27.175 (22 Apr 2002 09:37:55 GMT) NNTP-Posting-Date: 22 Apr 2002 09:37:55 GMT X-Complaints-To: abuse@theplanet.net X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200