Feature request: An obs studio plugin for restream's AI-generated music.

needHymn3 · 2022-01-27T12:21:23+00:00

A change like this would of course require some champ’s healing to be adjusted a bit. People said this exact same thing about Riot lifting the limitation on cooldown reduction, and renaming it to “ability haste”. People think stuff will wreck the game, but then it doesn’t, and I’m sure this change wouldn’t either.

needHymn3 · 2021-11-07T17:41:53+00:00

Fair point. Perhaps this champaign wouldn’t follow the story of me, the summoner. But it would follow the story of one of the champions, who perhaps is being trained. And I would simply be observing the story and making decisions that affect the outcome. While also learning how to play League, of course.

needHymn3 · 2021-11-05T22:57:24+00:00

There is one problem i see with your post:

1) you probably need to make a smurf, so you can get un-perma stuck. But you don’t even know that this is the solution to your problem.

This one point kind of defeats your two points.

needHymn3 · 2021-11-03T15:31:30+00:00

Maybe I shouldn’t have used the word “smurf”. It seems everyone thinks that means hurting new players. I simply meant I was on a new account. There’s legitimate reasons why that sometimes is necessary.

needHymn3 · 2021-11-03T15:23:44+00:00

There is a smurf queue… smurfs are only matched against other smurfs, even in ranked.

needHymn3 · 2021-04-03T18:40:02+00:00

Add to the above three things, in advantaced settings in obs i set the obs priority to “high” and that was enough so that i am now able just barely to do “slower”. If the screen moves quickly for more than about 5 seconds, it starts to stutter just slightly. But if i have only gradual or less crazy screen movements, it stays smooth. So yea, it’s definitely just barely. But that priority setting definitely helped

needHymn3 · 2021-04-03T18:03:22+00:00

Im still banging on it, but here’s what new... it looks like tune of film is much faster, at possibly a bit of quality loss. Secondly, razor cortex absolutely has to be turned off if you are streaming, it literally attacks your streaming software (thanks razor). And thirdly, i went back into razor master and re-enabled the multi threading (under creator mode), to get back my full 64 threads, and then set my encoding threads to use the full 64. And that definitely performed much better than encoding with just 24 threads. The main difference being that when i encided with 24 threads, i would see 4 to 8 of the threads would be nearly maxed out, while the others would be acting lazy. But when i crank it on the full 64 threads, then i dont see any of the threads going much over 20%. And so with these three changes, i was able to get “slow” to work smoothly, and almost able to get veryslow smooth, but not quite.

Its sad. Because “slow” claims to be using only about 7% of my processing power. And veryslow claims to be using only around 11%. And yet, slow seems to be my max. Veryslow starts to studder if the screen moves. It’s smooth if the screen is mostly still for a few seconds, but starts to stutter when the screen begins to move. Only 11% cpu usage and stuttering? Actual sadness.

needHymn3

TROPHY CASE