General information about addons
Starting with 1.70 drivers I've implemented the option to apply addons at UNi Xonar driver installation procedure.
This could be useful in various scenarios like:
- applying 3rd party drivers mods more easily (like Alexas addons once they are made specifically for UNi Xonar Addons option)
- installing a different version of a component, as in specific cases newer components are not always better, for example a C-media Panel version that doesn't have the stereo upmix turning off bug like "c-media panel v1.62" addon.
- a method of distributing newer audio drivers that might not be ready for general release.
- replace default ASUS Panel Skin with your desired custom one without doing this manually every time you install the drivers.
About the addons functionality:
- Addons install along side with UNi Xonar drivers and not separately.
- "Apply Addons" check/uncheck state isn't saved by UNi Installer.
- Files from the addons will replace the files that are included in UNi Xonar drivers during the setup preparation routine just before the installation starts.
- Once launched, the UNi Xonar Installer will detect and show the content type of the files that are located in the Addons\ folder and that are about to be loaded if you check the "Apply Addons" option (pic).
How to install addon packs:
- Download the desired addon.
- Save it to the directory where the UNi Xonar driver installer is located , for example "D:\UNi Xonar Drivers\UNi Xonar 1818 v1.70.exe". (pic)
- Launch addon and click extract.
- Launch UNi Xonar driver installer, if you've extracted the addon correctly , "Apply addons" option from the installer show the type of content that will be loaded. For example, for C-media panel addon, in the UNi Xonar Installer it will show "Apply addons: DLL"
- Click install.
How to add your own custom files
In the Addons folder you will have to make a new folder corresponding to the custom files you want to load. There you will copy the custom files. The following folders are recognized:
- dir\ -> reference; where UNi Xonar installer is located
- dir\Addons = ..\
- ..\XP driver\ -> location for WinXP custom driver files (customized .inf's, additional .dll files, addon_youraddonname.ini )
- ..\W7 Driver\ -> location for Win7/8/10/11 custom driver files (customized .inf's, additional .dll files, addon_youraddonname.ini)
- ..\Skin\ -> location for custom ASUS Panel Skin files
- ..\SetupBefore\ -> load other applications that you want install before installing audio drivers, these are called from a setup.bat file that you will have to make
- ..\SetupAfter\ -> load other applications that you want install after installing audio drivers, these are called from a setup.bat file that you will have to make
- ..\INI\ -> load a custom cmudaxp.ini
- ..\DLL\ ->location for ASIO, Cmedia Panel components
- ..\CustomApp\ -> Asus Audio Center folder
- ..\Installer\ -> location for driver installer setup
Dynamically alter driver .inf files (New capability starting with 1.75 drivers)
Starting with 1.75 drivers you can dynamically change the driver .inf files (e.g. XonarDX.inf) included in the UNi Xonar driver installer before they are installed.
In order to change the driver .inf files you need to create a addon_youraddonname.ini file in Addons\W7 Driver or Addon\XP Driver folder depending which OS driver files you want to change. Here is a commented sample INI file. Applying the addon_sysfx_sample.ini through UNi Xonar installer would change the driver files like this XonarDX.inf file.
When launching UNi Xonar installer, selecting "Apply addons: ..." checkbox and clicking next will display a new page that shows the detected addons_*.ini files that the user can select to apply to the drivers (pic).
How to make an addon package for distribution:
- Create a clean Addon folder
- Create subdirectory corresponding with the type of content your addon in based on
- Copy custom files to the subdirectory (pic)
- Addon folder ->Add to archive (pic)
- Set name and create SFX arhive (pic)
Bayilo Kanto09 Apr 2013 @ 20:43
I do have three questions:
1) Within the list of the Addons folder configuration you have mentioned, which one should I use to include a registry file (e.g. *.reg) that is intended to update the registry automatically after the driver installation?
2) The previous Addons provided by Alexas had a different sub-folder structure than what you have listed. How should we change it to make it work perfectly with your new proposed addons folder structure?
3) Alexas Addons has a driver already included in it. Should we delete his driver within his Addon folder in order to avoid a conflict with your new driver?
CarvedInside10 Apr 2013 @ 00:02
1) dir\Addons\SetupAfter\ , make a empty setup.bat file , edit the setup.bat file and add "mycustomregfilename.reg". You can also add registry entries with command line "reg add" as well but parameters are a little bit more complicated.
2)3) From the Alexas addons you should only copy cards .inf files and the additional dlls that are not included in the default drivers. You copy them from SoftwareDriver\Driver\ to \dir\Addons\W7 Driver\. Do not copy audio driver files as they will override the Audio driver files included in the UNi Xonar and so you will end up with 1.63 drivers installed.
You will also need the DHT4.MSI (or however its called) which you should copy to Addons\SetupAfter\, you can call it by adding a new line in the setup.bat previously created.
If you have problems coming with something workable, my advice would be to wait for a proper implementation from alexa or someone else.
PTmax10 Apr 2013 @ 18:55
If someone managed to make Alexa's mods work with this, without overwriting driver files, I would be delighted if he/she shared the whole procedure with us....
Cu12 May 2013 @ 14:16
Hi, i create this skin addon but when install, this skin don't apply correctly, then copy all files manualy to skin folder in customapp folder from this unixonar folder driver in Program Files for correct apply for this skin.
The files are not copied accordingly.
Aqui esta el addon: https://dl.dropboxusercontent.com/u/6210632/Xonar/Zaom%20White%20Skin.exe
Sharky15 Jul 2013 @ 04:09
How to install new version of front panel switch? I tried to extract it in several ways, but always with the same result: no detected any addon. Soo... way?
CarvedInside15 Jul 2013 @ 16:25
It is because that is not a addon, it is a standalone application. You run it each time you want to switch.
Bulle31 Oct 2014 @ 15:20
Where are these addons? I cannot find them.
CarvedInside01 Nov 2014 @ 23:06
User created addons (like DHT) can be found here. But a new DHT addon that is compatible with 1.75 drivers is not ready yet.
Evil Norman21 Jul 2015 @ 01:00
Hi, I'm new commenting but I've been actively browsing the site for a while now. I've got an Asus Xonar D2 and I've installed several versions of the UNi but lately I've been having an issue. When I perform a clean driver install I choose the basic setup but when the installer indicates it's done and needs to reboot the main UNi driver installer window is stll open in the background and refuses to close. I have to force it to close in order for the system for finish the reboot process. Not sure why it started but I'm using the 1822 v1.75a along with the Xonar Switch 1.71s. I'm wndows 7 64bit sp1, 8 gigs ram, etc. Any help would be apreciated
CarvedInside21 Jul 2015 @ 22:18
You've posted the comment under the wrong page. The correct place for this issue would be the main UNi Xonar page.
Now getting to the problem you are reporting. You should know that restart is not mandatory and almost in all cases it is not needed. You should not restart when asked by the driver installer, UNi Xonar installer still has tasks to do and that's why it's not closing. I've written the suggestion not to restart in the UNi Xonar installer help.
mousse25 Jun 2016 @ 14:07
How to install addons? It says "none" and I extracted all the zip file into dir/addons (dir is the driver .exe installation folder).
CarvedInside27 Jun 2016 @ 19:45
Which addons do you want to install? Which Uni Xonar driver version are you installing?
Maybe you've extracted the zip contents to separate folder in Addons directory (e.g. "Addons\addon_name\W7 driver\") instead of extracting them directly (e.g. "Addons\W7 driver\").
If that's not the case and you still haven't figured out what the problem maybe you can upload or send me screenshots of the Addons folder contents.
Alejandro Rigali01 Oct 2016 @ 07:47
Ok, I found an issue trying to install addons. Seems like if you have the Uni-xonar installer buried over a long path name (or in a path with spaces on it, not really sure), addons are not detected. I ran the installer multiple times and it found no addons each time, until I moved all files to c:\temp, then the option to install the addons appeared after it, Hope it might be usefull for others.
Best regards, thanks for the great job, keep rocking.
CarvedInside01 Oct 2016 @ 16:12
Thanks for the feedback. Can you give me the full path that didn't worked? In my testing I used "G:\DRIVER CMEDIA\UNi Xonar 1822 v1.75a\Output\Test path zero 1 two 10034 long\down the rabbit hole\" and that does work. Tell me your OS as well.
Jason21 May 2017 @ 22:52
this doest work i swear i try it for 3 hours ...i read step by step but doest work
CarvedInside22 May 2017 @ 01:47
What exactly are you trying to do? If you show me the files you are using I could look into it.
Chhagan03 Dec 2022 @ 15:05
When I install Asus xonar dg driver with addon sound not come through the sound card but without an addon sound comes. I use addon 1777 drivers + ASIO1.0.exe and driver UNi-Xonar-W10-1825-v1.81a-r2.exe. Kindly help!
CarvedInside07 Dec 2022 @ 06:53
If you followed the instructions correctly, it could be that 1777 audio drivers are to old to work with Windows 10 and Windows 11. I sincerely don't even understand why you need ASIO 1.0. Go with ASIO4ALL or FlexASIO.
I noticed your previous comments here and here that might be the same issue. The first time I tried to help you and asked some questions you didn't bother responding, and then came back with what looks like the same issue. That's not alright at all and neither is bringing an issue time and time again.
I don't have the time and energy anymore to even test if "1777 drivers + ASIO1.0.exe" does really not work on Windows 10/11. So please don't ask for help with this issue.