XR341ck - how to prevent automatic input cycling when no signal received?

wzzt
wzzt Member Posts: 3 New User

When the time passes the threashold with the Windows setting of "When plugging in, turn display off after X minutes" set (defautl 10 minutes), my Acer XR341CK keeps switching between all the inputs endlessly.  Each time it passes displayport my speakers play a devices connected then device disconnected sound.  I believe this issue can be resolved by forcing the monitor to remain in displayport input even without a signal detected.

 

So how can I prevent automatic input cycling when no signal is received? I can't find it in the screen options i've went through them all several times.

Answers

  • Qwixt
    Qwixt Member Posts: 6 New User

    I found that if I set the monitor to Extend in the Daisy Chain setting, and leave the monitor powered, then it will go into power saving mode properly when put into sleep mode or when signal is lost (computer shutoff). The bad news is that 16.1 and 16.1.1 drivers show freesync not supported if the monitor is set to "Clone".

     

    I hate this monitor.

     

  • mdm
    mdm Member Posts: 15

    Tinkerer

    Interesting haven’t tried this, and when set to Extend I get this new page?!

     

    1.PNG

  • Qwixt
    Qwixt Member Posts: 6 New User

    I have had my monitor in extend mode since I first got it because of the cycling through input issue. So I have always seen that extra tab showing DP Diagnostics. I only came to this forum because I was wondering why freesync was not working after 16.1 drivers, then I discovered it was a  difference between clone and extend settings.

     

    How screwed up is a monitor that can't sleep properly? lol

     

    I did report the issue to AMD, so if you notice it happening to you as well, you should report the issue as well so it gets more attention and AMD can fix the issue, since freesync was working fine in extend mode in 15.12 and earlier. It would be nice to get an updated firmware for this monitor, but there is no way I would risk sending this monitor in to Acer and playing the monitor lottery again. I knew I shouldn't have kept this monitor.

     

    If the next driver update from AMD does not correct the issue, then I might write my own screensave for win 10 to drop brightness and contrast to 0 or whatever is the lowest it can go.

     

  • mdm
    mdm Member Posts: 15

    Tinkerer

    I think firmware can’t do anything for this monitor, it is probably the DP standard (1.2a) pushed near limit that is the issue, an/or AMD drivers...?
  • Qwixt
    Qwixt Member Posts: 6 New User

    I set the monitor to "clone", and that DP diag page does go away.

     

    Not sure if anyone cares at this point, but resolved my issue good enough.I was looking into writing a screensaver to dim the screen as much as possible, and I came across some C++ code for turning off the monitor via DDC/CI. When I used that code to power off the monitor, the cycling no longer happened. It does not completely turn off the monitor like hitting the power button. Behaves just like sleep as far as I can tell.

     

    So I used that code as basis for the screensaver, and added some code to capture mouse and keyboard input to exit. Now, instead of using windows power option to turn off display, I use this screensaver. During reboots, it will still cycle through the inputs, but that's not important to me.

  • Omegaclawe
    Omegaclawe Member Posts: 5

    Tinkerer

    So... I feel dumb with how long it took me to get this working. I had it working for a while with the DP passthrough set to "Extend" instead of "Clone", and doing some hacky things to make freesync still work, but this didn't last forever.

     

    Then, two days ago, I hit the wrong button, and changed the input manually. I manually changed it back to DP. Now, when the monitor turns off, it doesn't cycle; it stays on DP. Sure, I've got to do this if the monitor ever actually loses power, but... the answer is so simple I can't believe I spent the better part of a year not even having tried it. I can more or less set my other settings entirely independant of this, too, for whichever DP passthrough mode or what have you I want.

     

    Tl;dr - Manually selecting the input solved my problems.