audacity v3.7.5

I've gotten a nice present with the recent version of audacity as presented in MX Linux my desktop distro of choice. The latest is version v3.7.7 just wait for the version the current one on in MX Linux is v3.7.5.

This version has new file format based features, which of course means the data files are not backward compatible

features since v3.6

• Master effects

• Audacity has master effects! Master effects are effects which apply to the entire project at once. More information can be found at Audacity Support: Using master effects & realtime effects.

• New compressor / limiter

• A new compressor and limiter have been added, replacing the previous versions.

• A gain reduction history has been added to these effects when they’re used as a realtime effect.

• Factory Presets suitable for a wide range of use cases for these effects have been provided by Vladislav Isaev and Marek Iwaszkiewicz, available via the Presets & Settings button.

• New themes

• Audacity has new and improved dark and light themes.

• switch between themes via Preferences -> Interface.

• The theme previously used still is around as Classic theme, and themes even older than that can be optionally installed as custom themes.

• Updated instructions on creating custom themes can be found here [link]

• Increased performance

• Audacity is now quite a bit snappier than before, especially when working on larger projects and on larger screens.

BUGS

Audacity has a long standing bug which is a buffer overflow error when you want to edit projects larger than 100 hours.

What happens is that the cursor loops at exactly 99:59:59 hours back to 00:00:00 hours effectively making editing beyond 100 hours impossible.

work around

What I do is simply record past the rollover, do everything live, meaning make no mistakes and chop the project into pieces if something has to be edited in post production. It's an annoyance but it works

I currently have a project which is aimed at 120 hours. I will keep you posted on the bug

Sources:

https://www.audacityteam.org/

https://www.audacityteam.org/faq/

https://plugins.audacityteam.org/

https://github.com/audacity/audacity-manual/releases

https://www.youtube.com/watch?v=f5TXPUOFH6A

#programming #audio #OpenSource #mathematics #physics #Lineair #Algebra #Audacity #editor #studio #production #vst #Linux #win64 #mac

@icedquinn @tknarr @navi sadly you are correct to the point that @fuchsiii jokingly says that:

#Win32 / #Win64 is the most stable #ABI on #Linux.

Personally, I am so frustrated about this situation that I mandate all applications for @OS1337 to ship their dependencies with themselves statically linked.

• Making it the problem of the Softwares' Maintainers!
  • If they use some stuff that doesn't allow that, then that's their problem…
• But then again I also statically compile against #musl because #GlibC is notorious for bricking shit with minor updates and anything #GNU seems to be run by folks who think: 'Just recompile it with the new version!' is a valid answer for their bullshit.

Why I love freeBSD

Additional data

I love FreeBSD because it doesn't rename my network interfaces after a reboot or an upgrade.

I shall dwell on what Stefano may mean as I have experienced this nightmare on the Linux path countless times

• using the if tools ifconfig ifup ifdown route and others on a LAN local network I repeat on a LOCAL network
• these tools were depreciated due to many issues with them, decades later (IIRC)
• no linux distro ever told me as a user that I needed to use replacements like ip
• I install a new version of a random distro (was on an ESR) and could not address the NIC's no iftools
• names of the NIC's were also replaced with cumbersome cryptic names, again, no fucks given no warning, I should have read the remarks in the GNU tool sources?
• WTF?!?

In that period I needed to enter the world of freeBSD
it was a chilibox experience with three main factors. Great docs, consistent tools logic and control governed by a central body of all, no guerilla tool changes which could disrupt server up keep flow. Just rest, ease and stability

Mind you I know BSD from before the chilibox, in fact I've played with BSD way before even Linux was in the balls of though of Torvalds

TLDR;

• choose BSD for your servers if you need consistent OS behaviour for decades
• choose Linux for bleeding edge changes and chances of breaking server (VMs) at regular updates
• choose win64 for love of being tortured
• choose mac to give away your aurum to the mac overlords
• choose the abacus for absolute stability

#freeBSD #Linux #ifconfig #ip #win64 #mac #aurum #IT #notes #ITNotes #dragas #programming #OpenSource #no #Linux #logic #analysis

VIM

Bram Molenaar

human programming

Background

It has come to my attention that my beloved VIM has become invested with LLM AI slop

The lead programmer is not following standard rules of coding anymore.

People have called him many things, but one thing is certain. The man is intelligent in the programming field and knows what he wants.

VIM needs LLM slop!

the programmer screams!

We don't think so!

we roar back!!!

A couple of programmers decided to create a hard fork of vim

VIM

• version V9.1.0 January 2K24
• last commit
• no LLM slop
• Pure Bram Molenaar level human crafted code

If you are categorically against large language model slop this is a project for you to support!

This is a hard Fork meaning that you cannot merge it back with me VIM main source line

Project

https://codeberg.org/NerdNextDoor/vim

Source
https://mastodon.social/@mrmasterkeyboard/116192873098653079

https://codeberg.org/NerdNextDoor/vim

#VIM #VIMMasterRace #programming #LLM #AI #hostile #environment #Amiga #BSD #freeBSD #netBSD #openBSD #ghostBSD #LINUX #mac #win64 #OpenSource #POSIX #technology #mathemathics #physics

While #ai slop is above atmosphere, you should know that, it still cannot fix win64assembly bugs easily (without human interaction). Hallucinations are high: it mixes 32bit and 64 bit together, still.
Sucks at MIPS. And if you do not be careful, it misleads you. You have to re-check flags! Do not forget.

#assembly #win64 #win32 #reverseengineering

Do you also want contribute to the Open Source movement?
Don't know where to start?

• write a new program in
• C++
• rust
• Python
• goLang
• hunt for bugs and submit patches in existing programs
• choose any OS you like freeBSD openBSD netBSD Linux (win64 is fine is you work mostly there) to code for

You can't write programs (yet)?

• We need translators of programs, many programs dont have enough locale translators for languages used in projects you also use
• Interfaces to contribute are easy to follow

Want one easy example?

You must (have) use(d) google voice
It's getting enshittified (makes more and more mistakes) and is NOT opensource

Common Voice by Mozilla

• Common Voice is Open Source
• I contribute there (years)
• You need a only phone
• I contribute in three languages (ES NL UK EN)

Don't just use Open Source software CONTRIBUTE!

Make the movement more powerful!

my stats are here (screencap)
What are yours?

https://commonvoice.mozilla.org/en/dashboard/stats

#OpenSource #Voice #Common #Voice #CommonVoice #programming #rust #C #CLang #goLang #go #Linux #BSD #freeBSD #openBSD #netBSD #mac #win64

Log4Shell

TIL about the breakdown of the Log4Shell shared library.

• Date of occurence
• 24 November 2K21
• location of programmer at home with his son logging into minecraft (which failed)
• this vulnerability had existed unnoticed since 2013
• it was privately disclosed to the Apache Software Foundation { Log4j is a project}
• discloser: Chen Zhaojun of Alibaba Cloud's infosec team
• date 24 November 2021
• exploit severety MAXIMUM
• It's simple to execute
• estimation of affect ration of 50% of the internet (many hundreds of millions of devices)
• vulnerability abuses Log4j allowing requests to arbitrary LDAP and JNDI servers
• that allows attackers to
• execute arbitrary Java code on server / client
• leak sensitive data

Innerworkings

• Log4j
• open-source logging framework
• enables programmers to log data within their applications
• can include user input
• is used ubiquitously in Java programs especially enterprise software
• Originally written in 2001 by Ceki Gülcü
• part of Apache Logging Services
• project of the Apache Software Foundation

Tom Kellermann, a member of President Obama's Commission on Cyber Security

• Apache is "one of the giant supports of a bridge which facilitates the connective tissue between the worlds of applications and computer environments

Affected commercial services

• Amazon Web Services {AWS}
• Cloudflare
• iCloud {Apple infrastructure}
• Minecraft: {Java}
• Steam {multi platform gaming}
• Tencent QQ### Wiz and EY sate that the vulnerability affected 93% of enterprise cloud environments

The Log4Shell vulnerability's disclosure received strong reactions from cybersecurity experts.

Cybersecurity company Tenable stated

• exploit is "the single biggest, most critical vulnerability ever## Ars Technica
• arguably the most severe vulnerability ever

Quote
Log4j is foundational software. This 20+ year-old Java logging library quietly powers system events in applications worldwide, like user logins and calculation results. But this small piece of software had quietly become a dependency in thousands of projects across the Java ecosystem.

Opinion & reaction

• I'm blown away by the events leading to the tornadoes & typhoons that followed shortly after in the OpenSource programming World
• Fifty percent of software was affected with 93% of enterprise software sub section
• Log4Shell is a critical infrastructure level shared library
• nearly everyone using java depends on it's functional I/O

Analysis

• why do most Open Source software users only contact programmers when bugs are detected?
• why do they (almost) never get compliments when it goes well?
• programmers burn out after a while and leave projects abandoned
• when you were a kid, your mom / dad / family complimented you on good results
• programmers need the same
• otherwise they will leave the projects

Open Source programming is a thankless job

• Zero cash influx
• no thank you's
• complaints even when software has long matured to stable levels
• entitled users
• threats to be Doxxed or worse

Be nice to Open Source programmers

• If you have following contact here on the Fediverse with one say thank you
• don't expect replies (esp when hundreds to thousands of followers are indicated)
• realize you either can't code programs of that caliber or don't want to invest the time
• I am lucky to have conversational contact ont the FediVerse with critical infrastructure programmers
• I always say thank you, because I know how hard it is to write software of that magnitude
• when I review their software, I am critical, but formulate my words and sentences in a manner I would want to read them if places were switched
• I am thankful first, thus send them Universal Love and Universal Energy
• My toot history stand for these statements (on my other Fediverse accounts)

Don't be a dick!

Be nice to programmers

Give them Love

Z

#Log4Shell #TIL #programming #data #Java #exploit #ZeroDay #technology #Enterprise #networking #OpenSource #POSIX #BSD #freeBSD #ghostBSD #openBSD #Linux #win64 #mac #history #reading

Sources:

https://github.blog/open-source/inside-the-breach-that-broke-the-internet-the-untold-story-of-log4shell/

https://en.wikipedia.org/wiki/Log4Shell