I think it is probably worth pointing out that many of the support staff/techs at Apple will still be unaware of the 2013 iMac and FD issue because the Engineering Team haven't yet issued a report on the problem. They haven't done so apparently, because at this time they are investigating the issue and trying to determine exactly what is the cause/fix and if it is, indeed, only limited to 2013 iMac's with Fusion Drives fitted. Initially they issued a report regarding driver issues with certain 3rd party Audio Interfaces... and that is the report that most of the CS/tech Depts are refering to when asked about an issue with audio and OS X and new iMacs..
The reason, as far as i understand, for the delay in issuing the updated report... (That the various CS/Tech departments rely on for info..) is apparently because, as I mentioned earlier, there are two issues that the end result is very similar but the cause is entirely different...
#1) 2013 iMac with FD causing "crackles and pops"
#2) Driver issues relating to USB3 and/or Driver issues relating to changes in Mavericks.. that also cause "crackles and pops"
(and, for the record, there is the third issue of Audio cutting out entirely after a period of time which seems to be limited to only certain 3rd party Audio Interfaces and 2013 iMacs with FDs fitted but is in addition to or instead of issue #1)
Initially the Engineering team were investigating this issue with the basic premise it was an Audio Interface/Drive/Firmware/hardware related problem... which indeed it is for some of the people reporting the sound issue... and would be extremely typical when a new major version of OS X is released.
It's only later on they began to get reports from people with 2013 iMacs with FDs who were having the same sounding issue but without any 3rd party Audio Interfaces installed/used... and only then they apparently realised there were indeed two/three different issues and of course some people who had 2013 iMacs with FDs also were using Audio Interfaces that needed driver/firmware updates too... so that added to the initial confusion and delays!
Needless to say, its going to take a little time for;
A) The Engineering team to work out whats going with Problems #1 & #3 and how to fix it successfully without causing issues elsewhere in the system.
B) The 3rd Party Devs to identify, correct, rewrite, test and then issue driver/firmware updates to fix issue #2
I would expect an updated report to be issued to the CS/Tech Depts once the Engineering Team have finished their initial "look/see' at issues #1 & #3... and then the CS/Techs will be more "up to date" with what's going on.
I will add that one of my clients called Apple reference issue #1 and the Tier 2/3 Tech he spoke to, was aware of both issue #1 and issue #2 though he had little info relating to #1... which was understandable.. given no reports have been issued yet from the Engineering Team.
I guess in summary, what i am saying is... patience people..(Though I completely understand the level of frustration being felt..)
These things dont get fixed over night... and it may be some time until they are fixed.. Maybe as quickly as a few days.. maybe as long as a couple of months.. No one knows yet... Things are still in the early stages of the process.
This is why the suggestion/workaround is being made to disable the FD for the time being..so you can carry on working with Audio... and when the fix is issued then enable the FD again... Its not a complex proceedure and so long as you make good backups it's pretty easy to re enable again later.
Some people are also reporting simply booting from an external drive and not using the FD at all, fixes the issue for them.. again as a temp workaround until such time as a fix is issued.
Disclaimer: I do not work for Apple in any sense.. I am simply relaying information that has been either provided to me from some of my clients who are having these issues and have spoken with Apple.. .. from discussions I have had with people at Apple myself in regards to these issues.. or from communications received from trusted 3rd party sources. As always,unless/until Apple release a formal notice/report regarding these issues, nothing is confirmed and anything related back by me, may contain inaccuracies for obvious reasons.
Cheers..