-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to have a system-wide configuration file for Windows #1143
Comments
The idea of a system-wide config is that no matter where you are on the system and no matter who you are, you get the same config file. Your proposal is neither a system-wide, nor a user-wide config, as the location of the config depends on the location of the invoking process. This is not acceptable, sry. |
I agree with your definition and it’s like linux do.
On Windows we can either use the Windows directory (not recomended), the c:\programdata directory (but only since Windows 7) or the registry to store the system-wide configuration (to complicated and not portable).
If you want to use the c:\programdata directory you can use a win32 api function to locate it. Note that in Windows normaly, no hard coded path should be in the executable. This also apply for the "c:\\soundfonts\default.sf"" hardcoded in fluidsynth.
If your are interrested in this approach, I can search to modify the proposal in ordre to use the appropriate win32 API to locate the c:\\programData directory.
Note that jack for Windows for the asio plugin jack-router use my first proposal to place the jack-rooter.ini file together with je jack-rooter.dll.
An other alternative is to reword my proposal by:
Provide the ability to have a generic configuration file on a multi-user Windows OS.
And clearly specify:
It's no a system-wide approach as for posix-like OS because it's related to the invoked executable.
To be honest my goal it to have something alowing me to have a functioning fluidsynth on a Windows system that my family use. I don't want any body having to configure fluidsynth before playing music of listening midifile. The hardcodec "c:\\soundfonts\\default.sf2" is the main problem I encountered.
|
You probably mean I would prefer to go with the If the default.sf2 strikes you so much, I would be open to relocate this into |
Yes, I prefer having default.sf2 into c:\ProgramData\fluidsynth. But it is not so important if we have already a system-wide configuration file. Finaly the solution invoked yesterday reaches my goal:
I have tested and it works perfectly for my need: all users of my Windows machine can use a configured fluidsynth without having to define a user configuration file. |
Ok, thanks. I'll probably adapt your solution later, when I find some time. |
Implemented in 5c38efb and will be part of 2.2.9 |
I want a system-wide configuration file for fluidsynth on Windows
Linux has one on /etc but Windows does not have /etc or similar.
My proposal is to place the system-wide configuration file togheter with the fluidsynth executable.
I know that only administrator can modify this file, but with a junction you can put it elsewhere.
My solution
If you accept win32 api code in this part of program, the solution is very simple (see patch below).
HTH
The text was updated successfully, but these errors were encountered: