toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

230
active users

#switching

0 posts0 participants0 posts today
Continued thread

But we can simplify this.

I'm not putting finished effects into standalone metal #boxes at this point; I'm #experimenting, not producing a product. So I have a simple #modular system I cooked up to connect arbitrary effects #experiments together. One of the things it does is handle the power-supply stuff, so each effect board doesn't need to do any of that. It just receives a nice 0V and buffered #Vcc (9V) it can rely on, along with a buffered 4.5V to use as a #bias voltage when AC coupling #signals, since this is a single-supply system.

So we can chop out all the power stuff from the schematic, which fills basically a ninth of the image - divide it into 3 rows and 3 columns, like the Brady Bunch intro, and the left-middle square is basically the power section.

But there's a bigger chunk we can strip out. Boss (and many other) pedals of the era frequently used "soft switching" to enable / disable the effect while playing. If you go back in time, real physical #switches were used, so the signal was actually totally disconnected from the effects circuitry when in the "off" position. This is called "true #bypass", as opposed to the soft switching.

#Soft #switching involves having two signal paths through the effect. One applies the characteristic effect, and the other basically just buffers the signal and bypasses the rest of the effect stuff. This is implemented with transistors and latches.

2/x

Continued thread

Solved! 🥳

This was a pretty "interesting" bug. Remember when I invented a way to implement #async / #await in #C, for jobs running on a threadpool. Back then I said it only works when completion of the task resumes execution on the *same* pool thread.

Trying to improve overall performance, I found the complex logic to identify the thread job to put on a pool thread a real deal-breaker. Just having one single MPMC queue with a single semaphore for all pool threads to wait on is a lot more efficient. But then, a job continued after an awaited task will resume on a "random" thread.

It theoretically works by making sure to restore the CORRECT context (the original one of the pool thread) every time after executing a job, whether partially (up to the next await) or completely.

Only it didn't, at least here on #FreeBSD, and I finally understood the reason for this was that I was using #TLS (thread-local storage) to find the context to restore.

Well, most architectures store a pointer to the current thread metadata in a register. #POSIX user #context #switching saves and restores registers. I found a source claiming that the #Linux (#glibc) implementation explicitly does NOT include the register holding a thread pointer. Obviously, #FreeBSD's implementation DOES include it. POSIX doesn't have to say anything about that.

In short, avoiding TLS accesses when running with a custom context solved the crash. 🤯

One thing I notice when reading about people's problems #switching to #linuxaudio is that their attempts/workflows often seem quite complex.
To avoid setbacks and frustration, my suggestion would be to start simple and accept limitations in the beginning, get to know the system better, and then aim for more complex setups as your know-how grows.

Cleaning house, have thrown out instagram, replaced spotify with deezer and I am now going through my old gmail account to see if there are any connections there before finally deleting it.

One problem though, I keep in touch with a bunch of old friends through messenger (facebook). They are reluctant for some reason to switch over to signal. Any tips on how to convince them without seeming like a nagging bore?

#Switching
from the bird to #BlueSky.
My main question is; WHY NOW ?

The main reason would have been at least two years ago, when Elon 'stepped in'.

Having been brainwashed by right wing propaganda...
NOW you've had enough so you switch to another hedge fund backed new platform? [meaning that at some point they want to see money]

I really don't get it.

💜 Is this the dawn of a new era? 💜

A day of testing FreeBSD as a potential daily driver.

Spoiler alert: I don't think I'm confident about a complete switch. Those who know me know I'm slow as hell, and it'll take time. But running a day under FreeBSD proves that it's possible for my workloads. And the first step has been done.

The first OS I used was DOS (well, if you don't count the Sinclair ZX80) and then I moved on to Windows. Then in 2009 I switched to macOS.

I found the hardware and software as trouble-free as could be and so I've stuck with macOS till now. But now, given Apple's current direction, I have been thinking since WWDC that it is time to switch again. Question is, to what?

I see people online who talk about how they'll never switch away from Apple for whatever reason. Good for them. I have no such compunctions. I will switch if the OS (or the company) no longer aligns with what I want.

I have been running both Linux and Windows on secondary machines for a while because I knew this day was coming. From a purely software perspective, given that it has the most software and supports most things I currently run, Windows seems to be the choice. But I'm not absolutely certain.

But it looks very much as if my next computer will not be a Mac.

#Apple #macOS #Windows #Linux #OS #Switching
a.farook.orgAkkoma

"Here, we studied the genomic architecture of DUP-TRP/INV-DUP by investigating the DNA of 24 patients identified by array comparative #genomic hybridization (aCGH) on whom we found evidence for the existence of 4 out of 4 predicted structural variant (SV) haplotypes..The point of template #switching in 4 samples was shown to be a segment of ∼2.2–5.5 kb of 100% #nucleotide similarity within inverted repeat pairs...inverted low-copy repeats act as recombinant substrates"

cell.com/cell-genomics/fulltex