this might seem way way out there and odd but im wondering if a timeout condition is occurring viz casio and bb ie bb is waiting for data ..doesnt get it and thus stops. only pg will know in their coding if a stop condition can occur re the above. maybe midi lag is the issue with cas but not fp.
total!y blue skying it but if fp works with 2024 is there a possibility that the fp transmssion is faster than the casio ? so a lag condition doesnt occur ?
as a crazy experiment check if you have big buffers in bb settings ...check this...then see if reduceing the buffer size.helps. sometimes the silliest things can cause problems.
by the way...and i dont want to get into a big debate over this ..but if your useing pc on board sound chip...ive seen lots of issues helping folks over the years...would recommend a decent low latency asio audio nterface. maybe try out for a week to ensure it works great see rb forum and tips forum for good interfaces. a decent interface will let you set low buffers so you dont get latency which you mentioned up thread.
ps.do you have the net or background programs active while midi recording ? check in task mgr...ie other programs consuming pc resources ? also if you reply by saying but why does cas work with previous years bb versions and not 2024..? a possible answer is maybe 2024 places added demands on pc resources over previous years. but only pg can answer if 2024 consumes more resources.
just some ideas.
om. 🇨🇦. 🇬🇧
Last edited by justanoldmuso; 01/27/2408:26 AM.
my songs....mixed for good earbuds...(fyi..my vocs on all songs..) https://soundcloud.com/alfsongs (90 songs created useing bb/rb.)
if fp works with 2024 is there a possibility that the fp transmssion is faster than the casio ?
ANSWER: Actually I think it would be the opposite because the Roland is 15 years old and the Casio is brand new. The Casio could be too fast or transmitting too much data. Still doesn't quite go along with why Casio works with all earlier versions EXCEPT 2024.
i dont want to get into a big debate over this ..but if your using pc on board sound chip...ive seen lots of issues helping folks over the years...
ANSWER: I have a desktop and laptop. In one system I am using an external audio interface and the other the internal sound card - makes no difference.
Ok given your answers and all the ideas presented in this thread...and bear with me...but heres further thinking...
1..maybe pg can comment if 2024 is consuming more pc resources than preceeding years. if true then possibly other tasks on the pc in total with bb are leading to a resource issue and impacting bb ? check in task mgr eg is net running also ? if so try without the net.
2..now i know what your going to say which is an enigma...ie...BUT...fp works on bb 2024 ! and thats an excellent point....given your point that maybe cas is throwing out more data than fp maybe this in combo with the larger resource useage bb2024 in total is causeing this odd stop situation. ive seen lots of weird things over the years. it would be interesting to investigate how much data per sec is transmitted by cas over midi versus the fp. and get actual figures. in summary it might be just a pc resource issue. ie bb 2024 plus cas consumes more resources than bb2024 plus fp.. but i might be out to lunch on this. out of interest check out size of 2014 bb exe versus 2024 bb exe. ...there might be a clue there. ram useage ?
3..its totally unrelated but interestingly yonks ago i helped someone with a cas...he ended up getting another kbd.
heres a final thing thats bugging me...some people might say 'its gotta be a codeing bug in bb'...but if true why does fp work with 2024 ?
im gonna get a cuppa tea and do more thinking...lol.
best.
om
Last edited by justanoldmuso; 01/27/2410:04 AM.
my songs....mixed for good earbuds...(fyi..my vocs on all songs..) https://soundcloud.com/alfsongs (90 songs created useing bb/rb.)
ok something ive found. running 2024 on a basic song here tssk manager in win is reporting around 2 percent to about 5 percent cpu useage for bbw64 and around 460 mb of ram useage. which varies depending on default synth loaded. in the bb drive itself the exe for bbw64 seems to be around 56mb.. and bb 2024 32 bit is 44mb ? do you concur ?
L2L can you please tell me in 2024 64 bit running for fp connected what your above stats are in win task mgr ? now repeat for casio connected. any big differences in ram or cpu viz fp ? repeat above for 2024 32 bb. does cas work in bb 32 ?? now please repeat for your 2014 version bb. task mgr again. firstly fp then casio connected.. how much pc resources are being consumed ? cpu and ram.
addendum. i assume youve been running bb 64 thru all this. could you try with bb32 exe which comes with 2024 and use with casio connected... does the problem disappear ?
humour me..lol...i hate to be beaten the reasons for above are to assess the possibility of the pc running out of resources. what keeps on troubling me is fp works with 2024 which might lead one logically to conclude there isnt a bug in bb2024. btw as others have said andrew is v good people.
om. 🇨🇦. 🇬🇧
Last edited by justanoldmuso; 01/27/2403:47 PM.
my songs....mixed for good earbuds...(fyi..my vocs on all songs..) https://soundcloud.com/alfsongs (90 songs created useing bb/rb.)
That was a great suggestion, but unfortunately, it did not solve the problem. I don't have to even be playing a single note repeatedly; it occurs (the MIDI recording stops in the middle of the song) when I am playing anything - not even just fast notes.
The MIDI clock rate I believe is 31.25kbits/second. Extrapolating that out, and presuming a start and stop bit are added to the 8-bit byte, this means that a byte transmits in about 320 microseconds, and with the normal MIDI message taking up three bytes, indicates that a complete message is transmitted in less than 1 millisecond (3 x 320 microseconds).
USB will transfer data at a significantly higher data rate again.
So I believe that your issue is not in any way related to the speed of your playing (unless you are exceeding 1000 note events / second ).
You mentioned that the BiaB Stop Recording message is displayed. That message would not normally come from the transmitted MIDI. It would come from within BiaB, usually from the Stop button being pressed on the transport.
Is this the stop message that you see?
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
Delving a little further into MIDI, there are System Real Time messages that include a Start and Stop message which are normally used to control sequencers. Are there any settings on the Casio to instruct it to run as a sequencer or to synchronize an external device?
Could you provide a screen capture of the end of the MIDI data at the point where the unexpected Stop event occurs? (Please make sure that no filters are affecting the displayed data)
Last edited by AudioTrack; 01/28/2401:36 PM.
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
Delving a little further into MIDI, there are System Real Time messages that include a Start and Stop message which are normally used to control sequencers. Are there any settings on the Casio to instruct it to run as a sequencer or to synchronize an external device?
ANSWER: Not that I'm aware, but I am reaching out to Casio about this. There is an internal recorder on the Casio, but it is triggered by pushing an actual physical button that I can assure you is not being pushed.
Could you provide a screen capture of the end of the MIDI data at the point where the unexpected Stop event occurs? (Please make sure that no filters are affecting the displayed data)
Attached is a screenshot of the last MIDI messages before the recording of MIDI stopped and the "Save Recording?" dialogue pop-up box.
Was "MIDI Recording Stops Suddenly And Randomly" ever sorted out after pages n pages of posts ?
No, the issue is still present with BIAB 2024 and I am still working on it with PG Support. We have determined that early versions of BIAB 2014 thru 2019 do not cause this issue. I'm still waiting to test some later versions.
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
Video: Band-in-a-Box 2025 for Windows: Using The BB Stem Splitter!
In this video, Tobin provides a crash course on using the new BB Stem Splitter feature included in Band-in-a-Box 2025® for Windows®. During this process he also uses the Audio Chord Wizard (ACW) and the new Equalize Tempo feature.
Video: Band-in-a-Box® 2025 for Windows®: Using the BB Stem Splitter
Check out the forum post for some optional Tips & Tricks!
Congrats to Misha (Rustyspoon)…downloaded/installed a full Audiophile 2025!
Breaking News!
We’re thrilled to announce that Rustyspoon has made PG history as the very first person to successfully complete the download and install of the full Band-in-a-Box 2025 Windows Audiophile Edition (with FLAC files)—a whopping 610GB of data!
A big shoutout to Rustyspoon for stepping up to be our test "elf!"
With the launch of Band-in-a-Box® 2025 for Windows, we're adding new videos to our YouTube channel. We'll also share them here once they are published so you can easily find all the Band-in-a-Box® 2025 and new Add-on videos in one place!
Whether it's a summary of the new features, demonstrations of the 202 new RealTracks, new XPro Styles PAK 8, or Xtra Styles PAKs 18, information on the 2025 49-PAK, or detailed tutorials for other Band-in-a-Box® 2025 features, we have you covered!
Band-in-a-Box® 2025 for Windows is here, packed with major new features and an incredible collection of available new content! This includes 202 RealTracks (in Sets 449-467), plus 20 bonus Unreleased RealTracks in the 2025 49-PAK. There are new RealStyles, MIDI SuperTracks, Instrumental Studies, “Songs with Vocals” Artist Performance Sets, Playable RealTracks Set 4, two new sets of “RealDrums Stems,” XPro Styles PAK 8, Xtra Styles PAK 19, and more!
Special Offers
Upgrade to Band-in-a-Box® 2025 with savings of up to 50% on most upgrade packages during our special—available until December 31, 2024! Visit our Band-in-a-Box® packages page for all the purchase options available.
2025 Free Bonus PAK & 49-PAK Add-ons
We've packed our Free Bonus PAK & 49-PAK with some incredible Add-ons! The Free Bonus PAK is automatically included with most Band-in-a-Box® for Windows 2025 packages, but for even more Add-ons (including 20 Unreleased RealTracks!) upgrade to the 2025 49-PAK for only $49. You can see the full lists of items in each package, and listen to demos here.
If you have any questions, feel free to connect with us directly—we’re here to help!
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.