07973: pce and clones [mlairj, mlair]: CD music ends before expected

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07973	Sound	Minor	Always	May 9, 2021, 02:21	6 days ago

Tester	ICEknight	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	Fixed	OS	Windows (x64)
Status [?]	Resolved			Driver	nec/pce.cpp
Version	0.231	Fixed in Version	0.253	Build	x64
		Fixed in Git Commit		Github Pull Request #

Summary	07973: pce and clones [mlairj, mlair]: CD music ends before expected
Description	CD tracks stop playing earlier than they should. This can be observed in the Victory music after defeating a boss. I'm reporting this despite the "Incorrect sound" warnings because it's a regression from 0.230, where the track took longer to start but ended properly. This is how it plays on real hardware:
Steps To Reproduce	Beat any boss and the Victory track will play (I'm providing savestates with the first boss almost beaten).
Additional Information	Might be worth noting that other games like Bonanza Bros now seem to start their music tracks a few seconds in, rather than at their beginning (and also don't loop). Could be related to commit 2caa566? https://github.com/mamedev/mame/commit/2caa566f22606682ee432c410d40376335e12b02
Github Commit

Flags
Regression Version	0.231
Affected Sets / Systems	pce and clones [mlairj, mlair]

Attached Files	savestates.zip (290,323 bytes) May 9, 2021, 02:27 Uploaded by ICEknight Monster Lair savestates at the first boss

No.18830 Haze Senior Tester May 9, 2021, 20:56	PCE-CDs are strange, might need reconverting
No.21226 Kale Developer Mar 29, 2023, 16:03 edited on: Mar 29, 2023, 16:04	This needs to be rechecked in 0.253, it's probably fixed but I haven't tested it. It's also possible that the redump.org files behaves better and the CD images we have hooked in SW list are just bad.
No.23788 Kale Developer 6 days ago	Assume fixed around 0.253, not sure which commit hash.
No.23795 JimCarlTay Tester 6 days ago	It's likely that this commit "3cf4d60bf1d9473cfe95944fa58366538b70e34d" may have fixed this bug, but it was not mentioned in the commit message.