pajackconnect
nixpkgs
pajackconnect | nixpkgs | |
---|---|---|
4 | 975 | |
76 | 15,753 | |
- | 2.8% | |
2.2 | 10.0 | |
8 months ago | 2 days ago | |
Shell | Nix | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pajackconnect
-
Perks of having a LinuxAudio setup!
PulseAudio: PulseAudio-ALSA-JACK Bridge (Comes out of the box with Cadence!) pavucontrol The rest of PulseAudio magic is done by playing with your default.pa/system.pa files ;)
-
PipeWire: The Linux audio/video bus
> Yeah making PulseAudio play nice with JACK seems to be tricky.
for me https://github.com/brummer10/pajackconnect has worked flawlessly... but I've switched to pipewire and I'm not looking back !
-
Making Sense of the Audio Stack on Unix
> whenever I read the Arch wiki about how to have PulseAudio and JACK coexist,
https://github.com/brummer10/pajackconnect
start jack, start pulseaudio, run pajackconnect, done
-
osx -> linux for personal use (bitwig, vscode, occasional game etc)
Jack + Qjackctl to set things like buffer size has actually been pretty seamless to me using Bitwig. Everything kind of just works once I setup a Pulse Audio -> Jack Bridge via Qjackctl and this script. I can get latency way down low in Bitwig, and then when I'm running normal apps and games the bridge works perfectly. Pipewire is exciting though, it's just pretty new so I haven't seen as much documentation or tools.
nixpkgs
-
Nix: The Breaking Point
I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.
As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...
- Maintainers Leaving
-
Air Force picks Anduril, General Atomics to develop unmanned fighter jets
https://github.com/NixOS/nixpkgs/commits?author=neon-sunset
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...
For example,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
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...
-
The xz attack shell script
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...
-
Debian Git Monorepo
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
-
From xz to ibus: more questionable tarballs
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...
What are some alternatives?
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
pipewire - Mirror of the PipeWire repository (see https://gitlab.freedesktop.org/pipewire/pipewire/)
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
ncmpcpp - Featureful ncurses based MPD client inspired by ncmpc
git-lfs - Git extension for versioning large files
cava - Cross-platform Audio Visualizer
pulsemixer - CLI and curses mixer for PulseAudio
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
mocp - Music On Console Player
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.