I have 9 choruses in my 30 bar song yet when I go to record a MIDI solo the program just stops in the middle of my solo, in some random spot, asks if I want to save the MIDI file. Sometimes it doesn't even make it through the first chorus, other times it will let me go for a few choruses but never makes it through to even 1/2 way through the song. Running the latest version in Windows 11. Any help is appreciated as BIAB is unusable like this.
One issue is the song has too many bars. 30 bars times 9 choruses equals 270 bars. Band-in-a-Box has a maximum bar limit of 256 bars when all the instrument tracks are set for normal time. When an instrument track is set for half, double or triple time the maximum bar limit is less than 256 bars. As a test, try reducing the number of choruses to 8 or 7.
That's a good point, Jim. I never use multiple choruses so I'm not fully aware of their limitations. I know that it's certainly possible to use "Number of choruses" to create a backing that's longer than 256 bars since only the first chorus is the one that is restricted and the others are repetition of that chorus. I suspect that the 256 bar restriction would certainly be a factor during the recording process, though, because the melody is not linked to just the first chorus and so it is not repeated like a chorus.
The problem has not been resolved. I am working with support but have made no progress. I am running 2024 Build 1109. I have created a NEW SONG of 10 measures and 3 choruses. Real Tracks Bass and Drums only. Recording MIDI to the Melody channel or Soloist channel - it doesn't matter which channel I use. At random, the MIDI recording just stops in the middle of the song (never the same place twice). I am running a Casio PX-S5000 through USB as a MIDI controller. I have made sure the computer will not "put to sleep" the USB ports. There is no rhyme or reason as to when it will stop recording MIDI data. Sometimes stopping when less than 100 notes are played and sometimes after 900 notes are played. It is totally random. I have tried this on two computer systems using many different songs with the same results. I can use the 10 year-old BIAB 2014 running from the USB hard drive it was supplied to me on from PG Music in 2014 and this causes no problems. Very perplexing (and frustrating). There is an error message that pops up whenever I run BIAB 2024 and support has not been able to debug this. I've attached a screenshot of the pop-up error message.
1) I am running 2024 Build 1109. (answers previous question about version) 2) I have created a NEW SONG of 10 measures and 3 choruses. (Eliminates theory of exceeded 256 limit) 3) Real Tracks Bass and Drums only. 4) Recording MIDI to the Melody channel or Soloist channel - it doesn't matter which channel I use.
Results: At random, the MIDI recording just stops in the middle of the song (never the same place twice).
Expected Results: MIDI does not stop recording.
Background Information: (to prove legit setup and issue is new to 2024) a) I am running a Casio PX-S5000 through USB as a MIDI controller. b) I have made sure the computer will not "put to sleep" the USB ports. c) I have tried this on two computer systems using many different songs with the same results. d) I can use the 10-year-old BIAB 2014 running from the USB hard drive it was supplied to me on from PG Music in 2014 and this causes no problems. e) There is an error message that pops up whenever I run BIAB 2024, and support has not been able to debug this. I've attached a screenshot of the pop-up error message.
I am just trying to get someone on this forum to confirm your issue. You've supplied a lot of good information in your last post quoted here I'm going to turn it into a standard step to repeat form. --------------------------------------- Steps for FORUM MEMBERS to Reproduce the Issue: 1) Created a NEW SONG of 10 measures and 3 choruses, using Real track Bass on track (1) and Real Drums on track (3) 2) Recording MIDI to the Melody channel or Soloist channel. --- Settings = Start from bar one chorus one, --- Audio = None, --- Filters = default --- MIDI output is a VST
Results: MIDI stop recording in random spots. Expect: MID does not stops recording. ---------------------------------------
Can anyone in this forum confirm the issue?
UPDATE: Following the above steps, it could not replicate the issue sing WAS drivers and MS GS waves. Other pieces of data that need to be defined. - In the Start from bar one chorus one, correct? A picture would be nice. - You have record audio to none correct? - What are your midi filter settings? A picture would be nice. - For your midi output are you sending it back to your Casio sound module, or are you sending it to an internal VST? If internal which?
Last edited by jpettit; 01/23/2404:34 PM.
Studio One (latest version), Win 11 23H2 , i9 -10940X 3.3 GHz, 32GB Mem, a 4K 40" monitor, PreSonus Studio Live III Console as interface/controller. secondarily test on Reaper, Cakewalk, and S1 on Surface Pro 3 Win 10 (latest versions).
1. In the Start from bar one chorus one, correct? - YES. I am starting from bar one - the start of the song. 2. You have record audio to none correct? -CORRECT. Record to Audio = NONE 3. What are your midi filter settings? A picture would be nice. - See attached Screen Capture 4. For your midi output are you sending it back to your Casio sound module, or are you sending it to an internal VST? If internal which? - MIDI output going to Pianoteq Version 8.2 internal VST or Synthogy Ivory. It doesn't matter which VST plug-in as they all create the error. - Audio Output to computer soundcard ASIO4ALL driver.
Answers to your questions are in BOLD above. I have created a new test song, 32 bars and 3 choruses.The same problem still exists when I record MIDI. The program stopped at random points (see screen captures). When I click on "OK - KEEP TAKE" the song continues to play from where it stopped, but without recording MIDI or the error box with ACCESS VIOLATION will pop-up (see screen shot). I have attached the error messages and my MIDI/Audio settings to this message.
Ok thanks I will update the steps to replicate. The first thing they jumped out at me is you're using ASIO and you're using ASIO4All. That can throw a monkey into the replication process. Can you try your test setting that audio drivers to WAS?
Studio One (latest version), Win 11 23H2 , i9 -10940X 3.3 GHz, 32GB Mem, a 4K 40" monitor, PreSonus Studio Live III Console as interface/controller. secondarily test on Reaper, Cakewalk, and S1 on Surface Pro 3 Win 10 (latest versions).
Ok thanks I will update the steps to replicate. The first thing they jumped out at me is you're using ASIO and you're using ASIO4All. That can throw a monkey into the replication process. Can you try your test setting that audio drivers to WAS?
I tried testing using WAS audio drivers - FAIL. The same thing happened. I was actually able to get through the song once, but then on the second time through it just stopped the MIDI recording at a random spot. I also continue to get the ACCESS VIOLATION pop-up error on start-up of BIAB even when I switched to have it start with WAS instead of ASIO. Back to the drawing board...
Please try MME, I think you will than me. Oh and be sure to try Return to Factory Settings.
Well I'll give you this much, it DID let me record all the way through the song without stopping as it had, but the LATENCY is absolutely atrocious!! The program is completely unusable with this amount of latency. There has to be another solution than to use MME
Another thing they would help out is if people reading this thread would try the simple two-step test and reply with it’s working OK for me or I can replicate.
This data points us to your set up vs. a general bug.
There’s probably a dozen variables involved with this problem, so it’s a game of process of elimination.
What are the specs of your system? It’s a good idea to put that in your signature, so you never have to answer the question again.
Studio One (latest version), Win 11 23H2 , i9 -10940X 3.3 GHz, 32GB Mem, a 4K 40" monitor, PreSonus Studio Live III Console as interface/controller. secondarily test on Reaper, Cakewalk, and S1 on Surface Pro 3 Win 10 (latest versions).
Yes, I also do not believe it is a software bug. I am running a desktop and a Laptop and they are both having the same issue. Here are my system stats for the Desktop, we will start with that one first: Operating System: Windows 10 Home 64-bit Intel Core i7 6700 @ 3.40GHz 16.0GB Single-Channel DDR4 @ 1063MHz (15-15-15-36) Graphics: 2047MB NVIDIA GeForce GTX 750 Ti (NVIDIA) Realtek Audio - NOT in exclusive mode Storage: 931GB Seagate ST1000DM003-1SB102 (SATA ) 1863GB Western Digital WDC WD20EZRZ-00Z5HB0 (SATA ) Casio Privia PX-S5000 as a MIDI controller (USB)
I record in my DAW and not in BiaB and the only time I have had recording problems is when there was a conflict in audio settings. For instance every time my Nvidia Geforce RTX 4060 updates it activates it audio, thus causing me problems. Since I use an external audio device I have to go into Device Manager and deactivate the Nvidia and sometimes the RealTek audio which sometimes a Win 10 update will activate.
Are you using the Nvidia audio in one computer and the RealTek audio in the other computer? Personally I don't think either card is the best for recording. YMMV
Seated at the restaurant, He "Darling can you say something that makes my heart beat faster"? She "Your wife just walked in"!
64 bit Win 10 Pro, the latest BiaB/RB, Roland Octa-Capture audio interface, a ton of software/hardware
A friendly reminder to anyone responding to the issue, please try the steps called out above to reproduce and respond with your results.
Other ideas of variables involved in the issue are good, but we first have to establish that this is a local issue.
Thanks
Studio One (latest version), Win 11 23H2 , i9 -10940X 3.3 GHz, 32GB Mem, a 4K 40" monitor, PreSonus Studio Live III Console as interface/controller. secondarily test on Reaper, Cakewalk, and S1 on Surface Pro 3 Win 10 (latest versions).
An Update: I just tried to record a MIDI track again with the MME drivers, and the bug popped up! It stopped recording MIDI at a random point in the song. So now this error has shown up using every possible driver on my system: WAS, ASIO and MME. I'm not sure what to try next.
You have proven that the audio driver is probable not the issue. I have not seen one person on this forum, that has over 40 people logged in at any given time, confirm that it works for them.
Your hardware all seems perfectly adequate, so I not thinking that's an issue either. The one thing I'm pondering is, the rate that you got the failures did seem to be different with different audio drivers. You have already tried returning your setup to the factory default setups to eliminate that, correct?
Studio One (latest version), Win 11 23H2 , i9 -10940X 3.3 GHz, 32GB Mem, a 4K 40" monitor, PreSonus Studio Live III Console as interface/controller. secondarily test on Reaper, Cakewalk, and S1 on Surface Pro 3 Win 10 (latest versions).
- If you enable the wizard playalong feature under the play menu, and record yourself playing the QWERTY keyboard, does the error happen? - In Options | Preferences | Record Filter if you uncheck everything except for Notes does the error happen? - When you are recording, is "None" selected for Audio?
OK, I recorded midi under these similiar conditions for the a half hour or so. Using MME with no significant issue with latercy (likely because of how I playkeys - the original slow hand). I set up 12 bars x 3x using RD's and Piano MST and Bass RT. Played and recorded fine. No crashes.
It does appear you may have the Pianoteq VST on two channels - on the thru so that you hear it play, and then on the Melody in order to playback the recorded midi. this worked fine on my machine, but may be stressful for your system? I suggest you just put default Synth on the thru to lighten the CPU load during recording.
Ok I think I have found the culprit. Unfortunately, it looks like my new Casio PX-S5000 keyboard does not play nice with BIAB. Here's the test I did: I have brought out my old Roland FP-8 Keyboard and hooked it up via USB MIDI and the program runs fine and lets me record to MIDI for the entire song without stopping - no problems at all. When I close out the program and then hook up the Casio keyboard (via USB) the problem rears it's ugly head and the MIDI recording stops at random places. Does anyone else on the forum have a Casio PX-S5000 and can you reproduce this? I do not know if it would happen with the other PX-S models or not. But this is a brand new keyboard and this is what seems to be giving me the grief. I have duplicated this problem on both my laptop and desktop. Roland FP-8 - no problems. Casio=problem. So is this something in BIAB programming that needs to be addressed or what? I'm not sure where to go next. I really want to use the Casio. I tried changing settings on the Casio having to do with Local control ON/Off and High resolution MIDI out from the Casio - but these made no difference. I still have the problem whenever I use the casio PX-S5000 keyboard and try to record MIDI.
Last edited by Lot2Learn; 01/24/2407:52 PM. Reason: Added the last 2 sentences
Video - Band-in-a-Box® DAW Plugin Version 6 for Mac®: New Features for Reaper
Band-in-a-Box® 2024 includes built-in specific support for the Reaper® DAW API, allowing direct transfer of Band-in-a-Box® files to/from Reaper tracks, including tiny lossless files of instructions which play audio instantly from disk.
Already grabbed your copy of Band-in-a-Box® 2024 for Mac®? Head to our Support Page to download build 803 and update your Band-in-a-Box® 2024 installation with the latest version developed by our team!
Along with the 50+ new features added with Band-in-a-Box® 2024 for Mac®, we've also released an awesome collection of new Add-ons! On top of the 222 new RealTracks (+50 bonus RealTracks), we've also released new MIDI SuperTracks, Instrumental Studies, "Songs with Vocals" Artist Performance Sets, Playable RealTracks Set 3, Playable RealDrums Set 2, and two new sets of "RealDrums Stems."
Order Band-in-a-Box® 2024 for Mac during our special (which ends July 31st) and you'll receive a Free Bonus PAK that includes a lot of these new Add-ons:
- MIDI Styles Set 88: "Look Ma! More MIDI 11: SynthMaster"
- Instrumental Studies Set 20: New Orleans Piano
- MIDI SuperTracks Set 40: More SynthMaster
- MIDI SuperTracks Set 43: Rock & Pop Keys
- Artist Performance Set 15: Songs with Vocals volume 5
- Playable RealTracks Set 3
- Playable RealDrums Set 2
- SynthMaster Sounds and Styles, with audio demos
- RealCombos 2024 Booster PAK: *For Pro customers, this includes 35 new RealTracks and 58 new RealStyles.
*For MegaPAK customers, this includes 25 new RealTracks and 45 new RealStyles.
*For UltraPAK customers, this includes 28 new RealStyles.
- RealDrums Stems Set 6: More Pop, Rock & Country
Want even more new Add-ons? Boost your Free Bonus PAK to a 2024 49-PAK for just $49 and add even more new Add-ons to your collection:
- 50 Bonus Unreleased RealTracks & RealDrums
- MIDI Styles Set 89: "Look Ma! More MIDI 12: Funk, Jazz & Blues Keys"
- Instrumental Studies Set 21: '80s Hard Rock Guitar
- MIDI SuperTracks Set 41: Jazz Comping & Soloing Piano
- MIDI SuperTracks Set 42: Soul & New Orleans Keys
- Artist Performance Set 16: Songs with Vocals volume 6
- RealDrums Stems Set 5: Jazz, Latin, Funk & World
Band-in-a-Box® 2024 for Mac® Videos: One-Stop Shopping!
With the release of Band-in-a-Box® 2024 for Mac®, we're adding new videos to our YouTube channel. We'll also post them here when they are published so that you can easily find all of our Band-in-a-Box® 2024 for Mac® videos in one place!
The Band-in-a-Box® 2024 for Mac videos released as-of June 28, 2024 are:
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