

I’m specifically looking into this at the moment as I have been gifted a pi 5.
Most websites say avoid trying to host jellyfin on a pi 5 (codec and hardware issues are frequently noted). Do you have experience that shows these are non-issues?
I’m specifically looking into this at the moment as I have been gifted a pi 5.
Most websites say avoid trying to host jellyfin on a pi 5 (codec and hardware issues are frequently noted). Do you have experience that shows these are non-issues?
This is not correct. Bluetooth is a radio frequency communication tool. RF is part of the electromagnetic spectrum and does, in fact, "move’ at the speed of light.
Obviously, more plants are needed to combat the destructive USB industry.
Thanks for the suggestion, I started looking into LaTeX during my studies but never went through with learning it. Others have suggested Scribus, is there a reason why you might opt for LaTeX over that for this case?
DigiKam and it’s associated plugins are what I use to sort, manage and store photos. It does have facial recognition option too, but I have not used it until now.
I noticed that as part of the LaTeX description, thanks for confirming! I will take a look at scribus.
You need an incredibly robust quality management system to even achieve certification (allowing you to place on the market) when creating systems which include life support function, or functions which potentially could kill a user. All potential changes both within and outside of the manufacturers’ control MUST be assessed and constantly monitored so such issues CANNOT arise.
No one should be able to legally place an unsafe app on the market, or legally perform changes to the app without the necessary checks and balances.
Medical device approvals in most countries are definitely not the wild west. Although they are not perfect.
Laptops are being gradually added to the list of devices within scope of this change. It only counts for any new device being sold on the market after the changes take effect.
The clause only makes sure that chargers do not limit, when connected to competitors devices. The regulation is coming from an e-waste perspective, which the EU has made it clear that it is not interested in entertaining or letting companies push them around.
As I commented above, the regulation clearly states “any additional charging protocol allows for the full functionality of PD… irrespective of the charging device used.”
So they can’t have both unless they split EU & RoW devices.
This is not correct for devices being sold to the EU at least. Part of the amendment to the Radio Equipment Regulation outlines the exact standards for power delivery that must be used, and that interfaces which are capable of being charged @ > 15W must “ensure that any additional charging protocol allows for the full functionality of the USB Power Delivery…”.
For data transfer, I don’t see the point and future improvements to USB will come from industry in future.
The only way around this is with a wireless charging protocol, but manufacturers are moving away from that it appears.
Thanks for the response! Is it limited to encoding services then, so if I’m only dealing with streaming common media file types (e.g. MKV, MP4) is it still a problem? I’m not dealing with a ridiculous amount of media, so I could outsource the encoding process alone if needed…