soulboy wrote:I know its unlikely but you never know they might agree, but what about asking them to open source the code? The anyone could have a go at fixing it.
Hi, i'm new to the forum and have only started using emu harware in the last year or so, and am only now in the process of buying an rfx card. I have read this entire thread and am frustrated that I am going to be experiencing these bugs!
From what I can see, the only realistic options for fixing these problems are:
1. Creative/E-mu release eos source code and someone fixes the bugs (unlikely)
2. Someone finds a way to gain access to the source code and someone fixes the bugs (still pretty unlikely)
2. Somebody writes their own version of EOS. This may sound far fetched... but just look at what has happened for the MPC community with the JJ os releases. Since Numark took over Akai the newer MPCs that have been released have been substandard, and a group called JJ have written a number of OS for them that are FAR superior to the originals. If as a group we put the time and effort into researching this idea, we may be able to find a solution. If we find out what needs to be done, who is capable of doing it and then offer them enough $$$ (i would be willing to donate and i am sure that so would many others) then maybe we can get a whole new unofficial eos with no bugs and maybe even some cool new features. This IS possible if somebody with the time and knowledge is willing to apply themselves so let's not give up!!!!
Let's start by everyone posting anything they KNOW about designing OSs like this... e.g. Is it possible to somehow extract code from EOS 4.7 and then just fix the bugs or does the whole thing have to be made from scratch? Is anyone on here involved in programming? etc etc
You guys have been fighting for 3 years so i can understand that you are all tired but i am fresh to this so have at least 3 years in me... let's take this into our own hands!