In the year 2000, E-MU Systems, a wholly owned subsidiary of Creative Technology Ltd. of Singapore, released the RFX-32 FX/Mixer Card for the company\'s Emulator 4 Ultra line of hardware samplers. There is a confirmed flaw in the last official release of the Emulator 4 Ultra operating System version: EOS 4.61, which affects Emulator 4 Ultra hardware samplers, to which the RFX-32 FX/Mixer Card has been installed. The same flaw also affects EOS beta version 4.7. This software flaw, nicknamed the "Random Panning Bug" by the owners of affected hardware units, creates the following problem when an audio signal is routed through the RFX-32 FX/Mixer Card and output from the affected units audio outputs:
Monophonic and stereo audio signals cannot be combined freely using the RFX-32 FX/Mixer Card, without creating the unwanted effect of one or more channels of audio panning randomly between the left and right channels of the stereo audio field.
This flaw makes the RFX-32 FX/Mixer Card unusable as a digital audio mixer, and limits its use as an effects processor when combining stereo and mono samples. The purpose for which the option card was designed, and advertised by E-MU systems.
E-MU Systems was made aware of this major flaw in the product. E-MU systems continued to sell and advertise the RFX-32 FX/Mixer Card as an audio mixer with the knowledge of this flaw. No action was ever taken by E-MU Systems to correct the flaw before the Emulator 4 Ultra line of hardware samplers and RFX-32 FX/Mixer Card were discontinued.
We the undersigned demand that E-MU Systems, a wholly owned subsidiary of Creative Technology Ltd.of Singapore, address and fix the random stereo panning flaw in the last official release of the Emulator 4 Ultra operating System version: EOS 4.61, which affects the Emulator 4 Ultra line of hardware samplers to which the RFX-32 FX/Mixer Card has been installed.
Help spread the word about this petition. Copy the code below and paste it into your website or blog to help promote this petition.
The views expressed in this petition are solely those of the petition's sponsor and do not in any way reflect the views of iPetitions. iPetitions is solely a provider of technical services to the petition sponsor and cannot be held liable for any damages or injury or other harm arising from this petition. In the event no adequate sponsor is named, iPetitions will consider the individual account holder with which the petition was created as the lawful sponsor.