Jump to content

kafeaulait

Member
  • Posts

    4
  • Joined

  • Last visited

Awards

This user doesn't have any awards

kafeaulait's Achievements

  1. The big thing that drew me into Linux was actually /r/unixporn. Being able to customize my workspace to look and behave exactly how I want it to brings a rather warm and fuzzy feeling. That and tiling window managers are the bomb.
  2. I'd prefer to avoid solutions that hinge on existing technologies, as the facts change constantly. Not only is it not true that Twitch enforces a hard cap of 3500 kbps (in fact, it is their advised maximum for technical reasons), but it also does not translate well to other existing services, future technology, or similar use cases (local recording).
  3. Hi guys, this thread is less about build recommendation and more of a general knowledge inquiry. If there is an existing repository of information about game streaming in general, I'd appreciate being pointed there as well! The question is: A couple possibilities I've thought of with my existing knowledge on the subject: Using GPU encoding: With the GTX 1000-series and RX 400-series GPUs offering excellent performance at affordable prices, hardware-accelerated encoders seem to be commonplace for a minimal performance hit. This means the CPU choice isn't likely to make much of a difference. True/False? Why? Using CPU encoding: I've heard in passing that CPU encoding can make the stream look better (even though anecdotally I have not had much success with my Ivybridge i5 from 2012). Is this worth it in some cases? How? What are the considerations? What would be some specs to consider in the CPU for this use case? Thread count? Core count? Single core clock speed? Cache? Some obscure video encoding technology nobody has made a big deal about? Feel free to elaborate on more extreme use cases (e.g. 4k/8k at 144fps gaming) as well if they are relevant.
×