The accompanying condensed consolidated financial statements include the accounts of Avid Technology, Inc. and its wholly owned subsidiaries (collectively, "Avid" or the "Company"). These financial statements are unaudited. However, in the opinion of management, the condensed consolidated financial statements reflect all normal and recurring adjustments necessary for their fair statement. Interim results are not necessarily indicative of results expected for any other interim period or a full year. The accompanying unaudited condensed consolidated financial statements have been prepared in accordance with the instructions for Form 10-Q and, therefore, do not include all information and footnotes necessary for a complete presentation of operations, financial position and cash flows of the Company in conformity with accounting principles generally accepted in the United States of America ("U.S. GAAP"). The accompanying condensed consolidated balance sheet as of December 31, 2010 was derived from the Company's audited consolidated financial statements, but does not include all disclosures required by U.S. GAAP. The Company filed audited consolidated financial statements for, and as of, the year ended December 31, 2010 in its 2010 Annual Report on Form 10-K, which included all information and footnotes necessary for such presentation. The financial statements contained in this Form 10-Q should be read in conjunction with the audited consolidated financial statements in the Form 10-K. Certain prior period amounts have been reclassified to conform to the current year presentation.

The Company's preparation of financial statements in conformity with U.S. GAAP requires management to make estimates and assumptions that affect the reported amounts of assets and liabilities and disclosures of contingent assets and liabilities at the dates of the financial statements and the reported amounts of revenues and expenses during the reported periods. The most significant estimates reflected in these financial statements include revenue recognition, stock-based compensation, accounts receivable and sales allowances, inventory valuation, goodwill and intangible asset valuations, fair value measurements and income tax asset valuation allowances. Actual results could differ from the Company's estimates.

In October 2009, the Financial Accounting Standards Board ("FASB"), issued Accounting Standards Update ("ASU") No. 2009-13, Multiple-Deliverable Revenue Arrangements, an amendment to Accounting Standards Codification ("ASC") Topic 605, Revenue Recognition, and ASU No. 2009-14, Certain Revenue Arrangements That Include Software Elements, an amendment to ASC Subtopic 985-605, Software - Revenue Recognition (the "Updates"). ASU No. 2009-13 requires the allocation of revenue to each unit of accounting using the relative selling price of each deliverable for multiple-element arrangements. ASU No. 2009-13 also amends the accounting for multiple-element arrangements to provide guidance on how the deliverables in an arrangement should be separated and eliminates the use of the residual method by establishing a hierarchy of evidence to determine the stand-alone selling price of a deliverable based on vendor-specific objective evidence ("VSOE"), third-party evidence ("TPE") and the best estimate of selling price ("ESP"). If VSOE is available, it is used to determine the selling price of a deliverable. If VSOE is not available, the entity must determine whether TPE is available. If so, TPE would be used to determine the selling price. If TPE is not available, then the entity would be required to determine its ESP. ASU No. 2009-14 amends ASC Subtopic 985-605 to exclude from the scope of software revenue recognition requirements sales of tangible products that contain both software and non-software components that function together to deliver the essential functionality of the tangible products. The Updates also include new disclosure requirements on how the application of the relative selling price method affects the timing and amount of revenue recognition. The Updates must be adopted in the same period using the same transition method and are effective prospectively, with retrospective adoption permitted. The Company adopted the Updates prospectively on January 1, 2011 for new and materially modified arrangements originating after December 31, 2010.

Prior to adoption of the Updates, the Company generally recognized revenues using the revenue recognition criteria of FASB ASC Subtopic 985-605, Software - Revenue Recognition. As a result of adoption of ASU No. 2009-14 on January 1, 2011, the Company now typically recognizes revenue using the criteria of FASB ASC Topic 605, Revenue Recognition. Historically, the Company was generally able to establish VSOE for undelivered elements in multiple-element arrangements as allowed by ASC Subtopic 985-605 and, therefore, could typically recognize revenues for each element of multiple-element arrangements as the element was delivered. Under the new guidance, revenue may be recognized in an earlier period for a limited number of multiple-element arrangements for which VSOE could not be established for all undelivered elements under the previous guidance. For those arrangements, the Company will now determine a relative selling price for the undelivered elements through the use of TPE or ESP, and the recognition of certain revenues that would have been deferred under the previous guidance will likely be recognized at the time of delivery under the new guidance, provided all other criteria for revenue recognition are met. For the three and six months ended June 30, 2011, adoption of the Updates resulted in increases in total revenues of approximately $1.8 million and $6.3 million, respectively. These increases were primarily the result of sales arrangements now accounted for under the guidance of ASU No. 2009-13 that contained undelivered elements for which VSOE of fair value could not be established as of June 30, 2011. The Company cannot reasonably estimate the effect of the adoption of the Updates on future financial periods as the impact will vary depending on the nature and volume of new or materially modified arrangements in any given period.

The Company recognizes revenue when persuasive evidence of an arrangement exists, delivery has occurred, the sales price is fixed or determinable, and collection is probable. However, determining whether and when some of these criteria have been satisfied often involves assumptions and judgments that can have a significant impact on the timing and amount of revenues the Company reports. For example, the Company often receives multiple purchase orders or contracts from a single customer or a group of related parties that are evaluated to determine if they are, in effect, parts of a single arrangement. If they are determined to be parts of a single arrangement, revenues are recorded as if a single multiple-element arrangement exists.

Generally, the products the Company sells do not require significant production, modification or customization of software. Installation of the products is generally routine, consists of implementation and configuration and does not have to be performed by Avid. However, certain transactions for the Company's video products, typically complex solution sales that include a significant number of products and may involve multiple customer sites, require the Company to perform an installation effort that it deems to be complex, non-routine and essential to the functionality of the products delivered. In these situations, the Company does not recognize revenues for either the products shipped or services performed until the essential services have been completed. In addition, if these orders include a customer acceptance provision, no revenues are recognized until the customer's formal acceptance of the products and services has been received.

In the first quarter of fiscal 2011, the Company adopted ASU No. 2009-13, Multiple-Deliverable Revenue Arrangements, an amendment to ASC Topic 605, Revenue Recognition, and ASU No. 2009-14, Certain Revenue Arrangements That Include Software Elements, an amendment to ASC Subtopic 985-605, Software - Revenue Recognition. ASU No. 2009-13 requires the allocation of revenue, based on the relative selling price of each deliverable, to each unit of accounting for multiple-element arrangements. It also changes the level of evidence of standalone selling price required to separate deliverables by allowing a best estimate of the standalone selling price of deliverables when more objective evidence of fair value, such as vendor-specific objective evidence or third-party evidence, is not available. ASU No. 2009-14 amends ASC Subtopic 985-605 to exclude sales of tangible products containing both software and non-software components that function together to deliver the tangible products essential functionality from the scope of revenue recognition requirements for software arrangements. The Company adopted this accounting guidance prospectively and applied its provisions to arrangements entered into or materially modified after December 31, 2010.

The Company recognizes revenue from the sale of non-software products, including software bundled with hardware that is essential to the functionality of the hardware, under the general revenue recognition accounting guidance of ASC Topic 605, Revenue Recognition and ASC Subtopic 605-25 Revenue Recognition - Multiple-Element Arrangements. The Company recognizes revenue in accordance with ASC Subtopic 985-605, Software - Revenue Recognition for the following types of sales transactions: (i) standalone sales of software products and related upgrades and (ii) sales of software elements that are bundled with non-software elements, when the software elements are not essential to the functionality of the non-software elements.

For 2011 and future periods, pursuant to the guidance of ASU No. 2009-13, when a sales arrangement contains multiple elements, such as non-software products, software products, customer support services, and/or professional services, the Company allocates revenue to each element based on the aforementioned selling price hierarchy. Revenue is allocated to the non-software deliverables as a group and to the software deliverables as a group using the relative selling prices of each of the deliverables in the arrangement based on the aforementioned selling price hierarchy. If the arrangement contains more than one software deliverable, the arrangement consideration allocated to the software deliverables as a group is then recognized using the guidance for recognizing software revenue, as amended.

The Company utilizes a pricing model for its products to capture the right value given the product and market context. The model considers such factors as: (i) competitive reference prices for products that are similar but not functionally equivalent, (ii) differential value based on specific feature sets, (iii) geographic regions where the products are sold, (iv) customer price sensitivity, (v) price-cost-volume tradeoffs, and (vi) volume based pricing. Management approval ensures that all of the Company's selling prices are consistent and within an acceptable range for use with the relative selling price method.

While the pricing model currently in use captures all critical variables, unforeseen changes due to external market forces may result in the revision of some of the Company's inputs. These modifications may result in consideration allocation in future periods that differs from the one presently in use. Absent a significant change in the pricing inputs, future changes in the pricing model are not expected to materially impact the Company's allocation of arrangement consideration.

From time to time, the Company offers certain customers free upgrades or specified future products or enhancements. For software products, if elements are undelivered at the time of product shipment and provided that the Company has vendor-specific objective evidence of fair value for the undelivered elements, the Company defers the fair value of the specified upgrade, product or enhancement and recognizes those revenues only upon later delivery or at the time at which the remaining contractual terms relating to the elements have been satisfied. If the Company cannot establish VSOE for each undelivered element, all revenue is deferred until all elements are delivered, the Company establishes VSOE or the remaining contractual terms relating to the undelivered elements have been satisfied. For non-software products, if elements are undelivered at the time of product shipment, the Company defers the relative selling price of the specified upgrade, product or enhancement and recognizes those revenues only upon later delivery or at the time at which the remaining contractual terms relating to the elements have been satisfied.

Approximately 61% of the Company's revenues for the first six months of 2011 were derived from indirect sales channels, including authorized resellers and distributors. Certain channel partners are offered limited rights of return, stock rotation and price protection. For these partners, the Company generally records a provision for estimated returns and other allowances as a reduction of revenues in the same period that related revenues are recorded in accordance with ASC Subtopic 605-15, Revenue Recognition - Products. Management estimates must be made and used in connection with establishing and maintaining a sales allowance for expected returns and other credits. In making these estimates, the Company analyzes historical returns and credits and the amounts of products held by major resellers and considers the impact of new product introductions, changes in customer demand, current economic conditions and other known factors. While the Company believes it can make reliable estimates regarding these matters, these estimates are inherently subjective. The amount and timing of the Company's revenues for any period may be affected if actual product returns or other reseller credits prove to be materially different from the Company's estimates.

A portion of the Company's revenues from sales of consumer video-editing and audio products is derived from transactions with channel partners who have unlimited return rights and from whom payment is contingent upon the product being sold through to their customers. Accordingly, revenues for these channel partners are recognized when the products are sold through to the customer instead of being recognized at the time products are shipped to the channel partners.

At the time of a sales transaction, the Company makes an assessment of the collectability of the amount due from the customer. Revenues are recognized only if it is probable that collection will occur in a timely manner. In making this assessment, the Company considers customer credit-worthiness and historical payment experience. If it is determined from the outset of the arrangement that collection is not probable based on the Company's credit review process, revenues are recognized on a cash-collected basis to the extent that the other criteria of ASC Topic 605, ASC Subtopic 985-605 and Securities and Exchange Commission Staff Accounting Bulletin No. 104 are satisfied. At the outset of the arrangement, the Company assesses whether the fee associated with the order is fixed or determinable and free of contingencies or significant uncertainties. In assessing whether the fee is fixed or determinable, the Company considers the payment terms of the transaction, its collection experience in similar transactions without making concessions, and the Company's involvement, if any, in third-party financing transactions, among other factors. If the fee is not fixed or determinable, revenues are recognized only as payments become due from the customer, provided that all other revenue recognition criteria are met. If a significant portion of the fee is due after the Company's normal payment terms, which are generally 30 days, but can be up to 90 days, after the invoice date, the Company evaluates whether it has sufficient history of successfully collecting past transactions with similar terms. If that collection history is successful, revenues are recognized upon delivery of the products, assuming all other revenue recognition criteria are satisfied. If the Company were to change any of these assumptions and judgments, it could cause a material increase or decrease in the amount of revenue reported in a particular period.

In June 2011, the FASB issued ASU No. 2011-05, Presentation of Comprehensive Income. This ASU eliminates the current option to report other comprehensive income and its components in the statement of changes in equity and requires an entity to present components of net income and other comprehensive income in one continuous statement, referred to as the statement of comprehensive income, or in two separate consecutive statements. ASU No. 2011-05 is effective for fiscal years and interim periods beginning after December 15, 2011, which is January 1, 2012 for Avid. While this ASU changes the presentation of comprehensive income, there are no changes to the components that are recognized in net income or other comprehensive income under current accounting guidance; therefore, adoption will not have an impact on the Company's consolidated financial position, results of operations or cash flows.

In May 2011, the FASB issued ASU No. 2011-04, Amendments to Achieve Common Fair Value Measurement and Disclosure Requirements in U.S. GAAP and IFRS. This ASU amends current U.S. GAAP fair value measurement and disclosure guidance to be consistent with International Financial Reporting Standards, including increased transparency around valuation inputs and the categorization by level of the fair value hierarchy for items that are not measured at fair value in the statement of financial position, but for which the fair value of such items is required to be disclosed. ASU No. 2011-04 is effective for fiscal years and interim periods beginning after December 15, 2011, which is January 1, 2012 for Avid. Adoption is not expected to have an impact on the Company's consolidated financial position, results of operations or cash flows.