Track utility #1 defined as midi channel #2. Then I saved the song. Loading the song next time BIAB changed the MIDI channel to #1. Why does BIAB not save te entered midi channels of the utility tracks with the song? All tracks are set back to midi channel #1. before and after attached...
thomas
Last edited by Genos Keyboarder; 12/26/2210:03 AM.
MIDI channel 2 is the one that BIAB sets aside for the Bass. This may be what is causing the problem. To see if I'm right or wrong, try setting the utility track to one that BIAB does now use... for example channel 11.
You can see which MIDI channels BIAB sets aside by selecting "Options | Preferences | Channels".
I can't imagine that the programmers would allow MIDI channel 2 input then. Then they would have to point out that for the utility tracks you may only take the MIDI channels from 11. The management of the channels must be done internally in the BIAB. The MIDI tracks already contain events with different channels, if you use the list editor you can see that. Someone of the developers should explain the MIDI event and channel management. So what has priority and how that is managed internally. (especially volume, program change and channel)
Under options/preferences, MIDI options/ channels you can assign the bass and piano tracks to different channels, freeing up channels 2 and 3. I don't know if that will help or not but it might be worth a try.
My momma didn't raise a fool. And if she did it, was one of my brothers.
64 bit Win 10 Pro, the latest BiaB/RB, Roland Octa-Capture audio interface, a ton of software/hardware
It should save to whatever channel it's set to as you could be using another VSTi on that track. "All tracks are set back to midi channel #1" I just tried it and yes it goes back to ch1 even if I set it to ch15 with Sforzando on the track. I think it's just something that was missed, hopefully there should be a fix.
I just spend 30 minutes which I will never get back going down this midi rabbit hole one more time. I immediately determined something is amiss. BIAB midi has always been what I term a hot-mess, but I can generally find a way to work around it.
Take a look at my default midi channel setup ( after a return to factory settings). I have multiple tracks sharing Ch#1. When I load the demo style, the piano and vocal choir both are on Ch#1. The piano patch plays the choir, not a piano. And the choir also plays a choir.
This is generally where I just stop. I will pass this thread to the development guys to see if they have a fix for all this.
I just spend 30 minutes which I will never get back going down this midi rabbit hole one more time. I immediately determined something is amiss. BIAB midi has always been what I term a hot-mess, but I can generally find a way to work around it.
Take a look at my default midi channel setup ( after a return to factory settings). I have multiple tracks sharing Ch#1. When I load the demo style, the piano and vocal choir both are on Ch#1. The piano patch plays the choir, not a piano. And the choir also plays a choir.
This is generally where I just stop. I will pass this thread to the development guys to see if they have a fix for all this.
Yes, that is wrong. The piano should be on channel 3. Did you happen to change the piano channel to channel 1 prior to the return to factory settings? If so not changing back to channel 3 could be a bug. "BIAB midi has always been what I term a hot-mess" That is one of the reasons I get out of BiaB ASAP. I do all of my MIDI work in Studio One Pro 6.
My momma didn't raise a fool. And if she did it, was one of my brothers.
64 bit Win 10 Pro, the latest BiaB/RB, Roland Octa-Capture audio interface, a ton of software/hardware
"BIAB midi has always been what I term a hot-mess" That is one of the reasons I get out of BiaB ASAP. I do all of my MIDI work in Studio One Pro 6.
IF, the BBPlugin worked with midi only (or if bbw4 would no generate up wavs as well !), look Ma no wavs, it is only a few secs generate time and as well you have all the sends.
Maybe they should just make a midi only Plugin ? I had that all worked out to do, and everything needed to do it, maybe I should get back onto that ?
I notice that you have a MIDI Supertrack style loaded. Is this on the Piano track and is it sforazando or maybe another VST? That would explain why you have two channels 1.
It's okay to have two tracks directing MIDI instructions to the same channel provided they are going to different VSTs. The setting is literally saying, "BIAB is sending data on channel 1 to whatever is in the plugin slot". I'm guessing that the other tracks are showing the default soft synth. (Problems will arise if all the tracks are sending MIDI to the same synth.)
Quote:
The above is my understanding. I don't play around with MIDI plugins too often in BIAB so I'm not an authority by any stretch of the imagination. Please feel free to correct me if my understanding wrong.
I had a similar problem with utility tracks not handling midi channels correctly after saving and reloading, and posted the issue and got an answer from Andrew at PG Music saying:
It does seem to be a bug that the channel is not saved on Utility tracks with the .MGU. There is an easier work-around though - right-click on the track --> Track Settings --> MIDI Channel --> select "Multi-channel". This setting is saved, and your MIDI file should play with the correct patch.
Perhaps this work-around will work for your issue. It's good to know that PG Music admits it is a "bug" that utility tracks cannot save and replay midi channels, because we can thus assume this will be fixed in the future.
Another trick, if you only need a few tracks with permanent assigned midi channels, you can put that information on either the Melody, Soloist or Audio tracks (any of them can hold midi information and be renamed.) Those three, unlike the utility tracks, will not have this problem.
I notice that you have a MIDI Supertrack style loaded. Is this on the Piano track and is it sforazando or maybe another VST? That would explain why you have two channels 1.
It's okay to have two tracks directing MIDI instructions to the same channel provided they are going to different VSTs. The setting is literally saying, "BIAB is sending data on channel 1 to whatever is in the plugin slot". I'm guessing that the other tracks are showing the default soft synth. (Problems will arise if all the tracks are sending MIDI to the same synth.)
Regards, Noel
No, this is not a SMT. It is all just plain MIDI. The style is Style is AG_GOSP.STY (AG_GOSP - Slow Tempo 3/4 Gospel). All midi is sent to the default Synth.
Hello all. Thank you for your help. I have the program only a week, but I'm afraid I will discover all the bugs ;-) I have 40 years of experience with MIDI and software development. So of course I test everything out so I can use it for my purposes.
No, this is not a SMT. It is all just plain MIDI. The style is Style is AG_GOSP.STY (AG_GOSP - Slow Tempo 3/4 Gospel). All midi is sent to the default Synth.
Hi Dan,
My mistake. I just saw the light blue colour and didn't look any further than that. I was colour-coded into a false sense of security. Now, when I pay attention to the original image, I can see it is just a plain MIDI style. Sorry.
Thanks for checking it out.
I wonder what changed your MIDI settings and gave you two channels 1? I've never had anything like that happen (that I'm aware of, at least).
For reference, the image below shows what they should be.
No, this is not a SMT. It is all just plain MIDI. The style is Style is AG_GOSP.STY (AG_GOSP - Slow Tempo 3/4 Gospel). All midi is sent to the default Synth.
Hi Dan,
My mistake. I just saw the light blue colour and didn't look any further than that. I was colour-coded into a false sense of security. Now, when I pay attention to the original image, I can see it is just a plain MIDI style. Sorry.
Thanks for checking it out.
I wonder what changed your MIDI settings and gave you two channels 1? I've never had anything like that happen (that I'm aware of, at least).
For reference, the image below shows what they should be.
--Noel
I've just reset to factory settings and the midi channels are again different to the above.
Brian Cadoret BIAB 2025 Pro build 1125e with BIAB2023 UltraPAK . Samplitude Pro X4 Suite. Mixcraft 10.5 Pro Studio Focusrite 2i2 Scarlett Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz 3.20 GHz Installed RAM 8.00 GB
Interesting. A few versions of BIAB back, I had channels 7 and 6 (guitar and strings) swap with one another. I reported it to PG Music at the time, and then promptly forgot about it until now. In all the years I've had BIAB, I've never altered the MIDI channels. What is there now on my image is from BIAB 2023 (1005). I have no idea if these are the channels before the swap occurred or after.
Below are the settings shown in the 2023 manual. It seems that mine are still swapped! I'll change them back.
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.
Already using RealBand® 2025 for Windows®? Download Build 5 now from our Support Page to ensure you have the latest enhancements and improvements from our team.
PowerTracks Pro Audio 2025 is here! This new version introduces many features, including VST3 support, the ability to load or import a .FLAC file, a reset option for track height in the Tracks window, a taller Timeline on the Notation window toolbar, new freeze buttons in the Tracks window, three toolbar modes (two rows, single row, and none), the improved Select Patch dialog with text-based search and numeric patch display, a new button in the DirectX/VST window to copy an effects group, and more!
First-time packages start at only $49. Already a PowerTracks Pro Audio user? Upgrade for as little as $29!
Video: Summary of the New Band-in-a-Box® App for iOS®
Join Tobin as he takes you on a tour of the new Band-in-a-Box® app for iOS®! Designed for musicians, singer-songwriters, and educators, this powerful tool lets you create, play, and transfer songs effortlessly on your iPhone® or iPad®—anytime, anywhere.
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.
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean