Originally Posted By: rayc
I watched the earlier video, I'm no fool - I know there're things H.C. can offer, and learnt about the midi splitting thing which seems to be one of the aspects that was a problem, if I recall correctly. I was pleased to learn that piece of info even if it may be only temporarily useful.


I agree. It's a bit surprising there's been no questions to why two instances of the midi file were used in the project. It's due to how BIAB addresses differently opening a midi file to how BIAB addresses importing a midi file.

Opening a midi file automatically loads all the midi file channels onto the Melody Track and assigns sequencer. Opening a midi file also automatically analyzes the chords and populates the Chord Chart. Opening populates the title, disables the BIAB current style, sets the start/end bars, sets the key signature and tempo.

Importing a midi file separates the midi channels and loads each of the song's channels onto individual utility Tracks. Importing a midi does not do any of the tasks that the Opening process does. So in the tutorial technique demonstrated in this video, a midi file must be opened first and then imported to work because only importing offers the option to select whether to import into the current project or start a new project.

BIAB 2025:RB 2025, Latest builds: Dell Optiplex 7040 Desktop; Windows-10-64 bit, Intel Core i7-6700 3.4GHz CPU and 16 GB Ram Memory.