Activity for Martin
-
Martin posted a comment on discussion Feature Requests
Nope sorry, nothing was changed in this regard
-
Hey Tommy and everyone else, that is a very interesting find! Taking out the SdcFlags.AllowChanges might, however, break the program for some people. So I have tried to implement the following change: first it will try to switch the settings without SdcFlags.AllowChanges (should preserve refresh rate), if this fails it will try again with SdcFlags.AllowChanges (to make it more compatible to weird setups). I will push the code changes in a second but have also uploaded a beta version over here: https://sourceforge.net/p/monitorswitcher/discussion/requests/thread/c39199d104/...
-
Hi everyone, in the past months I did some smaller changes and implemented some possible optimizations based on feedback from individual users. Internally I changed some things around in how the Adapter IDs are matched to possibly make the switching more stable on some setups where windows would shuffle the complete internal display setup on each reboot. I did also add a change that could fix problems with restoring the monitor refresh rates. Because both changes are rather fundamental I do not want...
-
I'm using the predecessor of the G9 myself and have also observed similar issues. However, in my experience it's rather windows that gets completely confused and is really struggling to work with the monitor. When not in PBP I always had huge trouble with window sending the signal to the wrong monitor/cable so that I had to switch inputs in the monitor all the time. Non related to the profile switcher but still very annoying and the reason why I stopped using PBP and just disconnected the second...
-
Sharing of profiles between computers is not possible, the display paths and adapter settings are quite unique to each individual setup. Often already small changes to an existing setup wil require the creation of new profiles. So sharing profiles between computers won't work 99% of the time, sorry
-
If I understand you correctly then you also want to switch the input that the monitor is using? Unforunately that's not possible as far as I know, sorry.
-
I have no idea why this might be happening, all this button does is send a global SC_MONITORPOWER broadcast to the system. This maybe is some energy saving setting in windows. Could it be that the devices which get locked are notebooks with different energy saving settings?
-
You can do this already by using the Commandline version, see the wiki for details and examples: https://sourceforge.net/p/monitorswitcher/wiki/Home/
-
It simply sends all monitors into stand-by-mode
-
Hi Mark, can you please e-mail me again? I have not received your e-mail, must have gotten stuck in the spam folder or was accidentally removed
-
Thanks for the last bit of information, this is interesting and stirred an idea for a rather radial fix. I have uploaded here ( https://drive.google.com/file/d/1toczPb6iI_audbJemNuki791eIjFx6g5/view?usp=sharing ) another release of 0.8.0.0 (now called beta3) where I did quickly hack together a more radial solution to the Adapter ID matching. It now has a third matching method - what it tries to do is using the first method (that gets it party right), but as soon as it finds a matching Adapter ID...
-
Thanks for the last bit of information, this is interesting and stirred an idea for a rather radial fix. I have uploaded here (https://drive.google.com/file/d/1toczPb6iI_audbJemNuki791eIjFx6g5/view?usp=sharing) another release of 0.8.0.0 (now called beta3) where I did quickly hack together a more radial solution to the Adapter ID matching. It now has a third matching method - what it tries to do is using the first method (that gets it party right), but as soon as it finds a matching Adapter ID it...
-
That is great to hear that it actually improves the reboot problem. I will then do some more testing and maybe push it out as a new release over the christmas holiday. (Any more feedback from anyone else if 0.8.0.0 improves on their problems is still appreciated!) Regarding the issue with your monitor order, this is new to me and I can only guess on the reason. It's probably because windows API exports certain monitor pathways and that's what is stored in the profiles. When the monitors change their...
-
It might improve it even for single adapters (the problem is that windows is changing the adapter IDs on each computer restart and that the program has to somehow has to match the stored old setup with completely different IDs to the new IDs). Ever since the first release I have been trying to make this more and more stable, unfortunately it's a really messy thing what the Windows API does here in the background. For the debug out, it's currently not possible to dump it to a file when using the GUI...
-
The profile switcher should not be touching the icons, I guess this is a pure Windows mechanism. Maybe Microsoft changed something here with one of the bigger updates?
-
A while ago I did try to do some changes to the Adapter ID matching with the upcoming version 0.8.0.0. However, I never had the time to test the changes for stability so the new version was never release yet. If you want you can try it out and see if it maybe magically fixes your problems. I did upload the debug 0.8.0.0 release to my Google Drive for anyone who might be interested -> https://drive.google.com/file/d/1TVmFQ0zdaRA52rEAX19ln3ek5kmwoxeD/view?usp=sharing
-
Currently there is no option to let the profile switcher run on windows startup, you have to manually set this up by creating a shortcut in Users*\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup It's on my ToDo list to add an option for doing so, but I currently don't have much time to work on the program, sorry.
-
The MonitorSwitcherGUI.exe will also require the MonitorSwitcher.exe application, so it's better to not just copy it to the Startup folder but to create a link there (and make sure that the execution path is set properly). Then it should just work fine.
-
Possible improvement for adapter ID matching
-
Added cleanup of Zero array elements
-
Updated Windows SDK Constants and variables to most recent version
-
This is interesting, apparently Microsoft has added new constants to the Windows API and you have a system that is using those. I will have to get the latest Windows SDK and hope that I can find the required constants to implement them in the profile switcher
-
You can use the switcher via commandline as briefly mentioned here: https://sourceforge.net/p/monitorswitcher/wiki/Home/ If you want to figure out how it works, the source code can be found here: https://sourceforge.net/p/monitorswitcher/code/HEAD/tree/
-
You can already do this by using the command line interface described here https://sourceforge.net/p/monitorswitcher/wiki/Home/ Simply put a call to the profile you want into your windows autostart
-
The windwos API at this point unfortunately is very unspecific about the error message, so it's not possible to get any more details on why it failed.
-
Unfortunately there are some rare situations where the program fails to properly assign the saved profiles to current monitors. So far I could not figure out any solution, sorry - windows is really annoying on this end as it changes adapter IDs on each reboot,
-
That is quite weird and should not happen as windows should not allow to disconnect all monitors. Maybe your upstairs monitors are just not properly detecting that there is now an input (basically waiting on the wrong source)? What happens if you turn off and then turn on the monitors after the swichting failed? One thing you can try is to switch only to a single upstairs monitor before switching the second one on. Another thing I would advice is to assign hotkeys so that you can easily switch around...
-
Sorry that appears to be a bug. You can reset all hotkeys by going to C:\Users{UserName}\AppData\Roaming\MonitorSwitcher and deleting the file "Hotkeys.xml" (close the program before doing so).
-
Please make sure that it also works after a reboot! One thing I have observed is that the monitor profiles sometimes stop to work for reasons I don't understand. Maybe due to driver or settings updates in Windows. Just resaving the profiles then often fixes the problem.
-
If you can also set it with the window settings then it's just weird that it doesn't work and honestly I'm out of ideas what you could try. Unforunately I only have very old monitors with a fixed refresh rate of 60Hz and can thus not try this out myself. I'm really going on a strecth here on things you can try: 1) Try an older version (you will have to resave your profiles) 2) Try to update your monitor/tv drivers if possible, maybe even try older drivers - maybe you can find the once you where using...
-
The problem is that the tool is using windows API for saving and restoring the settingss and can thus only restore those settings which are accessible with windows tools. The only chance I see is that you somehow teach the windows display settings those missing modes, maybe by installing better drivers for the TV?
-
Hey Robin, sorry for the late reply. The vsync frequency is properly set in your config and is also loaded property in the debug output. So honestly I have no idea why it would still apply 60Hz. The only thing I can think of is that it tries to set it to 120Hz and when that fails it defaults back to 60Hz. Out of curiosity, can you set the 120Hz refresh rate by using only windows settings without the tool or do you have to use the NVIDIA settings panel for achieving that?
-
Added a console option "-noidmatch" which completely disables the matching of adapter IDs (for testing purposes only)
-
This is most likely a problem with the NVIDIA display driver. The monitor profile switcher can only save and restore those settings which can be set by windows. Another option might be that you have set a weird refresh rate in your config, <refreshRate> <numerator>59950</numerator> <denominator>1000</denominator> </refreshRate> just somehow sounds wrong. What is the final and working refresh rate you are setting the TV to using the NVIDIA control panel?
-
This is something that you have to fix with your windows setup. On a normal windows 10 setup it should work without any problems. Probably some firewall or security setting is blocking the application? What you can try is copy it somewhere else and only place a link in the startup folder.
-
That is ineed good to know, so something is going wrong with the Adapter ID Matching. That means there is hope :-) Unfortunately I do not have much time right now for working on the project, but please let me know how it behaves after a reboot (I would expect that it won't).
-
That must be then happen by the NVIDIA drivers, which would be very weird (and still nothing I can do about that), sorry
-
That is a very complex setup you have (from the point of the program). Unfortunately USB adapters have been always causing lots of trouble since those are apparently not that well supported by the windows API. I tried to come up with some windows API extensions for version 6 which made them work for simple setups, but apparently your setup is too much for the program to handle. Especially since loading does not work at all (even before a reboot) I don't know if I can come up with a fix for your problem....
-
I have no idea why it wouldn't work, are you using an display USB adapter? Can you give me some details what your setup is. How many display adapters (what type) and what is attached to it? Only thing I noticed is that there was USB mentioned in the XML, sadly there have been some problems with USB adapters before - but I was hoping that this was fixed now.
-
Very unfortunate that the alternative mode also fails for you :( Can you also attach the xml file of the profile you were loading? Does it only fail to work after a reboot or does it never work at all?
-
One thing that is for sure is that the program cannot copy and apply the NVidia Settings since those are handled in a special way by the NVidia drivers to which I do not have any access to. What the program does is the following, it uses standard windows API to save and restore all the windows monitor settings. It could be that for whatever reason the Windows settings for your setup interfere with the NVidia settings. I can, however, not imagine why this would permanently block the monitor settings...
-
Started work on graphical configuration user interface (work in progress)
-
Thanks for the feedback, the new version has now been released
-
Release Version 0.7.0.0
-
Updated version number
-
Profiles are saved in C:\Users{USERNAME}\AppData\Roaming\MonitorSwitcher\Profiles\ check the xml files if you can find any setting that might work. The problem however might be the difference between the nVidia video settings and the windows video settings. The program can only save those settings which can be set in the windows video settings, any special settings set by the nVidia drivers it won't be able to save or restore. So make sure you create the setup you are saving by only changing windows...
-
I have finally managed to implement an alternative monitor switching mode which might hopefully work in all those cases where the switching stops to work after a reboot. You can find the new version as a beta release here: https://sourceforge.net/p/monitorswitcher/discussion/general/thread/4d64ab84 please comment only in the beta release thread if the new test version fixes your problems. Please also make sure to resave your profiles with the new version as additional information are now saved in...
-
I finally managed to implement an alternative monitor switching mode which uses a new method for updating AdapterIDs after a reboot. This new mode is only used if the default mode fails (for any reason). Before releasing this experimental mode to the public I would like to gather some feedback on a beta version of 0.7.0.0 if this really works. You can download the Beta Version here: https://drive.google.com/file/d/0B-YmOiwzkYM-Z1lTV0pIbGJ5QUE/view Since now additional information are saved with the...
-
Added alternative monitor switching mode
-
Added writing and loading of additional monitor informations to profiles
-
I have started on the implementation but due to holidays and family matters have not finished it yet. But I can assure you that I'm still on it.
-
Sorry, still haven't had the time to implement this. Not sure if setting the resolution is possible at all. I doubt it as it would enable lots of security problems.
-
Thanks for the detailed report of this very strange issue. Unfortunately I really think that this is just a bug of windows. Probably because when you would apply this change in configuration manually windows would do it step by step and not applying all changes at once. Sadly there is nothing I can do to really fix this, the saved monitor configuration is very complex and I don't see any way at the moment to predict this behaviour and fix it. Sorry, but it seems like you have to get use to switch...
-
Added new category for calculated stats
-
Just a quick status update, I have implemented the API calls for getting the user friendly names already. Next step is implementing everything in the core of the program. Sadly I don't have much time at the moment, but I hope that I can release a new version within the next 4 weeks.
-
I'm working on improving the algorithms of the program right now, please try again the next release which should be finished within the next 4 weeks (hopefully)
-
Implemented getting of additional monitor information
-
Various smaller changes
-
Update API definitions to latest Window standard
-
Thank you very much for that suggestion, I do not have much time to work on the project at the moment but this definetly could be a solution. It might take me one or two weeks to get this to work, but I will definetly try it out!
-
Very weird debug output from both of you. Honestly I don't see what is going on. Can you try one more thing? Setup the profiles and get the debug output when switching before you reboot the computer. Then reboot the computer and get the debug output again. So basically two outputs, one that still works and one that does not after the reboot.
-
First Release - Version 0.2.0.0
-
Home
-
Many minor fixes and changes
-
Home
-
Home
-
Home
-
Home
-
Better training data based on Verdana
-
Added export options as image and text file
-
Added filtering of single stats items
-
Fixed having to double click popup
-
Added options button to disable/enable display of category labels
-
Added edit optin for single player view
-
Added button to remove player(s)
-
Changed table display to DataGridView
-
Added version information to title
-
Added support for brown headers aswell
-
Added merging of all data of a single player in multi player view
-
Changed player name column in parse window to update while parsing
-
Added parsing of kills and might
-
Added extraction of header area
-
Even Faster Screenshot Parsing
-
Faster Screenshot Parsing
-
Added category parsing
-
Added paring of leaders, colosseum and others stats
-
Added About/Donation window
-
Added clear session button
-
Added display of categories
-
Added parsing of might stats
-
Added filtering of categories
-
Added CheckBoxComboBox component to solution
-
Finalized loading of session data
-
Cleanup of packages
-
Initial Commit of Alpha Version Code
-
Home
-
Can you try if the old version is still working (just download it again). Please try to make sure that loading the profiles also does not work when using the command line utility (see the wiki). You have to run the command line version from a windows command prompt (cmd.exe)
-
Sorry for the long delay, I was not aware that sourceforge is having any moderation function (I do not receive notifications on that). The problem with the flucutating low part is that on each reboot the Adapter IDs change (for whatever stupid reason). What the Program tries to do is compare the saved settings to the current settings and create a working mix of both worlds (old settings with ne adapter IDs). For some reason this is not working on your system. What you can try is to use the latest...
-
ah okay, that seems to be part of the NVIDIA driver and therefore I can't access those settings by just using Windows API, sorry
-
Try the latest version, this should fix the problem
1 >
