UNofficial Digital Performer Community bug list discussion

[bayswater]

Does anyone publish a bug list? Bug fix reports, bug reporting pages, etc, but a complete bug list? I've see them from open source projects or non profit institutes, but a commercial software developer?

[MIDI Life Crisis]

And thus we venture down the rabbit hole once again...

If it isn't legally required to admit every little fault in your product, no matter what one would ever be able to sell anything because nothing is perfect.

Caveat emptor.

I'm perfectly happy to let this forum function as it has. If someone has a better idea, go for it.

https://www.phpbb.com

[mikehalloran]

Does anyone publish a bug list? Bug fix reports, bug reporting pages, etc, but a complete bug list? I've see them from open source projects or non profit institutes, but a commercial software developer?

Nothing comes to mind. Now and then, you'll find a short list that's called something like Known Issues from this or that developer but those are few and far between.

I keep a text doc of bugs and workarounds for various issues on apps as they are important to me. Except for the basics, I don't believe that anyone ever uses an app the way I do and vise versa.

[stubbsonic]

And thus we venture down the rabbit hole once again...

Wasn't MLC the one who hours ago suggested that "the team" (required to address, publish and provide workarounds for bugs) should be called MOTU Tech Support?

So... thus?

[MIDI Life Crisis]

And thus we venture down the rabbit hole once again...

Wasn't MLC the one who hours ago suggested that "the team" (required to address, publish and provide workarounds for bugs) should be called MOTU Tech Support?

So... thus?

Not at all what I said. You're added the parenthetical comments are YOU'RE position. Not mine.

Don't believe everything you think.

[stubbsonic]

I agree with Stubby. It's a big job and best left to a team. Maybe call them MOTU Tech Support? Catchy.

It, the "big job" what were you referring to"

[MIDI Life Crisis]

You're deep in the weeds here, man. Give it a rest.

[stubbsonic]

I said (paraphrasing): The effort to maintain a public list of bugs/workarounds requires a team effort.

To which MLC said: I agree with Stubby. It's a big job and best left to a team. Maybe call them MOTU Tech Support? Catchy.

Then I said: "IIRC, that was the whole point of this list, was that the MOTU tech support team did not publish a Known/Acknowledged Bugs list. There was some disagreement as to whether or not they SHOULD"

Then others re-visited the question of whether MOTU (or any developer does or should) maintain a list of known issues/bugs.

Then MLC says: "And thus we venture down the rabbit hole once again..."

I point out that MLC played a part in entering said rabbit hole, by suggesting that this is best left to MOTU support, to which he responds:

"Not at all what I said. You're added the parenthetical comments are YOU'RE position. Not mine.
Don't believe everything you think."

You don't have to take any responsibility for being vague in your language. But if it makes you feel good to blame me, I'll take it.

[MIDI Life Crisis]

Dude, you are missing the point, but let me spell it out for you.

My position is and has always been that documenting and chasing down the minutia of bugs and "perceived" bugs is, and should be, MOTU tech support.

You can twist, and turn, and pervert that all you want and try to show your prowess, or lack there of, in linguistic gymnastics, but all I said was, and do try to follow along here...

MOTU TECH SUPPORT is where this process should be happening.

We await for something non-sequitur...

[stubbsonic]

I'm psyched that you think I'm a linguistic gymnast (I have the build for it).

[MIDI Life Crisis]

I'm psyched that you think I'm a linguistic gymnast (I have the build for it).

OK, so can we get back to discussing Kitchen Cabinets from London now! LOL

[stubbsonic]

Another user discovered what may be a bug in the Spacial Maximizer, and I immediately confirmed the bug on my system and submitted a techlink.

[Robert Randolph]

I went through every reported issue and thoroughly attempted repeating it in 9.13.

Of 14 confirmed issues plus 2 unconfirmed issues:

• 2 related issues were fixed (tab cycling issue)
• 1 new feature in 9.1 that never worked correctly.(hardware inserts)

That will be my last update on the thread. I figured it only fair to keep it at least up to date since 9.13 came out soon after I decided to end this public effort.

[stubbsonic]

Thanks for following up, RR.

With the "1 New Feature in 9.1 that never worked correctly.(hardware inserts)"

Are you saying that is fixed also? It wasn't clear.

[Robert Randolph]

Thanks for following up, RR.

With the "1 New Feature in 9.1 that never worked correctly.(hardware inserts)"

Are you saying that is fixed also? It wasn't clear.

Hardware inserts work perfectly here now. The ping and routing works correctly.

There's still an issue with bundle names not propagating, but functionally they are working.