alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Martin Tarenskeen <m.tarenskeen@zonnet.nl>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	Alsa-devel mailinglist <alsa-devel@alsa-project.org>,
	Clemens Ladisch <clemens@ladisch.de>
Subject: Re: [PATCH 1/2] amidi: ignore not only Active Sensing but all System Real-Time messages
Date: Mon, 11 Apr 2016 13:17:54 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1604111304310.4695@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.02.1604110858100.9999@lnxricardw1.se.axis.com>



On Mon, 11 Apr 2016, Ricard Wanderlof wrote:

>
> On Sun, 10 Apr 2016, Clemens Ladisch wrote:
>
>> By default, amidi ignores Active Sensing messages because they are sent
>> by many devices in the background and would only interfere with the
>> actual messages that amidi is supposed to capture.  However, there are
>> also devices that send Clock messages with the same problem, so it is
>> a better idea to filter out all System Real-Time messages.
>
> I would argue that it would be better to have both options, somehow. I.e.
> active sensing is mostly a nuisance, but I can imagine occasions
> (analyzing the output from a sequencer perhaps) where one would want to
> keep the rest of the real time messages.

Hi,

I can see your point. I have been thinking about that but my coding skills 
are somewhat limited. I can image keeping the -a (--allow-realtime) option 
the way it is and adding a new option -c (--allow-clock) to allow 
receiving of 0xf8 midiclock messages. At the same time 0xf8 should be 
filtered by default, just like 0xfe. The other realtime messages are much 
less a problem because they are not sent continuously (e.g. start and 
stop)

What do you think Clemens Ladich, is this doable?

-- 

Martin Tarenskeen

  reply	other threads:[~2016-04-11 11:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-10 19:29 [PATCH 1/2] amidi: ignore not only Active Sensing but all System Real-Time messages Clemens Ladisch
2016-04-10 19:30 ` [PATCH 2/2] amidi: fix timeout handling Clemens Ladisch
2016-04-11  7:00 ` [PATCH 1/2] amidi: ignore not only Active Sensing but all System Real-Time messages Ricard Wanderlof
2016-04-11 11:17   ` Martin Tarenskeen [this message]
2016-04-11 11:47     ` Martin Tarenskeen
2016-04-11 13:29   ` Clemens Ladisch
2016-04-11 13:41     ` Ricard Wanderlof
2016-04-11 14:13       ` Clemens Ladisch
2016-04-11 14:18         ` Ricard Wanderlof
2016-04-17 13:21   ` [PATCH v2 1/2] amidi: ignore not only Active Sensing but also Clock bytes Clemens Ladisch
2016-04-17 13:21     ` [PATCH v2 2/2] amidi: fix timeout handling Clemens Ladisch

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=alpine.LFD.2.20.1604111304310.4695@localhost.localdomain \
    --to=m.tarenskeen@zonnet.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=ricard.wanderlof@axis.com \
    --cc=tiwai@suse.de \
    /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).