Oh no!! Tell me it's not true: "Render" does not include the Volume Automation Key Frame?
For the Individual Rendered Files? They all do not have the Mutes and lowered volumes that I personally worked on for a total of three days already?
That's exactly the reason why I needed to use the Volume Automation (key frame) of RB: so that I can accurately adjust instrument volumes bar-by-bar, such as muting some instruments ..
you seem to be having so many problems with RB can we ask about your set up?
how much RAM? what processor? what audio interface if any what sound card?
did you take onboard rharv's points about not using RB like BIAB? how are you muting various bars?
are yuo recording mixer moves on individual tracks? are you using volume nodes? are you entering values in the event list of each track using F2?
key frame is a term i'm not familiar with, i do know mixer move, event list volume change, volume node etc but in the context of RB key frame doesn't mean anything to me. the term does not appear in the manual index.
just what are trying to do and how are you doing it? the fact that it does not work when so many of us achieve the mix we want tends to suggest your process is not working - not the program.
and why are you trying to render trakcs? waht do you want to do with them? if you are exporting to another DAW why not use the BIAB plugin to start with? or export the BIAB song direct to the DAW you want to use?
yes rharv i just tried the render to wav files and volume changes are lost but no exceptions occurred. merge audio and midi tracks to stereo wav file works fine which is why i've had no problems. i stay in RB for a final mix and then merge to a wav file for mastering. my mix and mutes work fine.
still a bit confused about the OPs workflow. why mix and finalise in RB then export wav files to another program?
surely better to go straight from BIAB to the DAW of his choice but I don't understand the bit about not seeing which bar he's dealing with.
i'm not sure what he wants to do he can't do in RB. perhaps he can tell us and we can at least get him working happily on his music.
still it's another fix identified. and annoying that something that worked is now broken
Just a side note, check if you are using 'Gain Nodes' instead of 'Volume Nodes'. I've had problems using Gain Nodes during rendering in the past with other builds but no problem with Volume nodes. I use 'Volume Nodes' exclusively now and have had no problems using them with the latest build of Realband 2021 [5] 64 bit.
Just tried this out with RB2019/5 Volume nodes work, gain nodes don't. Don't know when this got broken but gain nodes have worked for me previously, AFAIK I have never knowingly used volume nodes.
I first reported the problem with the gain nodes not working in October 2017 when I was using RB2017 ver7. The help desk told me to use the Volume Nodes as a work around at that time.
Hello Mike, I use Volume nodes on nearly every song I make in Realband and only use them on audio tracks. I don't use any midi tracks so I'm specifically stating that Volume nodes do indeed work for audio tracks. Perhaps you are talking about something else that I don't understand.
yes they record as if they are midi controls in the event list but they do alter the volume of audio tracks
that's how i muted a part of a track and that definitely carried over to a merged stereo file although rendering individual tracks the volume changes didn't work - that was the subject of the OP.
i discovered that volume nodes can be tricky. if you just add a node at the level you want, RB fades down over the whole track from the previous level. instead of muting where you want, it fades down slowly from the previous setting.
if you want bar 4 of a track to mute, you set a node at the existing volume on bar 3, beat 3 , 119 ppq depending on yuor resolution, and the node for the volume you want - zero for mute - at bar 4, beat 1, 0 ppq. same with restoring the level. if you don't set another zero node, the part will fade up to the new node at the desired level.
It does assume a fade, I get that's what they are for .. move the volume from here to hear just like I actually moved the slider; so I can't fault RB on that part. If you want a sudden change you have to enter it.
Seems more to me like an issue that Volume nodes get used on Merge, but Gain Nodes don't .. and apparently the OP is stuck with Gain Nodes at this point. I'd try editing and using the Data Filter to change the CC# to the desired one, but that's just me. In reality, if the default was that this process created Volume nodes and not Gain nodes, it may be better for most users in the long run.
Del learned his desired workflow years ago, and maybe more people would like that as the default. Just a thought
I do not work here, but the benefits are still awesome Make your sound your own!
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