Seems like these methods are slowly degrading as time goes by.
First issues with setting codec and resolution starts becoming unreliable. After initial positive feedback when updated to inject localStorage after Stadia performance update, it starts needing a refresh for many to work properly. Or does only work sporadicly, worst case for some, it does not work at all.
Then now codec starts being defaulted to VP9 consistently for some.
I have tested multiple ways of forcing and injecting but always end up at VP9 codec now. Despite using MacOS Catalina which should not default to VP9 since it does not have HW decode support.
Following issues and thoughts arise:
Investigate how codecs are actually handled and set to stream by Stadia at the time being.
Probably need a better way of injecting codec/resolution values, suspect timing might affect if stream values are set or not.
Before releasing next version of codec/resolution, beta-testing is highly recommended. Since it is apparent that the different chrome environments behave extremely different.
Seems like these methods are slowly degrading as time goes by. First issues with setting codec and resolution starts becoming unreliable. After initial positive feedback when updated to inject localStorage after Stadia performance update, it starts needing a refresh for many to work properly. Or does only work sporadicly, worst case for some, it does not work at all.
Then now codec starts being defaulted to VP9 consistently for some. I have tested multiple ways of forcing and injecting but always end up at VP9 codec now. Despite using MacOS Catalina which should not default to VP9 since it does not have HW decode support.
Following issues and thoughts arise: Investigate how codecs are actually handled and set to stream by Stadia at the time being. Probably need a better way of injecting codec/resolution values, suspect timing might affect if stream values are set or not. Before releasing next version of codec/resolution, beta-testing is highly recommended. Since it is apparent that the different chrome environments behave extremely different.