https://www.theregister.com/2024/07/16/jon_kern/

@sami There's tons of great immediate mode vector graphics frameworks all over the place these days. That could be also the reason...

Proactive misuse of MPE is the latest. Before I tried it sometimes as experiment. Now it is like the first thing I ever fill before trying anything else because of "tracker feeling". Also when MPE parameters have been allocated to the full note operators can give surprising results and have more dimensions.

With the overhauling modulation capabilities in #Bitwig, there's still need for manual curves, so I've taken this somewhat fixed strategy in order to not get confused about all options:

1. At most one manual curve per track and I always record it to mod-wheel. That way it translates from hardware to every plugin and have different meanings.
2. Rest of the automation and "wiggling" with modulation capabilities
3. Proactively (mis)using MPE parameters (pressure timbre etc) exactly to sequence automation. It feels pretty natural as it is like note effects in trackers. Like in a bass I might map pressure to subtone, so that it can be taken away while harmonics are kept in same voulme.

Sometimes modulation crap becomes too convoluted. In those situations I make a new track and record the curve there as. #MIDI CC 1 (modwheel).

Have been a bit with confused for couple of years how and when, when there is lot of options, but this is now what I'm converged into.

#MusicProduction

Everything was clipping in every patch I've done for that time now that I checked :-) Now I also know what to check and where in the future, and hopefully start to get out some actually usable sounds This is why switching DAW is not something that you want pursue too often. Every DAW have few of these. That said, still happy that I switched from #Ableton Live.

Took me two years to pay attention this setting for filters in the Poly and FX Grid devices of #Bitwig.

I've been wondering why they just don't feel or sound right but could not have pointed my finger. So I just put this it to +12 dB. and problem fixed.

With stock devices (not necessarily with some analog emulated plugins) sound does not destroy. If you add let's 20 dB gain boost and bring it down the same amount it should be perfectly recovered (assuming that signal path is "stock-only").

#MusicProduction

I started my own fork of #isync (or #mbsync)

https://codeberg.org/jarkko/isync

It has now couple of commits:

❯ git log --oneline -2
8ea62c9 (HEAD -> main, origin/main) fix: compile with -fno-lto
f5782aa refactor: open code FORCEASYNC far and near parameters

The first is the fix for crash in #Fedora. The second open codes FORCEASYNC:

diff --git a/src/common.h b/src/common.h
index 940e74d..22bd827 100644
--- a/src/common.hb
+++ b/src/common.h
@@ -120,7 +120,8 @@ BIT_ENUM(
        ZERODELAY,
        KEEPJOURNAL,
        FORCEJOURNAL,
-       FORCEASYNC(2),
+       FORCEASYNC_F,
+       FORCEASYNC_N,
        FAKEEXPUNGE,
        FAKEDUMBSTORE,
 )

I plan to do this for all of those, as it allows to cut some slack out from bit_enum_get.pl. That will lead to a roadmap where eventually the whole ugly script can be rendered out replaced with BIT_UL macro from kernel (msync is GPL 2.0 licensed).

There is also a #zig branch but before build can be defined properly the C codebase first needs to be made sound in terms of the build. Then it is relatively easy task to repeal and replace main.c with main.zig.

#email

That said, file path complete in vim is great (C-x and f) if that is considered as auto-complete :-)

Right and BTW I use ctags [not lsp] ;-)

@oherrala It is still better than auto-complete lottery, Internet forums and ChatGPT ;-)

The only #Rust tutorial you ever need is:

cargo doc --open -p <crate>

This opens documentation in the web browser for any crate that a project might be using.

Example would end up opening documentation for env_logger:

cargo add env_logger
cargo doc --open -p env_logger

#rustlang

#audija #kickdrum is really a game changer plugin. E.g. can resize the window freely. There is also 2.0 upcoming.

And despite being simple it has added value to using stock plugins of a #DAW, given that EQ curve is calculated and thus does not cause phasing issues.

#musicproduction

Love this #YouTube channel: www.youtube.com/@ConsoleCowboys. So much useful and applicable content. Whoever #ConsoleCowboys is, I'm your fan.

@montar It is a mystery but people get upset and fork a lot these days.

Like I got EGLIBC fork from the past (despite I respect Ulrich Depper's amazing contributions to open source, cpumemory.pdf is still always at hand ;-)) but these days people in my opinion are way too sensitive and get upset way too easily.

I don't think Linux could have happened if world had worked like this 1991.

@montar It is a mystery but people get upset and fork a lot these days.

Like I got EGLIBC fork from the past (despite I respect Ulrich Depper's amazing contributions to open source, cpumemory.pdf is still always at hand ;-)) but these days people in my opinion are way too sensitive and get upset way too easily.

I don't think Linux could have happened if world had worked like this 1991.

@oleksandr @gromit @vbabka I'm looking into how I could possibly make it compile Zig by stealing ideas from https://dev.yorhel.nl/ncdu, which did such conversion (used to be a C project). If a few core data structures were a bit more robust and safe that would make a difference (but since zig is very interoperable with C no need to turn all things around).

I.e. first just replace main.c with with main.zig, autotools with build.zig and rewrite perl generator scripts in zig but no other changes. That makes it easier compilation job at least ("./autogen.sh && ./configure && ./make" vs "zig build"). And rename the program as "zmbsync" so that it does not name conflict with the Fedora package.

@lkundrak @ljs SUN employees doing pair programming

I still hate reading GAS syntax after all these years. I learned assembly with Turbo Assembler and Intel syntax, which I still think is so much more readable.

Just so that you know llvm-ir is the language tag for #LLVM #IR when formatting it for #Markdown. I did not know this but found it by trial and error.

@oleksandr @gromit @vbabka I made my own independent fork that I use from now on ;-) mbsync should almost never change to anything, and it is only 15 KSLOC program.

I have some ideas how to modernize it too a bit (to make it easier to maintain) so might work on that too. Got familiar with the code base thanks this bug.

@vbabka Thanks! I applied like wide array of places because you know economy is not doing too well, and ended up to this situation.