• Re: How to maximize audio fidelity

    From J. P. Gilliver@3:633/280.2 to All on Sun Jun 29 12:07:13 2025
    ICBPbiAyMDI1LzYvMjggMTU6Mzk6MTQsIG1pY2t5IHdyb3RlOg0KPiBIb3cgdG8gbWF4aW1p emUgYXVkaW8gZmlkZWxpdHk/DQo+IA0KPiBTb21lIHByb2dyYW1zIGxpa2UgeW91dHViZSBh bmQgcmFkaW9tYXhpbXVzIHByb3ZpZGUgdm9sdW1lIGNvbnRyb2xzLCBhbmQNCj4gd2luZG93 cyBwcm92aWRlcyBvbmUuDQo+IA0KPiBUbyBtYXhpbWl6ZSBmaWRlbGl0eSB3aGlsZSBtYWlu dGFpbmluZyB0aGUgc2FtZSB2b2x1bWUsIGRvZXMgb25lIHdhbnQgdG8NCj4gYSkgRGVjcmVh c2UgdGhlIFdpbmRvd3Mgdm9sdW1lIGFuZCBpbmNyZWFzZSB0aGUgYXBwbGljYXRpb25zIHNl dHRpbmc/DQo+ICAgICAgYikgdG8gaXRzIG1heD8NCj4gICBjKSBJbmNyZWFzZSB0aGUgV2lu ZG93cyB2b2x1bWUgYW5kIGRlY3JlYXNlIHRoZSBhcHBsaWNhdGlvbiB2b2x1bWU/DQo+ICAg ICAgZCkgdG8gdGhlIFdpbmRvd3MgbWF4Pw0KPiAgIGUpIFNldCBib3RoIGluIHRoZSBtaWRk bGUgc29tZXdoZXJlPyAgV2hlcmU/DQoNCltdDQpMb29raW5nIHB1cmVseSBhdCB2b2x1bWUg Y29udHJvbHMgKGkuIGUuIGlnbm9yaW5nIHRoaW5ncyBsaWtlIGxvc3N5IA0KY29tcHJlc3Np b24gc3VjaCBhcyBtcDMgZXRjLiksIHRoZW4gY2FzY2FkZWQgKG9uZSBhZnRlciB0aGUgb3Ro ZXIpIA0KInZvbHVtZSBjb250cm9scyIgYXJlIGp1c3Qgc3VjY2Vzc2l2ZSBtdWx0aXBsaWNh dGlvbiBieSBhIGZhY3Rvci4NCg0KT25lIG9mIHRoZW0gYmVpbmcgYXQgZnVsbCBzY2FsZSAt IGRvZXNuJ3QgbWF0dGVyIHdoaWNoIG9uZSAtIHdpbGwgDQpjb250cmlidXRlIG5vIGRlZ3Jh ZGF0aW9uICh0aGUgZmFjdG9yIGlzIDEpLiBTbyBub3JtYWxseSwgZG8gdGhhdCAtIA0KdW5s ZXNzIHRoYXQgbWVhbnMgeW91IGhhdmUgdG8gc2V0IHRoZSBvdGhlciBvbmUgX3NvXyBsb3cg dGhhdCB5b3UgZ2V0IA0Kcm91bmRpbmctZXJyb3Igbm9pc2UuDQoNCkluIHByYWN0aWNlLCBh c3N1bWluZyB5b3UncmUgdXNpbmcgMTYtYml0IHJlcHJlc2VudGF0aW9uIG9yIGJldHRlciwg DQp5b3UncmUgdW5saWtlbHkgdG8gYmUgYWJsZSB0byBoZWFyIF9hbnlfIGVmZmVjdC4NCg0K SWYgeW91J3JlIHRhbGtpbmcgYWJvdXQgX3Byb2Nlc3NpbmdfLCByYXRoZXIgdGhhbiBhY3R1 YWwgbGlzdGVuaW5nLCB0aGVuIA0Kc2V0IGFsbCBzdGFnZXMgdG8gZnVsbCB2b2x1bWUgLSBv ciDDlzEsIG9yIHdoYXRldmVyIGl0IGNhbGxzIGl0OyB0aGF0IHdheSANCnlvdSdsbCBub3Qg bG9zZSBhbnl0aGluZy4gKElmIGp1c3QgY2hhbmdpbmcgbGV2ZWxzLCB5b3Ugd29uJ3Qgb3Zl cmxvYWQ7IA0KaWYgc29tZXRoaW5nIGlzIGFscmVhZHkgb3ZlcmxvYWRlZCBbY2xpcHBpbmdd LCB0aGVuIG11bHRpcGx5aW5nIGJ5IDEgDQp3b24ndCBtYWtlIGl0IHdvcnNlLCBhbmQgbXVs dGlwbHlpbmcgYnkgbGVzcyB0aGFuIDEgd29uJ3QgbWFrZSBpdCBhbnkgDQpfbGVzc18gZGlz dG9ydGVkLiBfU29tZV8gcHJvY2Vzc2luZyBhY3Rpdml0aWVzIC0gc3VjaCBhcyBzb21lIGtp bmRzIG9mIA0KZmlsdGVycyAtIF9jYW5fIHJlc3VsdCBpbiBhW24gZWZmZWN0aXZlXSBnYWlu IGdyZWF0ZXIgdGhhbiAxOyBpZiB5b3UgDQpmaW5kIHRoYXQgaXMgaGFwcGVuaW5nLCB0aGVu IHNldCBhIMOXLjUgc29tZXdoZXJlIGluIHRoZSBwcm9jZXNzLikgSWYgeW91IA0KaGF2ZSBz b2Z0d2FyZSB0aGF0IGhhcyBjb250cm9scyB0aGF0IGdpdmUgYWN0dWFsIGdhaW4gKG1vcmUg dGhhbiDDlzEpLCANCmRvbid0IHVzZSB0aGF0IC0gaXQgd29uJ3QgX2dhaW5fIGFueSBmaWRl bGl0eSwgYW5kIHVubGVzcyBpdCdzIGEgZmFjdG9yIA0Kb2YgYSBwb3dlciBvZiB0d28sIHdp bGwgX2luIHRoZW9yeV8gYWRkIHNvbWUgZGlzdG9ydGlvbiAtIHRob3VnaCBfaW4gDQpwcmFj dGljZV8gdGhpcyB3b24ndCBiZSBhdWRpYmxlLiAoT2J2aW91c2x5IGlmIHRoZSBmaW5hbCBy ZXN1bHQgZXhjZWVkcyANCmZ1bGwgc2NhbGUsIGkuIGUuIGNsaXBwaW5nLCB0aGVuIGV2ZW4g cG93ZXJzIG9mIHR3byBhcmUgdG8gYmUgYXZvaWRlZC4pIA0KSWYgeW91ciBmaW5hbCByZXN1 bHQgaXMgbG93IGxldmVsLCB0aGVuIGRvIGJvb3N0IGl0IC0gYnV0IG9ubHkgYnkgcG93ZXJz IA0Kb2YgdHdvLiAoR2V0dGluZyB0byBhYm92ZSBoYWxmIGZ1bGwgc2NhbGUgaXMgc3VmZmlj aWVudDsgdGhlIGxvZ2FyaXRobWljIA0KY2hhcmFjdGVyaXN0aWMgb2YgaHVtYW4gaGVhcmlu ZyBtZWFucyB0aGUgZGlmZmVyZW5jZSBiZXR3ZWVuIA0Kb3Zlci1oYWxmLWZ1bGwtc2NhbGUg YW5kIGFjdHVhbCBmdWxsIHNjYWxlIGlzIGJhcmVseSBhdWRpYmxlLiktLQ0KDQpKLiBQLiBH aWxsaXZlci4gVU1SQTogMTk2MC88MTk4NSBNQisrRygpQUwtSVMtQ2grKyhwKUFyQFQrSCtT aDAhOmApRE5BZg0KAA0KV3JpdGUgYSBxdWVzdGlvbiwgdXNpbmcgIndoeSIuDQoNCldoeT8N
    Cg==

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: 255 software (3:633/280.2@fidonet)
  • From Paul@3:633/280.2 to All on Sun Jun 29 23:47:28 2025
    On Sun, 6/29/2025 7:56 AM, Ed Cryer wrote:
    Ed Cryer wrote:
    micky wrote:
    How to maximize audio fidelity?

    Some programs like youtube and radiomaximus provide volume controls, and >>> windows provides one.

    To maximize fidelity while maintaining the same volume, does one want to >>> a) Decrease the Windows volume and increase the applications setting?
    b) to its max?
    c) Increase the Windows volume and decrease the application volume?
    d) to the Windows max?
    e) Set both in the middle somewhere? Where?

    Not every audio source says what its streams are, and years ago when I
    would copy the url from the browser url field and insert it into
    Radiomaximus, it only worked one time out of 3, iirc.
    OTOH, today WYPR.org has two streams and at least one works. But it
    gives two choices, https://wtmd-ice.streamguys1.com/wypr-1
    and https://wtmd-ice.streamguys1.com/wypr-1-mp3

    The webpage doesn't say which would be better, and I can't hear a
    difference in this case, but in general
    f) Does an mp3 suffix imply the other is not mp3?
    g) Is mp3 likely to be better, worse, or the same as whatever the
    alternative is? What is the likely alternative?

    (BTW, WYPR Classical comes pre-loaded, but not the talk/news main
    channel. Somehow, the author gathers user-installed stations for his
    pre-load list, but I don't know if he does it stealthily or if each user >>> has to send it in somehow. I think I added WYPR news 10 years ago and
    he doesn't seem to know that I did.)


    I continue to recommend Radiomaximus, which comes preloaded with 100's
    of stations from around the world, and allows you to add your own, if
    you know the stream url, or can find out from the source. You can play
    one station while recording another (or two iirc). It also allows
    *timed* recording of your desired programs, which afaik nothing else
    does. You don't have to be there for it to start recording. It used to
    be free indefinitely if you didn't need timed recording but now I think
    it's only for 14 days. But the license which was not expensive lasts,
    so far, for ever. Raimersoft has 2 other similar products, Tapinradio
    and RarmaRadio. When I looked into it 10 years ago, I thought
    Radiomaximus had a better array of features and he's expanded them. ,
    but he still has the other two.

    BTW2. all the NPR stations have phone apps (well, not WAMU) but the WYPR >>> app has within its app Play on Demand of every individual NPR radio
    program, like the New Yorker Radio Hour and it might well still have
    Cartalk, even though there are no new episodes.

    I've often come across this problem. My hearing isn't too good, and I often use a hearing aid.
    The best I've found is to use a graphic equaliser, and just play with it until I get it right.
    These days, though, GEs aren't too prevalent in apps; but the older versions might be useful.
    You can raise or lower higher frequencies or lower frequencies. I like to start with everything on the middle line, and take it from there.

    Ed

    Try this Open Source program.
    Some people report a trojan on it, but the supplier says it's a false positive; and I get no sign of malware here.

    https://sourceforge.net/projects/peace-equalizer-apo-extension/

    128 Reviews
    Downloads: 26,555 This Week

    Ed

    I see this in Device Manager, but there is no user-space GUI
    to operate it. There is a RealTek APO item and three files installed,
    but there seems to be no way to do anything with them. That's in Win11.

    *******

    I have a number of Win10 installs. On the Test Machine, only one of the
    Win10 installs (it's 22H2 as well), has the RealTek Equalizer.

    [Picture]

    https://i.postimg.cc/QxLB2vfX/Win10-Equalizer-Via-Old-Driver.gif

    The chances of someone managing to do that today, are slim indeed.
    There must have been a temporal hole, where somehow that sneaked in
    (maybe I reinstalled it in the right moment).

    That's because, normally, Microsoft has been replacing items like that,
    with the "bland version".

    The picture has Asus branding, and the motherboard claimed to have
    some beginner level of Dolby for the sound (it's a software effect,
    but it keys off some PNP info to get enabled). That should not have
    anything to do with the Equalizer, which is a RealTek Equalizer and
    not a Dolby product.

    There are some newer sound hardwares, different than HDAudio,
    which also have effects as part of the "package", but the driver
    process is just as flaky and un-satisfying.

    While I can make you a picture like that, a fat lot of good it will do.

    Paul



    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From J. P. Gilliver@3:633/280.2 to All on Mon Jun 30 05:54:13 2025
    T24gMjAyNS82LzI5IDIwOjIwOjQxLCBtaWNreSB3cm90ZToNCltdDQoNCj4gSSBoYXZlIHRv IGFzay4gIFdoeSB3YXMgdGhlIGZpcnN0IHBvc3QsIHJlcGx5aW5nIHRvIG1lLCBsZWdpYmxl IGFuZCB5b3VyDQo+IG93biByZXBseSB0byB5b3Vyc2VsZiwgYWN0dWFsbHkgeW91ciBuZXh0 IDMgcG9zdHMgaW4gdGhpcyB0aHJlYWQsDQo+IHJlcXVpcmVkIHNvbWUgc29ydCBvZiBjb252 ZXJzaW9uIGZvciBtZSB0byByZWFkIGl0L3RoZW0uDQoNCltdDQpUaGUgcHJvYmxlbSBfbWF5 XyBiZSBUaHVuZGVyYmlyZDsgdGhlcmUncyBhIGRpc2N1c3Npb24gaW4gdGhlIFRCIG5ld3Nn cm91cC4NCklmIHNvbWVvbmUgdXNpbmcgYSBtb2Rlcm4gdmVyc2lvbiBvZiBUaHVuZGVyYmly ZCB1c2VzIC0gb3IsIHBvc3NpYmx5LCANCnF1b3RlcyAtIGEgbm9uLUFTQ0lJIGNoYXJhY3Rl ciwgVEIgbm90IG9ubHkgKGNvcnJlY3RseSkgZGVjbGFyZXMgdGhhdCANCmZhY3QgaW4gdGhl IGhlYWRlciwgYnV0IGFsc28gKHVubmVjZXNzYXJpbHkpIGVuY29kZXMgdGhlIG1lc3NhZ2Uu IE90aGVyIA0KdXNlcnMgb2YgVEIgKGFuZCBzb21lIG90aGVyIGNsaWVudHMpIGRvbid0IGtu b3cgdGhpcyBoYXMgaGFwcGVuZWQsIGFzIA0KdGhlaXIgY2xpZW50IGF1dG9tYXRpY2FsbHkg ZGVjb2RlcyB0aGUgbWVzc2FnZTsgdXNlcnMgb2Ygb3RoZXIgY2xpZW50cyANCnNlZSBsaW5l cyBvZiBjb2RlLg0KDQpJdCBpcyBob3BlZCB0aGF0IHNvbWUgZnV0dXJlIHZlcnNpb24gb2Yg VEIgbWF5IG5vdCBkbyB0aGlzLg0KDQpUaGF0IG1heSBub3QgYmUgdGhlIGNhdXNlLCBvZiBj b3Vyc2UsIGJ1dCBpdCBzb3VuZHMgbGlrZSBpdCBmcm9tIHlvdXIgDQpkZXNjcmlwdGlvbi4N Ci0tIA0KSi4gUC4gR2lsbGl2ZXIuIFVNUkE6IDE5NjAvPDE5ODUgTUIrK0coKUFMLUlTLUNo KysocClBckBUK0grU2gwITpgKUROQWYNCgANClRoZXknZCBuZXZlciBoZWFyZCBvZiBtZTsg dGhleSBkaWRuJ3QgbGlrZSBtZTsgdGhleSBkaWRuJ3QgbGlrZSBteSANCnNwZWVjaDsgdGhl eSB0dXR0ZWQgYW5kIGNsdWNrZWQgYW5kIGxvb2tlZCBhdCB0aGVpciB3YXRjaGVzIGFuZCAN CmV2ZW50dWFsbHkgSSBzYXQgZG93biB0byBhIHRodW5kZXJvdXMgbGFjayBvZiBhcHBsYXVz ZS4NCi0gQmFycnkgTm9ybWFuIChvbiBwcmVjZWRpbmcgRG91Z2xhcyBCYWRlciksIGluIFJU IDYtMTIgSnVseSAyMDEzDQo=

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: 255 software (3:633/280.2@fidonet)
  • From Paul@3:633/280.2 to All on Mon Jun 30 07:16:02 2025
    On Sun, 6/29/2025 3:20 PM, micky wrote:
    In alt.comp.os.windows-11, on Sun, 29 Jun 2025 12:56:58 +0100, Ed Cryer

    Ed

    Thanks for the encouragement, Ed.

    Try this Open Source program.
    Some people report a trojan on it, but the supplier says it's a false
    positive; and I get no sign of malware here.

    https://sourceforge.net/projects/peace-equalizer-apo-extension/

    And for this. Very impressive. I'll try it.

    I have to ask. Why was the first post, replying to me, legible and your
    own reply to yourself, actually your next 3 posts in this thread,
    required some sort of conversion for me to read it/them.

    128 Reviews
    Downloads: 26,555 This Week

    Ed

    This is the problem, where (we're not sure) some email composition
    setting causes NNTP post processing to involve UTF-8 at some point.
    UTF-8 cannot be carried on a 7 bit channel, without body
    text BASE64 encoding. If Thunderbird had "measured" the text and
    noticed it was 7 bit clear, perhaps that encoding would not have
    been used. I think a 0x00 NULL in the body text, should also cause this.
    JP had that happen a few days ago.

    There seems to be some sort of processing like this going on, in TB...

    text --> HTML --> text (oops, this needs BASE64) --> POST

    When a legacy NNTP reader sees body BASE64, it typically has no BASE64 decoder. Very old ones, you would need to use "b64.exe" and convert from
    BASE64, back into a format you could view. The same happens if you were
    to look up Ed's post on HowardKnight, it shows as encoded BASE64 there as well.

    If viewed in Thunderbird, the post will look "normal", as it will auto-convert BASE64 in this case. Via its "mailnews" stack, it can apply the same transform it would use if that happened in an email.

    So far, no one has discovered any procedure (acceptable to a user),
    that will fix this. If we cannot reliably reproduce it (prepare
    a setup where it happens each and every time), then it won't be
    treated seriously in a bug report.

    Paul

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From micky@3:633/280.2 to All on Mon Jun 30 08:01:47 2025
    In alt.comp.os.windows-11, on Sun, 29 Jun 2025 20:54:13 +0100, "J. P.
    Gilliver" <G6JPG@255soft.uk> wrote:

    On 2025/6/29 20:20:41, micky wrote:
    []

    I have to ask. Why was the first post, replying to me, legible and your
    own reply to yourself, actually your next 3 posts in this thread,
    required some sort of conversion for me to read it/them.

    []
    The problem _may_ be Thunderbird; there's a discussion in the TB newsgroup. >If someone using a modern version of Thunderbird uses - or, possibly,
    quotes - a non-ASCII character, TB not only (correctly) declares that
    fact in the header, but also (unnecessarily) encodes the message. Other

    Seems like it should be the other way around. If I'm some non-ASCII
    foreigner, I nee


    users of TB (and some other clients) don't know this has happened, as
    their client automatically decodes the message; users of other clients
    see lines of code.

    I never would have guessed this. Very interesting.

    It is hoped that some future version of TB may not do this.

    Now that I know who/what to blame, it doesn't bother me so much (and
    never bothered me much).

    That may not be the cause, of course, but it sounds like it from your >description.

    Yes it does.

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Tweaknews (3:633/280.2@fidonet)
  • From micky@3:633/280.2 to All on Mon Jun 30 08:06:20 2025
    In alt.comp.os.windows-11, on Sun, 29 Jun 2025 22:15:32 +0100, Ed Cryer <ed@somewhere.in.the.uk> wrote:

    J. P. Gilliver wrote:
    On 2025/6/29 20:20:41, micky wrote:
    []

    I have to ask. Why was the first post, replying to me, legible and your >>> own reply to yourself, actually your next 3 posts in this thread,
    required some sort of conversion for me to read it/them.

    []
    The problem _may_ be Thunderbird; there's a discussion in the TB newsgroup. >> If someone using a modern version of Thunderbird uses - or, possibly,
    quotes - a non-ASCII character, TB not only (correctly) declares that
    fact in the header, but also (unnecessarily) encodes the message. Other
    users of TB (and some other clients) don't know this has happened, as
    their client automatically decodes the message; users of other clients
    see lines of code.

    It is hoped that some future version of TB may not do this.

    That may not be the cause, of course, but it sounds like it from your
    description.

    I post through Betterbird. I see nothing of micky's complaints;
    everything looks hunky dory here.

    IIUC it's not that you see them. It's that I see them, using Forte
    Agent 5, which I guess does something, use non-ASCII characters?, that
    causes Betterbird to reply encoded. >>

    Ed

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Tweaknews (3:633/280.2@fidonet)
  • From Paul@3:633/280.2 to All on Mon Jun 30 08:56:18 2025
    On Sun, 6/29/2025 6:06 PM, micky wrote:
    In alt.comp.os.windows-11, on Sun, 29 Jun 2025 22:15:32 +0100, Ed Cryer <ed@somewhere.in.the.uk> wrote:

    J. P. Gilliver wrote:
    On 2025/6/29 20:20:41, micky wrote:
    []

    I have to ask. Why was the first post, replying to me, legible and your >>>> own reply to yourself, actually your next 3 posts in this thread,
    required some sort of conversion for me to read it/them.

    []
    The problem _may_ be Thunderbird; there's a discussion in the TB newsgroup. >>> If someone using a modern version of Thunderbird uses - or, possibly,
    quotes - a non-ASCII character, TB not only (correctly) declares that
    fact in the header, but also (unnecessarily) encodes the message. Other >>> users of TB (and some other clients) don't know this has happened, as
    their client automatically decodes the message; users of other clients
    see lines of code.

    It is hoped that some future version of TB may not do this.

    That may not be the cause, of course, but it sounds like it from your
    description.

    I post through Betterbird. I see nothing of micky's complaints;
    everything looks hunky dory here.

    IIUC it's not that you see them. It's that I see them, using Forte
    Agent 5, which I guess does something, use non-ASCII characters?, that
    causes Betterbird to reply encoded. >>

    Ed

    Forte Agent is not ready for that BASE64 variant. There are some other NNTP clients that have a similar problem. Some NNTP clients don't even know
    what UTF-8 is, and all they know is the code page representations.

    If a user picks up a copy of RN, that's an example of an *unthreaded*
    client, and trying to read NEWS in there would be suitably awful. They're
    not going to handle BASE64 properly either.

    The only option I can think of for Ed Cryer, is to use both THunderbird
    and Betterbird, do email-only in one program, do NNTP-only in the other program, each using its own profile.

    In the NNTP program, you turn off HTML composition (as it is not needed particularly for USENET and the policies for individual groups). And that should
    be enough to stop this. At a guess.

    Until we get a bug fix some day,

    Paul

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From micky@3:633/280.2 to All on Mon Jun 30 11:52:39 2025
    In alt.comp.os.windows-11, on Sun, 29 Jun 2025 18:56:18 -0400, Paul <nospam@needed.invalid> wrote:

    On Sun, 6/29/2025 6:06 PM, micky wrote:
    In alt.comp.os.windows-11, on Sun, 29 Jun 2025 22:15:32 +0100, Ed Cryer
    <ed@somewhere.in.the.uk> wrote:

    J. P. Gilliver wrote:
    On 2025/6/29 20:20:41, micky wrote:
    []

    I have to ask. Why was the first post, replying to me, legible and your >>>>> own reply to yourself, actually your next 3 posts in this thread,
    required some sort of conversion for me to read it/them.

    []
    The problem _may_ be Thunderbird; there's a discussion in the TB newsgroup.
    If someone using a modern version of Thunderbird uses - or, possibly, >>>> quotes - a non-ASCII character, TB not only (correctly) declares that >>>> fact in the header, but also (unnecessarily) encodes the message. Other >>>> users of TB (and some other clients) don't know this has happened, as >>>> their client automatically decodes the message; users of other clients >>>> see lines of code.

    It is hoped that some future version of TB may not do this.

    That may not be the cause, of course, but it sounds like it from your >>>> description.

    I post through Betterbird. I see nothing of micky's complaints;
    everything looks hunky dory here.

    IIUC it's not that you see them. It's that I see them, using Forte
    Agent 5, which I guess does something, use non-ASCII characters?, that
    causes Betterbird to reply encoded. >>

    Ed

    Forte Agent is not ready for that BASE64 variant. There are some other NNTP >clients that have a similar problem. Some NNTP clients don't even know
    what UTF-8 is, and all they know is the code page representations.

    If a user picks up a copy of RN, that's an example of an *unthreaded*
    client, and trying to read NEWS in there would be suitably awful. They're
    not going to handle BASE64 properly either.

    The only option I can think of for Ed Cryer, is to use both THunderbird
    and Betterbird, do email-only in one program, do NNTP-only in the other >program, each using its own profile.

    INteresting, but FTR, I wasn't asking anyone to fix this or to change
    anything. i was only asking why it happened. And now I know. It's no
    big deal. Because clicking on Reply converts it. (Which probably means I
    could make it read it even without clicking Reply, and I'm sure Ralph
    could tell me how, but it's no big deal.)

    In the NNTP program, you turn off HTML composition (as it is not needed >particularly for USENET and the policies for individual groups). And that should
    be enough to stop this. At a guess.

    Until we get a bug fix some day,

    Paul

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Tweaknews (3:633/280.2@fidonet)
  • From Philip Herlihy@3:633/280.2 to All on Mon Jun 30 20:39:26 2025
    In article <f8i06k9eeniggco9k0v4pmpvtr977a5q6i@4ax.com>, NONONOmisc07 @fmguy.com says...

    In article <68uv5kd6se8jn7cad6p1qlaocjccketn6a@4ax.com>, NONONOmisc07 >>@fmguy.com says...
    To maximize fidelity while maintaining the same volume, does one want to >>>a) Decrease the Windows volume and increase the applications setting?
    b) to its max?
    c) Increase the Windows volume and decrease the application volume?
    d) to the Windows max?
    e) Set both in the middle somewhere? Where?



    Certainly I've found that with some devices the max output of an app
    (e.g. YouTube) can overload an input stage somewhere - either the USB
    DAC that I use or the small speaker set I have connected. I just >>experiment, and amplifying a low output level doesn't seem to degrade
    the sound.

    So it wouldn't matter if use a or c?
    And maybe even b and d.


    It'll depend on the hardware you have, but on my Dell Vostro, I set
    Windows Media Player to about 2/3 max volume, and then adjust my
    speakers' volume to taste. With WMP on max output, I get that harsh
    sound that comes from an overload somewhere. You should experiment.

    --
    --
    Phil, London

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Philip Herlihy@3:633/280.2 to All on Mon Jun 30 20:45:39 2025
    In article <103q74h$15dk2$1@dont-email.me>, G6JPG@255soft.uk says...
    One of them being at full scale - doesn't matter which one - will
    contribute no degradation (the factor is 1). So normally, do that -
    unless that means you have to set the other one _so_ low that you get >rounding-error noise.

    In practice, assuming you're using 16-bit representation or better,
    you're unlikely to be able to hear _any_ effect.



    Not my experience. On my ageing Dell Vostro, if I have Windows Media
    Player set to maximum output there is clear "clipping", which gives the
    sound a harsh edge. Turn down the output control on WMP (compensating
    as needed with the speakers' volume control) and the distortion
    disappears.

    --
    --
    Phil, London

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From micky@3:633/280.2 to All on Mon Jun 30 23:32:53 2025
    In alt.comp.os.windows-10, on Mon, 30 Jun 2025 07:04:41 +0100, "J. P.
    Gilliver" <G6JPG@255soft.uk> wrote:

    On 2025/6/30 2:52:39, micky wrote:
    In alt.comp.os.windows-11, on Sun, 29 Jun 2025 18:56:18 -0400, Paul
    <nospam@needed.invalid> wrote:

    On Sun, 6/29/2025 6:06 PM, micky wrote:
    In alt.comp.os.windows-11, on Sun, 29 Jun 2025 22:15:32 +0100, Ed Cryer >>>> <ed@somewhere.in.the.uk> wrote:

    J. P. Gilliver wrote:
    On 2025/6/29 20:20:41, micky wrote:
    []

    I have to ask. Why was the first post, replying to me, legible and your
    own reply to yourself, actually your next 3 posts in this thread, >>>>>>> required some sort of conversion for me to read it/them.

    []
    The problem _may_ be Thunderbird; there's a discussion in the TB newsgroup.
    If someone using a modern version of Thunderbird uses - or, possibly, >>>>>> quotes - a non-ASCII character, TB not only (correctly) declares that >>>>>> fact in the header, but also (unnecessarily) encodes the message. Other >>>>>> users of TB (and some other clients) don't know this has happened, as >>>>>> their client automatically decodes the message; users of other clients >>>>>> see lines of code.

    It is hoped that some future version of TB may not do this.

    That may not be the cause, of course, but it sounds like it from your >>>>>> description.

    I post through Betterbird. I see nothing of micky's complaints;
    everything looks hunky dory here.

    IIUC it's not that you see them. It's that I see them, using Forte
    Agent 5, which I guess does something, use non-ASCII characters?, that >>>> causes Betterbird to reply encoded. >>

    Ed

    Forte Agent is not ready for that BASE64 variant. There are some other NNTP >>> clients that have a similar problem. Some NNTP clients don't even know
    what UTF-8 is, and all they know is the code page representations.

    If a user picks up a copy of RN, that's an example of an *unthreaded*
    client, and trying to read NEWS in there would be suitably awful. They're >>> not going to handle BASE64 properly either.

    The only option I can think of for Ed Cryer, is to use both THunderbird
    and Betterbird, do email-only in one program, do NNTP-only in the other
    program, each using its own profile.

    INteresting, but FTR, I wasn't asking anyone to fix this or to change
    anything. i was only asking why it happened. And now I know. It's no
    big deal. Because clicking on Reply converts it. (Which probably means I
    could make it read it even without clicking Reply, and I'm sure Ralph
    could tell me how, but it's no big deal.)

    However: the discussion in the TB groups suggests that it is only
    necessary to put something (UTF-8?) in the header, _not_ encode the
    body; there is hope that some future version of TB (and probably BB)
    will actually do this.

    That would be nice.

    Glad it's not bothering you though.>>

    Thank you.

    In the NNTP program, you turn off HTML composition (as it is not needed
    particularly for USENET and the policies for individual groups). And that should
    be enough to stop this. At a guess.

    Until we get a bug fix some day,

    Paul

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: Tweaknews (3:633/280.2@fidonet)
  • From Paul@3:633/280.2 to All on Tue Jul 1 08:05:26 2025
    On Mon, 6/30/2025 12:21 PM, J. P. Gilliver wrote:
    On 2025/6/30 11:39:26, Philip Herlihy wrote:
    []

    It'll depend on the hardware you have, but on my Dell Vostro, I set
    Windows Media Player to about 2/3 max volume, and then adjust my
    speakers' volume to taste. With WMP on max output, I get that harsh
    sound that comes from an overload somewhere. You should experiment.

    Interesting. When you say "WMP on max output", do you mean the slider in the WMP window? Does it still sound like an overload with that on max., but with the master volume control (near the clock) set to _less_ than max.?

    Put a calibrated tone into a .wav file and instead of listening
    to the output, put a multimeter on AC volts between Tip and Shield
    (which measures the Left channel output).

    That will tell you how close to overload you are.

    Some FOSS-like players, have the "up to 2X volume control" and
    potentially those can clip.

    OK, let's start our test.

    Audacity, Generate Tone, Amplitude 1.0, Frequency 440Hz, time 5 minutes

    Play, OS slider 100% = RealTek Audio out is 1.142 VAC (sounds about right... should be ~1.1 VAC)

    Now, close Audacity. Use the exported WAV, fire up WMP Legacy.

    WMP Legacy starts with its volume slider at 50%, while system tray is 100% right now

    Output = 0.630 VAC

    Now, push WMP control to 100% volume

    Output = 1.241 VAC (which is likely to be clipping)

    This is just a ballpark test, to see how close it is.

    To do a real test, you pass the audio output from one computer,
    to the Line In on a second computer, record in Audacity, and
    look for clipping in the sine wave samples.

    Some sound cards can manage more amplitude than the RealTek HDAudio.
    Sound Blasters for example, some of them were good for a bit more
    than that. But to me, a reading of 1.1 VAC is what I'm looking for
    as a max, when doing this with multimeter and not blowing
    out my eardrums doing a tone test on live speakers :-) Multimeter is
    a TrueRMS (which does not mean much when you look at some of
    the readings it has given at times).

    Paul

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Philip Herlihy@3:633/280.2 to All on Tue Jul 1 20:22:22 2025
    In article <103udn0$27r2q$3@dont-email.me>, G6JPG@255soft.uk says...

    On 2025/6/30 11:45:39, Philip Herlihy wrote:
    In article <103q74h$15dk2$1@dont-email.me>, G6JPG@255soft.uk says...
    One of them being at full scale - doesn't matter which one - will
    contribute no degradation (the factor is 1). So normally, do that -
    unless that means you have to set the other one _so_ low that you get
    rounding-error noise.

    In practice, assuming you're using 16-bit representation or better,
    you're unlikely to be able to hear _any_ effect.



    Not my experience. On my ageing Dell Vostro, if I have Windows Media
    Player set to maximum output there is clear "clipping", which gives the
    sound a harsh edge. Turn down the output control on WMP (compensating
    as needed with the speakers' volume control) and the distortion
    disappears.

    Ah, you're using external speakers, with a physical volume control (a
    knob, or up and down buttons)?

    Rotary dial. In another sub-thread I've been made to realise that I've overlooked the "system" volume control, which I'll have to play with nex
    time I play music!

    --
    --
    Phil, London

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Philip Herlihy@3:633/280.2 to All on Tue Jul 1 20:27:04 2025
    In article <103udhu$27r2q$2@dont-email.me>, G6JPG@255soft.uk says...

    On 2025/6/30 11:39:26, Philip Herlihy wrote:
    []

    It'll depend on the hardware you have, but on my Dell Vostro, I set
    Windows Media Player to about 2/3 max volume, and then adjust my
    speakers' volume to taste. With WMP on max output, I get that harsh
    sound that comes from an overload somewhere. You should experiment.

    Interesting. When you say "WMP on max output", do you mean the slider in
    the WMP window? Does it still sound like an overload with that on max.,
    but with the master volume control (near the clock) set to _less_ than max.?

    It's always good to have it pointed out you've overlooked something!
    I've ignored the "system" volume control, simply adjusting the WMP
    control and the speaker volume (rotary dial). Next time I play any
    music I'll experiment!

    Thinking about it more, I realise I don't really understand quite what's
    going on when clipping is detected. I'm using an external USB DAC
    (Cambridge Audio Dacmagic). So the signal is still digital when it
    reaches that - the speaker volume control is downstream (analogue
    signal). So how does a digital output (however loud it's coded to be) overload a downstream input stage? I wonder if this is a shortcoming in
    my DAC - though it certainly delivers better sound than the standard PC
    jack.

    --
    --
    Phil, London

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Paul@3:633/280.2 to All on Wed Jul 2 00:59:09 2025
    On Tue, 7/1/2025 8:36 AM, J. P. Gilliver wrote:
    On 2025/7/1 11:27:4, Philip Herlihy wrote:
    In article <103udhu$27r2q$2@dont-email.me>, G6JPG@255soft.uk says...

    On 2025/6/30 11:39:26, Philip Herlihy wrote:
    []

    It'll depend on the hardware you have, but on my Dell Vostro, I set
    Windows Media Player to about 2/3 max volume, and then adjust my
    speakers' volume to taste. With WMP on max output, I get that harsh
    sound that comes from an overload somewhere. You should experiment.

    Interesting. When you say "WMP on max output", do you mean the slider in >>> the WMP window? Does it still sound like an overload with that on max.,
    but with the master volume control (near the clock) set to _less_ than max.?

    It's always good to have it pointed out you've overlooked something!
    I've ignored the "system" volume control, simply adjusting the WMP
    control and the speaker volume (rotary dial). Next time I play any
    music I'll experiment!

    Thinking about it more, I realise I don't really understand quite what's
    going on when clipping is detected. I'm using an external USB DAC
    (Cambridge Audio Dacmagic). So the signal is still digital when it
    reaches that - the speaker volume control is downstream (analogue
    signal). So how does a digital output (however loud it's coded to be)
    overload a downstream input stage? I wonder if this is a shortcoming in
    my DAC - though it certainly delivers better sound than the standard PC
    jack.

    Unless it's been badly set up, a DAC should not produce clipping, unless fed with a digital signal that already includes clipping. It will produce a signal of a given voltage. That could still be more than whatever it is feeding is capable of accepting.

    Ideally, you need something that can produce a signal you can vary the output of, in an analogue fashion: ideally a signal generator, but maybe a CD player playing a test tone, with a volume control. Feed this into your "speaker" (amplified speaker system), and turn it up until you hear distortion; at that point, measure the output with a voltmeter (with it still connected to the speaker input); that is the maximum voltage the speaker can accept. (Doesn't matter if the voltmeter isn't "true RMS" or what frequency you use, though I'd suggest a low one - as long as you use the same signal for all measurements.) Then measure (again, while connected to the speaker load) the output of your DAC playing the same signal. If this is higher than the speaker can take, you've found the problem. (The solution would be a resistive dropper - or, always run the system volume turned down sufficiently; this latter in theory affects fidelity, but in practice I challenge anyone to be able to
    hear any degradation.)

    Do this when you have the house to yourself if you don't want to irritate people!

    If you can borrow an oscilloscope, that will show you fairly quickly if any signal you can get at is clipping, and let you find any relevant levels.

    Here is some clipping.

    [Picture]

    https://i.postimg.cc/GmZSBPBn/clipping.gif

    And that is sending a sine wave played in windows Media Player Legacy
    on one side of the room, to the Line_In on a second PC. The second PC
    is using Audacity to record the Line_In signal. Since the tone is 440Hz
    and the ADC is 44.1KHz, each (damaged) sine wave is sampled 100 times
    per wave. The screen representation fits a continuous curved line to the discrete dots, giving the impression of a much much higher sampling rate.

    One channel is clipping, the other is not, due to some Balance
    setting that is not in the center of the scale. That saves me from
    taking two pictures.

    A square wave, is a summation of sine waves. The components of the
    clipped waveform, now include at least two sine waves, and quite
    possibly a lot more harmonics of the fundamental (all with unique
    phase and amplitude to make the waveform what is is). These
    off-tones, serve to give the 440Hz clipped sine wave tone a
    "raspy sound that is not quite right".

    If I connected the Line_In level computer speakers to that signal,
    the volume knob on the speaker would need to be turned down. Maybe
    the computer speakers move the cones to full excursion, when only
    a 0.07 VAC input signal is received. By setting the volume pot to
    1/14th of full scale, I can avoid blowing the speakers. The volume
    pot could be log or linear, I did not take note of the details
    while building the kit. The speakers on the test machine, the knob
    is NEVER MOVED. It's what you do with quality pots :-) There is a pot
    for Left channel, and a pot for Right channel. In fact, the amp
    doesn't even have an on-off switch. It's always on.

    Paul

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Philip Herlihy@3:633/280.2 to All on Wed Jul 2 03:27:33 2025
    In article <1040ko8$2or9a$2@dont-email.me>, G6JPG@255soft.uk says...
    Unless it's been badly set up, a DAC should not produce clipping, unless
    fed with a digital signal that already includes clipping. It will
    produce a signal of a given voltage. That could still be more than
    whatever it is feeding is capable of accepting.




    I know what clipping sounds like - it's very characteristic. We have a
    street preacher who visits our town square who has a habit of belting
    out his story with something being overloaded, and the sound is even
    less appealing than his admonishments.

    My system WMP, PC, USB, DAC clips (irrespective of overall volume level)
    on some CDs if the WMP level control (and the system level) are at 100%.
    If I turn down the WMP control, I get clean sound, which I can then
    amplify to considerable levels without loss of quality. Yes, I'd be interested to know quite which stage is being overloaded.

    --
    --
    Phil, London

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)
  • From Paul@3:633/280.2 to All on Wed Jul 2 09:42:30 2025
    On Tue, 7/1/2025 1:27 PM, Philip Herlihy wrote:
    In article <1040ko8$2or9a$2@dont-email.me>, G6JPG@255soft.uk says...
    Unless it's been badly set up, a DAC should not produce clipping, unless
    fed with a digital signal that already includes clipping. It will
    produce a signal of a given voltage. That could still be more than
    whatever it is feeding is capable of accepting.




    I know what clipping sounds like - it's very characteristic. We have a street preacher who visits our town square who has a habit of belting
    out his story with something being overloaded, and the sound is even
    less appealing than his admonishments.

    My system WMP, PC, USB, DAC clips (irrespective of overall volume level)
    on some CDs if the WMP level control (and the system level) are at 100%.
    If I turn down the WMP control, I get clean sound, which I can then
    amplify to considerable levels without loss of quality. Yes, I'd be interested to know quite which stage is being overloaded.


    https://www.tenforums.com/sound-audio/208334-output-volume.html

    Using some of the info there, you can get a dB reading for the master Volume.

    [Picture]

    https://i.postimg.cc/wjdkbX12/sound-in-db-legacy-control-panel.gif

    But the quantification of sound and tracks is endless.

    https://www.audiosciencereview.com/forum/index.php?threads/ending-the-windows-audio-quality-debate.19438/page-19

    It seems the windows Way, is for Groove Music player to automatically
    fight against the user setting :-)

    Ultimately, the knob(s) on your external amplifier cascade,
    are the final arbiters of what you hear.

    *******

    In theory, you could use Stereo Mix (AKA "What you hear") as
    a means of monitoring the output. That takes a sample of the
    output and hairpins it back towards the ADC blocks. But that
    is no longer a neutral agent -- I tested Stereo Mix here, and
    I could not observe clipping quite the same way as using
    a second computer to monitor it.

    The HDAudio CODEC has gain and attenuation blocks (popular models
    you can find the hardware block diagram for this), in 1.5dB steps.
    If you could read out the settings on those, you could do a
    more deterministic calculation of the output range possible
    for given settings. But if WMPL is using "math for gain",
    by scaling the values by some float-value, then looking
    at the hardware control settings is useless. And that's the
    sort of thing VLC has been doing to various extents. Unless
    WMPL labels the slider properly, there's no way to know
    exactly what it is doing.

    On modern computers, the sound path is not necessarily
    HDAudio any more. Which will introduce a whole new set of
    variables to study. For example, some laptops have
    "digital amp chips" which have a "status", and your
    speakers can claim they are "Not Ready". Which I'm
    sure leads to customers shitting square bricks of excitement,
    when the speakers no longer work.

    Paul

    --- MBSE BBS v1.1.1 (Linux-x86_64)
    * Origin: A noiseless patient Spider (3:633/280.2@fidonet)