Originally Posted By: allanmorrow
Am trying to add a ‘pad’ Realtrack to BIAB piece, with intention of rendering it as MIDI file so can eventually use it in DAW. Am only using those Realtracks suggested by the program and that have required ‘n’ in ‘Chart’ column.

At present, some of these pads are fine, whereas others produce weird notation, which translates to equally odd MIDI files with many missing notes and suddenly cut-off chords. The ones that don’t work are those with long notes (which I think of as traditional pad format); those with shorter notes are fine.

I’m wondering if I’m doing something wrong or simply expecting the program to do something it can’t?

Pads that are OK are: 2266, 2267, 2268, 2291, 2305, 2745 and 2746. Those that produce the strange effect described are: 1265, 1278, 1543, 1840, 1841 and 1842. There are further oddities with 2293, which loads with that number but changes to 2291 once rendered, and 2266 which changes to 2265.

Wonder if anyone has thoughts on the matter, and / or can see if they can re-create the problem please? Song tempo – 85BPM and in key of ‘F’.

BIAB version 628, Windows 10.


I'm curious as to why you would even want to convert an RT pad sequence to MIDI in the first place when converting RT to MIDI gives iffy results and you have much, much, better options available-that are already in MIDI-through the MIDI supertracks or by selecting a regular MIDI track patch and picking a preset... This will be accurate note-for-note as they are already MIDI to begin with.

Am I missing something here?

DB09

Band-in-a-Box 2024. Custom Build Desktop PC W/ Windows 10 Home 64-bit. CPU: Intel Core i5-9600k @ 3.7GHz (6 core x 6 threads) RAM: 16GB DDR4. Storage 238GB SSD + 2.7 TB HDD. GPU: ZOTAC NVIDIA GeForce GTX 1050 Ti 4GB