Hi

If you import a perfomance you have the same waveform in user memory and library, but in this case this is what you want for creating a user memory or library without dependencies.

For importing the waveforms:

First identify the library sample name your performance use : Edit>Part Select>Element Select>Osc/Tune>

Search performance wich use this waveform in your library. (*)

Import this performance

Edit your user performance and modify the reference to waveform by searching the same name in your user memory (by waveform search)

If you see doublons in screen 'waveform search' for that name and filtering by user memory, first go to Contents>Data Utility>Waveform and delete the doublon (you see only the waveforms of user memory in this screen), then edit your performance.

Then store your performance

You can now delete the import performance then save your user memory.

((*)I have made an utility that find the performances using a waveform.)

I have a user database which includes lots of samples from loaded libraries. I made the mistake not to import the performances but store the modified performances as new. (So it doesn't include the waveform?) Is there a way to still import the waveforms and include them in the user file so I can use them on an other montage with other libraries loaded?

If you did not use the Library Import function to efficiently assemble the data into the MONTAGE USER Bank area, you still can create a file that can be loaded to another MONTAGE, but because you did IMPORT the data, unfortunately, your only option is to completely replace the data in the target MONTAGE. (Use the X7A BACKUP FILE format which saves everything as it is.)

(At least you realize it was a mistake not to have Imported the Library Data you wanted to make transportable data)... here’s why...

The proper way to create a new Library is assemble all the data in the User Bank, this means all Performances will be referencing User Bank Wave locations. This means if the Performance you want to make transportable is already installed in one of the 8 LIBRARIES, then in order to make that Performance transportable to a different Montage or to a new Library, you MUST use the Library Import Function.

What it does is take all the information that makes the selected Performance work, and duplicates it in User Bank locations. Instead of still referencing a Read Only Memory location of the Library, you move it to dynamic RAM location. Yes, it is now in the MONTAGE twice, but different wave Bank designations. If you know where to look, the Oscillator screen tells you exactly *where* the Source Waveform located. It’s not a mystery unless you remain unaware of the Oscillator assignment within the Element.

In other words, if you were to just start to edit a Performance, if it is a Factory Preset, your only choice is to STORE it to USER.
If you just start to edit a Performance, if it is a Library Performance, your only choice is to STORE it to USER.

In both cases, the Source Waveform does not move, it is in a fixed location. The difference is... in the first instance if you take that data to a friend’s MONTAGE it will play perfectly... because your friends Factory Preset Waveform List is exactly like yours. The second Performance will not transport to your friends MONTAGE because their Waveform Library List is not the same as your Waveform Library.

Just editing and storing a Library Performance does not move the Waveform data.
Only the act of Library Import does this, it actually copies everything to make the Performance work including the Waveform into the lowest numbered empty location in the User Waveform area.

Therefore, only when you want to make transportable files and/or only when assembling data into a new Library, would you use the Library Import function. As long as you are going to be on YOUR instrument fine but transportable requires IMPORT.

Using Import will allow you to “REPOINT” the AWM2 Elements in every case to the duplicated data in User Waveform area.
Ultimately, when all of the data you wish to make transportable is in your User Bank, and is properly referencing User Waveform locations, that’s when you can STORE/SAVE the data as a newly named LIBRARY FILE .X7L or as a newly named USER FILE.

The .X7L can be directly loaded to the backline MONTAGE as you require.
The .X7U can be loaded to the User area of the backline MONTAGE.

Hi,

Thanks both for your replies.

I like to have multiple libraries loaded for building new performances, so of course it is impossible to import all performances. And I don't know in advance which performance of which library i will need when merging new performances. So in order to have a nice workflow and not to interrupt the process, (look in library for a good performance to merge, store current one, go to utility, import the new performance from library, go to current performance, look for the imported performance in user bank) I would like to make a suggestion for a future OS-update:

When merging performances from user bank OR libraries, I think it would be great when you want to STORE it, the montage would ask if you want to IMPORT the wave files with it if it comes from a library. I think this would be very useful.

One more question, Does it matter in what order the libraries have been loaded on another montage when only loading a USER file which uses library waveforms?

Thanks!

Stef

(ps: I have never ever used the word performance this much) Performance, performance, performance,...

When merging performances from user bank OR libraries, I think it would be great when you want to STORE it, the montage would ask if you want to IMPORT the wave files with it if it comes from a library. I think this would be very useful.

This request shows you that you partially understand the concept. But your request is totally not necessary... when you want to Import the data you simply "know" to use Import, it has a specific use case. You are simply trying to justify your lack of knowing what to do initially. When merging Performances you will not suddenly realize , oh I want create a new Library.

When you are building new data recognize that if it is going to be made transferable you must build making sure that every portion of the data is pointing to User Bank locations - be those for Waveforms, for Motion Sequences, for Arpeggios, etc. For the firmware operation to "ask if you want to IMPORT the Wave files with it *if it comes from a Library*" while this seems practical to you (having forgot to do so initially) does not support *how* the instrument works. It is not an "Omega-13 button" that lets you go back and fix a previous mistake, sorry. You don't get an Omega13!
Simple rule: building Libraries means independently constructing it in various User memories.

You must decide this BEFORE you merge any data, don't you see that?
Your suggestion is for those who have made YOUR same error (forgetting to use IMPORT). SORRY, it will remain an error. For many reasons your suggestion simply could not work. At the last minute you want to decide to make all you've done an Import... it's not that it isn't a good suggestion for the mistake you made, its just that it don't work like that...

One more question, Does it matter in what order the libraries have been loaded on another montage when only loading a USER file which uses library waveforms?

Of course it matters... but not to the player accessing the data. Each Library (and you will begin to appreciate this) each Library is self sufficient. It contains all the Waveforms, Samples, Arps, Motion Seqs, Live Sets, etc., etc, that the data contained in it, need. It contains all the data needed by the Performances within it. So from a performer standpoint, no, it doesn't not matter.

ps: I have never ever used the word performance this much) Performance, performance, performance,...

capitialize it Performance when referring to the Mode or the MONTAGE Program. It is still a word you may wish to use in common language. "The musician performer recalled a single MONTAGE Performance and gave the audience the performance of a lifetime".