Hi Arthur Marsh! On 2007.02.18 at 22:44:29 +1030, Arthur Marsh wrote next: > As previously discussed here, I'm tending towards an Audigy 4 Pro while > I can still get one in Australia - I don't have the free PCI slots or > fast enough PC to use another solution whilst keeping hardware synth and > mixing. I wonder why are you saying this. First, I don't understand about PCI slot - Audigy requires one, you should go to USB cards if you don't have a free one. Second, why do you think that mixing streams in software takes that much of CPU power? I stopped jack, restarted it with different options and started playing 20 audio tracks via alsa->jack chain with default alsa 44.1->48khz sample rate conversion. About 30 seconds after that, I ran ps (top shows cpu usage for last few seconds, while only averaged cpu usage since start shows meaningful results). mosgalin 6160 0.1 1.2 40640 26552 pts/9 SLl 15:38 0:00 jackd -t1000 -R -P89 -dalsa -Phw:1,1 -r48000 -p512 -n2 -H mosgalin 6184 0.2 2.9 74084 59768 pts/4 SLl 15:38 0:00 aplay -D jackplug track01.wav mosgalin 6186 0.3 2.9 74084 59768 pts/4 SLl 15:38 0:00 aplay -D jackplug track02.wav mosgalin 6188 0.3 2.9 74084 59768 pts/4 SLl 15:38 0:00 aplay -D jackplug track03.wav mosgalin 6191 0.3 2.9 74088 59772 pts/4 SLl 15:38 0:00 aplay -D jackplug track04.wav mosgalin 6193 0.2 2.9 74084 59768 pts/4 SLl 15:38 0:00 aplay -D jackplug track05.wav mosgalin 6195 0.3 2.9 74088 59772 pts/4 SLl 15:38 0:00 aplay -D jackplug track06.wav mosgalin 6197 0.2 2.9 74084 59768 pts/4 SLl 15:38 0:00 aplay -D jackplug track07.wav mosgalin 6199 0.3 2.9 74088 59772 pts/4 SLl 15:38 0:00 aplay -D jackplug track08.wav mosgalin 6203 0.3 2.9 74088 59772 pts/4 SLl 15:38 0:00 aplay -D jackplug track09.wav mosgalin 6205 0.3 2.9 74084 59768 pts/4 SLl 15:38 0:00 aplay -D jackplug track10.wav mosgalin 6207 0.2 2.9 74084 59768 pts/4 SLl 15:38 0:00 aplay -D jackplug track10.wav mosgalin 6209 0.2 2.9 74088 59772 pts/4 SLl 15:38 0:00 aplay -D jackplug track09.wav mosgalin 6211 0.2 2.9 74084 59768 pts/4 SLl 15:38 0:00 aplay -D jackplug track08.wav mosgalin 6213 0.3 2.9 74088 59772 pts/4 SLl 15:38 0:00 aplay -D jackplug track07.wav mosgalin 6215 0.2 2.9 74084 59768 pts/4 SLl 15:38 0:00 aplay -D jackplug track06.wav mosgalin 6217 0.3 2.9 74084 59768 pts/4 SLl 15:38 0:00 aplay -D jackplug track05.wav mosgalin 6219 0.2 2.9 74088 59772 pts/4 SLl 15:38 0:00 aplay -D jackplug track04.wav mosgalin 6222 0.2 2.9 74084 59768 pts/4 SLl 15:38 0:00 aplay -D jackplug track03.wav mosgalin 6224 0.3 2.9 74084 59768 pts/4 SLl 15:38 0:00 aplay -D jackplug track02.wav mosgalin 6226 0.2 2.9 74088 59772 pts/4 SLl 15:38 0:00 aplay -D jackplug track01.wav mosgalin 6236 0.0 0.0 62316 788 pts/3 S+ 15:39 0:00 grep jack So I don't know where you got the assumption that mixing uses a lot of CPU power. Unless by "not fast enough PC" you mean 486 ;), it shouldn't burden your PC that much. As about software synth, well, first of all, hardware synth on Live/Audigy really sucks. It worked nicely for some very old games ;), but either in general, or on linux with alsa drivers it produces output much worse than timidity. So I doubt you'll be able to do anything useful with it anyway. Also, about 10 years ago, when I had P166MMX system, it was mostly enough for software synth - only a few midi files with a lot of tracks required more powerful system. Back than, hardware synth on Live was useful. However, I fail to understand why are you trying to re-create that kind of configuration now. -- Vladimir ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
