Re: [linux-audio-dev] rosegarden, alsa_seq and usx2y rawusb
Uwe Koloska rwote: Hello, have now figured out how to drive my audio and midi with tascam us-122 on SuSE 9.2 -- and (after disabling all tv thingies) it works very reliable and with very few xruns. The following software seems to be involved: - linux-2.6.8-24.3 (SuSE Standard kernel -- heavily patched) patched with linux-2.6.8-24-usx2y-0.8.6.patch from rncbc (CONFIG_HPET_RTC_IRQ=n) - realtime-lsm-0.8.5 - ruis jack jack-0.99.21.1usx2y-17.suse92 - qjackctl-0.2.13-1 - rosegarden4-0.9.9-2 - ZynAddSubFX-1.4.3-141 With this configuration I have found a weird problem: When starting jack with driver 'alsa' (from qjackctl) I am able to play my alsa instruments (for example ZynAddSubFX) from within rosegarden: - start ZynAddSubFX - start rosegarden - choose ZynAddSubFX for the active track - play the keyboard an listen to nice ZynAddSubFX sounds ... But when starting jack with driver 'usx2y' the midi seems not to arrive at ZynAddSubFX (or Hydrogen or fluidsynth or ...) Even ASeqView doesn't show any incoming events if chosen as instrument in rosegarden. Restarting jack with driver alsa -- and all went well ... What is the problem? And what can I do to help with this problem? Are there any missing facts? I cannot confirm this issue yet, but seems strange how just using the alsa hwdep pcm interface affects the alsa sequencer behavior. They should be orthogonal. As most of your stack is filled with these custom versions of mine for alsa and jack, I'll try to reproduce this at my SUSE 9.2 box. BBL tonight Bye now. -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED]
Re: [linux-audio-dev] rosegarden, alsa_seq and usx2y rawusb
On Sunday 12 Dec 2004 22:44, Uwe Koloska wrote: But when starting jack with driver 'usx2y' the midi seems not to arrive at ZynAddSubFX (or Hydrogen or fluidsynth or ...) Try changing Rosegarden's Sequencer Timer setting (Settings - Configure Rosegarden - Sequencer - Synchronisation) to system timer, or something else other than (auto). Chris
Re: [linux-audio-dev] rosegarden, alsa_seq and usx2y rawusb
Chris Cannam wrote: On Sunday 12 Dec 2004 22:44, Uwe Koloska wrote: But when starting jack with driver 'usx2y' the midi seems not to arrive at ZynAddSubFX (or Hydrogen or fluidsynth or ...) Try changing Rosegarden's Sequencer Timer setting (Settings - Configure Rosegarden - Sequencer - Synchronisation) to system timer, or something else other than (auto). Ah -- thank you. Will try that at home. Uwe -- voiceINTERconnect www.voiceinterconnect.de ... smart speech applications from germany
Re: [linux-audio-dev] Re: rosegarden, alsa_seq and usx2y rawusb
Stefan Turner wrote: Since this has been mentioned, my US-122 doesn't work AT ALL using usx2y, but is fine with alsa. I am using qjackctl 0.2.13 and Jack 0.99.0 (the most recent versions AFAIK). All I get is: 17:47:12.866 JACK is starting... 17:47:12.867 /usr/bin/jackstart -R -dusx2y -dhw:1 -r44100 -p512 -n3 -H -M 17:47:12.873 JACK was started with PID=6369 (0x18e1). back from read, ret = 1 errno == Success jackd: unknown driver 'usx2y' 17:47:12.885 JACK was stopped with exit status=1. 17:47:14.885 Could not connect to JACK server as client. This doesn't bother me, unless there are meant to be advantages of using usx2y? Try using -p128 -n2, and tell us whether you can't notice any aural difference, let alone if you can ignore a XRUN storm =:) You need both the specific 'usx2y' backend driver patched into jackd, *and* the new hwdep pcm (aka rawusb) interface available on the sand-usb-usx2y alsa kernel module. As Uwe did, you can look under http://www.rncbc.org/usx2y/ for what fits you and try this out. Cheers. -- rncbc aka Rui Nuno Capela [EMAIL PROTECTED]
Re: [linux-audio-dev] rosegarden, alsa_seq and usx2y rawusb
Am Montag, 13. Dezember 2004 11:15 schrieb Chris Cannam: On Sunday 12 Dec 2004 22:44, Uwe Koloska wrote: But when starting jack with driver 'usx2y' the midi seems not to arrive at ZynAddSubFX (or Hydrogen or fluidsynth or ...) Try changing Rosegarden's Sequencer Timer setting (Settings - Configure Rosegarden - Sequencer - Synchronisation) to system timer, or something else other than (auto). No, this doesn't change anything ... Have tried both, changing the setting - with - without restarting rosegarden. And now I have noticed the following: if the midi doesn't reach the alsa_seq client zynaddsubfx, after some time the following error message from the synth appears: NOTES TOO MANY ( POLIPHONY) - (Part.C::NoteOn(..)) To make it clear: this message doesn't appear for the first notes, but after some time. So for me it looks like midi reaches the program, but can't be processed -- even the meter from zynaddsubfx doesn't show anything. Very mysterious Uwe
Open Source Hardware (Re: [linux-audio-user] Re: [linux-audio-dev] RME is no more)
Lee Revell wrote: Christ, what the fuck country do you live in? Don't you understand the concept of people having bills to pay? Or do you just assume the RME guys are independenly wealthy and just design sound cards for fun? Interestingly some people seem to be existing who are working on Linux for fun. Also there is a concept known as Open Source Hardware which was mentioned here before. Cheers, Andreas
[linux-audio-dev] [Fwd: Graphical dataflow programs violate patents]
-Forwarded Message- From: Xavier Amatriain [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Graphical dataflow programs violate patents Date: Tue, 14 Dec 2004 10:57:56 +0100 I read that National Circuits sued and won a case against Mathworks for their Simulink product infringing a number of paterns (September this year). According to a summary of the claims (which you can read here http://cafc.bna.com/03-1540.pdf): the dispute was about the term data flow diagrams (which are interpreted) as a graphical computer program whose execution follows a set of semantic or operational rules as follows: 1. The order of the operations is not completely specified by the user 2. The order of operations is implied by data interdependencies 3. a node may only execute after all its inputs have become available, and, 4. outputs are generated after a node completes execution It turns out that most graphical audio programs such as Max, Pd, OSW or CLAM's Network Editor may be infringing these patents. Luckily this is still not valid in Europe and we hope will never be. Read more about this story at: http://patentlaw.typepad.com/patent/2004/09/federal_circuit.html http://digital.ni.com/worldwide/bwcontent.nsf/web/all/03B9A7C68030C42D86256F08006499CD http://www.mathworks.com/company/pressroom/articles/article7951.html http://news.thomasnet.com/fullstory/16801 -- /** * Xavier Amatriain ** Music Technology Group * ** IUA- Universitat Pompeu Fabra ** ** www.iua.upf.es/~xamat ** ***/
[linux-audio-dev] Re: rosegarden, alsa_seq and usx2y rawusb
Since this has been mentioned, my US-122 doesn't work AT ALL using usx2y, but is fine with alsa. I am using qjackctl 0.2.13 and Jack 0.99.0 (the most recent versions AFAIK). All I get is: 17:47:12.866 JACK is starting... 17:47:12.867 /usr/bin/jackstart -R -dusx2y -dhw:1 -r44100 -p512 -n3 -H -M 17:47:12.873 JACK was started with PID=6369 (0x18e1). back from read, ret = 1 errno == Success jackd: unknown driver 'usx2y' 17:47:12.885 JACK was stopped with exit status=1. 17:47:14.885 Could not connect to JACK server as client. This doesn't bother me, unless there are meant to be advantages of using usx2y? Stefan Turner ___ Win a castle for NYE with your mates and Yahoo! Messenger http://uk.messenger.yahoo.com
Re: [linux-audio-dev] Firewire and Macie Onyx
How probable is it that Mackie will produce such drivers, or release the necessary specs? And, if given specs, can someone be persuaded to do a driver? IIRC, the FireWire interfaces is based on a DM1000 chip (that's for sure) running BeBob (not so sure anymore) which happends to be supported some day by the FreeBob project... daniel
Re: [linux-audio-user] Re: [linux-audio-dev] RME is no more
On Sun, 2004-12-12 at 12:03 +0100, Esben Stien wrote: Frank Barknecht [EMAIL PROTECTED] writes: So basically they want to protect their investment in getting knowledge of how to implement a powerful firewire interface from the eyes of other hardware manufacturers. A society where you put money higher than cooperating with other people is not a good society, in my opinion. Christ, what the fuck country do you live in? Don't you understand the concept of people having bills to pay? Or do you just assume the RME guys are independenly wealthy and just design sound cards for fun? Sheesh. Lee
[linux-audio-dev] Re: [linux-audio-user] announce-list policy
On Sun, 2004-12-12 at 13:58 +0200, Kai Vehmanen wrote: when linux-audio-announce was created, it was agreed that announcements should be crossposted to all three lists. The reasoning was that this way people wouldn't have to subcsribe to LAA if they were already on LAD+LAU. Now when you look at LAA archives, some people post only to LAA, some (like me) to all three lists, and some to either LAA+LAD or LAA+LAU. I didn't even knew that LAA existed. :-/ Perhaps Mailman should be configured so that it adds a footer to each message, containing basic stuff such as where to go to subscribe/unsubscribe, and where are the other related lists. Anyway, i think your proposal makes sense. Crosspostings are bad. Ok, now let me subscribe real quick now to LAA... -- Florin Andrei http://florin.myip.org/
