Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Noisy\s+computer\s+line\s+in\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Noisy\s+computer\s+line\s+in\s*$/: 4 ]

Total 4 documents matching your query.

1. [RTTY] Noisy computer line in (score: 1): Author: Bill Straw via RTTY <rtty@contesting.com>; Date: Sun, 15 Jan 2017 16:16:56 +0000 (UTC); I am just running the AFSK simple set-up of computer line in / line out to K3 line out / line in. Didn't think I was having decoding problems. The other day I was using Google remote desktop to liste; /archives//html/RTTY/2017-01/msg00049.html (7,142 bytes)
2. Re: [RTTY] Noisy computer line in (score: 1): Author: Tim Shoppa <tshoppa@gmail.com>; Date: Sun, 15 Jan 2017 12:56:13 -0500; Make sure your computer isn't cranking the gain on the line in. Most shack audio line levels you want to keep at the 1V P-P level if at all possible. If you're attenuating down to sub-millivolts (mic; /archives//html/RTTY/2017-01/msg00050.html (8,530 bytes)
3. Re: [RTTY] Noisy computer line in (score: 1): Author: Kok Chen <rtty@w7ay.net>; Date: Sun, 15 Jan 2017 10:32:22 -0800; This probably happens more often than you think :-). I have many times received email that cocoaModem was not decoding well even with clean loud signals. I tell them to make sure the sound interface; /archives//html/RTTY/2017-01/msg00051.html (8,102 bytes)
4. Re: [RTTY] Noisy computer line in (score: 1): Author: Stanley Zawrotny <k4sbz.stan@gmail.com>; Date: Sun, 15 Jan 2017 15:59:12 -0500; You might bring this up in the RFI forum. Send RFI mailing list submissions to rfi@contesting.com To subscribe or unsubscribe via the World Wide Web, visit http://lists.contesting.com/mailman/listinf; /archives//html/RTTY/2017-01/msg00052.html (8,208 bytes)

Current List: 1 - 4
Page: [1]