elapsed time for program fix

Author
peregrine
Max Output Level: -87 dBFS
  • Total Posts : 158
  • Joined: 2005/11/20 10:31:27
  • Status: offline
2011/08/31 00:14:38 (permalink)

elapsed time for program fix

I turned in a bug report last June for a problem I've had since SONAR7. I've always had a work around for it, but because of setup requirements for a new VSTi, its now become a showstopper. I asked support for a status last week, and, as expected, all they would tell me was that it had been turned over to their developers. I told them I think that's a coded way of saying it's a piece of paper on someone's desk. That must be close because I didn't get any argument from them. So my question is this. If you've ever submitted a bug report, how long did it take before you had a fix released? I'm just trying to get a sense of the approximate wait time involved.
#1

1 Reply Related Threads

    lfm
    Max Output Level: -53 dBFS
    • Total Posts : 2216
    • Joined: 2005/01/24 05:35:33
    • Location: Sweden
    • Status: offline
    Re:elapsed time for program fix 2011/08/31 00:30:34 (permalink)
    I put plenty stuff 5 years ago that never was attended to. So I did not upgrade anything from Sonar 4 until 8.5, but issues were not showstoppers in this case - more a matter of principle.

    It's just recently I feel Cake has discovered the value of proper handling of customers and issues they have. They now have email notification when status of reports are updated and I even got suggestions from support to workaround it.

    So better late than never.

    One day we will get a ticket based support system that makes it easy to maintain conversation until solved. Not these horrific forms with plenty stuff to fill in over and over.

    So to get fixes you need a product that is alive and maintained still - but with reported stuff the X-series upgrade only get further away for me.
    post edited by lfm - 2011/08/31 00:32:04
    #2
    Jump to:
    © 2024 APG vNext Commercial Version 5.1