This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.
EmuNewz Network › PSP Emulation › JPCSP Official Forum › Commercial Game Discussion › JPCSP - Playable Games v
Downstream Panic! - ULUS10322

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Threaded Mode
Downstream Panic! - ULUS10322
gid15 Offline
Dev team
**********
Posts: 2,420
Threads: 30
Joined: Dec 2009
Reputation: 50
#11
03-25-2015, 06:45 PM (This post was last modified: 03-25-2015, 06:46 PM by gid15.)
Code:
17:08:38 DEBUG hle.sceMp3 - thread mp3 play - sceMp3GetInfoToAddStreamData returning writeAddr=0x0892A760, writableBytes=0xFD20, readOffset=0x2F760
17:08:38 DEBUG hle.sceMp3 - thread mp3 play - sceMp3NotifyAddStreamData id=0x0, bytesToAdd=0x1FA40
Hmmm, 0x1FA40 are added to the stream data even though only 0xFD20 were reported as writable. I would like to know how a real PSP reacts on that.

Could someone generate a JpcspTrace with this config file:
Code:
sceMp3GetInfoToAddStreamData 0xA703FE0F 4 xppp
sceMp3NotifyAddStreamData 0x0DB149F4 2 xx

Thank you!
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Find
Reply
sum2012 Offline
Posting Freak
*****
Posts: 1,087
Threads: 149
Joined: Sep 2011
Reputation: 8
#12
03-26-2015, 11:59 AM (This post was last modified: 03-26-2015, 01:46 PM by sum2012.)
Only can use @unknownbrackets JPCSPtrace
(03-25-2015, 06:45 PM)gid15 Wrote:
Code:
17:08:38 DEBUG hle.sceMp3 - thread mp3 play - sceMp3GetInfoToAddStreamData returning writeAddr=0x0892A760, writableBytes=0xFD20, readOffset=0x2F760
17:08:38 DEBUG hle.sceMp3 - thread mp3 play - sceMp3NotifyAddStreamData id=0x0, bytesToAdd=0x1FA40
Hmmm, 0x1FA40 are added to the stream data even though only 0xFD20 were reported as writable. I would like to know how a real PSP reacts on that.

Could someone generate a JpcspTrace with this config file:
Code:
sceMp3GetInfoToAddStreamData 0xA703FE0F 4 xppp
sceMp3NotifyAddStreamData 0x0DB149F4 2 xx

Thank you!


Attached Files
.txt   JPCSPtracelog.txt (Size: 13.47 KB / Downloads: 193)
Find
Reply
gid15 Offline
Dev team
**********
Posts: 2,420
Threads: 30
Joined: Dec 2009
Reputation: 50
#13
03-27-2015, 10:34 AM
Code:
19:30:21.078518 thread mp3 play - <- sceMp3GetInfoToAddStreamData 0x0, 0x09EB8558(0x891AA40), 0x09EB855C(0xFD20), 0x09EB8560(0x0) = 0x0
19:30:21.105342 thread mp3 play - <- sceMp3GetInfoToAddStreamData 0x0, 0x09EB8514(0x892A760), 0x09EB8518(0xFD20), 0x09EB851C(0xFD20) = 0x0
19:30:24.973613 thread mp3 play - <- sceMp3GetInfoToAddStreamData 0x0, 0x09EB8514(0x891AA40), 0x09EB8518(0xFD20), 0x09EB851C(0x1FA40) = 0x0
19:30:28.928594 thread mp3 play - <- sceMp3GetInfoToAddStreamData 0x0, 0x09EB8514(0x892A760), 0x09EB8518(0xFD20), 0x09EB851C(0x2F760) = 0x0
19:30:33.095982 thread mp3 play - <- sceMp3GetInfoToAddStreamData 0x0, 0x09EB8514(0x891AA40), 0x09EB8518(0xFD20), 0x09EB851C(0x3F480) = 0x0
Interesting information: sceMp3GetInfoToAddStreamData never returns more writable bytes than the half-buffer size, even at the first call.
I will update Jpcsp accordingly.
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Find
Reply
sum2012 Offline
Posting Freak
*****
Posts: 1,087
Threads: 149
Joined: Sep 2011
Reputation: 8
#14
03-28-2015, 10:27 PM
Compile myself in this commit https://github.com/gid15/jpcsp/commit/3d...35bdd8e0d9

Fixed


Attached Files
.7z   jpcsplog.7z (Size: 1.8 MB / Downloads: 202)
Find
Reply
sum2012 Offline
Posting Freak
*****
Posts: 1,087
Threads: 149
Joined: Sep 2011
Reputation: 8
#15
11-08-2020, 02:13 PM
last work
https://github.com/jpcsp/jpcsp/commit/08...54a5b4cc75
first bad
https://github.com/jpcsp/jpcsp/commit/71...f18c7a258a

It mean https://github.com/jpcsp/jpcsp/commit/71...f18c7a258a has problem

Attach their and b1b7e7e log


Attached Files
.7z   good-0858ea2-log.7z (Size: 534.15 KB / Downloads: 213)
.7z   bad-7136396-log.7z (Size: 203.99 KB / Downloads: 197)
.7z   bad-b1b7e7e-log.7z (Size: 205.24 KB / Downloads: 234)
Find
Reply
gid15 Offline
Dev team
**********
Posts: 2,420
Threads: 30
Joined: Dec 2009
Reputation: 50
#16
11-09-2020, 05:23 PM
(11-08-2020, 02:13 PM)sum2012 Wrote: It mean https://github.com/jpcsp/jpcsp/commit/71...f18c7a258a has problem
Excellent! Thank you for pointing out the exact commit introducing the issue!
It should now be fixed in 97124eb.
Always include a complete log file at INFO level in your reports. Thanks! How to post a log
Find
Reply
sum2012 Offline
Posting Freak
*****
Posts: 1,087
Threads: 149
Joined: Sep 2011
Reputation: 8
#17
11-10-2020, 12:00 PM
Yes, 97124eb version fixed


Attached Files
.7z   log.7z (Size: 3.99 KB / Downloads: 223)
Find
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)