shairport-sync
Grav
shairport-sync | Grav | |
---|---|---|
59 | 84 | |
6,879 | 14,290 | |
- | 0.2% | |
8.7 | 8.5 | |
8 days ago | 10 days ago | |
C | PHP | |
GNU General Public License v3.0 or later | 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.
shairport-sync
-
Finamp: AirPlay 2 support
It's worth noting that shairport-sync exists. Perhaps it could be made easy by knitting some functions together?
-
Whole home sync'd rpi audio w plex, spotify, airplay
You want SnapCast. You'd run snapserver on your Linux box and snapclient on your Pi's. Snapserver has support for Airplay (via shairport-sync) and Spotify (via librespot). I recommend using MPD for your music library, as I don't think PlexAmp can output audio in a way that's useful for snapserver.
-
RaspberryPi Now Playing Dashboard using last.fm data and Airplay receiver
I use shairport-sync for airplay (https://github.com/mikebrady/shairport-sync), complete instructions via: https://blog.adena.dev/blog/apple-airplay-on-raspberry-pi-in-7-easy-steps
-
Curious to see if everyone pays full price for sonos products or are there ways to get discounts? Would appreciate any guidance to save $s.
If you’re interested, you might be able to get Airplay 1 & 2 support by running shairport-sync on your pi.
-
Review Request - First Circuit Design (Onion Omega 2 Stereo DAC Hat) | Any Suggestions Please
The plan is to run shairport-sync on the Omega 2 and have audio output to a 2x50w class d amplifier board.
-
Whole Home Audio - Design Help
To replace it, I've purchased in-ceiling speakers and a Control 4 Amp (C4-16AMP3-B) which I can control via the network. I plan on using shareport-sync for AirPlay and librespot for spotify as the sources to play music. 90% of the use for my whole home audio is for music.
-
Can anyone help me figure out how to use PulseAudio and ShairPort-Sync together to point AirPlay to a Bluetooth Speaker?
ShairPort-Sync allows my Mac to listen for a AirPlay with multiple instances available, each pointing to different settings as per this GitHub Issue, which would allow me in theory to run multiple AirPort plugs and output each to an Alexa. Rarely would I ever need to have them playing all at once, and at this point I don't really care about maintaining pure audio quality or latency. I just need to be able to get out of my office and move to the kitchen, then back to my office without needing to spend a ridiculous amount of time trying to move what I was listening to on my iPad into my Echo Show
-
How to build a raspberry pi dac
The benefit of the Pi is the open source software, in particular I use https://github.com/mikebrady/shairport-sync in order to turn it into an AirPlay 2 receiver, which I can stream to using my phone or laptop. It's my main way of sending audio to my hifi setup.
-
Airplay2 to multiple phone
The only option I know of would be to use multiple raspberry pi’s running Shairport-Sync. I’ve been using the airplay 2 version for about a year and it works great. You might be able to build a server and run multiple instances of shairport with multiple audio cards. https://github.com/mikebrady/shairport-sync
-
Has the Nest Audio been transitioned to Fuchsia?
So, after looking around, I realised that just like the Nest Hub 2nd gen, the Nest Audio also has a (sort of) exposed debug USB port. And these devices are (originally) running Linux. Since the Nest Hub 2nd gen has been jailbroken, I'm hoping that I can do the same on the Nest Audio, with a singular purpose: to inject a ShairPlay service, which would run parallel to the Chromecast services, which would allow me to use them as native AirPlay2 speakers.
Grav
-
Ask HN: What products other than Obsidian share the file over app philosophy?
There are flat-file CMSes (content management systems) like Grav: https://getgrav.org/
I guess, in some vague/broad sense, config-as-code systems also implement something similar? Maybe even OpenAPI schemas could count to some degree...?
In the old days, the "semantic web" movement was an attempt to make more webpages both human- and machine-readable indefinitely by tagging them with proper schema: https://en.wikipedia.org/wiki/Resource_Description_Framework. Even Google was on board for a while, but I guess it never saw much uptake. As far as I can tell it's basically dead now, both because of non-semantic HTML (everything as a React div), general laziness, and LLMs being able to parse things loosely.
-------------
Side thoughts...
Philosophically, I don't know that capturing raw data alone as files is really sufficient to capture the nuances of any particular experience, or the overall zeitgeist of an era. You can archive Geocities pages, but that doesn't really capture the novelty and indie-ness of that era. Similarly, you can save TikTok videos, but absent the cultural environment that created them (and a faithful recreation of the recommendation algorithm), they wouldn't really show future archaeologists how teenagers today lived.
I worked for a natural history museum for a while, and while we were there, one of the interesting questions (well, to me anyway) was whether our web content was in and of itself worth preserving as a cultural artifact -- both so that future generations can see what exhibits were interesting/apropos for the cultures of our times, but also so they could see how our generation found out about those exhibitions to begin with (who knows what the Web will morph into 50 years later). It wasn't enough to simply save the HTML of our web pages, both because they tie into various other APIs and databases (like zoological collections) and because some were interactive experiences, like games designed to be played with a mouse (before phones were popular), or phone chatbots with some of our specimens. To really capture the experience authentically would've required emulating not just our tech stacks and devices, among other things.
Like for the earlier Geocities example, sure you could just save the old HTML and render it with a modern browser, but that's not the same as something like https://oldweb.today/?browser=ns3-mac#http://geocities.com/ , which emulates the whole OS and browser too. And that still isn't the same as having to sit in front of a tiny CRT and wait minutes for everything to download over a 14.4k modem, only to be interrupted when mom had to make a call.
I guess that's a longwinded of critiquing "file over app": It only makes sense for things that are originally files/documents to begin with. Much of our lives now are not flat docs but "experiences" that take much more thought and effort to archive. If the goal is truly to preserve that posterity, it's not enough to just archive their raw data, but to develop ways to record and later emulate entire experiences, both technological and cultural. It ain't easy!
- Soupault: A static website management tool
- Grav is a modern open-source flat-file CMS
- Grav – A Modern Flat-File CMS Using PHP and Markdown
-
It Took Me a Decade to Find the Perfect Personal Website Stack – Ghost+Fathom
I took a more traditional approach, focusing on something that's "good enough", which in my case was a cheap VPS and an install of Grav: https://getgrav.org/
Some optional customization for page templates/fonts/CSS, some CI so I can build and deploy it inside of a Docker container, Matomo for analytics that respect privacy (which I already use elsewhere) and some additional web server configuration to hide anything interesting behind an additional login and I'm good. Maybe backups and uptime monitoring if I'm feeling brave, which is what most sites should also have (so copy + paste there).
All of that for under 100 euros per year (could also pay half of that if I didn't host anything else on the server), the blog has actually survived getting on the front page of HN once or twice and requires relatively little maintenance, at least a bit less than a proper install of WordPress, due to its larger surface area.
The best thing is that it's simple enough for me to understand how it works, to be able to move it anywhere as needed and use more or less plain Markdown for writing the blog posts. Here's a quick example of a recent post: https://blog.kronis.dev/articles/ever-wanted-to-read-thousan...
Now all that's left is to find motivation to write more, but at least 90% of my time doesn't go into tinkering with custom fancy solutions, no matter how much I'd love that. Then again, nothing wrong with the alternatives either: 400 euros might be perfectly worth it for some, whereas working with static site generators or even custom CMSes would be a fun experience for others!
- Grav: Modern, open-source, flat-file CMS
-
Is it possible to convert a WordPress site into a static site that can still be easily edited?
I'd check out Grav. https://getgrav.org/
-
Gravity - A new, open source DNS/DHCP server with Adblocking and inbuilt config replication
Also, there is a CMS called Grav. Both Gravity and Grav use a very similar (but not identical) font for their logo.
- Mercredi Tech - 2023-06-28
-
website with unlimited pages ??
I would use a flat file cms like https://getgrav.org
What are some alternatives?
balena-sound - Build a single or multi-room streamer for an existing audio device using a Raspberry Pi! Supports Bluetooth, Airplay and Spotify Connect
Pico - Pico is a stupidly simple, blazing fast, flat file CMS.
homebridge - HomeKit support for the impatient.
october - Self-hosted CMS platform based on the Laravel PHP Framework.
RPiPlay - An open-source AirPlay mirroring server for the Raspberry Pi. Supports iOS 9 and up.
Bolt - Bolt is a simple CMS written in PHP. It is based on Silex and Symfony components, uses Twig and either SQLite, MySQL or PostgreSQL.
raspotify - A Spotify Connect client that mostly Just Works™
Bludit - Simple, Fast, Secure, Flat-File CMS
Mopidy - Mopidy is an extensible music server written in Python
Strapi - 🚀 Strapi is the leading open-source headless CMS. It’s 100% JavaScript/TypeScript, fully customizable and developer-first.
AmpliPi - Whole House Audio System 🔊
GetSimple CMS - GetSimple CMS