OK, I have looked closely at this. It appears what we are seeing is a way to permit the midi tracks in the BIAB VST within Reaper to use whatever sound-source is available rather than the Win10 GM player. To do this, the BIAB VST is first inserted on one of the Reaper tracks. Apparently, the midi tracks on the first page of the BIAB VST output to the standard BIAB midi default channels:
Next, it appears in Pipeline's clip that we just have to use Reaper routing to send the individual default midi channel from the Reaper track which has the BIAB VST on it, to a separate Reaper Track, which has a sound synth on it which then receives the midi channel. Could it really be that simple! Oh, then we have to mute the original BIAB VST tracks (I think).
Yes once you have the midi you like you can then drag it out into it's instrument track and mute that track in the BIAB VST.
But I posted this info May 2019 Video: Playback Audio/MIDI Tracks from Plugin maybe I didn't make it clear enough. Now that others are using this they will soon find what all the fuss is about solo/mute buttons, YOU NEED THEM !
LiceCaps are nice for quick demos, but a video within someone explaining what you are seeing can only go so far.
And then we have the BIAB-VST ... this is not your typical VST plugin (Dah, I don't have to tell you that).
And finally, my midi routing chops are just above the novice level so this stuff is not fully clear to me at times. But I am getting it. thanks for being persistent!
Can't get it to work! No midi flowing from the BIAB VST SMT piano [channel 3 Track 1] to the 88Keys VST on [All, Track 2].
I route [midi chn 3 track 1] to [All on Track 2]. Then I arm track 2, but no midi coming in and no sound coming out. Oh well, one more strikout for the BIAB-VST.
Did you double click the piano track in the BIAB VST ? it can be confusing as some users think yellow is solo color, blue is sync play, green is mute and red is mute, I thought green was go and red was stop but both green and red are stop, I got confused at the traffic lights the other day after using BIAB VST I pressed the brake twice with my left foot thinking the lights would turn blue and I could go I think I was just still a bit stressed out EDIT: in the pic I should of set the audio send to none.
I have a single MST Piano with several RTs in the style. No matter what I do I cannot make the MST button/track turn BLUE. It just toggles red to yellow. I see your midi track turns blue. Maybe it doesn't work with SMTs? What are the chances?
Also try soloing the piano track in the BIAB VST and send All midi channels make sure it's not on another.
Don't know how to do that " try soloing the piano track in the BIAB VST " tried both yellow and red colors. No blue available.
I did try the ALL midi channel and no go. So it does work in your machine. I have the newest beta running. How about you?
Oh well, I don't really need this feature. Just thought if it worked I might find a use for it. Generally, that captures my entire thoughts on the BIAB Vst.
The number 1 priority should of been to get this interface working, make it industry standard, intuitive. Get away from Biab DOS thinking and get into professional DAW thinking. I don't know what else I can do, in the beginning I asked ever so nicely, but over a year on
Here is the good news. In the past if I pushed enough buttons enough times it would always crash before it played. Today, I pushed every button in every way to get to this routing to work. And it did not crash!! That's progress.
That's why as the tracks are generated they should be set to blue (except for master it will stay green)
Blue appears to be Solo (or play since multple tracks can go blue) Except the midi track it can't go blue unless every other track is green (which appears to be mute). Red is also mute.
OMG, these buttons are crazy... And to make it worse they appear to be single click, double click and right click activated in some manner beyond me.
I just tried turning the other tracks to blue but they won't turn blue unless the midi track is yellow and the midi track won't turn blue unless the other tracks are green ! Man this is doing my head in !
I think you will just have to add another track with another instance of the BIAB VST, load the same song.SGU and generate only the Midi Super Tracks and send that to the piano track.
Red, Blue, Green, oh my! No wonder I am having such a hard time with this. I am partially color blind!
Its like you said "The number 1 priority should of been to get this interface working, make it industry standard, intuitive. Get away from Biab DOS thinking and get into professional DAW thinking." Or like I previously said "it is time for PGMusic to get into the 21st century".
When you are at the checkout line and they ask if you found everything say "Why, are you hiding stuff?"
64 bit Win 10 Pro, the latest BiaB/RB, Roland Octa-Capture audio interface, a ton of software/hardware
Blue is sync. Allows playing that track synced with the daw track (right click)
Red is mute. (left click)
Green/yellow is play yellow being midi
Clicking in the left track pane highlights the intended track basically “Solo”
Highlight the first track under master and hold Shift then hit last track highlights them all to play them all
Hold control allows picking individual tracks to highlight and play together to solo mire than one.
Also the + in each track has options to sync and mute that track
As pipeline mentioned you can play the midi by setting up an instrument track and inputting the plugin into it and placing an instrument in the track.
Last edited by Rob Helms; 04/27/2011:40 AM.
HP Win 11 12 gig ram, Mac mini with 16 gig of ram, BiaB 2025, Realband, Reaper 7, Harrison Mixbus 9 32c , Melodyne 5 editor, Presonus Audiobox 1818VSL, Presonus control app.
Your first video shows a clear bug. The midi should sync along with the audio. I also feel super midi tracks should be a different color so the blue identifies sync and sync alone. That would solve two obvious issues. Users could sync whatever tracks they want with the DAW.
HP Win 11 12 gig ram, Mac mini with 16 gig of ram, BiaB 2025, Realband, Reaper 7, Harrison Mixbus 9 32c , Melodyne 5 editor, Presonus Audiobox 1818VSL, Presonus control app.
How easy is this for anyone to work out, you simply would not have had all the stress, confusion and giving up if it had worked this way. The generated tracks play along with the host as default, simply mute, solo or drag out, simply click the Sync Host button to preview just in the VST that's it, that's all I've been saying for a year !!
Hi Dan, I'm glad to hear that you got things working. To sum all this up:
GREEN = Audio Track YELLOW = MIDI Track BLUE = "Track (Audio or MIDI) is synced to DAW" RED = "Track (Audio or MIDI) is muted"
*You cannot sync both Audio and MIDI tracks at the same time. This is because the plugin cannot output audio and midi together. So if an Audio track is synced (blue) then you can sync other audio tracks, BUT double clicking on a MIDI track will do nothing. If you want to sync MIDI tracks then make sure there are no Audio tracks selected. The same happens vice versa. I hope this helps!
I’m going to agree with pipeline on a couple things here. Some of how it is, is fine here. This is what I would change.
1. Change the drag feature to grab in the right track pane to drag
2. Turn the green drag button into a sync to host button ( I like the ability to sync tracks individually) or at the least leave the sync in the “+” list
3. Add a mute/solo button left “m” for mute “s” for solo left click alternating
4. Don’t really need a sync to host button near play it can be on the master track like the individual tracks.
5. Don’t need the ability to add VSTs to plugin once synced to host each track can be run thru a FX channel, or a instrument track and any type of VST or FX can be tested before dragging.
These things would make the plugin more intuitive to new DAW users.
I hope at some point the ability to sync midi and audio at the same time can be added but now understanding that it not a bug but intended helps me in my workflow.
HP Win 11 12 gig ram, Mac mini with 16 gig of ram, BiaB 2025, Realband, Reaper 7, Harrison Mixbus 9 32c , Melodyne 5 editor, Presonus Audiobox 1818VSL, Presonus control app.
5. Don’t need the ability to add VSTs to plugin once synced to host each track can be run thru a FX channel, or a instrument track and any type of VST or FX can be tested before dragging.
Vst on a plugin track was just spitballing ideas for "Down the track" mentioning that won't make PG stop what they are doing and implement it. To get something implemented you need to nag for years like I nagged for 10 years to get the VST Sync implemented so users could use ezdrummer/ezkeys etc..
This current nagging for industry standard solo mute sync has been going on for over a year and could very well need someone else to take the baton.
I remember Adar saying it was on the chalkboard for down the road. So maybe
Last edited by Rob Helms; 04/27/2001:14 PM.
HP Win 11 12 gig ram, Mac mini with 16 gig of ram, BiaB 2025, Realband, Reaper 7, Harrison Mixbus 9 32c , Melodyne 5 editor, Presonus Audiobox 1818VSL, Presonus control app.
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