Originally Posted by Sonorous
I'm also not having any success changing any values in regedit.
I'm currently using an ASUS G53SX with Windows 7 and the version of the Realtek driver I'm using is V188.8.131.5234
As Eliah stated, no Pins show up in my regedit due to what I assume is some recent update to the driver. This is how mine looks:
I've tried adding a variety of pins using the data "02 00 00 00" and "04 00 00 00" and none of them work.
The last time I recall having access to jack retasking was both on a desktop and laptop that initially came with Windows Vista/7 on them but I had reformatted and installed Windows XP on both of them.
It seems that the GUI of the Realtek settings is vastly different on XP than it is from its Vista/7 counterpart - even if the same version of the driver is installed on either operating system.
I have never been able to gain access to jack retasking in the Vista/7 GUI - this one (this is a screenshot of the GUI from my own computer):
But I've always been able to do it in the XP GUI - this one (just a picture from Google but it's the same way it has always looked to me on XP):
Is there any way as far as anyone knows to force an install of the XP version/GUI?
Or perhaps something else can be done in besides changing/adding Pins and binary data in regedit to get retasking to work.-EDIT-
I'm also curious if my case is more complex because of my laptop. You'll notice in the image I posted of my Realtek GUI that my 2 jacks are both black instead of coloured like everyone elses seem to be. I'd just like to state that the laptop itself does in fact have 2 real physical jacks, both are actually coloured/painted black, but 1 has a headphone icon engraved over it, and the other has a mic icon engraved over it.
Just out of curiosity I decided to uninstall and reinstall the driver and Pins do now show up in regedit.
Pin01 shows up with the data "01 00 00 00"
Pin04 shows up with the data "04 00 00 00"
I'd like to clarify I haven't touched or modified these yet - this is how they show up after a fresh install and reboot:
This is throwing me off a little since these don't exactly match all the Pins and data values with what a previous user listed in this thread.
Tnitro said that "Pin01" is a rear black-coded RR RL jack and "Pin04" is a rear pink mic jack
And a couple users said that data values "01 00 00 00" are for mic-in and "04 00 00 00" are for front speakers
So by default if my:
"Pin01" has the data "01 00 00 00" that means my "rear black-coded RR RL" jack is set to "mic-in"
"Pin04" has the data "04 00 00 00" that means my "rear pink mic" jack is set to "front speakers"
Pin04 having the hex value 04 00 00 00 is what's throwing me off. Why would a mic jack, by default, be set to front speakers?
Mind you I'm on a laptop and as I stated in my previous post both my jacks physically appear black, and virtually appear black in the GUI on Windows 7. So your colour coding for these hex values don't or rather can't really apply to me.
Where are you guys "figuring out" what each hex value means? I'm not saying you're entirely wrong but I'm starting to think the hex values don't correspond to the same thing on everyone's computer. Only a few people have reported having success changing their regedit based on the hex values some users are providing while a handful of others here and on other forums are reporting it does nothing for them.
There are two things I've come across on other forums that may be of some use to people here:
One user said that after rebooting their computer after changing regedit, regedit does not retain the changes they made and restores the hex values back to their defaults because the Realtek driver application is set to load on startup and changes the regedit values back to their defaults. I'm sure the name of the process varies from version to version/operating system to operating system but for me it's RTHDVCPL.exe - I'm sure it's the same for some others too.
Another user said that the ability to retask jacks was removed sometime on/after version R2.5. I'm not sure if this is true and I have yet to test this myself yet. I'll post back with the results once I find an older version to try it with.