I upgraded from v2019 to v2022 yesterday and just a few minutes ago installed the Build 914 update. I was hoping this update might take care of the problem I'm having, but no joy.
First off, let me state that I was NOT having this problem with v2019. It didn't appear until just a short while ago when I loaded an existing tune and tried to change an instrument. Specifically, in the bass track, "Finger Slap Bass" was selected and I wanted to change this to "Slap Bass 1". When I did so, the bass channel's instrument remained unchanged BUT the melody channel's instrument was switched to Slap Bass. WTF. I tried again just to make sure I hadn't made a fumble-fingered mistake, but nope. Just now, to see if this sort of thing was occurring with any other channels, I tried the Piano channel, and changed its instrument -- or tried to. Sure enough, the instrument didn't change, but the melody's instrument did. Next, I tried changing the melody instrument. Well, at least this channel works as intended. But apparently, none of the others do.
Just in case it should matter, although I don't see why it should, I have Cakewalk's TTS-1 indicated as the default synth.
I went to Options>Preferences and looked around in the MIDI File, MIDI Options, and Overrides tabs, but the settings there -- which I'm assuming are 2022's default settings? -- all looked reasonable. At least nothing jumped out at me as being obviously wrong.
So, anyway, I'm hoping one of you can point out what BiaB is doing wrong here. It ain't me, because I haven't changed a thing. This is all BiaB.
Wish I could help you Michael, God knows I have tried to figure this all out since I use a lot of midi. In the past I have opted to take the midi out of BIAB as quickly as possible and figure it all out in my DAW, which has worked well for me. But I would like to do more in BIAB with Midi. However, my conclusion at this time is that this is a bad time to try to figure out the midi routing and patch assignments in BIAB due to the recent update. I have just seen the strangest stuff, similar to what you are reporting here. All I can offer is, keep reporting and things will get fixed or someone will come along who knows a lot more about this then you and I.
Mario, I've tried it on two songs so far, and it's doing the exact same thing with both of them. No, the tracks aren't frozen. They're MIDI. What's the point?
If you could duplicate this, it would be most helpful. Oh, one more thing I didn't mention earlier -- both tunes I tried this out on are MIDI only. No Real Tracks, just in case that might matter for some reason.
Dan, like you, I export my BiaB files to my DAW (Cakewalk), where I do most of my production and edits, including final instrument assignments. But still, when working in BiaB, I like to have things sound as close as I can to the way I'm picturing it. I don't know about the rest of the folks here, but when I select a style, to me that's just a starting point. I will almost always change instrument assignments as I develop a song. It would be extremely limiting to be stuck with a style's default instrumentation.
At this point, I'm convinced this is BiaB problem, since, as I mentioned above, I haven't changed a thing. Prior to the upgrade, I could change instruments either on the fly or with the song idle, didn't matter. Hopefully, the staff will find a workaround to this and will include a fix in an upcoming Build.
I got some unexpected available time so I ran some experiments. Here is what I found:
1- using both versions 912 and 914 I changed instruments and the change worked as expected. BUT I reread you message and found out that you had a melody track whereas I didn't in these experiments.
2 - using only version 914 I changed instruments but they did not change! They stayed the same sound even though the track IDs changed. The melody track was not affected like in your case.
Note I mostly work in MIDI and all of these experiments were MIDI only with no frozen tracks. Also I tried the above on 3 or 4 different existing songs and the results were always as stated above.
The conclusion is there is a bug in 2022 BiaB version 914 and maybe other versions. You may want to report this to PGmusic and reference this thread.
Like Dan I get out of BiaB as fast as I can. I do all of my instrument changes in my DAW, Studio One Pro 5.
(edit) would others please try this and report what you see. Thanx!
Last edited by MarioD; 01/02/2209:26 AM.
OK, a random thought; Why does toilet paper need a commercial? Who's not buying it?
64 bit Win 10 Pro, the latest BiaB/RB, Roland Octa-Capture audio interface, a ton of software/hardware
I love that Mario used the same wording as I did: "..as fast as I can" . We both appreciate the sense of urgency for taking the midi into our DAW to process further. There is definately a lesson to be learned by our common experience.
as already reported in several other threads, I also still have that Midi patch problem - on the Soloist track, on the Utility Tracks and sometimes also on the Melody Track. It's definately a bug (since BiaB 2022, no matter which patch) - and unfortunately there has not been much reaction from PG to this, so far.
Since I use BiaB as a Playalong Tool and not for creating backing tracks or other kinds of music production, leaving BiaB as fast as I can is no solution for me :-)
Since the beginning of December, I'm quite patient on this, but a "We're working on it" from PG would really be appreciated by now.
Last edited by MoveToGroove; 01/02/2210:31 AM.
BiaB UltraPak+ 2026; Windows 10 Bass: Intermediate; Piano: Beginner I came to this forum in order to suggest feature improvements for non-professional musicians like myself that use BiaB mainly as a playalong tool and as a learning tool
I wanted to throw this out there as it may explain some of the things being reported.
I don't know this for a fact, but I believe some of the PG "demos" in recent years have essentially hard-coded the arrangments in such a manner that you can't adjust them fully. I think we have seen this with multistyles and/or multidrum demos. So while some of the demos are good starting points for our own arrangments, it could be that others are not so flexible. This is just fodder for thought until someone who knows better comes along.
Dan, it doesn't happen only with the Demo Songs, and it worked fine in BiaB 2020 (I skipped BiaB 2021, but I think others have reported that also it still worked fine in BiaB 2021).
Last edited by MoveToGroove; 01/02/2210:53 AM.
BiaB UltraPak+ 2026; Windows 10 Bass: Intermediate; Piano: Beginner I came to this forum in order to suggest feature improvements for non-professional musicians like myself that use BiaB mainly as a playalong tool and as a learning tool
Dan, interesting your observation, but in my case, no demos, or portions thereof, were used.
I haven't read up on any of these past experiences with MIDI tracks being locked -- or situations to that effect -- but it sure seems high time to me that PGM should have addressed this.
I tried the Piano channel, and changed its instrument -- or tried to. Sure enough, the instrument didn't change, but the melody's instrument did.
I can't seem to duplicate this problem. Does this happen with the ZZJAZZ demo song? -If so, can you tell us the specific steps you are using to change the patch? -If not, what style/song does it happen with?
I've had this happen to me before (and reported it, just to be told, by PGMusic support, that it was by design)...
When I right click on the description of a track that I want to change, instead of right clicking on the track name... The focus of the track doesn't shift.
However, the right click menu does come up, on the track that you right clicked on, and it makes you think that you are changing instruments on that track. But you are really modifying the track previously highlighted (because to focus didn't change when you right clicked on the track that you thought you were modifying.
Apparently this is "By Design"... See attached screen shots...
I attach a video with a little "medley" of my midi problems:
Example 1, after File - Open: Melody should be Vibraphone, but plays Piano. Example 2, after loading Demo Song Soloist should be Guitar, but plays Piano (some other times horn) Example 3, after Drag&Drop a midi: Imported tracks all play Piano
Last edited by MoveToGroove; 01/06/2206:39 AM.
BiaB UltraPak+ 2026; Windows 10 Bass: Intermediate; Piano: Beginner I came to this forum in order to suggest feature improvements for non-professional musicians like myself that use BiaB mainly as a playalong tool and as a learning tool
MoveToGroove,I did exactly the same manipulations as you and everything worked. So I can't help, just understand that you're disappointed, at the very least. I will rather think of a bad config. You must have already returned to the basic parameters, so that's not it. Really weird. Good luck! What is your Vsti/Dxi by default?
I attach a video with a little "medley" of my midi problems:
Example 1, after File - Open: Melody should be Vibraphone, but plays Piano. Example 2, after loading Demo Song Soloist should be Guitar, but plays Piano (some other times horn) Example 3, after Drag&Drop a midi: Imported tracks all play Piano
These are quite often due to embedded patch changes imported with MIDI. You could try step-editing the MIDI and deleting any you find.
I believe I've had cases in past versions where it isn't embedded CCs, though.
Last edited by Gordon Scott; 01/06/2207:44 AM.
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 .
thanks for feeling with me, it's really annoying, since more than half of what I'd like to use BiaB for doesn't work. My Settings are as follows:
BiaB UltraPak+ 2026; Windows 10 Bass: Intermediate; Piano: Beginner I came to this forum in order to suggest feature improvements for non-professional musicians like myself that use BiaB mainly as a playalong tool and as a learning tool
this happens with many demo songs and with literally all my midis (no matter if created earlier in BiaB by myself or bought from whichever Midi Shop), and I didn't have any problems with midi patches before I installed BiaB 2022, and there are also other users that have these problems.
Last edited by MoveToGroove; 01/06/2208:24 AM.
BiaB UltraPak+ 2026; Windows 10 Bass: Intermediate; Piano: Beginner I came to this forum in order to suggest feature improvements for non-professional musicians like myself that use BiaB mainly as a playalong tool and as a learning tool
My advice would be to go back to your old version (which worked) by monitoring the forums for a possible fix. A very sad solution, but which would undoubtedly allow you to take advantage of the software? Because you could enjoy 100% of the old version? They will necessarily release a fix since there is a referenced midi problem.
yes, I have already installed my old version on a second computer. However, I hope that the issue will be fixed soon by PG, since I'd like to use the new features as well, for sure.
BiaB UltraPak+ 2026; Windows 10 Bass: Intermediate; Piano: Beginner I came to this forum in order to suggest feature improvements for non-professional musicians like myself that use BiaB mainly as a playalong tool and as a learning tool
i got exactly same problem.reported to support early december but getting nothing back except the usual ...return to factory settings run as admin delete the Mysetup.dk intrface.bbw files, roll back to previous year that it worked(making my latest purchase of bb pointless (haha)
i have given up on this problem now and have to rechannel all midi which goes on to utility tracks everytime. im exhausted the amount of times i have re booted and rolled back and tried all combinations of drivers for something that definatley worked on the 2021 version.
i dont mess around with settings on installs, i just let everythin default so everything should be as last year.
anyway, my heads in the cuckoo nest now and im done.
rebuilt styles,songs and real tracks. win 10...amd a10 radeon r6 4c+6g 1.8ghz 64 bit hp envy biab 2023 with 1004 build. styles 1 to 429 plus extras 1,2,3,4 and 6. running as admin,cleaned up returned to factory settings.
XPro & Xtra Styles PAK Sets On Sale Now - Until May 15, 2026!
All of our XPro Styles PAKs and Xtra Styles PAKs are on sale until May 15th, 2026!
It's the perfect time to expand your Band-in-a-Box® style library with XPro and Xtra Styles PAKs. These additional styles for Band-in-a-Box® offer a wide range of genres designed to fit seamlessly into your projects. Each style is professionally arranged and mixed, helping enhance your songs while saving you time.
What are XPro Styles and Xtra Styles PAKs?
XPro Styles PAKs are styles that work with any version (Pro, MegaPAK, UltraPAK, UltraPAK+, or Audiophile Edition) of Band-in-a-Box® 2025 (or higher). XPro Styles PAKS 1-10 includes 1,000 styles!
Xtra Styles PAKs are styles that work with the UltraPAK, UltraPAK+, or Audiophile Edition of Band-in-a-Box® 2025 (or higher). Xtra Styles PAKs 1-21 includes 3,700 styles (and 35 MIDI styles)!
The XPro & Xtra Styles PAKs are not included in any Band-in-a-Box® package.
The XPro Styles PAKs 1-10 are available for only $29 ea (reg. $49 ea), or get them all in the XPro Styles PAK Bundle for only $149 (reg. $299)! Listen to demos and order now! For Mac or for Windows.
The Xtra Styles PAKs 1-21 are available for only $29 ea (reg. $49 ea), or get them all in the Xtra Styles PAK Bundle for only $199 (reg. $349)! Listen to demos and order now! For Mac or for Windows.
Note: XPro Styles PAKs require Band-in-a-Box® 2025 or higher and are compatible with ANY package, including the Pro, MegaPAK, UltraPAK, UltraPAK+, and Audiophile Edition.
The Xtra Styles require the UltraPAK, UltraPAK+, or Audiophile Edition of Band-in-a-Box®. (Xtra Styles PAK 19 requires the 2025 or higher UltraPAK, UltraPAK+, or Audiophile Edition. They will not work with the Pro or MegaPAK version as they require the RealTracks included in the UltraPAK, UltraPAK+, or Audiophile Edition.
Supercharge your Band-in-a-Box today with XPro Styles PAKs and Xtra Styles PAK Sets!
With the release of Band-in-a-Box® 2026 for Mac, we’re rolling out a collection of brand-new videos on our YouTube channel. We’ll keep this forum post updated so you can easily find all the latest videos in one convenient spot.
Whether you're exploring new features, checking out the latest RealTracks or Style PAKs, this is your go-to guide for Band-in-a-Box® 2026.
Band-in-a-Box® 2026 for Mac is here and it is packed with major new features! There’s a new modern look, a GUI redesign to all areas of the program including toolbars, windows, workflow and more. There’s a Multi-view layout for organizing multiple windows. A standout addition is the powerful AI-Notes feature, which uses AI neural-net technology to transcribe polyphonic audio into MIDI—entire mixes or individual instruments—making it easy to study, view, and play parts from any song. And that’s just the beginning—there are over 100 new features in this exciting release.
Along with version 2026, we've released an incredible lineup of new content! There's 202 new RealTracks, brand-new RealStyles, MIDI SuperTracks, Instrumental Studies, “Songs with Vocals” Artist Performance Sets, Playable RealTracks Set 5, two new RealDrums Stems sets, XPro Styles PAK 10, Xtra Styles PAK 21, and much more!
Special Offers
Upgrade to Band-in-a-Box® 2026 for Mac and save up to 50% on most upgrade packages during our special offer—available until May 15, 2026. Visit our Band-in-a-Box® packages page to explore all available upgrade options.
2026 Free Bonus PAK & 49-PAK Add-ons
Our Free Bonus PAK and 49-PAK are loaded with amazing add-ons! The Free Bonus PAK is included with most Band-in-a-Box® 2026 for Mac packages, but you can unlock even more—including 20 unreleased RealTracks—by upgrading to the 2026 49-PAK for just $49.
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.
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.
. We both appreciate the sense of urgency for taking the midi into our DAW to process further. There is definately a lesson to be learned by our common experience. 
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean