Processing Ajax...

Title
Close Dialog

Message

Confirm
Close Dialog

Confirm
Close Dialog

Confirm
Close Dialog

User Image
Christian Treffler
42 discussion posts
Hi,

I still have the problem as described in:
Triggers sometimes don't work

But I think I know now what the issue is. Part of the trigger conditions are a match of monitor profile. And apparently one profile sometimes is "forgotten".
I have a keyboard shortcut to load that profile. The result is in attachment 'ProfileLoaded.jpg'. The profile is loaded and I get what I expect on all three monitors. But when I check the monitor profiles none of them is highlighted (See attachment 'MonitorProfiles.JPG').
So DF loads the monitor profile successfully, but then forgets which profile is currently active. And any trigger relying on that profile is not executed.

This happens only sometimes. Sometimes I see the profile 'Lab 3 Monitors' highlighted and then the trigger works.
Another observation, but this needs to be confirmed with multiple tests:
When I move with my laptop from one docking station (Work Desk) to the other (Lab), DF sometimes recognizes the new environment and loads the 'Lab 3 Monitors' automatically. And then it doesn't forget that. Sometimes I need to call that profile by a keyboard shortcut. And then the profile is loaded, but then forgotten.

Any idea what can cause this?

Regards,
Christian
• Attachment [protected]: MonitorProfiles.JPG [42,358 bytes]
• Attachment [protected]: ProfileLoaded.jpg [5,146 bytes]
Aug 24, 2018  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
It's possible that some of the display values are slightly different on the different docking stations. When you load the profile, and it doesn't show as detected, can you try either overwriting the profile (Monitor Config > Save > Profile Name), or saving it as a new one, and then see if loading/detecting it works correctly after that?
Aug 24, 2018  • #2
User Image
Christian Treffler
42 discussion posts
Hi,

it took me a while to get this testing done. So here's the feedback:

I have two identical docking stations, on my "Work Desk" and in the "Lab". Both have 2 external monitors connected, but different resolutions. On putting the laptop in either docking station DF correctly recognizes the connected monitors and activates the correct monitor profile. But in the lab it sometimes "forgets" the profile after adjusting.

I tried overwriting the profile long time ago, without success. Recently I deleted the profile 'Lab 3 Monitors' and saved the settings as new profile 'Lab_3_Monitors'. That worked for some time, but today I have the issue again: Plugged the laptop into the docking station, both monitors recognized, profile loaded. But then it's not showing an active profile and triggers don't work.

Now here's a point: Both monitors are also connected to a desktop PC. And one of them was still showing the input from that PC. Nevertheless, it was recognized correctly by DF. When switching inputs on that monitor it immediately shows correct setup.
I removed the laptop from the docking station and put it in again. Now DF shows 'Lab_3_Monitors' as active profile. I'm confused: Even with monitor switched to the wrong input, DF immediately recognizes that the monitor is connected and sets the monitor profile. But doesn't show that profile as active?

Regards,
Christian
Sep 10, 2018  • #3
Keith Lammers (BFS)'s profile on WallpaperFusion.com
The next time you can reproduce that, could you send me a copy of the output from the program below, once when the monitor is on the PC input (and the profile is not detected), and once when it's on the laptop input and detected correctly?

http://www.binaryfortress.com/Files/DisplayFusion/BFCustomerTest.exe

Thanks!
Sep 10, 2018  • #4
User Image
Christian Treffler
42 discussion posts
Here you are, 4 files in a zip file.
The files which start with a 'P' are from tests where the monitor profile was not forgotten. The one which start with an 'F' are the ones where problems occurred.
Monitor 1 is the in-built laptop monitor.

Best Regards,
Christian
• Attachment [protected]: DFTest.zip [12,041 bytes]
Sep 11, 2018 (modified Sep 11, 2018)  • #5
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Thanks! It looks like when it's not working, it's not getting all of the info from the monitor. When it's fine, the monitor model and serial are correctly detected. When it's broken (I'm assuming when the input is on the PC instead of the laptop) those are missing, which is why the Monitor Profile isn't matching any more. The monitor must not send that info back to the laptop until it's on the right input.
Sep 13, 2018  • #6
User Image
Christian Treffler
42 discussion posts
Thanks.
I had a look at the outputs myself and saw the differences.
Right now I have stored two profiles with slightly different names for this setup. And identical triggers for both.

Best Regards,
Christian
Sep 13, 2018  • #7
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Ah ok, that's a good workaround then :)
Sep 14, 2018  • #8
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(-)  Login to Vote(-)