groovebasin

If you want to see a fun example of this build system in action, have a look at my ffmpeg fork which has the build system ported to zig build: https://github.com/andrewrk/ffmpeg Particularly interesting is the use of nasm as a package dependency, which is executed to compile many assembly files into object files, which are then linked into the ffmpeg static library. I'm using this package in a work-in-progress reboot of Groove Basin (a music player server) in Zig: https://github.com/andrewrk/groovebasin/tree/zig-pkg Point being that if you want to collaborate on the music player project, you don't need to screw around with a million system dependencies, it's just `zig build` and you're off to the races - no matter whether you are using Windows, macOS, or Linux. The zig build system is under heavy construction during this release cycle of

You are correct that I also asked other online communities this question. I wouldn't say I was trying to force a narrative. I was asking out of concern. I was especially unnerved after seeing the development graph on GitHub: https://imgur.com/M09Nkx9 Also seeing there were features that haven't been implemented for the last 6 years made me even less confident about the future of the project: https://github.com/ziglang/zig/issues/68 Even from this post: https://andrewkelley.me/post/full-time-zig.html Of all the Zig projects the author said he was going to work on: - https://github.com/andrewrk/groovebasin/tree/zig - https://github.com/andrewrk/genesis/tree/zig - https://github.com/andrewrk/clashos he never committed and did any of them.

I wrote a fairly similar library that additionally uses data from last.fm and pandora, and supports compiling by track similarity as well: https://github.com/gwicke/compilation I'm using it to power the auto-playlist feature in my fork of https://github.com/andrewrk/groovebasin, a node music player.

I wanted to see how one of my personal projects compared, so I looked at Groove Basin. Groove Basin [1] is an open source music player server. It has a sophisticated web-based client with the ability to retag, label, create playlists, stream, browse the library, chat with other users, upload new music, and import music by URL. I just checked the payload size of a cold load, and it's 68 KB. I'll just keep doing my thing over here. [1]: https://github.com/andrewrk/groovebasin

This is the first version of Ubuntu to ship with [GrooveBasin](https://github.com/andrewrk/groovebasin), a music player server I've been working on for 4.5 years.

After 4 months of hard work and joining both the Debian JavaScript Packaging team and the Debian Multimedia Packaging team, I have managed to get Groove Basin [1] accepted into Jessie [2], just in time for the freeze! [1]: https://github.com/andrewrk/groovebasin [2]: http://permalink.gmane.org/gmane.linux.debian.devel.changes....

This is a great link, thank you! I found a project someone is working on that seems really interesting: "Music player server with a web-based user interface" https://github.com/andrewrk/groovebasin

Currently no. But it's planned that it will: https://github.com/andrewrk/groovebasin/issues/30 All modifications to music files will be done in a separate temporary file on the same device and then rename(2) will be used to atomically overwite the old file. This way race conditions and power failure have no chance of corrupting the file.

I'm particularly interested in your opinions on tagging. Can you explain what most software gets wrong about tagging? Here's the plan so far, although it's not implemented: https://github.com/andrewrk/groovebasin/issues/30 The idea is that you might edit tags for a file which doesn't even support tags, such as AAC. So it would let you do that, and the changes would then be reflected in the DB. However we would also have a UI pane for "Suggested Library Fixes" or something like that. This would be things like moving files to their canonical location, updating incorrect duration tags, duplicate file detection, etc. It would also have suggestions like this: * These songs have tag edits that you have made but they cannot be saved. Do you accept this change? (Proposed change: wrap the file in a container format which supports tags)

What could I do to get my JavaScript game engine[1] listed on the JavaScript game engines showcase page[2]? Or my music player server[3] on the music showcase[4]? [1]: https://github.com/andrewrk/chem [2]: https://github.com/showcases/javascript-game-engines [3]: https://github.com/andrewrk/groovebasin [4]: https://github.com/showcases/music