Dudes, I've said this before. Contrary comments that imply there's something inherently wrong with the program need to be based on FACTS. Of course anybody can have any opinion they want no matter how stupid it is but in a discussion like this give me the facts please.

If there's a problem you post it in DETAIL so others can replicate it. Probably 95% of all these so called issues are user errors because nobody else can replicate it. It if is truly a bug PG will look into it and issue a patch for it. An example of that was the VST tempo lock issue. That was supposed to work for years and didn't until a couple years ago. In case you guys think I'm just a fan boy every year when the testing started my very first post in the RB test forum was "Have you fixed the tempo lock issue yet?" That was a bug.

Having issues in loading VST's is not a bug and saying the program crashes all the time is not a bug either because others do not have that issue and it doesn't crash for anybody else other than once in a great while. If you're getting more than the occasional random crash it's you, period. You should post EXACTLY what you did to create that crash and let all of us try to replicate it.

Now, what's the definition of a bug? A bug is something that is supposed to work a certain way according to the documentation and does not. If something is not in the documentation and you're having fun going off the reservation with stuff that PG doesn't recommend and you get crashes then that's on you. If you WISHED something worked a different way, fine request it but it's not a bug.

Does this make sense or am I talking to the wall?

Bob

Biab/RB latest build, Win 11 Pro, Ryzen 5 5600 G, 512 Gig SSD, 16 Gigs Ram, Steinberg UR22 MkII, Roland Sonic Cell, Kurzweil PC3, Hammond SK1, Korg PA3XPro, Garritan JABB, Hypercanvas, Sampletank 3, more.