Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001930]: Can`t get timidity woking in soft synth mode
Date: Mon, 20 Mar 2006 23:40:02 +0100	[thread overview]
Message-ID: <bc06377842e84ca1278a938283ed7873@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1930> 
======================================================================
Reported By:                drolyk
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   1930
Category:                   PCI - intel8x0
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Distribution:               Debian
Kernel Version:             2.6.15.6
======================================================================
Date Submitted:             03-15-2006 23:41 CET
Last Modified:              03-20-2006 23:40 CET
======================================================================
Summary:                    Can`t get timidity woking in soft synth mode
Description: 
Can`t get timidity woking in "soft synth mode".
======================================================================

----------------------------------------------------------------------
 rlrevell - 03-20-06 23:29 
----------------------------------------------------------------------
I think this is a Timidity issue not an ALSA problem.  Did it work with
previous versions?

Fluidsynth does not have a soft synth mode, it only supports soundfonts.

----------------------------------------------------------------------
 fdoffizi01 - 03-20-06 23:40 
----------------------------------------------------------------------
So this is something magic?

ciccio@Vaiolo ~ $ aplaymidi -l
 Port    Client name                      Port name
128:0    FLUID Synth (5036)               Synth input port (5036:0)

Fluid synth HAS soft synth function and suffer the same exact problems as
timidity when used in this way: player plays but no sound comes out (and
only first few midi (instrument settings I think) commands are received as
I can see from fluidsynth message log).

That's why I think it's not a timidity issue. Is alsa who actually creates
port for these soft synths? May be the problem is there...

Issue History
Date Modified  Username       Field                    Change              
======================================================================
03-15-06 23:41 drolyk         New Issue                                    
03-15-06 23:41 drolyk         Distribution              => Debian          
03-15-06 23:41 drolyk         Kernel Version            => 2.6.15.6        
03-19-06 23:55 fdoffizi01     Note Added: 0008700                          
03-20-06 01:28 rlrevell       Note Added: 0008702                          
03-20-06 01:42 fdoffizi01     Note Added: 0008703                          
03-20-06 03:24 rlrevell       Note Added: 0008706                          
03-20-06 06:08 drolyk         Note Added: 0008709                          
03-20-06 06:22 rlrevell       Note Added: 0008710                          
03-20-06 07:19 Raymond        Note Added: 0008711                          
03-20-06 12:55 fdoffizi01     Note Added: 0008718                          
03-20-06 15:50 fdoffizi01     Issue Monitored: fdoffizi01                    
03-20-06 22:19 drolyk         Note Added: 0008726                          
03-20-06 22:21 drolyk         Note Edited: 0008726                         
03-20-06 22:36 fdoffizi01     Note Added: 0008727                          
03-20-06 23:29 rlrevell       Note Added: 0008729                          
03-20-06 23:40 fdoffizi01     Note Added: 0008730                          
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

             reply	other threads:[~2006-03-20 22:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20 22:40 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-19  9:06 [ALSA - driver 0001930]: Can`t get timidity woking in soft synth mode bugtrack
2006-04-26 11:48 bugtrack
2006-04-20 12:37 bugtrack
2006-04-19 14:56 bugtrack
2006-04-19  8:08 bugtrack
2006-04-15  8:49 bugtrack
2006-03-21  9:58 bugtrack
2006-03-21  7:46 bugtrack
2006-03-20 23:14 bugtrack
2006-03-20 22:54 bugtrack
2006-03-20 22:29 bugtrack
2006-03-20 21:36 bugtrack
2006-03-20 21:19 bugtrack
2006-03-20 11:55 bugtrack
2006-03-20  6:19 bugtrack
2006-03-20  5:22 bugtrack
2006-03-20  5:08 bugtrack
2006-03-20  2:24 bugtrack
2006-03-20  0:42 bugtrack
2006-03-20  0:28 bugtrack
2006-03-19 22:55 bugtrack
2006-03-15 22:41 bugtrack

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=bc06377842e84ca1278a938283ed7873@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /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