A Audio, hi-fi and car audio  forum. Audio Banter

Go Back   Home » Audio Banter forum » UK Audio Newsgroups » uk.rec.audio (General Audio and Hi-Fi)
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

uk.rec.audio (General Audio and Hi-Fi) (uk.rec.audio) Discussion and exchange of hi-fi audio equipment.

10 metres audio cable going into PC = too long?



 
 
LinkBack Thread Tools Display Modes
  #2 (permalink)  
Old April 23rd 06, 11:37 AM posted to alt.engineering.electrical,uk.rec.audio,rec.audio.tech
Don Pearce
external usenet poster
 
Posts: 1,412
Default 10 metres audio cable going into PC = too long?

On Sun, 23 Apr 2006 03:13:33 -0800, (Floyd L.
Davidson) wrote:

(Don Pearce) wrote:
Just as your supposed "diagram" didn't show what a ground loop is,
your "evidence" isn't evidence.


Your posting was essentially an assertion that if you connect up a
microphone wrongly, it doesn't work properly. Now maybe you don't
understand why you shouldn't connect a microphone the way you suggest,
but it is a fact.

My web site evidence showed - and yes it did show - that when you know
what you are doing and connect everything up properly, there is no hum
when you touch a microphone body.


You haven't shown anything.

And I notice that, even though this URL has been posted twice before,
you don't have a word to say about it.

64.70.157.146/pdf/Bondingcableshields.pdf

*That* is evidence. And it clearly debunks virtually everthing you've
had to say in this thread.


You clearly wouldn't know evidence if it bit you on the backside if
you believe a pdf carries more weight than an actual sample.

And of course the stuff in the pdf has no bearing on the actual issue,
which is that a ground loop necessitates a loop in the ground. One
would have thought that even a limited skill in reading would have
made that clear.

And you still haven't explained why you think it is a good idea to
connect the screen to one side of the capsule in a microphone - you
certainly didn't think it was a stupid thing to do when you posted it
- just bitched about the "fact" (sic) that a microphone hums when you
grab hold of it.

All through this thread you have revealed that you don't understand
what is going on, you post diagrams that contradict your position, you
believe a single connection constitutes a loop, you think that hum is
signal, you introduce common mode DC - and I still haven't fathomed
what that had to do with anything.

Now please, go away and reflect on all of these things, forget the
"theory" you have learned and find out how the real world actually
works.

OK?

d

--
Pearce Consulting
http://www.pearce.uk.com
  #4 (permalink)  
Old April 23rd 06, 12:24 PM posted to alt.engineering.electrical,uk.rec.audio,rec.audio.tech
Don Pearce
external usenet poster
 
Posts: 1,412
Default 10 metres audio cable going into PC = too long?

On Sun, 23 Apr 2006 12:07:41 GMT, Roy L. Fuchs
wrote:

On Sun, 23 Apr 2006 11:37:05 GMT, (Don Pearce)
Gave us:

All through this thread you have revealed that you don't understand
what is going on, you post diagrams that contradict your position, you
believe a single connection constitutes a loop, you think that hum is
signal, you introduce common mode DC - and I still haven't fathomed
what that had to do with anything.


Noise IS a signal. If you knew what the word signal meant, you
would know that. ANY perturbation of a circuit is signal. You need
to learn that.

No - the wanted stuff is the signal - the rest is interference. Ever
heard of signal to noise ratio? You would call it signal to signal
ratio. Now that makes much more sense, doesn't it?

UNwanted signals get injected into circuitry all the time. With
audio circuit, we hear the result. That doesn't change the FACT that
it is still, nonetheless a signal.


No, noise gets injected into audio circuits when you don't know what
you're doing - like when you screw up the connections in a microphone
so it hums when you grab it. Have a listen to my MP3 and you will hear
just how wrong you are.

Now please, go away and reflect on all of these things,


Please grow the **** up. GTFU


GTFU? Did you put that bit in so you could read it as well?

forget the
"theory"


You're a goddamned idiot.

you have learned and find out how the real world actually
works.


I retract that... you're a goddamned retard.


A retard who, unlike you, can wire up a microphone so it doesn't hum
when you grab it. Seems to say it all, really.

OK?


**** off. YOU go back and read what he said, now that you know what
constitutes a signal.


I have explained that to you ad nauseam.

Now even from here, I can see you turning red - that vein on your
forehead is looking none too healthy, and all those burgers and fries
have probably raised your blood pressure to a dangerous level. I
wouldn't like give yourself a heart attack over this. Just take that
break, and go and think about it.

d

--
Pearce Consulting
http://www.pearce.uk.com
  #6 (permalink)  
Old April 24th 06, 09:03 AM posted to alt.engineering.electrical,uk.rec.audio,rec.audio.tech
Jim Lesurf
external usenet poster
 
Posts: 3,051
Default 10 metres audio cable going into PC = too long?

In article , Roy L. Fuchs
wrote:
On Sun, 23 Apr 2006 12:24:51 GMT, (Don Pearce) Gave
us:


No - the wanted stuff is the signal - the rest is interference. Ever
heard of signal to noise ratio? You would call it signal to signal
ratio. Now that makes much more sense, doesn't it?


Even with s/n ratio, in an engineering analysis BOTH the signal AND
the noise are signals.


As with various of the other statements I have seen in this thread on
various sub-topics, the above seems to me to be an over-simplification.
Interesting to speculate if in this case it is the above statement that is
ambiguous, or the ways in which the terms are actually used by engineers
are ambiguous... Perhaps this supports the argument that people become
engineers because they can't communicate very well... :-)

If you go back to some of the early sources [e.g. 1] then you can find some
that describe what is observed by the receiver/destination as something
like a 'received signal' which may include some 'noise' (and some
distortion or other systematic alterations).[2]

However the sources also routinely refer to 'signal to noise' ratio.

Shannon seems to resolve this by distinguishing between the 'signal' (i.e.
what the source transmitted) and the 'received signal' (i.e. what the
destination actually observed to arrive).

So if we were to use a term like 'received signal' in the above statement
it would essentially become either a tautology or self-referential as the
signal includes the noise. Thus the problem with the statement is that it
is unclear due to the ambiguous use of 'signal'. Hence, as often is the
case with such ambiguous statements, people start arguing about the meaning
when they are simply using different definitions which the ambiguity
allows. :-)

FWIW for the above reason, when teaching Information Theory/ Comms/
Instrumentation I tended to use another approach which is common in the
area. This is to say that a 'signal' means that the pattern (or part of the
pattern) *is used to convey information content*.

Thus in the context of communications a 'signal' means that the sender and
destination have to have pre-agreed the coding/modulation system to be
employed, and the meanings of the code symbols or distinguishable patterns.

In the context of a physical scientist making observations - e.g. an
astronomer observing what can be received from a distant radio galaxy - the
'signal means that the observed pattern will be used to obtain information
about the distant source.

The status of 'signal' then stems from the deliberation or requirement that
it conveys information on a defined basis.

In both contexts what distinguishes 'signal' from 'noise' is the
information conveyance the 'signal' provides, and that 'noise' tends to
obscure, or limit, or make uncertain, the information recovery. This then
helps make clear the actual meaning in practice of terms like 'signal to
noise ratio'. (Although there may then be hours of fun for all the family
as they argue about the distinction in this phrase between assuming
'signal' means either the intended/transmitted or the 'received' signal.
:-) )

Slainte,

Jim

[1] e.g. Shannon
http://cm.bell-labs.com/cm/ms/what/s...day/paper.html

[2] Probably best at this point not to start worrying about distortion as
being 'signal' or not... ;-

--
Electronics http://www.st-and.ac.uk/~www_pa/Scot...o/electron.htm
Audio Misc http://www.st-and.demon.co.uk/AudioMisc/index.html
Armstrong Audio http://www.st-and.demon.co.uk/Audio/armstrong.html
Barbirolli Soc. http://www.st-and.demon.co.uk/JBSoc/JBSoc.html
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 12:41 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.SEO by vBSEO 3.0.0
Copyright ©2004-2025 Audio Banter.
The comments are property of their posters.