Q: Best practices for text prompts in Composition Workflows

Best practices: Text prompts provide a powerful interface for generating personalised chord progressions in Composition Workflows. As with any generative AI applications though, not all prompts are created equal, and some may yield better results than other. Here are some tips to help you get the best out of your prompts: <ul> <li>** Use english **: while you may have success using prompts in popular languages, for best results, we highly recommend writing your prompts in english</li> <li>** Rephrase your prompt **: if you notice that your existing wording does not yield great results, try completely rewording the sentence with synonyms.</li> <li>** Clarity is key **: the more specific your prompt is to achieve what you want, the more likely you are to get the results you expect. For example, the prompt "A progression which may include 7ths" is less likely to produce a chord progression containing 7th chords than the prompt "A progression that always includes 7ths".</li> <li>** Avoid musical conflicts **: some concepts in your prompt may reference to very different musical intents. For example, if you ask AIVA to generate "a complex and dissonant chord progression in the style of the Moonlight Sonata by Beethoven", don't expect the results to reflect the first part of the prompt, since the Moonlight Sonata's harmony is rather simple.</li> <li>** Use roman numerals instead of chord letters **: if you want to include chords in your prompts, we recommend you use roman numerals as opposed to letters. For</li> </ul>

Q: Upload MIDI Guidelines

How should my MIDI file be formatted for the best results? <ul> <li>Any orchestrated MIDI file of a composition generated on the music engine is a good example of a format that will work well as an influence.</li> </ul> Your MIDI file should follow those formatting standards: <ul> <li>Contain more than a single musical idea: If a MIDI file contains just a single melody or bass line, for example, there will not be enough information to learn from</li> <li>Organise instruments and musical parts (melody, chords, bass, etc) across separate MIDI tracks. AIVA looks at individual MIDI tracks to perform the analysis if all the notes of all musical sections/parts are in the same track, the results won't be ideal</li> <li>MIDI channel 10 should be reserved for percussion only.</li> <li>Contain a quantized score - performance recording in MIDI will not work well as input since the notes are likely to deviate from a clear metric structure, which may cause problems during the analysis.</li> </ul> The following guidelines are recommended (but not necessary, don’t worry if you don't understand those): <ul> <li>MIDI program change events (for instruments) on each track. Currently, AIVA uses the MIDI program change events to determine the instruments that are playing when analyzing the orchestration. If the instrumentation is unknown or only specified in the track names, you can always set the ensemble type of the influence when uploading the MIDI file, or correct the ensemble type detected automatically after the analysis is complete.</li> <li>Accu</li> </ul>

Question 1

I don't understand the terms of License

Accepted Answer

Under a Free Plan

You may use the tracks that are created under a Free plan for non-commercial purposes. That includes ANY use cases that are meant to be non-for-profit, and that are not promoting any commercial activity in any way.
The copyright of the tracks you create is owned by AIVA
You MUST give credit to AIVA when using the track. For example, if you are publishing a video on Youtube with some music composed by AIVA under a Free Plan, you can add the following line in the description of your video:

Soundtrack composed by AIVA (Artificial Intelligence Virtual Artist): https://www.aiva.ai

Under a Standard Plan

You can use the tracks for monetized content only on YouTube, Twitch, Tik Tok and Instagram.

The copyright of the tracks you create is owned by AIVA
You DO NOT need to give credit to AIVA when using the track

Under a Pro Plan

The copyright of the tracks you created is owned by YOU. This means you can use the tracks in ANY way that you like, for as long as you are using AIVA as an individual, or a small business that generates less than $300k in annual revenue, or has less than 3 employees. If you are part of a business that doesn't fit this criteria, please contact us here

When you upgrade to Pro Monthly or Pro Annually, you will own the copyright of all of the compositions created before your subscription started AND during your subscription.

If you decide to cancel your P

Question 2

General User Manual

Accepted Answer

${color}[#000000](Creating a track, Composition Workflow & Import MIDI) Creating a track Creating a track from a Chord Progression Creating a track Step by Step Import MIDI Duplicating a track Downloading a track Sharing a track

Style Designer Creating a Style Personalising a Style Creating a track Publishing a Style Using your Custom Style with the Composition Workflow Feature Styles Library Organising

**Editing a track ** Opening a track in Editor Changing the zoom Viewing multiple layers at once Adding Effects Section Editing Changing the BPM Adding a custom layer Instrument Editing Note editing Listening to the changes Saving the changes Percussion Editing

Uploading an Influence [Upload an Influence

Question 3

Upload Audio Guidelines

Accepted Answer

How should my audio file be formatted for the best results?

Any recent audio recording, that contains enough musical content should be accepted. Please note, uploading non-musical content like speeches, conversation, nature noises and various ambient sounds will not work.
The uploaded audio file needs to be anywhere between 1 minute - 20 minutes long
The uploaded audio file needs to be in .mp3 or .wav format

Question 4

Best practices for text prompts in Composition Workflows

Accepted Answer

Best practices:

Text prompts provide a powerful interface for generating personalised chord progressions in Composition Workflows. As with any generative AI applications though, not all prompts are created equal, and some may yield better results than other. Here are some tips to help you get the best out of your prompts:

** Use english **: while you may have success using prompts in popular languages, for best results, we highly recommend writing your prompts in english
** Rephrase your prompt **: if you notice that your existing wording does not yield great results, try completely rewording the sentence with synonyms.
** Clarity is key **: the more specific your prompt is to achieve what you want, the more likely you are to get the results you expect. For example, the prompt "A progression which may include 7ths" is less likely to produce a chord progression containing 7th chords than the prompt "A progression that always includes 7ths".
** Avoid musical conflicts **: some concepts in your prompt may reference to very different musical intents. For example, if you ask AIVA to generate "a complex and dissonant chord progression in the style of the Moonlight Sonata by Beethoven", don't expect the results to reflect the first part of the prompt, since the Moonlight Sonata's harmony is rather simple.
** Use roman numerals instead of chord letters **: if you want to include chords in your prompts, we recommend you use roman numerals as opposed to letters. For

Question 5

Upload MIDI Guidelines

Accepted Answer

How should my MIDI file be formatted for the best results?

Any orchestrated MIDI file of a composition generated on the music engine is a good example of a format that will work well as an influence.

Your MIDI file should follow those formatting standards:

Contain more than a single musical idea: If a MIDI file contains just a single melody or bass line, for example, there will not be enough information to learn from
Organise instruments and musical parts (melody, chords, bass, etc) across separate MIDI tracks. AIVA looks at individual MIDI tracks to perform the analysis if all the notes of all musical sections/parts are in the same track, the results won't be ideal
MIDI channel 10 should be reserved for percussion only.
Contain a quantized score - performance recording in MIDI will not work well as input since the notes are likely to deviate from a clear metric structure, which may cause problems during the analysis.

The following guidelines are recommended (but not necessary, don’t worry if you don't understand those):

MIDI program change events (for instruments) on each track. Currently, AIVA uses the MIDI program change events to determine the instruments that are playing when analyzing the orchestration. If the instrumentation is unknown or only specified in the track names, you can always set the ensemble type of the influence when uploading the MIDI file, or correct the ensemble type detected automatically after the analysis is complete.
Accu

Question 6

Upload Influence Guidelines

Accepted Answer

How should my audio file be formatted for the best results?

Any recent audio recording, that contains enough musical content should be accepted. Please note, uploading non-musical content will not work.
The uploaded audio file needs to be anywhere between 1 minute - 20 minutes long
The uploaded audio file needs to be in .mp3 or .wav formats

How should my MIDI file be formatted for the best results?

Any orchestrated MIDI file of a composition generated on the music engine is a good example of a format that will work well as an influence.

Your MIDI file should follow those formatting standards:

Contain more than a single musical idea: If a MIDI file contains just a single melody or bass line, for example, there will not be enough information to learn from
Organise instruments and musical parts (melody, chords, bass, etc) across separate MIDI tracks. AIVA looks at individual MIDI tracks to perform the analysis if all the notes of all musical sections/parts are in the same track, the results won't be ideal
MIDI channel 10 should be reserved for percussion only.
Contain a quantized score - performance recording in MIDI will not work well as input since the notes are likely to deviate from a clear metric structure, which may cause problems during the analysis.

The following guidelines are recommended (but not necessary, don’t worry if you don't understand those):

MIDI program change events (for instruments) on each track. Currently, AIVA uses

Frequently Read Articles

Browse All Categories