Re: [Timidity-devel] Patching autoconf fragments for C99 compatibility

[TAMUKI S. <ta...@li...>]

Hello Jonathan-san and all,

I am one of the members involved in the development and maintenance of
TiMidity++.  Due to personal circumstances, the frequency of receiving
E-mails has decreased.  I apologize for the delay in replying from the
TiMidity++ development members and causing everyone concern.

Around the beginning of 2000, MIDI and its peripheral standards such
as SMF were widely used by general users and industry people.
However, due to various factors, the number of users using other
standards and formats increased, and it seemed that MIDI was gradually
dying out, especially in Japan.  It seems that the TiMidity++
development members who were busy at the time have gradually faded out
and are now active in various fields.  Nonetheless, there is universal
demand for MIDI among core users and industry people, and I believe
that TiMidity++ has a reason for existence.  I believe other
TiMidity++ developers have similar thoughts.

By the way, I'm working with another group of people to develop our
own Linux distribution based on Slackware.  TiMidity++ is one of the
major packages in the Linux distribution's multimedia category.  Of
course, we also maintain packages such as libtimidity, SDL_sound, and
SDL_mixer.  I didn't know about Open Cubic Player UNIX version, but
it looks interesting software, so I'd like to try it someday.  I run
the TiMidity++ hourly tarball release mechanism on our Linux
distribution development server.  It checks for patch commits every
hour, performs a compilation test if there is an update, and uploads a
tarball.  Some time ago, our Linux distribution development server
suffered a severe failure.  Fortunately, the data remains intact, and
most of the functions necessary for development have been restored,
but the TiMidity++ hourly tarball release mechanism remains suspended.
Restoration is delayed due to the low patch volume.

Jonathan-san, thank you very much for sending us the patch that fix
code that relies on obsolete C89 features such as implicit function
declarations and implicit ints.  It looks good to me.  I would like to
commit this patch, but I am hesitant because the TiMidity++ hourly
tarball release mechanism is stopped as mentioned above.  I would like
to restore it as soon as possible, so please wait for a while.  Not
only will we accept compilation issues like this one and security
patches, but we will also work on extending features and implementing
new features in line with the current situation.

From: Ozkan Sezer <se...@gm...>
Subject: Re: [Timidity-devel] timidity-devel shout out for main-developer
Date: Tue, 21 Feb 2023 20:40:15 +0300

> My interest is that I'm maintaining libtimidity:
> 
> https://sourceforge.net/projects/libtimidity/
> mirror: https://github.com/sezero/libtimidity
> 
> ... which is a fork from old SDL_sound which in turn had it forked from
> old timidity-0.2i, with additional fixes such as
> https://web.archive.org/web/20170824103526/http://www.onicos.com/staff/iz/timidity/dist/timidity-0.2i-bugfix.pat
> (that onicos.com archive seems have been gone, unfortunately, hence the
> archive.org link) and few additional bits from timidity++. Also applied
> an initial soundfont patch of Takashi Iwai to libtimidity (in soundfont
> branch), but keeping it as devel for now for lack of timidity++ config
> compatibility in it yet.

Ozkan-san, the site above has moved:

http://www33146ue.sakura.ne.jp/staff/iz/timidity/dist/timidity-0.2i-bugfix.pat

Regards,
TAMUKI Shoichi