I just released a Windows MIDI driver version of Timidity. datajake.braillescreen.net/uti…
As with the VSTi, it requires a set of Gravis Ultrasound patches in order to work. Once installed, a Timidity Configuration option will be in the Control Panel, and from there you can point the driver at the appropriate Timidity configuration file.
As with the VSTi, it requires a set of Gravis Ultrasound patches in order to work. Once installed, a Timidity Configuration option will be in the Control Panel, and from there you can point the driver at the appropriate Timidity configuration file.
![panel 1: quitting a terminal program isn't always easy
person (thinking): "I pressed Ctrl-C 17 times and NOTHING HAPPENED"
panel 2: ways to quit
Ctrl-C - the default
Ctrl-D - if you're at a prompt in a REPL >>>
q - if it's a full screen program
Ctrl-\ - sometimes works if Ctrl-C doesn't
kill -9 - the last resort
panel 3: how Ctrl-D works
programs that read input will usually have some code like this:
text = read_line()
if (text == EOF) {
exit()
}
Ctrl-D is how you send an EOF to the program ("I'm done!")
important: Ctrl-D ONLY works if you press it on an empty line
panel 4: how Ctrl-C works *
* unless your program is in "raw mode", we'll talk about that later
person: "ctrl-C"
terminal emulator: "ok, C is the 3rd letter of the alphabet, I'll write 3 to the tty"
OS terminal driver: ah, a 3, that means I should send the SIGINT signal to the current program
program: ooh, a SIGINT, I will [shutdown gracefully, immediately exit, ignore it, stop a subtask, etc]
* unless your program is in "raw mode", we'll talk about that later
panel 5: some programs have weird quitting incantations
for example every text editor (vim, nano, emacs, etc) has its own completely unique way to quit](https://fedi.ml/photo/preview/640/605679 "panel 1: quitting a terminal program isn't always easy
person (thinking): \"I pressed Ctrl-C 17 times and NOTHING HAPPENED\"
panel 2: ways to quit
Ctrl-C - the default
Ctrl-D - if you're at a prompt in a REPL >>>
q - if it's a full screen program
Ctrl-\ - sometimes works if Ctrl-C doesn't
kill -9 - the last resort
panel 3: how Ctrl-D works
programs that read input will usually have some code like this:
text = read_line()
if (text == EOF) {
exit()
}
Ctrl-D is how you send an EOF to the program (\"I'm done!\")
important: Ctrl-D ONLY works if you press it on an empty line
panel 4: how Ctrl-C works *
* unless your program is in \"raw mode\", we'll talk about that later
person: \"ctrl-C\"
terminal emulator: \"ok, C is the 3rd letter of the alphabet, I'll write 3 to the tty\"
OS terminal driver: ah, a 3, that means I should send the SIGINT signal to the current program
program: ooh, a SIGINT, I will [shutdown gracefully, immediately exit, ignore it, stop a subtask, etc]
* unless your program is in \"raw mode\", we'll talk about that later
panel 5: some programs have weird quitting incantations
for example every text editor (vim, nano, emacs, etc) has its own completely unique way to quit")
Erlend Sogge Heggen
in reply to The Matrix.org Foundation • • •congratulations!
> what might Matrix 3.0 bring? (…) Could it be switching to #MLS (or Decentralised MLS) for encryption?
That would be absolutely amazing as a top priority for v3
The Matrix.org Foundation
in reply to Erlend Sogge Heggen • • •keschi Θ
in reply to The Matrix.org Foundation • • •The Matrix.org Foundation
in reply to keschi Θ • • •@kescher Thanks for sharing your concerns. Our spec process requires proof and implementation before things get merged in, and we're not going to be shy about celebrating when a meaningfully improved UX, based on spec proposals that have stabilized and are on track for merging, is becoming available.
And we're ActivityPub-first in our approach to social in line with our values, but AP hasn't made the news recently in the same way – thus the editorial choice.
keschi Θ
in reply to The Matrix.org Foundation • • •Look, I am not discounting the improvements here at all. Especially Sliding Sync! A great thing to have.
But until it is part of the protocol, officially, it isn't.
And that editorial choice makes no sense, again, considering that Bluesky is not federated or decentralized at all currently, only could be made to be so in theory!
The Matrix.org Foundation
in reply to keschi Θ • • •@kescher Genuinely, thanks for sharing your thinking here. We've definitely heard from folks who pay close attention to the spec that the 2.0 comms centered on implementations land wrong for them.
No doubt we need to calibrate how we communicate about these things... Relatedly, we've been very glad to hear that our Governing Board is interested in helping us think about our outbound communications strategy!
Didek
in reply to The Matrix.org Foundation • • •For me, the biggest problem with Matrix ecosystem right now are servers not cleaning after themselfs.
I can wait for some features, but in the meantime servers I have struggle to survive because of Synapse's state_groups_state infinite grow while Condu(wu)it/Dendrite seems to be too risky bet because of unsure development speed.
The Matrix.org Foundation
in reply to Didek • • •183231bcb
in reply to The Matrix.org Foundation • • •The Matrix.org Foundation
in reply to 183231bcb • • •@183231bcb Glad to hear you're having a good experience there! And thanks for raising that – aside from availability in that mobile client, the improved UX is available in the develop/nightly builds of one web/desktop client.
That said, it's fair to say that's many people aren't going to use those at this time.
Given the length of the road we're traveling here, we're eager to celebrate incremental progress where we can 😅
The Matrix.org Foundation
Unknown parent • • •Laelia
in reply to The Matrix.org Foundation • • •I do however have a question, one of the biggest drawback for my friends to make the switch is the lack of basic chat features(Messages with images, Custom stickers, and so on) is there any news on that front?
The Matrix.org Foundation
in reply to Laelia • • •MSC2530: Body field as media caption by tulir · Pull Request #2530 · matrix-org/matrix-spec-proposals
GitHubamd
in reply to The Matrix.org Foundation • • •The Matrix.org Foundation
in reply to amd • • •feld
in reply to The Matrix.org Foundation • • •The Matrix.org Foundation
in reply to feld • • •hexaheximal
in reply to The Matrix.org Foundation • • •The Matrix.org Foundation
in reply to hexaheximal • • •Midgard
in reply to The Matrix.org Foundation • • •If a friend loses her device again without having recovery, she has to abandon her account. Better to be upfront about this than to leave her in confusion as to why she's "banned", so a client should say:
> You've successfully signed in. Before you can send and receive messages with this device, you need to validate it using another device or a recovery passphrase.
> If you lost all devices where you were signed in and do not have a recovery passphrase, you should create a new account.