melys-devel Mailing List for Melys sequencer

On Sun, Dec 22, 2002, Sylvain Lavoie wrote:
> Hello everyone,
> 
> I was just wondering is Melys still being developped?  

	In fact I don't know, I was asking me the same question, (I've
	just realized I'm still on this list thanks to your mail)

> Is anyone using Melys with version 0.9.x of ALSA?

	Not me yet.  At this time I'm testing other sequencers and 
	I'll try again melys soon (I'm testing muse right now, and
	facing a MidiIn problem).

	Take care.

-- 
o Pétition contre les brevets logiciels : http://petition.eurolinux.org
o Tony Bassette:      tba...@ap... ( ICQ : 25995434 )
o APRIL :             http://www.april.org/
o THE CORRS :         http://www.thecorrs.net/

Hello everyone,

I was just wondering is Melys still being developped?  Is anyone using 
Melys with version 0.9.x of ALSA?

Thanks,
Sylvain

PS: Please send me a reply (mailto:la...@nb...) cause I'm not 
currently subscribed to the list!

Steve Ratcliffe <st...@pa...> wrote:
> I don't know of any problem that would cause this.  Does the midi file
> contain tempo changes?  

	No it doesn't ...

> What version of ALSA are you using?

	I'm currently using the Alsa 0.5.9c.

> There have been changes to ALSA in the which caused tempo changes not
> to take affect.  But this was a fair while ago so it is probably not the
> problem.
> 
> Let me know if you have any more details.

	I'll redo some test tonight and send you as many details I'll be able 
	to get

-- 
o Pétition contre les brevets logiciels : http://petition.eurolinux.org
o Tony Bassette:      tba...@ap... ( ICQ : 25995434 )
o APRIL :             http://www.april.org/
o THE CORRS :         http://www.thecorrs.net/

On Fri, Nov 03, 2000 at 10:23:07AM +0100, Tony Bassette wrote:
> 	I've just discovered Melys and thougt that it will be very useful for 
> 	me. But when I try to play a mid file (generated by cubase or jazz)
> 	the tempo of the beginning of the song act strange going slow to fast
> 	to the regular speed.

I don't know of any problem that would cause this.  Does the midi file
contain tempo changes?  What version of ALSA are you using?

There have been changes to ALSA in the which caused tempo changes not
to take affect.  But this was a fair while ago so it is probably not the
problem.

Let me know if you have any more details.

> 	I think that's enought for a first post, and far to be the latest one.
> 
> 	I hope I can help you in anyway I can. 

Thanks, cheers,
..Steve

	Hi everyone,

	I've just discovered Melys and thougt that it will be very useful for 
	me. But when I try to play a mid file (generated by cubase or jazz)
	the tempo of the beginning of the song act strange going slow to fast
	to the regular speed.

	I think that's enought for a first post, and far to be the latest one.

	I hope I can help you in anyway I can. 

	Take Care.

-- 
o Pétition contre les brevets logiciels : http://petition.eurolinux.org
o Tony Bassette:      tba...@ap... ( ICQ : 25995434 )
o APRIL :             http://www.april.org/
o THE CORRS :         http://www.thecorrs.net/

Hi,

On Tue, Apr 04, 2000 at 09:57:53AM -0500, R. Steven Rainwater wrote:
> Thanks! I added the patch and it works great now.
> Both Melys and seq can see the incoming MIDI data.
> I assume this patch will go into the main ALSA code
> before the next release? 

Thats great.

I sent it to the bug database and actually looks like it
was fixed in CVS today, even though its still in INCOMING
in the database.

..Steve

On Tue, 4 Apr 2000 00:17:15 +0100, Steve Ratcliffe wrote:

>> [SB Live! not recording, but probably applies to all cards]
>
>OK I have now found the problem.  Apply the patch below to alsa-driver.
>This probably is a bug with all cards, not just the Live!

Thanks! I added the patch and it works great now.
Both Melys and seq can see the incoming MIDI data.
I assume this patch will go into the main ALSA code
before the next release? 

-Steve


_____________________________________________________________________
R. Steven Rainwater * http://www.ncc.com/humans/srainwater/index.html
"As you struggle to save humanity be sure to avoid electrodes in
your path"  -- Robotron 2084

> [SB Live! not recording, but probably applies to all cards]

OK I have now found the problem.  Apply the patch below to alsa-driver.
This probably is a bug with all cards, not just the Live!

..Steve

Index: kernel/seq/seq_midi_event.c
===================================================================
RCS file: /usr/src/CVS/alsa-driver/kernel/seq/seq_midi_event.c,v
retrieving revision 1.1.1.8
diff -u -r1.1.1.8 seq_midi_event.c
--- kernel/seq/seq_midi_event.c	2000/04/02 19:16:39	1.1.1.8
+++ kernel/seq/seq_midi_event.c	2000/04/03 23:12:53
@@ -221,8 +221,7 @@
 	int rc = 0;
 	unsigned long flags;
 
-	if (c < 0 || c > 0xff)
-		return -EINVAL;
+	c &= 0xff;
 
 	if (c >= SND_MCMD_COMMON_CLOCK) {
 		/* real-time event */

> I installed the current CVS code over the weekend.
> Melys no longer segfaults when I try to record MIDI
> but nothing is recorded. Could you post your 

I upgraded yesterday to the latest CVS and I am also seeing that recording
has stopped working.  I'll investigate and then get back to you.

..Steve

On Sat, 1 Apr 2000 16:22:48 +0100, Steve Ratcliffe wrote:

>I also have a Live! but I do not see this problem on either input
>or output.  I am using a version of ALSA from CVS just after 0.5.6,
>so the problem may have been fixed.

I installed the current CVS code over the weekend.
Melys no longer segfaults when I try to record MIDI
but nothing is recorded. Could you post your 
conf.modules (or modules.conf!) contents so I can
compare them to mine? Also what linux kernel version
are you using?

>Not being able to restart the driver is definitely an ALSA error.
>Have a look in /var/log/messages and see if there is an Oops
>message written when the problem occurs.

I checked and nothing was appearing in the log
either with the 0.5.6 version or the current CVS
version of ALSA.

>You can use the alsa-lib/test/seq program to receive MIDI
>events and print out them out:
>
>	seq decoder 64.0

Thanks! This was very helpful - having two programs
to test the port allows me to reduce the number of
variables. It's very clear at this point that Melys
has nothing to do with the problem - it must be in
ALSA (either a bug or config problem). Using the
command above I get two lines of output indicating
that the port is being monitored but nothing else
is ever displayed regardless of whether or not the
attached MIDI device is sending data.

-Steve


_____________________________________________________________________
R. Steven Rainwater * http://www.ncc.com/humans/srainwater/index.html
"As you struggle to save humanity be sure to avoid electrodes in
your path"  -- Robotron 2084

Your problem looks similar to ALSA bug number 619:

	http://www.alsa-project.org/cgi-bin/bugs/00_INCOMING?id=619;user=guest;selectid=619

Although the bug report is saying it happens on output, while you are
seeing a problem on input.

I also have a Live! but I do not see this problem on either input
or output.  I am using a version of ALSA from CVS just after 0.5.6,
so the problem may have been fixed.

> Am I doing something wrong? Is there a way to test the
> port using another program so I can determine if melys
> or ALSA is to blame? Also, once melys segfaults, port
> 64:0 becomes unusable for reading *or* writing until I
> reboot the computer. I am unable to simply restart the
> ALSA driver - it insists that it is in use.

Not being able to restart the driver is definitely an ALSA error.
Have a look in /var/log/messages and see if there is an Oops
message written when the problem occurs.

You can use the alsa-lib/test/seq program to receive MIDI
events and print out them out:

	seq decoder 64.0

..Steve

On Wed, 29 Mar 2000 20:44:17 +0100, Steve Ratcliffe wrote:

>> 2) MIDI event capture. Is this already implemented?
>
>It should just work once you have set ALSA_INPUT_PORTS.  (You also need
>to ensure that the snd-seq-midi module is loaded) All MIDI events are
>captured/recorded, even ones that you can't yet edit such as pitch-bend,
>controllers and sysex.

I was able to make half of it work. I connected a
Yamaha PSR-270 keyboard to the Sound Blaster Live!,
did a "modprobe snd-seq-midi", and then set both
ALSA_INPUT_PORTS=64:0 and ALSA_OUTPUT_PORTS=64:0.
Using both pmidi and melys I can send MIDI data
to the keyboard without problems. 

However, I can't seem to get MIDI-in to work. It
may be user error. Here's what happens everytime:

1. load melys
2. On track one click the record button
3. melys segfaults

Am I doing something wrong? Is there a way to test the
port using another program so I can determine if melys
or ALSA is to blame? Also, once melys segfaults, port
64:0 becomes unusable for reading *or* writing until I
reboot the computer. I am unable to simply restart the
ALSA driver - it insists that it is in use.

All the other ALSA driver features for the Sound Blaster
Live! card seem to work. I can play .wav files, use the
internal synth, play MIDI files internally, download and
use soundfont files, and use external MIDI output. Only
the external MIDI input seems to be a problem.

I'm using the Sound Blaster Live! value card, Red Hat
6.1 with the stock 2.2.12 kernel, and ALSA 0.5.6.

FWIW, here's my conf.modules setup:

 # Alsa stuff
 alias char-major-116 snd
 options snd snd_major=116 snd_cards_limit=1 snd_device_mode=0666 snd_device_gid=0 snd_device_uid=0
 alias snd-card-0 snd-card-emu10k1
 options snd-card-emu10k1 snd_index=0
 # OSS compatibility stuff
 alias char-major-14 soundcore
 alias sound-slot-0 snd-card-0
 alias sound-service-0-0 snd-mixer-oss
 alias sound-service-0-1 snd-seq-oss
 alias sound-service-0-3 snd-pcm-oss
 alias sound-service-0-8 snd-seq-oss
 alias sound-service-0-12 snd-pcm-oss

And the sequencer port info (prior to the segfault):

 Client info
   cur  clients : 5
   peak clients : 10
   max  clients : 192

 Client   0 : "System" [Kernel]
   Port   0 : "Timer" (system:Rwe:Rwe-)
   Port   1 : "Announce" (system:R-e:R-e-)
     Connecting To: 63:0
 Client  63 : "OSS sequencer" [Kernel]
   Port   0 : "Receiver" (system:-we:-we-)
     Connected From: 0:1
 Client  64 : "External MIDI 0" [Kernel]
   Port   0 : "MIDI 0-0" (device:RWe:RWeX)
 Client  65 : "Emu10k1 WaveTable" [Kernel]
   Port   0 : "Emu10k1 Port 0" (device:-We:-We-)
     Connected From: 128:0[t:0]
   Port   1 : "Emu10k1 Port 1" (device:-We:-We-)
     Connected From: 128:0[t:0]
   Port   2 : "Emu10k1 Port 2" (device:-We:-We-)
     Connected From: 128:0[t:0]
   Port   3 : "Emu10k1 Port 3" (device:-We:-We-)
     Connected From: 128:0[t:0]
 Client 128 : "Melys sequencer" [User]
   Port   0 : "port-0" (application:rWe:rWe-)
     Connecting To: 65:0[t:0], 65:1[t:0], 65:2[t:0], 65:3[t:0]
   Output pool :
     Pool size          : 200
     Available cells    : 199
     Cells in use       : 1
     Peak cells in use  : 1
     Alloc success      : 1
     Alloc failures     : 0
     Alloc no-pool      : 0
   Input pool :
     Pool size          : 200
     Available cells    : 200
     Cells in use       : 0
     Peak cells in use  : 0
     Alloc success      : 0
     Alloc failures     : 0
     Alloc no-pool      : 0 



-Steve

_____________________________________________________________________
R. Steven Rainwater * http://www.ncc.com/humans/srainwater/index.html
"As you struggle to save humanity be sure to avoid electrodes in
your path"  -- Robotron 2084

Hello,

> 1) The instrument selection dialog. It appears that 
> this hasn't been finished yet - what's the time frame
> on this? If no one else is currently working on it,
> who do I send patches to? ;-) 

Yes, this is not finished and no-one is working on it.  So if you
have patches this would be excellent, send them to me (or the list for
small ones).

> 2) MIDI event capture. Is this already implemented?

Oh yes, it certainly is.  This was one of the very first things to
be written, way before there was a graphical display.

> (I wasn't sure from the docs if this is what
> "record" does or not). What I'd like is to be able
> to plug in my MIDI keyboard and enter notes directly
> into Melys.

It should just work once you have set ALSA_INPUT_PORTS.  (You also need
to ensure that the snd-seq-midi module is loaded) All MIDI events are
captured/recorded, even ones that you can't yet edit such as pitch-bend,
controllers and sysex.

..Steve

Hi,

I was wondering about the status of a couple of
Melys features. I just subscribed to this list so
forgive me if these have already been discussed!
(I checked for a list archive but it didn't seem
to have anything in it)...

1) The instrument selection dialog. It appears that 
this hasn't been finished yet - what's the time frame
on this? If no one else is currently working on it,
who do I send patches to? ;-) 

2) MIDI event capture. Is this already implemented?
(I wasn't sure from the docs if this is what
"record" does or not). What I'd like is to be able
to plug in my MIDI keyboard and enter notes directly
into Melys.

Thanks!

-Steve


_____________________________________________________________________
R. Steven Rainwater * http://www.ncc.com/humans/srainwater/index.html
"As you struggle to save humanity be sure to avoid electrodes in
your path"  -- Robotron 2084

Hi,

Version 0.1.15 of Melys is out.  It has some bugs fixed which showed up
when more than one file was open.  This is due the the ALSA changes so
that would only affect you if you were using the latest ALSA CVS.

The new thing is the beginning of a grid for a background in the views.
At present it just shows bar lines, but it will be more configurable in
the future.

..Steve

Just the obligatory test message.

..Steve