timidity-talk — TiMidity++ list in English.

Re: [timidity-talk] combined diff for various mixing pop-related bug fixes

[A. Z. <and...@co...>]

On Sun, 6 Sep 2009 18:57:40 -0500 (CDT)
Eric Welsh <ew...@bi...> wrote:

> 
> I have attached a diff that replaces the diff I sent earlier today, and
> fixes the other anti-popping measure I wrote many years ago as well.

Will these changes be going into CVS?  I'd rather download the entire
source from CVS than patch individual files.

Andrew Zimmer

[timidity-talk] combined diff for various mixing pop-related bug fixes

[Eric W. <ew...@bi...>]

mix.c: next_stage(), compute_mix_smoothing()

   Added new and corrected old volume-ramp related anti-popping measures.
   All volume ramps, whether from pans, expression/volume changes, or
   non-attack envelopes, now occur over a minimum window of 20 msec
   (incorrectly commented as 0.5 msec in previous versions).

Earlier today, I sent a bug fix for instruments with too-short release
envelopes.  In looking over some of the other envelope-related code I had
written in the past, I noticed that I had forgotten to take the
"control_ratio" variable (playback rate / samples per second) into
account.  At -s 44100 and the default 1000 controls per second,
control_ratio = 44.  Thus, all of my previous comments of 0.5 msec were
incorrect, and timidity was actually using an effective amp ramp window of
22 msec.  Worse yet, the window length (in time) would change with
different playback sampling rates.  While it was difficult to measure in
previous examples of pan-related and rapid volume-related popping, the new
release-related popping was easy to visualize and measure in a WAV editor.
What I thought was 0.5 msec in the code before was indeed 22 msec in
reality :(

I also noticed some possible problems with the envelope-related patch I
sent earlier today and fixed them.

I have attached a diff that replaces the diff I sent earlier today, and
fixes the other anti-popping measure I wrote many years ago as well.
Rather than use 22 msec, I shortened it to a nice round 20 msec.  Audibly,
the popping test midi I have sound the same as the prior incorrect
implementation.  Reducing the window to 15 msec causes definate pops, so I
think 20 msec is as short as it can reasonably go.

-Eric

Re: [timidity-talk] Clicking Noise On Some SoundFonts (bug fix: patch attached)

[Eric W. <ew...@bi...>]

On Sat, 29 Aug 2009, A. Zimmer wrote:

> From: Eric Welsh <ewelsh@bi...> - 2009-08-28 03:56
>
> > Adding a decent release envelope solved the problem. This is not a
> > problem with timidity, but a problem with the instrument not having any
> > kind of sane envelope.
>
> Using the swami soundfont editor (http://swami.resonance.org/trac) I can
> also modify the volume envelope release value and eliminate the clicking
> noise.

I have attached a reasonably proper (I think) fix for the problem.  Rather
than deal with it during instrument loading, or checking to be sure that
envelope values get set to reasonable parameters in the first place, I
went to the lowest level of the problem and fixed it directly in the
mixing routines.  Now, any envelope ramp (from starting volume to final
ending volume) MUST take place over a minimum of 0.5 msec.  This should
gaurantee that the problem is solved even for unforseen combinations of
envelope settings in the future.  The problematic recorder sounds much
much better now :)

> However, using swami to take a quick survey of the many SF2 soundfonts
> that I have gathered from the Web, I discover that perhaps the majority
> of them have a near zero release value set.  All these fonts should
> therefore cause problems with Timididty++, but as I have indicated
> previously, they will not cause problems with the fluidsynth software
> synthesizer.  So, is the assessment that these soundfonts lack a
> "sane envelope" really a correct one?

TiMidity was originally written to use GUS pats.  There are several
kludges and lots of comments with ?? that deal with specific weirdness in
GUS pats.  I have been using TiMidity since around 1996, since before SF2
files, and have edited many many instrument files from all sorts of
different sources.  My memory is a little fuzzy on pre-PAT formats, such
as instruments from Kurzweil, Roland, and Yamaha synthesizer disks, but I
seem to remember all of them having reasonable release envelopes.  So, up
until SF2 files, most digital instruments had reasonable envelope
parameters.  Then there was a flood of SF2 instruments, many of which had
either no envelopes at all, or really strange envelopes.  From my
(relatively ancient) perspective, these SF2 files have broken envelopes.

While I still maintain that the SF2 files are broken, as several people
have pointed out, TiMidity should still be able to deal with it and at
least avoid generating popping sounds.  I totally agree ... there was just
a large energy barrier to digging back into the TiMidity source code after
several years of inactivity....

The patch was generated off a not-current version of mix.c.  If the patch
offsets are too far off, or the file has changed too much from the current
version (which I think is unlikely), the patch is within the next_stage(int v)
function, and it should be fairly obvious where to insert the new code
given the surrounding code chunks in the patch.



If I could ever get the softsynth to compile and run properly in Windows,
I'd fix some XG SYSEX event handling problems too....  The normal midi
file playing routines already have fixes for the issue, but they never
made it into the realtime synth routines.  Does anybody have any
experience getting the realtime softsynth to compile and run under
Windows?

-Eric

Re: [timidity-talk] Clicking Noise On Some SoundFonts

[A. Z. <and...@co...>]

From: Eric Welsh <ewelsh@bi...> - 2009-08-28 03:56

> Adding a decent release envelope solved the problem. This is not a
> problem with timidity, but a problem with the instrument not having any
> kind of sane envelope. 

Using the swami soundfont editor (http://swami.resonance.org/trac) I can
also modify the volume envelope release value and eliminate the clicking
noise.

However, using swami to take a quick survey of the many SF2 soundfonts
that I have gathered from the Web, I discover that perhaps the majority
of them have a near zero release value set.  All these fonts should
therefore cause problems with Timididty++, but as I have indicated
previously, they will not cause problems with the fluidsynth software
synthesizer.  So, is the assessment that these soundfonts lack a
"sane envelope" really a correct one?

Re: [timidity-talk] Clicking Noise On Some SoundFonts

[A. Z. <and...@co...>]

On Thu, Aug 27, 2009 at 10:56 PM, Eric Welsh<ewelsh@bi...> wrote:

> Adding a decent release envelope solved the problem.  This is not a
> problem with timidity, but a problem with the instrument not having any
> kind of sane envelope.

I, too, have eliminated the popping sound by altering the timidity.cfg
file to include an envelope release parameter for the soundfont.

But if Timidity++ is not at fault, then how is fluidsynth able to
render without the popping noise using the same soundfont?

http://fluidsynth.resonance.org/trac

Using fluidsynth and the same midi and soundfont does not produce
the popping noise while using Timidity++ does produce the noise.

It seems Timiditiy++ has been written primarily to handle PAT fonts.
A later addition allowed the use of SF2 fonts but there apparently
is some difficulty.

Re: [timidity-talk] Clicking Noise On Some SoundFonts

[A. Z. <and...@co...>]

Hello,

The original message about the clicking noise with some SF2 soundfonts
was posted about 8-12 months ago.  Since that time, with no replies,
the links have died.

Here are the files re-posted to a new location.

MP3 example of clicking noise with a Timidity++ rendered midi file.
(Note: This is a microtonal composition, so if the tuning sounds a bit
off it is deliberate.):

http://home.comcast.net/~frank.peters/beatgen.mp3 (MP3 file is about 3.4 Mb)

The midi file:

http://home.comcast.net/~frank.peters/beatgen.mid

The SF2 soundfont used:

http://home.comcast.net/~frank.peters/WT_Clarinet.sf2 (SF2 file is about 330 kB)

Re: [timidity-talk] Clicking Noise On Some SoundFonts

[Bob v. d. P. <bo...@me...>]

> Yeah, I guess you're right.  Behavior I would want as a "power user"
> probably isn't the best thing for the average user....  I'll take a look
> over the code and see where I could most easily insert some sort of
> release envelope check.  It would default to the minimal time required to
>

Just a thought ... instead of changing anything in what Timidity does, would
a warning message be more appropriate? Something like the existing messages
about no-such-font, etc. along with a short suggestion on how to fix?

Also, I'm a bit dismayed that no development is being done anymore with this
fine package. I find that it is very handy to use timidity for bulk
midi-to-wav conversions. I don't know of any other command line programs
which do this at all ... maybe if there are some I'd not be quite as
dismayed?

-- 
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bo...@me...
WWW:   http://www.mellowood.ca

Re: [timidity-talk] Clicking Noise On Some SoundFonts

[Eric W. <ew...@bi...>]

On Fri, 28 Aug 2009, Aaron Johnson wrote:

> Good software design in my philosophy is allowing the flexibility and
> generality when needed, but, yes, saving the user from themselves!
> Given that the clicks were not heard on say FluidSynth, I'd say they
> have something like this in place.
> And I think something like this would be very good for Timidity.

> A lot of people may have already written Timidity off as not being
> capable of professional, clean-quality work, b/c it has clicking noise
> where other MIDI soundfont software doesn't. They may have said, as I
> did, "development isn't active, it's old software, I don't think this
> will get fixed", and move on, to get their music done without the
> hassle of figuring it out.....I perceive NOT dealing with it clikcing
> as a bug, not a feature. My 2¢!!!

Yeah, I guess you're right.  Behavior I would want as a "power user"
probably isn't the best thing for the average user....  I'll take a look
over the code and see where I could most easily insert some sort of
release envelope check.  It would default to the minimal time required to
avoid a pop.  It still wouldn't sound all that good, because no (or
super short) release just generally sounds bad, but at least it wouldn't
pop any more.  I'm still a little leery of defaulting to a noticably long
release (which is what most good instruments have), since perhaps the
short release was actually intentional, but perhaps such a longer default
could be added as a --option (we're running out of -? letters).

I'm going to see if I can find a good place to put the check so that it
can be made after all the various different routines that instruments are
read in from.  I don't want to hack separate fixes for the SF2 reader, the
PAT reader, the -P reader, and maybe separate softsynth versions of all of
these.  The softsynth will be the worst, since I am totally unfamiliar
with how instruments get loaded on the fly for that, and I have no way to
easily test it under my home Windows setup.  I hope that I can find an
easy place just upstream of the mixing routines where the envelopes get
translated into internal values.  A check for no release should be easy to
do there, and the minimal pop avoidance value set there for all cases.
Any --option for longer defaults, though, might be a lot more difficult to
add, since that place in the routine has probably lost track of whether
the envelope was missing in the original instrument, or if these values
were what was actually set by the instrument or other overriding
parameters in the .cfg files.

Short answer: I hope to be able to fix the pops for all instrument
sources by adding a minimal super short release time, but changing the
default to be a longer "nice sounding" one may not be so easy and will be
left as a future wish for now.

-Eric

Re: [timidity-talk] Clicking Noise On Some SoundFonts

[Aaron J. <aa...@ak...>]

Hi Eric,

Good software design in my philosophy is allowing the flexibility and
generality when needed, but, yes, saving the user from themselves!
Given that the clicks were not heard on say FluidSynth, I'd say they
have something like this in place.
And I think something like this would be very good for Timidity.

However I understand your concern for purity and literally 'doing what
the user asks'...so 3 thoughts come to mind:

1) You could have a auto-declicking provision coded in by default, and
have a command line option to disable.
2) You could have a command-line option to *enable* auto-declicking,
where it's off by default
3) You could document the issue. The user searching for solutions now
is in the dark, and is likely to give up on Timidty. Right now, it's
not mentioned but in passing, and adding 'strip=tail' doesn't work.
Google didn't really bring it up except this recent thread, and the
manpage mentioning the 'strip=tail' option. So, if it weren't for
tinkering, I would write off Timidity too.

A lot of people may have already written Timidity off as not being
capable of professional, clean-quality work, b/c it has clicking noise
where other MIDI soundfont software doesn't. They may have said, as I
did, "development isn't active, it's old software, I don't think this
will get fixed", and move on, to get their music done without the
hassle of figuring it out.....I perceive NOT dealing with it clikcing
as a bug, not a feature. My 2¢!!!

All best,
Aaron.


Aaron Krister Johnson
http://www.akjmusic.com
http://www.untwelve.org

On Fri, Aug 28, 2009 at 12:16 AM, Eric Welsh<ew...@bi...> wrote:

>
> This may bring up the wider question of what is the "correct" behavior of
> timidity in the case where "stupid" envelope parameters are specified.
> Should it continue operating as it currently does, and just accept them
> as-is, or should it set some minimum release rate that is still very very
> short, but would be long enough to prevent clicks?
>
> Sorry, I'm going to go into a historical rant now to overly explain
> the issue....  It is my emperical experience that amplitude changes need
> to be ramped over a minimum of 0.5 milleseconds from starting amplitude to
> new ending amplitude.  Any faster than that and clicks happen.  All notes
> playing in timidity have a current internal amplification, a target
> amplification, and an increment value that tells it how rapidly to
> increase/decrease the amplification.  Envelopes are implemented by
> adjusting these internal values on the fly as the different portions of
> the envelope are reached in the sample.  Volume pans and Expression levels
> are handled in the same routine, it's all done during the mixing stage.
> Originally, timidity had clicking problems during rapid Expression level
> changes, or during very rapid (instant) far right/left pans during the
> middle of a note.  I added a check to adjust the minimum time spent
> ramping between initial and target amplitudes to 0.5 msec and the popping
> went away.  Any shorter and the volume pops, any longer and the ramp delay
> starts to become audible and sound slightly "sluggish".  I deemed this to
> be a reasonable compromise between "do what I told you" and "do what I
> meant" since the brain will not notice the 0.5 msec delay in the volume
> adjustment.
>
> So, why is this code not kicking in when there is no release rate set?
> I'm going to guess that timidity pre-calculates that the end of the sample
> play time has been reached, and thus ends the note without any additional
> mixing (since there is no sample left to mix since it ended the resampling
> upstream of the mixing already).  This is just a guess, and I'm too lazy
> to go dig into the code to look right now.  Whatever the reason, I don't
> think that any additional fixes could be easily made at the mixing level
> to check for non-existant release rates.  I think the changes would have
> to be implemented during SF2/PAT loading itself, to check for "bad"
> envelopes and adjust them to something "not so bad".
>
> If I remember correctly, and my memory is a little hazy on this at the
> moment, I think that the standard GUS pat loader will use a default
> pre-set envelope if no envelope at all is found in the instrument.  This
> is bypassed when the -P option is used, and the envelope is used as-is
> directly from the pat (this part I am *sure* of).  This would explain why
> the recorder click problem was very bad when I used -P, but was reasonably
> mild when I edited my gravis.cfg file to load the pat instead.
>
> If this is being done for the standard GUS loader (I have no idea how the
> realtime softsynth handles it), should it be done for SF2 as well?  What
> is, philosophically, the best thing to do here?  Should timidity trust the
> user and do exactly what the user said to do, because the user knows best?
> Or should it set a minimum release rate to protect the user from himself?
> Protecting the user from himself is a dangerous path to take, since it is
> easy to go too far and deny the user from accomplishing his intentions.
> If I tell it 0 release, and timidity auto-fudges this to 0.5 msec release,
> would this auto-fudging behavior be "bad" because it isn't doing what I
> explicitly told it to do?  I'm hesitant to auto-correct "bad" envelope
> settings.
>
> Also, from a purely personal viewpoint, I think the popping noises are
> "good", since they alert the user that there is something amiss with the
> instrument and that its envelopes should be edited to sound better.
> Better to have the user blatantly notice the problem and fix it properly
> than to mask over the problem and result in a not-as-great sounding, but
> not jarringly bad sound.
>
> -Eric
>



--

Re: [timidity-talk] Clicking Noise On Some SoundFonts

[Eric W. <ew...@bi...>]

On Thu, 27 Aug 2009, Aaron Johnson wrote:

> I realized that adding a release envelope on the order of 180-200 or
> sometimes more did the trick (it was at first confusing, b/c quicker
> envelopes get *higher* numbers (like 255 being fastest), not lower...I
> wonder if they are denominators of a fraction in some kind of
> non-linear time equation??)

> I added the 'strip=tail' option b/c it mentions clicking in the
> manpage, but it doesn't seem to be the critical piece...the critical
> piece is the 'rate=:::180' option.

The strip=tail is an ancient option meant for some ancient GUS pats that
could sometimes contain garbage at the end of the sample.  There are
probably not any instruments still in use today that would benefit from
this.  I have not seen any instruments like this in a long long time.

> Thanks for looking into this...everything works really well now!

> >> >> >> > If I render this file with fluidsynth the clicking noise does not
> >> >> >> > occur.  Also, if I tweak the attack or decay rates in the Timidity
> >> >> >> > configuration file, I can mitigate the clicking noise somewhat but
> >> >> >> > cannot eliminate it entirely.
> >> >> >> >
> >> >> >> > Could this be a problem with the soundfont or is Timidity just not
> >> >> >> > able to process SF2 fonts completely?

I'd be curious to know if WildMidi exhibits this issue too.  If there is
one thing I am sure of, it is that Chris Ison knows his GUS instrument
envelopes!

This may bring up the wider question of what is the "correct" behavior of
timidity in the case where "stupid" envelope parameters are specified.
Should it continue operating as it currently does, and just accept them
as-is, or should it set some minimum release rate that is still very very
short, but would be long enough to prevent clicks?

Sorry, I'm going to go into a historical rant now to overly explain
the issue....  It is my emperical experience that amplitude changes need
to be ramped over a minimum of 0.5 milleseconds from starting amplitude to
new ending amplitude.  Any faster than that and clicks happen.  All notes
playing in timidity have a current internal amplification, a target
amplification, and an increment value that tells it how rapidly to
increase/decrease the amplification.  Envelopes are implemented by
adjusting these internal values on the fly as the different portions of
the envelope are reached in the sample.  Volume pans and Expression levels
are handled in the same routine, it's all done during the mixing stage.
Originally, timidity had clicking problems during rapid Expression level
changes, or during very rapid (instant) far right/left pans during the
middle of a note.  I added a check to adjust the minimum time spent
ramping between initial and target amplitudes to 0.5 msec and the popping
went away.  Any shorter and the volume pops, any longer and the ramp delay
starts to become audible and sound slightly "sluggish".  I deemed this to
be a reasonable compromise between "do what I told you" and "do what I
meant" since the brain will not notice the 0.5 msec delay in the volume
adjustment.

So, why is this code not kicking in when there is no release rate set?
I'm going to guess that timidity pre-calculates that the end of the sample
play time has been reached, and thus ends the note without any additional
mixing (since there is no sample left to mix since it ended the resampling
upstream of the mixing already).  This is just a guess, and I'm too lazy
to go dig into the code to look right now.  Whatever the reason, I don't
think that any additional fixes could be easily made at the mixing level
to check for non-existant release rates.  I think the changes would have
to be implemented during SF2/PAT loading itself, to check for "bad"
envelopes and adjust them to something "not so bad".

If I remember correctly, and my memory is a little hazy on this at the
moment, I think that the standard GUS pat loader will use a default
pre-set envelope if no envelope at all is found in the instrument.  This
is bypassed when the -P option is used, and the envelope is used as-is
directly from the pat (this part I am *sure* of).  This would explain why
the recorder click problem was very bad when I used -P, but was reasonably
mild when I edited my gravis.cfg file to load the pat instead.

If this is being done for the standard GUS loader (I have no idea how the
realtime softsynth handles it), should it be done for SF2 as well?  What
is, philosophically, the best thing to do here?  Should timidity trust the
user and do exactly what the user said to do, because the user knows best?
Or should it set a minimum release rate to protect the user from himself?
Protecting the user from himself is a dangerous path to take, since it is
easy to go too far and deny the user from accomplishing his intentions.
If I tell it 0 release, and timidity auto-fudges this to 0.5 msec release,
would this auto-fudging behavior be "bad" because it isn't doing what I
explicitly told it to do?  I'm hesitant to auto-correct "bad" envelope
settings.

Also, from a purely personal viewpoint, I think the popping noises are
"good", since they alert the user that there is something amiss with the
instrument and that its envelopes should be edited to sound better.
Better to have the user blatantly notice the problem and fix it properly
than to mask over the problem and result in a not-as-great sounding, but
not jarringly bad sound.

-Eric

Re: [timidity-talk] Clicking Noise On Some SoundFonts

[Aaron J. <aa...@ak...>]

Hi Eric,

I was just about to write you to say that I came up with the same solution!!!

I realized that adding a release envelope on the order of 180-200 or
sometimes more did the trick (it was at first confusing, b/c quicker
envelopes get *higher* numbers (like 255 being fastest), not lower...I
wonder if they are denominators of a fraction in some kind of
non-linear time equation??)

Anyway, the syntax is described on the manpage. Here's an example:

bank 0
0 %font MyFontName.sf2 0 0 rate=:::180 strip=tail

I added the 'strip=tail' option b/c it mentions clicking in the
manpage, but it doesn't seem to be the critical piece...the critical
piece is the 'rate=:::180' option.
Since we are just setting release time, the attack, decay & sustain
portions are left default, and are hence empty with their following
colons.

Thanks for looking into this...everything works really well now!

Best,
AKJ

On Thu, Aug 27, 2009 at 10:56 PM, Eric Welsh<ew...@bi...> wrote:
> First thing I tried was to load the sf2 bank up in Awave and resave it as
> a PAT.  I could then use the -P flag to force all instruments to be played
> using the specified .pat instrument file.  My standard recorder (the one
> in FreePats) sounds fine.  The pc51d derived recorder pat file clearly
> exhibits the "clicking" noises you described.  This rules out any sf2
> specific envelope problems, since the problem is in the Gravis PAT format
> as well.
>
> Looking at the recorder envelope, it appears that it has no release
> rate at all.  So, when the note ends, the note simply ends abruptly
> without any decaying volume ramp.  This is very likely what is causing the
> clicking sound.  Any extremely rapid change in volume level, such as going
> from a playing note to instantly zero amplitude, will cause an audible
> click in your speakers.
>
> Adding a decent release envelope solved the problem.  This is not a
> problem with timidity, but a problem with the instrument not having any
> kind of sane envelope.  Timidity is behaving as it should and
> ending the note immediately upon a NOTEOFF event, since there is no
> release decay envelope.  Speaking from my experience of looking at many
> many sf2 banks over the years, this is not unusual....  You can fix the
> problem by either resaving the sf2 bank after editing the envelope in an
> instrument editor, or add flags within the timidity .cfg files you are
> using to control that specific instrument's envelope.  Unfortunately, I do
> not remember the syntax for how to do this in the .cfg files :(
>
> Maybe someone else can chime in with how to alter SF2 (or even PAT)
> envelopes from within timidity .cfg files.
>
> -Eric
>
> On Thu, 27 Aug 2009, Aaron Krister Johnson wrote:
>
>>
>>
>> Hi Eric,
>>
>> Attached is a MIDI file of some Medieval music by Machaut that has audible
>> clicks when used with the Personal Copy GM soundfont (using the recorder
>> patch, program 75 in 1-based counting, or 74 in 0-based counting scheme)...
>>
>> I trust you can track down, or already may have the Personal Copy GM
>> soundfont, but in case you can't here's a link to it that I've uploaded to
>> my site:
>>
>> http://www.akjmusic.com/PC51d.sf2 (58mb download!!)
>>
>> Hope this can help Timidity developers track down the click problem! :)
>>
>> Best,
>> AKJ
>>
>> http://www.akjmusic.com
>> http://www.untwelve.org
>> http://www.nabble.com/file/p25177354/machaut-b15-gm.mid machaut-b15-gm.mid
>>
>> Eric Welsh wrote:
>> >
>> > On Thu, 27 Aug 2009, Aaron Krister Johnson wrote:
>> >
>> >> I couldn't find the files either...it looks like a file-sharing site
>> >> whose
>> >> links have expired...anyway, are you a developer for Timidity? It would
>> >> be
>> >> great to get to the bottom of this issue!
>> >>
>> >> Best,
>> >> AKJ
>> >
>> > I'm haven't been active in development recently, but I've done some work
>> > with envelopes and associated click problems in the past.  I'm a little
>> > limited in my SF2 knowledge, but I could probably dig a bit into the code
>> > to see if it is an SF2 specific envelope problem, or if it is an envelope
>> > problem at all.  If you have problematic files of your own, send them my
>> > way and I can start taking a look them.
>> >
>> > -Eric
>> >
>> >> http://www.untwelve.org
>> >> http://www.akjmusic.com
>> >>
>> >>
>> >> Eric Welsh wrote:
>> >> >
>> >> > I tried the links below to the problematic files, but they don't appear
>> >> to
>> >> > work anymore.  Could the original author repost them somewhere else?
>> >> >
>> >> > -Eric
>> >> >
>> >> > On Wed, 26 Aug 2009, Aaron Krister Johnson wrote:
>> >> >
>> >> >> Hi,
>> >> >>
>> >> >> I can confirm that this happens to me too, and can also confirm that
>> >> it
>> >> >> is
>> >> >> indeed annoying!
>> >> >>
>> >> >> I've noticed it for all versions of Timidity as far back as I can
>> >> >> remember
>> >> >> using it, say from 2003....
>> >> >>
>> >> >> Best,
>> >> >> AKJ
>> >> >>
>> >> >>
>> >> >> A. Kalten wrote:
>> >> >> >
>> >> >> > Hello list,
>> >> >> >
>> >> >> > Timidity usually gives good results, but on some soundfonts it will
>> >> >> > produce an annoying clicking sound.  As an example, I have uploaded
>> >> >> > an MP3 of a wave file created with Timidity that contains the
>> >> clicking
>> >> >> > noise.  Also uploaded are the MIDI file and the soundfont used
>> >> (there
>> >> >> > is only a single instrument involved).
>> >> >> >
>> >> >> > http://firstbooks.biz/midi/beatgen.mp3   (MP3 file is about 3.4 Mb)
>> >> >> >
>> >> >> > http://firstbooks.biz/midi/beatgen.mid
>> >> >> >
>> >> >> > http://firstbooks.biz/midi/WT_Clarinet.sf2  (SF2 file is about 330
>> >> kB)
>> >> >> >
>> >> >> > Note: This is a microtonal composition, so if the tuning sounds a
>> >> bit
>> >> >> > off it is deliberate.
>> >> >> >
>> >> >> > If I render this file with fluidsynth the clicking noise does not
>> >> >> > occur.  Also, if I tweak the attack or decay rates in the Timidity
>> >> >> > configuration file, I can mitigate the clicking noise somewhat but
>> >> >> > cannot eliminate it entirely.
>> >> >> >
>> >> >> > Could this be a problem with the soundfont or is Timidity just not
>> >> >> > able to process SF2 fonts completely?
>> >> >> >
>> >> >> > Regards,
>> >> >> >
>> >> >> > AK
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >>
>> >> -------------------------------------------------------------------------
>> >> >> > This SF.Net email is sponsored by the Moblin Your Move Developer's
>> >> >> > challenge
>> >> >> > Build the coolest Linux based applications with Moblin SDK & win
>> >> great
>> >> >> > prizes
>> >> >> > Grand prize is a trip for two to an Open Source event anywhere in
>> >> the
>> >> >> > world
>> >> >> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> >> >> > _______________________________________________
>> >> >> > Timidity-talk mailing list
>> >> >> > Tim...@li...
>> >> >> > https://lists.sourceforge.net/lists/listinfo/timidity-talk
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >> http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25164608.html
>> >> >> Sent from the TiMidity++ - General mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >>
>> >> ------------------------------------------------------------------------------
>> >> >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> >> >> 30-Day
>> >> >> trial. Simplify your report design, integration and deployment - and
>> >> >> focus on
>> >> >> what you do best, core application coding. Discover what's new with
>> >> >> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> >> >> _______________________________________________
>> >> >> Timidity-talk mailing list
>> >> >> Tim...@li...
>> >> >> https://lists.sourceforge.net/lists/listinfo/timidity-talk
>> >> >>
>> >> >
>> >> >
>> >> ------------------------------------------------------------------------------
>> >> > Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> >> > 30-Day
>> >> > trial. Simplify your report design, integration and deployment - and
>> >> focus
>> >> > on
>> >> > what you do best, core application coding. Discover what's new with
>> >> > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> >> > _______________________________________________
>> >> > Timidity-talk mailing list
>> >> > Tim...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/timidity-talk
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >> http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25171137.html
>> >> Sent from the TiMidity++ - General mailing list archive at Nabble.com.
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> >> 30-Day
>> >> trial. Simplify your report design, integration and deployment - and
>> >> focus on
>> >> what you do best, core application coding. Discover what's new with
>> >> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> >> _______________________________________________
>> >> Timidity-talk mailing list
>> >> Tim...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/timidity-talk
>> >>
>> >
>> > ------------------------------------------------------------------------------
>> > Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> > 30-Day
>> > trial. Simplify your report design, integration and deployment - and focus
>> > on
>> > what you do best, core application coding. Discover what's new with
>> > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> > _______________________________________________
>> > Timidity-talk mailing list
>> > Tim...@li...
>> > https://lists.sourceforge.net/lists/listinfo/timidity-talk
>> >
>> >
>>
>> --
>> View this message in context: http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25177354.html
>> Sent from the TiMidity++ - General mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>> trial. Simplify your report design, integration and deployment - and focus on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Timidity-talk mailing list
>> Tim...@li...
>> https://lists.sourceforge.net/lists/listinfo/timidity-talk
>>
>



-- 

Aaron Krister Johnson
http://www.akjmusic.com
http://www.untwelve.org

Re: [timidity-talk] Clicking Noise On Some SoundFonts

[Eric W. <ew...@bi...>]

First thing I tried was to load the sf2 bank up in Awave and resave it as
a PAT.  I could then use the -P flag to force all instruments to be played
using the specified .pat instrument file.  My standard recorder (the one
in FreePats) sounds fine.  The pc51d derived recorder pat file clearly
exhibits the "clicking" noises you described.  This rules out any sf2
specific envelope problems, since the problem is in the Gravis PAT format
as well.

Looking at the recorder envelope, it appears that it has no release
rate at all.  So, when the note ends, the note simply ends abruptly
without any decaying volume ramp.  This is very likely what is causing the
clicking sound.  Any extremely rapid change in volume level, such as going
from a playing note to instantly zero amplitude, will cause an audible
click in your speakers.

Adding a decent release envelope solved the problem.  This is not a
problem with timidity, but a problem with the instrument not having any
kind of sane envelope.  Timidity is behaving as it should and
ending the note immediately upon a NOTEOFF event, since there is no
release decay envelope.  Speaking from my experience of looking at many
many sf2 banks over the years, this is not unusual....  You can fix the
problem by either resaving the sf2 bank after editing the envelope in an
instrument editor, or add flags within the timidity .cfg files you are
using to control that specific instrument's envelope.  Unfortunately, I do
not remember the syntax for how to do this in the .cfg files :(

Maybe someone else can chime in with how to alter SF2 (or even PAT)
envelopes from within timidity .cfg files.

-Eric

On Thu, 27 Aug 2009, Aaron Krister Johnson wrote:

>
>
> Hi Eric,
>
> Attached is a MIDI file of some Medieval music by Machaut that has audible
> clicks when used with the Personal Copy GM soundfont (using the recorder
> patch, program 75 in 1-based counting, or 74 in 0-based counting scheme)...
>
> I trust you can track down, or already may have the Personal Copy GM
> soundfont, but in case you can't here's a link to it that I've uploaded to
> my site:
>
> http://www.akjmusic.com/PC51d.sf2 (58mb download!!)
>
> Hope this can help Timidity developers track down the click problem! :)
>
> Best,
> AKJ
>
> http://www.akjmusic.com
> http://www.untwelve.org
> http://www.nabble.com/file/p25177354/machaut-b15-gm.mid machaut-b15-gm.mid
>
> Eric Welsh wrote:
> >
> > On Thu, 27 Aug 2009, Aaron Krister Johnson wrote:
> >
> >> I couldn't find the files either...it looks like a file-sharing site
> >> whose
> >> links have expired...anyway, are you a developer for Timidity? It would
> >> be
> >> great to get to the bottom of this issue!
> >>
> >> Best,
> >> AKJ
> >
> > I'm haven't been active in development recently, but I've done some work
> > with envelopes and associated click problems in the past.  I'm a little
> > limited in my SF2 knowledge, but I could probably dig a bit into the code
> > to see if it is an SF2 specific envelope problem, or if it is an envelope
> > problem at all.  If you have problematic files of your own, send them my
> > way and I can start taking a look them.
> >
> > -Eric
> >
> >> http://www.untwelve.org
> >> http://www.akjmusic.com
> >>
> >>
> >> Eric Welsh wrote:
> >> >
> >> > I tried the links below to the problematic files, but they don't appear
> >> to
> >> > work anymore.  Could the original author repost them somewhere else?
> >> >
> >> > -Eric
> >> >
> >> > On Wed, 26 Aug 2009, Aaron Krister Johnson wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> I can confirm that this happens to me too, and can also confirm that
> >> it
> >> >> is
> >> >> indeed annoying!
> >> >>
> >> >> I've noticed it for all versions of Timidity as far back as I can
> >> >> remember
> >> >> using it, say from 2003....
> >> >>
> >> >> Best,
> >> >> AKJ
> >> >>
> >> >>
> >> >> A. Kalten wrote:
> >> >> >
> >> >> > Hello list,
> >> >> >
> >> >> > Timidity usually gives good results, but on some soundfonts it will
> >> >> > produce an annoying clicking sound.  As an example, I have uploaded
> >> >> > an MP3 of a wave file created with Timidity that contains the
> >> clicking
> >> >> > noise.  Also uploaded are the MIDI file and the soundfont used
> >> (there
> >> >> > is only a single instrument involved).
> >> >> >
> >> >> > http://firstbooks.biz/midi/beatgen.mp3   (MP3 file is about 3.4 Mb)
> >> >> >
> >> >> > http://firstbooks.biz/midi/beatgen.mid
> >> >> >
> >> >> > http://firstbooks.biz/midi/WT_Clarinet.sf2  (SF2 file is about 330
> >> kB)
> >> >> >
> >> >> > Note: This is a microtonal composition, so if the tuning sounds a
> >> bit
> >> >> > off it is deliberate.
> >> >> >
> >> >> > If I render this file with fluidsynth the clicking noise does not
> >> >> > occur.  Also, if I tweak the attack or decay rates in the Timidity
> >> >> > configuration file, I can mitigate the clicking noise somewhat but
> >> >> > cannot eliminate it entirely.
> >> >> >
> >> >> > Could this be a problem with the soundfont or is Timidity just not
> >> >> > able to process SF2 fonts completely?
> >> >> >
> >> >> > Regards,
> >> >> >
> >> >> > AK
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> -------------------------------------------------------------------------
> >> >> > This SF.Net email is sponsored by the Moblin Your Move Developer's
> >> >> > challenge
> >> >> > Build the coolest Linux based applications with Moblin SDK & win
> >> great
> >> >> > prizes
> >> >> > Grand prize is a trip for two to an Open Source event anywhere in
> >> the
> >> >> > world
> >> >> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> >> >> > _______________________________________________
> >> >> > Timidity-talk mailing list
> >> >> > Tim...@li...
> >> >> > https://lists.sourceforge.net/lists/listinfo/timidity-talk
> >> >> >
> >> >> >
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >> http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25164608.html
> >> >> Sent from the TiMidity++ - General mailing list archive at Nabble.com.
> >> >>
> >> >>
> >> >>
> >> ------------------------------------------------------------------------------
> >> >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> >> >> 30-Day
> >> >> trial. Simplify your report design, integration and deployment - and
> >> >> focus on
> >> >> what you do best, core application coding. Discover what's new with
> >> >> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> >> >> _______________________________________________
> >> >> Timidity-talk mailing list
> >> >> Tim...@li...
> >> >> https://lists.sourceforge.net/lists/listinfo/timidity-talk
> >> >>
> >> >
> >> >
> >> ------------------------------------------------------------------------------
> >> > Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> >> > 30-Day
> >> > trial. Simplify your report design, integration and deployment - and
> >> focus
> >> > on
> >> > what you do best, core application coding. Discover what's new with
> >> > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> >> > _______________________________________________
> >> > Timidity-talk mailing list
> >> > Tim...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/timidity-talk
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25171137.html
> >> Sent from the TiMidity++ - General mailing list archive at Nabble.com.
> >>
> >>
> >> ------------------------------------------------------------------------------
> >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> >> 30-Day
> >> trial. Simplify your report design, integration and deployment - and
> >> focus on
> >> what you do best, core application coding. Discover what's new with
> >> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> >> _______________________________________________
> >> Timidity-talk mailing list
> >> Tim...@li...
> >> https://lists.sourceforge.net/lists/listinfo/timidity-talk
> >>
> >
> > ------------------------------------------------------------------------------
> > Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> > 30-Day
> > trial. Simplify your report design, integration and deployment - and focus
> > on
> > what you do best, core application coding. Discover what's new with
> > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> > _______________________________________________
> > Timidity-talk mailing list
> > Tim...@li...
> > https://lists.sourceforge.net/lists/listinfo/timidity-talk
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25177354.html
> Sent from the TiMidity++ - General mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Timidity-talk mailing list
> Tim...@li...
> https://lists.sourceforge.net/lists/listinfo/timidity-talk
>

Re: [timidity-talk] Clicking Noise On Some SoundFonts

[Aaron K. J. <aa...@ak...>]

Hi Eric,

Attached is a MIDI file of some Medieval music by Machaut that has audible
clicks when used with the Personal Copy GM soundfont (using the recorder
patch, program 75 in 1-based counting, or 74 in 0-based counting scheme)...

I trust you can track down, or already may have the Personal Copy GM
soundfont, but in case you can't here's a link to it that I've uploaded to
my site:

http://www.akjmusic.com/PC51d.sf2 (58mb download!!)

Hope this can help Timidity developers track down the click problem! :)

Best,
AKJ

http://www.akjmusic.com
http://www.untwelve.org
http://www.nabble.com/file/p25177354/machaut-b15-gm.mid machaut-b15-gm.mid 

Eric Welsh wrote:
> 
> On Thu, 27 Aug 2009, Aaron Krister Johnson wrote:
> 
>> I couldn't find the files either...it looks like a file-sharing site
>> whose
>> links have expired...anyway, are you a developer for Timidity? It would
>> be
>> great to get to the bottom of this issue!
>>
>> Best,
>> AKJ
> 
> I'm haven't been active in development recently, but I've done some work
> with envelopes and associated click problems in the past.  I'm a little
> limited in my SF2 knowledge, but I could probably dig a bit into the code
> to see if it is an SF2 specific envelope problem, or if it is an envelope
> problem at all.  If you have problematic files of your own, send them my
> way and I can start taking a look them.
> 
> -Eric
> 
>> http://www.untwelve.org
>> http://www.akjmusic.com
>>
>>
>> Eric Welsh wrote:
>> >
>> > I tried the links below to the problematic files, but they don't appear
>> to
>> > work anymore.  Could the original author repost them somewhere else?
>> >
>> > -Eric
>> >
>> > On Wed, 26 Aug 2009, Aaron Krister Johnson wrote:
>> >
>> >> Hi,
>> >>
>> >> I can confirm that this happens to me too, and can also confirm that
>> it
>> >> is
>> >> indeed annoying!
>> >>
>> >> I've noticed it for all versions of Timidity as far back as I can
>> >> remember
>> >> using it, say from 2003....
>> >>
>> >> Best,
>> >> AKJ
>> >>
>> >>
>> >> A. Kalten wrote:
>> >> >
>> >> > Hello list,
>> >> >
>> >> > Timidity usually gives good results, but on some soundfonts it will
>> >> > produce an annoying clicking sound.  As an example, I have uploaded
>> >> > an MP3 of a wave file created with Timidity that contains the
>> clicking
>> >> > noise.  Also uploaded are the MIDI file and the soundfont used
>> (there
>> >> > is only a single instrument involved).
>> >> >
>> >> > http://firstbooks.biz/midi/beatgen.mp3   (MP3 file is about 3.4 Mb)
>> >> >
>> >> > http://firstbooks.biz/midi/beatgen.mid
>> >> >
>> >> > http://firstbooks.biz/midi/WT_Clarinet.sf2  (SF2 file is about 330
>> kB)
>> >> >
>> >> > Note: This is a microtonal composition, so if the tuning sounds a
>> bit
>> >> > off it is deliberate.
>> >> >
>> >> > If I render this file with fluidsynth the clicking noise does not
>> >> > occur.  Also, if I tweak the attack or decay rates in the Timidity
>> >> > configuration file, I can mitigate the clicking noise somewhat but
>> >> > cannot eliminate it entirely.
>> >> >
>> >> > Could this be a problem with the soundfont or is Timidity just not
>> >> > able to process SF2 fonts completely?
>> >> >
>> >> > Regards,
>> >> >
>> >> > AK
>> >> >
>> >> >
>> >> >
>> >>
>> -------------------------------------------------------------------------
>> >> > This SF.Net email is sponsored by the Moblin Your Move Developer's
>> >> > challenge
>> >> > Build the coolest Linux based applications with Moblin SDK & win
>> great
>> >> > prizes
>> >> > Grand prize is a trip for two to an Open Source event anywhere in
>> the
>> >> > world
>> >> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> >> > _______________________________________________
>> >> > Timidity-talk mailing list
>> >> > Tim...@li...
>> >> > https://lists.sourceforge.net/lists/listinfo/timidity-talk
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25164608.html
>> >> Sent from the TiMidity++ - General mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> ------------------------------------------------------------------------------
>> >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> >> 30-Day
>> >> trial. Simplify your report design, integration and deployment - and
>> >> focus on
>> >> what you do best, core application coding. Discover what's new with
>> >> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> >> _______________________________________________
>> >> Timidity-talk mailing list
>> >> Tim...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/timidity-talk
>> >>
>> >
>> >
>> ------------------------------------------------------------------------------
>> > Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> > 30-Day
>> > trial. Simplify your report design, integration and deployment - and
>> focus
>> > on
>> > what you do best, core application coding. Discover what's new with
>> > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> > _______________________________________________
>> > Timidity-talk mailing list
>> > Tim...@li...
>> > https://lists.sourceforge.net/lists/listinfo/timidity-talk
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25171137.html
>> Sent from the TiMidity++ - General mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> 30-Day
>> trial. Simplify your report design, integration and deployment - and
>> focus on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Timidity-talk mailing list
>> Tim...@li...
>> https://lists.sourceforge.net/lists/listinfo/timidity-talk
>>
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> 30-Day 
> trial. Simplify your report design, integration and deployment - and focus
> on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Timidity-talk mailing list
> Tim...@li...
> https://lists.sourceforge.net/lists/listinfo/timidity-talk
> 
> 

-- 
View this message in context: http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25177354.html
Sent from the TiMidity++ - General mailing list archive at Nabble.com.

Re: [timidity-talk] Clicking Noise On Some SoundFonts

[Eric W. <ew...@bi...>]

On Thu, 27 Aug 2009, Aaron Krister Johnson wrote:

> I couldn't find the files either...it looks like a file-sharing site whose
> links have expired...anyway, are you a developer for Timidity? It would be
> great to get to the bottom of this issue!
>
> Best,
> AKJ

I'm haven't been active in development recently, but I've done some work
with envelopes and associated click problems in the past.  I'm a little
limited in my SF2 knowledge, but I could probably dig a bit into the code
to see if it is an SF2 specific envelope problem, or if it is an envelope
problem at all.  If you have problematic files of your own, send them my
way and I can start taking a look them.

-Eric

> http://www.untwelve.org
> http://www.akjmusic.com
>
>
> Eric Welsh wrote:
> >
> > I tried the links below to the problematic files, but they don't appear to
> > work anymore.  Could the original author repost them somewhere else?
> >
> > -Eric
> >
> > On Wed, 26 Aug 2009, Aaron Krister Johnson wrote:
> >
> >> Hi,
> >>
> >> I can confirm that this happens to me too, and can also confirm that it
> >> is
> >> indeed annoying!
> >>
> >> I've noticed it for all versions of Timidity as far back as I can
> >> remember
> >> using it, say from 2003....
> >>
> >> Best,
> >> AKJ
> >>
> >>
> >> A. Kalten wrote:
> >> >
> >> > Hello list,
> >> >
> >> > Timidity usually gives good results, but on some soundfonts it will
> >> > produce an annoying clicking sound.  As an example, I have uploaded
> >> > an MP3 of a wave file created with Timidity that contains the clicking
> >> > noise.  Also uploaded are the MIDI file and the soundfont used (there
> >> > is only a single instrument involved).
> >> >
> >> > http://firstbooks.biz/midi/beatgen.mp3   (MP3 file is about 3.4 Mb)
> >> >
> >> > http://firstbooks.biz/midi/beatgen.mid
> >> >
> >> > http://firstbooks.biz/midi/WT_Clarinet.sf2  (SF2 file is about 330 kB)
> >> >
> >> > Note: This is a microtonal composition, so if the tuning sounds a bit
> >> > off it is deliberate.
> >> >
> >> > If I render this file with fluidsynth the clicking noise does not
> >> > occur.  Also, if I tweak the attack or decay rates in the Timidity
> >> > configuration file, I can mitigate the clicking noise somewhat but
> >> > cannot eliminate it entirely.
> >> >
> >> > Could this be a problem with the soundfont or is Timidity just not
> >> > able to process SF2 fonts completely?
> >> >
> >> > Regards,
> >> >
> >> > AK
> >> >
> >> >
> >> >
> >> -------------------------------------------------------------------------
> >> > This SF.Net email is sponsored by the Moblin Your Move Developer's
> >> > challenge
> >> > Build the coolest Linux based applications with Moblin SDK & win great
> >> > prizes
> >> > Grand prize is a trip for two to an Open Source event anywhere in the
> >> > world
> >> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> >> > _______________________________________________
> >> > Timidity-talk mailing list
> >> > Tim...@li...
> >> > https://lists.sourceforge.net/lists/listinfo/timidity-talk
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25164608.html
> >> Sent from the TiMidity++ - General mailing list archive at Nabble.com.
> >>
> >>
> >> ------------------------------------------------------------------------------
> >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> >> 30-Day
> >> trial. Simplify your report design, integration and deployment - and
> >> focus on
> >> what you do best, core application coding. Discover what's new with
> >> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> >> _______________________________________________
> >> Timidity-talk mailing list
> >> Tim...@li...
> >> https://lists.sourceforge.net/lists/listinfo/timidity-talk
> >>
> >
> > ------------------------------------------------------------------------------
> > Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> > 30-Day
> > trial. Simplify your report design, integration and deployment - and focus
> > on
> > what you do best, core application coding. Discover what's new with
> > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> > _______________________________________________
> > Timidity-talk mailing list
> > Tim...@li...
> > https://lists.sourceforge.net/lists/listinfo/timidity-talk
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25171137.html
> Sent from the TiMidity++ - General mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Timidity-talk mailing list
> Tim...@li...
> https://lists.sourceforge.net/lists/listinfo/timidity-talk
>

Re: [timidity-talk] Clicking Noise On Some SoundFonts

[Aaron K. J. <aa...@ak...>]

Eric,

I couldn't find the files either...it looks like a file-sharing site whose
links have expired...anyway, are you a developer for Timidity? It would be
great to get to the bottom of this issue!

Best,
AKJ

http://www.untwelve.org
http://www.akjmusic.com


Eric Welsh wrote:
> 
> I tried the links below to the problematic files, but they don't appear to
> work anymore.  Could the original author repost them somewhere else?
> 
> -Eric
> 
> On Wed, 26 Aug 2009, Aaron Krister Johnson wrote:
> 
>> Hi,
>>
>> I can confirm that this happens to me too, and can also confirm that it
>> is
>> indeed annoying!
>>
>> I've noticed it for all versions of Timidity as far back as I can
>> remember
>> using it, say from 2003....
>>
>> Best,
>> AKJ
>>
>>
>> A. Kalten wrote:
>> >
>> > Hello list,
>> >
>> > Timidity usually gives good results, but on some soundfonts it will
>> > produce an annoying clicking sound.  As an example, I have uploaded
>> > an MP3 of a wave file created with Timidity that contains the clicking
>> > noise.  Also uploaded are the MIDI file and the soundfont used (there
>> > is only a single instrument involved).
>> >
>> > http://firstbooks.biz/midi/beatgen.mp3   (MP3 file is about 3.4 Mb)
>> >
>> > http://firstbooks.biz/midi/beatgen.mid
>> >
>> > http://firstbooks.biz/midi/WT_Clarinet.sf2  (SF2 file is about 330 kB)
>> >
>> > Note: This is a microtonal composition, so if the tuning sounds a bit
>> > off it is deliberate.
>> >
>> > If I render this file with fluidsynth the clicking noise does not
>> > occur.  Also, if I tweak the attack or decay rates in the Timidity
>> > configuration file, I can mitigate the clicking noise somewhat but
>> > cannot eliminate it entirely.
>> >
>> > Could this be a problem with the soundfont or is Timidity just not
>> > able to process SF2 fonts completely?
>> >
>> > Regards,
>> >
>> > AK
>> >
>> >
>> >
>> -------------------------------------------------------------------------
>> > This SF.Net email is sponsored by the Moblin Your Move Developer's
>> > challenge
>> > Build the coolest Linux based applications with Moblin SDK & win great
>> > prizes
>> > Grand prize is a trip for two to an Open Source event anywhere in the
>> > world
>> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> > _______________________________________________
>> > Timidity-talk mailing list
>> > Tim...@li...
>> > https://lists.sourceforge.net/lists/listinfo/timidity-talk
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25164608.html
>> Sent from the TiMidity++ - General mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> 30-Day
>> trial. Simplify your report design, integration and deployment - and
>> focus on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Timidity-talk mailing list
>> Tim...@li...
>> https://lists.sourceforge.net/lists/listinfo/timidity-talk
>>
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> 30-Day 
> trial. Simplify your report design, integration and deployment - and focus
> on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Timidity-talk mailing list
> Tim...@li...
> https://lists.sourceforge.net/lists/listinfo/timidity-talk
> 
> 

-- 
View this message in context: http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25171137.html
Sent from the TiMidity++ - General mailing list archive at Nabble.com.

Re: [timidity-talk] Clicking Noise On Some SoundFonts

[Eric W. <ew...@bi...>]

I tried the links below to the problematic files, but they don't appear to
work anymore.  Could the original author repost them somewhere else?

-Eric

On Wed, 26 Aug 2009, Aaron Krister Johnson wrote:

> Hi,
>
> I can confirm that this happens to me too, and can also confirm that it is
> indeed annoying!
>
> I've noticed it for all versions of Timidity as far back as I can remember
> using it, say from 2003....
>
> Best,
> AKJ
>
>
> A. Kalten wrote:
> >
> > Hello list,
> >
> > Timidity usually gives good results, but on some soundfonts it will
> > produce an annoying clicking sound.  As an example, I have uploaded
> > an MP3 of a wave file created with Timidity that contains the clicking
> > noise.  Also uploaded are the MIDI file and the soundfont used (there
> > is only a single instrument involved).
> >
> > http://firstbooks.biz/midi/beatgen.mp3   (MP3 file is about 3.4 Mb)
> >
> > http://firstbooks.biz/midi/beatgen.mid
> >
> > http://firstbooks.biz/midi/WT_Clarinet.sf2  (SF2 file is about 330 kB)
> >
> > Note: This is a microtonal composition, so if the tuning sounds a bit
> > off it is deliberate.
> >
> > If I render this file with fluidsynth the clicking noise does not
> > occur.  Also, if I tweak the attack or decay rates in the Timidity
> > configuration file, I can mitigate the clicking noise somewhat but
> > cannot eliminate it entirely.
> >
> > Could this be a problem with the soundfont or is Timidity just not
> > able to process SF2 fonts completely?
> >
> > Regards,
> >
> > AK
> >
> >
> > -------------------------------------------------------------------------
> > This SF.Net email is sponsored by the Moblin Your Move Developer's
> > challenge
> > Build the coolest Linux based applications with Moblin SDK & win great
> > prizes
> > Grand prize is a trip for two to an Open Source event anywhere in the
> > world
> > http://moblin-contest.org/redirect.php?banner_id=100&url=/
> > _______________________________________________
> > Timidity-talk mailing list
> > Tim...@li...
> > https://lists.sourceforge.net/lists/listinfo/timidity-talk
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25164608.html
> Sent from the TiMidity++ - General mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Timidity-talk mailing list
> Tim...@li...
> https://lists.sourceforge.net/lists/listinfo/timidity-talk
>

Re: [timidity-talk] Clicking Noise On Some SoundFonts

[Aaron K. J. <aa...@ak...>]

Hi,

I can confirm that this happens to me too, and can also confirm that it is
indeed annoying!

I've noticed it for all versions of Timidity as far back as I can remember
using it, say from 2003....

Best,
AKJ


A. Kalten wrote:
> 
> Hello list,
> 
> Timidity usually gives good results, but on some soundfonts it will
> produce an annoying clicking sound.  As an example, I have uploaded
> an MP3 of a wave file created with Timidity that contains the clicking
> noise.  Also uploaded are the MIDI file and the soundfont used (there
> is only a single instrument involved).
> 
> http://firstbooks.biz/midi/beatgen.mp3   (MP3 file is about 3.4 Mb)
> 
> http://firstbooks.biz/midi/beatgen.mid
> 
> http://firstbooks.biz/midi/WT_Clarinet.sf2  (SF2 file is about 330 kB)
> 
> Note: This is a microtonal composition, so if the tuning sounds a bit
> off it is deliberate.
> 
> If I render this file with fluidsynth the clicking noise does not
> occur.  Also, if I tweak the attack or decay rates in the Timidity
> configuration file, I can mitigate the clicking noise somewhat but
> cannot eliminate it entirely.
> 
> Could this be a problem with the soundfont or is Timidity just not
> able to process SF2 fonts completely?
> 
> Regards,
> 
> AK
> 
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Timidity-talk mailing list
> Tim...@li...
> https://lists.sourceforge.net/lists/listinfo/timidity-talk
> 
> 

-- 
View this message in context: http://www.nabble.com/Clicking-Noise-On-Some-SoundFonts-tp19123503p25164608.html
Sent from the TiMidity++ - General mailing list archive at Nabble.com.

[timidity-talk] timidity as an add-on to a music editor

[David F. <df...@an...>]

Hi
A friend has written a music editing program and I use Timidity++ with
it - to play back the musical notation.

He has recently added a cursor to the program that follows the music as
it is played. He has provided a delay option to the cursor, to allow for
the time it takes for the sound fonts to load.

The time it takes Timidity to load the sound font varies from
arrangement to arrangement so I am finding that there is no convenient
value.

Is there some way for a 'headless' Timidity (eg alsa/pulse/jack
interface) to indicate when the first measure is being played - as is
used in the measure counter in the ncurses interface.

many thanks

David

[timidity-talk] Pro Patches light with Timidity

[andy_blah <and...@gm...>]

I have been trying to use Pro Patches light (a replacement .pat set for the
Gravis Ultrasound) with the Windows Timidity (the version from this site:
http://timidity.s11.xrea.com/index.en.html#down). I have tried to place a
timidity.cfg and a default.cfg file in the folder with the patches, and
tried to open it with Timidity from options, but every time I try to play a
midi, nothing happens and when I restart Timidity it just says that it can't
read the configuration file. Could somebody help me make Timidity work with
those patches? Both timidity.cfg and default.cfg contain this: 
 
dir C:\Games\OldGames\ULTRASND\MIDI\ 
 
0, 2, 1, 1, 1, acpiano 
1, 2, 1, 1, 1, britepno 
2, 2, 1, 1, 4, synpiano 
3, 2, 1, 1, 1, honky 
4, 2, 1, 1, 4, epiano1 
5, 2, 1, 1, 4, epiano2 
6, 2, 1, 1, 1, hrpschrd 
7, 2, 1, 1, 1, clavinet 
8, 12, 12, 12, 12, celeste 
9, 12, 12, 12, 12, glocken 
10, 12, 12, 12, 12, musicbox 
11, 12, 12, 12, 12, vibes 
12, 12, 12, 12, 12, marimba 
13, 12, 12, 12, 12, xylophon 
14, 12, 12, 12, 12, tubebell 
15, 12, 12, 12, 12, santur 
16, 2, 16, 16, 19, homeorg 
17, 2, 16, 16, 19, percorg 
18, 2, 16, 16, 19, rockorg 
19, 2, 16, 16, 19, church 
20, 2, 16, 16, 19, reedorg 
21, 2, 16, 16, 19, accordn 
22, 2, 16, 16, 19, harmonca 
23, 2, 16, 16, 19, concrtna 
24, 24, 24, 24, 24, nyguitar 
25, 24, 24, 24, 24, acguitar 
26, 24, 24, 24, 24, jazzgtr 
27, 24, 24, 24, 27, cleangtr 
28, 24, 24, 24, 24, mutegtr 
29, 29, 29, 29, 29, odguitar 
30, 29, 30, 30, 30, distgtr 
31, 29, 30, 30, 31, gtrharm 
32, 39, 32, 32, 32, acbass 
33, 39, 32, 32, 32, fngrbass 
34, 39, 32, 32, 36, pickbass 
35, 39, 32, 32, 32, fretless 
36, 39, 36, 36, 36, slapbas1 
37, 39, 36, 36, 36, slapbas2 
38, 39, 36, 36, 32, synbass1 
39, 39, 36, 36, 32, synbass2 
40, 40, 40, 40, 40, violin 
41, 40, 40, 40, 40, viola 
42, 40, 42, 42, 40, cello 
43, 40, 40, 40, 40, contraba 
44, 40, 40, 40, 40, tremstr 
45, 40, 40, 40, 45, pizzcato 
46, 24, 24, 46, 46, harp 
47, 47, 47, 47, 47, timpani 
48, 51, 51, 48, 48, marcato 
49, 51, 51, 49, 48, slowstr 
50, 51, 51, 48, 48, synstr1 
51, 51, 51, 48, 48, synstr2 
52, 52, 52, 52, 52, choir 
53, 52, 52, 52, 52, doo 
54, 52, 52, 52, 52, voices 
55, 128, 128, 55, 55, orchhit 
56, 56, 56, 56, 56, trumpet 
57, 56, 56, 56, 56, trombone 
58, 56, 56, 56, 58, tuba 
59, 56, 56, 56, 56, mutetrum 
60, 56, 56, 56, 56, frenchrn 
61, 56, 56, 56, 56, hitbrass 
62, 56, 56, 56, 56, synbras1 
63, 56, 56, 56, 56, synbras2 
64, 66, 66, 64, 64, sprnosax 
65, 66, 66, 66, 66, altosax 
66, 66, 66, 66, 66, tenorsax 
67, 66, 66, 66, 66, barisax 
68, 68, 69, 69, 69, oboe 
69, 68, 69, 69, 69, englhorn 
70, 68, 69, 69, 70, bassoon 
71, 68, 69, 69, 71, clarinet 
72, 73, 73, 73, 73, piccolo 
73, 73, 73, 73, 73, flute 
74, 73, 73, 73, 73, recorder 
75, 73, 73, 73, 75, woodflut 
76, 73, 73, 73, 75, bottle 
77, 73, 77, 77, 77, shakazul 
78, 73, 73, 73, 73, whistle 
79, 73, 73, 73, 73, ocarina 
80, 29, 29, 29, 29, sqrwave 
81, 29, 29, 29, 29, sawwave 
82, 73, 73, 29, 77, calliope 
83, 73, 73, 29, 29, chiflead 
84, 29, 29, 29, 29, charang 
85, 52, 52, 29, 85, voxlead 
86, 52, 52, 29, 86, lead5th 
87, 52, 52, 29, 32, basslead 
88, 52, 52, 88, 88, fantasia 
89, 52, 52, 29, 89, warmpad 
90, 52, 52, 29, 89, polysyn 
91, 52, 52, 29, 89, ghostie 
92, 52, 52, 29, 89, bowglass 
93, 52, 52, 29, 89, metalpad 
94, 52, 52, 29, 89, halopad 
95, 52, 52, 29, 89, sweeper 
96, 52, 52, 96, 89, aurora 
97, 52, 52, 52, 89, soundtrk 
98, 52, 52, 52, 89, crystal 
99, 52, 52, 52, 89, atmosphr 
100, 52, 52, 52, 89, freshair 
101, 52, 52, 52, 89, unicorn 
102, 52, 102, 102, 89, echovox 
103, 52, 102, 102, 89, startrak 
104, 24, 102, 102, 104, sitar 
105, 24, 105, 105, 105, banjo 
106, 24, 105, 105, 105, shamisen 
107, 24, 105, 105, 105, koto 
108, 115, 115, 115, 115, kalimba 
109, 24, 69, 105, 109, bagpipes 
110, 24, 42, 42, 40, fiddle 
111, 24, 105, 105, 105, shannai 
112, 114, 114, 112, 112, carillon 
113, 114, 114, 112, 112, agogo 
114, 114, 114, 114, 114, steeldrm 
115, 115, 115, 115, 115, woodblk 
116, 115, 117, 117, 117, taiko 
117, 115, 117, 117, 117, toms 
118, 115, 117, 117, 117, syntom 
119, 128, 128, 128, 128, revcym 
120, 128, 128, 128, 128, fx-fret 
121, 128, 128, 128, 128, fx-blow 
122, 128, 128, 128, 122, seashore 
123, 128, 128, 128, 128, jungle 
124, 128, 128, 128, 128, telephon 
125, 128, 128, 128, 128, helicptr 
126, 128, 128, 126, 126, applause 
127, 128, 128, 128, 128, pistol 
128, 128, 128, 128, 128, blank 
155, 128, 128, 128, 128, highq 
156, 128, 128, 128, 128, slap 
157, 128, 128, 128, 157, scratch1 
158, 128, 128, 128, 158, scratch2 
159, 159, 159, 159, 159, sticks 
160, 128, 128, 128, 160, sqrclick 
161, 128, 128, 128, 160, metclick 
162, 128, 128, 128, 128, metbell 
163, 163, 163, 163, 163, kick1 
164, 164, 164, 164, 164, kick2 
165, 165, 165, 165, 165, stickrim 
166, 166, 166, 166, 166, snare1 
167, 167, 167, 167, 167, claps 
168, 168, 168, 168, 168, snare2 
169, 171, 169, 169, 169, tomlo2 
170, 170, 170, 170, 170, hihatcl 
171, 171, 171, 171, 171, tomlo1 
172, 172, 172, 172, 172, hihatpd 
173, 175, 173, 173, 173, tommid2 
174, 174, 174, 174, 174, hihatop 
175, 175, 175, 175, 175, tommid1 
176, 178, 176, 176, 176, tomhi2 
177, 181, 177, 177, 177, cymcrsh1 
178, 178, 178, 178, 178, tomhi1 
179, 181, 177, 177, 177, cymride1 
180, 181, 177, 177, 180, cymchina 
181, 181, 177, 177, 181, cymbell 
182, 182, 182, 182, 182, tamborin 
183, 181, 177, 177, 177, cymsplsh 
184, 128, 128, 128, 128, cowbell 
185, 181, 177, 177, 177, cymcrsh2 
186, 128, 128, 128, 128, vibslap 
187, 181, 177, 177, 177, cymride2 
188, 178, 188, 188, 188, bongohi 
189, 175, 189, 189, 189, bongolo 
190, 175, 190, 190, 190, congahi1 
191, 175, 191, 191, 191, congahi2 
192, 171, 191, 191, 192, congalo 
193, 128, 128, 128, 193, timbaleh 
194, 128, 128, 128, 194, timbalel 
195, 128, 128, 128, 195, agogohi 
196, 128, 128, 128, 196, agogolo 
197, 128, 128, 128, 128, cabasa 
198, 128, 198, 198, 198, maracas 
199, 128, 128, 128, 128, whistle1 
200, 128, 128, 128, 128, whistle2 
201, 128, 128, 128, 128, guiro1 
202, 128, 128, 128, 128, guiro2 
203, 128, 128, 128, 128, clave 
204, 128, 204, 204, 204, woodblk1 
205, 128, 205, 205, 205, woodblk2 
206, 128, 128, 128, 206, cuica1 
207, 128, 128, 128, 207, cuica2 
208, 128, 128, 128, 208, triangl1 
209, 128, 128, 128, 209, triangl2 
210, 128, 128, 128, 128, shaker 
211, 128, 128, 128, 128, jingles 
212, 128, 128, 128, 128, belltree 
213, 128, 128, 128, 128, castinet 
214, 128, 128, 128, 128, surdo1 
215, 128, 128, 128, 128, surdo2 
 
 
I have uploaded the patch set here, so you could take a look: 
http://www.megaupload.com/?d=4R3CLFE1
-- 
View this message in context: http://www.nabble.com/Pro-Patches-light-with-Timidity-tp24681080p24681080.html
Sent from the TiMidity++ - General mailing list archive at Nabble.com.

[timidity-talk] using Timidity instruments inside OpenMPT running on Wine

[Paulo S. <nit...@gm...>]

Hi!
Is that possible to use Timidity instruments inside OpenMPT, running
on Wine? (i'm using Ubuntu Linux 9.04)
(i'm using OpenMPT running on Wine due on a lack of good trackers
nativelly running on GNU/LInux as good as OpenMPT - i did anyway a
request on OpenMPT developers on these sources being recoded to a more
open and multiplatform environment - and i'm not good in C coding
enough to replace all the mswindows-api calls into open api calls like
gnome, qt, wxwidgets or any other...)
Or, is it possible to obtain the Timidity 128 midi instruments as .wav
or .aiff instruments, and having them into OpenMPT?
thanks, and best regards to all

Re: [timidity-talk] Tuning with --freq-table

[Eric W. <ew...@bi...>]

On Sun, 26 Jul 2009, anisometropie wrote:

> 2009/7/26 Eric Welsh <ew...@bi...>
>
> > Try "#extension opt", and include the dashes before the arguments:
> >
> > #extension opt -B 2,8
> > #extension opt -EFreverb=0
> > #extension opt -s 32000
> > #extension opt --fast-decay
> > #extension opt --freq-table=/etc/timidity/temperament.egal
> >
> > -Eric
> >
>
> If i add the sharp #, it will comment the line.
> I've tried without and I get a syntax error for those lines :
>
> extension opt -iA
> extension opt -B2,8
> extension opt -Z /etc/timidity/temperament.egal
> extension opt -Os -EFreverb=0&

I googled for a man page and pulled up the following:

>>BEGIN QUOTE
   #extension opt [-]{option} [optarg]
          Sets the value of boot-time options.

   ...

   These  "#extension" statements are beginning with character '#' that is
   the comment flag of old TiMidity(version 0.2i or  earlier).   So
   these statememts are treated as comment line.
   The latest TiMidity treats "#extension" as white-space. So you can
   omit it.
<<END_QUOTE

So, #extension is treated as a special case and not treated as a comment.
It also looks like you can simply omit the #extension and use "opt" by
itself like you were originally doing (but don't forget to prefix the
options with their - signs).  I've always used the #extension lines, but
it looks like either way should work from the documentation.

-Eric

Re: [timidity-talk] Tuning with --freq-table

[anisometropie <ani...@gm...>]

2009/7/26 Eric Welsh <ew...@bi...>

> Try "#extension opt", and include the dashes before the arguments:
>
> #extension opt -B 2,8
> #extension opt -EFreverb=0
> #extension opt -s 32000
> #extension opt --fast-decay
> #extension opt --freq-table=/etc/timidity/temperament.egal
>
> -Eric
>

If i add the sharp #, it will comment the line.
I've tried without and I get a syntax error for those lines :

extension opt -iA
extension opt -B2,8
extension opt -Z /etc/timidity/temperament.egal
extension opt -Os -EFreverb=0&

Re: [timidity-talk] Tuning with --freq-table

[Eric W. <ew...@bi...>]

On Sun, 26 Jul 2009, anisometropie wrote:

> # Instrument configuration file for timidity
> # $Id: timidity.cfg,v 1.7 2005/09/03 19:26:03 hmh Exp $
> [...]
> #opt s32kHz             #default sample frequency to 32kHz
> #opt fast-decay         #fast decay notes
> *opt freq-table=/etc/timidity/temperament.egal*
>
> but this is not working.
> Any idea why?

Try "#extension opt", and include the dashes before the arguments:

#extension opt -B 2,8
#extension opt -EFreverb=0
#extension opt -s 32000
#extension opt --fast-decay
#extension opt --freq-table=/etc/timidity/temperament.egal

-Eric

[timidity-talk] Tuning with --freq-table

[anisometropie <ani...@gm...>]

Hello,

I'm using this command to start a timidity server.
*timidity -iA -B2,8 -Z /etc/timidity/temperament.egal -Os -EFreverb=0&*

i'm using the option* -Z /etc/timidity/temperament.egal *because I want to
set the A to 442hz, and still the have the equal temperament.

but this option *only* works when I use the command myself in bash.
I want this option to be used every times, even when I start my computer.

so I added this line to /etc/timidity/timidity.cfg :

# Instrument configuration file for timidity
# $Id: timidity.cfg,v 1.7 2005/09/03 19:26:03 hmh Exp $
[...]
#opt s32kHz             #default sample frequency to 32kHz
#opt fast-decay         #fast decay notes
*opt freq-table=/etc/timidity/temperament.egal*

but this is not working.
Any idea why?

thanks in advance.

Re: [timidity-talk] timidity midi to pcm project

[注册.吴 <zhf...@gm...>]

dear Yair K:
       problem 2 is ok.
thanks.
 Yours 
 FUFO          

--------------------------------------------------
From: "注册.吴" <zhf...@gm...>
Sent: Tuesday, July 21, 2009 9:08 AM
To: "Yair K." <ce...@gm...>; <tim...@li...>
Subject: Re: [timidity-talk] timidity midi to pcm project

> dear Yair K:
>     thanks for your reply.I have 2 problems.
>        
>     1. when I compile the MSVC6.0 project,there are some error. 
> 
> --------------------Configuration: timw32g - Win32 Debug--------------------
> Compiling...
> w32g_i.c
> D:\workshop\midi\TiMidity++-2.13.2\interface\w32g_i.c(3573) : warning C4013: 'messagesizeof' undefined; assuming extern returning int
> D:\workshop\midi\TiMidity++-2.13.2\interface\w32g_i.c(3573) : warning C4047: 'function' : 'const char *' differs in levels of indirection from 'int '
> D:\workshop\midi\TiMidity++-2.13.2\interface\w32g_i.c(3573) : warning C4024: 'strncpy' : different types for formal and actual parameter 2
> D:\workshop\midi\TiMidity++-2.13.2\interface\w32g_i.c(3573) : error C2198: 'strncpy' : too few actual parameters
> D:\workshop\midi\TiMidity++-2.13.2\interface\w32g_i.c(3577) : warning C4047: 'function' : 'const char *' differs in levels of indirection from 'int '
> D:\workshop\midi\TiMidity++-2.13.2\interface\w32g_i.c(3577) : warning C4024: 'strncpy' : different types for formal and actual parameter 2
> D:\workshop\midi\TiMidity++-2.13.2\interface\w32g_i.c(3577) : error C2198: 'strncpy' : too few actual parameters
> Error executing cl.exe.
> 
> timw32g.exe - 2 error(s), 5 warning(s)
> 
>   2.  if I comment 'strncpy' ,it can compile success. when I run timw32g.exe ,it warning "..can't read any configuration file.." and if I open any midi file to play,there are no sound .(even if I set Output is "AIFF FILE", the aiff file is also no sound.)
>   
> thanks .
> your reply is very appreciated.
> Yours 
> FUFO
> 
> 
> --------------------------------------------------
> From: "Yair K." <ce...@gm...>
> Sent: Monday, July 20, 2009 8:53 PM
> To: <tim...@li...>
> Subject: Re: [timidity-talk] timidity midi to pcm project
> 
>> On Mon July 20 2009 13:49:39 注册.吴 wrote:
>>> dear all:
>>>           I am study midi .I want a project thank can decoder a midi file
>>> to pcm file.I have downloaded TiMidity++-2.13.2 . when I compile it in
>>> MSVC6.0, I find it it difficult to me .so are there anybody have such
>>> project in MSVC6.0? thanks all
>> 
>> I recall there's a MSVC6 project in the configs/ subdirectory.
>> 
>> Yours,
>> Yair K.
>> 
>> ------------------------------------------------------------------------------
>> Enter the BlackBerry Developer Challenge  
>> This is your chance to win up to $100,000 in prizes! For a limited time, 
>> vendors submitting new applications to BlackBerry App World(TM) will have
>> the opportunity to enter the BlackBerry Developer Challenge. See full prize  
>> details at: http://p.sf.net/sfu/Challenge
>> _______________________________________________
>> Timidity-talk mailing list
>> Tim...@li...
>> https://lists.sourceforge.net/lists/listinfo/timidity-talk
>>