All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Enderborg <pme@ufh.se>
Cc: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Re: Rawmidi bug or missed feature?
Date: Fri, 01 Mar 2002 20:22:27 +0100	[thread overview]
Message-ID: <3C7FD4F3.BFDA1791@ufh.se> (raw)
In-Reply-To: 200203011345.IAA12541@renoir.op.net

Paul Davis wrote:

> >I have a program that read's from a raw midi device. In midi there
> >are some simple compression.  It is assumed that if the data flow is
> >correct, and the data should be interpreted as paramaters to previus
> >command if it's not a new command. But when I open a raw midi stream
> >I can get in to the stream without having the "previus" command. Is
> >there any way to do a query or reset the stream so I can get that
> >command? If it's only one midi channel sending the same type of
> >command it will never get in to sync!
>
> raw MIDI means ***RAW*** MIDI. there is no parsing, no state, no
> history, no automatic reset. you just read and write a stream of
> bytes.
>

Yes it raw. But it's sent by the sequcenser within alsa.  So the state is
there.

This is the configuration:

Roland MCR-8->midi-device->alsa-seq->user_code->alsa-seq->raw_midi

So how far back should I need to reset? The communication roland and
alsa-seq is in sync and
my user-land code is sending snd_seq_event_t. I guess that my problem
will disapear if I turn
active-sening-on and that is what I going to try.

>
> it sounds as if you should issue a full MIDI reset sequence when you
> open the device (all notes off on every channel, reset all controllers
> to a default value, restore all programs to a known state, etc.)
>

That will not help my reading. The device is in sync with alsaseq and
there shuld not
be needed to reset the transmitter. And even if I do. The merge of midi
streams could be
smart enough to see that it is of the same type.

>
> --p

--
foo!




_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

  parent reply	other threads:[~2002-03-01 19:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28 22:56 Rawmidi bug or missed feature? Peter Enderborg
2002-03-01 13:45 ` Paul Davis
2002-03-01 14:58   ` Ricardo Colon
2002-03-01 19:22   ` Peter Enderborg [this message]
2002-03-01 20:30     ` Paul Davis
2002-03-01 21:06       ` Peter Enderborg
2002-03-01 21:31         ` Paul Davis
2002-03-01 22:18           ` Peter Enderborg
2002-03-02 11:14             ` Jaroslav Kysela
2002-03-02 13:31               ` Peter Enderborg
2002-03-02 17:11                 ` Paul Davis
2002-03-02 17:45                   ` Peter Enderborg
2002-03-02 18:01                     ` Paul Davis
2002-03-02 18:37                       ` Peter Enderborg
2002-03-02 18:58                         ` Paul Davis
2002-03-02 19:15                           ` Peter Enderborg
2002-03-02 19:31                             ` Paul Davis
2002-03-02 22:22                               ` ALSA sequencer in user land (was: Rawmidi bug or missed feature?) Frank van de Pol
2002-03-02 17:55                                 ` Paul Davis
2002-03-03  0:34                                   ` Frank van de Pol
2002-03-02 20:18                                     ` Paul Davis
2002-03-03  4:13                                       ` CAPs Bob Ham
2002-03-02 17:55                 ` Rawmidi bug or missed feature? Roger E Critchlow Jr
2002-03-02 18:36                   ` Peter Enderborg
2002-03-02 20:43                     ` Roger E Critchlow Jr
2002-03-02 22:20                       ` Peter Enderborg
2002-03-01 21:32         ` Paul Davis
2002-03-02 10:28 ` Jaroslav Kysela

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=3C7FD4F3.BFDA1791@ufh.se \
    --to=pme@ufh.se \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.