Bob,

I've been playing around with harmonising audio attached to an SGU file. As a consequence, there are a couple of things that I need to clarify.

1. When TC Helicon is loaded, notice that the label for the window indicates that there is no melody (#1 on below image).

2. The two harmonising options that require melody (#2 on image) are grayed out and are not accessible. This is normal behaviour.

3. Other melody-related options (#3) are also disabled.

4. The ONLY option is to harmonise using the chords. (4 Unison is available for this.)


Quote:
SPECIAL NOTE
In my above post, I outline how to force a BIAB file to be an MGU file. If you do this, and then open TC Helicon the options #1, #2, #3 (image below) will all be available.

HOWEVER, the above options will not work properly because the melody that has been entered is not a proper transcription of the audio melody. So trying to force midi harmony, in this case, will cause errors.

TO USE THE MELODY HARMONY OPTIONS, it is necessary that the notated midi melody is an accurate transcription of the audio melody.


OVERALL SUMMARY
As you can see by all the above posts, I've really put TC Helicon through its paces in BIAB 2017. The only time I received an error was when I tried to generate a second lot of harmony without saving the file after generating the first section of harmony. After saving the file, there was no issue with generating a second section of harmony.

Attached Files (Click to download or enlarge) (Only available when you are logged in)
tc helicon with sgu file.JPG (48.72 KB, 135 downloads)
MY SONGS...
Audiophile BIAB 2025