When exporting a library, will that library include only the user waveforms connected to performances, or also orphaned waveforms that don't belong to anything? If the latter, is there any way to clean up your user waveforms so that only those actually in use remain? Basically, how do I ensure a library isn't larger than it needs to be?

Excellent questions...

Care should be taken so that orphaned Waveforms are eliminated by never including them in .X8L File.

At first that sounds circular— but if by “exporting a library” you mean creating a new custom Library File that can be then loaded in any MONTAGE or MODX, then there are basically two methods to create the File
1) By assembling just the data you wish to include in this File in the MODX’s internal USER Bank... then *save as...* using the “Contents Type” = Library File to generate the .X8L File.
2) By assembling just the data you wish to include in your Library using the Melas Waveform Editor (MONTAGE/MODX)...

Method 1 On board the MODX
In the first method, you will manually assemble just the data you wish to use — purposefully avoiding duplicates and orphans (we’ll explain how below) — If you are assembling data from multiple Library Files, you can load them, as Libraries temporarily into the MODX.

You then will play through the Performances of that Library, create a list of the names of the Performances you wish to include in your new custom Library. Once you have assembled the list, you will use the LIBRARY IMPORT routine to move those Performances into your User Bank.

Rule: it is always possible to create a Library File by saving the contents of your USER Bank — you are telling the MODX to create a special type of file that includes instructions to write the data into the Flash memory (semi-permanent). Data written to one of the 8 Library locations is never overwritten by a LOAD process... it will remain until you specifically DELETE it (or initialize your entire instrument).

The “Library Import” is a function that moves and repoints all necessary Waveforms used in your selected Performances from the Library location, so that they have a place in the USER Bank and the Waveforms are copied to the User Waveform area. And because you will mark *just* the Performances that you will use, no duplicate or unassigned data will be moved to the User location. This means no unnecessary data will be written into your custom Library File when you create it.
[UTILITY] > “Contents” > “Library Import”
Using your list, find and mark each Performance name
In one operation they all will be moved (added) to the data User in your User Bank. Any orphaned Waveforms are screen out by this process.

Once you have extracted the Performances from that set, you can then Delete the temporary Library source data... making room for more...
Load your next candidate temporarily into a Library location... continue assembling data from this new candidate. Again, you simply play through the Library decide what Performances you want... write down the names. Then once you have all the Performance names, go to “Library Import” — mark each Performance and in one operation you will add these new Performances, including just the Waveforms and Arpeggios that make them work... these will be added to those already in your User Bank.

The Import function will add these new Waveforms to the end of the catalog listing for your USER Bank.

You can continue assembling data in this fashion... until you have 640 Performances... in your USER Bank. This is what we mean by “assembling” just the data that you wish to place in your Library in the Library File... you avoid orphans by choosing the Performances... the MODX does the heavy lifting sorting out the Waveforms and Samples.

The IMPORTING of the Performances from each candidate must be done in one operation to ensure no duplicates. Any unassigned Waveforms (orphans) are screened by this process. Once all your data is successfully housed in the USER BANK
[UTILITY] > “Contents” > “Store/Save” > set “Content Type” = Library File
The end result is a File that when LOADED will write the data, Waveforms and all, to FLASH.

Method 2 Using the Waveform Editor
If you have the Melas MONTAGE/MODX Waveform Editor... the concept is the same.
You open each Library File in the Editor... and you open an empty File into which you’ll assemble your data.
You basically drag and drop the Performances you want into your empty File template, the Editor sorts out everything.
You can have it search and remove duplicates and orphans and discard them. You then can save the new Library as a Library File

They both do the same thing — the Editor gives you a mechanical advantage in that it is quick and visual.
It does what you can do manually on the MODX as I’ve outlined above.

Ok, thanks. So basically (if doing it on the MODX) the answer is "don't make mistakes". 🙂

I mean, there are other ways to end up with orphan waveforms (importing a performance and then deleting it, which doesn't delete the associated waveforms, or manually importing the wrong waveform when creating your own sampled performance), and then I guess the only way to get rid of them is to either manually delete those waveforms or clear the user data and start over.

No, those are not the only way... say you imported a Performance, then changed your mind and you Delete the Performance, you are correct that would leave the dreaded orphan (unassigned Waveform)... this is when you go ahead and SAVE AS ... a (temporary) Library file... Load that temporary Library File into Flash, then use “Library Import” to import just the Performances that you want to place in your permanent Library. (When writing a Library you use ink, not pencil... so permanent ink means “a do-over”... )

If you have loaded your own Waveform, that’s different... doing so will mean you know it and you know where it is used...
Press [UTILITY] > “Contents” > “Data Utility” > touch the “Waveform” Folder. Here you will see the current User Bank Waveforms (only).

This happens because — If it was a Waveform that you loaded directly into an AWM2 Element, you’ll find it in the Waveform folder. Tap it to see the pop-in menu, tap DELETE.

If you know that a Waveform is an orphan, you can manually delete them using the Data Utility Folder, but often, especially when you did not create the data yourself, you don’t know which Waveform is which... and when that is the case, “do it over”... but if you know a Waveform is an orphan, just hanging out, unattached to anything... you can simply Delete. Even in your first example... if you Deleted the Performance but you took note of the Waveform name... you’re in business. Find it, tap “Delete”. Just be sure it is not used elsewhere.

It is the contents of this Waveform Folder that get installed in the File when save as LIBRARY FILE.
Creating a LIBRARY FILE, literally, takes the data in the Arp folder, the Live Set folder, the Motion Seq folder, the Performance Folder, and the Waveform folder and bundles them in the Library File.

I'm not sure if there's an ideascale item yet asking for a "Waveform Prune" option to manually clear unused waveforms in the user area. Also, not sure if there's an ideascale item to request a feature which analyzes the waveform usage in response to saving a user, library, "all" file and automatically prune out the unused waveforms. A prompt to let you clear out the unused waveforms and elect to prune (or not) before saving the library/user/all file. Both would help enhance the on-board user experience.