Talk:Crosstalk

Latest comment: 7 years ago by Kvng in topic PSNEXT merge

On a line edit

I remember getting crosstalk on a line when I was younger (1995) - does anybody know if this is able to happen any more? --^pirate 20:03, 23 April 2006 (UTC)Reply

Most certainly. I think the article should mention twisted-pair shielded cabling since this the most common method of combating crosstalk in cabling. One could even mention trace inductance on circuit boards. Rmcii 05:24, 6 May 2006 (UTC)Reply

95% of electronics is digital. It is weird that crosstalk in digital systems is ignored here. http://www.ivorcatt.co.uk/x147.pdf . Ivor Catt109.151.24.231 (talk) 11:04, 1 June 2016 (UTC)Reply

xtalk edit

The description of the Zurich club xtalk should be linked to from the disambiguation page, if at all. It's certainly not related to the electronics meaning of crosstalk. LouScheffer 14:15, 13 July 2006 (UTC)Reply

Tape edit

I wonder if we could add a paragraph on crosstalk on magnetic tape media - i.e. between the A-side and B-side of audio cassettes. — TheHerbalGerbil(TALK), 05:41, 13 April 2010 (UTC)Reply

You're talking about Print-through. I've added a See also link. -—Kvng 15:37, 5 January 2013 (UTC)Reply
No, print-through is a different phenomenon. Print-through is crosstalk caused by one winding of tape on a reel magnetising the ones above and below it (causes pre/post-echo). I'm pretty sure Herbal Gerbal is talking about spillover between sides (adjacent tracks) due to oversaturation (which, incidentally, can also cause print-through) or more commonly from misaligned record or playback heads.--MXocrossIIB (So, you were saying?); 20:03, 17 May 2015 (UTC)Reply

"Crosstalk" edit

The usage and primary topic of Crosstalk and cross-talk is under discussion, see talk:crosstalk (disambiguation) -- 65.94.43.89 (talk) 04:16, 23 May 2015 (UTC)Reply

PSNEXT merge edit

GeneC1 (talk · contribs) has proposed merging PSNEXT into this article. ~Kvng (talk) 14:33, 29 July 2015 (UTC)Reply

  Done ~Kvng (talk) 16:03, 27 July 2016 (UTC)Reply