From: SourceForge.net <no...@so...> - 2009-09-11 17:42:18
|
Bugs item #2839507, was opened at 2009-08-18 12:06 Message generated for change (Settings changed) made by m9710797 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=2839507&group_id=38274 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Sound Group: None Status: Open >Resolution: None >Priority: 7 Private: No Submitted By: Patriek Lesparre (guyver800) Assigned to: Wouter Vermaelen (m9710797) Summary: moonsound/opl3 4 operator FM fail Initial Comment: exactly the same symptoms as 2823673, steps to reproduce differ (not found yet). ---------------------------------------------------------------------- >Comment By: Wouter Vermaelen (m9710797) Date: 2009-09-11 19:42 Message: I'm reopening this because it is a valid bug report. We simply didn't spend the time yet to investigate it. I'm also giving it a more realistic priority because AFAIK no released MSX software triggers it. (Note: I'm not saying it's not important, every bug is important. But I am saying it's not THE most important bug). And again any info you can provide on how to reproduce this is appreciated and will greatly speedup the process of fixing this bug. ---------------------------------------------------------------------- Comment By: Patriek Lesparre (guyver800) Date: 2009-09-11 12:46 Message: Marking this bug as it is in practice. You simply reject any bugs that take effort on your part. Evidence is in years of IRC logs where you constantly require bug submitters to practically fix the bug for you. It's a crying shame that you don't take your users and your slogan seriously. ---------------------------------------------------------------------- Comment By: Patriek Lesparre (guyver800) Date: 2009-08-25 09:58 Message: Vampier, I'm not looking for apologies, nor have I written anything passionate. I'm just reporting a bug, and getting the feeling I'm supposed to fix it for you. There are dozens of bugs in the tracker that are not being solved because they are "too hard to find", but often are caused by 'optimization' or not reading docs, or implementing findings by your own team members wrong. (Case in point: the Maze of Galious demo mode bug could've been solved years earlier because the behaviour of the Z80 was accurately measured by oscilloscope by the openMSX team. But no, it was deemed "too hard" and the behaviour that was specifically measured remained implemented wrong.) As a project that "strives for perfection", I find such matters careless and unfortunate. Furthermore, and this is the part where it might get passionate, after having shaped the core of this emulator in the early years of its existence, only to have my contributions denied or forgotten, I feel I'm allowed a bit of bitterness. The denial of the team to grant me a CVS account years ago was a slap in the face. So fine, you didn't want me working on this emulator anymore, but then don't complain about lack of time. Be glad I'm contributing at all! openMSX - the MSX emulator that strove for perfection and lost its way. ---------------------------------------------------------------------- Comment By: Patrick van Arkel (vampier) Date: 2009-08-25 06:51 Message: Mr. Lesparre please remember that none of the openMSX members are being paid. We work on openMSX as a fun project. Every team member has his unique skills which are sometimes limited to a certain part of openMSX. As by your passionate reply I apologize personally for this bug... bugs happen but in the end they all get solved. Thanks for your patience and understanding in this matter. ---------------------------------------------------------------------- Comment By: Patriek Lesparre (guyver800) Date: 2009-08-24 18:49 Message: It happens when playing a limited set of music and/or toying around with keyboard playing in MBFM's voice select menu. Sometimes sooner than later. The exact sequence of events is unknown, nor is it my job to find it. I don't have blueMSX installed and don't plan on doing so. It's your bug, you debug it. Don't rely on a reporter to do 80% of the work. That said, differences from MAME are a likely cause. Especially as the previous bug with same symptoms was caused by one of your 'optimizations'. Also, I'm counting 11 developers on this project. So your personal lack of time is largely irrelevant, isn't it? ---------------------------------------------------------------------- Comment By: Wouter Vermaelen (m9710797) Date: 2009-08-24 18:08 Message: Thanks a lot for this bug report. Though I didn't start to look into it yet, because it's very hard to track this down without a way to reproduce this bug. And lately I really lack the time to review 2000 lines of mostly foreign code (as you probably know we didn't write this code ourselves, but took it mostly from mame). Any clues on how to reproduce this or track this down could be useful. For example has blueMSX the same problem (or any other emulator that supports YMF262)? BlueMSX uses an early version of the openMSX YMF262 implementation, still very close to the original mame code. If that still works it's likely something we broke, otherwise it's most likely a problem that already existed in the original code. Thanks. Wouter ---------------------------------------------------------------------- Comment By: Patriek Lesparre (guyver800) Date: 2009-08-24 17:21 Message: also occasionally happens in a partial way, where some notes in an octave will function fine but others will produce complete silence. openMSX - the MSX emulator that aims for regression ---------------------------------------------------------------------- Comment By: Patriek Lesparre (guyver800) Date: 2009-08-18 12:08 Message: openMSX - the MSX emulator that aims for destruction ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=421861&aid=2839507&group_id=38274 |