After recording a midi track to Realband I have discovered if I re-open the song I do not get any sound from that track unless I open the synth and make sure I am on the same channel. So how do I save the actual synth sound to the song? Furthermore when I record the string track and play it back I hear nothing on the oboe track. Oboe channel 1 strings channel 2.
Last edited by Rich59; 04/05/1812:50 PM.
BIAB 2018 latest build, Window 10 Pro 64 bit operating system X64 based processor Intel(R) Xeon(R) CPU ES-2670 @ 2.60GHz 16 Gigs Ram Tascam 2x2 audio interface. Podxt
My guess is that you are saving as a midi file as you were working in midi,
Unfortunately midi does not save track information only channel and voice and midi data etc In order to save track specific information like assigned synth you must save in the DAWS native format . For Realband that is a . SEQ file , it will then recall those setting when loaded. If you save or export as midi you will always have to tell the receiving program what synth it is using on what track so if for example you save as midi then open in say Sona you would have to reassign your specific synths vst etc to the respective tracks And then save as a Sona project. I did explain this on my long link on the other thread Regards Mike ps Just another point Midi tracks, midi channels, and midi ports are three separate things , Therefore midi channel 2 may not be on midi track2 unless you set it to be. In fact BIAB uses track 2 for midi drums on channel 10 This again was covered in my link.
Press both the Ctrl and F5 keys at the same time or click on "Options" > "Preferences" to open RealBand's Preferences dialog window. Then click on the number "3" or on the "File" tab to open the file window.
The last selection at the bottom of the "File" page is "Default to SEQ format when saving a file". The checkbox is supposed to be checked by default but it may have somehow become unchecked.
Still messed up. Recorded Oboe on channel 1 selected channel 1 for track to be recorded plays fine select channel 2 for strings selected channel 2 for track to be recorded The oboe now is using the string patch.
So the issue isn't how it is being saved which is what I perceived. The issue is the sounds changing although they are on different midi channels as I record subsequent tracks.
Last edited by Rich59; 04/06/1812:51 AM.
BIAB 2018 latest build, Window 10 Pro 64 bit operating system X64 based processor Intel(R) Xeon(R) CPU ES-2670 @ 2.60GHz 16 Gigs Ram Tascam 2x2 audio interface. Podxt
Very strange just a thought . It almost sounds as if the synth you are using is not multi timbral. You may have to insert multiple separate instances one for each track
As test for now why not try just using the coyote wave table as a default synth in your midi setting and send midi to default vst And try that with different basic gen midi voices on different tracks and channels Also set track specific thru voice in rb pref as previously if you want to hear what you are recoding. Mike
You may have to insert multiple separate instances one for each track Mike, If it is not to much trouble could you further explain the above statement. Specifically the steps you take to do this.
BIAB 2018 latest build, Window 10 Pro 64 bit operating system X64 based processor Intel(R) Xeon(R) CPU ES-2670 @ 2.60GHz 16 Gigs Ram Tascam 2x2 audio interface. Podxt
I suspect your problem is that the data on track two is actually on the same channel as the data on track one. If both came in from your keyboard, then both are on the same channel, even if you changed it at the track level.
I suggest you highlight track 2 (select all), hit F2 to bring up the MIDI Event Editor, and look at what channel the notes are on. If track 2 is not listed as channel 2, then use the "Rechannel MIDI" command in RealBand to change track two from its original channel to channel 2. Assign your instrument and you should be good to go. I do this all the time.
You can do the same to see what happens on track 1. Make sure each instrument is on a different MIDI channel.
If two tracks share the same channel (which oftentimes you may intentionally do), then all the MIDI commands go out on that same channel. So whatever the "last" instrument patch selected along the MIDI timeline was will be the one that plays.
I could be wrong, but I believe that is your problem.
John
Laptop-HP Omen I7 Win11Pro 32GB 12TB SSD Desktop-ASUS-I7 Win10Pro 32GB 12TB SATA
Hi Rich This is normally done for choosing specific VST and DXI By right clicking on a midi track in real band and choosing Specific vst/dxi for MIDI track this will insert the vst on its own port.
Your external hardware mid synth will be as selected in your midi set up As an input and output device .
Please remember I am using a midi controller keyboard just to play the midi notes to the software to VST and DXI of which I can insert separate instances of I am not using an external synth like a full Yamaha keyboard with on board voices for any of my voices. So I don’t have the problem that you have, You could try using your keyboard as just an input device to send midi note data to the software and use internal vst and dxi Other than that you have me stumped
Mike, the keyboard is just a midi controller not an actual synth. JFord's suggestion in the post above yours sounds like it may be the answer. I will check it out after work and give an update.
BIAB 2018 latest build, Window 10 Pro 64 bit operating system X64 based processor Intel(R) Xeon(R) CPU ES-2670 @ 2.60GHz 16 Gigs Ram Tascam 2x2 audio interface. Podxt
JFord, I also changed the channels to 1 and 2 respectively on the midi out of the synth software before each instance of recording but I will check this out tonight.
BIAB 2018 latest build, Window 10 Pro 64 bit operating system X64 based processor Intel(R) Xeon(R) CPU ES-2670 @ 2.60GHz 16 Gigs Ram Tascam 2x2 audio interface. Podxt
I surrender, Nothing works . If I change the midi channel to the correct channel in the midi events dialog box the other recorded midi channel does not play back any sound. Or I here the sound from the first track on the second track and if I go into that channels midi events dialog I find that the channel changes to the one I selected in the first track.
Last edited by Rich59; 04/06/1812:16 PM.
BIAB 2018 latest build, Window 10 Pro 64 bit operating system X64 based processor Intel(R) Xeon(R) CPU ES-2670 @ 2.60GHz 16 Gigs Ram Tascam 2x2 audio interface. Podxt
Well you do seem to have problems I still think the best bet is to go back to a basic set up using something simple like the coyote wave table as your default synth See my post earlier
Quote “As test for now why not try just using the coyote wave table as a default synth in your midi setting and send midi to default vst And try that with different basic gen midi voices on different tracks and channels Also set track specific thru voice in rb pref as previously if you want to hear what you are recoding.”
And see how you get on then with different voices and channels on different tracks. Mike
HI Rich Maybe this will help after you have tried my last post suggestion of a simple set up
Here is a SEQ file that I made by opening a BIAB mgu in Realband. From the pic you will note that the first 8 tracks are designated as BB tracks that means they have retained their respective BIAB track and channel defaults, Therefore drums are on track 2 channel 10 and the other tracks follow BIAB default track and channel assignments as well. You will also note that it is sending to my virtual midi synth however this gets over ruled by my midi preference reroute MIDI playback to default dxi/vst synth in this case Coyote WT
You will also notice I have Classic Track view open very handy view to see what goes where (CNTR 9)
Gentlemen, Thank you for all the help you have offered and time spent. Yesterday I decided to download Reaper and after getting it set up I recorded 4 different tracks to the intro of the song I was trying to do. Once I understood the basics and got the drivers set up it worked beautifully. In fact when I installed it it searched for all my vst plugins including my synth. I did not have to do a thing except to select the correct input and output devices. After saving the song, if I re-open it the synth comes up for each individual track with the correct instrument, and, each instance of the synth is labeled with the track number and instrument based on the track name. All I have to do is click the effects icon on the track I want to work on and that instance of the synth comes to the front of my 2nd monitor screen and the sound selected for that track plays. After testing I decided to make the purchase. Thanks again for all your help. It is greatly appreciated.
God bless you and your families, Rich
ps: I am still using BIAB so I am sure I will still be bugging you guys alot. lol!
BIAB 2018 latest build, Window 10 Pro 64 bit operating system X64 based processor Intel(R) Xeon(R) CPU ES-2670 @ 2.60GHz 16 Gigs Ram Tascam 2x2 audio interface. Podxt
I would still love to take a look at your RealBand file to see if I can figure out what the underlying problem was. I'm glad that you were able to make it work in Reaper; however, it works for me in RealBand going back many years. If you could provide the file (no judgment and I won't share with anyone), I would love to take a look at it. Mainly, because I think this would be of help to other people who might experience a similar problem. Similar questions have been asked on the forum many times over the years and having a good answer helps everyone.
But if not, that's fine, too. I'm sure it will come up again.
My instruments always save in BIAB and RealBand. I can pull up projects from years ago, and as long as the VSTi's are still in the list of available VSTi's, everything works like the day I saved it.
John
Laptop-HP Omen I7 Win11Pro 32GB 12TB SSD Desktop-ASUS-I7 Win10Pro 32GB 12TB SATA
Unfortunately I deleted that project. I was working on a backing track for my church, It was only strings and I had an oboe in the intro. Never got to actually create anything because the synth and Realband would not work together.
BIAB 2018 latest build, Window 10 Pro 64 bit operating system X64 based processor Intel(R) Xeon(R) CPU ES-2670 @ 2.60GHz 16 Gigs Ram Tascam 2x2 audio interface. Podxt
If you ever do try it again, let me know (ping me) and maybe we can figure it out. I'm pretty sure it's just one little thing (maybe two) that's easily fixed that's being overlooked.
John
Laptop-HP Omen I7 Win11Pro 32GB 12TB SSD Desktop-ASUS-I7 Win10Pro 32GB 12TB SATA
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.
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean