It took me awhile, at least maybe a year, to adjust my way of working to the way RealBand operates enough that the program would operate without crashing too often. But, it still crashes more often than I would like.

2bSolo, your right in your observation some users often seem to have RealBand crashes while other rarely do. I can't speak for others but for me it was a learning process. I constantly had to think about what I was doing when a crash happened, what could I do to adjust so it wouldn't happen again, test and see if my adjustment works. I discovered a couple of weak spots in how the program operates and try to avoid them.

Save, save, save! You can't save too often. The more often you save the less often you crash!

Every now and then use save as and save the project under a new name. If, or when, your project crashes, close the program, open the program and open the last project name that worked. You've lost whatever you did from the time of the last save as to the time the crash happened but ... you didn't completely lose the project!

If you use a feature like the gain or volume nodes you need to use extra care. In addition to the saves and save as you need to take steps specific to the feature like clean-up nodes, don't move any node up, down, left or right too much. In other words, don't create a node unless you need it and when you do create one, create it where you need it.

So, the program is temperamental. I wish it wasn't but it is. Learn what sets it off and minimize those things.

Everyone has to decide for themself if the benefits outweigh the effort required. For me, it does.

Jim Fogle - 2025 BiaB (Build 1128) RB (Build 5) - Ultra+ PAK
DAWs: Cakewalk Sonar - Standalone: Zoom MRS-8
Laptop: i3 Win 10, 8GB ram 500GB HDD
Desktop: i7 Win 11, 12GB ram 256GB SSD, 4 TB HDD
Music at: https://fogle622.wix.com/fogle622-audio-home