Can it decode x265 as my pi4 media player struggles with that and only plays the audio stream? So x264 is my current preferred format but comes in at much bigger file sizes.
With the Raspberry Pi foundation seemingly prioritizing commercial customers over normal consumers (contrary to their stated goals), I’m just gonna give up hope now of ever having one, and simply get an Orange Pi 5 which is available, and faster. I am happy that they seem to be moving the right direction with things though (fan headers, proper power management, PCIe 3.0 breakouts, etc)
Availability has been improving recently, at least in my country (UK).
While the hardware specs are often more compelling, the problem I find with the Pi alternatives is they usually depend on custom images and kernels. Pi hardware may be less ideal but I feel more confident it will have lasting software support.
Availability has been improving recently because all of the commercial partners were given a heads up that the Pi 5 was releasing and they have ramped down their purchasing of the 4 for that reason. That’s why Ebon Upton, who has no reason to speak up about this stuff, mentioned “Pi 4s will be in stock soon!”…because he was ramping up for the Pi 5 release. He pulled this shit with my hackerspace back with the original Pi. He came, gave a presentation, and the Pi 1 only had 256mb of ram at the time. Sold like 100 pis at that event, promised us nothing was changing, and then a week later, announced that all pis were going to get 512mb free and by default for the same $35 we all paid. He’s a scumbag, and I’ve watched him closely ever since. He hasn’t changed a single bit. In fact, his announcement about Pi 4s being in stock for everyone again soon was my heads-up that the Pi 5 was releasing, so I told everyone to stop buying them that asked me.
So, since they’re going to become profit mongering dbags and ruin their product and brand, what are the best alternatives? I’ve never used them but I’ve been aware of them for several years now.
I have some projects that I’m working on that seemed like a Raspberry Pi would work well with but I’m not interested if they’re going public.
Raxda. Profit-oriented from the get-go, but has excellent support. You might still need to fiddle with the official Mali drivers though (tougher than the Linux NVidia drivers).
Otherwise, if you just need a quick solution for let’s say, a NAS built around USB storage, you can just use anything as long as it has proper support for Armbian (Chinese manufacturer’s own Linux distros sometimes have spyware and stuff that make one of the cores run 100% all the time, also no Mali drivers).
Compute modules are now standard with 5V rails, making battery operation clunkier, because data centers.
And for a very long time, the 4x MIPI buses were hidden on Raspberry Pis, locking users out from most screens to hack to them.
MIPI itself relies on custom “ignition” codes (don’t know what the actual architectural names were for them), that can in theory, be so personalized each individual display and camera could be locked to the SoCs to the point the display itself would need the “ignition” code.
My speculation: I think a lot of these were made to hinder making actual portable devices a lot more clunkier than they need to be. For displays, many use the HDMI port instead. Even official stuff has its own clunk, like the Pi 400 using USB specifically for keyboard, all while an I2C or SPI would have been more than sufficient. The GPIOs of those SoCs were made for this kind of purpose.
Beaglebone has always been less shittified than Rpi, but didn’t keep up price-wise.
Rpi fell under the spell of consumer attention almost from the beginning, abandoning whatever mission it had to make media center boards.
Besides Broadcom, Rpi is also under the thumb of ARM. I don’t see why else the Pico didn’t use RISC-V cores with actual mul/div and floating point hardware instead of the kludges they bolted onto the cortex m0.
There’s been talk of this for a while. Sadly it means that things like quality, price, leaps in innovation, things remaining useable across different models, will inevitably get worse as they start to pursue profit over everything else.
On routers and modems the DHCP range is usually not allocating the full range for IP addresses to hand out to devices. If I were you I would configure the pi-hole to have a static IP address on the pi-hole itself so it will be independent from your router’s DHCP server. For example let’s say
the DHCP IP range is 192.168.1.20 to 192.168.1.254
then you can pick for example 192.168.1.19 for your pi-hole
With that approach you will avoid IP address conflicts and the pi-hole should be fine. If you’re using systemd on the pi-hole that is maybe easiest, here an example :
Since cryptsetup is not going to be at all usable in the initramfs shell any time soon, I’ve decided instead to just encrypt my /home folder with ecryptfs. The Debian Wiki has an article on how to do this.
Set a crontab command that turns on your wifi to run every minute or two, thoroughly test it, then disable your wifi and wait a minute or two before trying to reconnect.
My mind for mounting personally goes to foam with cutouts (making sure the foam is of an antistatic variety). This would provide a snug fit for different hardware in their assigned spaces, plus easy removal/rearrangment, and in-built shock absorption in case of drops etc. Channels could be cut in the foam to allow different connections and route them where you need.
Now, I can’t say I’ve ever built a project like this so this may not work for your needs.
Yes that was my main concern too. I suppose if you wanted to really go for it, you could also make cutouts for fans and cut some channels for airflow, but in the end aluminum panels with maybe some rubber standoffs for mounting may just be the safer option. And I suppose thubscrews for securing boards would make them easily removable
Yep with an inset rivet tool. I can set multiple mount points. Just drilling new ones when I want a different to pcb. If I can find a 3 high pcie frame I could mount to the case so it can be accessed from the side while the case is closed. It would be pretty usablele.
Sounds like you’re going in a good direction. Again I’ve personally never put anything like this together, I’d be interested to see what you come up with
Really like the idea of thumb screws. But I can see them being to big on the board side.
But then if I can find plastic ones this would need less of an issue. They would still need to ne 5 ot 6 mm above the board. So they can fit. But positioning would be less of an issue shorts wise.
Dont bother with raspberrypis for most things anymore. Too expensive for that old shitty hardware they put on the boards..
Machines like the Intel N100 is much simpler to deal with. No more shitty hardware incompatability and old CPU which doesnt even have proper modern HW offloading (looking at you Pi4.. what a shitboard)
And the N100 even has AV1 decoding, which is why I’ll be using the mini PC, I bought as a server (which has an N100), for Kodi as well, since I try to get most stuff in AV1 and the Pi was my only device that was too slow to play it
I tried to look into this for a bit, but unfortunately nothing yet matches the Chromecast experience for me just yet.
I found my old Chromecast just wasn’t running current versions of the streaming apps, let alone 4k. I ended up getting a new one, it does run a lot better and more independently than the one I had from 2013. I have hooked up vlc on it to a file share on my PC and the convenience is extremely nice.
Chromecast works well with the SHIELD, I have an og and it’s great. The only issue I’ve run into was some fuckery with Netflix’s password crackdown while trying to cast my GF’s friend’s account to the shield after putting in the “I’m not stealing pixels I swear” code.
For the pi if the old tutorial doesn’t work I think your only chance is someone incorporating open matter casting into Kodi.
raspberrypi
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.