Utility tracks don't show up in the Bar Settings window, so how can do bar settings for Utility tracks at particular bars? I'm looking to mix the horns down for the first verse and bring them back in for the chorus and 2nd verse.
Band-in-a-Box® for Windows Version 2025 (1125e) 64 bit application RealBand 2025 (1) Windows 10 Pro 64-bit Intel Core i7 4800MQ @ 2.70GHz Haswell 22nm Technology 16.0GB Dual-Channel DDR3 @ 798MHz (11-11-11-28)
Utility tracks don't show up in the Bar Settings window, so how can do bar settings for Utility tracks at particular bars? I'm looking to mix the horns down for the first verse and bring them back in for the chorus and 2nd verse.
Yes, but... That would turn a ReaLTrack into an AudioTrack (.wav), and take up more space and create an additional file.
RealTracks (and RealDrums) are already Audio files. They are 'assembled' to make a new output file. That's what plays when you press generate/play. It's always been that way with RealTracks. There is no 'additional' file at all.
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
Yes, but... That would turn a ReaLTrack into an AudioTrack (.wav), and take up more space and create an additional file.
In the 2022 version if you generate a RealTrack onto a Utility track, like you would on a legacy track, it will remain a RealTrack. Also Volume Automation does not turn a RealTrack into an orange audio track.
Last edited by Chantelle - PG Music; 02/23/2209:48 AM.
Yes, but... That would turn a ReaLTrack into an AudioTrack (.wav), and take up more space and create an additional file.
RealTracks (and RealDrums) are already Audio files.
Yes and no. Real tracks are not stored as a separate wav file in the song's folder. They are stored in the designated RealTracks folder. Only the .sgu/.mgu file needs to be stored and references the RealTrack to be used. Not seperate audio file, as would be created if you use the audio edit feature. (Not volume automation).
Chantelle's comment is correct. I am referencing 2022 version. But if you use audio edit features.. it will convert to an audio file
Hi Thunderthud, thanks for the clarification. Yes, when you click the Edit menu in the Audio Edit window, those functions will convert the RealTrack to an orange audio track, whereas the Volume Automation feature does not.
Yes, but... That would turn a ReaLTrack into an AudioTrack (.wav), and take up more space and create an additional file.
Exactly, you don't need all these wav files, most of the destructive Audio Edits can be made non destructive same as the Vol automation thus not writing the RealTrack data to wav files. You want to be able to copy any RealTrack/Drum data to any other track without creating new wav files, "Look Ma No WAVs". This is the same way modern DAWs work.
There have been a number of similar questions based on inaccurate expectations regarding UTs, probably prompted by PGM inferring that they were the same as Legacy Tracks. I think a tutorial video from PGM explaining what we can and cannot do with UTs would be appropriate.
This particular subject, "RealTracks Being Converted to Audio Tracks" by AudioEdit, is NOT unique to Utility Tracks. The same issue exists on Legacy Tracks. So, in this case... I guess "all tracks are equal".
This particular subject, "RealTracks Being Converted to Audio Tracks" by AudioEdit, is NOT unique to Utility Tracks. The same issue exists on Legacy Tracks. So, in this case... I guess "all tracks are equal".
This is true. The unique concept of "RealTracks Being Converted to Audio Tracks" in the Audio Edit Window has been possible on Legacy Tracks since 2012 when Audio Performance Tracks were introduced in BIAB for Windows. Audio Recording introduced in 2015 in BIAB elevated the program to the level of being a digital multi track recorder. This was a huge development that was overlooked by most BIAB users that participate in the Forums thus generating few if any questions or discussion.
Being a multi track recorder put BIAB on par with top of the line hardware, stand alone multi track recorders at that time like the Tascam DP 24 and Zoom R24. All of the principles of multi track recording apply to BIAB and most every process and technique applicable to hardware units can be used in BIAB. The Audio Channel and Artist Performance track is the bridge and link between RealTracks, the BIAB Mixer and audio. Most folks only knew Artist Performance Track from the Artist Performance sets included with the purchase of the program.
As a multi track recorder that when combined with other BIAB features like the RealTrack Medley Maker and MultiStyles, the myth that BIAB was limited to only seven tracks is completely dispelled. The RealTrack Medley Maker provides a 10 channel RealTrack sub-mixer to each of the seven Legacy Tracks making it possible to generate a stereo mix of up to 70 different instruments in a single render. Combine the RealTrack Medley Maker with the Audio Channel and Artist Performance Track feature, these multi track recording processes create layers of tracks numbering in the dozens with no degradation in the sound quality.
Originally Posted By: Thunderthud
Yes, but... That would turn a RealTrack into an AudioTrack (.wav), and take up more space and create an additional file.
Regardless of what program a track is edited in, there will be an audio file created to use it in BIAB. In BIAB, any audio file can be saved as an MP4 to reduce the file size without affecting the BIAB song audio quality.
It appears you've generated and frozen RT1515 on Track 1 in BIAB and then extracted text data of that generated track in order to open that exact generated RT1515 audio data in Reaper without creating an audio file (Wav/Mp3/Mp4). The Gif demonstration clearly shows Track 1 in BIAB has not been edited and is colored green and not orange that indicates the track has been converted to an Artist Performance Track after editing has been done on the track.
The issue in this post is that editing with the BIAB Audio Editor with commands other than volume automation creates an audio file when the project is saved and closed.
What you've shown is Reaper reading text instructions from BIAB without having to export the file as audio. However, you obviously must then complete the edit in Reaper so how do you get the edited audio from Reaper back into the BIAB project without creating an audio file that will load and be saved as an Artist Performance Track? Are you able to generate a text file in Reaper that BIAB can read to import the edited audio without it creating an Artist Performance Track audio file?
"so how do you get the edited audio from Reaper back into the BIAB project without creating an audio file" The whole idea is to get out of Biab into a modern DAW where you have a 1000 times more control and freedom to do what you like without creating a hard drive full of wav files, you don't want to get back in Biab. I can regenerate any section of any track directly in Reaper. I can generate a whole new track. I can generate RealCharts. I can generate midi tracks. I can generate all the style tracks. I can instantly change an FX RealTrack into a Direct Input with all the same sections playing. I can instantly change back from DI to FX RT. I can instantly change a stereo RealDrums track into 10+ stems tracks. I can generate up the missing Holds for UsersTracks. I can generate up Midi UsersTracks. Is that a good thing or a bad thing ?
The best thing about Biab is it's content and all the wonderful content is in a simple txt file. Don't forget I spent years in the RealBand jail of crashing, frustration and massive project files. If I had know I could do this back in 2009 with Reaper I would not have spent all these years here. This way is heaven !
You've answered your own question. It's obviously a bad thing. The 'do it in Reaper' solution fails to accomplish the tasks requested.
With respect to the posted question, you've presented a complicated, sluggish process specific to Reaper that uses approximately 66mb of disk space to avoid creating a 3-4mb file. The process is dependent on using BIAB generated data and audio and with the power of Reaper's features, tools and the power of scripting, nothing on the list of BIAB tasks you posted apply to the post question. It does demonstrate Reaper can't edit a RealTrack as simple, quick and easy as BIAB can do them natively.
In the 2022 release, the whole idea is to not leave BIAB for a DAW because there's no longer (never was) 1,000 times more control and freedom to create tracks that are complex arrangements, not just random renders of a chord progression. Hard drive space is of no concern because BIAB projects and associated files can be stored on external storage.
The better solution is to record non-BIAB audio/midi tracks in a DAW and import those tracks into the BIAB project and take advantage of all the exclusive and unique capabilities the BIAB program.
You're correct saying the best thing about BIAB is it's wonderful content. But also it's features, tools and processes that are all contained in the singular BIAB program. Your years of struggle with RealBand is because RB has never been a full-featured BIAB product. The VST-Plugin isn't either. Reaper, Sonar, Logic, Pro-Tools, Studio One, Cakewalk, Ableton, Garageband, Audacity and all other DAWs have none of the BIAB capabilities embedded.
You are missing the point completely, All Modern DAW's have no problem at all with non destructive audio editing and play direct from source. If Biab had this you would not have this problem, you could simply copy any section of a RealTrack to another track without it becoming a wav file, you can apply any effect without it becoming a wav on the hard drive. If it played direct from the source as DAWs do, it would be quicker and you would have a Live Arranger that played real audio not midi direct from keyboard chord input. And that is a BAD thing ? The best thing you could possibly do is contact all these DAW companies and get them to go back to destructive off line editing of the 90's. Last year utility tracks generated up Audio RealTracks this year they are in RAM, does that get a bit scary for you ? How can you stop PG going any further and allowing copying of RealTracks to another track without it turning into a wav file and having more non destructive editing like Vol automation, where did that come from ??? I was the one that had to really fight to get Vol automation in RealBand !!!! I was the one that showed way back how to have more tracks in Biab !!! I have showed PG how to have instant generate of tracks in RealBand !!! Way way back I suggested Biab be 64bit and have more tracks, I copped so much flack for suggesting such a thing !!! And now I see the same users saying how wonderful more tracks and 64bit are. So many things that have been added to Biab I suggested that you yourself now use, and here I am now getting hassled for saying such things. I think you should be showing a bit more appreciation for what I do rather than purposefully giving me a hard time. I use Reaper as an example, if it can do it Biab can also. Maybe you are one of the reasons here why Biab was still stuck in the 90's for so long. Why don't you suggest new ideas yourself rather than fighting to keep it in the past, if you want that go back to an older version. It's like you are holding onto the past and don't want to let it go. Give me a *^%$&( break and grow up.
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