781–790 of 859 posts
Earlier quoted context omitted.
It is, and the A72 has ~2-3x the IPC of the A53 depending on workload.
Realize I should have added that... but no way to edit original post... is there an easy way to do so?
Earlier quoted context omitted.
I've run into the same. It often would come back from a reboot without DNS restarted correctly. I never went through a Pi Hole update without having to manually fix things either. A few weeks ago I switched to Ad Guard Home. Has been rock solid since. The big dancehaus it doesn't support the exact same filter files.
I believe you can add your own filter files, so in this sense you could basically link the same ones right?
What I meant is it doesn't seem to parse the same range of formats, so it rejected some of Pi Hole's filters as malformed.
> 4K! I'm very excited about these upgrades too (especially GigE), but as far as I can tell nothing on this news page specifies whether the Pi will also support HDR output as part of the 4K upgrade. That's most of the practical benefit of 4K - that 4K releases tend to come with HDR10 or DolbyVision support. Anyone know if we can expect HDR output to work? If I knew it supported that I'd be purchasing one right now to…
don't want to derail the RPi4 celebration, but for this specific purpose (media centre) I've been super happy with Nvidia Shield. You can often pick them up for $150 on a sale, less on ebay. 4k HDR, runs Android TV (some people have managed to get Ubuntu running on it too), VLC/Kodi work well, Moonlight works well for game streaming from another gaming PC with NVidia card. It's super zippy, too, and quite small (thou…
Earlier quoted context omitted.
Not at all. The reason I upgraded my home LAN many years ago was exactly because 100Mbps is not enough to stream 1080p videos. It does suffice on average, but the bitrate changes a lot within the same file.
I haven't actually seen a single 1080p raw bluray file with a higher video bitrate than 35 Mbps. Maybe with TrueHD/Atmos audio the total bitrate could push past 40, but 100 Mbps is way more than you need for 1080p. Even 4k doesn't seem to push past 50 Mbps, but I think that's because h.265/HEVC is more efficient for the same observed quality/CRF.
Blu-rays use H.264 High Level 4.1. That has a maximum bitrate (for a single buffer) of 50 Mbps. The average bitrate for an entire disc is usually closer to 25-30. Even the most extreme cases, like the mastered-in-4K Lawrence of Arabia, have peaks at about 48 Mbps, and average bitrates of about 42 Mbps.
If you're having issues streaming Blurays on a 100 Mbps network, the speed of the network is not your problem!
Earlier quoted context omitted.
Hi, thanks for running this. It's helpful information. Something strange is that in your cpuinfo the SoC is detected as BCM2835, while in all the spec sheets online it's supposed to be BCM2711. Do you know if you are possibly working with a different version of the hardware? One reason this is important is that some of us in this thread are trying to work out what the video decoding and 4K HDMI capabilities are with…
BCM2835 vs BCM2711 is all in software, the board itself doesn't tell you explicitly. The regular vc4 drivers are just an rpc to the code running on the GPU with start.elf. I wouldn't be surprised if the old drivers just worked.
Earlier quoted context omitted.
> Raspberry Pi 3 media center Just read theverge review on how the Pi struggles to play a video full screen, even if resolution is 480p. How are then people using it as a media center?
What review did you read? Playing video is likely the only thing the PI 3 does really well; even most H265 FHD do play without stuttering on the 3+ although we're close to the board limits. Are you sure the writer didn't use the board the wrong way? Some people still believe that videos should be streamed after being transcoded because that is the only way to watch them on their ridiculously limited smart TV which la…
I'm not sure that transcoding has anything to do with it, unless the transcoding was happening on the Pi itself (which would indeed be dumb). Most of the time people are transcoding things it's x264 -> x264 with Plex, just with a much lower bitrate (and probably 720p) because (as you say) their player's platform can't handle it and no one cares about video quality these days.
This is the death knell for x86 PCs for the consumer market. No regular user needs more than this. Developers and hardcore gamers will be the only ones left on x86. Intel will be a shadow of themselves soon. They have did such a bad job at diversifying.
> No regular user needs more than this. These are words I've heard from arrogant techies for decades, yet they are continually surprised to find that people don't use the shit they condescendingly designed for them based on that premise.
The people not using the shit? They account for 58% of site visits. See: https://www.stonetemple.com/mobile-vs-desktop-usage-study/
Earlier quoted context omitted.
I'm crossing my fingers here. This is really something they should have put in the specs if it's supported. With 10bit decoding and Rec. 2100 [1] support, this would make a fantastic platform to build a media center on. I'd certainly upgrade from the Pi 3 even though I don't currently have a 4K television. [1] https://en.wikipedia.org/wiki/Rec._2100
What are the odds that this will support 1080p streaming with Plex? I've tried Plex on a Pi 3 using a Roku as a player with 1080p and it's a complete failure. Plex tries to encode everything even if native playback to the Roku is possible using the Roku media player.
Earlier quoted context omitted.
> not typically been used to implement malicious functionality so raspberry pi, in an effort to be more open than say Dell/HP, where you had/have to pay to download drivers, bios and other updates, is _more_ malicious than say apple/google who are competing to create a closed garden with a remote lockout, where nothing is owned, only rented? ya. I really don't understand this viewpoint. Look, I've used embedded 386s.…
I don't own a smartphone/any Apple/Google products, or Dell/HP machines for that matter (not surprising to me that they're bad). My frame of reference is typical PCs, which aren't in the habit of applying vendor lockin with regards to what peripherals you can use - and other SBCs. I don't understand the premise that not applying vendor lockin to a camera module would make SBCs unreasonably expensive. Competing SBCs a…
> But I never claimed that kids should be taught that. What I do
> claim is that kids should not be taught that it's ethical or
> normal/acceptable to try and use malicious functionality to
> institute vendor lockin, creating an artificial monopoly in
> compatible peripherals, because it isn't.
The way I see it, a Raspberry Pi is more than the sum of its parts- while commercial companies care about the chips and the complexity a solution like a Pi can remove, I personally bought a Pi for my brother to learn on.