What does the following sysex mean?

41 10 42 12 40 01 30 03 0C F7
41 10 42 12 40 01 33 5A 32 F7
43 10 27 30 00 0C 44 00 F7

It is sent just before the title music starts in Star Trek: Judgement Rites... and choosed General MIDI in the sound setup.
It does not seem to a reset message as my Yamaha MU50 don't seem to do anything when reciving the message?

41 10 42 12 - 40 01 30 - 03 ==> Roland Reverb Hall 1
41 10 42 12 - 40 01 33 - 5A ==> Roland Reverb 90 (all channels?)
43 10 27 - 30 00 0C - 44 ==> Yamaha TG100 ???

ah.. now i noticed the change to "Hall 1" on my MU50.. nothing else cahnges tough, i also tested on my SC-55 but there is no change to reverb level at all?

So it has TG100 sysex? Thats intersting, i think i will try ST:JR with my TG100 maybe it will sound good 😉

Reading Roland docs, it's an 'output reverb level'. Not ones sent to each individual channel. Default value = 64 --> 90 (sysex).

Yamaha sysex is sent incomplete:
43 10 27 - 30 00 [00] - 0C 44 - 00 F7 ==> master tune 0C44h

tikalat: Thanks for the pointer to IPS XP.

Stefan_L: Is there a way I can do either of your suggestions using munt via the Daum SVN? I unfortunately dont have a real MT-32 available to me at the moment.

Python1980 wrote:

Stefan_L: Is there a way I can do either of your suggestions using munt via the Daum SVN? I unfortunately dont have a real MT-32 available to me at the moment.

Sure.. MUNT works like a MT-32 so it should not be a problem for it to read midi messages.
I have checked the music files from ST:JR and it seems there are 9 sysex files... one for each "episode" and one for the title. So i dont know i my idea would work so good afterall 😒

Stefan_L wrote:
Colud not one solution be taht you first load the disk version and let teh game uplaod the sysex and then quit and start the cdrom version without turning of the MT-32 as the instrument data should still be in the MT-32 memory then? Or log an SMF with dosbox from the disk verison sysex and play the SMF before you start the cdrom version.

I tried the first suggestion, like Stefan_L suspected in the post above it didnt work.

While trying the second suggestion I noticed something. The recording (made by using ctrl-alt-f8 in dosbox) I made from the floppy version using MT-32 settings sounded very wrong when played in a windows midi player as expected but the recording I made from the CD version using MT-32 settings sounded fine.

Because of this I tried playing the CD with MT-32 settings but under vanilla dosbox so that munt wasnt being used....and it sounded ok! I have confirmed that the games config file does change when you select MT-32 or GM.

As a final test I did a recording of the CD version set to GM and running in vanilla dosbox. Then I played all three recordings using Megamid in vanilla dosbox and then in Daum SVN. The two CD recordings were identical as far as I could tell, both sounded ok with GM in vanilla but bad with MT-32 in Daum which was the opposite of the floppy recording.

So it seems that the end result in the CD version is GM no matter what the game config setting is, which to me is weird. Why have an MT-32 setting and (as mentioned by Stefan_L) separate music files if its just going to be GM anyway?

I hope this makes sense, my MIDI knowledge is extremely small. Is there anything else I could try?

Dumping notes.

Star Trek - 25th Anniversary
1) Detect 2 bad files (bridge.mt, ground.mt)
Judging from context of other used channels, ch6 should be volume controller (B5 46 66 --> B5 07 66)

2) MT-32 custom sfx, map

PATCH: 0; timbre=128 (Energize )
PATCH: 1; timbre=129 (Dematerial)
PATCH: 2; timbre=130 (Demat shor)
PATCH: 3; timbre=131 (Materializ)
PATCH: 4; timbre=132 (Beeps )
PATCH: 5; timbre=133 (Red Alert )
PATCH: 6; timbre=134 (Viewscr 1 )
PATCH: 7; timbre=135 (Viewscr 2 )
PATCH: 8; timbre=136 (Ship Phase)
PATCH: 9; timbre=137 (Door )
PATCH: 10; timbre=138 (Photons )
PATCH: 11; timbre=139 (Buttons )
PATCH: 12; timbre=140 (Hand Phase)
PATCH: 13; timbre=141 (Tribble Co)
PATCH: 14; timbre=142 (Scanner )
PATCH: 15; timbre=143 (Misc. Eeri)
PATCH: 16; timbre=144 (Expl 1 )

Star Trek - Judgment Rites
1) Each MT-32 file has its own custom bank setup: FED, LIGHT, MADNESS, (..)
2) GM files have lots of chorus, reverb hits. And Orchestra drum kits. Plus custom SC-55 sysex commands per file too.

Going to see if I can parse the MT-32 / GM sysex better.

https://en.wikipedia.org/wiki/List_of_MT-32-c … _computer_games
- Noticed that neither Star Trek game is listed here. 😀

And MT-32 MIDI check of 25th Anniversary shows.. possible CM-32L sfx usage.

File = GROUND.MT
- #13 = creaking
- #15 = thunder, explosion
- #16 = windchime
- #19 = engine, explosion
- #20 = machinegun
- #21 = crash, explosion

Many appear to have pitch wheel + xmidi loops. Real in-game play would be the final certify.

tikalat wrote:

https://en.wikipedia.org/wiki/List_of_MT-32-c … _computer_games
- Noticed that neither Star Trek game is listed here. 😀

Would you like someone to fix that for you? 😀

Star Trek: Judgment Rites (1993)

Title: Driver fixes
Date: November 10, 2013

About:

General MIDI
- Send GS reset

MT-32 (Collector's CD)
- Fix detection
- Fix by DenizOezmen

=================================================
=================================================

Note:
Chose to leave the 25th Anniversary volume 'pseudo-bug' thing alone - looks more intentional when compared to other tracks, in-game music.

edit:
Game makes heavy use of ORCHESTRA, reverb, chorus, sc-55 sysex commands.

@stiletto
No, that's quite alright.

Mapped out HMI format (Descent). Amazingly looks very close to standard MIDI, but with weird Human Machine Interfaces extra voodoo going on.

Roland GS:
Drums = TR-808, POWER
Perc = shaker, mute surdo, high q, metronome bell, belltree
Reverb, Chorus

Issue:
Rvb, Crs not correctly reset every track - have to hack driver to do this.
Send GS reset for Yamaha cards compatibility

Descent (1995)
Descent II (1996)

Title: Driver + MIDI fixes
Date: October 17, 2013

About:

General MIDI
- Send GS reset
- Reset reverb, chorus
- Use SC-55 Fl. Key Click

##################################################
##################################################

Both games use same MIDI engine version - same fix file.

Descent II uses ELECTRONIC, BRUSH, POWER. +small percussion.

Forgot to mention ST:JR uses Hi-Hat ORCHESTRA percussion.

^ mega thanks!!!

tikalat: That is absolutely fantastic! Thankyou for taking the time to fix the detection bug in STJR.

I noticed that you modified the FED mission files as well as the general DATA files. Does this mean that each mission may need some attention, but you didnt have saves that far in to test or should everything be fine for all missions?

Only added gs reset sysex to both files - affects General MIDI @ title screen or 1st mission intro.

Everything else looked '''normal''' from the xmi dumps.

Did a quick dry test run and Descent I + II now use Fl. Key Clicks
Re: Interplay - sound driver hacking

Note to self:
Update GM enhancement thread to document SC-55 non-GM fixes.

Fixed an error I made with Descent 1 only - Saw (01) --> Saw Wave (00). Updated pack.

Also noticed that Blackthorne uses Fl. Key Click for "drip" sfx. Going to fix that too.

gonna check the new patch in 10mins... is there any way to skip to a level that uses the click sound so I can see if both SC-55s work OK?

Cheat codes

http://www.cheatcc.com/pc/descent.html
- gabbagabbahey, farmerjoe 14

http://www.cheatcc.com/pc/descent2.html
- freespace 3