Quote:

Do you have an imported MIDI file in some songs, where it might have its own patches?



No imported midi. Unless it was in the styles/songs included/created in biab v.2009 thru 2011.

Quote:

About the "curious issue in the "+" dialog", yes, I've seen that in the other Roland patch maps. Whoever made and named the patches, or alternatively, whoever made the patch map, chose to call certain patches member of a group a family. Some make sense; many do not.

My alternative: I edited a copy of the patch map to copy those instruments I use all the time to my own groupings at the top of the patch map. It's just a text file, and it's OK to have a particular patch appear more than once in the file. With mine set up in groups named Acoustic, Electric, and Horns, I can almost always find the patch I want at the top of the list.



Matt, yeah, I have also edited the physical position of the text listings in the .pat for convenience. Will probably try some favorite grouping, as you suggest. Great idea, Matt. I read in in the narrative of one of the patch files that a biab .pat has a 1,000 line limit. Is this still so?

In the "+" dialog, when an instrument is selected from the pull down menu, the search result sure isn't "keyed" to the text descriptors. e.g., select "piano", the results vary and include descriptors without the word "piano". Therefore, it must be keyed to the msb, lsb and/or patch numbers - as these numbers are the only other characters appearing in the .pat. My guess is that the programming that was used in this function probably pre-dates msb/lsb.

Maybe PG can update this function.

In the "+" dialog, the "search" button *is* keyed to the text descriptors. But "all" patches must be displayed and the result simply finds and highlights - one at a time - the next corresponding text - one at a time - while displaying the *entire .pat list*. To find and highlight the next match, the "search button" dialog must be opened and "ok" selected, again....and again...and again.

It would make much more sense and be much quicker and easier for the "search" function to populate a new display result which displays >only the matches< - not the entire freaking 1,000 entries of the .pat.

Maybe PG can update this function, too.