hi,
i am not sure how to write support for midi interfaces
on a serial port. the best way i think would be a pseudo
alsa midi driver (as a pty). do these exist already?
and where can i find the most up to date documentation
on alsa midi (but not /dev/sequencer).
--martijn
_
hi,
i think someone once started writing an alsa driver for the
emagic audiowerk8 card, but i have not been able to find
it, so probably it didn't get finished. does anyone here know
anything about this driver? perhaps there is still some code
somwhere or at least documentation on the hardware? i
> So, i think there's a time to code THEN there a time
> to build docs (the doxygen sections in code are oftenly updated).
>
> This is why i think there is a non-sense in this *advandage*
> of OSS here.
I don't agree. Good documentation is essential and I see the lack
of it as a serious pr
> The following patch:
>
> http://fett.net/m/alsa/alsa-0.9.0rc1-unitor8.patch
>
> implements a driver for the Emagic Unitor family of multiport MIDI
> interfaces. Only serial connection is supported. You need to rerun the
> autoconf toolchain after applying the patch.
>
> The driver is heavily bas
> > I have that document also. Emagic would not give me any AMT
> > documentation, that's why I aksed.
>
> Did they actually say 'no', or just didn't answer?
They did asnwer:
> Hi there,
> as AMT is our own standard and permanently improved, there is no
> possibility of public access of the te
> > This is nice. What documentation did you use for writing the driver?
>
> http://www.math.tu-berlin.de/~sbartels/unitor/unitor8_doc.txt
>
> It's in German. I have a translation of it I made using some online
> translation thingy a while ago, but I still find the German version a bit
> more re
I'm working on a library for accessing MIDI hardware, which uses plugins
to communicate with the hardware. Now I'm not sure how to compile
these shared libraries. Should I use -Bsymbolic? This makes the linker
give a warning when the library is not linked against all the shared
libraries
it needs
below is a message i sent earlier, but with the wrong email address:
writing audiowerk driver (philips saa7146a), some questions
hi,
i have finally been able to get the information i need to be able
to write a driver for the emagic audiowerk8 audio interface.
now since i am not an ex
> > - does alsa allow varipitch? i think the new rme cards are supposed to
> > have this feature and the audiowerk8 has it, i.e. it can change its
> > sampling
> > rate from about 37700 to 58200 hz while running in 1hz increments.
> > this allows for sync to video/tape/midi or whatever. or it
> > - should i use the normal double buffered aproach or does having
> > more than 2 buffers have advantages?
>
> most of pci drivers use a linear contigous buffer for pcm (per
> stream).
> the scatter-gather buffer is not supported yet on alsa (as a mid/high
> level layer -- it would be possibl
> there is a runtime instance for a pcm stream, and this holds the
> informaton such as the current rate, channels, formats, etc.
> there is no pitch parameter implemented in alsa, but this can be added
> easily into the runtime instance, if inevitablly necessary.
i don't think the audiowerk is t
> > i don't think the audiowerk is the only card capable of varipitch,
though
> > most cards don't support it, but it is a nice feature and since alsa is
> > supposed to be advanced... :)
>
> many consumer chips support in fact, too, such as emu10k1, ymfpci,
> cs46xx (also trident?) sbawe and gus
> it seems that USB audio supports 24 bit sample in 3 bytes format.
> and additionally i've found there are 20bit and 18bit sample formats.
> the world is large...
>
> an arising problem is that the number of formats is limited to 32.
> already 26 format types are used. the rest are only 6, and
> are formats currently a bit in a 'supported formats' flag?
i meant mask instead of flag...
--martijn
___
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/a
> > i have finally been able to get the information i need to be able
> > to write a driver for the emagic audiowerk8 audio interface.
>
> Did emagic give you information about the hardware, or is it from some
> other source?
Emagic pointed me to http://www.landamore.com/audiowerk.html
All the
> > > it seems that USB audio supports 24 bit sample in 3 bytes format.
> > > and additionally i've found there are 20bit and 18bit sample formats.
> > > the world is large...
> > >
> > > an arising problem is that the number of formats is limited to 32.
> > > already 26 format types are used. th
I again sent an email to alsa-devel using the wrong account. I think
it is all outlook's fault...
--martijn
- Original Message -
From: "Martijn Sipkema" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 05, 2002 7:50 PM
Subject: opening alsa
> you do it using ~/.asoundrc to define a PCM device that has the
> channel characteristics you want.
>
> next, you'll be asking how. that's the part i can't help you with. the
> archives have some examples, and there are several people on the list who
> can tell you.
aha, so the idea is that an
> >> correct. i know you love EASI
> >
> >is it that obvious? :)
> >
> >perhaps if more people like it, it would make sense porting
> >it to linux...
>
> much less sense than porting ASIO, i'm afraid. there are very few
> programs for win/macos that use EASI, but lots that use ASIO, and an
> ASIO
> correct. i know you love EASI
is it that obvious? :)
perhaps if more people like it, it would make sense porting
it to linux...
--martijn
___
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in
> > I have an AudiowerksII from Emagic. I was wondering what steps I could
> > take to get this supported by Alsa. I have some programming experience
> > but have never worked on device drivers before. I have contacted
> Emagic.
> > What Next?
Have Emagic supplied you with the specifications? Y
> Hi! I wanted to ask, how about forcing
> an absolute timestamp for _every_ midi event?
> I think this would be great for softsynths,
> so they dont need to work with root/schedfifo/lowlatency
> to have a decent timing. Not allways you are willing
> to process midi at the lowest latency possible.
[...]
> Is there already a commonly available UST on linux? To my knowledge the
only
> thing that comes close is the (cpu specific) cycle counter.
No, not yet. I think we should try to get hard- or firm-timers and POSIX
CLOCK_MONOTONIC into the Linux kernel.
--martijn
-
[...]
> > - Callback based.
>
> Callbacks on midi are retarded, and VERY annoying. It's simply
> throwing more work to the programmer which the lib can and should do.
> Seriosly, think about it, what is better?
Actually I was talking about the audio API in this case.
> > - All buffers in a call
[...]
> Well, i guess i didnt make myself clear enough.
> Technically, when you use some count/clock/tick based method
> for doing things, there is a certain hardware that generates such
> things.
> How are you sure that you will be able to generate those reliably
> within
> the OS? The only way i
[...]
> > I'm working on this, but it is not that easy since merging MIDI streams
> > is non-trivial and I want to be able to have hardware do the scheduling
if
> > it supports it and this means events can only be queued in timed order.
>
> Not necessarely; If you have the ability to adjust when y
[...]
> Within ALSA we have two priority queues, one for tick (bar,beat) scheduled
> events, and one for clock (ns) scheduled events.
As MIDI uses MIDI tick messages for time based sync and MIDI clock messages
for tempo based sync I kind of feel the ALSA sequencer naming is a little
confusing :)
> > I don't want to support tempo (MIDI clock) scheduling in my MIDI API.
This
> > could be better handled in the application itself. Also, when slaved to
MIDI
> > clock
> > it is no longer possible to send messages ahead of time, and not
supporting
> > this
> > in the API makes that clear to the
> Why is it important to keep the API simple, shouldn't it be functional in
first place and make the API usage simply?
Who says a simple API can't be functional?
> Anyway (IMHO), there should really be an API which combines audio and MIDI
playback, recording and timing of events and makes it pos
> > 4) BTW, is anyone working on MIDI RESET for ALSA 1.0.0?
> >alsa-kernel/core/rawmidi.c says MIDI reset is in the
> >TODO stage. I have instruments that sometimes need
> >MIDI reset. OSS/Linux 2.0.x had a handy seq_reset()
> >in drivers/sound/sequencer.c which mostly worked well
> >open pcm, and get a handle.
> >
> >snd_pcm_poll_descriptors(handle, &pfd, err);
> >
> >Get a poll file scriptor in pfd.
> >
> >select(nfds, rfds, wfds, efds, tvp);
> >
> >Is it possible to use this call with alsa ?
>
> select is generally deprecated in linux (linus says so!). but you can
> use
> > > >open pcm, and get a handle.
> > > >
> > > >snd_pcm_poll_descriptors(handle, &pfd, err);
> > > >
> > > >Get a poll file scriptor in pfd.
> > > >
> > > >select(nfds, rfds, wfds, efds, tvp);
> > > >
> > > >Is it possible to use this call with alsa ?
> > >
> > > select is generally deprecated i
> recently a technical information about emagic unitor8 was revealed,
I suppose this doesn't mention AMT? Can I have this information. It
might contain more than what I already have.
> and it includes a small desription about MTP, too.
> there, the initialization sysex is mentionted, so perhaps t
[...]
> > I suppose this doesn't mention AMT? Can I have this information. It
> > might contain more than what I already have.
>
> the info appeared in another thread (running-status bug on mtpav):
> http://www.math.tu-berlin.de/~sbartels/unitor/unitor8_doc.txt
> the project itself seems dead now
[...]
> It appeared that Martijn Sipkema was working on a library:
> http://sourceforge.net/mailarchive/message.php?msg_id=1511505
I'm sorry to say that it is nowhere near finished.
--ms
---
This SF.net email is sponsore
[...]
> If
> anyone would like, I can post information somewhere (just tell me).
Please do.
--ms
---
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance
36 matches
Mail list logo
