![]() It even splits up the percussion really well too, which is a nuisance channel with other converters.ĥ) The most channels I've ended up getting in feeding in some big MIDIs are 29 so I think your maximum is extremely fair.Ħ) The list of MIDI events is tough to make use of when there are a lot of events in the MIDI, so I think adding an event filter to hide a lot of what you aren't looking for would be a great addition to what you already have. The above two being addressed in the future would completely blow the need for PetiteMM out of the water except for machines it doesn't operate on.ģ) Your octave arrows are facing in the correct direction! ~yay~ This has been a really weird issue with past MML converters and while it's easy to address with Replace All, it's great that it Gets It Right The First Time™.Ĥ) The chord separation parses everything right - no funny sounds. I would love if in the future, the "mystery" gets smoothed out, and all notes can be translated correctly. Mostly, I am finding most of whatever is getting spat out as a % is a 16th note triplet or a dotted 32nd note rather than something really weird that should be written in ticks. So far, what I can see:ġ) The note pitch parsing is correct, but when a note spans across more than one bar, I am seeing that instead of translating it as a tie (^) it translates as another note (a-g+.) This is something that's easy to hear and manually address for me but it could just as easily be overlooked.Ģ) With some math and thanks to your automatic bar spacing, I can figure out what the %s are supposed to be. I have attempted making a few ports to help with testing and feedback. To me, it already does way more than PetiteMM and will take its place easily in my usage.įor feature recommendations, I'd recommend adding a way to directly output a conversion to a text file and perhaps more interfacing and interaction options, such as CLI and drag-and-drop for direct-to-text conversion for speed of usage. I did run into a lot of "unsupported lengths" in my test MIDI and will have to cross-reference with a MIDI editor anyways just to see what it should be. ![]() I love this tool! Thank you! Something important you didn't mention that your tool does, and it's fantastic for people who missed or didn't calculate channels ending short, is that you commented the number of bars each channel has so that it is easy to pad the rest out if nothing remains to merge in. This is going to take 99% of the tedium out of porting for me, because I've been splitting chords and percussion in a MIDI editor so much that it wasn't fun for a long time. The MIDI I tested appears to have several hundred events, so loading this dialogue and scrolling through was very slow (probably not much you can do about that as again, Wine) but also stable.Ġ041:err:tooltips:TOOLTIPS_Timer How did this happen?lmao Now, the MIDI event panel is extremely detailed. Conversion was a little slow, but it's likely a Wine thing. ![]() It turns out that if the MIDI is in the directory of the tool and you type just the name (with extension) of the file into the tool alone, it will read the file and output it to the buffer below. However, I did find a working solution, so good news for Linux users, but I can't say for sure the results will be the same on a Mac OS. ![]() The program doesn't appear to have a command line interface to just accept a file path/name either. I've tried dragging and dropping a MIDI over the icon too, and no action. I tried both in Windows format (backslashes) and Linux format, with the Z: drive prefix and without. I've tried typing in the full path manually and pressing convert, and nothing appears to happen. 0037:fixme:clipboard:import_text unsupported TEXT type "TEXT"Ġ037:fixme:xdnd:XDNDDATAOBJECT_DUnadvise (0xf74321f8, 3337652): stubĠ037:fixme:xdnd:XDNDDATAOBJECT_DUnadvise (0xf74321f8, 3337628): stubThen, I get a blank error window that I'm assuming is a program crash because when I force close it, it just kills the whole program.
0 Comments
Leave a Reply. |