-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ralf Mardorf wrote: > Hi Quentin :) > > before you read what I reply to your statements about Windows, pleas > read my last sentence. > >> I agree that it it a nuisance that we have to look out for these >> things. It all has to do with the reason why Linux works so much better >> as a DAW than windows, and that is the kernel. > > Are there any Linux DAWs that work better than Windows DAWs? I read > about that not only I have MIDI jitter, but that MIDI jitter is a > problem for every Linux DAW, even if it's not hearable for most Linux > DAWs, it's still there and Windows DAWs definitive have no jitter. > Latencies are fine with Windows and Linux for my TerraTec and the audio > software needs less resources by more functionality. > > I'm not fine with Windows, but I guess you are wrong. What will work > better with Linux DAWs? > >> Under the windows >> system, the kernel is very small in relation to linux, and all drivers >> are loaded as modules onto the kernel. When I say all, I mean all. >> That opens the floor to hardware manufacturers to merrily go and change >> just about anything, as long as they supply the new drivers with the >> piece of hardware. The drawback is a slight performance hit. >> > > I know much more about Linux, but I can set up Windows DAWs that > performs much, much, much better than Linux DAWs. The whole structure of > Windows is much smarter than the structure of Linux, smaller and more > efficient, excepted of the filesystem and for multiuser systems I can't > see any advantages for Linux (excepted of the political issue). > >> This is BAD for us, as this all has to be incorporated in the kernel, >> either though direct support by some hardware manufacturers (very few) >> or by reverse engineering. These kernel then has to be tested, and >> ultimately be transformed by our RT kernel hackers to be a RT kernel >> viable for real time audio work. Quite a process. >> >> All this says one thing - get tried and trusted hardware if you are only >> going to build a single system. Check out our Greylist for advice: >> http://www.64studio.com/node/69 . If you have the cash to try new >> systems, do it and report back to the greylist. >> > > That's the problem, I'm very poor, I bought hardware that was 100% > perfect with a Windows DAW, Cubase with much more functionality than > Linux has got, but I never liked Microsoft, that's why I only used > Linux, resp. I couldn't get a DAW running, so a friend gave me the money > to buy better hardware. I asked the list, I read > http://www.64studio.com/node/69 and many posts in the internet and > anyhow it seems that I bought the wrong hardware. I often got hardware > with chipsets that are posted as fine with Linux, but it wasn't because > of different revisions of the boards. > >> If you have a perfectly working system, please contribute to our >> greylist with your working setup, and help other users to get their 64 >> Studio setups working out of the box. >> >> PS: There is no whitelist, because no hardware can be deemed fully >> supported... It sometimes comes down to combinations as well. BUT, >> generally all items marked as Grey can be considered fully or >> satisfactorily supported. >> >> Cheers,Quentin > > If my mobo isn't fine, I only can try to find a better board, if there > will be one with an integrated graphics around 50,-€. > > Because of my connections I can get a legal Cubase for my homestudio for > free, so a Microsoft based DAW also will be less expensive for me. > People say I'm an idiot, because I will use Linux because of ethical > reasons. > > The problem with the hardware isn't just that the hardware companies are > all evil, it's also because it's much easier to write drivers for > Windows. I'm a coder and I'm not able to program more than "Hallo
There is an open call to hardware manufactures to provide the kernel devs what they need to do the driver work for them. Greg KH has been pushing this for years. I also find coding for Linux much easier. The tools are already there, for whatever Language I could want. Windows sucks as a devel platform. > world!" for Linux, I'm jobless and could learn and program 24 hours a > day, a professional coder has got only 8 hours a day. > > Even dedicated coders, Ardour, Rosegarden, have troubles with the make > files, so for a hardware company the effort won't pay. They don't have to do anything. The situation is not a technically complex one. Most of the problems are legal and or social in nature. > I'm not fine with saying Linux is better, without giving arguments what > especially is better. Excepted of the ethical reasons, multi user sytems > / servers and maybe safeness when using the internet and that there are > a few good software that is expensive for MacOS and Windows, Linux will > cause more trouble than MacOS and Windows will do. It goes beyond ethics, but I have said that before. > > Anyway, today I've to test if the BIOS upgrade did change anything, if > not I'll have to look for a new low-cost board with AM2 socket and if > also a new board won't change anything, I have to change to Windows :(. > The friend who gave me the money for the hardware I bought for Linux, > only uses MacOS and Windows and he'll give me a gift if I stop wasting > my time with Linux. In your case that may be the right choice. Your hardware can and will limit your software choices. This is nothing new. I paid this same price when I was a Windows DAW user. I had a VIA chipset that was a nightmare _under_Windows_ for audio work. It happens to everyone. > I'm serious frustrated. I only have one friend who always tries Linux > DAWs too. He installs latest Linux distros, set up DAWs, tested those > DAWs and goes on making music with Windows, because he always has > similar problems to mine. Instead of using Windows I compile and > compile, check out repositories, try distros. > I do sympathise. I remember Cubase SX on my Windows 2000 machine, and that pushed me over the edge to the FLOSS world. A big part of your problem is expecting things to work exactly the same as before. This is a different OS, with a very sophisticated kernel that was designed to do things other than make music. Sometimes in the short term that gets in our way, but in the end everyone tends to benefit from the work the kernel guys do. Also, a big part of your problem is all the constant compiling and messing with the internals. Not once have you tried building a newer kernel though. If you want to try and stick around, this is where the drivers are, so there may be some bug fixes that pertain to you. Of course the choice is still yours. > Nearly every thing is fine with Linux when using Suse 11.0, but I can't > get a DAW, at the moment with Suse 11.0 and 64 Studio 2.1 default and 64 > Studio Lenny. Not fine is the fax, because I've got a Linux compatible > card, that's not Linux compatible, because of a chipset combination and > because also of an USB device with bad Linux drivers. Sometimes an a/b > box I've got isn't able to work as fax, sometimes it only can send fax > and sometimes it works, that depends to the distros versions I used. > I should create a macro for this phrase: "it pays to do research, don't assume anything". It may sound harsh but you didn't do proper due diligence, and you are paying a price. I do not say this to be mean, but I do believe that the entire world would benefit from a huge dose of personal responsibility. > Anyway, I'm not willing to write more about MacOS and Windows, I need Probably a good idea on FLOSS based list. A lot of your comments tend to inflame emotions, especially since you seem to be uninformed on some very key issues. That is all I will say on this as it is way OT. I hope you stay and I hope that things work out. > informations about ways to get a stable Linux DAW with less, very less > money, independent the situation if Windows and MacOs are better or more > worse than Linux. Buy better hardware. Regardless of the OS, if your hardware is crap then everything afterwards is moot. This is true in the Windows world too. I had an AMD K7 paired with a VIA chipset. Even switching to Windows 2000 did not really solve the underlying issues with the chipset, though my latencies got worse by an order of magnitude. I have a friend who had to buy a new computer because the MOTU card he has would not work on his AMD64 based motherboard. The point is, for something this demanding, do your research. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIvkYQwRXgH3rKGfMRAjzYAJ9o0Qf5DOhN1KKS+e9MjR9wBxI7nQCgrDp3 z7O6hoKQoKJqVEik3tM+wLI= =hvwM -----END PGP SIGNATURE----- _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
