So here are some suggestions/questions in order to improve the documentation/intuitivity/ergonomy : But I'm not good at writing documentations either. a Midi channel which plays chords of 3 notes at the same time would be mapped to three YM2612 channels), but that's another thing I never did.Īnd yes, the documentation isn't good at all. This is another thing which would be addressed by a single global mid2vgm tool.Īnother thing which I wanted to implement was a "chord mode", which would allow you to map a polyphonic Midi channel to more than one channel in the vgm (e.g. Vgmmerge can still be useful to create things like this (2×YM2612 + 2×YM2413 + 2×SN76496) or this (2×YM2612 + 1×YM2413 + 2×SN76496) however, since ValleyBell and I used different algorithm to handle the tempo, the YM2612 portion of such a vgm will drift by a few dozen samples by the end of the song. Of course there are way more parameters than those but it's a pseudocode extreme exemplification. From a programming point of view it would be as simple as adding separate routines to handle the different chips, such as NoteOnYM2612(channel, note) and NoteOnYM2151(channel, note), or passing a parameter to a generic routine which will later address the request, like NoteOn(chip, channel, note). See those comboboxes? I wanted to add more chips there, such as the YM2151, but I never ended up doing so for various reason (primarily, the lack of collections of YM2151 instruments, unlike YM2612 instruments which can be found like everywhere). That's what I had in mind when I designed my own mid2vgm converter (which targets 2×YM2612): No, I mean a gigantic mid2vgm tool where you can map any Midi channel to whatever you want.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |