Also book in the manual see if there's ways to configure the keyboard send more or less MIDI data. Looking on at the manual online it looks like it has two to three different on's and off's and CC numbers for different pressures of on and off. etc.
PGM, does the filter notes record filtered data or does it just not show it?
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).
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.
Are you using two VSTi?
No, I am only using Pianoteq VSTi. I have tried using the CoyoteWT and the same problem exists (recording MIDI stopping at random).
When I look at the MIDI Monitor file generated when running BIAB 2014 (which is the last version I have that works properly with the Casio) there are only entries labeled "Ext" in the column for the Source. Looking at the BIAB 2024 MIDI Monitor there are entries for both "Ext" an "1" - what is the difference between source labeled "Ext" and "1" ? I wonder if the fact that source "1" does not show up in the MIDI monitor of the 2014 version has any bearing on the situation. Also, there are no "Note-Off" entries in the 2014 version MIDI monitor file so I don't think that has anything to do with it. In addition, the 2014 file does not have any of the "#88 Undefined" entries that are being generated in the 2024 MIDI monitor file. More clues perhaps?
I believe you said you have another keyboard that has a broken key, right? If so have you looked at the MIDI data being sent by it? Maybe play with the pitch bend and mod wheel to see if BiaB is blocking that data. If it is then the problem is with the Casio. If not then the problem is with BiaB.
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
What, if any, MIDI data is being sent if you just start the MIDI monitor and play nothing on the keyboard?
If I hit "Record MIDI" this is what shows on the MIDI Monitor (see attached image) with those last 3 entries being generated by the count-off on the drum track. So it looks like Source "1" is the BIAB program itself. These entries are before a single note is played on the MIDI keyboard.
I believe you said you have another keyboard that has a broken key, right? If so have you looked at the MIDI data being sent by it? Maybe play with the pitch bend and mod wheel to see if BiaB is blocking that data. If it is then the problem is with the Casio. If not then the problem is with BiaB.
Neither my old keyboard or the new Casio have any mod or pitch bend wheels - just keys.
I just found this MIDI implementation chart in the Casio manual. It might have some bearing on the situation but I have no idea how to use this information. See attached.
I have a very strong suspicion that a lot of the additional / unexpected events are generated and input into the data stream by the BiaB program itself. (Although this doesn't necessarily get anyone closer to the cause of the lockup problem.)
BIAB & RB2024 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
Ok a couple of IMPORTANT pieces of information I have just discovered in my testing. This all goes along with my theory that the CASIO PXS5000 keyboard does not play nice with BIAB 2024. FIRST, the Casio transmits High Resolution Velocity MIDI data. High Resolution MIDI Velocity CC#88 was adopted by the MMA around 2010, giving controllers and instruments a velocity range of 0-16,000+, instead of the basic MIDI 0-127. (Pianoteq is one of the few software instruments that respond to it.). These are the CC # 88 picked up in the BIAB MIDI Monitor but apparently BIAB 2024 does not know how to respond to these. This is most likely causing the recording to stop abruptly with some of the MIDI data being transmitted by the Casio BIAB just doesn't know what to do with it and translates it into the wrong command and stops the recording.
SECOND: I am able to DISABLE the high resolution MIDI velocity data transmission in the Casio and when I do that, BIAB responds better, but not perfect. The MIDI Monitor no longer picks up any strange data, the only thing listed is Note on clean data (see attached screen shot). BIAB seems to do well with this UNLESS, I play too fast or strike the same note repeatedly and very fast. These two actions will cause the recording to STOP abruptly.
So I'm getting closer, but I can't play too fast because as soon as I do or repeat a single note fast in succession, it triggers the recording to stop - and that is with high velocity resolution turned off. So it seems that BIAB is having a problem with the rapid playing. Also, I wonder if BIAB programming can implement the High resolution Velocity MIDI data reception into its programming.
Good job! Thumbs up PGM can make some improvements to their recording code that might fix this.
Meanwhile do you have a DAW the you can export the backing tracks to and record your performance there?
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).
Good job! Thumbs up PGM can make some improvements to their recording code that might fix this.
Meanwhile do you have a DAW the you can export the backing tracks to and record your performance there?
It would bereally nice if PGM can fix this with an update.
Yes, I can export the backing tracks into my DAW and record that way. I just like having a quick way to record right into BIAB (when the inspiration hits) and then save the MIDI file that I can then import into my DAW for remixing later.
I remember reading a post a couple of years ago about a problem created by a mismatch in resolution of MIDI data.
Given that you have high resolution input, it may be that you need to match that PPQ (parts per quarter note) in BIAB. (This is what solved the problem for the user in the past.) This mismatch in PPQ resolution could also explain why you are getting multiple notes happening as a single event (i.e. high resolution PPQ data being reduced to lower resolution PPQ data).
Under "Options | Preferences", choose "Midi file" and try setting BIAB's PPQ to a much higher resolution. By default, BIAB uses 120 PPQ. It might be that you need to run this setting at 1920. Also check your keyboard and VSTi/DXI softsynth to see if these also need to be matched.
I agree with Noel and PGM would want you to try that first.
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).
I remember reading a post a couple of years ago about a problem created by a mismatch in resolution of MIDI data.
Given that you have high resolution input, it may be that you need to match that PPQ (parts per quarter note) in BIAB. (This is what solved the problem for the user in the past.) This mismatch in PPQ resolution could also explain why you are getting multiple notes happening as a single event (i.e. high resolution PPQ data being reduced to lower resolution PPQ data).
Under "Options | Preferences", choose "Midi file" and try setting BIAB's PPQ to a much higher resolution. By default, BIAB uses 120 PPQ. It might be that you need to run this setting at 1920. Also check your keyboard and VSTi/DXI softsynth to see if these also need to be matched.
Regards, --Noel
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. This stops the entire song waiting for me to click on the pop-up dialog box as to whether I want to save the recording. Then, when I close the dialog box, the song continues to play. Somehow, BIAB is getting a signal to STOP RECORDING, but I don't know what it is interpreting in my playing as that command. So weird. I'm not giving up yet, but I'm getting close. I have a 2014 version of BIAB that works fine (without changing the PPQ settings) so I'm starting to think the upgrade has done nothing but create headaches. It would be interesting to see another Casio PX-S5000 user try to duplicate the issue.
L2L. i asked you up thread some questions but no response. sigh so lets have another go.
1.did you compare your bb 2014 settings in bb with your bb 2024 settings ? includeing recording dialog settings.? also at the top of the bb chord view post back your settings for number of choruses and end bar for both 2014 and 2024.
2. i find it telling that the other midi kbd fp works fine i read upthread..correct ?
3. re stop ...thats good deducing mate. maybe its a setting in bb THATS DIFFERENT TWEEN 2014 and 2024. Because as you said something is telling bb to stop. im wondering if there is a linkeage tween the flipping over of choruses and the stop condition.
4. something to try. do an experiment as follows. instead of embedding the repeats in the chord sheet...in 2024...unfold the whole song and enter chorus 1 at top of bb. ie...lay the song out in one long chord sheet. does the stop problem go away ? sometimes ive found for some reason unfolding works better than embedding repeats etc.
5.casio has a user forum. worst case if its not a bb bug i would contact cas support and raise the issue on the forum.
your call on whether to get back to me.
sometimes its difficult for people to help others because the helpers arent there. thus its a process of elimination often.
L2L. i asked you up thread some questions but no response. sigh so lets have another go.
1.did you compare your bb 2014 settings in bb with your bb 2024 settings ? includeing recording dialog settings.? also at the top of the bb chord view post back your settings for number of choruses and end bar for both 2014 and 2024.
ANSWER: Yes, I have compared the settings and they are the same.
2. i find it telling that the other midi kbd fp works fine i read upthread..correct ?
ANSWER: The Roland keyboard works fine with 2024, just the Casio has the problem
3. re stop ...thats good deducing mate. maybe its a setting in bb THATS DIFFERENT TWEEN 2014 and 2024. Because as you said something is telling bb to stop. im wondering if there is a linkeage tween the flipping over of choruses and the stop condition.
ANSWER: It is definitely a MIDI event being transmitted by the Casio and interpreted by BIAB as a STOP signal.
4. something to try. do an experiment as follows. instead of embedding the repeats in the chord sheet...in 2024...unfold the whole song and enter chorus 1 at top of bb. ie...lay the song out in one long chord sheet. does the stop problem go away ? sometimes ive found for some reason unfolding works better than embedding repeats etc.
ANSWER: Makes no difference.
5.casio has a user forum. worst case if its not a bb bug i would contact cas support and raise the issue on the forum.
your call on whether to get back to me.
sometimes its difficult for people to help others because the helpers arent there. thus its a process of elimination often.
Yes, Thanks.
om
LATEST UPDATE: I have been working with Andrew at PG Support and using different versions of BIAB here is what my testing shows: BIAB 2016 - runs perfectly. No problems and no errors. BIAB 2018 - runs perfectly. No problems, no errors. BIAB 2020 64 Bit - runs perfectly. No problems and no errors. So all of those versions are all perfect. I tried stressing them all to the max with very fast and rapid playing and playing one note in succession rapidly 20 - 30 times and they all were perfect. As soon as I try to run BIAB 2024 - ERROR - Access Violation.This error pops-up when I run the program. When I click to close that error dialogue box another box pops-up telling me an exception has occurred and I can continue but I should save work and reboot program. Then if I close out that box and try to record in the program, the program will run but will stop recording the second I play the same note rapidly, even just 4 or 5 times in a row. I tried to crash all of the other versions listed above several times using this technique and they never stopped the recording. Only 2024 stops the recording when I play notes rapidly.
When 2024 crashes and you get the pop up window that tells you a crash has occurred a crash file is created. I believe the file is stored at C:/bb/Data/Logs. You should be able to identify the crash file by the file time stamp. Send an email to support@pgmusic.com with the file attached. Reference this thread and mention Andrew is involved.
... As soon as I try to run BIAB 2024 - ERROR - Access Violation.This error pops-up when I run the program. When I click to close that error dialogue box another box pops-up telling me an exception has occurred and I can continue but I should save work and reboot program.
When 2024 crashes and you get the pop up window that tells you a crash has occurred a crash file is created. I believe the file is stored at C:/bb/Data/Logs. You should be able to identify the crash file by the file time stamp. Send an email to support@pgmusic.com with the file attached. Reference this thread and mention Andrew is involved.
Let me clarify the sequence of events. As soon as I try to run 2024 - ERROR - Access Violation. The error log in BB\Data gives no more information than what is on the pop-up dialog box when BIAB is started: " Access violation at address 000000000075E7E4 in module 'bbw64.exe'. Read of address 0000000000000629 at: 000000000075E7E4 " This error pops-up when I start BIAB. When I click to close that error dialogue box another box pops-up telling me an exception has occurred and I can continue but I should save work and reboot program. It doesn't matter if I reboot because the pop-up comes every time. Then when I close out that pop-up box I can use BIAB - so I guess it is inaccurate to say the program crashes. Next, I load up a song and try to record a MIDI track by playing on the Casio keyboard. That is when the program will stop recording the instant I play the same note rapidly, even just 4 or 5 times in a row. Note: This only happens with the Casio Keyboard. When I switch over to the Roland Keyboard, even though I get the "ACCESS VIOLATION" on start-up of BIAB 2024, I am able to record MIDI without it stopping when I play a few notes rapidly in succession like the Casio does. Therefore, I do not believe the "ACCESS VIOLATION" error is the key to the problem of the program stopping during MIDI recording. It is purely an issue with a MIDI signal being sent by the Casio when notes are played rapidly that tells the recording to STOP. Also, this STOP MIDI message is only "heard" in BIAB 2024, not in the 4 other early versions I have tested using the Casio keyboard.
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.
![[Linked Image - Only viewable when logged in]](https://www.pgmusic.com/forums/ubbthreads.php?ubb=download&Number=27225&filename=PPQ resolution.jpg)
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean