RME as stated that the new firmware has nothing to do with performance per se, but has mostly to do with win8 compatibility and some DSP fix.

With that said, I have a line6 dream rig that has all kinds of firmware updates with all of the items included in the kit. Line6, don't get me started on them either, has stated that you may have to reflash an existing firmware twice to make sure it took on the unit. My thoughts were, you have to be kidding. But they weren't.

I do not know if that is what happened here with my UFX or not. I do know that before X3, I had zero pops and crackles during recording or playback. Seems to me several RME users are the majority of reporters on this issue with X3. I am glad it isn't just me too. :-D

It would be nice if the bakers could borrow a RME FF UFX, UCX or one of their other higher end interfaces to see what performance testing they can do to help us RME users out. 

trnfoot
I am using the UFX in X3 Via firewire and have not seen these issues. I know its pretty basic and you are probably already aware, but those of you having FW issues make sure you are using a Texas Instruments FW chipset.

Thanks for the info.  Very interesting.  Do you mind sharing some more info?  Are you working with audio, midi or both?  # tracks?  Settings?  
 
Yes my mobo uses TI FW chipset.  

Which Firewire TI chipset?...cause they are not all the same chipsets...and TI (texas Instruments make a few chips for firewire)...not all Ti chips work well with all devices...So, what does the fire face manufacture suggest to use for the Fireface ufx?..=TI chipset xxx1324....and follow suit I say...If that does not work...Perhaps updating the firewire computer interface to a 800/400 1394b version card, may gain better legacy Windows Driver for win 8, and disabling onboard firewire chip...may help.

I neglected to update this thread.
This seems to go away on reboot.
 
Today I updated the firmware to the new one, and i'll test it to see if its bulletproof.

Possibly solved!  I decided to try some different drivers instead of ASIO.  None worked very well, all having various glitchy audio.  But once I went back to ASIO my performance was *much* better.  The clicks when arming or disarming tracks is gone.  The lag when arming tracks is gone.  Closing the preferences window now takes half a second, not 3-4 seconds as before. Overall it is like I got a nice driver update.
 
The only thing I can think of is that with ASIO Sonar does not run its sound card profiler, which it does with every other type of driver.  So as I changed drivers the profiler ran several times.  Perhaps running the profiler did something to smooth out the ASIO communication.
 
In any event, I am very pleased, but wary the fix could be temporary.  I am very curious if this would help others who have had similar problems.  Also curious if anyone has a logical reason why this should work, as I though using ASIO drivers meant profiling the sound card is not necessary.