I did a quick project on BIAB 2022. I rendered using the usual dialog, choosing no full render, render individual tracks, each track dry and center, no normalization.
When playing the project within BIAB, it all sounded fine with the mixer faders at their default positions. But the rendered file is probably 24 dB too hot in the bass track -- it is loud and completely distorted. The other tracks rendered fine (in their individual files.)
I tried pulling back the bass fader before rendering,m but that didn't work. I was able to get a usable file by pulling down the complete "This song" fader. That got the bass below the distortion level.
This never happened to me on any previous release. Anybody else seeing this behavior?
I did a quick project on BIAB 2022. I rendered using the usual dialog, choosing no full render, render individual tracks, each track dry and center, no normalization.
When playing the project within BIAB, it all sounded fine with the mixer faders at their default positions. But the rendered file is probably 24 dB too hot in the bass track -- it is loud and completely distorted. The other tracks rendered fine (in their individual files.)
I tried pulling back the bass fader before rendering,m but that didn't work. I was able to get a usable file by pulling down the complete "This song" fader. That got the bass below the distortion level.
This never happened to me on any previous release. Anybody else seeing this behavior?
I just tried this with that style and it worked fine.
The mixed track WAV (all tracks in one file) was fine and the individual tracks including the bass were also fine (separate WAVs for each track).
i assume youve pulled down the fader in the mixer on the bass trak ?...that dont work ? post a pik of the audio edit window for bass trak plz after being genned. best om
i assume youve pulled down the fader in the mixer on the bass trak ?...that dont work ? post a pik of the audio edit window for bass trak plz after being genned. best om
No, As I recall, the track fader was reset automatically when I did the render, but the "This Song" was not. At least that is my recollection. I will do some additional testing Friday. Maybe I overlooked something obvious.
I loaded the demo song for _SJAZZC2 style and certainly did not find the bass to be too loud. Actually, if anything it was sitting a little in the background.
The levels were all set to 90 when I loaded the song:
BIAB & RB2024 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 was able to do further testing. It happens on other styles. I installed at level 904, but updated to 905, and the problem is still present. To notice the problem, one does need to listen carefully, and perhaps use studio-grade speakers. On my system, the problem is blatantly obvious, but on other systems, it may not be so obvious. In all cases, the bass is at the expected level in the mix when playing directly under BIAB, but it renders about 6dB higher when you send it to WAV. That is always wrong, but depending on the style it may or may not sound distorted. With _SJAZZC2, it is horribly distorted. With _PROMSP it is twice too loud, but not badly distorted.
I was able to create a very simple song from scratch using all defaults, no special settings, and the problem is there every time. The problem is not strictly related to the rendering dialog. The same problem happens if I render a track by dragging onto the "WAV" part of the widget and then drag the rendered file to my song folder. And it happens every time, only on bass -- the other instruments are always fine.
Here is a guide to the attached files:
Loud bass _SJAZZC2.TXT is the BIAB file (in text form) of the file I started with
Played from BIAB live.mp3 is what the full mix sounds like when played under BIAB using default mixer settings. Sounds perfectly normal.
Played from BIAB live.png is a screen shot of that file in Audacity. Notice that with all the instruments in the mix, it is never close to clipping.
Bass line dragged.mp3 is the sound file when I drag-render just the bass track
Bass line dragged.png is that same file displayed in Audacity. Notice the bass track alone is much hotter than the entire mix file, and is badly clipped.
I didn't change any mixer settings -- or any other settings -- any time when saving these examples. Also note that I did not request normalization -- indeed, I didn't even use the render dialog. These are the levels that BIAB used on its own.
Aha. I think I know what is happening here. The tracks that render as stereo are coming out at the right level. The tracks that render as mono have a routing problem internal to BIAB that is doubling their level. I used _PROMSP which has 2 guitars that render mono, and those guitars are both double loud.
This is undoubtedly a bug. I'm sure it never worked like this before I have done dozens (maybe hundreds) of projects like this and would have noticed a doubling of the volume for sure.
As a test, could you try manually saving the bass to a wav file rather than dragging it.
To do this...
1. Right click on the Bass track
2. Select "Track Actions"
3. Select "Save Track as WAV File" (double check which directory it's being saved to... by default, the file will save in the same directory as the song file and it will be called "[song title] BBBass_Real_SingleRender.wav"
3. Select "Save Track as WAV File" (double check which directory it's being saved to... by default, the file will save in the same directory as the song file and it will be called "[song title] BBBass_Real_SingleRender.wav"
4. Now load that saved WAV into Audacity
Is this any better?
No. That WAV file is double loud and clipped, just like the results when dragging or when using the render dialog.. (It is mono, as expected.)
There was an issue with an earlier test version where all the channels were getting summed if you selected Solo or Mute the buttons, but I thought that was resolved.
Did you mute or solo any tracks when creating the output audio?
BIAB & RB2024 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 was an issue with an earlier test release where all the channels were getting summed if you selected Solo or Mute the buttons, but I thought that was resolved.
Did you mute or solo any tracks when creating the output audio?
I did some solo/mute operations at first, but the files I loaded above were all done without any solo or mute. And the file I created from scratch (not loaded above) had the same problem even though I never touched solo or mute on that file.
Perhaps this is another variation of the bug you referred to. It does seem the mono tracks are being double-summed.
When you click on the "Plugins" tab on the Mixer, what does it day for the Bass track? Is it four "none" like shown on the image below?
Also, under "Options", try "Return to Factory settings" using the MOST option first up and then the ALL option if the "most" one doesn't seem to make a difference. I've often found that when BIAB does something it never used to, "Return to factory settings" solves the problem.
Lastly, is it possible that there might be a setting, or a plugin, on the Audacity track that's causing the volume increase?
Hi all! Pumps2 (and anyone else experiencing this issue) - on the mixer, are your "this song" and "all songs" faders set higher than zero? That's the only way I was able to duplicate this issue.
User Video: Next-Level AI Music Editing with ACE Studio and Band-in-a-Box®
The Bob Doyle Media YouTube channel is known for demonstrating how you can creatively incorporate AI into your projects - from your song projects to avatar building to face swapping, and more!
His latest video, Next-Level AI Music Editing with ACE Studio and Band-in-a-Box, he explains in detail how you can use the Melodist feature in Band-in-a-Box with ACE Studio. Follow along as he goes from "nothing" to "something" with his Band-in-a-Box MIDI Melodist track, using ACE Studio to turn it into a vocal track (or tracks, you'll see) by adding lyrics for those notes that will trigger some amazing AI vocals!
Wir waren fleißig und haben über 50 neue Funktionen und eine erstaunliche Sammlung neuer Inhalte hinzugefügt, darunter 222 RealTracks, neue RealStyles, MIDI SuperTracks, Instrumental Studies, "Songs with Vocals" Artist Performance Sets, abspielbare RealTracks Set 3, abspielbare RealDrums Set 2, zwei neue Sets von "RealDrums Stems", XPro Styles PAK 6, Xtra Styles PAK 17 und mehr!
Add updated printing options, enhanced tracks settings, smoother use of MGU and SGU (BB files) within PowerTracks, and more with the latest PowerTracks Pro Audio 2024 update!
Download and install this to your RealBand 2024 for updated print options, streamlined loading and saving of .SGU & MGU (BB) files, and to add a number of program adjustments that address user-reported bugs and concerns.
Did you know... not only can you download your Band-in-a-Box® Pro, MegaPAK, or PlusPAK purchase - you can also choose to add a flash drive backup copy with the installation files for only $15? It even comes with a Band-in-a-Box® keychain!
For the larger Band-in-a-Box® packages (UltraPAK, UltraPAK+, Audiophile Edition), the hard drive backup copy is available for only $25. This will include a preinstalled and ready to use program, along with your installation files.
Backup copies are offered during the checkout process on our website.
Already purchased your e-delivery version, and now you wish you had a backup copy? It's not too late! If your purchase was for the current version of Band-in-a-Box®, you can still reach out to our team directly to place your backup copy order!
Note: the Band-in-a-Box® keychain is only included with flash drive backup copies, and cannot be purchased separately.
Handy flash drive tip: Always try plugging in a USB device the wrong way first? If your flash drive (or other USB plug) doesn't have a symbol to indicate which way is up, look for the side with a seam on the metal connector (it only has a line across one side) - that's the side that either faces down or to the left, depending on your port placement.
Update your Band-in-a-Box® 2024 for Windows® Today!
Update your Band-in-a-Box® 2024 for Windows for free with build 1111!
With this update, there's more control when saving images from the Print Preview window, we've added defaults to the MultiPicker for sorting and font size, updated printing options, updated RealTracks and other content, and addressed user-reported issues with the StylePicker, MIDI Soloists, key signature changes, and more!
A few excerpts:
"The Tracks view is possibly the single most powerful addition in 2024 and opens up a new way to edit and generate accompaniments. Combined with the new MultiPicker Library Window, it makes BIAB nearly perfect as an 'intelligent' composer/arranger program."
"MIDI SuperTracks partial generation showing six variations – each time the section is generated it can be instantly auditioned, re-generated or backed out to a previous generation – and you can do this with any track type. This is MAJOR! This takes musical experimentation and honing an arrangement to a new level, and faster than ever."
"Band in a Box continues to be an expansive musical tool-set for both novice and experienced musicians to experiment, compose, arrange and mix songs, as well as an extensive educational resource. It is huge, with hundreds of functions, more than any one person is likely to ever use. Yet, so is any DAW that I have used. BIAB can do some things that no DAW does, and this year BIAB has more DAW-like functions than ever."
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