• 7 Posts
  • 126 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle
  • VGA was originally a proprietary technology developed by IBM, though it was later built upon by VESA and is now publicly documented, so while it wasn’t developed by VESA as an open standard from the get-go, it is now considered an open standard that doesn’t require any licensing fees to implement. DVI was developed by the “Digital Display Working Group” and also does not require any licensing fees, though there are licensing terms you may have to abide by and there may be some costs associated with testing and validation to ensure you meet those terms and the spec.



  • That’s reasonable, people deserve to get paid for their labor. In this situation however, the difference between them is that DisplayPort is a royalty free VESA standard. So while manufacturers have to pay for the materials and such to include it in their devices, they don’t have to pay any additional fees to license the standard. HDMI on the other-hand is a “brand” of proprietary connector/interface (kind of like how “Velcro” isn’t the actual name of a product, it’s a “brand” of hook and pile tape), so not only do manufacturers have to pay for the materials and labor related to physically acquiring and installing the connectors, but they have to pay both per-device and annual licensing fees for rights to use the HDMI product.


  • “Direct playing” just means the source file is entirely compatible with the client device and doesn’t require any transcoding/re-encoding by the server, it doesn’t really tell you whether the client is using software or hardware decoding to play it. I’m guessing it’s probable that a Jellyfin server could still report “direct playing” even if the client is using software decoding to play it. However, if the client device is something like a smart TV or something with a more locked down OS, and the maintainer/manufacturer removes support for a codec from that device, you may show more transcoding action on your server for things that previously just direct played because smart devices like that may not have support for software decoding, or may not have the horsepower to try even if they still have the codecs installed.




  • H.265 (HEVC) is not a free (as in freedom) codec, so yes. You as an individual consumer can use things like Handbrake to encode H.265 video for your personal use, probably using the free x265 software encoder, but in order for a device like your phone, camera, TV, laptop, etc. to have hardware accelerated encoding or decoding, the manufacturer has to pay a licensing fee.

    This is true of lots of proprietary technologies. HDMI is another one. In order for a device to ship with an HDMI port (as opposed to Displayport), the manufacturer has to pay a per-device licensing fee.









  • I’m not a particularly skilled or professional developer, so I’ll defer to those who are on determining its usefulness for professional grade projects. However, I tried it a time or two for some of my small personal projects and had to proofread and correct mistakes so I stopped fooling with it. If I’ve got to babysit it and fix its mistakes anyway, then what’s even the point? I guess for large blocks of code it might be handy to not have to type it all out, but then you’ve still got to proofread and correct that much more anyway, so my ethical concerns aside, it really didn’t help me any more than just searching Stackoverflow to remind myself how to do something.