From: "Petter Sundlöf" <petter.sundlof@findus.dhs.org>
To: John Rigg <j@sound-man.co.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: Some problems with two 1010LTs (pcm_multi & jackd)
Date: Fri, 27 Jan 2006 00:14:41 +0100 [thread overview]
Message-ID: <43D957E1.3030608@findus.dhs.org> (raw)
In-Reply-To: <20060126184843.GA3747@localhost.localdomain>
>>After this I tried to run jackd -d alsa -r44100 -p512 -C multi_capture
>>-P multi_playback
>>
>>I then get this stdout message:
>>
>>jackd 0.100.7
>>Copyright 2001-2005 Paul Davis and others.
>>jackd comes with ABSOLUTELY NO WARRANTY
>>This is free software, and you are welcome to redistribute it
>>under certain conditions; see the file COPYING for details
>>
>>JACK compiled with System V SHM support.
>>loading driver ..
>>creating alsa driver ...
>>multi_playback|multi_capture|1024|2|48000|0|0|nomon|swmeter|-|32bit
>>configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
>>nperiods = 2 for capture
>>nperiods = 2 for playback
>
>
> It's starting with the wrong sample rate and number of frames, but using
> the right devices. That's strange.
> You say you installed alsa-lib over an existing one. Are you sure you replaced
> it?
I pasted in a "later" jack command line, where I tried with 44k/512
frames instead. So the stdout output doesn't match the command I
actually used at that time.
>
>>I then start Ardour and open a session. I place the playhead somewhere
>>and try to start playback. Nothing happens. After a few seconds, Ardour
>>is disconnected from JACK, and I receive this in jackd's stdout:
>>
>>ALSA: poll time out, polled for 17416024 usecs
>
>
> This is the error message I kept getting before I patched pcm_multi.c.
>
> It might be worth removing alsa-lib and jack completely and
> recompiling/reinstalling.
That'd be a dependency nightmare on Fedora Core :/ alsa-lib is patched
and installed, but I'll double double check it tomorrow (today's been
too rough; had to evactuate rehearsal room and guitarist breaks his
little finger).
> You won't be able to record for long like this. It will run for a while,
> as the clocks are pretty accurate, but they will drift and you'll get
> xruns and/or jackd will die.
Yeah. Since I don't have any external S/PDIF sources yet, I guess I'll
have to wait until/if a solution for 1010LT cards has landed.
[snip...]
>># S/PDIF second soundcard (playback)
>>> bindings.18.slave b
>>> bindings.18.channel 8
>>> bindings.19.slave b
>>> bindings.19.channel 9
>
>
>One more thing - I'm not sure if the S/PDIFs are working yet on 1010LT.
>Try commenting these sections out in .asoundrc.
Done, but no change.
I'll try making sure alsa-lib is patched alright.
Thanks for the help.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
next prev parent reply other threads:[~2006-01-26 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 14:04 Some problems with two 1010LTs (pcm_multi & jackd) Petter Sundlöf
2006-01-26 18:48 ` John Rigg
2006-01-26 23:14 ` Petter Sundlöf [this message]
2006-01-27 12:53 ` John Rigg
2006-01-27 14:02 ` John Rigg
2006-01-26 19:10 ` John Rigg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43D957E1.3030608@findus.dhs.org \
--to=petter.sundlof@findus.dhs.org \
--cc=alsa-devel@alsa-project.org \
--cc=j@sound-man.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.