Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]When I set it to 30FPS, running the streaming program crashes, 60FPS is allright #431

Open
caron0k opened this issue Oct 9, 2024 · 10 comments

Comments

@caron0k
Copy link

caron0k commented Oct 9, 2024

Describe the bug
When I set it to 30FPS, running the streaming program crashes, set to 60FPS the program runs exactly right.

Debug Log
chiaki_session_2024-10-09_13-35-32-613613.log

MacOS Crash Report.pdf

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Settings'-> 'Stream'
  2. Change Remote FPS to '60 fps'
  3. Return to Steam PS5
  4. See the crash error

Expected behavior
none

Screenshots
none

Desktop (please complete the following information):

  • OS: MacOS Monterey
  • Version 12.7.6 (21H1320)
  • Device MacBook Pro (Retina, 15-inch, Mid 2015)
  • chiaki-ng Version 1.9.0

Additional context
none

@caron0k
Copy link
Author

caron0k commented Oct 9, 2024

It's weird, I tried to change the bitrate from 60,000 to 50,000 and everything worked fine:

chiaki_session_2024-10-09_14-23-03-855855.log

@streetpea
Copy link
Owner

@caron0k it looks like remote play is never becoming available on the console (the server for the remote play stream from the server never comes up for some reason when using the settings you specified) causing this issue and causing chiaki-ng to quit bc it requires the remote play stream on the console to be running.

@streetpea
Copy link
Owner

streetpea commented Oct 10, 2024

I can give you another build that waits longer for the session id to become available and see if that helps but it probably won’t. It seems to be some bug on the remote play server running on the ps console (what the client app chiaki-ng is connecting to) is not launching properly when providing it with settings you specified.

@streetpea
Copy link
Owner

@caron0k I can't replicate the error, but maybe this build will fix the crash: https://drive.proton.me/urls/NY49QBAKMW#umLh2ynHISmG

@caron0k
Copy link
Author

caron0k commented Oct 14, 2024

@caron0k I can't replicate the error, but maybe this build will fix the crash: https://drive.proton.me/urls/NY49QBAKMW#umLh2ynHISmG

I have completed testing with the new version and everything is normal now. Thank you very much!

test20241014.ini.pdf
chiaki_session_2024-10-14_12-22-07-387387.log

@caron0k
Copy link
Author

caron0k commented Oct 14, 2024

Although everything is correct, But looking at the logs, there are many more errors than before. I don't know what they mean?

@caron0k
Copy link
Author

caron0k commented Oct 14, 2024

got the crash again :(
chiaki_session_2024-10-14_12-54-04-912912.log

@streetpea
Copy link
Owner

@caron0k so that confirms you’re getting data that isn’t supported by chiaki-ng. There are greater than the max frame slots present. Ideally, this shouldn’t crash, but it should fail

@caron0k
Copy link
Author

caron0k commented Oct 14, 2024

@caron0k so that confirms you’re getting data that isn’t supported by chiaki-ng. There are greater than the max frame slots present. Ideally, this shouldn’t crash, but it should fail

Okay, then I'll lower the bitrate to use it. THX again! :D

@streetpea
Copy link
Owner

@nowrep maybe I'm missing something, can you check this please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants