This happened when I upgraded to 2018. I have old version still and it is ok there. I use standard jazz 1 3 1234 count in. I displayed the metronome and that seems ok. It just does not make a sound on beat 1. I have installed the latest patches. This happens on a new blank song as well as existing songs. Thanks.
Just so you know you’re not crazy, I get this too.
I’m not sure what causes it. It’s not serious enough for me to have spent time, but now I will. I suspect it’s some setting in Preferences, Count-in/Metronome that you and I have in common. Can you post back and tell me what your setting is?
You play alto?
BIAB 2025 Win Audiophile. Software: Studio One 7 Pro, Swam horns, Acoustica-7, Notion 6, Song Master Pro, Win 11 Home. Hardware: Intel i9, 32 Gb; Roland Integra-7, Presonus 192 & Faderport 8, Royer 121, Adam Sub8 & Neumann 120 monitors.
Thanks, glad I'm not losing it, at least about this I have the count set as 1-3- 1234. It is same setting I used in previous version. I play tenor, alto, sop.
Here are my settings. These are not particularly based on thorough testing; I just happen to have these. At the moment I AM getting beat one of 1,3, 1234.
Allow lead in bar - checked 1-bar lead in - NOT checked Play lead in - checked Lead in type pulldown - Count-in Audible lead in - checked Volume 64 Instrument - Open hi conga 63 Pattern - 1-3 1234 Smart lead in - NOT checked
Tell me if any of your settings are different.
Also, what is the tempo and style of your song?
BIAB 2025 Win Audiophile. Software: Studio One 7 Pro, Swam horns, Acoustica-7, Notion 6, Song Master Pro, Win 11 Home. Hardware: Intel i9, 32 Gb; Roland Integra-7, Presonus 192 & Faderport 8, Royer 121, Adam Sub8 & Neumann 120 monitors.
Same as yours but I think it has something to do with midi settings. I checked VSTi/Dxi and No GM2. Now it will play all the beats but it does not matter what instrument I select - it is always a sidestick. Temp 190 JazzBop.
I'm remembering one other area: there is a setting to coordinate the timing of MIDI and audio.
This would be different on everyone's individual setup, with no way to really compare settings. In other words, if the MIDI must be adjusted to sound early, it might get clipped. On the other hand, you can set the count-in to be played by the B section of the RealDrums, if I recall correctly.
I use an external MIDI synth, so I can't help with any differences caused by using a VSTi.
Anybody else have this problem?
Last edited by Matt Finley; 03/03/1809:37 AM.
BIAB 2025 Win Audiophile. Software: Studio One 7 Pro, Swam horns, Acoustica-7, Notion 6, Song Master Pro, Win 11 Home. Hardware: Intel i9, 32 Gb; Roland Integra-7, Presonus 192 & Faderport 8, Royer 121, Adam Sub8 & Neumann 120 monitors.
Yes! One my main performing system, the first beat of the count-in invariably is lost. Not always, but mostly. I sounds as though the count in starts just before the audio-sub-system is activated. Sometimes I hear what sounds like the very end of that first beat, playing quite softly. That system uses the Focusrite 18i20 for the audio.
To boot, that same system often plays a single side-stick (rim shot) after the end of the song. Most annoying.
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! One my main performing system, the first beat of the count-in invariably is lost. Not always, but mostly. I sounds as though the count in starts just before the audio-sub-system is activated. Sometimes I hear what sounds like the very end of that first beat, playing quite softly. That system uses the Focusrite 18i20 for the audio.
To boot, that same system often plays a single side-stick (rim shot) after the end of the song. Most annoying.
Hmm. That ending shot may be the beginning missing click. We had a go-around about this many years ago.
BIAB 2025 Win Audiophile. Software: Studio One 7 Pro, Swam horns, Acoustica-7, Notion 6, Song Master Pro, Win 11 Home. Hardware: Intel i9, 32 Gb; Roland Integra-7, Presonus 192 & Faderport 8, Royer 121, Adam Sub8 & Neumann 120 monitors.
In that case, the Instrument, Pattern, and Volume settings for the count-in won't be relevant, they only apply to MIDI drums.
Which audio driver type are you using? I've tried with tracks frozen and unfrozen, with MME, ASIO, and WAS, and still get a full count-in, but if everyone with this problem is using the same type, that might be a clue.
I'd also be interested in knowing whether changing audio driver types makes a difference when this problem occurs.
The next time this happens to anyone, if they could make a note of whether the VU meter on the mixer for the Drums track shows a signal for the missing count-in beats, that'll tell us if they're generating but can't be heard, or if they're not generating at all.
If anyone notices any other details, like specific styles having this issue more than others, please let me know. I'll keep trying to replicate it on my end.
As i use ASIO, never used WAS, i didn't know about anything wrong. But if needed, PM me your frozen file, or ask for my normal email (some of you have it i guess), and i'll test it in the 3 modes; you guys always jump in to help everybody. The only 'bug' i noticed happens rarely, is that audio (Realdrums) and midi are out of sync with 512 BTW, on first start after loading a song, and it seems happening sometimes later at a bar measure count change. Regenerating fixes that permanently. ... F
It seems that this is not isolated, and many users have reported. I've tried MME, ASIO and WAS, unfreezing, regenerating, changing endings etc, all without change. All of the songs use RealDrums.
I've sent you more information on this with demonstrations and further details in the testing area.
Please let me know of any further tests or assistance I might provide.
I'm guessing (hoping?) that PG Music will look seriously at the way the count-in works, especially liberating it from a global setting. I remain (long time) optimistic. Maybe this could finally resolve the issue.
Trevor
Last edited by VideoTrack; 03/18/1812:55 AM. Reason: Added optimism comment about how the count-in currently works
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
Any update on this issue? I have this problem as well and it's a big turn off. In 4/4 mesure, most of the time I get 3 count in instead of 4 before the song starts. This is very frustrating!
Any update on this issue? I have this problem as well and it's a big turn off. In 4/4 mesure, most of the time I get 3 count in instead of 4 before the song starts. This is very frustrating!
This is like a 5 year old thread being revisited. I'm not sure if this helps but there are options for the count-in such as the two identified here. Could either of those be selected?
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
I just upgraded to 2024. Did not had that problem with 2019 version.
Try this as a starting point. With one of the problem songs loaded, Go to Song settings ( <Ctrl> N ) Place a tick in this check box, press OK and regenerate the song. See if the problem persists.
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
I have this problem with almost every style we use. I can't remember when it started, but certainly on 2023 and now on Audiophile 2024.
Here's one now: _FUNKMED.STY. Funk w/ Vintage Electric Piano.
Doesn't seem to matter what settings I change - 1-bar count-in same as two-bar. Audio driver settings don't matter - I tried two different sound cards.
I just tried _FUNKMED and I definitely had the drums counting beat 1. The image below shows my settings.
I'm using build 1109. This hasn't yet been released to the public but Andrew made it available a few days ago. So if you'd like to install it and try it...
A few more observations that I don't understand...
- On the Count-in dialog box, the "Instrument" setting does nothing. Nothing changes when I make changes to it. Why? I can choose any sound in the list and it has no effect
- If I Mute the Drum Track, the Count-in sound is different than otherwise and there is NO quiet beat or cut off beat - all the count-in beats sound the same. (Must also have "Lead-in drum count if drums muted" checked)
- The above is TRUE also when I UN-check "Audible Lead-in", but without the Drum Track Muted, there is no count-in - it's silent. With "Audible Lead-in" checked and Drum Track un-muted, I hear the count-in from the drum track with the missing or quiet first count.
Seems like "Audible Lead-In" makes the count-in come from the realdrums and muted drums causes the count-in to be some mystery count-in sound that works properly. The Instrument setting does nothing.
I would have figured after all this time, this would be fixed, so maybe I'm doing something wrong - just can't figure it out.
The only trick I have found so far, that is not a great workaround really, is to mute the drum track and re-add the drums to one of the Utility Tracks and un-Check "Audible Lead-In" and "Lead-in drum count if drums muted" checked. Now I get the mystery count-in sound, but there are no cut off or quiet beats. The problem with this workaround is that any Chord or Bar settings affecting drums have to be redone. I have already had to do this to one song that used a Loop instead of drums - worked fine in 2023, but in 2024, there was no count-in at all without making the changes I have described, re-adding the loop into Utility track and then muting the original Loop, then fixing all the Chord settings - PITA!
I'm trying to grasp the ramifications of doing this for all our songs that have a "broken" count-in. Would be way easier if this entire count-in dialog made sense and worked correctly.
I just tried _FUNKMED and I definitely had the drums counting beat 1. Regards, --Noel
Thanks, I will try this and post back. Are you hearing the first count-in beat at the same volume as the rest? I do hear it, but it is very quiet, then the next count is I expect it to be; very audible.
Thanks, I will try this and post back. Are you hearing the first count-in beat at the same volume as the rest? I do hear it, but it is very quiet, then the next count is I expect it to be; very audible.
Try this and see if it makes a difference: Song Settings (<Ctrl>N ), and disable fast generation:
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
On the Count-in dialog box, the "Instrument" setting does nothing. Nothing changes when I make changes to it. Why? I can choose any sound in the list and it has no effect
The choice of instrument works for MIDI instrument. With Realdrums, the count-in instruments are preset. If you choose a MIDI-only style and if the drum track is "green" (which indicates that Realdrums are present), then right-click on the Drum track in the Mixer and choose "Force drums track to MIDI drums", you'll be able to try out the instruments. Make sure to regenerate after selecting this option, though, and then regenerate each time after a change is made. The various settings that you put in place simply tell BIAB how you would like it to organise the backing track when it is generated. With this in mind, the final step after any change whatsoever is usually "Regenerate".
As the image above shows, when you have MIDI drums in place, the track will be yellow.
BIAB's colour coding system... yellow = MIDI, green = audio (Realdrums, Realtracks), light blue = MIDI Supertrack.
What would you like to have happen? Maybe someone on here knows how to achieve what you are after and they will be able to jump in and help.
Regards, --Noel
All I'm after is a consistent count-in no matter what style I use. I think NO count-ins for a style with a loop, for example _HOPHORN.STY Hip Hop Beat w/ Horns, is a 2024 bug - new to me after this update to 2024 (any build). The problem with the first count on Real Drum styles being quiet or silent is an older issue that nothing I have tried, other than the convoluted workaround I outlined above, works to fix the count-in.
The 1109 build did not affect or improve on any of these issues.
If you can play either of those styles and hear a count-in with each hit being the same volume, that's much different from what I'm getting and would love to know how to fix it.
I've attached a jpeg of a recording of what I typically hear for a count-in. Notice how low the level is for the initial hit - so quiet, some would not hear it at all.
Thanks, I will try this and post back. Are you hearing the first count-in beat at the same volume as the rest? I do hear it, but it is very quiet, then the next count is I expect it to be; very audible.
Try this and see if it makes a difference: Song Settings (<Ctrl>N ), and disable fast generation:
I don't think that has worked for anyone.
Changing the audio interface and ASIO driver doesn't do anything. Changing the various settings in the Count-in dialog doesn't help. Changing the processing quality in the ASIO driver doesnt help. I have not found any RealTrack of RealDrum preference settings that help.
I am curious to know if anyone who has ever experienced this issue has solved it? And I'm starting to think that not everyone experiences it - that really quiet first count-in hit?
Thanks for the graphic, Bullmoon. That helps heaps.
Now that I can see what you mean, I can reproduce it. Using the style _FUNKMED.STY, when I drag the drum track to Reaper, it's easy to see from the wav file that the first count is significantly quieter than the other counts.
I'll report this to the development team for you and I'll refer them to your posts.
I know that this is a work around, but hopefully it will allow you to solve the problem while waiting for PG Music to address it.
1) Enter into Audio Edit (#1 on the image below). 2) Select the Drums track (#2). 3) Activate the volume nodes (#3) 4) Enter three nodes as shown on the image so that the volume of beat 1 is increased and then returned to normal volume before the second drum note (#4). (The nodes can be positioned by dragging them vertically up and down the screen.)
Note: The drums for _FUNKMED.STY are stereo. It's only necessary to adjust the volume of one channel. The second channel will update automatically.
An alternative approach (also using Audio Edit) would be...
1) Enter Audio Edit. 2) Activate snap (#1). 3) Select the Drums track (#2) 4) Zoom in on the waveform view using the mouse's scroll. 5) Drag across beat 1 and a regions after it (#3). 6) Select "Amplify" from the drop-down "Edit" menu. 7) Enter a value between 3 and 6 when the option appears.
What I have also found is the same thing happens with exporting to an audio file. The exported file is trimmed at the beginning. I think the way things are being rendered, to a file or for playback, the rendering is partially chopping off the first beat or not ramping up in time to catch it. My guess is that some styles have enough samples ahead of the audio to not get cut off whereas others edited more tightly get cut off. But I really have no idea how the rendering engine works - just a guess.
What I should do is test an export with no count in to see if any of the band is cut off on the first beat, or if the issue is only with count-ins. I'll try this out later when I get a chance.
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.
We’re excited to introduce the new Band-in-a-Box iOS app, designed to enhance your music creation. The Band-in-a-Box iOS app is the perfect companion to your desktop version, giving you the freedom to sketch out ideas wherever you are and develop them further when you're back at your workstation. Now, you can create, play, generate, and transfer songs seamlessly between your iOS device, and desktop.
Key Features:
- Easily Create and Play Songs – Build and play songs effortlessly on your device.
- MIDI and RealTracks/RealStyles Support – Generate MIDI tracks and RealTracks/RealStyles right on your iPhone or iPad (RealTracks/RealStyles require an internet connection).
- Notation Support – View chord sheets, professional notation, tab, and drum notation for all tracks.
...and more!
Update your Band-in-a-Box® 2025 for Windows® Today!
If you’ve already purchased Band-in-a-Box® 2025 for Windows®, great news—a new update is now available! This update introduces a handy new feature: a vertical cursor in the Tracks window that shows the current location across all tracks, and more.
Video: Band-in-a-Box® 2025 for Windows®: Boot Camp: The AI Lyrics Generator
With Band-in-a-Box 2025® for Windows®, we've introduced an exciting new feature: the AI Lyrics Generator! In this video, Tobin guides you step-by-step on how to make the most of this new tool.
Band-in-a-Box® 2025 for Windows®: Boot Camp: The AI Lyrics Generator video.
Video: Band-in-a-Box® 2025 for Windows®: Using VST3 Plugins
Band-in-a-Box 2025® for Windows® now includes support for VST3 plugins, bringing even more creative possibilities to your music production. Join Simon as he guides you through the process in this easy-to-follow demonstration!
Video: Band-in-a-Box® 2025 for Windows®: Using VST3 Plugins
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.