Melodyne in Live
- • Loading the Melodyne plug-in
- • Melodyne in Live's Session View
- • Backing up and exchanging projects
- • Duplicating tracks
- • Saving plug-in settings for Melodyne
- • Bouncing/printing Melodyne edits (freezing/flattening)
- • Rewire
- • Miscellaneous notes
From this tour, you will learn how to make efficient use of Melodyne within Ableton Live. This tour relates to Live 9.
Please take note also of the information regarding the compatibility of Melodyne with Live on our website.
Loading the Melodyne plug-in
Load Melodyne as an insert effect into one of the audio tracks of the Live mixer. You will find the Melodyne Plugin in the Live browser under ‘Plug-Ins’ in the Melodyne folder.
You are advised, as a rule, to use Melodyne as the first plug-in in a track – i.e. before the compressor, EQ or other effects. The reason is this: during the transfer, Melodyne records the input signal you intend to edit – and with it all effects ahead of it in the signal chain, which are then frozen into the signal and can no longer be adjusted. In order to use your compressor, EQ and other effects in the usual way, you therefore need to make sure they are inserted after the Melodyne Plugin in the signal chain.
Melodyne in Live's Session View
If you are using Melodyne in Live’s Arrangement View, you can transfer audio to Melodyne, edit it and playback the results using exactly the same procedures as with any other DAW, all of which are described in our online user manual. However, Live also offers a Session View, and if you wish to use Melodyne in it, you should bear the following points in mind:
In Session view, Melodyne can sometimes be heard in the wrong places or not at all. Furthermore, Melodyne ignores clip changes in Session View and does not record transfers in the correct places. All these phenomena stem from the principles upon which Live operates and its special way of handling time. The clips in Session View represent small loops within the linear running time of the Arrangement in Live. It is from this Arrangement time that Melodyne derives its timing information; Melodyne is not informed about loops hidden within clips. Schematically, the picture looks like this:
Whilst the clip is still cycling within in the loop, Melodyne has long since moved on. If you nonetheless do wish to use Melodyne with clips in the Session View, you should activate Live’s global (Arrangement-) loop and set it to the length of the clip that you wish to edit with the plug-in in Session View. Then the loop of the linear time (and therefore also of Melodyne’s time) will correspond to the loop of the clip to be edited:
Given all this, it follows that it is impossible to record and subsequently play back the switching of clips on a track in Melodyne in any sensible way: if you switch clips during the transfer, Melodyne will still record the contents, but do so along the linear time axis that is determined by the arrangement. And the contents will be played back accordingly. It is therefore not possible to reproduce in Melodyne clip changes implemented in Live’s Session View, as Melodyne is always guided by Live’s linear Arrangement Time rather by that of individual clips.
You are therefore recommended to use Melodyne only when working in Live’s Arrangement View. But you would presumably do this anyway when editing vocals or other instruments. Besides which, Live offers user-friendly functions for transforming clips into building blocks of the arrangement, editing them there in Melodyne and then rendering them once more as clips.
Backing up and exchanging projects
During the transfer, Melodyne captures the track’s signal, creating recordings of the corresponding passages. The resulting audio files are stored in a folder of their own that you create in Melodyne via Settings/File Manager. It makes sense to create a subfolder like this within the project folder of each Live project. Then assign your transfers to this folder in the first instance of Melodyne you create. To do this, choose within Melodyne “Settings > File Manager > Store Transfers to ...” and then navigate to the folder in question by clicking on the ellipsis (“…”) icon.
Following this procedure ensures that when archiving or passing on your work, all the files you need will be in your project folder and not elsewhere on your computer.
If you are copying your project to another location, you should then immediately open the copy followed by an instance of Melodyne within it. Next choose “Settings > File Manager > Store Transfers To” and navigate as before to the newly copied Transfers folder to assign the path. Click for the purpose on the ellipsis icon (“…”).
If you didn’t set the transfer path prior to the first transfer, you can do so at any time later. Melodyne will automatically gather the data for the tracks already edited and move it to the storage location you have chosen as soon as you assign a path to it using the “Store Transfers To” command in the file manager.
When archiving and passing on projects, you do not need to worry about Melodyne’s audio cache, the size and location of which can be selected from Melodyne’s Preferences dialog. Melodyne will automatically restore the parameters found there, so there is no need to archive or copy them separately.
Sometimes you may want to copy a track including its Melodyne instance and Melodyne editing – in order, for instance, to generate a second voice. To do this, right-click on the “Duplicate” command in the mixer or audio track area.
Saving plug-in settings for Melodyne
Just as with an effects plug-in you can store different settings as presets, in Melodyne you can save different edits. You may wish to do this in order, for example, to allow a performer or artist to hear and choose between different edits of the same take. To save and reload Melodyne settings, follow the same procedures as for all other plug-ins.
Use for the purpose within the relevant effects chain the preset manager for the Melodyne plug-in. Save your current settings using the corresponding symbol and assign a name. You can store alternative edits as additional presets and switch between them using the preset selector.
Bouncing/printing Melodyne edits (freezing/flattening)
When you are using Melodyne in a project and have finished editing, you have two choices:
i) You can allow the Melodyne instance(s) to remain active until the final mixdown. If you do this, you will retain access to your Melodyne editing and will be able to make further refinements until the very last moment. This is convenient, but as long as the plug-in remains active it is draining the resources of your system.
ii) You can transform your Melodyne edits into new audio files. This will deprive you of further access to your Melodyne editing but free up resources, as the plug-in will no longer be in use. Turning your Melodyne edits into new audio files has the further advantage of allowing you to pass projects on to colleagues who don’t have Melodyne.
To transform a clip edited using Melodyne into a new audio file in Live, either of two techniques suggest themselves: one is simply to ‘freeze’ the track in question and the other to ‘freeze’ and then ‘flatten’ it.
"Freeze Track": With this option, which you will find in the track’s context menu, you can transform temporarily your Melodyne editing and any subsequent insert effects into audio. The advantage? The track is now a pure audio track and Melodyne is inactive, freeing up resources. Furthermore, you can unfreeze the track (also from the context menu) at any time in order to modify your Melodyne editing. The disadvantage? Any additional insert effects are also frozen and cannot therefore be modified either without unfreezing the track. Similarly, it is impossible to add new effects to the track while it is frozen. Freezing a track is best used, therefore, as a quick temporary measure designed to economize on resources rather than as a permanent solution.
"Flatten": If, rather than merely freezing a Melodyne track temporarily, you wish to transform it permanently into a new audio file, after freezing it you should select ‘Flatten’ from the track’s context menu. This command transforms the frozen track into a normal audio track reflecting permanently the result not only of your Melodyne editing but also of any effects that follow it in the signal chain. To avoid these insert effects being flattened along with your Melodyne editing and to make it possible to modify them later, before freezing and flattening the track, you should remove from it the insert effects in question (e.g. by dragging them to an empty track). Once the flattening process is complete, you can drag the effects back onto the Melodyne track and use them as freely as before.
Generally you will want to use Melodyne as a plug-in in Live. This is the most convenient way of working and means, moreover, that all Melodyne data is stored within your project structure, making archiving and passing on projects easier. Occasionally, however, you may wish to link the stand-alone version of Melodyne to Live as a Rewire client.
This can be useful if, for example, you wish to adjust samples quickly to the project tempo. When the program is integrated via Rewire, this happens automatically as soon as you drag a sample from the finder or explorer and drop it in the Melodyne window. You can then play back the samples at the correct tempo via Rewire and make further use of them in Live, enhancing them there perhaps through the application of additional plug-ins.
To link Melodyne Stand-Alone with Live as a Rewire client, proceed as follows:
First launch Live and within it create an audio track. In the Inputs/Outputs area, select as an input “Melodyne singletrack”. When you later launch Melodyne, a Rewire connection will be established automatically. The transport functions and tempo of the two programs will also be synchronized.
Now, from the Rewire pane in the Melodyne user interface, select the pair of outputs you wish to use for the audio transfer of this Melodyne document to Live. If you are working with a single Melodyne document, select within Melodyne “1-2”.
In the input area of the corresponding Live track, select also beneath “Melodyne singletrack” the corresponding pair of inputs. So as to be able to hear the signal permanently, activate input monitoring for the corresponding track.
You can, if you wish, open multiple Melodyne documents and transfer their audio via separate channels to separate audio tracks within Live.
Now load or else drag and drop the desired samples into Melodyne. These will then be analyzed and adapted to the project tempo. When you have finished editing the sample(s) in Melodyne, you can transfer the corresponding audio signals via Rewire from Melodyne to Live and record them there.
Please note that data from Melodyne is not automatically saved along with your Live project when the two programs are linked via Rewire. To make it possible to recreate an earlier work situation, you must save the Melodyne document manually in the form of an MPD file – ideally in the project folder of your Live project. When saving, activate the option “Save Copy of Audio File(s)” to ensure Melodyne saves a copy of the sample in the project folder.
We recommend an audio buffer size of 1,024 samples. Smaller values lead to a marked increase in the CPU load.
Should you require a smaller buffer, e.g. when adjusting the headphone mix directly in your computer and not via an external channel strip or mixer, switch all instances of Melodyne during the recording to bypass Reactivate Melodyne as soon as you begin editing your new track.
Plug-in format under OS X
Under OS X, you can in principle use Melodyne in Ableton Live either as a VST 2 (32-bit) or as an AU (32-/64-bit) plug-in. We recommend use of the AU version.
Time signature changes
Melodyne not only follows the time, as described above, but also the timeline of the Live arrangement. If you are working on the clip level, however, with different time signatures and insert these clips into the arrangement, discrepancies can arise between what is heard and the time signatures displayed. The problem here, however, is purely a visual one; the correctness of the audio output and editing functions of Melodyne, including the quantization, are in no way compromised by it.
If you automate the song tempo in the master track within Live’s Arrangement View, Melodyne and Live no longer run in sync or lead to a premature break off of a transfer. One workaround for this consists in transferring all tracks without any tempo changes to Melodyne first and then rendering the tracks edited with Melodyne, before using the tempo automation.
You can also, however, alter the tempo in Live manually by setting a new constant song tempo in the Tempo Field. If you then use the Tempo dialog in Melodyne (reached via the broken chain symbol), Melodyne will ‘learn’ the new tempo.