Bug 68909 - timidity++ makes dreadful noise on amd64
Summary: timidity++ makes dreadful noise on amd64
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Norikatsu Shigemura
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-11 05:20 UTC by Conrad J. Sabatier
Modified: 2005-04-12 21:13 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Conrad J. Sabatier 2004-07-11 05:20:15 UTC
	timidity++ with eawpats on amd64 creates horrible, screeching 
	noise over the music.  The music can be heard playing, but is 
	nearly drowned out by the terrible noise.
 >How-To-Repeat:
	install timidity++ and eawpats ports, configure in normal fashion, 
	play a file, then cover your ears!  :-)

Fix: 

Don't know what the problem is.  I've tried numerous 
	configurations and command line options, all yield the same results.  
	Never had this problem on i386.
Comment 1 Norikatsu Shigemura freebsd_committer freebsd_triage 2004-07-11 08:23:35 UTC
Responsible Changed
From-To: freebsd-ports-bugs->nork

I am working to upgrade timidity++(to 2.13.0), and I contacted 
to maintainer, but he doesn't reply this.  So I'll handle this. 
You can get following a patch and shars. 
http://tmp.ninth-nine.com/timidity++/timidity++.diff 
http://tmp.ninth-nine.com/timidity++/eawplus.shar 
http://tmp.ninth-nine.com/timidity++/guspat.shar 
But, these are not working about timidity++ slave ports.  The 
master port looks good.  If you have any idea, please feed back to me.
Comment 2 Florent Thoumie 2005-04-12 13:50:25 UTC
	What's the current state of this PR ?

-- 
Florent Thoumie
flz@xbsd.org
Comment 3 Conrad J. Sabatier 2005-04-12 19:11:11 UTC
On Tue, 12 Apr 2005 14:50:25 +0200, Florent Thoumie <flz@xbsd.org>
wrote:

> 	What's the current state of this PR ?
> 
> -- 
> Florent Thoumie
> flz@xbsd.org

I believe it was still open last time I looked, but it should really be
closed, now that the new update has been committed.

Thanks!

-- 
Conrad J. Sabatier <conrads@cox.net> -- "In Unix veritas"
Comment 4 Florent Thoumie freebsd_committer freebsd_triage 2005-04-12 21:13:22 UTC
State Changed
From-To: open->closed

Closed at submitter's request.