That does seem like a miss for an otherwise decent platform. HDMI out support is fine, but since this setup is quite portable, exposing a headphone jack seems obvious. I suppose bluetooth is the expectation now?
That does seem like a miss for an otherwise decent platform. HDMI out support is fine, but since this setup is quite portable, exposing a headphone jack seems obvious. I suppose bluetooth is the expectation now?
http://www.crazy-audio.com/2014/07/sound-quality-of-the-rasp...
If I was on the design team for it I could eventually come around to being fine with it.
I wonder if it doesn't already need to do that for non-audio-capable HDMI sinks. (My first HDMI monitor didn't have speakers or even a headphone jack, and as far as I recall, the source computer could tell this somehow and wouldn't offer to send sound to the monitor.)
Micro HDMI to HDMI cable is included in the kit.
Unlike the "normal" Raspberry Pi this device has a fairly focused use case that you have summarised well here. It is designed to be plugged into an HDMI TV and used as a PC, with the great bonus of a cool GPIO connector. You make some choices and you make some sacrifices to meet cost and space targets. This also isn't an iPhone that costs $800.
As for fitting the HDMI on, there isn't loads of space for a full size port. I'm not saying it would be completely impossible but it would be challenging. Have a look at the photo of the board in this post:
https://www.raspberrypi.org/blog/designing-raspberry-pi-400/
The non obvious thing looking at that photo is that the keyboard slopes back so you only have height at the front. Non-micro HDMI are surprisingly deep, without CAD looking up parts and looking up parts I can't tell if just wouldn't fit at all, but you certainly wouldn't be able to get much behind it. Note also that they couldn't work out a way to sensibly route the USB to the other side - it's clearly a busy board.
Which coincidentally _also_ needs a dongle to connect to an analog speaker...
I'm a bit more disappointed there is no usable usb c - and we could use these usb c-3.5 adaptors almost everyone has now.
Between Bluetooth headphones, HDMI out to the screen, HDMI audio splitters and $5 USB audio dongles, it really is a fine design choice - especially given that the RasPI’s analog audio out circuitry is low quality to begin with.
Yes, Bluetooth introduces a tiny bit of audio latency, which is perfectly acceptable for 98% of all use, and 99.9% of RasPI 400 uses. For the rest of the cases, use one of the other RasPI400 options, a RasPi 4 or a Razer laptop.
I have an AppleTV4K, and everything is perfectly synced with at least 3 brands of Bluetooth headphones - an 3-year-old eKids one, a 1-year old TaoTronics one, and a 2-year old nameless one.
In the early PlayStation 2 days, many flatscreen TVs (both Plasma and LCD) had delays that made games like Guitar Hero unplayable, so the games added a latency estimation/calibration setting you could use; My 12 year old Onkyo HDMI receiver has a special "eliminate latency in game mode" setting which disables some processing features and reduces sound latency by 50ms or so.
It's not that there were never problems; But anything made in the last 5 years or so, especially using BT4/BT5, should not have these issues.
Edit: just tried with an 8 year old or so JBL Clip I found lying around, and it does have ~100ms latency (estimated, not measured). But the newer ones don’t have it.
I use mpv and whenever I get audio latency from my headphones* I just adjust in the player.
* - It seems like there's some adaptive algorithm where they start off at 0ms latency but if they experience one hiccup they increase to 250ms-300ms and then another hiccup causes them to jump to 500ms. This is also why a keyboard shortcut that let's you adjust the exact a-v delay value is useful beyond just setting the value once.