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
  #13 (permalink)  
Old April 23rd 06, 07:07 PM posted to alt.engineering.electrical,uk.rec.audio,rec.audio.tech
Roy L. Fuchs
external usenet poster
 
Posts: 11
Default 10 metres audio cable going into PC = too long?

On Sun, 23 Apr 2006 15:07:55 GMT, (Don Pearce)
Gave us:

The reverse is so clearly the case that this barely merits an answer.


You're an idiot.
  #14 (permalink)  
Old April 23rd 06, 07:32 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 19:07:22 GMT, Roy L. Fuchs
wrote:

On Sun, 23 Apr 2006 15:07:55 GMT, (Don Pearce)
Gave us:

The reverse is so clearly the case that this barely merits an answer.


You're an idiot.


Oh dear! It really has got to you that I could prove my point so
easily while you have nothing.

d

--
Pearce Consulting
http://www.pearce.uk.com
  #15 (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
  #16 (permalink)  
Old April 24th 06, 04:42 PM posted to alt.engineering.electrical,uk.rec.audio,rec.audio.tech
Floyd L. Davidson
external usenet poster
 
Posts: 20
Default 10 metres audio cable going into PC = too long?

Jim Lesurf wrote:
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... :-)


Actually the language is probably a bit *too* precise for
non-engineers... and it gets worse too, because nobody had
mentioned "distortion" until your article.

First, here are correct technical definitions, from Federal Standard
1037C, for signal, noise, and distortion. (Just be aware that they
don't necessarily mean what one might thing!)

signal:

1. Detectable transmitted energy that can be used to
carry information.

2. A time-dependent variation of a characteristic of
a physical phenomenon, used to convey information.

3. As applied to electronics, any transmitted
electrical impulse.

4. Operationally, a type of message, the text of which
consists of one or more letters, words, characters,
signal flags, visual displays, or special sounds,
with prearranged meaning and which is conveyed or
transmitted by visual, acoustical, or electrical means.

Note that it is something that "can be used to carry information",
but there is no requirement that "information" either be present or
be useful.

The energy used for AC power *is* a signal. In this thread
*all* references to hum (which clearly *does* carry information,
otherwise we would not be able to hear it and distinguish that
it as unique) and to "power line" or "AC" are always correctly
referred to as a "signal", and may or may not be a "noise"
depending on the circumstance.

noise:

1. An undesired disturbance within the frequency
band of interest; the summation of unwanted or
disturbing energy introduced into a communications
system from man-made and natural sources.

2. A disturbance that affects a signal and that may
distort the information carried by the signal.

3. Random variations of one or more characteristics
of any entity such as voltage, current, or data.

4. A random signal of known statistical properties of
amplitude, distribution, and spectral density.

5. Loosely, any disturbance tending to interfere with
the normal operation of a device or system.

Each of those definitions carries some baggage, which usually
goes unnoticed until someone gets pedantic about technical terms.

Definition 1, the most precise and restrictive definition,
requires that the disturbance be "introduced", which implies
that it originate external to the circuit itself. That is the
difference between "noise" and "distortion", when the two are
differentiated. Generally though, a distortion is a noise, but
a noise is not necessarily a distortion. (Much as a signal
might be noise, but noise is not necessarily a signal.)

Definition 2 includes the term "distort". Definitions 3 and 4
use the term "random". And definition 5 is the more commonly
used catch all term.

distortion:

1. In a system or device, any departure of the
output signal waveform from that which should
result from the input signal waveform's being
operated on by the system's specified, i.e.,
ideal, transfer function.

Note: Distortion may result from many mechanisms.
Examples include nonlinearities in the transfer
function of an active device, such as a vacuum
tube, transistor, or operational amplifier.
Distortion may also be caused by a passive
component such as a coaxial cable or optical fiber,
or by inhomogeneities, reflections, etc., in the
propagation path.

2. In start-stop teletypewriter signaling, the shifting
of the significant instants of the signal pulses
from their proper positions relative to the beginning
of the start pulse.

Note: The magnitude of the distortion is expressed in
percent of an ideal unit pulse length.

The significance of the distinction between noise and distortion
might be lost on anyone but a design engineer, or perhaps a
theoretical physicist. At a maintenance and operations level,
it makes no difference.

If you go back to some of the early sources [e.g. 1] then you can find some


Ahem, Shannon is an "early source"???? Telecommunications as we
know it today was a hundred years old by the time Shannon began
publishing! And that has only been ~60 years now. I spend many
years working on equipment that was designed before Shannon...

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).


Shannon does not exclude noise from being a signal. He merely
uses the proper terms to distinguish between different signals,
with the realization that we have no interest in the information
carried by some signals... :-)

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.


What is commonly called "Signal to Noise Ratio" is commonly more
correctly called "Signal + Noise to Noise Ratio". In
circumstances where the ratios are greater than, say, 15-20 dB
or so, it is of little importance. Hence in typical
telecommunications voice channels it is rarely considered. On
the other hand in some data circuits and when applied to noise
figures for microwave radio receivers, where the ratios are much
smaller, the fact that the signal is actually Signal + Noise is
important.

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. :-)


Ah, but ignorance on the part of some is not the fault of those
who actually *are* using the term without ambiguity. Some
posters, Don Pearce being the most obvious, have not understood
the term and have been confused, and made efforts at confusing
others.

But that doesn't mean the terms are actually ambiguous.

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*.


Note the difference between something that "can" and something
that "is". Also, "information" seems to be misunderstood in
that definition... if you are suggesting that "hum" is a noise
that does not contain information, which is not the case. :-)

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.


That would not fit the typical way the term is used in practice by
people who work in the telecommunications field.

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.


Again, "can" is appropriate, but "will be" is going to cause a
misunderstanding.

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


That is too restrictive.

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


And it might well be the information carried by the noise signal that
makes the information from the desired signal uncertain...

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

Everyone who has any interest in effective communications should
study what Claude Shannon summarized. It is absolutely
fascinating to read.

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


Can it contain information?

Distortion can *always* be counteracted by the introduction of
an "error signal" which is opposite to the distortion.
Therefore it would seem that distortion is necessarily a signal
in all cases.

--
Floyd L. Davidson http://www.apaflo.com/floyd_davidson
Ukpeagvik (Barrow, Alaska)
  #17 (permalink)  
Old April 24th 06, 11:08 PM posted to alt.engineering.electrical,uk.rec.audio,rec.audio.tech
Ron Capik
external usenet poster
 
Posts: 4
Default 10 metres audio cable going into PC = too long?

"Floyd L. Davidson" wrote:

.....snip..


Jim

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


Everyone who has any interest in effective communications should
study what Claude Shannon summarized. It is absolutely
fascinating to read.


Wow, that brings back memories! The Shannon Day conference/celebration
was quite an interesting event. Now I'm going to have to dig through my old
files for that packet of papers.


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


Can it contain information?

Distortion can *always* be counteracted by the introduction of
an "error signal" which is opposite to the distortion.
Therefore it would seem that distortion is necessarily a signal
in all cases.


--
Floyd L. Davidson http://www.apaflo.com/floyd_davidson
Ukpeagvik (Barrow, Alaska)


I'd tend to say that distortion adds to noise side of the SNR, and
some can be corrected ...but *always* ? Let's say the distortion
is the result of clipping...

[ ...or maybe I've missed your point. ]

Later...

Ron Capik
--


  #18 (permalink)  
Old April 25th 06, 12:15 AM posted to alt.engineering.electrical,uk.rec.audio,rec.audio.tech
Floyd L. Davidson
external usenet poster
 
Posts: 20
Default 10 metres audio cable going into PC = too long?

Ron Capik wrote:
"Floyd L. Davidson" wrote:

Distortion can *always* be counteracted by the introduction of
an "error signal" which is opposite to the distortion.
Therefore it would seem that distortion is necessarily a signal
in all cases.

....

I'd tend to say that distortion adds to noise side of the SNR, and
some can be corrected ...but *always* ? Let's say the distortion
is the result of clipping...

[ ...or maybe I've missed your point. ]

Later...


Absolutely always. Recall that distortion is a known condition
resulting from the communications channel itself. The output is
known *before* the signal is input. (E.g., clipping is not
arbitrary, and produces a very specific error signal.)

Which of course is something Shannon describes, and uses in
examples, in "A Mathematical Theory of Communication".

--
Floyd L. Davidson http://www.apaflo.com/floyd_davidson
Ukpeagvik (Barrow, Alaska)
  #19 (permalink)  
Old April 26th 06, 04:47 PM posted to alt.engineering.electrical,uk.rec.audio,rec.audio.tech
Ron Capik
external usenet poster
 
Posts: 4
Default 10 metres audio cable going into PC = too long?

"Floyd L. Davidson" wrote:

Ron Capik wrote:
"Floyd L. Davidson" wrote:

Distortion can *always* be counteracted by the introduction of
an "error signal" which is opposite to the distortion.
Therefore it would seem that distortion is necessarily a signal
in all cases.

...

I'd tend to say that distortion adds to noise side of the SNR, and
some can be corrected ...but *always* ? Let's say the distortion
is the result of clipping...

[ ...or maybe I've missed your point. ]

Later...


Absolutely always. Recall that distortion is a known condition
resulting from the communications channel itself. The output is
known *before* the signal is input. (E.g., clipping is not
arbitrary, and produces a very specific error signal.)

Which of course is something Shannon describes, and uses in
examples, in "A Mathematical Theory of Communication".

--
Floyd L. Davidson http://www.apaflo.com/floyd_davidson
Ukpeagvik (Barrow, Alaska)


Seems I must have missed something.
From my reading of that paper it would seem that it is only the case
in a closed loop, discrete system when the (mythical) perfect observer
and error channel exist to generate said error correction.

With a continuous source Shannon noted: " ... Since, ordinarily, channels
have a certain amount of noise, and therefore a finite capacity, exact
transmission is impossible. "

From the subject line I would expect to be dealing with continuous
source "ordinary" channels.


Ron Capik
--








  #20 (permalink)  
Old April 26th 06, 05:55 PM posted to alt.engineering.electrical,uk.rec.audio,rec.audio.tech
Floyd L. Davidson
external usenet poster
 
Posts: 20
Default 10 metres audio cable going into PC = too long?

Ron Capik wrote:
"Floyd L. Davidson" wrote:
Ron Capik wrote:
"Floyd L. Davidson" wrote:

Distortion can *always* be counteracted by the introduction of
an "error signal" which is opposite to the distortion.
Therefore it would seem that distortion is necessarily a signal
in all cases.

...

I'd tend to say that distortion adds to noise side of the SNR, and
some can be corrected ...but *always* ? Let's say the distortion
is the result of clipping...

[ ...or maybe I've missed your point. ]

Later...


Absolutely always. Recall that distortion is a known condition
resulting from the communications channel itself. The output is
known *before* the signal is input. (E.g., clipping is not
arbitrary, and produces a very specific error signal.)

Which of course is something Shannon describes, and uses in
examples, in "A Mathematical Theory of Communication".

....

Seems I must have missed something.
From my reading of that paper it would seem that it is only the case
in a closed loop, discrete system when the (mythical) perfect observer
and error channel exist to generate said error correction.


That describes the theoretical "equivalent" implementation that
Shannon used to illustrate the point.

For a practical example, consider typical implementations of
equalizers to counter amplitude distortion. By measuring the
characteristics of the channel, and one time adjustment can be
made that corrects amplitude distortion. The equalizer
essentially introduces an equal and opposite error to the known
distortion introduced by other parts of the channel, with the
results that amplitude distortion is removed from the equation
(to the degree that the equalizer can actually match the
distortion).

With a continuous source Shannon noted: " ... Since, ordinarily, channels
have a certain amount of noise, and therefore a finite capacity, exact
transmission is impossible. "

From the subject line I would expect to be dealing with continuous
source "ordinary" channels.


(I'm not sure what you mean by a "continuous source" channel. I
more or less ignored your odd use of "discrete system" above, but
it suffers the same problem of being ambiguous in this context.
The two words should related to analog vs. digital, but I don't
think that's what you meant.)

Keep in mind that I merely said it "could" be done. I did *not*
say it was practical. Of course in many cases that is exactly
what is commonly done (e.g., with amplitude distortion as
described above), but in others it just is not practical for any
number of reason, one of which would be when enormous bandwidth
is required. For example, it would hardly make sense to reduce
quantization distortion with that method!

Regardless, the point is that distortion is a known change which
can always be predicted from the characteristics of the channel
when a known signal is applied to the input. The difference
between distortion and noise is that noise is external to the
definition of the channel, and cannot be calculated before the
fact. Hence there is no "known error signal" with noise, but
there is with distortion.

--
Floyd L. Davidson http://www.apaflo.com/floyd_davidson
Ukpeagvik (Barrow, Alaska)
 




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 07:10 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.