Originally Posted By: VideoTrack
I see that Reaper has had a thorough bug-reporting feature since 2009. No wonder users advise of how robust Reaper is.

I am sure that many genuine issues are missed by PGM because there is no consolidated way of reporting such issues.


I found this thread whilst trying to find out how and where to report bugs. 'Nuff said, I think.

Quite a few companies are nervous of bug reporting in a public place, partly because they feel it might make them look bad and partly because they fear a deluge.

In practice I think such a reporting structure does give a consolidated means to identify and report, which helps to root out the real bugs from what my wife describes as a PICNIC, "problem in chair, not in computer", though the fields can be reversed :-).

It gives a place for people to search for what they think is a bug and see whether it's known, is a picnic, needs more information, has a workaround, or whatever.

The OpenSource community often does this very well, at least once a package reaches critical mass, think Ardour, Hydrogen, GIMP, LibreOffice, esoteric packages like Micromanager and of course Linux and the BSD derivatives themselves. Proprietery softwares also often do. Reaper is a good example, and the tie-in between Ardour and Harrison is another.

I've been an electronics professional since 1968 and a software professional since about 1970, so I know how hard it can sometimes be to fix a problem.

Almost always, the hardest part of fixing a problem is in being able to reproduce it reliably. There must be hundreds of thousands of BIAB users and some of those will put in some time to finding that "reproduce reliably".

Last edited by Gordon Scott; 07/29/20 06:23 AM.
Jazz relative beginner, starting at a much older age than was helpful.
AVL:MXE Linux; Windows 11
BIAB2025 Audiophile, a bunch of other software.
Kawai MP6, Ui24R, Focusrite Saffire Pro40 and Scarletts
.