HI Nick,
Well, "pd -rme" and "./configure --enable-rme" are both to use Ritch's driver. But "rme96xx" Is Guenter Geiger's newer, OSS driver for RME. Therefore you don't have to flag ./configure and the correct invocation is indeed "pd -inchannels 8 -outchannels 8"..
I'm grasping at straws here, but are you sure the es1371 module was loaded _after_ the rme96xx one? Otherwise Pd is trying to open your es1371. Perhaps there's some reason it can't do 8 channels that way.
Even if not, what does just "pd" do?
bon courage, Miller
./configure --enable-rme
Also fine.
start pd *without* option -rme, e.g.
The documentation says that "-rme" is to use Ritch's 9652 driver. Isn't this what we're doing?
pd -inchannels 8 -outchannels 8
Doesn't work. It launches, sometimes gives me
OSS: requested audio buffer size 14112 limited to 4096
(are we supposed to be using OSS at all?) and then just says
Pd: system call timed out
at which stage it's essentially dead; the GUI thread is running but nonfunctional.
Specifying "-verbose" suggests that this is coming from OSS.
So I try "pd -verbose -rme" and get as far as "RME open" before it just fails in the way I described (failing to find the entries in /dev).
Aside: comment from Andreas Poegl (I think: the PD list archive is out of date so I can't see the details) about the path settings for rme96xx: nope. The Makefile is broken since (in Red Hat 7.1) the first line of version.h is now a #include, not a definition of UTS_RELEASE.
Oh, and the xrmectrl program still appears nonfunctional.
Anyone got any ideas what I'm doing wrong? At this stage I'm thinking of completely giving up on PD as a viable option for this project.
--
Nick Rothwell Cassiel.com Limited nick@cassiel.com www.cassiel.com systems - composition - installation - performance