LameXP complains about updates in 2020 on startup. #94
Comments
|
Sorry, this happens because current version is more than a year old. There should have been a new version by now 😔 Being "trapped" in the home office for ~1 year now doesn't exactly add to my motivation, but new version will be released soon™. In the meantime you can test the latest release candidate: Regards. |
|
Oh that's definitely no problem! I was just concerned that the "skip update" check button was actually broken. Thank you for the release candidate. I've installed it and I'll see if I can find any bugs for you. |
|
Well it IS a bug that both checking: Disable Sound Effects and Disable Update Reminder are completly ignored, because when skipping update a very annoying loud music plays through my system, volume is always very loud on my studio because we use low Db levels for high DR and all system sound are disabled for that reason, so LameXP usage is now forbidden because of that. |
|
The option to disable the "Update Reminder", which normally suggest checking for updates 14 days after the previous update check – never LameXP will contact the update server without the user's consent – is completely unrelated to the built-in "expiry date" after which old versions will more offensively ask for an update. You can not turn off the built-in "expiry date" in an existing binary, only build a "fresh" binary from the original source codes. And that is exactly the purpose. It is primarily a countermeasure against those annoying software sites that are still offering 5+ years old builds of my software as what they call the "latest" version 😨 Also, the "Disable Sound Effects" option not effecting all sounds has already been addressed in: |
|
Well, hope new version doesn't have any sounds when Disable Sound Effect is checked, update reminder it's not so intrusive, although maybe it should refrain to recheck for one week after no updates found. |
Unless I still missed some sounds, which I hope not, it should be exactly like that. You can check the latest test build, if you like:
The "Update Reminder" can be disabled, as always. Nothing has changed about this. The "expiry date" also still works as it used to – for the reason pointed out in my previous reply – except that the TTL has been increased from 12 to 15 months. Of course, if you use a "fresh" version, you won't even notice there is a built-in "expiry date" . |
|
It appears the yearly update check is triggers only if the year is different as I vaguely remember it activating in Jan 2020 but the build is Dec 2019? I would also suggest introducing a day difference check between the "forced update check" as if the program is used & closed repeatedly, it checks EVERY TIME the program is launched. |
|
I honestly don't see the point of this check to begin with. There's enough
trouble with commercial software becoming unusable due to abandonment by
companies. Why add a timer to this program?
I mean, it works perfectly fine for me and I've had no trouble with it
EXCEPT this constant update check...
Sincerely,
Jonathan
…On Fri, May 7, 2021 at 3:53 PM AzzaAzza69 ***@***.***> wrote:
It appears the yearly update check is triggers only if the year is
different as I vaguely remember it activating in Jan 2020 but the build is
Dec 2019?
I would also suggest introducing a day difference check between the
"forced update check" as if the program is used & closed repeatedly, it
checks EVERY TIME the program is launched.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#94 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AONC3X3XHODR5PNO3XCTR23TMOE5RANCNFSM4WAERVSQ>
.
|
I don't install RC or beta versions on my working PC. So as it is now, "Update Reminder" uncheck doesn't refrain expiricy date to trigger, I wil start using runasdate to circunvect this (IMO stupid) feature which also triggers annoying and imposible to disable sound. |
It has been explained before: Also, this is Free/Libre software. So anybody with the modest programming skills can grab the source codes and make their own build at any time (actually all you need to do is open the existing project in Visual Studio and press the "Build" button) . |
Well, fair enough. But the more people try out pre-release versions and help to find possible regressions, the more "stable" the next release will be for everyone. Also, you don't even need to "install"; just grab the ZIP and extract it anywhere you like. (you can easily throw away that directory afterwards)
As explained before, what you are talking about is not the "Update Reminder" – which can be fully disabled, as always – but the result of using an expired binary. It will be completely gone for you once a "fresh" version is released – which will be soon™. The real problem is that a new version was not available "in time". That is my fault, yes. Roast me! 😧 |
|
Hi Lordmulder, You wrote: "You can not turn off the built-in "expiry date" in an existing binary, only build a "fresh" binary from the original source codes. And that is exactly the purpose. It is primarily a countermeasure against those annoying software sites that are still offering 5+ years old builds of my software as what they call the "latest" version" So please change your mind and give us users the choice! Please redesign the software so that users can choose whether and how to be reminded that they are using an outdated version. As an option for those. who like to be reminded also with sound (but this should be selectable and deselectable!) It seems that I'm not the only one with this wish. I would spend some dozens of money to solve this issue. |
It makes clear to the user that what they have downloaded is long outdated. And that they probably should pick another "download" site next time – one that keeps its files up-to-date. Or, even better, just download from the "official" project site 😏 Another important point: If a user happens to download a build that is many years old from one of the many sites that are spreading such "ancient" builds, there is no guarantee the built-in update system still works after all those years. Sure, we have several update servers for redundancy, but who knows how many of them will still be in service in 5+ years, or for what unforeseen reason the auto-update system will break. Making ancient binaries "expire" after a reasonable amount of time is a fallback mechanism that ensures that the user will be encouraged to find a less outdated binary – regardless of what has happened, this will probably still work.
You don't need to compile from the source codes, if you don't like to! If you want to follow the latest development, you can just grab the latest development build – updated usually at least once per month, or whenever something noteworthy has changed. And if you are using a "stable" version, the next "stable" version should be available long before the previous one expires. (Yes, "should". Because, this time around, it didn't quite work out like I planned. There are a few more things I need to look into, but just haven't found the time/motivation yet. Sometimes real life kicks in, you know?)
I know that the option to disable the sounds did not effect all sound effects in previous releases. This has already been addressed for the upcoming release:
As explained before, the update reminder is completely optional and can be disabled. The "expiry" mechanism is a different thing, and would be pointless if it could be disabled easily. The expiry time has been increased for the upcoming release, though. Regards. |
|
The problem is that some of us only use Final releases. There's no way now to use a final release without receiving that LOUD warning (my monitors are usually at a VERY high volume). Maybe you should make a new final version identical to the previous one with a longer expire date. And PLEASE low all the levels at least 10dB. Thanks. |
It was never supposed to happen that you get that message - and cannot update to a new stable release. Also, as said before, in current version you can disable all sounds. (BTW: Maybe you should consider enabling the "smart volume" feature of your sound card 😏)
If the release of the next "final" version wasn't imminent, this would be an option. As things are, hopefully not needed. |
|
Professional Audio Soundcards do not have such a feature like "smart volume" since we do not want to listen to music that is compressed by some blackbox compressing algorithm. |
What comes under the link is too complicated for me. As a programmer, you may see it differently, but I prefer to invest my time in listening to music, making music and recording sound. |
Oh yes. I understand that. |
My "Sound Blaster Pro" sure does 🤣 Anyway, just switch to "direct mode" with one click, if you plan listening to a longer recording that has consistent volume.
(Still, for most day-to-day audio sources, like television, youtube, video calls, games, etc. pp. "smart volume" can be a lifesaver)
This is Github. So better get used to people pointing to the relevant commit when it comes to discussing problems and/or fixes 😰 Anyway, the takeaway is this: It already has been fixed (a while ago) in the current version. |
|
I too vote for removing this feature, since from user's standpoint this is simply a bug: option supposed to do A is not doing A, and option supposed to do B is not doing B. Simple as that, regardless of the rationale behind. I got the software right from github in 2019 IIRC, and I've been satisfied with it since. Because there were far too many cases of some various apps I've been using which were broken by an update, my default policy is to update software when I need it, not when it needs it; unless there are security updates. There is nothing worse than a broken workflow because a new version, and honestly, LameXP with two very apparent bugs doesn't really spark confidence: "yeah better not update, if those 2 checkboxes are not working who knows what is broken in next release? At least major functionality works, I can live with those". Now that I've read this thread I understand what's going on and I'll update, I'd just like to add another vote that this issue. EDIT: It claims I already have the newest version.... yeah. Please disable that in the next stable build ;) |
|
To everyone on this thread:
I would like to being by saying I understand the maintainer/author's point
of view on this matter: supporting old versions of software that are/could
be broken is a huge waste of time for software maintainers.
That said:
1. This is 2021. People know they have a responsibility to maintain their
own software/computer systems is now common knowledge among most people,
even if they don't do it.
2. I've spent hours, if not days, setting up virtual machines and
maintaining old equipment for not just myself but people around me because
software no longer works on newer systems or the licensing system is broken
thus disabling the software.
Examples:
A. Driver based PDF printing applications that became unusable on newer
OSes.
B. Various CAD applications that need hardware dongles.
C. Torrent software that crippled the free version to push people to buy a
newer commercial version.
D. Various professional image editing programs that will not be named are
just a few examples of this.
3. The USER, not the author of the software, assumes the risk by running
old and outdated software.
4. If the author wishes only to release their software and not support it
via forums/email, that is also the author's prerogative.
5. Any software bundled with ads, crypto mining, search engines or other
annoyances to generate profit for the authors eventually become crippled
over time leading to increased maintenance which is usually performed BY
PEOPLE WHO KNOW WHAT THEY ARE DOING BUT DON'T GET PAID FOR IT ANYWAY.
I, personally, started collecting software and keeping backups of
installation files from over 30 years ago. I still have software that only
runs on Windows 98, XP, or 32bit-only systems that I occasionally use.
That said: intentionally crippling software, especially open source
software, in ANY way, is irresponsible and is in opposition to what open
source software is supposed to be.
With all due respect.
Jonathan
…On Thu, Aug 5, 2021 at 3:47 PM Jarekks ***@***.***> wrote:
I too vote for removing this feature, since from user's standpoint this is
simply a bug: option supposed to do A is not doing A, and option supposed
to do B is not doing B. Simple as that, regardless of the rationale behind.
I got the software right from github in 2019 IIRC, and I've been satisfied
with it since. Because there were far too many cases of some various apps
I've been using which were broken by an update, my default policy is to
update software when I need it, not when it needs it; unless there are
security updates. There is nothing worse than a broken workflow because a
new version, and honestly, LameXP with two very apparent bugs doesn't
really spark confidence: "yeah better not update, if those 2 checkboxes are
not working who knows what is broken in next release? At least major
functionality works, I can live with those".
Now that I've read this thread I understand what's going on and I'll
update, I'd just like to add another vote that this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#94 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AONC3XZHUHJ6C3RZ7YWIAPDT3IXYXANCNFSM4WAERVSQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Pro Soundcards start here: https://www.thomann.de/gb/audio_interfaces1.html
And for many pro audio & musicians soundcards/audio interfaces this just won't work. Yes, you can tick "Loudness Equalization" but it will have just no effect since ASIO takes the most direct way from CPU to audio out.
😞 Sounds like "Eat or die bird!"
Did you just lower the volume of the badly artifacte-ringing jeopardy sound or did you replace it by a better und softer sound? Actually, I like the melody a bit, but in such poor highly compressed sound "quality" it is simply an insult to the ear.
|
|
https://lordmulder.github.com/LameXP
You need to fix your link on github...
…On Fri, Aug 6, 2021 at 12:16 AM highqualitymusic ***@***.***> wrote:
My "Sound Blaster *Pro*" sure does rofl
Pro Soundcards start here:
https://www.thomann.de/gb/audio_interfaces1.html
They use ASIO and it's annoying to do seven things to enable it (and this
is just the shortest way to do so!) and another seven steps to disable it -
each time!!! 🤮
1. Click self-made link to sound.cpl
2. Scroll down though several outputs
3. Select RME audio channel
4. Click Properties
5. Click Enhancements Tab
6. Tick Loudness Equalization
7. Click OK
(8. Click active window)
And for many pro audio / musicians soundcards / audio interfaces this
won't work. Yes, you *can* tick "Loudness Equalization" but it will have
just no effect since ASIO takes the most direct way from CPU to audio out.
ASIO is *the* common standard for all devices musicians, producers and
pro audio girls and guys do work with.
We would have to take another ten clicks to switch to WASPI or DirectSound
driver which causes quite a mess and clicks to all digital systems behind.
And another ten click to switch back.
This is Github.
So better get used to people pointing to the relevant commit when it comes
to discussing problems and/or fixes cold_sweat
😞 Sound like "Eat or die bird!"
Anyway, the takeaway is this: It already has been fixed (a while ago) in
the current version.
👍
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#94 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AONC3X3YGI6LXAV7JIADH7LT3KTNLANCNFSM4WAERVSQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
Fixed in 56ddb11. |
Can you clarify, where exactly did you find the "wrong" link? 😕 |
|
Sorry, https://github.com/lordmulder/LameXP
The link on the right side of the page points to
http://lordmulder.github.com/LameXP
…On Mon, Aug 30, 2021 at 4:50 AM LoRd_MuldeR ***@***.***> wrote:
https://lordmulder.github.com/LameXP
You need to fix your link on github...
Can you clarify, where exactly did you find the "wrong" link? 😕
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#94 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AONC3XZRTBZHGZ7HVKPQLIDT7KFRBANCNFSM4WAERVSQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Oh, I see. Fixed now. |
For some reason every time I start LameXP, it insists on checking for updates even though I've done so a dozen times this year. Disabling "check for updates" does nothing. It still insists on checking every time.
(Great software, by the way. Just the constant update check is annoying.)
The text was updated successfully, but these errors were encountered: