Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #97084
    Profile photo of Patrick
    Patrick
    Participant

    Very sadly, for all involved, my solution was to return the damaged QU-32 to the seller and buy a new Presonus 32S. Re-seating connections between boards didn’t solve the problem, so there seemed to have been deeper damage.

    #93834
    Profile photo of Patrick
    Patrick
    Participant

    I know this is an old thread, but did you happen to take any photos while you had it opened?

    FedEx just manhandled a QU-32 I bought used and faders 17-32 aren’t operating as motorized. Their position seems to be recognized, as I can move them in GEQ mode and see the white dot move, but they physically stay still upon mix changes. Wondering if you noticed a single power connector per bank that might have come loose in my case?

    #83481
    Profile photo of Patrick
    Patrick
    Participant

    Hi, Ken,

    I suppose it’s a long shot that you’ll see this, but…

    Is there enough rear clearance within the lid of the Gig Rig that you can keep XLRs connected to the back of the QU-16 that run to rack units in the lower section? That is, can you leave everything connected for travel?

    Thanks,

    Patrick

    #50427
    Profile photo of Patrick
    Patrick
    Participant

    Is anyone else seeing a rotation bug in Qu-You 1.70 for Android? When I launch in portrait mode, there are four controls in a 2×2 arrangement. When I rotate to landscape, there are four controls in a 4×1 arrangement, as expected, When I rotate back to portrait, I get two stretched controls and blank space, rather than the screen going back to the 2×2 arrangement.

    If you are also seeing this, can you please report it to tech support? I sent screenshots showing the very obvious bug, but tech support implied it won’t be shown to developers unless others report the same problem.

    (This is rather counterproductive, in my view, as a former software developer. If there is clear evidence and reproducibility of a bug on a particular platform, I’d want to know about it, since that bug may be less reproducible or manifest itself in less clear ways on other platforms, requiring a longer investigation cycle. I get the concept of shielding developers from every report that comes in, but a glaringly obvious, clearly documented and displayed UI bug… pass it along… you’ll be doing the devs a favor.)

    Attachments:
    You must be logged in to view attached files.
Viewing 4 posts - 1 through 4 (of 4 total)