At the moment, no, because I couldn't think of a great way to visualize very complex MIDI commands. For example, if it's a batch MIDI command with 10 MIDI commands under it, or system exclusive commands that are 150 bytes long, how should that show up? The row height would have to be enormous for all of that data to fit. Regardless, I'll still look into an option for this as I know some users really want it. The other problem is that I don't normally read out the MIDI data for a song unless it's been loaded, or if it is set to "Load song on receive" as I have to be monitoring for those messages. In order to show this data, I will have to read out the data for every song in the entire library, which will significantly increase the memory usage and slow down the initialization. So that's something to keep in mind. With the way the the framework is set up, I can't just read out the MIDI data by itself without potentially causing problems later, and I don't want to have to query the database to populate the list, as that would cause major perform issues when actively filtering.
Mike
Mike