There's one killer feature in Serum that is pretty much non-existent in any other synth despite vast amount of plugins these days: render to osc. You can render one second of key press to wavetable. Then e.g. with something like #Polyend #Tracker you can use that wavetable to act as an filter and make effective use of wavetable mode given the limitations of the hardware. Serum and discoDSP Bliss 2 are essential plugins with hardware samplers and alike...

The first feature in #Kilohearts #PhasePlant that has made me turn into it more than #Serum is pretty cosmetic one: approachable way to modulate slope of an envelope.

E.g. with a bass patch for Serum I layer it with #Bitwig macro that has access to slopes through DAW interface but I cannot put it as part of preset. In Phase Plant I can have the macro within the preset.

#audio #musicproduction

@vbabka With TPM2, systemd-boot and FIDO2 logins you can pretty much set similar authority guarantees for machines at local premises, as you can do with SNP, TDX and SGX. Confidential computing is sort of like VPN but for computing, bringing attested remote resources. In appliances you could even do extra shielding by encrypting root and home partitions with different security policies.

Have been pretty happy how suddenly TPM2 has so much upbringing :-) When I implemented the support back in 2014 there was many years of with very few people paying any attention so this sudden interest has been totally unexpected. It is pretty de-motivating something that nobody wants to use.

@vbabka Something I just discovered anyway :-) I used Yubikey only for OpenPGP until very recently have started to use it for login into Google account etc.

Looking into pam_u2f.so for configuring #FIDO2 login,

Irritating thing #PayPal is that you can only add one hardware security key to your account.

@baptnz How does this connect to typst? I mean here the goal was to provide text paragraphs for typst document with arbitrary markup (not just links). I tried to use single bullet list also for the paragraph but that adds the bullet also to the main document (if I recall correctly). Just wondering if there is a simpler way to do same as I did, this was so far simplest way I found...

@liw If it is x86 I prefer Intel chipset, including GPU because Intel tends to enable Linux months before products hit the market. I.e. usually that kind of stack tends to be somewhat stress-free. This comes from ex-Intel employee but I think Intel has the best Linux team across the board when it comes to hardware companies :-)

@mpdesouza @monsieuricon @sj you can with "flatpak run" but yeah distrobox is definitely quick fix for this, thanks, had forgotten it :-) i mean it needs to be only "batch run" to update maildirs so not that inconvenient.

After couple of hours poking around I now know how to embed #typst markup from yaml to a typst document :-)

I’m working on resume made with typst (as I’m looking to find a new job by end of September), and in that I’m using #yaml file to separate presentation from the content. Job descriptions can involve links, and thus those entries need to be evaluated.

First observation was:

#eval(job.description, mode: "markup")

If mode-parameter is not defined, typst will try to parse the string as an expression (i.e. mode: "code" is the efault, which is feasible in this case.

Another problem was the use of the hash character for tags, which is used for comments in yaml.

I sorted that out by putting every description into double quotes after trying a few different approaches:

    description:
      "I first worked on Keystone Security Monitor for RISC-V by enabling it
      for CVA6 running on FPGA. This work was part of the EU funded
      #link(\"https://www.spirs-project.eu/\")[SPIRS project].
      It involved
      tuning the
      #link(\"https://buildroot.org/\")[BuildRoot]
      based embedded stack, and
      fixing various
      #link(\"https://github.com/keystone-enclave/keystone/issues/378\")[issues].
      in the OpenSBI firmware.
      For the second half of my contract I'm enabling Linux for the new SoC's
      developed by
      #link(\"https://sochub.fi/\")[SocHub project]."

The screenshot shows the end result.

Nothing too complicated but took some time to find working patterns so putting here as a #note for myself :-)

I've only recently discovered boot-time tracing using bootconfig and moved away from huge kernel command-line strings. This is the best tutorial on topic: https://www.youtube.com/watch?v=BjiC_a13e_k

@mpdesouza @sj @monsieuricon Yeah sure, I was not sure what to ask. I guess the thing to ask would be one dependency that at least suse does not seem to have: perl-Inline-C

OpenSUSE has perl-Inline and perl-Inline-Python packages only.

Flatpak package would be probably solution that would acceptable for most kernel developers because anyone can install it. The only glitch in that would be flatpak run prefix but that is not a big deal.

@mpdesouza @sj BTW, I went through all public inbox packages in OBS but none seem to work out of the box (tried locally both with osc and rpmbuild). I tried tune them various ways but without any mentionable success..

One working way would be probably to use OCI container, flatpak, appimage or something that containerizes all the perl shenanigans but gave up for the moment with this...

@sj @mpdesouza never heard but look worth of giving a shot!

BTW, thanks for the earlier busybox tip @ncopa! I might start using Alpine for testing x86 because for such a set n stone platform it is pretty efficient :-) I.e. the robustness that BuildRoot provides when working with SoC's, SBC's, FPGA's and that sort of stuff is not really required for x86.

For the record, for ad-hoc images I always use BuildRoot but it is nice to see also bigger features running as part of distribution kernel. In this case it is SGX cgroups which I have already smoked tested with kernel/busybox/notmuchelse style payload.

wondering that when compiling a Git tree that is packaged like distro kernel RPM packages for OpenSUSE is it enough to just point LINUX_GIT to a kernel tree clone?

I made this conclusion from: https://github.com/openSUSE/kernel-source/blob/master/scripts/linux_git.sh

But there's bunch of scripts so possibly something else needs also to be taken into account. I just thought that this is easier path to test a few patches vs using patch sequencing which would make more sense, if contributing to the downtstream kernel itself.

Cool story about 3M floppies https://spectrum.ieee.org/3m-floppy #floppy

@mpdesouza I've piped the pages a few times with wget, w3m and grep to check some info, ok maybe this does not count as "convenient" :-) does the job...

this would be something where rust port would be applauded given how many dependencies you need to process email properly...

@mpdesouza That said, I gotta say that I love the site's web design :-) Supported browsers include curl and wget. https://public-inbox.org/ #nojoke