• 2 Posts
  • 78 Comments
Joined 3 years ago
cake
Cake day: January 21st, 2021

help-circle

  • Yeah, just jump in.

    To get started it is best to keep Windows around, then if you need to get something done urgently you can go back to what you know then figure out how to do it in Linux later. Dual-booting is probably the best option if you are gaming as GPU passthrough can be difficult to get great performance. That is the approach I took a long time ago and then at some point I realized that I hadn’t booted into Windows for months and just deleted the partition.





  • I would try to avoid VP9. Hardware support is spotty and I suspect that new hardware is going to relatively quickly phase it out. AV1 is better in most circumstances except for a few devices that have hardware VP9 support but not AV1 (a few years of Android phones mostly). So unless you need a specific device you currently own to have hardware decoding support (only really matters if you are on battery for <=1080p content) just skip VP8.



  • My short opinion:

    Video

    h264 is the best option for compatibility. There have been free software encoders and decoders forever and IIRC all patents have expired. Basically every device you will encounter and every software system can play h264 videos and the encoders are fairly good.

    AV1 is the best option for quality. It is completely free and is becoming widely supported. It will likely be supported for a long time as it is the first widely available high quality free codec. It is significantly better quality than h264 so will result in smaller files for the same quality or better quality for the same file size. Hardware decoding support has only really become common in devices that hit the market in the last few years. But most new devices will have hardware decoding.

    Both of these are web-compatible as well which is nice.

    Audio

    Opus for lossy and FLAC for lossless are both some of the best codecs in their class, completely free and widely available. There are also both web-compatible.





  • Most archiver programs will set the modified time of a file to the modified time recorded in the archive (if present). Many archive formats support recording modification times because they were intended for backups and aim to perfectly record the original files including all data and metadata.

    I also agree that this is not what I want when using GUI modification programs (in my case file-roller) but the exact options available will depend on which program you use.




  • Honestly my biggest complaint is header wrapping. Technically you need to wrap lines at 998 bytes (not that any reasonable server actually cares). But in order to wrap a header you need to add spaces (because you can only break a line after whitespace). But where spaces are unimportant depends on each specific header. So you need to have custom wrapping rules for each header.

    In practice no one does this. They just hope that headers naturally have spaces or break them in random locations (corrupting them) because the protocol was too stupid.

    Binary protocols are just so much simpler. Give the length, then the data. Problem solved. Maybe we could even use a standard format for structured headers. But that would be harder to do while maintaining backwards compatibility.