There is the SW1000XG, a pci xg midi card.
Thanks for the info 😀
Also I think I found the problem with the sw60xg. There's a piece of software - a control panel I suppose - that gets installed dcalled EffectsGearII. From there you can select effects and under "other" is "XG Playback". If I select that - duh - the xg midi's sound like they should.
but both cards are acting the same now so there's some consistency at least 🤣.
Glad you got it working 😀
There's a slight delay at the start as the XG effects seem to get implemented when you play the midi, so there's a few notes non-XG and then the XG effects cut in. So it's a bit weird still
You know something, previously I had mentioned that I "thought" I was authoring the MIDIs to XG guidelines, but one thing that I've never edited/done: Most XG compatable MIDI files that I've ran across have some intentional delay in them (about a second or) before the actual music starts.
During this 1 second or so period is when the XG parameters for the various effects are set up and transmitted to the hardware... I've never edited/created the XG MIDI files like that, but rather made a single bulk sysex dump at the very beginning of the MIDI files (containing all of the various effects and processor parameters) to set up the XG parameters.
That's prolly why it sounds like that... standard (or normal) for the first few notes, and then like it should for the rest of the MIDI file. IIRC, I seem to remember reading about some sort of delay guideline that should be followed when the initial setup sysex dumps are sent to the hardware (to overcome/prevent that problem), but I really don't remember.
Anyhow, you can see what I'm refering to with all of the "official" Yamaha XG MIDI ZIPs that I previously linked to. As an example, if you load the previously mentioned "D_RP_02X.MID" into a decent MIDI sequencer, you can see that the sysex dumps are sent separately; one at a time; during the first second or so of playback before the music actually starts.