Right. You just learn of this problem today
Says who? I haven't cared to research specifics in the past because it hasn't affected me personally or professionally. Tracking down the source of this alleged "bug" isn't difficult, and again, that information paints a picture. Bus resets have nothing to do with audio per se, but simply with data negotiation. This is your first clue.
I do have a lengthy track record of dealing with standards bodies and implementation disputes, and it has been influential in discussions on this forum and others. On the other hand, you have submitted nothing to suggest a contrary interpretation. You have also egregiously misinterpreted industry rating systems and displayed a basic unfamiliarity with internal procedures.
then spend 60 seconds reading one source of information
Again, says who?
on a subject that's been tossed around online in great depth for over a year now and you immediately come to the conclusion that the problem is caused by the audio manufacturers.
That's not the conclusion I drew at all. All I am saying is that there is no evidence that the Agere chipset is faulty, and that audio interfaces have a long history of compatibility problems with various 1394 controllers, because they have always implemented based on a reference design rather than the standard.
Consider what is more likely: a bug in a general controller with an otherwise unblemished track record or a bug in a specialized controller? Now, look at the nature of the bug. Does it affect all devices, all devices using the same connection, or even all units of an affected device? If the problem can't be reproduced in other types of controllers or even in other models of the same type, the defect,
if there is a defect at all and not just a benign incompatibility, is probably in the specialized controller.
And for your information, the specialized 1394 controllers in question (along with some of the audio interface hardware) are made by many of the same companies as the computer chipsets--so don't even try to accuse me of selecting a side in this ridiculous little battle of yours.
Can you cite even one credible online source that's reached the same conclusion as you have?
Can you cite one credible source implicating Agere based on theory other than "it worked before, so it must be the computer chipset?" I have not yet encountered a credible source making a conclusion of any sort, nor have any alleged an Agere fault as you have. The lack of a detailed inquiry is telling. Why you are so convinced, absent any evidence at all and despite all contrary indications, that it's not the fault of the audio 1394 controller or audio interface, is a complete mystery.
You can find compatibility problem reports for every Firewire chipset manufacturer, including TI, with audio interfaces. In some cases, there are physical errors, such as voltage mismatches. However, and please read the following carefully, because you have continually ignored it: an audio controller
sometimes triggering a bus reset in
some products using that controller, but
no other controllers causing that problem,
does not point to a computer chipset problem unless you have other information.
As I have repeatedly requested, if you have any evidence, any at all, please share it. So far all I've received from you is a failure to read and understand.
