I wonder if anyone can advise if I'm doing something wrong. I want to select a custom MIDI style and add it to a track.
1: I right-click on the empty Melody track and choose 'Select custom MIDI style for this track'
2: I want a Slow String patch, so I choose Slow Strings as the Patch and then press 'Choose Style with this patch' (Figure 1)
3: I select 'BOSANEW' as the style which clearly shows it has a Strings track using Slow Strings. I press OK (Figure 2).
4: I now need to select which track I want to use from BOSANEW.STY. However, in the drop-down there is no Strings track. The tracks that are shown are actually the names of the tracks in my already existing song, not the ones in BOSANEW.STY (Figure 3).
5: It now gets more complicated/weirder. I now get a message that 'Slow Strings is on Guitar 2 track of Style BOSANEW' and 'it will be placed on the track that you chose: Flute. This is OK'. (Figure 4) When or how did I choose Flute? I had chosen to put it on the Melody track. There was never a track named Flute.
6: I press OK and it places the MIDI patch on the Melody track and labels it 'Strings' (Figure 5). I wrongly think I've succeeded.
7: I generate the song and it renames the Strings track to Flute and doesn't have any MIDI data. It is an empty track (Figure 6)
I've watched the online video and read the help and I believe I'm doing this correctly. Any advice? Can anybody see an error in my workflow?
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
I think you problem stems from the fact that you are trying to use the melody track. This is not part of the original style and you are in fact trying to load 2 styles at once one on the style tracks and another on the melody track.
I would have thought you should be loading the custom midi style to the style track that you want to replace then choosing which track from the custom style to use as a replacement for your original style track that you are inserting on. I may be be quite wrong I have not tried this but it seems logical to me. As this keeps the style tracks where they should be the first 5 tracks, and the melody free for melody notes.
What you are trying to do actually sounds like a good idea. I remember doing something similar a few years back with moderate success. The trick was you can not assign a midi patch to a track in a style which does not initially have midi data assigned to it. So the idea of moving over midi data from a track from a different style sounds like the thing to do.
Then more recently there was a video where new features were apparently added which made this appear like it would be easy-peasy. So I just now spent 20 minutes giving it a go as you indicated. I get the same results - kinda a mess. So there must be another way. If I get a little more time today, I will look for the video and/or type a different approach and see what I can get.
.. you should be loading the custom midi style to the style track that you want to replace then choosing which track from the custom style to use as a replacement for your original style track that you are inserting on.
Mike
Mike, on first read this sounds like crazy BIAB-speak. But you may have it with the Melody track. This track has always been different and may be the culprit here. I can tell you some of the initial issues I see is the track naming convention which assigns different names to the tracks (original BIAB track naming versus name of the instrument on the track) - this can be very confusing.
Hi Video Track. I think you problem stems from the fact that you are trying to use the melody track...
Mike, thanks for stepping in and your response is genuinely appreciated. I would have thought that by now (2019), if I could not use the melody track for this task, then the option would have been disabled, or at least a reasonable warning would have been provided. Instead, it was absolutely accepting to allow me to proceed. I'm intrigued.
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
The trick was you can not assign a midi patch to a track in a style which does not initially have midi data assigned to it. So the idea of moving over midi data from a track from a different style sounds like the thing to do.
Dan, you're on the money here. I have gotten it to work before, but it is totally hit-and-miss. That clue about having some MIDI data already on the track might be the clue.
Meanwhile, absolutely nothing I have read states that a user cannot add a MIDI style to a melody track. After all, that track is designed for MIDI, no?
I am beginning to think this is a programmatical issue (note how I'm careful with my terminology )
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
I still suspect it may be user-workflow. Even the demo shows multiple ways to complete this task. I am getting my second cup of coffee now, wife still sleeping I plan to duplicate a different workflow from the demo and see if I can get this to work, if time permits.
Dan, yes, this is one of the videos that I reviewed also (several times). Note that nothing is disabled for the Melodist or Soloist tracks. Every track is available to be selected for use.
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
I still suspect it may be user-workflow. Even the demo shows multiple ways to complete this task. I am getting my second cup of coffee now, wife still sleeping I plan to duplicate a different workflow from the demo and see if I can get this to work, if time permits.
Dan, I hope the wife is really tired. All help is appreciated. Big
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
I had a BIAB Retrack Style (all RTs). I inserted a Orchestral Strings midi track over the RT on the Strings track with only a couple clicks of the mouse straight from the mixer menus.
Not sure if it mattered, but I unchecked this box... Just too often confusing for me to deal with it.
If so, not a "programmatical issue" after all. This is just how BIAB works. It can drive newbees crazy while older veterans just scratch their heads. I do believe cooler heads prevailed in this instance.
Well it seems then it is as I said you must use a style track. The first 5 tracks are considered to be the style tracks , after all if you you disable the style in a song it only disables the first 5 tracks, the melody track and the soloist and audio if present still play.You cant make a six track style by putting a style track on the melody track.
So it seems to me if your want to modify a style then you have to modify a style track.
Can't disagree with anything mentioned except that if I can't 'Assign a custom MIDI style' to the Melodist or Soloist tracks, then those tracks simply shouldn't be available for this function. No?
I'm going to report it. Hopefully they can fix it. Why waste two unused tracks?
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
Mike and Dan, thanks. You found the reason, but <groan> the underlying problem clearly is in the program code itself. There is no reason that those tracks are unusable for that function, and clearly nothing prevents them from being used, but try using them and the results are completely awry.
There are other underlying problems also. If I try to place the custom style on a RealTrack instead (as suggested), it still gives me the choice of the names of the existing RealTracks in my song instead of the name of the track from the custom style. Check it out:
This entire feature is riddled with issues. More work required. I don't think we actually won, yet. But you better believe that your input is thoroughly appreciated .
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
Can't disagree with anything mentioned except that if I can't 'Assign a custom MIDI style' to the Melodist or Soloist tracks, then those tracks simply shouldn't be available for this function. No?
I'm going to report it. Hopefully they can fix it. Why waste two unused tracks?
There are more than just two wasted MIDI tracks. As you probably know my pet peeve with BiaB is that all of the MIDI tracks are preassigned. I really want all 16 MIDI tracks open for the user. If this were the case you would not be having your problem.
Note that there could be a radio button where one side would be as is now and the other side would be all MIDI tracks open for the user.
YMMV
Whenever I get something stuck in the back of my throat, I dislodge it by drinking a beer. It's called the Heineken Maneuver.
64 bit Win 10 Pro, the latest BiaB/RB, Roland Octa-Capture audio interface, a ton of software/hardware
The other frustrating thing is that is actually hit-and-miss. Sometimes I can get it to work. Don't ask me why or how, but I can apply a custom MIDI style to the Melodist track.
BIAB & RB2025 Win.(Audiophile), Sonar Platinum, Cakewalk by Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Kontakt, Focusrite 18i20, KetronSD2, NS40M Monitors, Pioneer Active Monitors, AKG K271 Studio H'phones
There are other underlying problems also. If I try to place the custom style on a RealTrack instead (as suggested), it still gives me the choice of the names of the existing RealTracks in my song instead of the name of the track from the custom style. Check it out:
As pointed out - Turn off the "auto generate track labels" feature. A long time source of confusion.
But back to point, how did the inserted midi track work out for you? As you can tell, not many folks use this feature but I suspect it can be a cool idea.
Video: Band-in-a-Box® 2025 for Mac®: VST3 Plugin Support
Band-in-a-Box® 2025 for Mac® now includes support for VST3 plugins, alongside VST and AU. Use them with MIDI or audio tracks for even more creative possibilities in your music production.
Band-in-a-Box® 2025 for Macs®: VST3 Plugin Support
Video: Band-in-a-Box® 2025 for Mac®: Using VST3 Plugins
With the release of Band-in-a-Box® 2025 for Mac, we’re rolling out a collection of brand-new videos on our YouTube channel. We’ll also keep this forum post updated so you can easily find all the latest videos in one convenient spot.
From overviews of new features and walkthroughs of the 202 new RealTracks, to highlights of XPro Styles PAK 8, Xtra Styles PAKs 18, the 2025 49-PAK, and in-depth tutorials — you’ll find everything you need to explore what’s new in Band-in-a-Box® 2025.
Band-in-a-Box® 2025 for Mac is here, packed with major new features and an incredible collection of available new content! This includes 202 RealTracks (in Sets 449-467), plus 20 bonus Unreleased RealTracks in the 2025 49-PAK. There are new RealStyles, MIDI SuperTracks, Instrumental Studies, “Songs with Vocals” Artist Performance Sets, Playable RealTracks Set 4, two new sets of “RealDrums Stems,” XPro Styles PAK 8, Xtra Styles PAK 19, and more!
Special Offers
Upgrade to Band-in-a-Box® 2025 for Mac with savings of up to 50% on most upgrade packages during our special—available until July 31, 2025! Visit our Band-in-a-Box® packages page for all the purchase options available.
2025 Free Bonus PAK & 49-PAK Add-ons
We've packed our Free Bonus PAK & 49-PAK with some incredible Add-ons! The Free Bonus PAK is automatically included with most Band-in-a-Box® for Mac 2025 packages, but for even more Add-ons (including 20 Unreleased RealTracks!) upgrade to the 2025 49-PAK for only $49. You can see the full lists of items in each package, and listen to demos here.
If you have any questions, feel free to connect with us directly—we’re here to help!
Cari amici
È stata aggerate la versione in Italiano del programma più amato dagli appassionati di musica, il nostro Band-in-a-Box.
Questo è il link alla nuova versione 2025.
Di seguito i link per scaricare il pacchetti di lingua italiana aggiornati per Band-in-a-Box e RealBand, anche per chi avesse già comprato la nuova versione in inglese.
Band-in-a-Box® 2025 pour Windows est disponible en Français.
Le téléchargement se fait à partir du site PG Music
Pour ceux qui auraient déjà acheté la version 2025 de Band-in-a-Box (et qui donc ont une version anglaise), il est possible de "franciser" cette version avec les patchs suivants:
Band-in-a-Box 2025 für Windows Deutsch ist verfügbar!
Die deutsche Version Band-in-a-Box® 2025 für Windows ist ab sofort verfügbar!
Alle die bereits die englische Version von Band-in-a-Box und RealBand 2024 installiert haben, finden hier die Installationsdateien für das Sprachenupdate:
Update Your Band-in-a-Box® 2025 to Build 1128 for Windows Today!
Already using Band-in-a-Box 2025 for Windows®? Download Build 1128 now from our Support Page to enjoy the latest enhancements and improvements 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.
But you may have it with the Melody track. This track has always been different and may be the culprit here. I can tell you some of the initial issues I see is the track naming convention which assigns different names to the tracks (original BIAB track naming versus name of the instrument on the track) - this can be very confusing.
)
.
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean