Courtesy of Stefan Westerfeld (who yet needs to create a Mastodon account), we now have fluidsynth2 support in master. And that means .sf3 ( + ) support.

Hm, C++14 supports lambda arguments of type 'auto', i.e. /nice/ function templates.
That allows me to throw away hundreds of lines of visitor code.

@macst3r Oh, knapp verpasst, einer meiner Freunde fährt gerade heute von Freiburg zu mir... ;-(

Eventuell kann er die aber in 2 Wochen oder so entgegen nehmen.

Noch ne andere Idee wäre der 36C3, kommst du da eventuell hin?

@macst3r Hi, hätte Interesse daran. Bin selber in Hamburg, wo liegen die denn rum?

Just came back from (industrial production fair in Hannover).

It's incredible how many products have to carry "" in the title or description these days, it's infected almost everything that deals with sensor or log data.
One presenter literally said "we also put 'blockchain' into the sensors software because the client WANTED it."

OTOH, it's nice to see that fabrication companies increasingly base their software stacks on and have learned to contribute back.

The source code is currently being rewritten in various places (CI, IPC, Build system, etc)

During the process, the various pieces of Beast documentation were converted to Markdown, structured and merged into a single cohesive document. Formulas can now facilitate (and ) and syntax highlighting was introduced. It is rendered to and and the was adjusted to closely match the Latex based PDF looks.

beast.testbit.org/#news

@federicomena The rounding errors introduced by the librsvg int arguments to query sizes for elements has caused me major headaches in the past.

@federicomena Well, It's UB, but happens to work most times, because C.

Staring into too much Rust lately has made you become sensitive about these things.

J/K ;-)

@mjog Maybe in a commercial context, but even there developers can only choose between tools that require *affordable* effort.

For FLOSS projects, it's usually a choice between a project that makes the developer life easy or no project. Personally, I rather use a program developed in an environment/language/framework I'm not familiar with than none at all.

Additionally, Web/Chrome/Electron work on all relevant devices these days, finding an unsuitable "operating environment" would be hard.

In
"Walking in my (Electron) shoes"
Gergely Nagy writes about having to deal with hate (!!) received from people for developing on .

Since I started moving to Electron, I've also had several interesting discussions (but not
"hateful" encounters) with people claiming that it must be slow or resource wasteful compared to native toolkits, both of which aren't really true in Beast's development context. Development itself is vastly superior though.

asylum.madhouse-project.org/bl

@federicomena

OMG, sorry, grabbed the link from static blog hosting at localhost... ;-)

Heh, now I discovered that Mastodon has "Delete & Redraft" as menu entry.

New Blog article…

Here’s my take on how "Mesh: Compacting Memory Management for C/C Applications" relates to GSlice:

GSlice considerations and possible improvements

testbit.eu/2019/gslice-conside

etc

@byllgrim
I see. Though it's also non-free, do you have an opinion on bitwig?

@byllgrim Is that about testbit.eu or testbit.org? Interesting, never seen that before.
And we don't have any Windows or Mac binaries there...

@byllgrim
I'm working on a complete makeover of beast. The new UI is written with Vue, and lots of pieces of the synthesis core are also redone.
Basically, the current gtk interface is nothing I can seriously recommend for productivity to someone.
That's also why Beast is kept at 0.x versions, once the makeover becomes usable, we'll enter 1.0 realm and have something much closer to a than current Beast.

@federicomena @alcinnz @hergertme

GLibc malloc was always on par with GSlice performance. GSlice was faster than non-glibc malloc() impls and it's more memory efficient, because it doesn't have to store boundary tags (2*size_t fields before each memory block that contain the memory size free() needs to know about).

True to the original slab magazine paper, it only recycles memory back to the kernel after a timeout of several seconds, a fact the Gitlab bug benchmarks don't reflect.

@alcinnz @federicomena
The GSlice allocator doesn't suffer from the catastrophic fragmentation described in the paper intro. Basically, it has per-thread aches for objects of the same size and it allocates and recycles objects of the same size from a single page, which prevents large fragmentation due to widely varying object sizes.

Show more
Mastodon

One of the first Mastodon instances, there is no specific topic we're into, just enjoy your time!