Making MT32 capable whdload titles work... #1361
Replies: 4 comments 5 replies
-
Either we add something like that to the XML, and have Amiberry pick it up, or we try to detect it from the filename and auto-magically enable it from Amiberry's side when relevant. We do something similar with CD32 titles, so assuming the filenames contain it, it wouldn't be too hard to do the same for MT32. |
Beta Was this translation helpful? Give feedback.
-
I thought about that, but in essence it relies on the user not changing the filename (and possibly removing the 'MT32' hint). The XML process, by comparison, identifies the whdload.lha by it's MD5sum, thus making it filename agnostic.... that's why it was my first choice ; the situation is already 'well targeted' as such. As I say though, I could only find 17 whdload archives so disposed (and HOL only lists 22 Amiga titles in all that support MT32), so it's a very small group of titles...I honestly don't think it's worthwhile reworking the XML for such a small number of titles. Still think it's a nice little feature add tho' ...up to you. We could do it by filename detection if that's easy, and if any user ever asks "Why doesn't MT32 work for my whdload title?", you know the first response is "Did you change the filename?" .... ;) |
Beta Was this translation helpful? Give feedback.
-
Seems to work as expected, uncovered oddity wrt MT32 emulation... Sound's great however, and works ... so that's a win, thanks ;) |
Beta Was this translation helpful? Give feedback.
-
Closing this as it's implemented ;) |
Beta Was this translation helpful? Give feedback.
-
As MT32 emulation is a latterly addition to amiberry, I really didn't expect the XML to cater for this case.
AFAICT, there are <20 whdload.lha game packs so disposed (I didn't check itch.io), so I'm unsure if there's much impetus to change the status-quo.
One can relatively easily create a config.uae file to be associated with these whdload.lha titles, to enable MT32 playback, which makes me wonder if this is more fodder for
wiki/FAQ
section....(sometimes I think the wiki needs a 'mini how-to' section for stuff like this =)OTOH.... if we really wanted the whd-booter process to automate this..... snippet example;
...we would need an additional
<hardware>
field of something likeSOUND=MIDI
~ amiberry's task would be to enable MT32 emulation (playback only) if this field is present.What drove my thoughts this way, is there is a very clear differentiation wrt the .lha game packs themselves... they are all available in both MT32 & non-MT32 versions, identified by the 'MT32' hint ....ie;
CastleOfDrBrain_v1.1_De_0304.lha
as opposed toCastleOfDrBrain_v1.1_De_MT32_0304.lha
To me, this gives rise to the premise that an amiberry user, who full well knows they have the MT32 roms present & MT32 emulation works, may deliberately choose the MT32 versions of these whdload.lha titles, fully expecting the whdload/whd-booter processes to enable MT32 emulation automatically....yes? (that is, I would NOT expect them to have to create a config.uae for the title, to get MT32 sound to work =)
Thoughts?
TIA
Beta Was this translation helpful? Give feedback.
All reactions