|
Log in to post
|
Print Thread |
|
|
|
|
|
RealBand
|
Joined: Jan 2009
Posts: 63
Enthusiast
|
OP
Enthusiast
Joined: Jan 2009
Posts: 63 |
Hi, I have a purchased MIDI sequence that we had used before. Brass Section on Track 1 assigned to Channel 1. The "volume" level was 120. Driving a Ketron SD4 sound module. Other instruments on other tracks and channels. This had worked fine for several months then all of a sudden the Brass Section appeared to have gone away. Closer examination by muting the other instrument tracks showed that the volume level was very low for the Brass Section. BUT the volume control and Event view still showed the original setting of 120. Note that prior to starting to track down the cause of the problem NO EDITS to the file had been done. Exited Real Tracks and tried starting again. Even over power cycles of the computer (and Ketron SM) the problem remained. Tried increasing to 127 in the event view, no significant change to sound level. Tried applying a 200% velocity increase via edit menu, no significant change to sound level. All other tracks/instruments worked fine, full volume. I went back to the original .mid file from the downloaded zip received at time of purchase. Same problem in there so again no chance of any accidental edits to the file introducing the problem. Just for grins I changed the channel on Track 1 from 1 to 6 (since 6 was unused in this sequence). Instantly the volume level of the Brass Section was restored. Has anyone seen this before? Any suggestions on how to track down what might have happened with channel 1 that could cause the volume level of the associated instrument to be very low? Note: I tried changing the Brass Section to Piano, and the Piano sound level was also very low when using channel 1. I have other MIDI sequences that use Channel 1 and I have not seen this problem with those sequences. We have a older recording from the sequence where we were having the problem that has the Brass Section at normal volume, so it is not just a case of "mis-remembering" the sound level  Is there a setting option somewhere in RealBand that would impact volume level on an individual channel that would "stick" over system restarts? Thanks, Burt
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: May 2003
Posts: 8,021
Veteran
|
|
Veteran
Joined: May 2003
Posts: 8,021 |
Channel 1 on the Ketron has been turned down.
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: May 2000
Posts: 38,502
Veteran
|
|
Veteran
Joined: May 2000
Posts: 38,502 |
Every time you power the Ketron off and back on, it does a full reset. So I doubt that it could have a stuck channel.
Use the Event List to check what's going on with that.
Are you calling the Track numbers "channels" or are you actually referring to MIDI Channels with the 1 and 6?
--Mac
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: May 2003
Posts: 8,021
Veteran
|
|
Veteran
Joined: May 2003
Posts: 8,021 |
Let's eliminate the Ketron. Set RB to use a DXi synth like the VSC and see if the brass section is right. If it is OK something must be amiss with the Ketro.
Mac is there a HARD reset for the Ketron?
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: May 2000
Posts: 22,526
Veteran
|
|
Veteran
Joined: May 2000
Posts: 22,526 |
Did the patch itself get wrote over with a lower volume setting?
Is the new song using the exact same patch as the original??
"Is there a setting option somewhere in RealBand that would impact volume level on an individual channel that would "stick" over system restarts? "
This is possible if you open the program using a template ($Options.seq) or such, but highly unlikely.. if you were using it you would know about it.
"Tried increasing to 127 in the event view, no significant change to sound level. Tried applying a 200% velocity increase via edit menu, no significant change to sound level."
This only changes the velocity (how hard you hit the key), not the overall volume control for the MIDI channel. See if there is CC #& or 11 causing the issue in the event list for channel 1.
My first hunch was a patch got saved with a lower volume applied...
I do not work here, but the benefits are still awesome
Make your sound your own!
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: May 2000
Posts: 38,502
Veteran
|
|
Veteran
Joined: May 2000
Posts: 38,502 |
Quote:
Let's eliminate the Ketron. Set RB to use a DXi synth like the VSC and see if the brass section is right. If it is OK something must be amiss with the Ketro.
Mac is there a HARD reset for the Ketron?
Cycling the power switch on the Ketron IS indeed a hard reset every time its done.
Nice feature, actually, once you have one and understand how it works.
The Ketron is a pure State Machine. It must get commands from a host or controller into its inputs before it will do anything. Those commands cannot be stored in the Ketron at all, they are "good" only as long as the current session or until an overiding command is sent.
--Mac
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Jan 2009
Posts: 63
Enthusiast
|
|
OP
Enthusiast
Joined: Jan 2009
Posts: 63 |
Thanks All,
Just to clarify. As I mentioned the sequence had not been overwritten. Just to make sure I went back and pulled the original sequence MIDI file from the zip I downloaded when I made the purchase. This totally unmodified (not even renamed) file had the same problem, so definitely not a case of the file being saved with a lower volume setting.
When I say channel I am referring to the actual channel number which may, or may not, be the same as a given track number depending on the actual MIDI sequence. In this particular case it happened that Track 1 was using channel 1 for the Brass Section patch. But of course that was just coincidental.
Perhaps a different MIDI file had set the volume on channel 1 and each time we have used this particular MIDI file we had previously played the one that set the volume on channel one. That would explain it not changing after a power on reset which I had thought would fully reset the Ketron. If that is the case then it will not be fun tracking down which file is the culprit. I will try just playing the offending MIDI file as the first one after the next power cycle to see if the problem is gone.
I know that velocity changes would only impact how hard the key was "struck" but I was trying anything that might change the perceived sound level as I was trying to track this down.
Now, assuming that something had set the volume on channel 1 in the Ketron to almost nothing. How would I change the volume on channel 1 (or any other individual channel)? My thought here is that I could send the appropriate setting change at the start of every MIDI file to make sure that this is not a problem in the future. Since changing the volume setting in the sequence on channel one did not have any impact where else would I change the volume level on an individual channel?
Thanks again,
Burt
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Jan 2009
Posts: 63
Enthusiast
|
|
OP
Enthusiast
Joined: Jan 2009
Posts: 63 |
Answering my own post I may have found the answer to what I was seeing. I was working with another purchased MIDI file that I hadn't revisited in quite some time. After working with it I remembered why I had shelved it. After that MIDI played once all the tracks were silent when playing it again! If I changed the Channel on one of the tracks that was now silent I had sound again, which is similar to what I was seeing with the MIDI that prompted this thread. I did some exploration and the new MIDI I was working with sets the expression controller on all of the instrument tracks, and the last thing it did with the expression was set it to 0! Then in each track as the last thing sent they did a reset all controllers. But it appears that Ketron does NOT reset the expression controller on a reset all controllers. At least it does not reset it to max. I tested this theory by adding a CC event at the start of each instrument track to set expression to 127 (max). This worked reliably, so probably I have another MIDI file that is setting expression to 0 on channel 1. Burt
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: May 2000
Posts: 22,526
Veteran
|
|
Veteran
Joined: May 2000
Posts: 22,526 |
I do not work here, but the benefits are still awesome
Make your sound your own!
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: May 2000
Posts: 38,502
Veteran
|
|
Veteran
Joined: May 2000
Posts: 38,502 |
Quote:
Perhaps a different MIDI file had set the volume on channel 1 and each time we have used this particular MIDI file we had previously played the one that set the volume on channel one. That would explain it not changing after a power on reset which I had thought would fully reset the Ketron. If that is the case then it will not be fun tracking down which file is the culprit. I will try just playing the offending MIDI file as the first one after the next power cycle to see if the problem is gone.
Toggling the Ketron power indeed is a full reset. It should and will cancel out any commands previously sent to the device.
Try it again, and this time, if the volume is still not right, immediately check the MIDI Event List for any CC7 or CC11 entries -- and see what they are.
I'm thinking now, however, that your problem might be in the *Audio* domain, though. Make sure that the offending track is not panned hard right or hard left and that the output is not somehow turned down or off for that Audio channel...
Odds are fairly good that the problem lies swomewhere within your computer and not the Ketron, although there is a very remote chance that the Ketron might be suffereing from a hardware fault, I doubt that as it plays on the other channels.
--Mac
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Jul 2000
Posts: 3,161
Veteran
|
|
Veteran
Joined: Jul 2000
Posts: 3,161 |
Remember that settings made to a Channel in one song can be carried over to the following song unless a global reset is sent to the Synth. In the case of the Ketron this can be achieved by a switching the Sound Modual off and on. Problems are created by CC11 or CC7 fading out at the end of a previous song at not reset in the next. CC64 Sustain set to 127 can create distortion in a following song. Pitchbend setting other than zero can cause later problems.
I would suggest that you include a CC121 value zero at the start of track 1 for all your songs using the Event List. This will create a soft "Reset all Controllers" each time a song is played from the start.
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: May 2003
Posts: 8,021
Veteran
|
|
Veteran
Joined: May 2003
Posts: 8,021 |
I would be surprised if a commercially made MIDI didn't have all the parameters sent at the count in of the tune.
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: May 2000
Posts: 38,502
Veteran
|
|
Veteran
Joined: May 2000
Posts: 38,502 |
What gets almost everybody at one time or another -- is that they don't realize that they must rewind the sequence all the way back to the beginning of the file and then hit Play in order for the sequencer to be able to send those critical CC and other changes that must be reset after something like a fade at the end. That leaves the State Machine in its last state sent, which is Volume all the way down for that track. However, one should be able to send a correction CC and turn it back up if that is the case, but only for that one playback because if it reaches the end of the song and the fadeout area, the commands will be sent again.
*Might* be what's happening here...
--Mac
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Jan 2009
Posts: 63
Enthusiast
|
|
OP
Enthusiast
Joined: Jan 2009
Posts: 63 |
Hadn't checked back until now.
I had rewound to start so that was not the case.
What the problem was, with the sequences in question, was the Expression level being "faded" to 0 or a very low value.
Edit [I mis-typed. CC11 IS reset on the SD4 by CC121. But some sequences appear to use CC7 (Volume) instead of CC11 (Expression) so in those cases Volume is not reset in the SD4). That said, the issue can also be addressed by starting each track with a CC11 set to 127, but using a CC121 is also a good idea.]
Add this to Pitch Bend Sensitivity CC101/100/6 that is another issue with "professionally" produced sequences, and as was mentioned above Sustain and it gets to be a bit of an annoyance.
Too bad RealBand doesn't have a 'Macro" capability so you could just hit a single command to insert all of the CC's at once.
I'm going to add these to a file to import and insert at the start of each track as needed. Hopefully that will make it quicker to update the sequences as needed.
Thanks,
Burt
Last edited by BurtB; 09/27/10 12:10 PM.
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: May 2000
Posts: 22,526
Veteran
|
|
Veteran
Joined: May 2000
Posts: 22,526 |
from http://www.midi.org/techspecs/rp15.php"Reset All Controllers Channel Mode message (#121) is clearly defined. The value byte is always 0, although many implementations allow any value (don't care)."
I do not work here, but the benefits are still awesome
Make your sound your own!
|
|
|
|
|
|
|
|
|
|
|
|
|
RealBand
|
Joined: Jul 2000
Posts: 3,161
Veteran
|
|
Veteran
Joined: Jul 2000
Posts: 3,161 |
I use a Seq file which is set up with tracks 1 to 16 (Channels 1 to 16) showing only the CC and RPNs data required to set up each Track/Channel. This file excludes data normally controlled via the Mixer & Tracks Windows. Use File > Load Scrap to load the file to Clipboard and then Paste > Merge with existing Data.
|
|
|
|
|
|
|
|
|
|
|
|
Ask sales and support questions about Band-in-a-Box using natural language.
ChatPG's knowledge base includes the full Band-in-a-Box User Manual and sales information from the website.
|
|
|
|
|
|
|
|
|
|
|
PowerTracks Pro 2026 for Windows is Here!
PowerTracks 2026 is here—bringing powerful new enhancements designed to make your production workflow faster, smoother, and more intuitive than ever.
The enhanced Mixer now shows Track Type and Instrument icons for instant track recognition, while a new grid option simplifies editing views. Non-floating windows adopt a modern title bar style, replacing the legacy blue bar.
The Master Volume is now applied at the end of the audio chain for consistent levels and full-signal master effects.
Tablature now includes a “Save bends when saving XML” option for improved compatibility with PG Music tools. Plus, you can instantly match all track heights with a simple Ctrl-release after resizing, and Add2 chords from MGU/SGU files are now fully supported... and more!
Get started today—first-time packages start at just $49.
Already using PowerTracks Pro Audio? Upgrade for as little as $29 and enjoy the latest improvements!
Order now!
Band-in-a-Box 2026 for Windows Special Offers End Tomorrow (January 15th, 2026) at 11:59 PM PST!
Time really is running out! Save up to 50% on Band-in-a-Box® 2026 for Windows® upgrades and receive a FREE Bonus PAK—only when you order by 11:59 PM PST on Thursday, January 15, 2026!
We've added many major new features and new content in a redesigned Band-in-a-Box® 2026 for Windows®!
Version 2026 introduces a modernized GUI redesign across the program, with updated toolbars, refreshed windows, smoother workflows, and a new Dark Mode option. There’s also a new side toolbar for quicker access to commonly used windows, and the new Multi-View feature lets you arrange multiple windows as layered panels without overlap, making it easier to customize your workspace.
Another exciting new addition is the new AI-Notes feature, which can transcribe polyphonic audio into MIDI. You can view the results in notation or play them back as MIDI, and choose whether to process an entire track or focus on specific parts like drums, bass, guitars/piano, or vocals. There's over 100 new features in Band-in-a-Box® 2026 for Windows®.
There's an amazing collection of new content too, including 202 RealTracks, new RealStyles, MIDI SuperTracks, Instrumental Studies, “Songs with Vocals” Artist Performance Sets, Playable RealTracks Set 5, two RealDrums Stems sets, XPro Styles PAK 10, Xtra Styles PAK 21, and much more!
Upgrade your Band-in-a-Box for Windows to save up to 50% on most Band-in-a-Box® 2026 upgrade packages!
Plus, when you order your Band-in-a-Box® 2026 upgrade during our special, you'll receive a Free Bonus PAK of exciting new add-ons.
If you need any help deciding which package is the best option for you, just let us know. We are here to help!
Band-in-a-Box® 2026 for Windows® Special Offers Extended Until January 15, 2026!
Good news! You still have time to upgrade to the latest version of Band-in-a-Box® for Windows® and save. Our Band-in-a-Box® 2026 for Windows® special now runs through January 15, 2025!
We've packed Band-in-a-Box® 2026 with major new features, enhancements, and an incredible lineup of new content! The program now sports a sleek, modern GUI redesign across the entire interface, including updated toolbars, refreshed windows, smoother workflows, a new dark mode option, and more. The brand-new side toolbar provides quicker access to key windows, while the new Multi-View feature lets you arrange multiple windows as layered panels without overlap, creating a flexible, clutter-free workspace. We have an amazing new “AI-Notes” feature. This transcribes polyphonic audio into MIDI so you can view it in notation or play it back as MIDI. You can process an entire track (all pitched instruments and drums) or focus on individual parts like drums, bass, guitars/piano, or vocals. There's an amazing collection of new content too, including 202 RealTracks, new RealStyles, MIDI SuperTracks, Instrumental Studies, “Songs with Vocals” Artist Performance Sets, Playable RealTracks Set 5, two RealDrums Stems sets, XPro Styles PAK 10, Xtra Styles PAK 21, and much more!
There are over 100 new features in Band-in-a-Box® 2026 for Windows®.
When you order purchase Band-in-a-Box® 2026 before 11:59 PM PST on January 15th, you'll also receive a Free Bonus PAK packed with exciting new add-ons.
Upgrade to Band-in-a-Box® 2026 for Windows® today! Check out the Band-in-a-Box® packages page for all the purchase options available.
Happy New Year!
Thank you for being part of the Band-in-a-Box® community.
Wishing you and yours a very happy 2026—Happy New Year from all of us at PG Music!
Season's Greetings!
Wishing everyone a happy, healthy holiday season—thanks for being part of our community!
The office will be closed for Christmas Day, but we will be back on Boxing Day (Dec 26th) at 6:00am PST.
Team PG
Band-in-a-Box 2026 Video: The Newly Designed Piano Roll Window
In this video, we explore the updated Piano Roll, complete with a modernized look and exciting new features. You’ll see new filtering options that make it easy to focus on specific note groups, smoother and more intuitive note entry and editing, and enhanced options for zooming, looping, and more.
Watch the video.
You can see all the 2026 videos on our forum!
Band-in-a-Box 2026 Video: AI Stems & Notes - split polyphonic audio into instruments and transcribe
This video demonstrates how to use the new AI-Notes feature together with the AI-Stems splitter, allowing you to select an audio file and have it separated into individual stems while transcribing each one to its own MIDI track. AI-Notes converts polyphonic audio—either full mixes or individual instruments—into MIDI that you can view in notation or play back instantly.
Watch the video.
You can see all the 2026 videos on our forum!
|
|
|
|
|
|
|
|
|
|
|
|
Forums57
Topics85,993
Posts798,740
Members40,006
| |
Most Online44,367
Mar 4th, 2026
|
|
|
|
|
|
|
|
|
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean