RPCS3 Forums
Audio issues with Demon's souls inside linux - Printable Version

+- RPCS3 Forums (https://forums.rpcs3.net)
+-- Forum: Support & Issues (https://forums.rpcs3.net/forumdisplay.php?fid=17)
+--- Forum: Support (https://forums.rpcs3.net/forumdisplay.php?fid=18)
+--- Thread: Audio issues with Demon's souls inside linux (/showthread.php?tid=198829)



Audio issues with Demon's souls inside linux - alirezaes - 05-30-2018

Hi.
I'm trying to run Demon's souls with lates linux build. But sound glitches are making it literally unplayble.
What I've tried so far:
 - Alsa, PulseAudio and OpenAl
 - Overclocking CPU up to 4.6 GHz.
 - trying all configs. SPU, PPU, Renderer API and ....

my specs:
  - Intel core i5 6600k
  - GTX 1060 6GB
  - 16 GB RAM
  - Archlinux + appimage
When running it, the console spams these:
Code:
[color=#ff6000]U {PPU[0x1000017] Thread (NexusRevolution Main) [0x00a67f94]} sceNp TODO: sceNpManagerGetNpId(npId=*0xd0378864)[/color]
[color=#ff6000]U {PPU[0x1000017] Thread (NexusRevolution Main) [0x00e13e64]} sceNp TODO: sceNpManagerGetOnlineName(onlineName=*0xd0378888)[/color]
[color=#ff6000]U {PPU[0x1000017] Thread (NexusRevolution Main) [0x00e13e74]} sceNp TODO: sceNpManagerGetAvatarUrl(avatarUrl=*0xd03788bc)[/color]

And when I stop emulation it prints these
Code:
E {PPU[0x1000011] Thread (_sys_MixerChStripMain) [0x0154e5a4]} Stat: 'sys_lwmutex_unlock' failed with 0x80010009 : CELL_EPERM [x66368]
E {PPU[0x1000011] Thread (_sys_MixerChStripMain) [0x0154e5a4]} Stat: 'sys_lwmutex_lock' failed with 0x80010005 : CELL_ESRCH [x66368]
E {PPU[0x1000013] Thread (_cellsurMixerMain) [0x01549ec4]} Stat: 'sys_mutex_lock' failed with 0x80010008 : CELL_EDEADLK [x8294]
E {PPU[0x1000013] Thread (_cellsurMixerMain) [0x01549ec4]} Stat: 'sys_lwmutex_lock' failed with 0x80010005 : CELL_ESRCH [x33184]
E {PPU[0x1000013] Thread (_cellsurMixerMain) [0x01549ec4]} Stat: 'sys_lwmutex_unlock' failed with 0x80010009 : CELL_EPERM [x33184]
Any Ideas?


RE: Audio issues with Demon's souls inside linux - Ani - 06-02-2018

Audio "loop" is known when it's not running at an ideal performance