PG Music Home Forums PG Music Product Forums Band-in-a-Box for Windows Band in a Box 2025 stutters when I play MIDI [Resolved]

Hello,

I just bought Band in a Box 2025 and installed it on my Dell XPS 18 PC with Windows 10 which is connected to my Clavinova CVP 307 piano which serves as both a master keyboard and a MIDI expander.

After working on the same installation with Band-in-a-Box 2020 without (almost) any problems for 5 years, I am now experiencing a serious problem with Band in a Box 2025: Band in a box works normally when I start a song, but as soon as I start playing on my piano with MIDI In enabled, it starts to stutter, stop, resume, re-stutter, etc.

Since everything worked fine with my previous versions of Band in a Box (2006, 2008, 2010, 2015 and 2020), I first thought that the problem came exclusively from the 2025 version of Band in a Box.

But the situation is probably more complicated, because I also tried by connecting my PC with Band-in-a-Box 2025 to a Yamaha P45 piano, and there, Band in a box worked perfectly even when I played on my piano and recorded myself in MIDI!

I deduce that the problem comes from the relationship between Band-in-a-Box 2025 and my Clavinova CVP 307: a file or a setting of Band-in-a-Box 2025 that would not work with my CVP 307? It is true that my CVP 307 is a rather old machine (it was released in 2004).

On the other hand, this is not a problem specifically related to Windows 10 because I tested my version 2025 of Band in a Box with a PC using Windows 11 connected to my Clavinova CVP 307 and I have the same problem when I play with MIDI In.

Do you know if other users have encountered a similar problem? Do you have any idea what can happen?

Thanks in advance for your answers.

Hi. I am by far not an expert on tis particular topic, but I'll offer a thought that may not help solve it but might help where not to look.

My wife has an even older Clavinova than yours and it works fine into BIAB, although it isn't practical for me to test it now with version 2025. MIDI is such a simple signal over a slow serial port that I suspect that is not the problem here. The structure of MIDI signals has not changed in all that time (MIDI 2.0 isn't really implemented just yet). Nor to my knowledge has anything about handling MIDI changed from Windows 10 to 11, as you tested.

If you can get users Gary Curran or RHarv to see your post, that might help. And if it does turn out to be a problem in version 2025, we can alert the developers.

Thanks Matt for your reply.
I am also very surprised that the problem apparently comes from the MIDI signal input.
But I have made multiple tests before realizing that the problem only appeared when I activated the MIDI Input Driver in the Options menu: tests on the PC, on the Windows version, on the keyboard, on the digital audio interface, etc.
In addition, I have been in contact for a month with the Band-in-box support team, and so far they have not found the origine of the problem.
That is why I would be very interested to know if anyone with an old Clavinova CVP (CVP 307/309 or earlier) has already worked with Band in a Box 2025 and whether or not they have encountered a problem similar to mine!

I see from the picture that there’s another variable: you have the French edition.

Could you describe your MIDI connection? From MIDI out on the Clavinova, or did that early a model have USB? Into what (such as a Focusrite Scarlett etc)?

I usually connect my Clavinova CVP 307 to my Dell XPS 18 PC via a Roland Duo Capture EX digital audio interface: in this case, I connect the MIDI ports of the piano to the MIDI ports of the interface, and I connect the USB-A port of the interface to a USB-B port of the PC.

But I also tested by connecting my Clavinova CVP 307 directly to my Dell XPS 18 PC: in this case, I connect the "USB to Host" (USB-A) port of the Clavinova to a USB-B port of the PC.

In both cases, I have the same stuttering problem with Band-in-a-Box 2025 that I did not have before with Band-in-a-Box 2020 as soon as I play on my Clavinova with the MIDI Input Driver enabled.

You have been very thorough. Not knowing what level of support you’ve already received, I’m referencing this thread to the developers to be sure it is seen.

Try to make you Audio Midi Settings look like this as much as you can. My keyboards work fine in BIAB.

Open the MIDI Monitor (Window menu) and filter to show only MIDI input. After playing for a while, save as a text file and paste some of it here - this might have some clues.

Thanks Matt !

Thanks DrDan
Here are two screenshots of my MIDI/Audi Drivers Setup window
1. When I connect my Clavinova CVP 307 directly to my PC and when I use the CVP 307 as master keyboard through MIDI In and expander through MIDI Out :
2. When I connect my Clavinova CVP 307 to my PC via my digital audio interface Duo Capture EX and when I use the CVP 307 as master keyboard through MIDI In and expander through MIDI Out :
Do you see anything wrong?
PS: I have the same problem of stuttering of Band in a Box 2025 when I use the VSTi/DXi synth option and play on my CVP 307 with MIDI input activated

Thanks Andrew!
I will do that tomorrow and come back to you !

In the first screen shot, why are there two entries for the Clavinova? Is it possible there are two drivers loaded? You might want to look in Device Manager in Windows and disable one of these.

Hello Andrew,

I failed to make exactly the requested recording:

- I made and saved a first piano recording with the MIDI Monitor enabled but I forgot to select only MIDI Input. I'm attaching an excerpt below anyway

- Then I couldn't reopen the MIDI Monitor window: I got an error message 121 (screenshot below), and I had to close and reopen BiaB to be able to make another recording with the MIDI monitor enabled/

- Finally when I selected only MIDI Input ont he MIDI Monitor and made a new recording (only 28 notes were recorded before Biab stuttered and stopped), the monitoring window remained empty! However, the notes sent in MIDI from my keyboard were recorded as seen on the score (screenshots below)!

For me, the mystery remains!

Stéphane

Extract from the MIDI Monitoring:
323 10429 1 99 26 00 Note On ($9x) 10 Pitch = D 3 Velocity = 0
324 10429 1 99 33 00 Note On ($9x) 10 Pitch = Eb 4 Velocity = 0
325 10429 1 99 24 00 Note On ($9x) 10 Pitch = C 3 Velocity = 0
326 10459 1 99 24 5A Note On ($9x) 10 Pitch = C 3 Velocity = 90
327 10471 1 99 26 20 Note On ($9x) 10 Pitch = D 3 Velocity = 32
328 10471 1 99 33 15 Note On ($9x) 10 Pitch = Eb 4 Velocity = 21
329 10534 1 B0 40 00 Control Change ($Bx) 1 CC Type = #64 Sustain Pedal CC Value = 0
330 10534 1 B0 7B 00 Control Change ($Bx) 1 CC Type = #123 All Notes Off CC Value = 0
331 10559 1 B1 7B 00 Control Change ($Bx) 2 CC Type = #123 All Notes Off CC Value = 0
332 10559 1 B9 7B 00 Control Change ($Bx) 10 CC Type = #123 All Notes Off CC Value = 0
333 10559 1 B9 40 00 Control Change ($Bx) 10 CC Type = #64 Sustain Pedal CC Value = 0
334 10559 1 B2 7B 00 Control Change ($Bx) 3 CC Type = #123 All Notes Off CC Value = 0
335 10559 1 B5 7B 00 Control Change ($Bx) 6 CC Type = #123 All Notes Off CC Value = 0
336 10559 1 B6 7B 00 Control Change ($Bx) 7 CC Type = #123 All Notes Off CC Value = 0
337 10559 1 B7 7B 00 Control Change ($Bx) 8 CC Type = #123 All Notes Off CC Value = 0
338 10559 1 B0 7B 00 Control Change ($Bx) 1 CC Type = #123 All Notes Off CC Value = 0
339 10559 1 B0 40 00 Control Change ($Bx) 1 CC Type = #64 Sustain Pedal CC Value = 0
340 10559 1 C3 42 Program Change ($Cx) 4 Program # = 66
341 10559 1 C3 00 Program Change ($Cx) 4 Program # = 0
342 10573 1 B0 40 00 Control Change ($Bx) 1 CC Type = #64 Sustain Pedal CC Value = 0
343 10573 1 B0 7B 00 Control Change ($Bx) 1 CC Type = #123 All Notes Off CC Value = 0
344 10633 1 91 1D 00 Note On ($9x) 2 Pitch = F 2 Velocity = 0
345 10633 1 99 24 00 Note On ($9x) 10 Pitch = C 3 Velocity = 0
346 10633 1 99 26 00 Note On ($9x) 10 Pitch = D 3 Velocity = 0
347 10633 1 99 33 00 Note On ($9x) 10 Pitch = Eb 4 Velocity = 0
348 10633 1 B3 7B 00 Control Change ($Bx) 4 CC Type = #123 All Notes Off CC Value = 0
349 10633 1 B3 40 00 Control Change ($Bx) 4 CC Type = #64 Sustain Pedal CC Value = 0
350 10633 1 BA 7B 00 Control Change ($Bx) 11 CC Type = #123 All Notes Off CC Value = 0
351 10633 1 BA 40 00 Control Change ($Bx) 11 CC Type = #64 Sustain Pedal CC Value = 0
352 10633 1 BB 7B 00 Control Change ($Bx) 12 CC Type = #123 All Notes Off CC Value = 0
353 10633 1 BB 40 00 Control Change ($Bx) 12 CC Type = #64 Sustain Pedal CC Value = 0
354 10633 1 B7 7B 00 Control Change ($Bx) 8 CC Type = #123 All Notes Off CC Value = 0
355 10633 1 B7 40 00 Control Change ($Bx) 8 CC Type = #64 Sustain Pedal CC Value = 0
356 10633 1 B0 7B 00 Control Change ($Bx) 1 CC Type = #123 All Notes Off CC Value = 0
357 10633 1 B0 40 00 Control Change ($Bx) 1 CC Type = #64 Sustain Pedal CC Value = 0
358 10633 1 BC 7B 00 Control Change ($Bx) 13 CC Type = #123 All Notes Off CC Value = 0
359 10633 1 BC 40 00 Control Change ($Bx) 13 CC Type = #64 Sustain Pedal CC Value = 0
360 10633 1 BD 7B 00 Control Change ($Bx) 14 CC Type = #123 All Notes Off CC Value = 0
361 10633 1 BD 40 00 Control Change ($Bx) 14 CC Type = #64 Sustain Pedal CC Value = 0
362 10633 1 B0 7B 00 Control Change ($Bx) 1 CC Type = #123 All Notes Off CC Value = 0

Screenshots

Hello Matt,

I have no idea why my Clavinova CVP appears twice in the MIDI Output Driver window, but in the Device Manager I only see one driver (screenshot herunder).

That said, my Biab stuttering problem already existed even when I only saw one line for the CVP driver, and the problem also appears when I use a VSTi.

Lazy, I saw you pictures of the configuration of the keyboard and it is NOTHING like mine. I had asked you to attempt to reproduce my configuration. The reason why is because mine work perfect. I just tried to record midi from the keyborad and all worked as intended. I have two keyboards I (only 1 is presently on, so you do not see the other in my picture. If I set my configure similar to yours I get nothing! I would be glad to show you via a video, but it is so simple if you just set the buttons right as I show.

Maybe I don't know what you are trying to do. Both my keyboards are Midi Controllers and do not have their own sounds. That is what BIAB can handle. You are not trying to play your internal keyboard synth? As best I know, that won't work. BAIB routing is very simple. The keyboard is routed only to the "thru" track unless you record then it can be set to the melody or soloist tracts. You can not sent the midi into BIAB and sent the MIDI out to you keyboard. Again, best as I know. Fact is I never record in BIAB. I save that for the DAW

LB and all...

i may be wrong and pg will need to confirm this but error code 121 as far as i understand is a win error code regarding connections eg networking or a physical connection ????
(see google as im not confident re this....)

which brings up a suggestion which i suggest pg might consider.
as there are all sorts of win error codes.

maybe in the bb (and rb) user manuals have a list of COMMON win error codes that could be displayed in bb PLUS how to solve if possible.
ie dont just display the error code eg 121 in this case BUT ALSO a suggested solution in the pg pop up panel for non tech folks ??

just an idea. i suspect in this case its a set up or connection issue re the external midi keyboard ? but maybe i'll get egg on my face ...lol.
anyhoo thats my best shot.

ps...i notice that 121 code has also popped up in other developers apps.

om

Windows Error Code 121 (0x79 hex) is a semaphore timeout error. That means a flag was set awaiting some other code to complete, and it didn't complete in time, and the error event was triggered.

I suspect that this might even just be a data looping issue. The MIDI data that BIAB is receiving is being sent back to the MIDI keyboard, which in turn sends it back to BIAB.
Change the MIDI routing to use a VSTi as per Dr Dan's suggestion and see if that changes the status.

I'm not sure the orange message is related to your MIDI input problem. It might be indicating that a window is not on top when it should be, but let us know if you see it again.

Go to Options | Preferences | MIDI options and enable MIDI Thru (if not already) and then open the MIDI Monitor again and try playing your keyboard. You should see data there regardless of whether BiaB is playing/recording. Also, if you watch the 'pianos' tab of the Mixer you should see notes light up there .... do you?

Hello DrDan,

It's normal that my configuration is not identical to yours, because my keyboard is a Clavinova CVP that produces its own sounds, and I use it both as a master keyboard AND as an expander.

That's why I don't check the VSTi/DXi synth option: with my Clavinova CVP, I don't need to use virtual instruments.

That being said, I still have the same problem when I check the VSTi/DXi option and use my virtual instruments (for example Garritan JABB 3): when I play on my keyboard with the MIDI Input Driver enabled, Band-in-a-Box stutters (stops, resumes, etc.).

But I'm sure that my MIDI/Audio Drivers Setup window setting is not the source of the problem: since 2013, I have used Band in a Box versions 2010, 2015 and 2020 with my CVP as a MIDI keyboard and as an expander and I have never encountered the problem that I have today with version 2025.

But maybe version 2025 of Band-in-a-box no longer handles MIDI inputs like previous versions, or it requires a more powerful PC configuration (I still have 8 GB of RAM!) or the Ultrapack version that I bought on HDD is corrupted ...

For now, I have no leads!

Hello AudioTrack,

Thanks for this suggestion. But I have the same problem when I don't use my Clavinova as an expander and I use a VSTi instead (for example Garritan JABB3): as soon as I play with the MIDI Input Driver enabled, BiaB stutters (sometimes after a few seconds, sometimes after a few dozen seconds).

Of course, I can play without the MIDI Input Driver enabled and enjoy BiaB's arrangements as backing tracks, but of course, I can't record myself in MIDI anymore!