I frequently have a problem with synchronising BiaB to song generated from a midi file that want to use for backing. My creation process to Open Special and load the midi file. BiaB quite nicely generates the song chords. Since the entire song is still in midi and stored in the sequencer, I was expecting BiaB to be in step with the midi song when it was played, and it usually is if the song is in 4/4. But when I have other time signatures, I often experience this midi ‘out of sync’ with the chord sheet. When I go to the next stage of separating the tracks out I can sometimes compensate by adjusting the number of bars before starting to play but sometimes not. Any help please!
BiaB has a default option of either 3 or 4 beats per cell. That's why 4/4 works as a default.
I haven't tried this, but it's probably the first thing I'd try.
If the song I was importing was in 5/4, I'd set the BiaB sheet for 3 beats on the first bar, 2 on the second, 3 on the third, 2 on the fourth and so on.
I find, not thinking about each numbered cell as a bar or measure of music, allows you to do many things BiaB wasn't originally built to do. This especially best if you are using MIDI styles, because MIDI is just thousands of times more editable than pre-recorded audio.
Hi Jim, that doesn't work. The time signature and tempo is set to what is in the values in the midi file itself. This is why I thought BiaB would automatically be in sync. You can change the time signature aftger loading but thatdoesn't help. Why would they be out of sync?
Thank you for the suggestion, but I'm not really clear on how that helps me? Sometimes a 3/4 midi is in sync and others are not. Also, the beats per bar is a bar setting so evvery bar would need to be set individually.
I don't think this is how BIAB works. Yes. BIAB will capture the chords. And it will caputure the midi content of each track within a midi file. But when it plays BIAB creates new content in accordance with the STYLE. It does not "play along" with a midi file from an external source. So you will not be able to "synch" the BIAB generated RTs and/or Midi tracks with the Midi File tracks. And if there is some "workaround" to make it all synch (which I assume there is by freezing utility tracks) it will sound like crap.
Another thing to consider is that the MIDI file may not necessarily have been created to align to beats and bars, time signatures an tempos. This can happen, for example, when live recording the different parts without a click track (think just turning on record and start playing the parts). I also have some older MIDIs where the originator runs the file through an app that randomizes the beats and bars to intentionally not align, but still sound properly when played back (a sort of copy protection mechanism).
John
Laptop-HP Omen I7 Win11Pro 32GB 12TB SSD Desktop-ASUS-I7 Win10Pro 32GB 12TB SATA
Ma\ybe a long shot but open the original mdi file in RealBand and see if that works when you want to edit and adjust volmes.. You can still generate RTs, new midi tracks and record.then export the project to whatever you use for backing tracks or jsut play i in RB.
Bob’s suggestion of RealBand is better odds than a long shot, because it supports non-integer tempos. If it’s a free-form tempo like John suggested it could be, I really don’t know what to do.
This has nothing to do with tempos or time signatures, but there’s a small point from Dan that I’m going to be picky about because it’s often misrepresented. I know he knows this: BIAB does not ‘capture’ the chords from an imported MIDI file. The MIDI standard doesn’t include chords (even the new MIDI 2.0) so there is nothing to capture. Instead, BIAB interprets what the chords are from reading the notes. It does a pretty good job of this in my experience, until you get into complex jazz chords with slash roots where even human transcribers could have arguments about the choice of chord. This omission in MIDI is one reason that transferring a song as Music XML often works better. It has the actual chord spelling (and includes text elements too). And the time signatures and tempo are clearly given throughout, assuming they were set in the original source.
BIAB 2025 Win Audiophile. Software: Studio One 7 Pro, Swam horns, Acoustica-7, Notion 6, Song Master Pro, Win 11 Home. Hardware: Intel i9, 32 Gb; Presonus 192 & Faderport 8, Royer 121, Slate VSX, Adam Sub8 & Neumann 120 monitors.
You've hit on the problem that I have with BiaB and that is the underlying way it works. The manual does not, or doesn't seem to, go into what's going on underneath the interface. In this particular case I see a midi file being interpreted by BiaB to detect the chords. The tempo and the key signature in the midi should be able to select an appropriate style to at least to start with and, when the song plays, the movement along the bars would be in time with the midi file. After all, that is all that is playing at this time. If you could explain to me what is happening in BiaB that sometimes, not always, this lock step with tempo is not the same. That way I could sort this out for myself.
I don’t know that we users can even make an attempt to explain what’s under the BIAB hood. It’s proprietary software and that’s unlikely to be something we would ever know. The best we can hope for is to get the attention of a PG Music staffer who could give you a step-by-step solution, if such exists.
BIAB 2025 Win Audiophile. Software: Studio One 7 Pro, Swam horns, Acoustica-7, Notion 6, Song Master Pro, Win 11 Home. Hardware: Intel i9, 32 Gb; Presonus 192 & Faderport 8, Royer 121, Slate VSX, Adam Sub8 & Neumann 120 monitors.
Well, I think the response with helpful suggestions has been great. I think, after all the time I have spent on this issue, that John Ford is probably on the right track. I will certainly look at all the suggestions that have been made. I have attached a zipped file containing some songs that work as I had expected and some that don’t. Those that do work are prepended with ‘!y’ and those that don’t are prepended with ‘!x’. I have done nothing more than Open Special > Open Midi File. There does not appear to be any settings that can alter the alignment. I would be really interested if anybody could have a look at the files and let me know their opinion. If this is a copyright issue then I apologise to the holder; I have no intention of using these files, I’ve had them for years and just searched through for examples of what I meant.
I start projects daily normally beginning with midi files for a variety of reasons and benefits and I don't recall having any synch problems off hand. Many are live midi recordings made without a click track. There have been corrupt and bad midi files over time but that's another topic and doesn't seem to be the problem. I'm anxious to review the files you've posted and appreciate you taking the time to do so.
There are several ways to get a midi file into BIAB and midi, as well as audio files, can be either opened or imported into a BIAB project with different characteristics between the two methods. The user's desired intent for the file data is the deciding factor to which method to use. I plan to look at these different methods I've mentioned and spend some time testing the files.
Just a thought ... MIDI has tempo and time-signature, but I think it may not have a indication of beat-1, so if there's an anacrusis, could that be causing the misalignment?
Jazz relative beginner, starting at a much older age than was helpful. AVL:MXE Linux; Windows 11 BIAB2026 Audiophile, a bunch of other software. Kawai MP6, Ui24R, Focusrite Saffire Pro40 and Scarletts .
Another thing to consider is that the MIDI file may not necessarily have been created to align to beats and bars, time signatures an tempos. This can happen, for example, when live recording the different parts without a click track (think just turning on record and start playing the parts).
This seems to be the case - of the files Jonel posted that I checked, the ones that didn't work were all misaligned or free tempo. This is fine if you're simply playing the MIDI, but when importing it into BB or any DAW you need to manually align things.
Originally Posted by jonel
If you could explain to me what is happening in BiaB that sometimes, not always, this lock step with tempo is not the same. That way I could sort this out for myself.
Sometimes MIDI files don't have correct tempo information or time signature, or an undefined key signature. To see what information is embedded in a MIDI file, you can use an app such as MIDIYodi to inspect them. Also I've personally come across many MIDI files that are defined at 120bpm which is the "default" tempo in most DAWs, yet the actual song is a completely different tempo - any DAW, including BIAB, would have no idea whether the notes are intentionally out of time or not, therefore they'd need manual correction.
There are a couple functions in BIAB that can help with this:
If the MIDI is off by exactly a bar or multiples of bars, then "importing" the MIDI instead of "opening" the MIDI can help - importing brings up a window that will let you offset any number of bars, or add blank bars to the beginning. See the screenshot below:
If the MIDI is off by any amount that is not exactly a number of bars, then you can shift the MIDI track by a specified number of beats or ticks using the options in this menu:
<< "This seems to be the case - of the files Jonel posted that I checked, the ones that didn't work were all misaligned or free tempo. This is fine if you're simply playing the MIDI, but when importing it into BB or any DAW you need to manually align things." >>
Same here. Another possible solution is to create a tempo map using the ACW. BIAB has a feature on the Master Track in the Mixer to create a mix and open it on the Audio Channel.
Opening the ACW then has the audio wave file automatically loaded and ready to create the tempo. Normally, the chords have also been analyzed, the key set, the Style muted etc. The midi file opens imported onto the Melodist Channel. I use the normal open command (F3) for this.
The Audio File can be muted or erased once the tempo map has been created.
Sometimes MIDI files don't have correct tempo information or time signature, or an undefined key signature. To see what information is embedded in a MIDI file, you can use an app such as MIDIYodi to inspect them. Also I've personally come across many MIDI files that are defined at 120bpm which is the "default" tempo in most DAWs, yet the actual song is a completely different tempo - any DAW, including BIAB, would have no idea whether the notes are intentionally out of time or not, therefore they'd need manual correction.
FWIW, 120bpm is also he default for MIDI.
Thinking about this, if I record an SMF file on either of my keyboards, I will most likely not set up any of that stuff. Usually I'm not using tempo, key signature or time signature, I'm just recording the notes I play. I'm not sure that a key signature is even present on either ... I've cartainly never used it.
One would like to think that full MIDI songs have them set suitably, but AFAICS, nothing I record will ... yet anyway.
Jazz relative beginner, starting at a much older age than was helpful. AVL:MXE Linux; Windows 11 BIAB2026 Audiophile, a bunch of other software. Kawai MP6, Ui24R, Focusrite Saffire Pro40 and Scarletts .
I think the replies to my orginal post have been outstanding and have shone a liight on both Midi as well as its its use in BiaB. Since I posted the initial issue I have also been examining the files and I can see some the problems now. The tempo map mentioned by Charlie was of particuar interst with regards to 'Abide With Me' which is clearly a live performance suited to the occasions when it would be performed.
I thank everbody very much for bringing a lot of light to this partiular topic for me. It has helped me a lot.
<< "This seems to be the case - of the files Jonel posted that I checked, the ones that didn't work were all misaligned or free tempo. This is fine if you're simply playing the MIDI, but when importing it into BB or any DAW you need to manually align things." >>
Same here. Another possible solution is to create a tempo map using the ACW. BIAB has a feature on the Master Track in the Mixer to create a mix and open it on the Audio Channel.
Opening the ACW then has the audio wave file automatically loaded and ready to create the tempo. Normally, the chords have also been analyzed, the key set, the Style muted etc. The midi file opens imported onto the Melodist Channel. I use the normal open command (F3) for this.
The Audio File can be muted or erased once the tempo map has been created.
Charlie, according to your pics you have turned off the Style! That eliminates BIAB from actually "play along" with the OPs midi. I think it is admirable that so many users have weighed in on this matter to help the OP, but I stand by my original comments.
The photos were a mock up to show menu locations made after I had tested. I decided to post my findings later after I had discarded the original file.
You're correct. The same as with the Stem Splitter, the imported material has to be synced with BIAB. When I open a file and use the Master render function and play it along with the imported midi file on the Melody Track, they are synced. BIAB disables the Style.
Creating a tempo map of that audio follows the same process the Stem Splitter syncs the separated tracks to BIAB.
I've opened two random midi files from my PC and then LX version of Jonel's "Old Rugged Cross" and the audio render and Melody Track Midi sync for each one.
I persevered and finally got the midi to work with a BiaB style.
The problem I initially had was when I opened a midi file (using special), I was able to frame the chordshhet with part markers and all worked OK. This was expected of course because the midi was stored in the sequencer. I wanted to split the tracks out from the sequencer so that I could eventually bring in a BiaB style. I had watched Henry Clarke do this by simply dragging the intitial midi file back on to BiaB and this was meant to automatically split the tracks over to the Untility tracks. It did do this but I discovered it was all out of sync with the original midi in the sequencer. I viewed the Utility tracks in the Tracks view and it was clear that tracks were not in the same position as the orginal.in the Melody track After a lot of messing about I tried doing the job manually using the Track Copy/Move feature. A bit laborious but it worked.
I don't know if there is a bettter way to do it. It did work OK for Henry though
It would seem that there is some inconstancy in the way BB treats midi when using the Open Special > Open Midi File and how BB deals with drooping the same midi file onto BB. It looks like Henry Clarke may have been lucky in his choice of midi file (or I was unlucky in my choice). Anyway, this is how I manage to get it work for me for a range of midi files.
I opened BB for a new song as per the manual and BB detected the chords and populated the chord sheet accordingly. At this point I checked/corrected the chords and part markers. I then switched to Track view to confirm that the multi-track midi was stored on the melody track. I set the cursor to mark the position of the first bar of the midi song.
Now it was time to drop the same midi file onto BB. I first used a midi file that had been problematic in syncing. When I dropped the midi file onto BB and accepted the defaults for importing into the song, I could see the Utility tracks being populated by the Melody midi tracks, as expected. But what I noticed was that the individual tracks started exactly one bar after the Melody midi had started. This was the problem I should have noticed before. So, I repeated drop operation and modified the ‘number of bars to insert’ parameter, in this case it required -1. When I did this then everything worked as expected. I tried this with other midi files and found the sometimes I needed -1 or 0 or +1 (so far).
The Open Special command doesn’t provide for any offset so something is going on there I think with regard to synchronising how the midi is interpreted. But I’m overjoyed that I can get this to work every time.
It would seem that there is some inconstancy in the way BB treats midi when using the Open Special > Open Midi File and how BB deals with drooping the same midi file onto BB.
There are several ways to open/import MIDI and there definitely are differences. Some of those differences depend upon how you reached the open/import stage. Those differences may also depend upon the MIDI file type.
The first two are the ones Henry uses, I believe.
File->Open Special->Open MIDI File Appears to import all MIDI data onto the Melody track, but analyses and inserts what it believes are suitable chord symbols.
Drag & Drop MIDI Separates out the MIDI channels and puts them into individual utility tracks in BiaB. Chords not analysed.
There are also the following with preset default actions.
File->Import->Import Melody from MIFI File Opens the track filter and defaults all tracks to BiaB's Melody track. The destinations can be changed. Chords not analysed.
File->Import->Import to soloist part from MIDI file Opens the track filter and defaults all tracks to BiaB's Soloist track. The destinations can be changed. Chords not analysed.
Melody->Edit Melody Track->Import Melody from MIDI file Same as File->Import
Soloist->Edit Melody Track->Import to Soloist from MIDI file Same as File->Import
There is also a selection of File->Import->Import chods from... options, the third of which seems to do much the same as the File->Open Special->Open MIDI File, also importing all of the tracks into Melody.
Most of those appear to me to make odd assumptions about which MIDI channel should go where and what patches to use. Probably there's some logic, but I lost patience.
I think Henry uses the File->Open special to analyse the chords, but then ignores the aggregated melody track. He then uses drag & drop as the easiest way to get the tracks separated out into a series of utility tracks where thay can be individually managed.
All those variations realy just show how features have been added with only modest regard for regularity and consistency.
Jazz relative beginner, starting at a much older age than was helpful. AVL:MXE Linux; Windows 11 BIAB2026 Audiophile, a bunch of other software. Kawai MP6, Ui24R, Focusrite Saffire Pro40 and Scarletts .
Importing with the midi would have been the method to use if it had performed chord analysis. This provided the ability to make the midi sync with the BB chord movement but does not provide chord analysis. Dropping the midi onto BB provides track separation but no chord analysis but gived no provision sync to BB. So the combination of Open Open Special > Open Midi followed by dropping the midi file onto BB is really the only option in my case. But, as I already said, this sometomes gets the Melody track midi out of kilter with the tracks the have bee split out to the Utility tracks.
Henry Clarke could overcome this by simply ignoring the Melody track by muting it, but this has drawback. For a start it would mean the BB chord cursor would be out of sync with the utility clips and perhaps with the new RealTrack generation. The problem really is BBs way of generating the sets of midi. They should be be the same because both are sourced from the same file.
As I think you said, maybe the MIDI files themselves also affect this. I did try with only a couple of files.
Jazz relative beginner, starting at a much older age than was helpful. AVL:MXE Linux; Windows 11 BIAB2026 Audiophile, a bunch of other software. Kawai MP6, Ui24R, Focusrite Saffire Pro40 and Scarletts .
The midi file might have an effect but, in this case, both features are working on exactly the same midi file. The Open Special does not allow for any parameter input from the user so you get what you are given. The subsequent dropping of the midi file onto BB does ask for offset parameters. The second feature with an offset of 0 should be provide the same alignment as the first. Fortunately it's easy to spot in the Tracks view and correct using further drops with an offset +/- dependending on the direction of misalignment. This is definitley a BB issue.
Instead of using the Open Command, try Import Chords Command. This allows access to chord analysis, tempo, the number of bars, and key signature synced with the BIAB Style which defaults to disabled and must be enabled.
Use File->Import->Import chords from Midi File (Midi Chord Wizard )
I opened three of Jonel's LX files from his zip folder: "Abide in me"; "old rugged cross", and "take my hand" as well as three midi files from my hard drive.
All six files synced and played correctly between the midi file and BIAB Style.
<< Most of those appear to me to make odd assumptions about which MIDI channel should go where and what patches to use. Probably there's some logic, but I lost patience. >>
Gordon is correct here. In this instance the user might have to manually set a channel because the midi composer may not use generally accepted channel designations such as Melody on Channel 4, Bass on Channel 2, Piano on Channel 3 or Drums on Channel 10 and so forth.
There are two options, let Import Chords automatically set the channels and place the melody channel. (Default)
or
Import the chords and place all of the midi file channels on the Melody Track.
If the midi file is imported onto the Melody Track and the user doesn't know the instrument placement channels, open the Sequencer to display all of the midi channels and numbers. Then the user can manually set the correct channels and import again to overwrite the current settings.
The Sequencer is an option to easily determine the channels and set these channels to match the midi file.
Band-in-a-Box® 2025 for Mac® users: Build 904 now available!
If you're already using Band-in-a-Box® 2025 for Mac®, make sure to grab the latest update! Build 904 is now available for download and includes the newest additions and enhancements from our team.
PowerTracks 2026 is here—bringing powerful new enhancements designed to make your production workflow faster, smoother, and more intuitive than ever.
The enhanced Mixer now shows Track Type and Instrument icons for instant track recognition, while a new grid option simplifies editing views. Non-floating windows adopt a modern title bar style, replacing the legacy blue bar.
The Master Volume is now applied at the end of the audio chain for consistent levels and full-signal master effects.
Tablature now includes a “Save bends when saving XML” option for improved compatibility with PG Music tools. Plus, you can instantly match all track heights with a simple Ctrl-release after resizing, and Add2 chords from MGU/SGU files are now fully supported... and more!
Get started today—first-time packages start at just $49.
Already using PowerTracks Pro Audio? Upgrade for as little as $29 and enjoy the latest improvements!
Band-in-a-Box 2026 for Windows Special Offers End Tomorrow (January 15th, 2026) at 11:59 PM PST!
Time really is running out! Save up to 50% on Band-in-a-Box® 2026 for Windows® upgrades and receive a FREE Bonus PAK—only when you order by 11:59 PM PST on Thursday, January 15, 2026!
We've added many major new features and new content in a redesigned Band-in-a-Box® 2026 for Windows®!
Version 2026 introduces a modernized GUI redesign across the program, with updated toolbars, refreshed windows, smoother workflows, and a new Dark Mode option. There’s also a new side toolbar for quicker access to commonly used windows, and the new Multi-View feature lets you arrange multiple windows as layered panels without overlap, making it easier to customize your workspace.
Another exciting new addition is the new AI-Notes feature, which can transcribe polyphonic audio into MIDI. You can view the results in notation or play them back as MIDI, and choose whether to process an entire track or focus on specific parts like drums, bass, guitars/piano, or vocals. There's over 100 new features in Band-in-a-Box® 2026 for Windows®.
There's an amazing collection of new content too, including 202 RealTracks, new RealStyles, MIDI SuperTracks, Instrumental Studies, “Songs with Vocals” Artist Performance Sets, Playable RealTracks Set 5, two RealDrums Stems sets, XPro Styles PAK 10, Xtra Styles PAK 21, and much more!
Upgrade your Band-in-a-Box for Windows to save up to 50% on most Band-in-a-Box® 2026 upgrade packages!
Plus, when you order your Band-in-a-Box® 2026 upgrade during our special, you'll receive a Free Bonus PAK of exciting new add-ons.
If you need any help deciding which package is the best option for you, just let us know. We are here to help!
Band-in-a-Box® 2026 for Windows® Special Offers Extended Until January 15, 2026!
Good news! You still have time to upgrade to the latest version of Band-in-a-Box® for Windows® and save. Our Band-in-a-Box® 2026 for Windows® special now runs through January 15, 2025!
We've packed Band-in-a-Box® 2026 with major new features, enhancements, and an incredible lineup of new content! The program now sports a sleek, modern GUI redesign across the entire interface, including updated toolbars, refreshed windows, smoother workflows, a new dark mode option, and more. The brand-new side toolbar provides quicker access to key windows, while the new Multi-View feature lets you arrange multiple windows as layered panels without overlap, creating a flexible, clutter-free workspace. We have an amazing new “AI-Notes” feature. This transcribes polyphonic audio into MIDI so you can view it in notation or play it back as MIDI. You can process an entire track (all pitched instruments and drums) or focus on individual parts like drums, bass, guitars/piano, or vocals. There's an amazing collection of new content too, including 202 RealTracks, new RealStyles, MIDI SuperTracks, Instrumental Studies, “Songs with Vocals” Artist Performance Sets, Playable RealTracks Set 5, two RealDrums Stems sets, XPro Styles PAK 10, Xtra Styles PAK 21, and much more!
There are over 100 new features in Band-in-a-Box® 2026 for Windows®.
When you order purchase Band-in-a-Box® 2026 before 11:59 PM PST on January 15th, you'll also receive a Free Bonus PAK packed with exciting new add-ons.
Upgrade to Band-in-a-Box® 2026 for Windows® today! Check out the Band-in-a-Box® packages page for all the purchase options available.
One of our representatives will be happy to help you over the phone. Our hours of operation are from
6:00AM to 6:00PM PST (GMT -8) Monday thru Friday, and 8:00AM to 4:00PM PST Saturday. We are closed Sunday. You can also send us your questions via email.
One of our representatives will be happy to help you on our Live Chat or by email. Our hours of operation are from
6:00AM to 6:00PM PST (GMT -8) Monday thru Friday; 8:00AM to 4:00PM PST (GMT -8) Saturday; Closed Sunday.
Norton Music
Yes. BIAB will capture the chords. And it will caputure the midi content of each track within a midi file. But when it plays BIAB creates new content in accordance with the STYLE. It does not "play along" with a midi file from an external source. So you will not be able to "synch" the BIAB generated RTs and/or Midi tracks with the Midi File tracks. And if there is some "workaround" to make it all synch (which I assume there is by freezing utility tracks) it will sound like crap. 
![[Linked Image - Only viewable when logged in]](https://www.pgmusic.com/forums/ubbthreads.php?ubb=download&Number=31387&filename=import midi.png)
![[Linked Image - Only viewable when logged in]](https://www.pgmusic.com/forums/ubbthreads.php?ubb=download&Number=31388&filename=edit melody.png)
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean