Advertisement
Guest User

Untitled

a guest
Sep 19th, 2017
67
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.01 KB | None | 0 0
  1. Lareqq - Today at 2:50 PM
  2. Hey furqan, Im from the Infinium discord and with Jason promoting your application some questions came up from my side. He told me to ask them to you instead. I hope you find the time to answer them, and Im sorry if some of them are noobish or smth. Im just really interested in that kind of stuff and it would be cool to learn more :> I'll just copy paste what I wrote him:
  3. Would you be able to tell which implementation you guys used for vp9 or did you write your own vp9 encoder? Cause from my understanding (might be wrong I just woke up) there is one from Google, which is meh, and one from ffmpeg which is rather good. But both get still outperformed by x264 when you talk pure perf/quality . While vp9 shines when we look at the actual Bitrate needed to achieve the same quality. Right? Or does that mean that you just offload the "more" work to your own server and then get a way better quality at the same bitrate in comparison to x264? Also I'm interested in the future :monkaS: it sounds good. But even you offloading work to your own servers atm, doesn't that mean the more people use your software the more loaded your servers get and the less work you can outsource from your own PC? Or are you going to scale your servers with your growing userbase? And also is the work your servers do needed in order for twitch to accept the way you encode your data? Because if that's the case it would mean it adds a layer of potential failure since if your servers go down it's not possible to stream anymore using your software which is a clear disadvantage when compared with obs.
  4.  
  5. furqan - Today at 10:36 PM
  6. hey how's it going
  7. thanks for the questions and yeah i'm definitley the right person
  8. so i'll break down the questions into a couple different things and asnwer them
  9.  
  10. Lareqq - Today at 10:36 PM
  11. Yea sure, sounds good!
  12.  
  13. furqan - Today at 10:45 PM
  14. in regards to encoders:
  15.  
  16. * we use a variety of encoders (vp9, vp8, nvenc/h264, software/x264)
  17. * vpX we use the google variants
  18. *
  19.  
  20. our main goal is to create a setup that works the best for your computer. we've noticed that different enoders (and different params per encoder) perform differently. For Example on the current gen i7's (the 7700k) vp9 outperforms everything. with about 8% CPU usage you get max complexity quality. you pack in about 40% more quality per bitrate, the picture looks better and its such a small % it's worth using.
  21.  
  22. for a lot of comptuers, using GPU or quicksync will be better. on the new i7/9s they have both v9 and h265 hardware encoding. the picture quality can be near perfect as we go through the chain.
  23.  
  24. the main end goal is we use your resources perfectly for your setup, automatically. in addition at any point if you want to chose somethign else (lets say i don't want to use the GPU, i can disable it). We have a database of 10k+ setups (cpu, gpu info) with different encoders / cpu % / bandwith etc and can use that data to understand what works well. we'll continue to add to it, and over time our process will get way better :smiley:
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement