|
gregf |
|
Ramtek's Trivia promoter
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 8601
|
|
Loc: southern CA, US
|
|
|
|
Send PM
|
|
Re: MAME in 2019
12/18/18 11:01 PM
|
|
|
>> I'd be very surprised if there's any movement on the discrete stuff, the dev involved
>> has basically been inactive for a while.
>
>> Also I'm not even sure he knows why everything is so muffled now, but yeah, it does
>> seem that anything that runs through the netlist system does seem to end up being
>> unclear.
>If I grabbed the driver code from version 0.162 before these changes to the sound
>happened, could I just drop it in, in place of the driver code for 0.204 and compile it,
>or has too much changed in MAME that I would actually need to know what I'm doing to
>implement the old code?
Moogly is correct.
This -> "Or has too much changed in MAME that I would actually need to know what I'm doing to implement the old code?"
It is possible to backtrack code changes from a few years earlier to see what changed, but there are 10 to 15 hurdles to have to clear first even if someone was able to fix the code or do some reverting and that means having to first mess around with old code first to find the fix. If lucky to fix the bug with older versions of MAME, then it would take more luck to get old code compatible with new code of MAME. How much spare time willing to spend doing all of that?
|
|
Index 
Flat 
Re: MAME in 2019
Reply
