Copy to new project

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

I have a project that crashed and I'm using the crashed/backup version. The problem is since using the "backup" it seems to be using allot more cpu than expected and a couple of synths (breaktweaker and Diversion) make an electrical interference noise on first play of the track. There,s no artefacts on further "plays" though, just a type of distortion I associate with over driven speakers. What I'm trying to do is copy all my patterns from one mulab session to another open session and hopefully that would sort whatever is causing the artefacts/cpu load. But I cant seem to copy them over though,,, I'm probably making a newby to Mulab mistake any advise.
In Orion there was a handy facility to merge tracks where you could just select a synth and all its patterns/effect (if wanted) into the open project. This was also good for opening a project track by track to eliminate bad synths/fx that crashed a project. is there anything like that , that I may have missed in Mulab ?

Post

With the rescued project open, make the Browser visible using the button to the left of the play button. In the browser, set "What" to "Sequences" to see the event sequences your composition sequence parts are using. You can save these as presets or export as a MIDI file (that's on the right-click menu). If you set "What" to "Audio Files", you'll get the list of streamed audio files your composition audio parts are using. These should already be somewhere on disk, so you should be able to recover them separately. Setting "What" to "Samples" shows the samples in use by the composition in MultiSampla - I think it shows all the project-specific ones, regardless of where the MultiSampla is used. The same applies to setting "What" to "Multi-samples". However, the options you have are very different. For Samples, these start off as embedded in the project file (except the factory library). You have the option to save these out to disk files. As multi-samples are specific to MuTools, you can only save them as presets.

So, that's all the bits of your project and gives you a way to export them all to disk to re-assemble in a clean project file.
MuLab has many options for consolidating your project. You can select all the sequence parts on a track, for example, and then "merge selected sequence parts" to form a new sequence and a part playing that sequence. You can also mix down a single track from the sequence parts plus targeted outputs to a new audio part on a new track. You do that by selecting the track and choosing "Render selected parts as new sample", then making sure "Create New Part Using Result" is checked.

Remember to back up the recovered project before starting any of this, of course... :)

-edit- (+) VST/is: of course, you can save the current settings to an FXB or FXP. Or, if you think the whole Rack is fine, you can save the rack out as a rack preset. Simiarly for anything in a MuX - either save the whole MuX out as a preset or save the bits inside to individual files.
-edit- (+) You can also clean up the project to remove all "unused" sequences, etc. You really, really want that back up first, of course...
Last edited by pljones on Sun Jun 04, 2017 4:30 pm, edited 1 time in total.

Post

Thanks pIjones I've had a look at what you have suggested and there's lots of sequences to sort out, so I'll have a look another day, I've had enough for now. :neutral:

Post Reply

Return to “MuTools”