This allows a lot of new possible use cases in a production environment that wouldn’t simply be possible with a real-time plugin. Using the snapshot trigger, you may use our instrument as a neat 4-voiced sample player, with all its implications. But for this, we have to know the complete melody line. So, what we intend to do is trying to implement the musical knowledge and experience and come up with nice harmonizations even for unexperienced users. This is indeed pretty neat, but either the user exactly knows what he is doing musically or it will be the just parallel voices, which isn’t very musically. Alternatively, the user may play all single pitches in realtime on a keyboard (knowing what harmony will fit and about a pleasant sounding voice leading). How should they know what harmony is intended without knowing anything about the melody, not even the key? There are harmonizers around that do have a realtime approach, where the user has to adjust the input key, and the voices run then parallel (in diatonic intervals) to the input voice. Think of 4 singers that try to sing a four-voice choir, but only one voice knows its melody, the others do not have any clue. Harmony Estimation and Voice Leading is theoretically not possible in realtime.deCoda does give you the mapping of chord changes over the whole song, so be aware that TONIC does not do this in case you were hoping to bring that sort of deCoda functionality into your DAW. TONIC is not a “chord-detection plug-in” but is rather a “key-detection plug-in”. What TONIC does not do, unlike deCoda, is provide a mapping of chord changes throughout the song. You can try this with all three keys and see if there’s one scale that sounds particularly interesting to you, and then start building up your song from there. TONIC provides a keyboard which, when clicked, will play corresponding audio tones so you can hear if those particular notes are indeed fitting with the music that is being analyzed. If you haven’t already committed to heart the scales for all 24 possible keys, then this can be helpful in learning them. Additionally, for any key you select in TONIC, the plug-in will provide guidance on the notes and chords that fit in that key.TONIC will be able to show you these alternatives while deCoda will not. However, if you’re working in a DAW and want to know what scales may work with a small audio loop or vocal line-a part which is not as harmonically complex or rich as a full song-then there could actually be a few keys that could fit with that part. When analyzing full songs like you’d do in deCoda, the analysis does usually give you the correct key for the song. TONIC will not only show you the key that it is most certain is a fit for the music-deCoda will only show you this most-certain key-but will also show you two other possible keys that might also be a fit. However, things differ a bit in that TONIC has a few extra features around the musical key that deCoda does not: Therefore, deCoda isn’t going to give better results than TONIC in terms of the key detected for the song. As you may suspect, deCoda and TONIC share the same exact technology for determining the key of the music. It shows up in the bottom-left corner of the deCoda window. It is true that deCoda, as one of the numerous algorithms it runs on the music, does detect the key of the song. If you’re looking to bring some of deCoda’s technology into your DAW, then TONIC might be useful to you. This means there’s already a big difference in use-case right from the start. The answer depends on what you’re trying to achieve and your specific workflow.įirst of all, deCoda is a standalone app but TONIC is a plug-in which must be used in a host (Ableton Live, Steinberg Cubase, PreSonus Studio One, etc.).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |