Soundmondo and Connect both do not save user waveforms, curves, microntonal, etc. This may or may not affect what you're trying to share.

MODX Connect would probably be easiest because there are less things to go wrong in the setup phase.

With Soundmondo you have the choice of public (everyone) or private (no one except yourself can access). Not sure either of these security models will fit what you're after. I'm assuming this is still how it works unless something has been updated.

Alternatively, you could first save your user area to backup just the User bank (save an X8U file) then erase everything except the one Performance you want to share. Then create a user file (X8U) with just the one Performance to share. Then load back up the original X8U you saved with all of your user content. I didn't say it would be easier - just an option.

Those are the free options.

At cost has been suggested already. I don't have the package so I cannot comment on the details.

Screenshots?

Blimey...

Just tried this with a friend, using MODX at both ends, and custom user waveforms that we both have in the same library.

Emailed him the file created by "Save" feature of Connect (only 8kb). He could load it, and it referenced the right custom wave files despite them not being in the emailed little file, which is of the type:

sharedPerfName.X8B

He used the "Load" feature of Connect to load it from a saved location in his File system on his computer.

Quite positively surprised at how seamless this was.

It was harder to get MODX Connect to connect than anything else about the whole process. Moral of story is do not connect MODX via USB until your computer has fully started. And connect MODX before launching MODX Connect. And DO NOT WIGGLE THE CABLE. It doesn't like the MODX being plugged out and back in again. Restart MODX Connect if connection is lost due to cable wiggles.

Now... back to cleaning out Patterns...

@Jason's suggestion would work, using "User" or "Backup" files, but both you and your buddy would need some patience.

Another way is:-

1) Save your performances as a Library File.

2) Make a Backup File.

3) Reset ALL. (takes you back to a clean machine).

4) Load in the Library you made in step 1.

5) Import the "One Performance" in question.

6) Make another User Library to a CLEAN USB Stick.

7) Give that USB STICK to your buddy.

8) Your buddy then loads in that Library which has the Performance, and any custom waveforms it was using.

[quotePost id=117299]@Jason's suggestion would work, using "User" or "Backup" files, but both you and your buddy would need some patience.

Another way is:-

1) Save your performances as a Library File.

2) Make a Backup File.

3) Reset ALL. (takes you back to a clean machine).

4) Load in the Library you made in step 1.

5) Import the "One Performance" in question.

6) Make another User Library to a CLEAN USB Stick.

7) Give that USB STICK to your buddy.

8) Your buddy then loads in that Library which has the Performance, and any custom waveforms it was using. [/quotePost]

Probably should point out that this, on a moderately loaded MODX, will take about 2 hours, minimum.

Takes about 20 minutes.

Antony, you're wrong. Some of the individual steps take longer than that, alone!

And you risk losing everything you've made if the backup fails.

This is not only a needlessly long process, it's also an irresponsible suggestion for the desire to share a single performance, in my opinion.

[quotePost id=117274]Seems obvious if you can upload to SM you should be able to export to USB.

If not, what do you suggest.[/quotePost]
The most reliable and complete way is to use John Melas Waveform Editor.

1. You create a User File from your MODX.
2. In Waveform Editor you create a new, empty MODX (or Montage) User file and you also open the User file from step 1.
3. Drag n drop the required Performance from your User File into the new, empty one. The Waveform Editor will automatically copy all the dependencies required: User Waveforms, User Arpeggios, User Curves.
4. Save the new User file or Export it as a Library File.