On 06/07/2011 10:11 PM, Ralf Mardorf wrote:
> On Tue, 2011-06-07 at 21:54 +0200, Robin Gareus wrote:
>> On 06/07/2011 08:01 PM, Ralf Mardorf wrote:
>> {SNIP}
>>> There's still another issue left.
>>>
>>> I need two sound card mixers, envy24control, even if my two TerraTec EWX
>>> 96/24 cards now should be MIDI interfaces only and much more important
>>> rather hdspmixer than alsamixer, for the RME HSDSPe AIO.
>>>
>>> $ wget ftp://ftp.alsa-project.org/pub/tools/alsa-tools-1.0.24.1.tar.bz2
>>
>> I did not follow all of the thread... But is alsa-tools-1.0.23 not good
>> enough? `sudo apt-get install alsa-tools` ?!
>
> I can try this, but building current versions can't harm.
It will just side-track you. ..and well.. it can potentially do harm:
you waste time, get angry and hit your [head|wife|...] with the
[keyboard|mouse|..] :-p
more seriously: It will cause problems later when updating.
and more generally: Some software that you install as package might not
be built against this version [of the library] and may not work or
behave strangely (though AFAIK alsa-lib-1.0.24's ABI is backwards
compatible with 1.0.23). And some cutting-edge release might be able to
produce sounds that harm your speakers or ears.. (though you're pretty
save with alsa-lib-1.0.24 there).
In general: Unless you have a _good reason_: don't bother to compile
anything and just use [binary] packages from your distributor.
>>> configure: error: Sufficiently new version of libasound not found.
>>
>> Here's a pragmatic way to make a .deb of libasound2 - alsa-lib-1.0.24.1
>>
>> cd /tmp/
>> apt-get source libasound2
>> sudo apt-get build-dep libasound2
>> mv -vi alsa-lib-1.0.23/ alsa-lib-1.0.24.1
>> curl ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.0.24.1.tar.bz2 \
>> | tar xvj
>> cd alsa-lib-1.0.24.1
>> # edit debian/changelog -> alsa-lib (1.0.24.1-1) unstable; urgency=low
>> # edit debian/rules -> remove line 15-18 (biarch builds)
>> libtoolize --force --copy --automake
>> aclocal
>> autoreconf
>> debuild -b -us -uc
>> sudo dpkg -i ../*asound2*.deb
>
> Thank you. This is just libasound without devel files?
nope, all of it. Here it creates:
/tmp/lib64asound2_1.0.24.1-1_i386.deb
/tmp/lib64asound2-dev_1.0.24.1-1_i386.deb
/tmp/libasound2_1.0.24.1-1_i386.deb
/tmp/libasound2-dev_1.0.24.1-1_i386.deb
/tmp/libasound2-doc_1.0.24.1-1_all.deb
>>> Not only needed to build those mixers ;).
>>>
>>> There should be /usr/include/alsa and there is
>>> /usr/src/linux-headers-2.6.39.1/include/sound.
>>
>> /usr/include/alsa/ --- libasound2-dev
>> /usr/src/linux/include/sound/ --- kernel headers
>
> but there seems to be the needed headers?!
"Sufficiently new version of libasound not found."
They're not the right version. see /usr/include/alsa/version.h
Apparently the alsa-tools 1.0.24 use some new symbols/functions which
are not present in alsa-lib-1.0.23.
>>> I'll try a soft link after cooking. Is this correct, or am I mistaken?
>>
>> bon appetit,
>> robin
>
> thank you, right now I'm eating :)
>
> I still can't start jackd by qjackctl.
> 22:05:03.722 /usr/bin/jackd -dalsa -r48000 -p1024 -n2 -D -Chw:1 -Phw:1
'-C.. -P..'
Did you configure specific Input-Devices AND Output-devices in
qjackctl's setup window instead of just setting the interface globally
and leaving those as "default".
does this work?
/usr/bin/jackd -dalsa -r48000 -p1024 -n2 -D -dhw:1
> Cannot connect to server socket err = No such file or directory
> Neither using the RME nor the TerraTecs.
>
> This does works:
> $ jackd --sync -Xalsarawmidi -dalsa -r48000 -p1024
> This
> $ jackd --sync -Xalsarawmidi -dalsa -r48000 -p250
BTW. IIRC you should not use the -X... options for JACK-midi but rather
use a2j instead. AFAIK there were/are [timing?] issues with the built-in
JACK midi backends. (see Jeremy's workshop slides on how to launch a2j
using qjackctl's "Execute Script" option.)
HTH,
robin
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user
