A Build 7 Update is available for RealBand Version 2017

Download the build 7 update

This is a cumulative update, that works from any previous 2017 build.

Summary of Changes for Build 7 (April 6, 2017)

• Potential access violation during ASIO playback.
• Always On ASIO is now automatically restarted after suspend to prevent issues with it not working properly afterward.
• Title of the program sometimes changed to "file converter" after importing a WAV file. This would be noticeable in the Windows Task Bar, or when alt-tabbing, etc.
• Errors when recording multiple tracks at once with build 6.

Summary of Changes for Build 6 (Mar 27, 2017)

• Fixed: RealTracks generation failed in certain cases with build 5, if using MME drivers and 'Output Always On' was selected.

Summary of Changes for Build 5 (Mar 15, 2017)

• Fixed: Improved support for the Vielklang VST instant harmonies plugin.
• Added: Always on MME added (checkbox setting).
• Improved: Much faster initialization of accompaniment functions (e.g. StylePicker and RealTracks Picker).
• Fixed: The time location of time-based VSTi plugins was being continually advanced when RB was stopped. This has been fixed so that the VSTi time location now gets set to RB's current time location when playback is not happening.
• Added: Drag and drop from the drop station to VSTi plugins that support this, is now implemented
• Added: In the PDF manual, clicking on the Bookmarks navigation pane, Table of Contents, or Index will jump to the corresponding page. (Note: To use the navigational elements, you need to open the PDF manual in Adobe Reader.)

Summary of Changes for Build 4 (Feb 20, 2017)

• FIXED - Program title was changed to 'file converter' if a conversion needed to be done such as after recording (this affected the title shown when alt-tabbing or hovering over the icon on the task bar, etc.).
• FIXED - Spurious warning about rebuilding style picker when not needed has been removed.
• FIXED - FX button now correctly turns blue if MIDI track is actually using a VSTi or DXi synth.
• FIXED - the choose note dialog in Notation Window had garbled text.
• FIXED - saving to XML would result in the timing being wrong, if the song's PPQ was not 120.
• FIXED - when drawing a slur in the situation of notes being extremely close together, program could potentially slow down or freeze.
• FIXED - a few miscellaneous minor localization and help-topic link issues

Summary of Changes for Build 3 (Dec 9, 2016)

• FIXED - Issue with the program freezing when non-realtime transposing a song with audio, or when doing a non-realtime time stretch or pitch shift on a track.
• UPDATED - Help files, manuals, tip files.

Summary of Changes for Build 2 (Dec 7, 2016)

• ADDED - RealScore and BigBand added to the Staff Options Chord Font selection combo box.
• ADDED - in note edit dialog, forced accidentals and note types (invisible, bend, hammer on, pull off, etc.) are now easier to select via listboxes that are always visible, rather than pull down combos.
• ADDED - Quarter Step checkbox in note edit dialog shown when the current note type is Bend.
• FIXED - when running Build 1 for the first time without any RB.CFG present, the Lead Sheet would display the stave lines extremely close together, unless Print Preview was visited at least once after running it for the first time.
• FIXED - when printing, or displaying just just the bass clef (no tab) in leadsheet, the note numbers were drawn above the clef which was interfering with chords symbols.
• ADDED - new setting adjust the vertical height of Bar Numbers in the Print Options dialog.
• ADDED - when saving notation to a jpg, in Print Preview, width and height settings are remembered.
• ADDED - checkbox to keep the ratio the same when changing width or height in Print Preview, and when saving to a jpg
• FIXED - In Staff Roll mode, the staff window wasn't showing notes that are at the start of a row.

Something wrong with build 7.Songs don't stop. The curser moves to the right spot if you hit the end of song button but won't won't stop if playing
Put build 1 in and all is fine.
I tried everything. Win 7 btw.

Build 4 is the last good one.Check out the thread.

I tried the SEQ and it stopped using ASIO and Always On or off.
I tried it using MME Always On and it did not stop.
I tried it with MME off and it stopped.

Summary of fixes since Build 4

• Added: Always on MME added (checkbox setting).

MIDI Super Tracks in RB not available FIX

So the addition of the button broke something else.

It's broken. I played a gig and kept getting audio drop outs. Very annoying V4 does not do that. I played about 60 gigs with 2014 without issues.

Is that using ASIO4ALL/VoiceMeeter or just MME ?

It's a pity Batch Render don't have SEQ to Video, then you could render all the songs to video, unless you use Conductor.

8 output wdm USB interface.

I would try it using ASIO4ALL or VoiceMeeter Banana

though sometimes you get a Device unavailable using ASIO4ALL as Microsoft GS Wavetable is using your audio device, so you need VistaMidi to change the Windows Default Synth to one like Coolsoft Midi Synth.

I just use VoiceMeeter Banana, in the Mixer panel set hardware output to your laptop sound device, then set RealBand Audio Drivers to ASIO and Drivers > VoiceMeeter ASIO, you can put VoiceMeeter Banana in the Programs > Startup menu to run on start.
You can set Windows Playback device to the VoiceMeeter AUX ASIO.

Look up my history here. I was a beta tester. I've been through these sort of issues for years. I appreciate your comments but it's Jeff I'd like to here from.This is the greatest but buggiest prog out there.

If you have been a beta tester you would know how long it may take to fix things if at all around here.
The solution are to let you play gigs NOW not in 10 years time.
For all we know Jeff could be in Hawaii, flat out working on new things or RB has been abandon due to it's bugs and crashing..

I did a gig yesterday with v4 and not one issue.

There will be a Build 8 posted very soon that fixes the playback not stopping issue. In the mean time disabling Output Always on in the MME driver selection dialog would prevent that from occurring.

Silvertones, I just did a source code comparison of build 4 vs build 7, and I am firmly convinced that the reason you are getting dropouts is due to the new default of 400ms Output Buffer Size for MME audio vs 2000ms which was the previous default. We lowered the default when we added Always On MME. All you have to do is increase it back to 2000ms and you should not be getting any dropouts. (We had created a new variable to ensure that if set to 2000 previously it would default to 400 unless later changed by the user.)

Thanks for stopping by Jeff. You've been missed, that's for sure.

Ok I'll give that a try. I'll reload build 7 and use it on my gig Monday.
I always leave at 2000 so I guess I didn't notice. I'll let you know.

Yes I loaded 7 and it was at 400 instead of the 2000 that is the default and what I use. I bet it'll be fine.

Jeff, I know we can be a bit ungrateful about RealBand at times, but it is special. I can't imagine life without its features! Thanks for all the work on it. It's kind of our Cinderella!

Listen I've played 100s of gigs with RB and made$1000s of dollars.It just freaks me out when your stable program clitches in front of a couple hundred people and it's because something gets fixed and something else gets changed that shouldn't have.

Thanks, Lambada.

Silvertones, my understanding, when that feature was implemented, was that Always On MME was considered a big priority to implement, and that it was considered very important that RealBand default to that setting enabled. This did require a lower buffer size, otherwise there would be a full 2 second delay when clicking on piano notes. I did mention to everyone involved that lowering the default could increase dropouts, but was asked to lower the default to 400ms. We probably should have issued a warning message about this.

Yes a warning would have worked.

Perhaps the change can be noted here:

We'll PT 2013 came through for me. I reloaded v 7 of RB made all the necessary settins. Tried it at home,played about 6 songs. I figured all was fine. Go to the gig get all set up try a song or two and all was fine
I then went to open the Jukr box and I hey a " file does not exist and RB crashes and closes. Thank God I had PT. It was flawless.

I just did a fresh new install. Should be fine. I'll know next gig.

Gig went flawless with v 7. Thank God. I thought I was back in a band again!