109
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Jan 2024
109 points (86.1% liked)
Selfhosted
39677 readers
288 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Man my home server IDLES at 76 watts per hour running x86. Now mind you I need the x86 to perform some of the functions I want. This thing works as an NAS, nextcloud, media server, kiwix, security camera (zoneminder), remote desktop (xrdp), runs home assistant, gpu AI upscaling for photos, and finally screeches along running a virtual pipe organ I built that takes 69 GB of RAM to run.
If I could do that with raspberry pi's I would in a heartbeat! the power savings alone would eventually pay for them. If it's doing what you want then don't worry about them. My pi400 works as a remote desktop client and one day I hope more of this stuff will work well on it/a future generation so I can ditch the tower, energy usage, and noise.
What is that virtual pipe organ and why is it using 69 GB RAM when running?
It is software (grandorgue) that pretends to be a pipe organ (the instrument). In order to run fast enough it needs to load every sound sample into memory to play, as well as usually multiple kinds of sound endings. I play professionally on a "small to mid sized" pipe organ with 1,438 pipes. The one I load for use at home has more than that!
The instrument was from the 1960s and I rebuilt it with a pi pico that you can see here, and you can hear the before (analog sound cards) versus one of the organs I've loaded into it here.
Here is an alternative Piped link(s):
here
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
That’s amazing sounding! Worth the watts, even if I did get church ptsd listening to it.
Hahaha yeah…it’s in many ways unfortunate that if you want to play/enjoy this instrument churches are the only option most of the time :/
Definitely worth the watts though!
I’ve been recently bingeing Look Mum No Computer’s rescue/re-build/midi-fication of an organ that had been shoehorned into an organist’s home, after the church had been converted. I’m more of an engineer than musician, but it’s amazing how much goes into the layering of sounds from so many different pipes.
My 6 yo loves learning with such a cool soundtrack too.