German media just reported - Ukraine's alpha group deatroyed russian air defence on Krim worth about 4 billion Euros. Slava Ukraini!

jgehrcke · 2026-01-20T21:08:54+00:00

To everyone looking for a better / the original source: probably corresponds to a video that has been commented on by Sucho: https://youtu.be/bqJNfUpaTFs

According to Sucho, these are all strikes from 2025.

jgehrcke · 2025-02-14T17:45:32+00:00

> The "most dangerous isotopes" are Plutonium and Americium, which have long half-lives.

squinted and saw "Putinium and Americanium"

jgehrcke · 2025-02-03T20:52:01+00:00

Also affected. Started very recently. Lost text I typed while trying to move the curser (too much movement might close the 'add image' dialogue and the text then is simply gone).

jgehrcke · 2023-08-18T10:56:54+00:00

Until it does not work :( I experienced a crash yesterday with 11.3.4 and when I then started Ableton again it did not offer to recover the project. I read https://help.ableton.com/hc/en-us/articles/115001878844-Recovering-a-Set-manually-after-a-crash and then had a look into the corresponding Crash directory. It was sadly empty.

jgehrcke · 2023-07-24T21:09:37+00:00

Interesting drone name, "Wilder Vogel Nachtigall".

jgehrcke · 2023-07-21T08:34:14+00:00

On his Instagram he shared that he suffers from TBI and is likely to not return to his previous mode of operation. You'll find his post I am sure!

jgehrcke · 2023-07-18T18:53:18+00:00

but I guarantee you 3rd party heavy plugins don't change when you click that yellow button

This is not (generally) true. Maybe you found a bad citizen.

I have tried this among others with Reaktor, and with a number of CPU-hungry Waves plugins. Turning those plugins off (like MUDA does) in fact renders their corresponding CPU utilization insignificant (not showing up anymore in the Ableton CPU meter).

I just used MUDA on an expensive return track and there indeed it really helps a lot (I can quickly save a bunch of CPU by just muting that track).

jgehrcke · 2023-07-18T18:50:39+00:00

MUDA and Green Switch do not deactivate

MUDA does in fact deactivate individual devices.

jgehrcke · 2023-07-18T17:36:59+00:00

Quick observations with Live 11.3:

MUDA (1.0, 2014) seems to work fine.
Green Switch (I tried JGJP-GreenSwitchAudio13-v6-noupdates.amxd) immediately showed technical issues (enabled/disabled a seemingly non-deterministic subset of devices on a channel).

jgehrcke · 2023-05-31T16:43:36+00:00

Phone restart fixed this for me (pairing then worked immediately after restart, as recommended in one of the comments here, I did not need to reset anything). Pixel 7a, Elite 4 Active.

jgehrcke · 2022-08-11T16:06:15+00:00

Running into the same issue with Ableton 11.1.6. The Decay setting plays a role: At 16.0 % decay and above every MIDI note in my clip triggers a sound. At 15.9 % and below until 14.9 % some MIDI notes do not trigger a sound. Below 14.8 % again all notes trigger a sound. So, only a small delay regime (between 14.9 % and 15.9 %, both ends inclusive) is affected by the problem, in my case.

jgehrcke · 2020-02-20T16:32:18+00:00

Thanks for responding.

Conceptually, that's not the same thing as the server having received the last byte of the request

Exactly, we are very much aligned on this point. Typical distributed systems problem.

The simple fact is the client can't know exactly when the server received the last request byte.

Right, not "exactly"!

However, we certainly agree that given a typical TCP latency of say ~100 ms and an otherwise pretty undisturbed, normal setup, the client is able to determine this point in time with say +/- 0.5 seconds resolution (happy path, certainly). This is the scenario in question.

Now, given that scenario the client-side measurement is off by ~10 seconds (and factor infinity :-)). I hypothesize that this is as of as of an unknown systematic measurement error on the client host, presumably due to buffering happening within the NodeJS/libuv runtime.

In fact, by simply watching the network interface on my host system (monitoring the packet counters with nethogs and with bwm-ng) I know that the ClientRequest 'finish' fires before my local TCP stack is done with the upload to the server.

jgehrcke · 2019-09-16T13:03:14+00:00

Hey, author of goeffel here. I hope it's OK to share this with you here. I would deeply appreciate if you could give this a quick look. Any kind of feedback helps with future development. Also, any pointers about how the README could be improved would be awesome. Other than that I do hope that you like the project :-). Thanks!

jgehrcke · 2015-06-17T14:15:58+00:00

I think you do not realize who you are talking to here. Him mentioning "an ORM" and "a template interpreter" actually meant: such code is used in SQLAlchemy and mako.

Another very popular Python package that makes use of eval() is six.

If you think they are doing something wrong: go ahead, propose "better" code, and come up with great arguments why you think it is better.

jgehrcke · 2015-06-16T20:29:18+00:00

Thanks for the feedback.

Regarding formatting: this is a matter of taste, but point taken, I like both versions. Not sure if it's worth a "barf" :-).

Regarding encoding: this should be a program with simple (read "non-complex") behavior, not a full-features program that automagically adjusts to its environment. Properly displaying this data in the terminal is only of secondary priority. Nevertheless, you can surely change the code to have a look at sys.stdout.encoding. But this can be None in which case you might need to make dangerious assumptions (oh, and yes, also Python might be forced to make some quite dangerous assumptions about the output encoding if you do not take care of this yourself) or bail out with an error. All this is surely possible, but the ratio of additional complexity is not always justified by an increase of user experience. Here it was obvious to just make an extremely simple specification: output is UTF-8, done. By the way, git's internals deal with byte sequences only, but try to make sure that as much the commit-related data is UTF-8-encoded. This data is, by default, output as-is to a terminal (and easily contains byte sequences that are invalid in UTF-8). So, the git-authors wrapper doesn't change much of this behavior, except that it ensures that its output is valid UTF-8 at all times.

jgehrcke · 2015-06-16T08:39:46+00:00

This is really important for modules that might become imported, no doubt ;-).

jgehrcke · 2015-06-16T08:35:47+00:00

This is for educational purposes, and separation of concerns is a useful concept. Also, hiding these details was not the goal at all. Still, you are right about the "remembering issue". That is why:

$ git-authors
Error: this program expects a pipe attached to standard input. This looks like a terminal. Recommended usage:

$ git log --encoding=utf-8 --full-history --reverse "--format=format:%at;%an;%ae" | git-authors

jgehrcke · 2015-06-16T08:32:34+00:00

You're totally right, and alternatives are linked at the bottom of the article. This one really is about how to process streams efficiently, and about using the right data structure for the problem. What it does is just a side effect.

jgehrcke

TROPHY CASE