There is a RealBand 2015 Build 7 update (Feb 19 2015)
http://www.pgmusic.com/support.realband.htm#2015_7

This patch will update RealBand Version 2015 to Build 7 from any previous 2015 build. It must be installed into your existing RealBand 2015 folder.

Summary of Changes (Feb 19, 2015) since Build 6

• Access violation in the Tracks window which could occur if track heights were changed.
• Access violation if you clicked on either the Tempo Percent or Transpose buttons and then entered text and pressed return.

Summary of Changes (Jan 19, 2015) since Build 2

• Fixed: Delete key in Audio Edit Window would always delete all both channels.
• Fixed: Moving a section of audio in tracks win would sometimes still create extra nodes.
• Fixed: Render – Merge Audio Tracks to WMA would show wrong strings in dialog, and would cause RB to freeze next time dialog is executed.
• Fixed: Select and Generate UserTracks didn't work from either the Main Menu or the Generate button. It only worked from Tracks Window right click.
• Fixed: Crash if no MP3 codecs present and attempting to save to MP3
• Added: Section letters shown in Chords Window.
• Added: - New 'Application Error' dialog that shows stack trace and lets the user email the Error Report to PG Support, or add the Error Report to RBError.LOG.
• Added: - Localization support.
• Fixed: - Loops dialog was sometimes showing a division by zero message when adding certain loop.
• Fixed: - Some acid loops were not being read properly.
• Fixed: - Some acid loops were not being recognized.

Summary of Changes for 2015 Build 2 (Dec 5, 2014)

• Fixed: Hotkeys not restored properly after entering a value in the pitch transpose or tempo adjust.
• Fixed: Added warning, when exiting MIDI Devices dialog or Audio Drivers dialog, if default sample rate for MME differs from song sample rate.
• Fixed: Added Acidize This Wav file command to the Render menu.
• Fixed: Elastique ASIO error when ASIO buffer size in sample frames was great than 1024.
• Fixed: Select and Generate User Track on main menu and Generate popup menu both launched the Pick a Loop dialog.
• Fixed: Render save track to file not working.
• Fixed: Existing video wasn't always cleared on a File - new.
• Fixed: Simple drums not working.
• Fixed: Help topic for Big Piano Options dialog not linked.
• Fixed: In the Generate Button dropdown menu, the favorites submenus for MIDI SuperTracks, UserTracks, and Loops were not being setup and populated correctly.

Andrew,
Just letting you know that this patch fixed all my problems!
Thank you for making my day!

You ROCK!
Jonathan

Ooops, it fixed all of the problems that I had at the time. But now that I can use Realband again, I made a song that uses tempo changes (percentages for part of it and an actual number in another part) and when I try to render, it gives me an access error and freezes the rendering process - thus making me force close the program.

The song also has style changes, but I noticed your patch had addressed tempo changes in a different part of the process, so I wondered if I might being seeing a related issue albeit downstream?

Not sure what you mean by a song that has tempo changes with "percentages for part of it". A tempo change in the song is an actual number. The tempo map only has actual numbers.

I just tried rendering a song with tempo changes and it didn't seem to have any problems.

Thanks for your reply Jeff.

I was referring to the option (at any bar) in BIAB to change the tempo either by a percentage or by simply typing the tempo you want.

I actually solved my above problem by first rendering all of my BIAB tracks to wave files. Then opening the song in RealBand file and deleting all of the band in a box tracks. Then I imported all the wave files. From there it rendered fine.

Thanks again,

Hi Jeff,

Still awaiting for the resolution of the accidental changes to Auditioning Patches using the Classic Tracks window where the + and - keys do not now change the patches in succession. This was the subject of an Email to Support which I understood was passed on to Development for solution. The latset PTW 2015 operates correctly, I understand.

LynB