emusonacid! legacy

i got a hint that if we want our document to be seriously useful some NAMES [real] and SERIALS are to be included...

please post it here...

and post authentic data [dont put me and all of us in a stupid situation, u know what i mean]


d2k

well, nice to see that everybody really care...:(

whats up with u guys? do u want this thing fixed?
gimme some names + serials



d2k

yo, check your pm. i can't get to my studio till sunday. as soon as i gather all the info i'll let you know. i'm just as eager as you bro, seriously eager trust it.

...

Maybe I am missing something, but why would you want our real names and the serial numbers off our emus?

if i want to send kind of official document describing our problems and want anybody to get us seriously, we need reayl data...simple as that...

d2k

sampleandhold wrote:Maybe I am missing something, but why would you want our real names and the serial numbers off our emus?

sorry, we should have clarified the purpose at the beginning of this thread...really this is a continuation of another post, a very important and relevant tangent if you will to the "RFX EMU - keep it in one post" thread viewtopic.php?t=346.

basically, we all collectively decided we shouldn't have to deal w/ EOS bugs, namely the two worst known, "random panning" http://www.basscadets.co.uk/emu/index.htm and "outbursts" http://www.basscadets.co.uk/emu/EOS470.htm and some of us have gotten word that EMU has completely dropped plans for future EOS revisions (i heard straight from Dan, EMU tech support manager available at extension 1219). so we decided as a team to fight back to get at least a final clean version of EOS. Division2000 here is organizing something big that requires us to give some serials and names to be taken seriously in fighting back. so that's what this is for...sorry it's not been previously explained.

see the other thread though b/c there are several new twists to possible fixes for these bugs/problems...particularly on pages 3 and 4.