On Monday, 24 July 2006 16:38, Lee Revell wrote:
Take the sequence 80 3D 35 31 80 3A 39 0E 80 37 31 03 80 31 1F in
the first line for example. I know that 0x80 is note-off, and 0x3D are
note number and 0x35 the velocity of the note-off. But what the heck is
the next byte, 0x31?
Delta
On Monday, 19 June 2006, Stephen Cameron wrote:
http://www.alsa-project.org/alsa-doc/alsa-lib/seq.html
Thanks, I'd found that already... it's slightly better than no
documentation. :-) But I'll take what I can get. It's a little
rough going at first when it kind of assumes you're aware of
On Sunday, 18 June 2006, Stephen Cameron wrote:
Hi,
I'm trying to figure out how to use the ALSA sequencer
with my app. (to date, I've been just using raw midi).
[..]
But if I take out this line
snd_seq_ev_set_dest(ev, 128, 0);
And replace it with:
On Thursday, 20 de April de 2006 09:57:14 -0400, Paul Winkler wrote:
I can understand not wanting to maintain it any more,
but where'd the download go??
http://gazuga.net/files -- 404
Here are the last files:
http://gazuga.net/specimen/files/
And here some old ones:
On Thursday, 20 de April de 2006 13:49:19 -0400, Paul Winkler wrote:
Sorry to disturb your eternal slumber, RIP.
You are burying the wrong guy. It was Pete Bessman who lived fast, died young,
and left a good-looking corpse behind.
Regards,
Pedro
On Wednesday 01 March 2006 12:51, Julian Storer wrote:
James Courtier-Dutton wrote:
default means just that. use the name default instead of
plughw: or hw:0,0
[...]
Ok, at the risk of spreading the myth that the ALSA documentation is
bad... is this stuff actually explained anywhere??
On Saturday 31 December 2005 00:52, Florian Schmidt wrote:
All of this depends on whether physical port midi activity is really
handled by IRQ's too. Anyone know more?
I don't know every MIDI interface details, but there are many different
variations. Please, somebody with better knowledge
On Saturday 31 December 2005 17:10, Paul Davis wrote:
On Fri, 2005-12-30 at 22:27 +0100, Pedro Lopez-Cabanillas wrote:
On Friday 30 December 2005 17:37, Werner Schweer wrote:
The ALSA seq api is from ancient time were no realtime threads were
available in linux. Only a kernel driver could
On Friday 30 December 2005 17:37, Werner Schweer wrote:
The ALSA seq api is from ancient time were no realtime threads were
available in linux. Only a kernel driver could provide usable
midi timing. But with the introduction of RT threads the
ALSA seq api is obsolete IMHO.
I don't agree with
?download
http://prdownloads.sourceforge.net/kmetronome/kaseq-0.2.3.tar.gz?download
Copyright (C) 2005, Pedro Lopez-Cabanillas plcl AT users.sourceforge.net
Released under the terms of the GNU General Public License (GPL)
References
[1] DCOP
http://developer.kde.org/documentation/other/dcop.html
[2
Now, what would an amidi command look like that guarantees to update
each and every midi-device found with said sysex file?
amidiall.sh
CUT
#!/bin/bash
CMD=$(which amidi)
PORTLIST=$($CMD -l|awk '/^hw:/ { print $1 }')
for P in $PORTLIST; do
echo $CMD --port=$P $*
$CMD
rosegarden and muse's source it seems there's always app specifics
intertwined.
Sure, *because* there wasn't a standard midifile library around in the
first place, they all hacked it into the program directly, therefore it is
intertwined :-).
No. The first release date of Thompson's
libmidifile would be cute, is any of the existing codebases flexible
enough so that it could be massaged into a nice lib?
vote++ to everything you said. dunno about any existing midi code though
flexible enough to be put into a lib.. After taking a glance at
rosegarden and muse's source it
,
Pedro
/*
* Copyright (C) 2005 Pedro Lopez-Cabanillas [EMAIL PROTECTED]
*
* This program sends a sysex MIDI message to an ALSA sequencer port
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License version 2
KMidimon 0.1
KMidimon is a MIDI monitor for Linux using ALSA sequencer, with KDE user
interface.
Quoting Dave Phillips in a three parts article for Linux Journal: At some
point, almost every serious MIDI musician needs to monitor a MIDI data stream,
perhaps to diagnose a
On Thursday 25 November 2004 18:02, Chris Cannam wrote:
On Wednesday 24 Nov 2004 22:06, Jens M Andreasen wrote:
According to my oldish midi-spec, controller (decimal) 120 is
undefined, so I was somewhat confused at first when I got it from
Rosegarden.
A bit of digging shows that it
On Monday 22 November 2004 18:07, Hans Fugal wrote:
Is there an app that will dump midi events in human-readable format to
stdout (or a file, or gui window, whatever)? Preferably it would work on
SMF as well as realtime (ALSA), and have filters to filter out
undesirables (e.g. active sensing
On Friday 10 September 2004 Eric Dantan Rzewnicki wrote:
On Thu, Sep 09, 2004 at 07:18:57PM +0200, Pedro Lopez-Cabanillas wrote:
And now Avid (the company owning Digidesign) bought M-Audio.
[...]
Really!?! when did that happen?
http://www.avid.com/company/releases/2004
On Friday 10 September 2004 Martijn Sipkema wrote:
The problem here is that class compliant devices suffer bad timing
because they use bulk transfers for MIDI data. The standard for
MIDI over FireWire is much better.
I don't agree on the subject that USB bulk transfers cause bad MIDI timing.
On Thursday 09 September 2004, Clemens Ladisch wrote:
M-Audio started following suit only after they hung their engineers
with a USB cable and bought Evolution who had always made
class-compliant devices.
And now Avid (the company owning Digidesign) bought M-Audio. I hope to see the
engineers
at this moment. I would like to know if you have more information,
ideas or want to collaborate in this task.
Regards,
Pedro
On Sunday 29 August 2004 01:50, Pedro Lopez-Cabanillas wrote:
Hi,
I have many old songs, stored as Cakewalk WRK files, and I don't use
Cakewalk or Sonar anymore. I'm not planning
El Sábado, 9 de Agosto de 2003 18:00, Benno Senoner escribió:
Basically I read the MTrk shown below and after the
ff 01 TEXT meta event which contains the text 'Reset Volume'
there are sequences of 00 07 7f till the next ff 01 text event
'Reset Pan'.
But the midi file spec says that after
Good hack, Clemens!
I've created a package which extracts the firmware for MidiSport devices
from the Windows driver files and installs the hotplug script to download
the firmware. You can get it at
http://www.informatik.uni-halle.de/~ladischc/midisport_linux_firmware.html
.
There are some
23 matches
Mail list logo
