next »

[winner]

Here's an update with an increased maximum voice limit of 400...

   www.un4seen.com/stuff/xmp-midi.dll

Let me know if you still have any trouble with it.

Thanks Ian! I think this may have solved some issues. I've tested this as well. At some point when playing the song, the MIDI Mixer dialog enumerates 397 active voices. The 400 limit seems to be sufficient for this file, but just barely.

Well.... I've tried another midi file, lightsg.mid, and that file, when playing, pins the active voices at 400. Probably it needs more. Uploaded to FTP incoming folder.

[Sub-Zero]

Thanks Ian.. Will give this one a shot..

[Ian @ un4seen]

Well.... I've tried another midi file, lightsg.mid, and that file, when playing, pins the active voices at 400. Probably it needs more. Uploaded to FTP incoming folder.

OK, here's another update with the maximum voice limit increased to 500...

   www.un4seen.com/stuff/xmp-midi.dll

I would be surprised if the killing of a voice is audible when there are 299 or 399 louder ones playing, so I'll be amazed if any are audible when there are 499 others

[saga]

Wouldn't it make sense to remove the voice limitation alltogether and use a resizable container for managing the voices?

[Ian @ un4seen]

Possibly. The voice limit was originally the only way to limit the CPU usage, but with the introduction of the automated voice killing when CPU usage gets very high, I guess it could be switched to dynamically allocating voices as they're needed. On the other hand, are more than 500 voices ever going to be needed?

[saga]

Well, there is the possible that someone wants not a single voice to be lost and for that they require 501 voices to be played, the next person needs 602 voices... I think this would work best if you change the voice limit slider to an editable dropdown list... You could provide some sane defaults (e.g. 16, 32, 64, 128, 256) but if someone really thinks they need more voices, they could just type in 999 or whatever. Or just remove the limit alltogether as you suggest and purely rely on CPU monitoring.

[guest]

This MIDI reaches current voice limit - 500:
http://www.mediafire.com/?n528j9i28hkb99b

[Rich Nagel]

This MIDI reaches current voice limit - 500:
http://www.mediafire.com/?n528j9i28hkb99b

Surely one doesn't have 500 fingers, no <grin>?

[winner]

This MIDI reaches current voice limit - 500:
http://www.mediafire.com/?n528j9i28hkb99b

That's one craaaazy fast piano piece. One instrument generates 500 voices.... hmmmm.... how does that happen?

[Emil Weiss]

yes you are right

greets

[saga]

I guess it sends no note-off events at all? So it's more a like a buggy midi file?

[xmretroplay]

On the other hand, are more than 500 voices ever going to be needed?

Old Yamaha XG software synths could play / process up to 1024 (!) voices at the same time (selectable from 32 up to 1024 in the S-YXG control panel)
And that was ~15 years ago when everyone had slow Pentium III PCs

For xmp-midi, it's best to set a hard limit of 1024 voices max.

Then set the default (soft limit) to a reasonable value (256 voices)

Finally, add a setting to increase the voice count to 512 and 1024 (for advanced users)

[saga]

For xmp-midi, it's best to set a hard limit of 1024 voices max.

It's best to not set arbitrary limits at all (if possible), as discussed above. 1024 is yet another arbitrary limit.

[Ian @ un4seen]

It is actually possible to try a higher limit by editing the "Voices" line in the XMPLAY.INI file (the 500 limit will be re-enforced when "Apply" is used in the MIDI config window). So if anyone has any MIDI files that are hitting the 500 limit, they can try raising it that way to see if things sound different then, and let me know if it does

Just to reiterate, when the voice limit is hit, it will be the quietest voice that is stopped, and that is quite unlikely to be audible when there are 499 louder voices playing. The quietest voice is also likely to be one that is already fading-out after a note/key release, so it may have been stopping shortly anyway.

[mrmudlord]

hmm, for some reason Musepack'ed soundfonts wont load in xmp-midi, got latest official musepack plugin as well as xmp-midi stuff ver.

[Ian @ un4seen]

Yeah, only FLAC and Wavpack encoded soundfonts are currently supported by the XMPlay MIDI plugin. XMPlay doesn't have a centralised decoding system for plugins, eg. the MIDI plugin can't simply pass a soundfont's encoded data to XMPlay and have it locate a decoder that can handle the data and decode it. A less centralised system (the plugins communicate directly) was added to give the MIDI plugin access to other plugins' decoders, but only the FLAC and Wavpack plugins have currently been updated to support that as they were the formats that I found to work best for packing soundfonts. Musepack encoding does seem to work pretty well too though; I'll try to get an update up tomorrow.

[mrmudlord]

Yep, kode54 and I did some very extensive tests....Musepack seems to beat Opus in terms of quality versus size...
I'm not sure if kode54 told you this, but you are welcome to redist our soundfont packer we made for our BASSMIDI driver. It has presets for all the most common encoders that BASS is able to decode.

[Ian @ un4seen]

An updated Musepack plugin is now up on the XMPlay webpage. And here's a MIDI plugin update to make use of it...

   www.un4seen.com/stuff/xmp-midi.dll

As well as the Musepack support, this update includes a few other additions/tweaks, so it's worth downloading even if not using Musepack-encoded soundfonts.

[Firebrand]

Out of curiosity, what are the other changes to the plugin?

[Ian @ un4seen]

The other changes are support for modulation depth range (RPN5) and channel pressure destination (GM2/GS/XG sysex) events, and the reverb level (CC#91) now defaults to 40 (instead of 0) in accordance with the GM2/GS/XG specs. The sinc interpolation has also been tweaked a bit for improved quality.