- Thread starter H0neyBadger
- Start date
- Views 498,936
- Replies 1,071
- Likes 52
Based on the brilliant job by @H0neyBadger and the switch-ffmpeg by @averne , I work out a hardware-acceleration version of chiaki using h265/hevc codec.
For my perspective, the image now looks sharper, the latency is more stable, and cpu/power consumption is significantly lower. Here's my local build.
For my perspective, the image now looks sharper, the latency is more stable, and cpu/power consumption is significantly lower. Here's my local build.
Last edited by kkwong,
Thanks a lot for doing this, you're the hero we need! Is it on GitHub, are you doing a pull request to the official repository and all that jazz?
I would love to do the pr, but it’s on the early stage, and I’m not familiar with the workflow (it’s not on GitHub). Would be nice to add the config module to let user to enable/disable.
Last edited by kkwong,
this is the update that everybody needs. from my 10 minutes testing the screen glitching / corruption seems to be completely gone, or reduced considerably, need some more time playing with this.
time to fire up genshin and hsr.
Thank you very much for this! I tried to test it but everytime I connect to my ps4 it crashes. You can see on the ps4 menu that it’s able to briefly launch remote play (pop up message “connected to” appears) but then the app closes because of an error. Never gets to display anything.
I’m on the latest fw and ams. Anyone else is having the same problem?
So sorry, I didn’t consider ps4, hevc is not supported on ps4 and I just hardcoded it, so it should be auto downgraded to h264, will fix it in next build.
Since I don't have a PS4, would you mind testing this version? Should be ok to downgrade.
BTW, there shouldn't be a huge gap between h264 hw/sw decoding, and IMO you can just get 50% drop in cpu load.
And this build I also optimized the frame update quene & decode quene mutation lock problem, reducing frame stuttering. If anyone interested, you can have a try.
Last edited by kkwong,
Thank you very much one again. I’ve tested it as soon as I could and now it works correctly with my PS4. I gotta say it was a really nice and smooth experience!
Here’s my setup: test was done in handheld mode, my Wi-Fi is 5ghz 100mbps down and 30up, tested with cod:bo3, duke3d, mafia definitive edition, rez infinite.
Latency seems to be greatly improved in comparison to 2.2.0, controls feels responsive even with fps games. Should it be like this? Are there differences between this build and the latest official that imply reduction in input latency? The experience to me is on par, let’s say, with the iOS remote play app (whereas the previous and official chiaki homebrew app for switch seemed a step back). No stutters happened during my gameplay, but I’ll keep testing. It crashes when you select 30fps instead of 60.
Above all, response time seems better. Thanks again. Great work!
For 30fps let me spent sometime to debug after I get home (away from town for a few days). H264 latency on aw/hw decode is almost the same, but for the new build, it would reduce “cpu load spike”, and I optimized the mutation lock to reduce “thread compete”, so that you will have a more stable experience.
For me on ps5, I would say it’s “flawless experience”
, I played god of war on it for a few hours and no stuttering felt.
do we know if we can get dual sense experiemental support on the switch version of chiaki like we can on pc version - thats the only thing really im missing its no great deal if not as at least we have portable ps5 ishFor 30fps let me spent sometime to debug after I get home (away from town for a few days). H264 latency on aw/hw decode is almost the same, but for the new build, it would reduce “cpu load spike”, and I optimized the mutation lock to reduce “thread compete”, so that you will have a more stable experience.
For me on ps5, I would say it’s “flawless experience”
haptic feedback as i can connect my ps5 controller to switch but it doesnt do the adaptive triggers etc just rumble.
also another note how do i get chiaki to work outside of my network like when im on different wifi to my ps5. i know i got to do port forwarding the last time i tried it did not work though
edit: managed the port forwarding
Last edited by ccarr6257,
man, could you please share the code snippet with the original developers of Chiaki? Could help a lot to be injected on the next version of Chiaki.
Or, share the code here to us, if possible.
I'd love to. Can someone contact the original author to show me a way to do the PR? I read the project instruction and I dont't know how to contact author~man, could you please share the code snippet with the original developers of Chiaki? Could help a lot to be injected on the next version of Chiaki.
Or, share the code here to us, if possible.
It seems to be a risk to directly upload to github.
Post automatically merged:
Port forwarding is a correct way, if it fails, then there may be some incorrect config~ For haptic feedback, I would say it's feasible, but in the code, the rumble control is occupied by the rumble channel, would be hard to merge haptic sound channel.
port forwarding all sucessful - user error on my part i forgot to reboot my router when i did it. thank you for looking into the haptic feedback possibility in terms of the switch version of chiaki, must have only been possible on pc port due to how pc's work. im happy regardless using joycons etc.I'd love to. Can someone contact the original author to show me a way to do the PR? I read the project instruction and I dont't know how to contact author~
Post automatically merged:
Port forwarding is a correct way, if it fails, then there may be some incorrect config~ For haptic feedback, I would say it's feasible, but in the code, the rumble control is occupied by the rumble channel, would be hard to merge haptic sound channel.
Last edited by ccarr6257,
Probably a ducking long shot but Is there a way to enable the mic support through like say your headset on the switch? They didn't enable it in the original chiaki version
Similar threads
-
- Portal
