Yep, the "+" window functions are a mess.

Well. I'll call support and ask if an update is possible. If PG won't or can't change the (dys)funtionality, I'll just have to bite the bullet and spend the hours doing some major editing of the .pat file patches into instrument groups, as you have, Matt.

Hey, wait! Isn't Biab supposed to be fun? lol

Re: the "unsaved patches" / JV-1080 playback in my biab song files:

The best theory I have is that the offending files originated on my laptops with previous builds ie, Biab 2009, 2010.

I use the lappys like a portable scratch pad for jotting down ideas when away from my desktop DAW. Then take the file to my desktop with all it's hardware, higher quality audio processing, softsynths, daw software, etc. for further processing. I have a fresh install of biab 2011, now build 317, on the pc.

It seems that most of the biab files I'm having those patch troubles with on the hardware synth, JV-1080, originated on the lappies. I use NI Bandstand, Garritan or Roland softsynths on the lappies. Of course, they're GM.

On the pc, Biab plays these saved GM files ok with softsynths. The hardware synth, JV-1080 will play *some* , not many, of these biab files ok *when switched to GM mode*.

I haven't found *one* of these created-on-another-machine-files that will play correctly *through the JV* when it's in "Performance Mode" - it does not play the GM patches from the biab song file, just the patches native to the "Performance 1 Template" created and saved in the JV-1080 itself. Obviously, the patch message isn't getting through. (Weird, when the file loads on biab/pc, the correct patch names appear in the main Biab Gui for each instrument button, but don't play through the JV.)

Now, get this....

If I load a created-on-another-machine-file in biab on the pc, then *re-select* the same instrument patches through the "+" dialog, *re-save* the patches through the "File, Save with Patches..." window - it works! Re-load the file and it plays the just re-saved GM patches fine through the JV in the very same Performance Mode using the very same Performance 1 Template. I do not understand why, but, apparently, the problem may be resolved by re-saving each of the files as above. This worked on a dozen or so files I tried this morning. {keeps fingers crossed}

Not a clue why this is so. GM is GM.....? I guess some midi message is getting lost.