zynthian-sys VS nixpkgs

There's a bunch of people doing some pretty amazing synth builds with the Raspberry Pi -- the Zynthian crew [0] springs to mind.

Basically bring your own USB midi keyboard / controller - these tend to be cheap, but also engender very strong opinions, so there's some distinct advantages to having them as separate components, but with the synth box being much more portable than a laptop or desktop.

As to the Korg Wavestate - on this side of the pond (AU) it has an RRP of A$1500, though street pricing is around A$1000.

[0] https://zynthian.org/

Another option might be to get a Raspberry Pi and a USB audio interface to run Zynthian. Zynthian can be built from scratch with a TV, mouse and keyboard. You will need the USB audio for a line input from your amp. Heaps of DIY learning building your own Zynthian. You can scale up to the full hardware kit if you like what you see.

I suggest something Raspberry Pi based, Zynthian for example. It's the total opposite in this regard, allowing so much freedom and possibilities that it can get overwhelming.

There are several great RPi synth projects around, including mt32-pi, mini-dexed and samplerbox, but they're all intended for headless use (or with a tiny embedded display). The outlier in that respect AFAIK is Zynthian: https://zynthian.org/

Exactly opposite situation in my case - my Ubuntu Studio rig has been rock solid for tracking and many projects .. but the good news is that even if, for whatever reason, you can't qite grok things to be as productive as a pro Ubuntu Studio user (hint: you can) we have all the good things happening in ZynthianOS to explore, anyway - and this just wraps up the same essential goodies into a hardware device that is push-button-user friendly:

http://zynthian.org

And of course there are bleeding edge lessons learned, applied in things like monome, etc.

Zynthian is a good option but a bit hard to get your hands on in the silicon supply chain crisis.

Zynthian is a good one to add to this list.

You might get some more traction by integrating a Raspberry Pi in a eurorack adapter (or RPi Pico) with some sort of CV interface and leveraging an open source project like Zynthian.

Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...

I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...

NixOS uses a monorepo and I think everyone's love it.

I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.

Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.

https://github.com/NixOS/nixpkgs

In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].

[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...

[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...

True, but irrelevant -- _some packages_, _somewhere_, do depend on xz, which, if built, requires pulling the source from GitHub (see the default.nix: https://github.com/NixOS/nixpkgs/blob/nixos-23.11/pkgs/tools...)

It's not the vulnerability that's a problem right now (NixOS was protected by a couple of factors) but rather GitHub's hamfisted response.

That is the problem.

We’ve noticed that some users have been asking about how to use older versions of Terraform in their Nix setups [1, 2]. This is an example of the diverse needs of people and the importance of maintaining backward compatibility. We hope that nixpkgs-terraform will be a useful tool for these users.

I think whateveracct was referring to is this link:

https://github.com/NixOS/nixpkgs/blob/master/pkgs/developmen...

What that file is doing, is building a package, and it essentially is a combination of what Makefile and what RPM spec file does.

I don't know if you're familiar with those tools, but if you aren't it takes some time to know them enough to understand what is happening. So why would be different here?

#!/usr/bin/env nix-shell #! nix-shell -i bash #! nix-shell -p sops #! nix-shell -I https://github.com/NixOS/nixpkgs/archive/refs/tags/23.05.tar.gz source config.sh "$@"

NixOS just got tabbyml[1] which is built on llama-cpp. Working on systemsd services the weekend and updating latest tabbyml release which supports rocm in addition to cuda

[1] https://github.com/TabbyML/tabby

[2] https://github.com/NixOS/nixpkgs/pull/291744