Hello,

I installed RealBand 2016 (7) patch.

I am pleased to announce that the patch has fixed the issues that I reported via email.

Thank you Andrew and the PG software / test team for your efforts.

Now I am ready for some Memorial Day weekend music fun. And of course a hamburger or 2.

Me too.

Good job so far.

Patch works great to me too! Nice logo!

Jeff

I still have random crashes when using ASIO drivers on my Focusrite interface. I DID bite on a bullet while upgrading to Windows 7 and have my song data all on a second drive. There is little on that computer outside of the OS and BIAB. (Chrome and Adobe Audition.) I crash when I stop the transport. In 70 minutes of work last night I crashed 5 times. Each time I crashed I lost some wave editing and had to do it all over. When you make an edit, play it to test it, and crash, there is no place in there to save that edit unless I save it before I listen to it, and why would I do that?

Hi,

I loaded a style into Realband and then recorded some tracks. So far I have not had any issues.

I am using a Focusrite Scarlett 2i4 USB audio interface with the ASIO Focusrite driver.

I am using the BIAB EverytingPak on the supplied USB external hard drive.

From your post you upgraded to Windows 7. I am assuming from XP?

What are your computer specs?

CHEERS!

My computer runs an i5 processor with 8gb or RAM, ATI 1gb graphics card, 10,000 RPM hard drives, Focusrite 2i4. It has a D-Link NIC in it that is disabled when I am doing music to avoid data bus traffic interference. I don't need CPU cycles sapped by Gmail polling when I an trying to work.

It's a hand built computer, as I know I build a better computer with quality parts I buy myself rather than the stuff Dell uses that was all supplied by the lowest bidder. It has run like a top with very few issues until I installed 2016. The rest of my computers ARE Dells, but that is just because they are so cheap I preferred to not waste my time and money building a computer just to surf. Note that there were no issues with XP running RB 2013 and 2014. Only when I installed 2016 did I start having problems. The upgrade to Win7 has not done a thing for me, though it was probably well past time to do it. I just hate the prep time that goes into it. Moving files, listing what apps I need to reinstall.... in this case all I lost in the format was stuff that I was keeping for convenience, like drivers I can always download again if I need them. The only apps are Chrome (I hate MSIE) and Adobe Audition (much easier to convert WAV to high sample rate MP3s. since RB doesn't allow conversion 320 MP3s without downloading external codecs and such). The problem is simply NOT my computer.

Remember, after the WIn7 install I also had to do a fresh install of RB/BIAB (I have never used BIAB, just FYI) so now everything is clean installs. And still, at random times, when I stop the transport I crash.

Eddie,
Do you have both the latest RB patch and BiaB patch installed?

I noticed you said you never use BiaB, but the 2 programs are closely intertwined, so thought I'd ask. Maybe updating BiaB will help RB.

I seem to remember a Transport Control issue being revolved in one of the updates recently ..

Of course I am up to date. Nerds do that sort of thing.

I don't use BIAB. Never once have. But that doesn't mean it isn't installed and up to date.

Very soon I am going to take my angle grinder and cut this hard drive in half and just admit this was a waste of $300. This is ridiculous that I have to dance like this. I expect software to work EVERY TIME, on every computer, exactly the same. As I keep saying while sounding like an annoying PITA, I have yet to need to "reset" Windows, Office, Chrome, Audition.... they work the same for everybody. The support has really gone downhill since PG has gotten so big. Back when I had the issue with using multiple MOTU interfaces, they actually did a remote session to my computer and worked with me. Now it takes 8-10 days to get responses to emails, and all the emails do is put me off, telling me to do newbie level nonsense rather than them fixing their problem. When we fought the problem with the MOTUs, after everybody and their brother giving me cliche nonsense about drivers and stuff that people who really don't know computers say because they have heard those buzzwords, it ended up being their problem as I said from day 1.

I am not the R&D department for PG Music. They need to fix their problems, not me. I am a paying customer. I am not going to spend my time downloading drivers when my drivers are current. They always are. I am not going to defrag my hard drive. I am not going to get into sound card debates.

Everything worked PERFECTLY with 2014. And nothing changed on my computer. I spend 5 hours updating to Windows 7 because PG suggested it. I have the SAME issue I had with XP. This is ridiculous. 5 restarts in 70 minutes last night. Much of that time redoing what I was not given the chance to save because it crashed. This has me at a point where I don't even want to work on music anymore.

Well if everything worked perfectly with 2014 and the latest real tracks show up in list, I'd be tempted to revert back to 14 again,considering the probs you are having Eddie.


Musiclover

FWIW, I'd try Chat over email. You get someone's attention right then, and possibly a remote session (as mentioned).

Also, weird experience tonight; I unplugged the mouse on my main system to use on a laptop (VERY stable W7 Professional OS on said main system)
Never ever had it BSOD before, but when I plugged the mouse back in the whole thing crashed to blue screen and rebooted .. turned out OK, but apparently not ALL software is perfect all the time.

Time of day, day of week matters when trying to get remote control support from PG. If I need help I call on the telephone. When remote control is the solution Wednesday early in the support work day works best for me. I realize the time is a problem for some, I'm lucky its 2pm eastern time for me.

Rharv how does a wireless mouse interfere with a system, I have both a wireless mouse and keyboard. Installed because the wire on both devices were too short to position my desktop under the work surface.

It wasn't a wireless mouse, just USB (hard wire), and I have no idea why it crashed my OS .. I just unplugged it, used it on another system and plugged it back in .. and crashed. Hard.
BSOD type message appeared, but it rebooted fine.

I was quite surprised. This particular system has been rock solid for years, but sometimes stuff happens I guess.

I misread your post sorry