2006-02-25, 09:00 PM
pBS: the easiest place to look for those pin names is in the driver install package. With my drivers the pins are defined in Prop7134.dll. If I open it up in a hex editor and search for P?r?e?v?i?e?w then it only finds 3 copies (same if I search for C?a?p?t?u?r?e) - the ?'s are because the text is unicode and has null's between each letter. It's possible that GraphEdit gets the pin count wrong because of the two pins with the same name. If you look at the GraphEdit xgr files, you'll notice it also uses the Pin names, so that wouldn't work either.
In fact, check that. See how GraphEdit tells the difference, if it can. Then try apply the same change to the config-recorders.xml file. When you re-open the graph with all the settings, have you been using gfr or xgr, and is the audio capture pin restored correctly?
Yea, I've seen reports everywhere that the ATI encoders have much lower CPU usage. I'm using the 'tweaked' ones that don't require an ATI card to be present.
JawBone: You need to set it to whatever source you're using, that way it can mute and unmute the device for you. It also uses it to select which source is used for recording. Try opening the windows mixer while you're in timeshifting mode and see if changing anything will make the sound start working. You will also need to swap the mixer to recording settings (via options > properties) to change the way sound is recorded, compared to playback. It should mute the playback mixer, but unmute the recording mixer. This might be the same switch on old card, can you confirm?
kmtrue: can you reduce the amount of code changes to maybe just a Stop, Run and see if it works? i.e. is the double tuning required? I'm tempted to make the code ignore the 'output' vs 'input' story. It really is a hack that it assumes that the DirectX mixer is named the same thing as the Windows Mixer control. Can you send a dump of your logs so that I can see exactly what needs tweaking. If you want you could also send a patch for the plugin
In fact, check that. See how GraphEdit tells the difference, if it can. Then try apply the same change to the config-recorders.xml file. When you re-open the graph with all the settings, have you been using gfr or xgr, and is the audio capture pin restored correctly?
Yea, I've seen reports everywhere that the ATI encoders have much lower CPU usage. I'm using the 'tweaked' ones that don't require an ATI card to be present.
JawBone: You need to set it to whatever source you're using, that way it can mute and unmute the device for you. It also uses it to select which source is used for recording. Try opening the windows mixer while you're in timeshifting mode and see if changing anything will make the sound start working. You will also need to swap the mixer to recording settings (via options > properties) to change the way sound is recorded, compared to playback. It should mute the playback mixer, but unmute the recording mixer. This might be the same switch on old card, can you confirm?
kmtrue: can you reduce the amount of code changes to maybe just a Stop, Run and see if it works? i.e. is the double tuning required? I'm tempted to make the code ignore the 'output' vs 'input' story. It really is a hack that it assumes that the DirectX mixer is named the same thing as the Windows Mixer control. Can you send a dump of your logs so that I can see exactly what needs tweaking. If you want you could also send a patch for the plugin