That is a lesson I learned dipping into BeagleBoard and it's driving me insane.

Like, the BeagleBone Black and BeaglePlay are extremely solid SBCs; the Black, which I run off an SD card, is incredibly solid and the Play is--I mean, reading the specs it may literally be able to do anything. They're also easy to get and at a reasonable price point. But the ecology and documentation, even the official Getting Started page, are nightmare fuel and by the way, do not use those instructions as they are broken and the associated OS is three years old. If you google enough, however, you may eventually realize you have to go to the forums and find the two threads where the latest OS updates--as in, this month--are being posted or go to the individual documentation linked off of the board, where you will probably find up something like a workflow or will give you enough for some extrapolation.

There are attempts to get the OS and kernel up to date and integrate them with Beagle-specific packages and cape firmware, but this is not just like a whole bunch of separate groups doing different things not talking to each other; it's like they don't even know the other groups exist when everyone is technically working on the same projects. It's depressing.

Got a 3b a loong time ago and I love it, I use it as a jukebox and a tinker station.

Would love to get another one but man are they crazily expensive now. Tried the banana and orange pis and the are like okay but yep, they are different and doesn't seem to have the same community at all.

Chip shortage please go away!

Edit: I buy old dell optiplexes for like 40€ instead but they do take up quite the space...

My dude, that is beautiful I now need to google C.H.I.P to see what's going on. And yeah, my Black is seriously solid.

Often even cheaper

Where can I find a cheaper mini PC? They all seem to be like $250+ on Amazon, Beelink included.

Before RPis went up in cost they were $35. Isn't there anything in that price range?

I consider SBCs drastically overhyped these days. RaspberryPi was nice enough when it was released a decade ago, but these days you can just get a Beelink or similar miniPC, which is much more capable and often even cheaper. It doesn’t have the GPIO, but even if you need that, you are generally better served with a cheap MCU connected to USB.

I would put it another way; they're ideal for You Have One Vital Job Only projects; Home Assistant and Pihole are my two specific,, but robotics, a router, even a dedicated NAS would be a use case. I could run a lot of things on a mini PC with a hypervisor--soon, I shall start be experimenting with that--but One Vital Job Only projects are ones that do their thing without me ideally ever noticing them other than maintenance, if that makes sense. And even more important, things I should not tinker with because they're just fine, which is why I ended up building a second, dedicated Media Server/media ripping/encoding/NAS machine; once I did that, I finally had a stable media library I could access for more than a month at a time before I got An Idea That Would Be Fun and Oops Time To Reinstall (seriously; before I built that machine, I had to run my media and plex from a Pi (aka One Vital Job) because if I put it on my main machine, I'd tinker it to death; hence, separate everything. I am basically hiding the cookies from a three year old and I am the three year old).

Tentatively--and this applies to a much smaller population--they're perfect for deconstructing the Linux kernel and operating systems in general because you get to work at a reduced scale. I have the repository for the Pi kernel in my bookmarks and go to just read through it and get familiar when I have some time or if I remember something I want to look for (my usb wifi dongle testing project was invaluable for how much kernel homework I had to do, it's hilarious). I know and can write in basic C++, I know how to compile, but I still don't pretend to understand the kernel; with the Pi's scale, though, I can grasp it, if that makes sense. I can recognize the structure and begin to get how things fit together. I can even--tentatively--find specific parts, identify drivers, especially when it comes to specific removable hardware where it's fairly obvious and easy to follow (following actual driver files....that's in progress). My goal before I die is to be able to read and follow the entire kernel end to end; I think I'm going to need to look into the benefits of reincarnation or cryogenics admittedly, but hope springs eternal.

(BeagleBones--if nothing else--has seriously upped my game on Figure It Out For Yourself. Which yes is a very me-specific use case, requires more homework to get context than literally every class I'm taking combined including TCP/IP class, and I literally don't have time to do in more than sprints, but did lead to me literally being able to making my first Universal New Install Checklist (covers every Linux operating system I've ever used including all my personal configurations and scripts, in order, with all exceptions) and my first foray into creating an auto-install-and-configure script I can run on a new machine. Yes, those Beagles had me doing a clean install that many times. No idea what I'm doing there and I really wish there was a universal template for that.)

Having said that, I haven't jumped into MiniPC/hypervisor culture so I am up for changing my mind the minute I make the leap. And seriously, this thread has moved it actively up my priority list, which I did not see coming, so thank you for that.

I would love to replace my tp link archer c7 v5 with something more powerful, but it has to be flashable with OpenWRT and kind of an all in one box router with wifi (i know, seperation of concerns would be better, but i don't care atm).

The options i see atm:

• Turris Omnia
• Banana Pi BPI-R4 (or R3 until R4 hits the shelves)

Problem is, they are both prohibitively expensive for a simple wifi-router.

ODroids are massively underrated. The first Pi we bought is dead. The second one is now so underpowered for what we want that it's been turned into retro arcade machine. It still finds ways to cause problems too. Whereas our first ODroid is still going strong after many years of faithful service. We added an ODroid toaster to the mix a couple of years ago that's also given us zero issues and works wonderfully.

My dude, you made me google, but fine; RockPro on Ameridroid is on my short list. I've been meaning to follow up on that one, so bookmarked the homepage.

What do you use it for?

I really want to get their riscV board. But waiting a bit for software ecosystem to shore up a bit.

I was lucky enough to get a 4 before the supply issues. I wish I could get any replacements.

Nowadays I just buy thin clients and pay the 40-50$ premium for projects. Better then than waiting for a pi.

Friend, this reply is beautiful. And reading the Zima site, I may be sold. What do you use to run the network? OpenWRT, DDWRT, Tomato?

And forget about trying to transcode Blu-ray rips, which most of my devices can’t stream natively, so transcode is the only option.

Ninety-nine percent of the time, I am unqualified to advise on anything; thanks to COVID, I got deathly into making a media server and ran into the transcoding problem followed by making a spreadsheet and experimenting and documenting my results.

My results (other can disagree): all my transcoding problems came down to audio streams and subtitles. None of this may apply to you, but just in case.

I approached it from three points: a.) I got the NVIDIA Pro to run Plex as NVIDIA can handle anything; b.) I made a server just for my media processing and storage (it also runs Plex as a secondary instance when my Shield is in use). I use MakeMKV for the raw rip into an mkv container with all audio streams. The rip I process through Handbrake so I can get as close to a clone as I can (4K to 4K, 1080p to 1080p, etc) with full original audio then make a copy of each and every audio stream into the equivalent container that was compatible with the sound limitations of whatever I was planning to stream it on. Example: my Sonos speakers wanted Dolby: DTS 7.1 to TrueHD. I also did a third copy of each stream into the equivalent AAC containers: TrueHD to AAC 7.1 to future proof. I also added a fourth copy that's a basic AAC 2.0 that rolls with anything; and c.) Subtitles: turn them off and use open subtitles files so no one has to deal with bitmaps. I tested through Plex to make sure, and watched for the switch from direct play to transcode, then reverified on my Windows machine, etc.

Yes, it will eat hard drive space like whoa--uncompressed audio streams do that--but with surprisingly few exceptions, I can get direct play for 4K on pretty much anything now, not just Plex. I also create multiple resolutions using either original rip 4K or original rip 1080p as source but with the same audio mapping (that's a me-thing and also, Covid). I know this sounds like a ridic amount of work, but once I set all the profiles, it's basically a batch job. My total movie library sits at 400 movies with about 1200 files; last year I re-audited my Handbrake profiles, deleted everything but my source rips (and actually did a mass re-rip on the older ones that I did before I started compiling the latest ffmpeg to use when compiling MakeMKV), and re-encoded everything using those profiles. Total time was about two weeks end to end; I did them in batches of fifty and checked in every six hours to move completed files back into my media drives and also restart.

The only ones now that need me to personally go in and make corrections are the remastered releases like Apocalypse Now and Scarface (my files were twice the size of the original, it was unreal). Every one of them rips huge and needs slightly different profile tweaks, so those I oversee personally.

I don't know if any of this is relevant to your setup, but I reverified running Plex on one of my Pis and it could direct play at least 90% of the 4K and anything lower, and the 4K problems seem to all be with those remasters.