From: James Courtier-Dutton <James@superbug.co.uk>
To: Ctirad Fertr <c.fertr@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: E-mu 1212M/1820M/1616M development
Date: Sun, 11 Nov 2007 22:51:34 +0000 [thread overview]
Message-ID: <47378776.6050403@superbug.co.uk> (raw)
In-Reply-To: <47376DE9.5000904@gmail.com>
Ctirad Fertr wrote:
> Hello,
>
> I just bought an 1616M PCMCIA in addition to my old 1212m v1 and want to
> help improve the current driver. I wrote one little patch for those
> cards in the past (and some bigger patches for my experiments which were
> never released) and now I have some time to continue.
>
> I'm going to add missing switches into mixer, make some changes in mixer
> to match the real I/O setup of each particular card model and perhaps
> also write some graphics patchmix like app.
>
A graphics patchmix like app would be the most useful at the moment. It
would permit us to enable the 96kHz and 192kHz options, as for these
different DSP code needs to be loaded, and that is best left to userland.
> Unfortunatelly, I'm unable to fix the most important bugs (at least from
> my point of view) dua to lack of documentation and knowlenge of DSP
> programming. These are:
>
> 1. non working 24bit playback. It should be on device 0,2 This device
> exists, but cannot be openned for playback.It is the last thing needed
> for serious DAW.
>
I will look into this. Please raise a bug on alsa-project.org so we
don't forget this.
> 2. Non working S/PDIF (and probably ADAT, too) on 1616(M) microdock
> ports. I think tese ports uses different set of registers than PCI 1010
> host card. Am I right?
>
Correct, they are different. I will try to update the driver with some
details tomorrow.
> 3. Midi I/O works well on 1212m v1, but only when 48kHz is set. At
> 44.1kHz signalling is corrupted (different UART timing? How to fix it?).
> On 1616m microdock MIDI I/O does not work at all.
>
There is no mention in the docs regarding the clock rates affecting MIDI
at all.
I think this might be a trial and error fix.
There is an extra register for midi routing config on the 1616m, so I
might have to get that sorted.
> I welcome any comments, advices and patches ;)
>
> ----
> Ctirad
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
next prev parent reply other threads:[~2007-11-11 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 21:02 E-mu 1212M/1820M/1616M development Ctirad Fertr
2007-11-11 22:51 ` James Courtier-Dutton [this message]
2007-11-12 22:35 ` James Courtier-Dutton
2007-11-13 13:15 ` Ctirad Fertr
2007-11-18 4:54 ` E-mu 1212M ADAT channels missing ? Kenneth Long
2007-11-18 10:45 ` Ctirad Fertr
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=47378776.6050403@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=c.fertr@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).