In this way, Melodyne obtains the audio data that it must have if it is to detect and display the notes. This is the purpose of what we call the “transfer”: This is essentially a recording process whereby the plug-in implementation of Melodyne makes its own copy of the track segments playing back in the DAW. But Melodyne, as we have seen, requires a more comprehensive overview for this reason, you have to send it in advance the track segments you wish to edit, so that it can study them. Since most commonly-encountered plug-in interfaces are designed for pure real-time operation, a plug-in, logically enough, is only shown the part of the audio file that is being played at that instant, which is rather like looking through a keyhole. In the case of the plug-in, the matter is somewhat more complicated. In the stand-alone implementation of Melodyne, this is when the audio file is first opened. Since for this analysis the audio file has to be examined as a whole, it cannot be conducted in real time it is performed once only, at the start, before the first blobs appear in the Note Editor. Before it can make its editing functions available to you, Melodyne must first analyze the audio material.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |