Ralf Mardorf wrote: <snip> > > With my new mobo and CPU, resources aren't a problem any more, but still > all MIDI applications get killed. I'll check out jackd 0.116.1 today or > tomorrow. >
> If you sync Rosegarden and Ardour by JACK transport take car that the > delay can't be heard, it also won't be in sync for you, because this is > an issue of JACK, not of the hardware. I recommend to use the audio > tracks of Rosegarden. > Syncing the two via jack is working just fine for me so I probably will not be changing my workflow anytime soon. I only use Rosegarden for editing midi, I prefer ardour for everything else. >>> hardware incompatibilities seems to be no interest of the Linux >>> community, even if it has nothing to do with evil proprietary stuff. At >>> >> I have to disagree with you here. Fixing hardware incompatibilities is >> a high priority within the Linux and Open Source community. In fact no >> other community or company puts the effort that the Open Source people >> do into correcting this very issue. The problem is with the hardware >> manufacturers themselves. There is a group of kernel devels that will >> sign NDAs and write the drivers for the hardware vendor. Who else does >> this? Microsoft will not write your driver for you, but the Linux >> kernel developers will. Please get your facts straight. >> > Fact is, that many people don't use Linux, but Windows, because of > troubles with chipsets. If you wish to have a forum for testing versions > of distros, the community is against this. I'm not talking about a > driver for the graphics and all evil vendors, I'm talking about basics > like incompatible motherboards, like my M2A-VM HDMI or maybe > incompatible CPUs like my BE-2350. I don't know what causes the problem > with my hardware. The linux kernel needs to know how to talk to chipsets, modems, wireless network adaptors, ethernet network cards, just like it needs to know how to talk to video cards. I make no distinction between these devices. If they don't work either you need to upgrade your kernel or the vendor screwed up. If Intel and the ATI division of AMD can get it right so can everyone else. > I know some people got problems with Windows too, but more people got > problems with Linux. > That is very true. There is no need for this situation, but it does exist. There is not a lot more that can be done about this. Either the hardware vendors sort out their problems or they don't. Fortunately we still have hardware to choose from. > Here I tried to get a forum for RCs, to write with other people that > don't convert to Windows, but stay with Linux, even though of the > problems: http://www.linux-club.de/viewtopic.php?f=8&t=99372 > It's on German and you need an account. The community isn't interested > in a forum, for people that try to do something against the hardware > problem. > > I often read that I should by new hardware, again and again AND hardware > that should be okay for some people isn't okay for them too, but they > don't know this. E.g. I can work with files.mid, but I can't produce > myself MIDI recordings. When people say that MIDI is fine for their > hardware, they often don't do MIDI recordings, they just play MIDI-files I do edit midi quite a bit. I do not really play "live" with a midi keyboard. The few times I have done midi recording I have quantized the resulting midi. I have also sent the output of my keybaord into qmidiarp, then the midi output of that into rosegarden and a soft synth. From there I could chop up the output into useable loops. The midi capabilities are quite powerful and useful, at least for what I need to do. There may in fact be problems with mixing live and pre-recorded midi, but I take issue with blanket statements that say midi is broken. I find such statements to be misleading and bordering on FUD. > from the net. And I'm not writing about Quentin, who made a test, I'm > writing about the pro-audio community that recommend hardware, that > wasn't really tested. My hardware is fine with openOffice, Thunderbird, > GIMP. That's something complete different to the work for printing shops > or to make soundtracks for films. > I agree, there is a difference between low latency audio work and general computing. Most "pro-audio" types don't seem to be aware of latency issues under any OS (Windows has had its share of problems too). I don't know what the solution is, but at least there are places like this to ask the questions (the Linux Audio Users list is another excellent resource, even better than this one since some of the ALSA and jack people are directly involved).
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
